IDOC-XI-Proxy(CRM) scenario

Hi Xi experts..
I am new in XI with ABAP background. I have give a project in XI to design and implement a scenaio. The scenarion is this one:
ECC5 to XI then XI to Proxy(CRM).
In functional specs of this following diagram is mention :
ECC5(ALE)-->IDOC( XI)--
> XI -
> Proxy(CRM).
(ORDERS.ORDERS05) (XI SOAP ORDERS)
Please help me out.
Points will be awarder sure.
regards
Santosh Khare

Hi Santosh,
Following are the Links:
https://www.sdn.sap.com/irj/sdn?blog=/pub/wlg/1819; [original link is broken] [original link is broken] [original link is broken]
Z Inbound Proxy Class
Please go through the 'HOW to guides' for IDOCs if you have service marketplace user ID:
Click on Exchange Infrastructure in the menu on left side
and select <i>How to sample Idocs within XI</i>.
https://websmp201.sap-ag.de/nw-howtoguides
I hope it helps,
Thanks,
Varun

Similar Messages

Why is a sender communication channel not required for IDOC and PROXY ?

Hello,
In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..) when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
Though this might be a regular question, I am not able to find a proper reason.
Please let me know the reason for the above request.
Thanks & Regards.

You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
Regards,
Raj

Idoc to Proxy Scenario

Hi,
I am working on a Idoc (ECC) to proxy (SRM) scenario , I am triggering the Idoc message from RWB, when I am trying so, message is getting pushed and it shows a success message in PI Moni. But it failes in the SRM system and the error message is as follows, Please provide me with some inputs. Also the Idoc message is not directly getting posted from ECC system.
Note: Logical system already exists in PI, ECC and also in SRM systems, Let me know should I check anything else.
Error Message:
==================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIProxy</SAP:Category><SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code><SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1><SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2><SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Error during proxy processing
An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause
Application Error
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
Trace message is:
============================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 782464</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="1" type="T">system-ID = SND</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2011-05-28T04:49:46Z CET </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">*                                                  * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = F506D1E488E811E0AF6B0000089A81FE</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="1" type="T">--start determination of sender interface action </Trace>
<Trace level="1" type="T">select interface </Trace>
<Trace level="1" type="T">select interface namespace </Trace>
<Trace level="1" type="T">--start determination of receiver interface action </Trace>
<Trace level="1" type="T">Loop 0000000001 </Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In </Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement </Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found </Trace>
<Trace level="1" type="T">Hence set action to DEL </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
</Trace>
<Trace level="1" type="T">Work Process ID: 786562</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SND</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PISUPER</Trace>
<Trace level="1" type="Timestamp">2011-05-28T04:55:09Z CET </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="Inbound Framework"></Trace>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0"><asx:values><CX_ERROR href="#o93"/></asx:values><asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary"><cls:CX_SY_NO_HANDLER id="o93"><CX_ROOT><TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID><PREVIOUS href="#o92"/><KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1580</CONTID></INTERNAL_SOURCE_POS></CX_ROOT><CX_NO_CHECK/><CX_SY_NO_HANDLER><CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME></CX_SY_NO_HANDLER></cls:CX_SY_NO_HANDLER><cls:CX_BBPX1_STD_MESSAGE_FAULT id="o92"><CX_ROOT><TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID><PREVIOUS/><KERNEL_ERRID/><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1754</CONTID></INTERNAL_SOURCE_POS></CX_ROOT><CX_DYNAMIC_CHECK/><CX_AI_APPLICATION_FAULT/><CX_BBPX1_STD_MESSAGE_FAULT><AUTOMATIC_RETRY/><CONTROLLER/><NO_RETRY/><STANDARD><CONTROLLER/><FAULT_TEXT>Error in an XI interface:
Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data
Program: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT><FAULT_URL/><FAULT_DETAIL/></STANDARD></CX_BBPX1_STD_MESSAGE_FAULT></cls:CX_BBPX1_STD_MESSAGE_FAULT></asx:heap></asx:abap></Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
</SAP:Trace>
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on May 28, 2011 8:08 AM

Hi,
      In service marketplace, try searching for notes related to SRM PI scenarios or the particular scenario you are imlementing. For exmaple, if you are implementing the scanerio for Invoice processing, try searching with this.
When we implemented the standard scenarios for SRM, found that they were quite a few notes for the individual scenarios that had to be implemented for the scenarios to run successfully. Most of these were on the ECC or SRM side.
Also, by the looks of your error message, seems the sender system (not PI) is not defined in SUS.
Might be that the logical system for ECC is not set up in SUS. Also check your SPRO settings in 'Define Backend Systems'.
Have a look at the following links which had a similar error :
Vendor replication from SRM 7.0 EBP to SUS via PI 7.0
Vendor Replication in SUS scenario
Regards

For R/3 to CRM Scenario ,creating ABAP Proxy for CRM which is in Target

In R/3 to CRM scenario it is ok creating ABAP Proxy for CRM which is Target system.if it is possible it is Client Proxy.it is correct or not

Hi,
Client Proxy. When you need to create Proxy for your Sender system then the proxy is generated on the client side and the Class created in Proxy generation is called in a report/FM etc.
Server proxy. The server proxy is created when you are sending the data from SAP XI to the receiving system.
The generation of proxy in both the cases happens on the sender or the receiver system.
Regards
Vijaya

Idoc to proxy scenario with an acknowledgment

Hi ;
I have to implement a IDoc to abapProxy scenario but an application acknowledgment must be return so IDOC status will be set.
How can i understand whether an application error exists while abapProxy is executing or not in status of IDOC?
Do I need to create and sent back new IDOC to the sender system in abapProxy code?
Thanks.

Hi,
See if you just want the ack for your IDOC coming from r/3 to XI, then you can use ALEAUD01 IDOC and you can configure it by running report IDX_NOALE in XI system..........
But if you want status change for appl error occuring in ABAP proxy system, then i think you will have to use a BPM for it.........you will have a recive step for getting your IDOC, then a transforamtion step for IDOC to proxy mapping, then a synch send step for sending proxy req and getting proxy response, then a transformaton step for mapping the proxy response to SYSTAT01 IDOC in r/3 for changing the IDOC status depending on success or error for your proxy response, then a send step to send this IDOC to r/3 system...............keep teh IDOC number in proxy req and proxy response so that you can use it in SYSTAT01 IDOC for sending it to r/3 and changing your IDOC status.
Regards,
Rajeev Gupta

How to do idoc to proxy scenario

Hi There,
As per requirement i am doing IDOC TO PROXY scenario. Can any one Pls help me how to do this configuration briefly.
with regards,
Naresh.K

Hi,
This is a Server Proxy Scenario.
To trigger the IDoc maintain necessary configuraions in R/3 and XI like.
1) RFC Destination (SM59) [XI & R/3]
2) Create Port (IDX1) [XI]
3) Load Meta Data for IDOC (IDX2) [XI]
3) Create Partner Profile (WE20) [R/3]
2) Create Port (We21) [R/3]
Also go thru this blog....<a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
There is no need to create sender IDoc communication channel and Sender Aggrement...
Go thru this blog for creating <a href="/people/siva.maranani/blog/2005/04/03/abap-server-proxies Server Proxies</a> by Siva Maranani
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

Idoc Vs Proxy

Hi Experts,
I have a scenario like i want to transfer the Idoc data from One sap system to another sap system through XI. So What is the best option to do this useing IDoc or Proxy?
Can you please breiefly explain me above Adavantage & Disadvanctage of these ways and Which one is best for me in this scenario.
Thanks in Advance,
Points rewared for each valuable answers.
Best Regards,
Vijay

Hi,
It all depends upon the business Scenerio..
Proxies can be used when data is huge and it is quite fast in action and you can trigger when ever you want...
Assume if the data has to be updated immediately to the receiver system in that case IDOC is fine...once the Idoc is created we can trigger it by settings or thru by back ground job and by Tcode we02 we can find the status of the IDOC
Regards
Agasthuri Doss

Help with Webservice to CRM scenario

Hey guys
i have a scenario in which users will buy some atricles through a website(shopping cart) and that info has to be posted to a CRM system.its an async scenario
do i need to know about BDOC's too or only knowledge of IDOC should be ok.
i m developing my interface as SOAP-XI-IDOC,is this right?
also which IDOC will be most suitable to implement this type of scenario
thanx
ahmad

Hi Ahmad,
<i>do i need to know about BDOC's too or only knowledge of IDOC should be ok.</i> - see this thing you will have to see that whether the data you want to post in CRM is having an IDOC or a BDOC for it.........XI doesn't deal with BDOC.....so if you have a BDOC for it in CRM, then in XI you will do SOAP-XI-IDOC scenario and in CRM you will map this IDOC to your CRM BDOC.
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

Regarding receiver determination problem in IDOC-XI-XML file scenario

Dear All ,
In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
Can anybody suggest what could be the reason behind this .
Thanks in Advance
Prabhat

Hi PRabhat,
In RCVR determination, you need to select the party & service (as appropriate) save the obeject
then refresh the configuration overview of recr det.
then you can see the partner/service
then you can open it & add the necessary objects.
Regards
Vishnu

Help needed in transferring IDoc from SAP CRM to XI

Hi All,
We are facing an issue in sending an IDoc from SAP CRM to XI system. The IDoc is triggered and the status is showing as 03 in SAP CRM system(WE05 is used) but it is not getting replicated in XI System. This is verified by logging into XI System and cross checked the records retrieved by executing the transaction IDX5. No entry is found for this IDoc.
In SM58 transaction, it is giving the status text as EDISDEF:Port SAPRIO segment defn E201CRMXIF_BILLI.
Any pointers on this issues will be very helpful. We are able to send information from XI to CRM.
The project is an upgrade one and the IDocs are developed earlier and were working fine one week back and no changes were made recently.
Thanks,
Udaya

Hi Kapil,
Thanks a lot for your help. We need to delete and recreate Metadata. This is a typical problem that is encountered during upgrade projects.
Thanks,
Udaya

IDOC import from CRM 7.0 to SAP PI 7.0 fails: unable to read segments

Hello,
We want to import an Idoc from a CRM 7.0 system to SAP PI 7.0.
The import fails with the message ""unable to read segments".
The issue is related to ALL Idocs, standard and customer defined.
The result of any import is that we can see the object in the import folder, but the structure is missing.
Importing any RFC from the same CRM system is no problem.
Any ideas?
Your help is appreciated.
Regards
Dirk

Hi Peter,
Thank you for your answer.
But we need to find out what the reason for this import error is.
Our customer will not be very pleased to see that all IDocs from CRM system cannot be found in the IDOC folder.
IDX2 import of metadata is no issue.
We were successful for standard and customer Idocs here.
Additional information:
We are already importing Idocs from a SAP ECC 6.0 system into PI in another SWCV
successfully. So this is a CRM system specific issue in our environment.
Regards
Dirk
Edited by: Meinhard Dirk on Aug 27, 2010 10:30 AM

R/3 46C(IDOC) -- XI -- Flat file scenario

Hi
Is there anyone who could give me information on a R/3 46C(IDOC) --> XI --> Flat file scenario?
Many thanks!
br
Göran

Hi Manish
We are using a standard IDOC called PROACT.PROACT01
(We are using transaction sa38(Report RSMIPROACT) in R/3 to send our IDOC.)
First we create the technical and business systems in SLD
Second we transfer these to the repository.(I think the only thing you need to do is to update the SLD cache to get them there - Design : Integration builder --> Environment --> clear SLD cache)
Then we just use the configuration wizard(Configuration : Integration builder --> Tools --> configuration wizard) to map everything together - defining sender and receiver etc(You get the configuration wizard tool by patching XI to patch level 4 or 5).
I assume that you have made all the configurations accordingly to the XI configuration guide which you can download from the service marketplace.
This is just a hint but maybe it can give you a start.
br
Göran

Error in IDOC(ALEAUD) to file Scenario

Hi ..
we have a client requirment were they want the ALEAUD acknowledgement in the form of file.
So we are creating a IDOC to file scenario, where IDOC is ALEAUD which is mapped to create a file in the traget system. but when we post the IDoc we get thwe following error.
*Note: have a small doubt. Can we use ALEAUD Idoc as a normal IDoc to File Scenario. because with the documents i understand that ALEAUD is a acknowledgment IDoc which is generated based on the request IDOC. but in our scenario we are manually using the structure of ALEAUD in the source system*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Kindly help me out .
Thanks in advance
Deepika

Hello,
If you need to send the ALEADUIT back to the SAP system if the file returns a successful ack, then you will need to have a BPM with a separate SEND step to send back the ALEAUDIT.
And check this ......
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
*******Reward points if found useful

IDOC to XML file scenario with party

Hi All,
I am developing a IDOC to XML file scenario with party in which I have extended the MATMAS idoc and configured the receiver FILE communication channel.
But its giving me the error *"No receiver could be determined"* with party. If I run the same scenario without the sender party its working fine.
And sender is my R/3 system under party P_Party and receiver is my third party system under P_Party.
Thanks in advance.
Gaurang

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

Acknowledgement for AsynThird-party-- SOAP-- PI-- ABAP proxy-- ECC scenario

Can someone please provide me a step-by-step for Third-party>SOAP>PI>ABAP proxy>ECC scenario.
Third-part system is sending an Asynchronous HTTPS message to PI which is then routed to the ECC system to do some processing. I have read many blong and all SAP Docu available on this subject, but i am still confused.
I understand that ABAP Proxies supports acknowledgement, but what needs to be done in the third-party system to be able to receive acknowledgements. Is there any special config. that needs to be done in Sender SOAP adapter?
What diff. needs to be done in ABAP proxy to be able to send acknowledgement messages, any config. in XI receiver adapter?
I will appreciate any guidance.
Thanks,
Saurabh

HI
Third party application need to have the synchronus communication enabled. If not then you need to get a wrapper develop for this kind of communication
For proxy development
Just go through these links:
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
ABAP Server Proxies (Inbound Proxy)
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
OutBound Proxy (Client Proxy)
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
Outbound Proxy (Client Proxy)
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
How to Activate Proxy.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
File to R/3 via ABAP Proxy with good example
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation

IDOC-XI-Proxy(CRM) scenario

Similar Messages

Maybe you are looking for