Bookshelf Home | Contents | Index | PDF     

Siebel Connector for SAP R/3 > EAI Queue >

EAI Queue Usage

The use of the EAI Queue is enabled through changes to the SAPWriteXML component parameter on the BAPIRcvr and BusIntMgr components. The default value for this component parameter is "WriteOnErr".

To enable the Siebel Application to SAP interfaces

  1. Set the SAPWriteXML component parameter on the BusIntMgr component to one of the following choices:
    • WriteBeforeErr
    • WriteOnly
    • WriteOnErr
    • WriteNone
  2. Restart the Siebel server.
  3. Start a Send Transaction Service background task to pick up erred transactions from the queue and resend them to SAP.

    For more information, read The Send Transaction Service.

  4. Test the queue by executing the Account to Customer Standard Integration.

    The data flow that sends an IDOC to SAP to create sales area information for the customer creates an entry in the queue, depending upon the mode.

  5. Choose Integration Administration EAI Queue from the Siebel application.
  6. Select the "tRFC Outbound to SAP" queue from the EAI Queue applet.

    Entries in the queue appear in the EAI Queue Items applet. Each entry contains:

    1. The Transaction ID used to identify the transaction to SAP in the Reference ID field.
    2. The data in transit as an XML file attachment.
    3. The Status field indicating the current status.

      Status values for Siebel application to SAP Send Transaction are Initial, Sent, or Confirmed. If the process errors, status remains in one of these three states until a Send Transaction Process executes. If the Send Transaction Process errs, the status appears as "Error in Sending." At this point, manual intervention is needed to determine the cause of the error.

  7. If a transaction has the status "Error in Sending" in the EAI Queue, make a note of the Transaction ID in the Reference ID field.

    This value uniquely identifies the transaction in the Siebel log file. Using this ID, you can find error information in the log file to help you determine the cause of the problem. When you determine the cause you may do the following:

    1. Edit the XML data held in the EAI queue for that transaction to correct the information and change the status from "Error in Sending" to "Initial". A Send Transaction service picks up the data and resends it to SAP.
    2. Delete the entry in the EAI Queue for that transaction and recreate it from the Siebel application using whatever correction may have been made.

To enable the SAP to Siebel interfaces

  1. Set the component parameter SAPWriteXML on the component BAPIRcvr so that it contains:
    • WriteBeforeErr
    • WriteOnly
    • WriteNone
    • WriteOnErr
  2. Start a BAPIRcvr component.

    For more information, read Starting the tRFC BAPI Receiver.

  3. Start a Process Transaction Service background task to pick up erred transactions from the queue and reprocess them into the Siebel application.

    For more information, read The Process Transaction Service.

  4. Execute the Customer to Account standard integration to test the queue.

    The data flow that sends an IDOC to the Siebel application to create an account creates an entry in the queue, depending upon the mode chosen.

  5. Choose Integration Administration EAI Queue to display the queue.
  6. Select the "tRFC Inbound from SAP" queue from the EAI Queue form.

    Entries in the queue appear in the EAI Queue Items list. Each entry contains:

    1. The Transaction ID used to identify the transaction to SAP in the Reference ID field.
    2. The data in transit as an XML file attachment.
    3. Status field indicating the current status.

      Status values for SAP to Siebel applications Send Transaction are Initial, Processed and Confirmed. If the process errors, status remains in one of these three states until a Process Transaction Service executes. If the Process Transaction Service errors, status appears as "Error in Processing". At this point, manual intervention is needed to determine the cause of the error.

  7. If a transaction has the status "Error in Processing" in the EAI Queue make a note of the Transaction ID in the Reference ID field.

    This value uniquely identifies the transaction in the Siebel log file and also in the SAP tRFC layer. Using this ID you can find error information in the log file to help you determine the cause of the problem. You can also retrieve information from SAP by SAP transaction SM58. When you determine the cause you may do the following:

    1. Edit the XML data held in the EAI queue for that transaction to correct the information and change the status from "Error in Processing" to "Initial." A Process Transaction Service picks up the data and reprocesses it into the Siebel application.

      NOTE:  You should not modify queue entries with the status Initial, Send, or Processed while the server is running. These entries may be in use by the background processes in the server. You may edit entries with Error in Processing or Error in Sending status values while the server is running.

    2. Delete the entry in the EAI Queue for that transaction and recreate it from SAP using whatever correction may have been made.

NOTE:  All components which may have services accessing the queue must execute on the same server machine. These components use a locking mechanism around the EAI Queue that operates correctly only when all processes execute on the same machine. These components are: BusIntMgr, SAPSendTrans, BAPIRcvr, and SAPProcessTrans.

    
Siebel Connector for SAP R/3