Bookshelf Home | Contents | Index | Search | PDF

Siebel Connector for SAP R/3 > IDOC Interfaces > IDOC Integration >

Receiving IDOCs from SAP

---

The EAI SAP BAPI receiver (tRFC) service may receive IDOCs from SAP as well as BAPI calls. When an IDOC is received, the EAI SAP IDOC Workflow Processor service is invoked to convert the raw data received from SAP into an IDOC integration object. This service then invokes the EAI SAP IDOC Workflow Service to invoke a workflow in the Siebel application. This topic provides additional information on the configuration and usage of the EAI SAP IDOC Workflow Processor service and the EAI SAP IDOC Workflow Service.

IDOC Workflow Processor Configuration

The business service EAI SAP IDOC Workflow Processor is called by the tRFC BAPI receiver when it receives an IDOC. Table 36 summarizes the user properties and component parameters that may be set to control its behavior. Those variables that may be set as component parameters must be set for the BAPIRcvr component.

Table 36.  IDOC Workflow Processor Configuration Options

Name	User Prop	Comp Param	MethodArg	Valid Values	Usage
SiebelMessage			X		Integration Object with raw data from the tRFC BAPI receiver.
DispatchFormat	X			"ALE"	Currently set to "ALE". This should not be changed.
DispatchService	X				Business Service to send IDOC integration object to workflow. This must be a service based on CSSWfEngine. Currently set to EAI SAP IDOC Workflow Service.
DispatchMethod	X				Business service method to call in DispatchService.
SAPIdocAllowedObjectnn	X				Name of IDOC Integration Object that can be accepted by the workflow processor. Read and the following note and caution.
SAPCodepage	X	X	X	Value from Transcode Encoding picklist	Siebel Codepage name for SAP codepage.
SAPIgnoreCharSetConvErrors	X	X	X	True or False	Default is False. If True, codepage conversion errors are handled by substitution of the question mark (?) character in place of an unrecognized character.

NOTE:  There may be up to 99 user properties defined with a name of the form, SAPIdocAllowedObjectnn, such as SAPIdocAllowedObject01, SAPIdocAllowedObject02, SAPIdocAllowedObject03, and so on. Each of these would contain the name of an IDOC Integration Object that can be accepted by the IDOC Workflow Processor.

CAUTION:  When an IDOC is received from SAP, the External Name is extracted from information in the control record of the IDOC. This name is then compared with the External Names for each integration object listed in the user properties SAPIdocAllowedObjectnn. When a match on the External Name is found, the corresponding IDOC integration object is used. For this reason, each IDOC integration object defined by an SAPIdocAllowedObjectnn user property must have a distinct external name. For example, two IDOC integration objects that both have the external name of DEBMAS02 cannot be used at the same time.

Invoking Workflows

Once an IDOC is received and passed to the Workflow Processor, the Workflow Processor must pass this IDOC integration object on to a specific workflow. The workflow name can be defined in two ways:

The Workflow User Property on the IDOC Integration Object definition in Siebel Tools can be set to the workflow name. When this type of IDOC Integration Object is received, it is sent to this workflow name. The workflow name must be set using Siebel Tools and the changed integration object must be compiled into the Siebel srf file.
The workflow name may be set in the ProcessName user property of the EAI SAP IDOC Workflow Service business service. If the workflow name is set here, all IDOCs received from SAP are sent to this workflow. The workflow name in the integration objects is ignored.

Standard integrations have been set up to use the first method. All workflow names are set in the Workflow User Property of the IDOC Integration Objects.

Bookshelf Home | Contents | Index | Search | PDF