IDOC-XI-EDI : Sender Party in IDOC with LS Partner Type

Hi
Does anyone know of a way to have IDOCs sent from SAP to XI to arrive with a sender party. Note The Partner Type of the original IDOC is LS. [I know how to do this with e.g. KU Partner Type.]
Thx, Duncan

Duncan,
Normally when the partner type is LS there is no need for a Party?
Can you let us know why you want to configure a party when the Sender Partner type is LS?
Meanwhile, thought I have never given this a shot, in the party why dont you try adding the agency , scheme and identifier with the corresponding scheme as ALE#LS . If it works well then the target is achieved but if it does not , then I dont think for LS this is possible.
Regards
Bhavesh

Similar Messages

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 customers in Sender Party for IDOC type KU

Hi All,
My scenario is IDOC to HTTP with sender IDOC Type KU.
We are using PO 7.4 and IDOC_AAE.
I have done the following settings.
Created a Sender Party and assigned a customer under party identifiers. (Also I can't add multiple values with same Agency and scheme it throws eror in PI)
For a single customer the end to end scenario is working fine.
But if I try to send the IDOC with other customer Number it fails as the entry is not maintained for that customer in Sender Party identifiers.
Also I can't afford to create a different party for each customer as there are hundreds of customers in the ECC Application system.
I also tried with value mapping but it won't worked.
Please suggest on this.
Regards,
Nitin...

Dear Nitin,
did you solve this problem? A am faced to it right now... ...
Regards,
Markus

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

Idoc to File. Partner type as 'KU' and 'LI'.. Acheivable w/o using Party's?

Hi all,
Idoc to File scenario.
I have the receiver partner type as 'KU' and sender partner type as 'LI'.
I want to create the scenario without using party for these partner Types.
Is it possible for me to create the B2B scenario without using party's?
Is it mandatory that we need to use partys and Identifiers for these kind of scenarios?
Kindly let me know if anyone has idea on this.
Thanks
-Seema

Hi Seema,
I appreciate that you chose to go with the parties
That should be called a good design decision.......
Now answering your query regarding the party identifiers
Idoc to File :
<SNDPOR>SAPDL1</SNDPOR>
<SNDPRT>LI</SNDPRT>
<SNDPRN>90000</SNDPRN>
<RCVPOR>SAPXI</RCVPOR>
<RCVPRT>KU</RCVPRT>
<RCVPFC>SP</RCVPFC>
<RCVPRN>36</RCVPRN>
For Sender Party (say party INTERNAL)
Agency : LD1_001
Scheme: ALE#LI
Name: 90000 (vendor number set in WE20 in the R/3)
For Receiver Party (say party EXTERNAL)
Agency: LDI_001 (SID_<client> BS as defined in SLD)
Scheme: ALE#KU#AG (AG for partner function SP)
Name: 36 (customer number set in WE20 in the R/3
This will resolve the IDoc header data into the following XI SOAP header information:
Sender Party - INTERNAL
Sender Service - LD1_001 (say this is the business system defined for logical system SAPLD1
Receiver Party - EXTERNAL.
Though, you can determine the receiver party alongwith the Receiver Service later at RCV DETERMINATION step, as I have said earlier.
Yes, for outbound you have to maintain the identifiers for Sender Party type LI, but you can still skip the Receiver KU type and update the SOAP header at RCV DET step.
File to Idoc:
<SNDPOR>SAPXI</SNDPOR>
<SNDPRT>KU</SNDPRT>
<SNDPRN>36</SNDPRN>
<SNDPFC>SP</SNDPFC>
<RCVPOR>SAPDL1</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>MAINSAP</RCVPRN>
For Sender Party (say party INTERNAL)
Agency: LD1_001 (SID_<client>)
Scheme: ALE#KU#AG
Name: 36
For Receiver Party (say party EXTERNAL)
Because the RCVPRT value is LS , no need to set the Receiver Party for that.
But if you want to have some Receiver Party value for the same you can use Header Mapping in receiver agreement.
Mandatory Setup in Receiver IDoc Adapter:
Set the indicator - Apply Control Record Values from Payload
Remember to set the Identifiers in the Identifiers Tab in Idoc channel.
Sender:
Agency : LD1_001 Scehma : ALE#KU#AG
Receiver:
Agency: LD1_001 Schema : ALE#LS
I am not sure why this ALE#LS entry is required, but according to my experience if we don't have that entry, the Idoc Adapter throws error while converting the Receiver Party (considering you use party in the ID configuration for both Sender and Receiver).
Yes you are right, you can hard code the SNDPRN, RCVPRN values in the mapping and can take the values from payload...........for that set the following Indicators in Idoc channel:
Take Sender from Payload
Take Receiver from Payload
Let me know if you have any concerns or any additional observation you make while configuring the scenarios. Thanks.
Regards,
Suddha

Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

Hi All,
We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

Hi,
Both the sender and receiver IDoc transmission is done by the RFC communication channel.
In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
Hope this helps...!!!!
~SaNv...

Sender Party Alternative Identifier Problem.

HI All,
I have a B2B scenario in which I have configured following things in Integration Directory
1.Sender party as PartyA
Business System-->ABC_001 with logical system as ABC_001.
2. Receiver party as PartyB.
Business Service--->InvoiveManagement.
Also there are other A2A scenario in which ABC_001 is under service without party.
Now when I send an Idoc from ABC_001 to XI, then by default SNDPRT is "LS" in Idoc control record. it would have been fine if i would have used Business system ABC_001 as service without party.
But here we want to use Sender system ABC_001 inside sender partyA for our B2B scenario.
I think we need to change some settings in sender R3. Is this possible?

Hi,
I am not too much into abap, and so am a little ignorant with the program RSNASTED you mentioned above.
One more thing, if you refer to the PDF , which Sravya pointed out in this thread, there in page number 17 there is a screenshot where SNDPRT is US. That screen shot is of we05 where you can view idocs.Can you please tell me how do we acheive that. Whenever I trigger an Idoc from my R3 system to any partner I want SNDPRT to be US, by default.
You can trigger idocs using transaction we19. Here, you can change the edidc values as required, and trigger the idoc. This however wouldn't work if the partner profile has not been configured properly.
This transcation is only used to test idocs. Check if the right receiver determination gets called, when the idocs are triggered from here, with different partner types.
If yes, then, it would confirm that the approach is right; and you could then find a way to call idoc with a right partner type using a transaction/program.
Regards,
Smitha.

IDOC-File Can Partner Type be KU or LI ?

Hi All
I am sending IDOC from R/3 system to XI.
Can partner type for XI be LI or KU?
What my assumption is, whenever R/3 sends IDOC to XI, it treats XI as LS always. So partner profile configured for XI will be under partner type LS
Please correct me if I have any misconcept.
Thanks in Advance.
Mugdha Kulkarni

You are correct.
Mudit

Sender party of reciever determination is getting used in IDOC receiver

Hi All,
i am having a very strange problem in my XI scenarios.
i have 2 scenarios: S1 and S2.....S1 scenario is running on production.......S2 scenario is on development....both S1 and S2 are similar in the sense, they are sending IDOC to SAP R/3.......
s1 scenario is having in recever determination :
sender party A
sender service A1
receiver service R/3 by IDOC adapter - in this apply control rec values from payload is checked.......This S1 scenario is running fine on production.....
s2 scenario is having in recever determination :
sender party B
sender service B1
receiver R/3 bY IDOC adapter - in this when i check apply control rec values from payload, then in SXMB_MONI i get error :Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner....So you see the sender party B is getting used in the IDOC comm channel......But when i uncheck control rec values from payload, then my msg is successfully processed in SXMB_MONI...
Now my question is : why S1 is runnig fine and S2 is not running fine on check apply control rec values from payload option......both are having party and service in sender.........So has it to do something with the definition of party......
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

Hi Bhavesh,
my scenario is file - idoc........basically it is XI msg->IDOC scenario....the source xi msg i am getting from another XI system.....but on dev, i cannot connect to that external XI system, so on dev i am having file sender adapter to send the source file to be mapped to IDOC and then to be send to R/3 dev..........
i saw the control rec values of both S1 of prd and S2 of dev........
S1 scenario is similar to S2 in the sense it also has XI msg from that external system.....but since prd is connected to that external XI system, so we have created a party and a business service in it.......it has in IDOC adpatere the option of appy control rec checked........
i saw that the control rec of both S1 and S2 msgs were similar......moreover the control rec values of S2 msg with and without the option of appy control rec checked were similar.........the only issue is when the apply control rec option is checked, then it gives error that "Unable to convert sender XI party http://sap.com/xi/XI/XIParty/B to an IDoc partner"......
But in S1 prd scenario, it is not giving this error on checking the option of appy control rec.......
Can you suggest why this is happening - why party B of S2 is considered differently from party A of S1......moreover these parties are simple parties created in ID.........
Thanks,
Rajeev Gupta

Configuring scenario to add Sender Party to a message from an IDoc

I want to make sure that when an IDoc is received in the XI system, the message Sender Party is populated. Currently I am trying to do this by associating the IDoc communication channel with a Business Service with a party. I was expecting that this would then force the message to adapt that party as the sender party, but this does not seem to be working.
In the header of the xml message I get this:
<SAP:Sender>
<SAP:Service>EQ1CLNT210</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ZINVOIC_CU.INVOIC02</SAP:Interface>
</SAP:Sender>
EQ1CLNT210 is the system that the IDoc is sent from, but the Service with Party that I am using has no <Party> subelement in the <Sender> element.
Am I doing this correct, or am I missing a step?
BR,
Tony.

Please cross check your steps with the list below,
if the problem persists, check the metadata
For File to IDOC,
in R/3
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using we21
4.create partner profile using we20
in xi
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using IDX!
for IDOC to FIle
R/3 side
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using we21
4.create partner profile using we20
5.distribute busynessmodel using bd64
for xi side
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using IDX!
4.create partner profile using we20
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
SAP R/3
R/3 to XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.

Party-based IDOC from external SAP sender

Hello experts.
I have PI 7.0
I have a scenario where I receive an IDOC from an external SAP system - that has SID=PRD and client=400
I also have an SAP system in my landscape with SID=PRD and client=400.
when I tried to define a service and edit it's adapter specific identifiers - i received the following error:
Check Result for Object EXT_SRV
SAP system ID PRD and client 400 already exist in service | PRD400
I understood that the PI will not be able to identify the sender if an it will receive an IDOC with SNDPRN=PRD400
When trying to figure out a way to overcome this and be able to receive the IDOC I came across the term:
party-based communication. I understood that I should define a party an in it a service for the external SAP system.
can some one please show me a detailed step by step example of such scenario?
All I found was this: [Java IDoc Adapter Partner Conversion |http://help.sap.com/saphelp_nw73/helpdata/en/7b/ebc8b9e34b434d9f3e80ef6776d77a/content.htm] and it is only valid for PI 7.3
Thank you very much.

Hi ,
In idoc communication few fields play a vital role SNDPRN,SNDPRT,RCVPRN,RCVPRT,SNDPOR and RCVPOR in EDI_DC40 segment. These fields actually identify the sender and receiver systems and ports.
Now in your case as I understood that a new sender SAP system is sending the same idoc to PI server along with an existing one. In this case you need to alter SNDPRN value to a new value, when you are sending the idoc. All other values will retain same values for same idoc (basic type and message type). In ID add a new party in object list with the new SNDPRN value.
In the ID scenario create a copy of each entry in interface determination,receiver determination,sender agreement and receiver agreement. In each of the copy add the new sender/receiver party information SNDPRN value.
This should take care of your problem. No need to do any changes in IR as IR will be common for both the senders, what differs will be the ID. PI server will run different instances of the scenario for different SNDPRN value.
Finally one small request, please kindly if possible close down your threads, in case you got proper and correct solutions to your questions. I noted you closed only one of last five threads you have opened. If you close threads after a solution has worked, then forum users become sure that the solution has worked for your case and therefore is correct.
Regards
Anupam

ALE Error while sending PO IDOC through EDI

Hi Experts,
                  I am sending one PO IDOC through EDI but I am getting the following error:-
                  Message no. B1130.
                  "Too many recipients found for message type ORDERS in the ALE model"
                  How can I solve this error ? Please guide me in this regards as this is an
                  important issue with urgency.
Thanks & Regards
Jitendra Gujarathi

Please check this discussion thread
Re: Too many recipients found for message type in the ALE model

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

IDOC send step not running with exception in BPM?

Hello,
hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
Situation:
We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
Any idea why the exception branch is not called?
Best regards
Dirk

Hello again,
we are one step further now.
We did the same with an RFC instead of the IDOC send step.
Same result:
The service is not reachable. So the step results in an system error.
But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
So it looks like connection problems do not trigger an exception?
Any help is welcome!
Best regards
Dirk

Urgent: IDOC to EDI with SAP Conversion Agent

Hi,
I have a requiremetn like IDOC to EDI ( Gentran ) scenario.
We have decided to use SAP Conversion Agent to deal the same.
Can anybody share their experiences on this kind of scenario.
Needed step by step information to complete would be appreciated with the full of points.
Cheers.,
E

check with tis may helpful for you
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
Regds
Abhishek

IDOC-XI-EDI : Sender Party in IDOC with LS Partner Type

Similar Messages

Maybe you are looking for