| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Connector for SAP R/3 > Customizing Integrations > Modifying Standard Integration Interfaces >
Understanding the Standard Integration Interfaces
The following topics describe the technical implementation of each business data flow used by the standard integrations.
SAP Field Mappings contains tables with all field mappings performed by the business service data maps.
Customer to Account Business Data Flow
Figure 4 shows the business data flow for the Customer to Account standard integration. In this scenario SAP is the System of Record (SOR) for Account/Customer master data. SAP initiates this flow in the form of a customer IDOC. The tRFC BAPI Receiver receives the IDOC and passes it to the SAP 4x Account-Update Siebel Account (4x IDOC) workflow. The workflow consists of a single business service data map that transforms the data contained in the IDOC to a Siebel integration object. This integration object instance is then passed to the Siebel adapter which updates the Siebel Database.
Account to Customer Business Data Flow
In this scenario Siebel is the System of Record (SOR) for Account/Customer master data. The Account to Customer standard integration uses synchronous BAPI communication as well as SAP's ALE communication services to create and update SAP customer information from Siebel accounts.
There are two business data flows at work here.
- Create Initial SAP Customer from Siebel Account (SAP General Data)
- Update SAP Customer from Siebel Account (SAP Sales Area Data)
These business data flows are called from the high-level workflow, "SAP 4x Account - Create or Update SAP Customer". This workflow branches based on whether or not a new customer is being created or a customer is being updated in SAP. If a new customer is being created, the first business data flow is invoked followed by the second data flow. If a customer is being updated, then only the second Business data flow is invoked.
The first business data flow (Figure 5) performs an initial creation of the customer in SAP. This is done through a synchronous BAPI call to SAP. This call provides an immediate response with the customer ID from SAP. Figure 5 shows the details of the SAP 4x Account-Create SAP Customer (BAPI) workflow. In this workflow, a record from the Siebel Database is extracted by the Siebel Adapter, passed to the SAP 4x Account-SAP Maps (MO) business service, and then passed to the BAPI adapter. The BAPI adapter communicates with SAP R/3 using the BAPI_CUSTOMER-CREATEFROMDATA BAPI, followed by the BAPI-TRANSACTIONCOMMIT BAPI. SAP R/3 returns the record to the BAPI Adapter, which forwards it to the SAP 4x Account - SAP Maps (MO) business service, which then forwards it the Siebel Adapter, which writes the record back to the Siebel Database.
In this business data flow, the Siebel Adapter extracts the account information. It passes an integration object instance containing this data to a business service data map, which converts it into a BAPI input integration object. Then it passes the integration object instance to the BAPI adapter and makes a call to SAP to create the customer. An additional call (not shown in Figure 6) commits the customer created in SAP. SAP returns the customer ID. The customer ID then resides in the BAPI Output integration object instance and this is passed to another business service data map. This business service data map creates a Siebel integration object instance with the name of the customer ID contained within it and this is used to update the Siebel Database.
Figure 6 shows the second business data flow, which updates the customer through an IDOC. The IDOC can pass in more information for the customer than the BAPI call. In particular, an IDOC can pass sales area information for the customer but a BAPI cannot. The figure illustrates the SAP 4x Account-Update SAP Customer (4x IDOC) workflow, which consists of the Siebel Adapter passing a record to the SAP 4x Account - SAP Maps (MO) business service. The SAP 4x Account - SAP Maps (MO) business service passes the record to the IDOC Adapter, which uses the BAPI tRFC Adapter to pass the record to SAP R/3 using the DEBMAS02 IDOC type.
This business data flow extracts account information from the Siebel Database using the Siebel Adapter and passes this to a business service data map in the form of an integration object. This map transforms the Siebel integration object into an IDOC integration object that is then passed to the IDOC adapter. The IDOC Adapter must be configured to call the BAPI tRFC adapter business service. This business service is very similar to the BAPI adapter, but handles Transactional RFC calls. For more information on this adapter as well as the IDOC adapter, read BAPI Interfaces and IDOC Interfaces.
Material to Product Business Data Flow
Figure 7 shows the business data flow for the Material to Product standard integration. SAP initiates this flow in the form of a material IDOC of message type MATMAS03. The IDOC is received by the tRFC BAPI receiver and passed to the Product-Receive SAP 4x Material (4x IDOC) workflow. The workflow consists of the Product-SAP 4x Maps business service that transforms the data contained in the IDOC to a Siebel integration object. This integration object instance is then passed to the Siebel adapter and the Siebel Database is updated.
Siebel Sales Order to SAP Sales Order Business Data Flows
The Siebel Sales Order to SAP Sales Order standard integration contains several business data flows. Using this interface you can perform the following actions:
- Validate the sales order
- Submit the sales order
- Update the sales order status
Three business data flows support these actions. Figure 8 shows the business data flow to validate a sales order. This consists of the Order-Simulate SAP 4x Order workflow. This workflow extracts a record from the Siebel Database, using the Siebel Adapter, which passes the record to the Order-SAP 4x Maps business service. This business service sends the record to the BAPI Adapter. The BAPI Adapter communicates with SAP R/3 using the BAPI SALES ORDER SIMULATE BAPI. SAP R/3 returns the record through the BAPI Adapter, which passes it to the Order-SAP 4x Maps business service. The Order-SAP 4x Maps business service passes it to the Siebel Adapter, which writes it to the Siebel Database.
Figure 9 shows the business data flow for submitting the sales order to SAP. This consists of the Order-Create SAP 4x Order workflow. This workflow extracts a record from the Siebel Database using the Siebel Adapter, which sends the record to the Order-SAP 4x Maps business service. This business service passes the record to the BAPI Adapter. The BAPI Adapter communicates with SAP R/3 using the BAPI SALES ORDER_CREATEFROMDAT1 BAPI. SAP R/3 returns the record through the BAPI Adapter. The adapter sends it to the Order-SAP 4x Maps business service. This business service transmits the record to the Siebel Adapter, which writes it to the Siebel Database.
Figure 10 shows the business data flow for retrieving sales order status. This consists of the Order-Create SAP 4x Order workflow. This workflow extracts a record from the Siebel Database, using the Siebel Adapter, which passes the record to the Order-SAP 4x Maps business service. This business service sends the record to the BAPI Adapter. The BAPI Adapter communicates with SAP R/3 using the BAPI SALES ORDER GETSTATUS BAPI. SAP R/3 returns the record through the BAPI Adapter, which passes it to the Order-SAP 4x Maps business service. This business service sends the record to the Siebel Adapter, which writes it to the Siebel Database.
Quote to Sales Order Business Data Flow
The Quote to Sales Order standard integration contains several business data flows. Using this interface you can perform the following actions:
- Validate the Quote
- Submit the Quote as a Sales Order
Figure 11 shows the business data flow for quote validation, which is similar to sales order validation, except for some additional business service data maps that convert a quote to a sales order and a sales order to a quote.
This consists of the Quote to Order SAP 4x Validate workflow. This workflow extracts a record from the Siebel Database, using the Siebel Adapter, which passes the record to the Order-SAP 4x Maps business service. This business service sends the record to the BAPI Adapter. The BAPI Adapter communicates with SAP R/3 using the BAPI_SALES ORDER_SIMULATE BAPI. SAP R/3 returns the record through the BAPI Adapter, which passes it to the Order-SAP 4x Maps business service. This business service sends the record to the Siebel Adapter, which writes it to the Siebel Database.
Submitting the quote as a sales order to SAP is similar to submitting a sales order. Figure 12 shows this business data flow. This consists of the Quote to Order SAP 4x Submit workflow. This workflow extracts a record from the Siebel Database, using the Siebel Adapter, which passes the record to the Order-SAP 4x Maps business service. This business service sends the record to the Siebel Adapter. The Siebel Adapter writes the record back the Siebel Database and calls the Order-Create SAP 4x Order workflow. The Order-Create SAP 4x Order workflow communicates with SAP R/3 using the BAPI_SALES ORDER_CREATEFROMDAT1 BAPI. SAP R/3 returns the record through the Order-Create SAP 4x Order workflow, which updates the Siebel Database. Note that the Siebel adapter is called to insert the sales order into the Siebel Database prior to the call to SAP.
Sales Order Updates Business Data Flow
Figure 13 shows the business data flow for the Sales Order Updates standard integration. It is triggered by the arrival of an ORDCHG message from SAP. SAP can be configured to send this message when a sales order in SAP has been changed. When the Siebel application receives an IDOC associated with the ORDCHG message, it retrieves the Sales Order ID from the message and calls the workflow "Order - Change SAP 4x Order Status" to retrieve Sales Order status from SAP and update the Siebel Database. The Siebel Sales Order to SAP Sales Order standard integration covers this workflow.
Account Order History Business Data Flow
Retrieval of Account Order History contains two business data flows. Figure 14 shows the business data flow for Get SAP Order List. This consists of the Account-Get SAP Order List (MO) workflow. This workflow extracts a record from the Siebel Database, using the Siebel Adapter, which passes the record to the Order-SAP 1x Maps business service. This business service sends the record to the BAPI Adapter. The BAPI Adapter communicates with SAP R/3 using the BAPI SALES ORDER GETLIST BAPI. SAP R/3 returns the record through the BAPI Adapter, which passes it to the Order-SAP 4x Maps (MO) business service. This business service sends the record to the Siebel Adapter, which writes it to the Siebel Database.
This flow retrieves the list of orders from SAP when given a customer ID from an account in the Siebel application. When you select one of these orders, it can be imported from SAP into the Siebel application. Figure 15 shows the business data flow for importing the SAP order. This consists of the Account-Import SAP Order (MO) workflow. This workflow extracts a record from the Siebel Database using the Siebel Adapter, which passes the record to the SAP 1x Order (Get SAP Order List) (MO) business service. This business service creates the Account-Import SAP Order (Siebel Order List) (MO) integration object and sends this integration object to the Siebel Adapter, which writes it to the Siebel Database.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Connector for SAP R/3 Published: 22 August 2003 |
