Bookshelf Home | Contents | Index | PDF |
Siebel Connector for SAP R/3 > Customizing Integrations > Building the Interfaces > Adding the SAP InterfacesYou need to use different Siebel business services depending upon the type of interface you are using with SAP. The following topics discuss the business services that you need in your workflow. Siebel-to-SAP InterfacesIf you are creating a workflow which must make a synchronous BAPI/RFC call you need to add the BAPI Adapter business service to your workflow. To make synchronous BAPI calls
For more information on using the BAPI Adapter see BAPI Interfaces. See workflows provided for the SAP standard integrations for examples. If you are creating a workflow which must make an transactional RFC call, you need to add the tRFC BAPI Adapter business service to your workflow. To make Transactional RFC calls
The tRFC BAPI Adapter can be configured to use the EAI Queue to temporarily store data within the BAPI call for recovery in case of error during transit to SAP. For more information on using the tRFC BAPI Adapter see BAPI Interfaces. If you are creating a workflow which must send an IDOC to SAP, you need to add the IDOC Adapter Business Service to your workflow.
The IDOC Adapter converts the IDOC to an RFC call and then invokes the tRFC BAPI Adapter. For this reason, this call can be configured to use the EAI Queue to temporarily store data within the IDOC for recovery in case of error during transit to SAP. For more information on using the tRFC BAPI Adapter with EAI Queue see BAPI Interfaces. For more information on using the IDOC Adapter see IDOC Interfaces. The SAP standard integrations provide examples of sending an IDOC to SAP. SAP-to-Siebel InterfacesThe tRFC BAPI Receiver processes data that SAP sends. This component invokes a workflow to process the data. The tRFC BAPI Receiver may receive an IDOC or a tRFC call from SAP. In each case, the first step in a workflow invoked by the receiver is a Business Service Data Map that accepts an EAI Property Set in the form of a SiebelMessage containing an IDOC or BAPI Input Integration Object instance. Figure 21 illustrates IDOC Processing and tRFC Call Processing. In IDOC Processing, data from SAP R/3 goes to the Siebel tRFC BAPI Receiver, which passes it to the IDOC Workflow Processor, which passes it a specific workflow (data dependent). This workflow consists of a Business Service Data Map and the Siebel Adapter. The Siebel Adapter then writes the data to the Siebel database. In tRFC Call Processing, data from SAP R/3 goes to the Siebel tRFC BAPI Receiver, which passes it a specific workflow (data dependent). This workflow consists of a Business Service Data Map and the Siebel Adapter. The Siebel Adapter then writes the data to the Siebel database. In each case no specific adapter needs to be added to the workflow to interface to SAP as this interface occurs outside of the workflow. When adding your business service data map to a Siebel workflow, you must create a process property in your workflow with the name SiebelMessage. This process property must then be an input to the initial business service data map. The services external to the workflow handles passing this SiebelMessage to your workflow and the process property of this name. NOTE: The SiebelMessage Process Property must be named "SiebelMessage", exactly as shown here. Do not use any spaces in the name. If the name is not correct, an error message results indicating that there are no children of type SiebelMessage in the property set passed to your workflow. Receiving IDOCs from SAPWhen receiving IDOCs from SAP there are two important configuration items to define:
For more information on configuration of user properties, see IDOC Interfaces. Receiving tRFC Calls from SAPWhen receiving a tRFC call from SAP there are two important configuration items to define:
For more information on configuration of user properties, see BAPI Interfaces. |
Siebel Connector for SAP R/3 |