IDOC - Proxy Scenario.

Hi..
I am doing MM-SUS Interface. i am thinking the Adapters are IDOC-->Proxy, If my understanding is wrong, pls correct me. Today at 9 am i am sending the PO Request from ECC -XI-SUS , i am getting the PO Confirmation from SUS-XI-ECC after 2 days. this scenario it will come to Synchronous Scenario (OR) Asynchronous Scenario. Pls suggest me
Regards,
Pasi.

Pasi ,
Help further extended...please check :
Re: MM-XI-SUS Integration
MM System - XI - SUS
MM-SUS XI configuration
MM-SUS cenario
Re: MM-SUS vendor replication error
R/3(MM) -XI- SUS Scenario Error
Hope it helps !!
Regards,

Similar Messages

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 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 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

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

Replacing IDoc - IDoc with IDoc - Proxy

Hi every one,
I have an IDoc - IDoc integration scenario between 4.5B and ECC 6.0 systems. The Idoc in the receiver system is not directly posted but an User - Exit is called and every thing is working fine.
I thought of experimenting replacing the scenario with Idoc - Proxy, and the source being 4.5B and target ECC. The User-Exit stuff as told above will taken care while implementing proxy.
Approach:
I create an inbound interface object in IR and use the Idoc as the message type and generate a server proxy using SPROXY in the ABAP stack of XI.
Please correct me. Also notify me if there are any potentials problems.
Regards,
-Naveen.

Hi,
SPROXY on the ECC system should be used to generate the ABAP proxy, not the XI system. Therefore, configurations will be required on the ECC system to point to the XI system in order to retrieve the interfaces to generate the ABAP proxy.
Also, it might be easier to create a simpler message type to use in the interface. IDOC has a quite complex structure and probably contains a lot of elements which will not be used by your proxy. The proxy interface should be as simple as possible to simplify your program development.
Regards,
Bill

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

Issue in IDOC-File Scenario

Hallo Everybody,
In one of the requirements,for the interface design which involves IDOC-FILE scenario we have a req as:-
Multiple IDOCs would be sent from SAP R/3 to SAP XI. Each IDOC can have 0-4 segments and for each segment a file needs to created.
The files needs to be FTPed to a location, only if all the IDOCs have been processed successfully.
Requirement:
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
2) We need to send a notification from XI, in case any IDOC processing fails.
3) How do we check in XI, if all the IDOCs have been processed successfully.
Please suggest me with some good stategies to resolve this issue.
Appreciations and Rewards in line.
Regards,
Younus

Hi
Are you planning to use BPM as it suits your requirement.
To collect the idocs in small bunches refer
Collecting IDocs without using BPM
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
BPM will allow you to wait for the time all IDOC are processed
2) We need to send a notification from XI, in case any IDOC processing fails.
BPM exception handling will allow this functionality even to the exact field you want to send notification
3) How do we check in XI, if all the IDOCs have been processed successfully.
Set Acknowledgment for IDOC's
refer
Posting multiple IDocs with Acknowledgement
Thanks
Gaurav

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
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
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

FTP to ABAP Proxy Scenario - getting error CO_TXT_CHANNEL_PASSWORD_ERROR

We have transported PI and EP data from development server to respective production, every thing is running fine except the abap proxy scenarios i.e. PI reads file from ftp location and calls the abap proxy but we are getting following errors:
<?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="OUTBINDING">CO_TXT_CHANNEL_PASSWORD_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = FD768D4A8772DB50E1000000AC10041E) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any solution?
Please note that I have searched and applied solutions given on SDN forums but didn't get any success. So I am looking for new suggestions.
Regards,
Jawed Ali

Jawed ,
Please test the HTTP destination of your receiver comm channel.
Which is the RFC connection to your R3 system.
Transaction SM59 and check the logon parameter for the connection you are using.
Regards,

EOIO is not working for file- BPM- Proxy scenario.

Hi All,
I have one File to BPM (Merge pattern ) to Proxy scenario.
I have two file communication channel at the sender side and defined QOS as EOIO for both. In SXMB_MONI it assings same queue for all messages.
BPM is merging that messages. However during that it assings different queue for merged messages.
When it comes to proxy , again different queues are assingned to the messages.
Is there any way I can define QOS in BPM or at the proxy side ( I know it should be at the sender side only , but it's not working..)
Thanks & Regards,
Dijesh Tanna.

HI,
Within the current release the BPM will always only use EO (SAP Note 833740).
May be the SAP note 905049 will help you on this ...
Thanks
Swarup

Error in FILE 2 Proxy Scenario

Hi All,
I am doing File to Proxy Scenario i am getting following error
Could any one provide the solution for this.
*<?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">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>MI_Emp_Sender</SAP:P2>
<SAP:P3>Namespace</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_Emp_Sender, request message, namespace )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Thanks in Advance
Mahesh
</SAP:Error>
Edited by: Mahesh Reddy on Jul 10, 2008 12:47 PM

Hi Mahesh,
1) Use SPROXY transaction.
Menu-> Proxy -> Activate All.
2) check in the interface determination if u are using correct
inbound interface.
3) If this if fine....try deleting all proxy objects of the interface
and create new.
Regards,
Praveen K

Soap -- XI -- IDOC/RFC scenario

Hello,
I have a jsp page that working in tomcat server.
I want to send values from jsp page to xi to r/3. I think it will have
soap-- xi -- IDOC/RFC scenario
Pls send me pdf /doc to implemet it
Regards

Hi,
Please Refer the Following Links
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Regards
Khanna

IDoc- File scenario: can you explain thses acknowledgments?

Hi,
I have an idoc->file scenario. in sxmb_moni I can see a green "OK" mark for my message in acknowldgment status column. when I dblclick the message, I can see my original message and 2 acknowldgment messages under this one in the top left.
1 acknowledgement is the OK one, the 2nd one is of type AckNotSupported.
When I dlbclick the OK one ack and click the idocoutbound, I can see:
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>450</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000257842</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
and when I dblclick the 2nd ack and IdocOutbound, I see:
<SAP:MANDT>450</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000257862</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD />
450 is the client of my IE, not the sender SAP system.
What should all this mean? What does each ack mean and why do I get 2 of them?
When I check the Idoc no. in XI, there is no such IDoc. Where are these Idocs sent from?
POINTS WILL BE ASSIGN FOR SURE FOR CORRECT ANSWER.
Thanks, Olian

green:
hoplist
<?xml version="1.0" encoding="UTF-8"?>

<SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
 <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
 <SAP:Engine type="IS"/>
 <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>
 <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
 <SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>
 </SAP:Hop>
 <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
 <SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>
 <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
 <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
 <SAP:Info>3.0</SAP:Info>
 </SAP:Hop>
 <SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">
 <SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>
 <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
 <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
 <SAP:Info/>
 </SAP:Hop>
</SAP:HopList>
content
<?xml version="1.0" encoding="UTF-8"?>

<SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
 <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
 <SAP:MANDT>350</SAP:MANDT>
 <SAP:DOCREL>700</SAP:DOCREL>
 <SAP:DOCNUM>0000000000258080</SAP:DOCNUM>
 <SAP:DIRECT>2</SAP:DIRECT>
 <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
 <SAP:CIMTYP/>
 <SAP:MESTYP>ALEAUD</SAP:MESTYP>
 <SAP:MESCOD/>
 <SAP:MESFCT/>
 <SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>
 <SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>
 <SAP:SNDPRT>LS</SAP:SNDPRT>
 <SAP:SNDPFC/>
 <SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>
 <SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>
 <SAP:RCVPRT>LS</SAP:RCVPRT>
 <SAP:RCVPFC/>
 <SAP:TEST/>
 <SAP:SERIAL/>
 <SAP:EXPRSS/>
 <SAP:STD/>
 <SAP:STDVRS/>
 <SAP:STATUS>03</SAP:STATUS>
 <SAP:OUTMOD/>
 <SAP:SNDSAD/>
 <SAP:SNDLAD/>
 <SAP:RCVSAD/>
 <SAP:RCVLAD/>
 <SAP:STDMES/>
 <SAP:REFINT/>
 <SAP:REFGRP/>
 <SAP:REFMES/>
 <SAP:CREDAT>0000-00-00</SAP:CREDAT>
 <SAP:CRETIM>00:00:00</SAP:CRETIM>
 <SAP:ARCKEY/>
</SAP:IDocOutbound>
Red one:
<?xml version="1.0" encoding="UTF-8"?>

<SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
 <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
 <SAP:Engine type="IS"/>
 <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>
 <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
 <SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>
 </SAP:Hop>
 <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
 <SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>
 <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
 <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
 <SAP:Info>3.0</SAP:Info>
 </SAP:Hop>
 <SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">
 <SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>
 <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
 <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
 <SAP:Info/>
 </SAP:Hop>
</SAP:HopList>
content
<?xml version="1.0" encoding="UTF-8"?>

<SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
 <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
 <SAP:MANDT>350</SAP:MANDT>
 <SAP:DOCREL>700</SAP:DOCREL>
 <SAP:DOCNUM>0000000000258083</SAP:DOCNUM>
 <SAP:DIRECT>2</SAP:DIRECT>
 <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
 <SAP:CIMTYP/>
 <SAP:MESTYP>ALEAUD</SAP:MESTYP>
 <SAP:MESCOD/>
 <SAP:MESFCT/>
 <SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>
 <SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>
 <SAP:SNDPRT>LS</SAP:SNDPRT>
 <SAP:SNDPFC/>
 <SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>
 <SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>
 <SAP:RCVPRT>LS</SAP:RCVPRT>
 <SAP:RCVPFC/>
 <SAP:TEST/>
 <SAP:SERIAL/>
 <SAP:EXPRSS/>
 <SAP:STD/>
 <SAP:STDVRS/>
 <SAP:STATUS>03</SAP:STATUS>
 <SAP:OUTMOD/>
 <SAP:SNDSAD/>
 <SAP:SNDLAD/>
 <SAP:RCVSAD/>
 <SAP:RCVLAD/>
 <SAP:STDMES/>
 <SAP:REFINT/>
 <SAP:REFGRP/>
 <SAP:REFMES/>
 <SAP:CREDAT>0000-00-00</SAP:CREDAT>
 <SAP:CRETIM>00:00:00</SAP:CRETIM>
 <SAP:ARCKEY/>
</SAP:IDocOutbound>

IDOC - Proxy Scenario.

Similar Messages

Maybe you are looking for