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]

Similar Messages

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 Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error: 403 Forbidden
 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
Sender
Service : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
Receiver:
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

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

Explain about Idoc to soap scenario

Hi All,
I am beginner to sap pi can anybody help me out, How to perform Idoc to soap scenario...

Dear Gaffar,
Please use the search functionality to learn.
Redirecting...
http://www.google.com/cse?cx=013447253335410278659%3Ak8ob9ipscwg&ie=UTF-8&q=idoc+to+soap+scenario&siteurl=www.google.com…
try out the scenario,create the thread if you face any issues.

How to trigger Idoc?

Hi,
I did all design and configuration steps and ALE configuration steps for Idoc to file scenario. Can any one tell me how to put idoc that this scenario should work??

Hi Pavani,
WE19 -> u can enter either basic type or message type.
click on create
go to menu object->edit control record
there give the receiver system paramters and source system parameters
after that double click on idoc segments, window opens with all the fields, give data and click on Test Idoc outbound processing.
check the status in we02.
Regards,
Ravi.

Idoc to http scenario

Anyone know how to do idoc to http scenario step by step?
Especially receiver http adapter configuration. Using a test tool for Http client, how can we get the parameters for it in adapter configuration?

>>Anyone know how to do idoc to http scenario step by step?
There is no guide on SDN which tells u step by step for IDOC to HTTP.You need to read for sender IDOC configuration and receiver HTTP configurations on SDN.
>>Using a test tool for Http client,
HTTP client tool is used only in case of sender HTTP not for receiver HTTP.
>>how can we get the parameters for it in adapter configuration?
The help.sap documentation on SDN has given all the parameters for all the adapters.
Thanx
Aamir

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

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 How to sample Idocs within XI.
https://websmp201.sap-ag.de/nw-howtoguides
I hope it helps,
Thanks,
Varun

How to get Idoc acknowledgment in File to Idoc scenario

Hi All,
Please give suggestions about the below mentioned scenario:
Scenario: FileXI- ECC - Data from File is converted to various IDocs and posted in SAP. (No BPM used)
Problem: Exception Handling > > We want a message back from SAP system telling us that out of 100 IDocs that were sent, n were posted successfully and rest failed along with the error description. How can this be achieved?
Regards,
XIer

Pls go thruough these links also
Please see the below links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
unable to import from SLD
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
IDOC Acknowledgements
R/3 IDOC ->XI-> ORACLE Error Handling
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
Regards
Abhishek Agrahari

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

IDOC and RFC/PROXY Scenarios

Is there a way to practice IDOC or RFC Scenarios if you only have access to the XI System? So you have XI abap and Java but no R/3 System...
Can someone tell me how I can practice IDOC and RFC scenarios please

It is possible to practive IDOC & RFC scenarios with XI's abap stack as sender & receiver of IDOCs and RFCs with the "XI" in the middle....
However, the problem might be the IDocs & RFCs might have to be created from scratch to test these out....
If you have some IDOcs that you can use in XI abap stack, have the program that generates this IDOc and when(if) XI abap stack receives this, the processing module to process this IDoc...
Similarly, the RFC FM has to be available on XI ABAP so that it can bhe invoked from the RFC interface..
Thanks.
Message was edited by:
Renjith Andrews

How to move Idoc scenario's

Hi,
My client is moving from IBM server to HP's SUPERDOM.
Now I have to run certain Idoc- XI- File and File-XI- Idoc scenario's to the new server.
I would like toi know what all configurations have to be done....

Hi Snehal,
You could find all the needed config in the below links!!
Check this blog on IDOC to File.
Introduction to IDoc-XI-File scenario and complete walk through for starters.
A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
How Tou2026 Convert an IDoc-XML structure to a flat file and vice versa in XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
For troubleshooting
Troubleshooting File-to-IDOC Scenario in XI.
Thanks,
Sathish Raj..

How to do idoc to proxy scenario

Similar Messages

Maybe you are looking for