Siebel Connector for SAP R/3 > EAI Queue > EAI Queue Usage with SAP R/3 tRFC >

Outbound from the Siebel Application


Figure 26 shows the current implementation of the EAI Queue when making tRFC calls from the Siebel application to SAP R/3.

Figure 26. Outbound from the Siebel Application Using tRFC

Figure 26 shows the flow of a business object from the Siebel database to the SAP database. From an EAI workflow, the EAI Siebel Adapter is invoked to extract data from the Siebel database corresponding to a Siebel business object definition. This data is used by the Siebel Adapter to create a Siebel integration object instance. This is passed through a transformation map service to create a BAPI input integration object instance. The BAPI input integration definition contains the structure of the data object to be passed to SAP in the tRFC call.

When the tRFC BAPI Adapter receives the integration object instance, it behaves depending upon the setting of the SAPWriteXML component parameter, as reflected in Table 35.

Table 35. Possible Status Values for EAI Queue Entries (Siebel to SAP)
SAPWriteXML Value
No SAP Connection Available
SAPCodepage Is Set
No SAP Connection Available
SAPCodepage Is Not Set
SAP Connection Available

WriteOnly

Entry made in EAI Queue with Status=Initial and ReferenceID=NULL.

Connection error occurs and no entry is created in the EAI Queue.

The entry in the EAI Queue is Status=Initial, and the ReferenceID is set with the Transaction ID from SAP.

Start a Send Transaction Process to send data from the queue to SAP.

WriteOnErr

Entry made in the EAI Queue with Status=Initial and ReferenceID=NULL.

Connection error occurs and no entry is created in the EAI Queue.

The first attempt tries to send data to SAP.

If the send to SAP fails, the entry in the EAI Queue is Status=Initial or Sent, and the ReferenceID is set with the Transaction ID from SAP.

The send to SAP fails only if the SAP connection fails during the send, or if system level information (such as IDOC/Logical system configuration) is incorrect.

If the send to SAP succeeds, no entry is made in the EAI Queue.

You can resend the entries in the queue that have the status of either Initial or Sent, by starting a Send Transaction Process, provided that any system-level configuration issues are resolved.

WriteBeforeErr

Entry made in the EAI Queue with Status=Initial and ReferenceID=NULL.

Connection error occurs and no entry is created in the EAI Queue.

An entry is created in the EAI Queue, followed by an attempt to send data to SAP.

If the send to SAP fails, the entry in the EAI Queue is Status=Initial or Sent, and the ReferenceID is set with a value from SAP.

The send to SAP fails only if the SAP connection fails during the send, or if system-level information (such as IDOC/Logical system configuration) is incorrect.

If the send to SAP succeeds, the entry in the EAI Queue is Status=Confirmed, and the ReferenceID is set with a value from SAP.

You can resend entries in the queue that have either the status of Initial or Sent, by starting a Send Transaction Process, provided that any system-level configuration issues are resolved.

WriteNone

Connection error occurs, and no entry is created in the EAI Queue.

Connection error occurs, and no entry is created in the EAI Queue.

Data will be sent directly to SAP.

If the send of data fails, an error is returned to the caller.

Siebel Connector for SAP R/3