Outbound interface using ABAP Proxy

Question

Hi Guys,
I am trying to create an interface between a Z table and XI using ABAP Proxy. I suggested file based interface, but client is insisting using ABAP proxy. Z table is in IS-Retail side.
I will appreciate is somebody can share a program to do this.
Any advise/guidance is appreciated.
Thanks,

Answer 1

Hi There
From your  subject line i can see that you want to develop an outbound proxy which means you want to send data to XI from your SAP custom table. That means you need to extract all the information from your Z-table and send it to XI via  proxy.
If my understanding is correct then what you need to do is :
1.Ask your XI team team to generate a message interface for you of type 'outbound' and include the structure in the way they want you to send data to them. 
2.Once the message interface is created by them , you can generate the same in transaction SPROXY .  Search for your interface namespace and then right click
on it and say 'CREATE' . Give the appropriate package and prefix to it.Generate the proxy, save and activate
3. Now you can create a report and then according to the structure generated by XI , you can popluate your internal table to be passed back.
4. Call the method of the proxy in your report and send the data to XI.
I can give you an example of how to do this:
suppose you have built up an internal table by extracting data from your Z-table .Lets say it is tbl_output.
In your report you need to trigger the proxy method as follows:
Note: i am assuming i am triggering an asynchronous proxy method from my report:
DATA:lo_senddata  TYPE REF TO CL_DATA_OUT,
                  lo_system_fault TYPE REF TO cx_ai_system_fault,
                  lo_root         TYPE REF TO cx_root.
ls_output-output_file-data[] = tbl_data[].
CREATE OBJECT lo_senddata
TRY.
* call the asynchronous method of the proxy and send the data
          CALL METHOD lo_senddata->execute_asynchronous
            EXPORTING
              output = ls_output.
* get the system exceptions and display the error text
        CATCH cx_ai_system_fault INTO lo_system_fault.
          WRITE:/ 'System Error:'(E01),
                  lo_system_fault->errortext.
          RETURN.
* get the root exception and display the textid value
        CATCH cx_root INTO lo_root.
          WRITE:/ 'System Error:'(E01),
                  lo_root->textid.
          RETURN.
      ENDTRY.
COMMIT WORK.
<b>Note:</b> 1. CL_DATA_OUT is the message interface class.
                  2. ls_output is the output structure to be sent back to XI and data 
                     is an internal table with the same structure as tbl_data.
                  3. It is very imp to catch exceptions as i have shown u above.
Please let me know if you are a little clear or you need some more clarifications on this.
cheers
shivika