Receiving IDOC error

Hello Experts,
         I had created Outbound IDOCs from sending server and it created with successfully status i.e. with 03 status. But at the receiver server that IDOCs are not received.
       Now, I am not able to find out which could be the reason for this.
      Receiver server is the non-sap server. Can any one give me the proper reason..??
     Any transaction codes are there to find out reason at sender side.
Thanks in advance....!!
Regards,
Poonam.

There might be lot of reson,
1. Check with your middleware team whethere they are able to connect SAP.
2.Check whether the Idoc is there is queue via transaction SMQ1.
I would suggest work with your middleware team to resolve the issue..

Similar Messages

Receiver IDOC error - using TCP/IP

Hi All,
I have a scnario where I am sending an IDOC to BCOMM ERP system via IDOC adapter from SAP PI using TCP/IP RFC program but while sending it is giving me an error in SM58 as IDocException occurred and there isn't much info in SM21 or ST22 or any other transaction.
Error log in SM21 says
Name of the partner program where an error has occurred. Check the
preceding system log entries.
Use the gateway monitor (transaction SMGW) to monitor the functions
of the gateway.
If someone has ever worked on such a scneario please let me knw and any pointers would be great.
Cheers
Abhi

Hi Michael,
I know that this is not the conventional way but we cannot use RFC of type 3 as it is not a ECC system , it can handle IDOC communication via Idoc adapter through a SAP connector at there end which can be handled only via TCP/IP.
I am able to do it for another system with similar scenario but Not able to do for this particular system.
Can you tell me about your scenario and how you did it?
Thanks for your reply.
Cheers
Abhi

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <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">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

IDoc receiver AEE: Error "Configuration for Sender/Receiver Partner Number/Port is incorrect"

Hi all,
We are on PI 7.4 AEX SP 7. We are trying to get the following scenario working: Inhouse warehouse management system (JMS) --> PI --> ECC (IDoc)
Sender is configured as 3rd party technical system system with business system maintained in SLD
business system has logical system assigned in SLD
adapter specific identifiers show logical system in ID / NWDS
logical system is defined in receiver (ECC system)
partner profile is created in ecc for this very logical system (inbound parameters)
No mapping of EDI_DC40 node in ESB (complete node disabled)
no header mapping in ID / NWDS
receiver IDoc AEE adapter is configured to not enforce control record (Control Record in IDoc XML = Not Mandatory)
no Identifiers specified in receiver IDoc AEE adapter
My guts feeling is that this should work, however, it doesnt't. Failing with "The Configuration for Sender/Receiver Partner Number/Port is incorrect. Enter proper values in Sender/Receiver Component"
Any thoughts are highly welcome.
Cheers
Jens

Hi,
The error mentioned by you is not related to the port..but its related to the Application ...
IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
Check with the functional consultant for the error you have received..
HTH
Rajesh

IDOC error while receiving

Hi Friends,
In my scenario, I have to receive P.O. message from partner in to my R/3 system.
I am using PI 7.1
When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI
I tried to find solution on sdn, and I got 2 related foroum,
Idoc Error
Re: No receiver could be determined. (File to Idoc)
But from this also I am not sure hw can i solve this error.
Please Suggest.
Thanks & Regards,
Brijesh Soni

Hi
For Error Only asynchronous processing supported for IDoc adapter outbound
IDOC adapter support asynchronous only,
Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.
This thread had same problem and resolved :
Re: No receiver could be determined. (File to Idoc)
In Your case QOS is BE. Plz check in your CC if and BE is by default..
If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

File to IDoc scenario - IDoc received with Errors

Hi,
I tried to send send IDoc from a file to SAP R\3. The communication channels are working fine, and I get the IDocs in R\3 but with status 56. When I examine the received IDoc structure in transaction "WE19", I see that the receiver port(SAP + SID of sap server) is blank with no values. I tested the IDoc adding the receiver port, and the IDoc got successfully posted...
I wonder why the receiver port that I specified in payload file content, does not reflect during runtime. I'm using the downloaded MATMAS IDoc structure with sender and receiver details as the input from file....
Please help me out!
Thanks!!
-Ajitha

Rodrigo/Sarvesh/Ravi/Haseeb,
Thanks for the inputs!! I have checked in IDX1 and the port name is the same. Also "Apply control records values from payload" checkbox is selected. I guess there was some problem with cache. It started working fine, when I started a new session
Thanks for your time and inputs!!!

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
SLD
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen

Receiver IDOC adapter - RFC_NO_Authority

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
Went thru receiver determination, Interface determination, message split, request message mapping, Technical routing and then got stuck at call Adapter stage. Below is the error:
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Runtime error RFC_NO_AUTHORITY has occurred</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Runtime error RFC_NO_AUTHORITY has occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Is there any step that I may have missed after I created the receiver IDOC Channel?
Could you please shed some light here?

Please, search SDN before posting....
check these link: Runtime error RFC_NO_AUTHORITY has occurred in SM58
What its error?

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Receiver Idoc adapter - issue

Hi,
I need to send an IDoc (CRMXIF_ORDER_SAVE_M01) to SAP CRM. The trouble occur when having/wanting to use/send only the segments that apply to release 620.
In order to do that I have in my receiver IDoc adapter specified the value '620' in the Segment Version part.
As soon as having done this my IDocs fail in the adapter giving me the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The segment specified in the above corresponds to the very fist sub-segment to the main segment (BUSTRANS). So if removing that segment the error jumps to the next segment (which would then be the first sub-segment).
Should be noted that I have no trouble sending IDocs if I've either not specified a Segment version (meaning latest version is automatically used) or if I explicitly request the latest by entering the latest segment release (700 in my case).
<Trace level="1" type="T">Convert one IDoc</Trace>
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_BUSTRANS</Trace>
<Trace level="2" type="T">Ignore unknown Segment E101CRMXIF_BUSTRANS</Trace>
<Trace level="2" type="T">Ignore segment field: APPL_SNAME</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_TASK</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_GUID</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_ID</Trace>
<Trace level="2" type="T">Ignore segment field: PROCESS_TYPE</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_TYPE</Trace>
<Trace level="2" type="T">Ignore segment field: POSTING_DATE</Trace>
<Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE</Trace>
<Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE_ISO</Trace>
<Trace level="2" type="T">Ignore segment field: LOGICAL_SYSTEM</Trace>
<Trace level="2" type="T">Ignore segment field: CRM_RELEASE</Trace>
<Trace level="2" type="T">Ignore segment field: CLIENT</Trace>
<Trace level="2" type="T">Ignore segment field: CREATED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CREATED_BY</Trace>
<Trace level="2" type="T">Ignore segment field: CHANGED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CHANGED_BY</Trace>
<Trace level="2" type="T">Ignore segment field: LOCAL_TIMEZONE</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_ID_OK</Trace>
<Trace level="2" type="T">Ignore segment field: HIGHEST_ITEM_NO</Trace>
<Trace level="2" type="T">Ignore segment field: CRM_CHANGED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CALC_SCHEMA</Trace>
<Trace level="2" type="T">Ignore segment field: SCENARIO</Trace>
<Trace level="2" type="T">Ignore segment field: VALID_FROM_EXT</Trace>
<Trace level="2" type="T">Ignore segment field: VERIFY_DATE</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY_X</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E103CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E107CRMXIF_ADDRESS</Trace>
<Trace level="2" type="T">Ignore unknown Segment E107CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS_F</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON_F</Trace>
Hope someone can help me so that I can succesfully limit the segment version used when sending Idocs.
Best regards,
Daniel

Hi,
Thanks for your quick reply.
The funny thing is that even if a try to post the exact same idoc (except for the EDI part) that I have received from CRM it still fails in XI with the before mentioned error.
But to answer your questions:
1. I'm not using java mapping but traditional message mapping (meta-data are up-to-date and structure is newly loaded).
2. No blank segments are being created
3. All segments have value 1 or blank (using blank works fine for me, that is when not trying to limit Segment version. But using 1 makes no difference)
Best Regards,
Daniel

Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
I'm getting an error (below) at the Call Adapter stage:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
I::000
and thus the IDOC can't get recreated.
Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
Can someone please shed some light?

Hi,
Addition to the above
Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
it should be only SAPSID..(SID is your system name..)
HTH
Rajesh

Monitoring receiver idoc communication channel

Hi All
I have an idoc to idoc scenario.
I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
How can i monitor receiver idoc communication channel?
How can i ensure that the idoc is delivered to the receiving system?
In sxmb_moni, status is checkered flag.
Many Thanks
Chandra Sekhar

Hi,
IDOC is on ABAP stack hence u can not monitor IDOC.
For testing purpose
1) GO to SXMB_MONI check the status of message.
2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
chirag

IDOC Error - Copy Sender from Payload: Sender Is Missing in Payload

Hi,
I have following scenario.
SOAP adapter ---> PI -
> IDOC Receiver -
> ECC
THe IDOC has a required node that is disabled and IDOC revicer communication channel has checkd following options.
Apply control record value from pay load
Take Sender from Payload
The soap message is mapped to IDOC structure. While testing I received following error.
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy Sender from Payload: Sender Is Missing in Payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Copy Sender from Payload: Sender Is Missing in Payload</SAP:Stack>
If you have seen similar error and please let me know how to trobleshoot. I appreciate your help.
Thank you,
Balaji

Thank you for the response. I can enable EDI_DC40 segment and map required following values.
· SNDPRN
· SNDPRT
· SNDPFC
· RCVPRN
· RCVPRT
However as we move transports to different environemnts the above values changes and I can't hard code in the mapping.
My questions is how can I map these values such that when transport moves across different environemtns the mapping valaues are still good. Please let me know.
Dont enable EDI_DC40 and dont select take sender ,receiver from pay load option,apply control record values from pay load.
this case IDoc adapter reads values from configuration time andno problem after trasporting to quality or prod.
Regards,
Raj

Receiving IDOC error

Similar Messages

Maybe you are looking for