Siebel Connector for SAP R/3 > Customizing Integrations > Building the Interfaces >

Integration ID

Integration ID serves many purposes. It refers to the back office objects such as customer number, sales order number, and so on. Integration ID can also be used in the user keys. Integration ID is used for both BAPI and IDOC based data flows.

BAPI-Based Data Flows

Standard BAPI data flows are used to either create new objects in SAP or get updated information from SAP. For both these cases Integration ID is used to update Siebel objects with SAP document number such as order number and customer number created in SAP.

For some special business objects such order, Integration ID is used to enforce the business rules. After the integration ID is populated with the back office information, then further update to the order business object is not allowed. The Integration ID is also used as one of the import parameters for the BAPI when the BAPI is used to extract information from SAP.

IDOC-Based Data Flows

IDOC-based data flows are generally one-way data transfers and are used in an asynchronous mode. Here the Integration ID becomes even more important as it is used not only to hold information about SAP document number but also used in the User Key to synchronize IDOC objects.

For inbound IDOCs like Product and Account data flows (from SAP to the Siebel application), the Integration ID is used as first User key for data transactions like Insert, Update, and Delete. In this case, the Integration ID is unique, because it is used as the primary key in the connected external application.

Make sure that incoming documents, such as Customer/Material, have a unique document number when sent to the Siebel application.