|Bookshelf Home | Contents | Index | PDF|
SAP Field Mappings contains tables with field mappings performed by the business service data maps.
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 Account - Receive SAP 46C Customer 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.
In this scenario, the Siebel application 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 four different data flows. The main workflow, Account - Submit SAP 46C Customer, orchestrates these data flows as shown in Figure 5.
This business data flow is called by the main workflow, Account - Submit SAP 46C Customer, when it determines that a new customer needs to be created. It uses a synchronous BAPI call to SAP to get the next available customer number. Note this BAPI does not create the customer in SAP but returns the next available customer number.
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 get the customer number. 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.
This business data flow extracts account information from the Siebel database using the Siebel Adapter and passes this to a Business Service 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.
Figure 9 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 46C Material workflow. The workflow consists of the Product-SAP 46C 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.
Figure 10 shows the business data flow to validate a sales order.
An Order is submitted from Siebel to SAP through the workflow Order - Create SAP 46C Order and Get Detailed List. This flow calls two lower level workflows: Order - Create SAP 46C Order and Order - Get Detailed List SAP 46C Order. These flows are shown in Figure 11 and Figure 12. Figure 11 shows the business data flow for submitting the sales order to SAP.
Figure 12 shows the business data flow for retrieving sales order status. The GetSAP46CGetDetailedList_BAPIToSiebel map is dependent upon the LOV SAP_SO_PART_MOVEMENT_TYPE and uses LOV values defined to set Line Item Action Type in the Siebel application.
The Quote to Sales Order standard integration contains one business data flow to validate the quote. Figure 13 shows the business data flow for quote validation.
The Business Data Flow for the Order Updates Standard Integration is shown in Figure 14. It is triggered by the arrival of an ORDCHG message from SAP. SAP can be configured to send this message when an order in SAP has been changed. When the IDOC associated with the ORDCHG message is received by the Siebel application, the Order ID is retrieved from the message and the workflow, Order - Get Detailed List SAP 46C Order, is called to retrieve Order status from SAP and update the Siebel database. This workflow is discussed in Siebel Sales Order to SAP Sales Order Standard Integration.
Retrieval of Account Order History contains two business data flows called by the top-level workflow Account - Import SAP 46C Order and Get Detailed List SAP 46C Order. The first is shown in Figure 15, the second is shown in Figure 16.
This flow retrieves the list of orders from SAP when given a customer ID from an account in the Siebel database. When a Siebel user selects one of these orders, it can be imported from SAP into the Siebel database. This Business Data Flow is shown in Figure 16.
|Siebel Connector for SAP R/3|