What I know is the technical solution of Siebel integrated with SAP

As the company develops, more and more systems are used. the ERP system uses sap and the CRM system uses Siebel to share and exchange data between systems. the following describes the sap and Siebel integration solutions I have learned.

Why do systems share and exchange data? Because the functions of the system are different. for example, the CRM system focuses on the management of customer/sales/performance information for product sales analysis, and the customer data is comprehensive, the material information only needs to use the materials used during the customer's transaction. The customers stored in the ERP system are narrow and only Store Contract customers who have direct transactions with the company. For materials, because the ERP system includes control over production, material information such as raw materials and semi-finished products also needs to be managed. that is, customers in the ERP system are a subset of customers in the CRM system, and materials in CRM are a subset of materials in the ERP system. if both sides maintain data together, it is easy to cause confusion. The best way is to passProgramDirect transfer to another system, such as maintaining material data in the ERP system, and then synchronizing the materials required in the CRM system to the CRM system.

Synchronous and asynchronous. synchronization means that after a sends a request or sends data to B, B immediately processes the data and returns the processing result. asynchronous processing is not necessarily performed immediately, requests are queued for processing and generally do not return processing results.

1. the main integration method of synchronization is bapi call, that is, RFC function call. in SAP, a function is created for se37, marked as an RFC function, and called by Siebel. of course, sap can also call the functions provided by Siebel, but this method has not been used yet. lightweight, the advantage is that the processing result can be returned immediately, which is suitable for real-time requirements or returned values; however, the bapi function or custom RFC function in SAP does not leave a record when it is called, and the execution result is unknown (basis may find the call log ?).
2. asynchronous integration, I mainly use the IDOC method. In IDOC mode, the SAP end must first define an IDOC data structure. When the system transmits data, it will string the data into a string and send it to the external system (if it is inbound, the received strings are parsed according to the corresponding structure.) After receiving the strings, the system parses the values of each field according to the agreed format and processes them accordingly. IDOC can send one or more messages at a time to enter the corresponding processing queue and wait for processing. the magnitude is slightly heavier than the bapi method (but it is not ideal for a large amount of data). The advantage is that each IDOC's inbound and outbound sites have records, and the data information and control information are easy to find, it is easy to track the results of Data Synchronization updates and facilitate tracking and debugging.