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 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 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.

Figure 4. Business Data Flow for the Customer to Account Standard Integration

Account to Customer Data Flow

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.

Figure 5. Business Data Flow for the Account to Customer Standard Integration
Click for full size image

This flow does the following:

  1. Retrieves the Siebel account from the Siebel database.
  2. Branches on whether or not the SAP Integration ID (Customer Number) exists in the Siebel Account. This determines whether or not the account has been sent to SAP:
    1. If the Integration ID does not exist, then reserves a customer number for the account in SAP and sends an IDOC to SAP with the customer information.
    2. If the Integration ID exists, then checks for the existence of this customer in SAP (this action makes sure that any previously sent customer IDOC has been processed) and updates the customer in SAP by sending an IDOC. If the customer does not exist in SAP, then error text is generated.

Account - Request SAP 46C Customer Number Data Flow

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.

Figure 6. Business Data Flow Using BAPI Adapter

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.

Account - Send SAP 46C Customer Data Flow

This business dataflow is used to create or update the customer in SAP. The account information is passed to SAP using IDOC DEBMAS05.

Figure 7. Business Data Flow Using IDOC Adapter

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.

Account - Check SAP 46C Customer Data Flow

This business data flow is used to check the existence of a customer in the SAP system.

Figure 8. Business Data Flow for the Check SAP Customer Standard Integration

Material to Product Business Data Flow

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. Using the ISS Authoring Import Export Service, release the Siebel integration object.

Figure 9. Business Data Flow for the Material to Product Standard Integration

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.

Figure 10 shows the business data flow to validate a sales order.

Figure 10. 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 11. 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.

Figure 12. Business Data Flow for Retrieving Sales Order Status

The Order - Get Detailed List SAP 46C Order workflow is used both to update order status in the Siebel application and to get the detailed order information when creating an order.

Quote to Sales Order Business Data Flow

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.

Figure 13. Business Data Flow for Quote Validation

Order Updates Business Data Flow

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.

Figure 14. Business Data Flow for the Sales Order Updates Standard Integration

Account Order History Business Data Flow

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.

Figure 15. Business Data Flow for Get SAP Order List

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.

Figure 16. Business Data Flow for Importing the SAP Order
Siebel Connector for SAP R/3