Proxy and IDOC Serializing techniques in PI

When we have  requirement where the Integration Server had to process the IDoc XML messages created by the IDoc adapter in the same sequence that the Idocs were sent from the SAP R/3 system. In this case the Quality of Service is Exactly Once in Order (EOIO).

The steps involved in setting up the inbound qRFC queues which will be used for IDoc serialization using the IDoc adapter:

1.Logon to the ABAP stack of  XI instance, execute the transaction SE16 and enter the table name as “IDXQUEUE”

2.Click on the “Create Entries” button and supply the parameters: PORT, CLIENT, MESTYP and QUEUEID for each of the IDoc message type that we want to serialize using the IDoc adapter. Save each entry.

3. To display the entries created, click on the “Table Contents” button, supply “*” to the PORT and MESTYP fields to select all entries in the table and execute:

List of all entries in the table “IDXQUEUE” shown below:

4.Test with some of the IDoc Message types for which we have setup the inbound qRFC queues. To check which inbound queue is used, execute the transaction SMQ2 in your ABAP stack and the following screen appears:

5.Execute again to list the inbound queue names and their entries. You will find the queue name occurring as shown below for example:

II. Setting up inbound qRFC queues for  Proxy serializing

Generating dynamic queues in ABAP proxy program through which we can establish EOIO message processing.

*declare variable for queue id and set the queue id

Data: queueid type SXMSQIDAPP.

queueid = “queue_new”.

*get protocol & set the queue id

prxy_async_messaging ?= prxy->get_protocol(if_wsprotocol=>async_messaging ).

prxy_async_messaging->set_serialization_context(queueid ).

*………………

* do your processing

*………………..

* call the execute method

CALL METHOD prxy->execute_asynchronous

     EXPORTING

        output = it.

COMMIT WORK.