ATTRIBUTE_INV_SND_PARTY

Hi,
I am setting up a new party in seeburger via EDI.
The EDI message went through successfully, but while getting into IDOC, it says the following error.
Unable to convert sender XI party ABC / ALE#KU#AG / to an IDoc partner.
I have checked the configurations and all seems to be correct.
Pleae let me know the issue

Hi,
Did you set the part identifiers at party level in the Intergration directory that corresponds to the seeburger id created/mentioned..
if not check the same at party context screen
HTH
Rajesh

Similar Messages

Error:IDOC_ADAPTER" ATTRIBUTE_INV_SND_PARTY : File to IDOC scenario .

Dear XI experts ,
Issue : Error to a new implementated SAP ERP SYSTEM . File to IDOC Scenario
Business Scenario : Exchange Rates from Thomas REuters (XML) - > XI-> SAP 1 , SAP 2 ERP Systems ( 2 diff SAP ERP systems)
SAP 2 is a new system set up for a new plant of our Organization.
The Excahnge rate is gettiong updated by IDOC: EXCHANGERATE.EXCHANGE_RATE01 in two SAP Systems
Each one is configured with diffrent IDOC receiver .
The Error is : for the SAP 2 system . The MEssage gets branched and one message is successfully sent to SAP1 , and turns an error : in SXMB_MONI for SAP2 system
I had been thropugh few blogs have performed the below steps:
-IDOC metadata : IDX2 have configured in XI
-checked the port of EGP , Partner Profile in SAP 2 ERP system
-Checked IDX1 , IDX2 of SAPEGP in XI .
-Refreshed business system .
-Tried to send the xml data from the start point through File Zilla(FTP)
Could somehow help as this is Production issue ans this is affecting the business.
Error from SXMB_MONI:
<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_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Reuters</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Reuters to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Reuters : is the Sender Party of Exchange Rates. I have seen in blogs to craete agency / schema , but since thsi scenario is 2 seperate SAP ERP systems , my question is do i need to create agency , schema for sender party .
Appreciate your Input
Thank you,
Vara
Edited by: Varalakshmi SB on Oct 26, 2011 12:14 PM
Edited by: Varalakshmi SB on Oct 26, 2011 12:16 PM

agency and scheme are used when your doing B2B scenarios.

File to convert to IDOC from bus.service failes with ALE#LI

Hello,
we habe implemented a scenario:
Non SAP system sends a structure to be uploaded to an R/3 system as IDOC.
All config looks fine.
We followed this description:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
So system is identified in adapter specific data as log.sys. LS test1 .
But we have this error:
Unable to convert partner abc / ALE#LI into an IDOC partner (message in german, only translated)!
Does anybody has an idea what is wrong?
Is it necessary to have the log.sys name in the message e.g. in SNDPRN?
Here we have after mapping:
<SNDPOR>testABC</SNDPOR>
<SNDPRT>LI</SNDPRT>
Best regards
Dirk
Message was edited by: Dirk Meinhard
Message was edited by: Dirk Meinhard

Hi Nimrod,
looks like I am not totally wrong here, but working together with externals who provide the outbound side is not really easy for testing.
Here is the EDI_DC-40 segment AFTER the Mapping, so the XML for the inbound IDOC:
- <PORDCR05>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>010</MANDT>
<DIRECT>1</DIRECT>
<IDOCTYP>PORDCR05</IDOCTYP>
<MESTYP>PORDCR</MESTYP>
<SNDPOR>A000000039</SNDPOR>
<SNDPRT>LI</SNDPRT>
<SNDPRN>0005354880</SNDPRN>
<RCVPOR>SAPK10</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>LOG10</RCVPRN>
</EDI_DC40>
Here is the 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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>Partner_ABC</SAP:P1>
<SAP:P2>ALE#LI</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Sender XI Party Partner_ABC / ALE#LI / could not be converted to IDoc Partner </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In my opinion we have to implement in WE20 of receiver R/3 system a partner LI with this number A000000039 from the EDI DC 40 segment? And we need to add it as identifier LOGICAL with ALE#LI and this number A000000039.
R/3 consultant says he cannot do this in the receiver R/3 system because the sender is no supplier in his system!
regards
Dirk

XI3.0 IDOC control record - SNDPRN and SNDPRT setting from payload

Hi,
I have a source XML from which I wish to create IDOC-XML and forward to the IDOC adapter to post to an R/3 system. I wish to create IDOCS with a sender partner type of 'KU' and a sender partner number which I wish to copy from the source XML document. I have read the How to sample IDOC-XI scenarios but I still cannot get this to work. Whenever the IDOC is created in the R/3 system is still has a sender partner type of 'LS' and a partner number taken from the sender business system.
To summarise - how do I map the customer number from the source XML-payload and use this to set the sender partner number and type for use by the IDOC adapter.
Many thanks
Ian

Sravya,
Thanks for your blog & reply:
I have changed my receiver agreement to map the sender party to /ORDERS05/IDOC/EDI_DC40/SNDPRN and set the schema to ALE#KU
& for Receiver party to /ORDERS05/IDOC/EDI_DC40/RCVPRN.
I'm receiving the following error message , can you please look into it :
<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>ALE#KU</SAP:P2>
<SAP:P3>5229</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI/ALE#KU/5229 to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Unable to convert sender party to IDoc partner

Hi guys!
I have read a lot of threads to this topic, however, I can't make my scenario working...
I use Party as sender of document and need to send it to target (our) R/3.
I have set up:
Sender party: Cocoon, Sender Business SERVICE: IslandSys
To target IDoc XML I map:
SNDPRT - KU
SNDPRN - D600
SNDPOR - IslandLS
In Party Identifiers:
Agency: IslandSys
Scheme: ALE#KU
Name: D600
Pertner profile - WE20 (target R/3)
type: KU, No. D600
In Business Service's Adapter Specific Identifiers: Logical System: IslandLS
But the scenario doesn't work..
What's wrong with the config?
Thanx a lot for help!
Olain

<?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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Cocoon</SAP:P3>
<SAP:P4/><SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Cocoon to an IDoc partner
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>

Multiple System identifiers for one EDI Party

Hi,
I'm getting a problem when trying to send an IDoc to another R/3 system. I did the first tests with our SandBox and everything was working perfectly. Now, I'm trying to do the same tests against our QAT server.
So first, I have created all the new entries under the party identifiers. Then, new Business Service, receiver determination ... and finally the sender agreement.
So, now the file is getting picked up but I get this error:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Tech_Data</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI/XIParty/Tech_Data to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Seems the new identifiers for QAT is not piked up?!? Do I need to do something else if I have multiple identifiers?
Rgds,
Yves

Hi Yves,
In the "Indentifier" section of your party definition for the EDI Party
Change the following:
AGENCY = Change the Business System from SBX to QAT
Scheme = Remains the same
Name   = Change the SBX Partner Number to QAT
         Partner Number(same as QAT Partner Number
         in R/3 Partner Profile)
Idoc Receiver CC for QAT
1) In the "parameters" tab, check the option "Apply Control Record Values from Payload"
2) In the "Identifiers" tab,
   Enter the BS for QAT in "Sender Agency"
   Enter the Scheme for QAT "ALE#<partner role>#<partner function>"(same as in
   the identifiers tab of the EDI party definition)
   Enter the BS for QAT in "Receiver Agency"
   Enter the Schem for QAt as "ALE#LS"
It should work with these changes.
Rgds,
Sam Raju

Acknowledgement errors in PI - JMS scenario

Hello,
We have a scenario R3 Idoc -> PI7.0 -> JMS. After the Idoc message is sent to PI, In the sxi_monitor, in acknowledgement status column, I normally see a red icon which says ack not possible. But for few JMS interfaces, I observe there is a green icon which says waiting for acknowledgement.
In the smq2 monitoring, I see queues for this acknowledgment message into error with IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY.
Did someone face a similar scenario. Even though the messages reach the third party via JMS queue, these messages are collected in queue with sysfail error. Please help how to get rid of this.
Regards,
Swapna

If you do not want to have acknoledgement, in your sender system, run ABAP program "IDX_NOALE"
In "Maintain Partner System Acknowledgment" screen, specify your Sender Port and client
Then you can turn off following acknowledgements:
System OK
System Error
Application OK
Application Error
Regards
Liang

ATTRIBUTE_INV_SND_PARTY

Similar Messages

Maybe you are looking for