Best Practices

Update iObjects with Transactional Data Using Individual Object Integration Framework

  • by Conny Dahlgren, Senior Consultant, SAP Australia
  • July 15, 2006
Learn the four steps to configure iObjects in mySAP CRM and get a fundamental understanding of the Individual Object Integration Framework configuration. This best practice solves the issue of having to correct and update business partner information within iObjects.
Key Concept
Individual Object Integration Framework (IOITF) manages an individual object’s (iObject’s) lifecycle in the context of a mySAP CRM solution. An iObject stores data for just one object, such as a vehicle, a piece of equipment, or other object that has a unique identification number. IOITF enables applications to interact with iObjects by using a defined protocol (event history) and protects iObject data from inconsistent changes. With IOITF, you can centrally maintain business rules (logic) that impact an iObject.

Say you buy a new car and purchase a service contract for it. The car manufacturer tracks who owns the car and the service contract in mySAP CRM. By tracking the service contract, the car manufacturer can ensure that the owner receives the appropriate service. The car manufacturer could even offer you promotions, such as coupons when the car has achieved a certain mileage.

You could directly identify the driver of the car from the individual object (iObject) (the car) instead of deriving the data from the service contract. The system adds a timestamp when you update the car driver information. This makes it possible to see when a car has changed drivers and who the previous drivers were.

With similar logic, you could, for example, also view who was the last service technician who used a piece of equipment or serviced a vehicle. Instead of using the sold-to party of a service contract as I use in my car example, you would use the service technician on the service or sales order. Using my car example, I will explain the four-step process for configuring an iObject so that you can update it with the business partner used in a transaction. This process also gives you insight into how IOITF works, enabling you to use it for other objectives that suit your business needs.

First, you configure the code and event changes for IOITF customizing. Then you maintain this customizing and the iObject category. Finally, you test the setting by creating a test service contract to ensure that the system updates the iObject accordingly. I have tested this process in mySAP CRM 4.0 and mySAP CRM 2005. People skilled in either mySAP CRM or ABAP should be able to perform the steps in this process.

Conny Dahlgren

Conny Dahlgren is a senior consultant with SAP Australia in Melbourne. He has worked with mySAP CRM since 2000, and with SAP products, including SD and MM, for more than nine years. Within mySAP CRM, Conny has experience in most areas in different roles. Currently he is a CRM solution architect for a large CRM project focusing on service and marketing.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.