IDOC sender/receiver partner type LS?

Hi,
I am in need of advise if SAP 5.0 can be configured for ORDERS outbound (PO NEU) to pick up receiver (KU) partner type by standard config?
I understand that there's exit available but would like to utilise standard application config method.
Regards,
Viv
will definitely award points for the help!!

if i understood u right this might help you
1. /people/shabarish.vijayakumar/blog/2006/09/13/wanna-party
2. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

Similar Messages

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

Receiver partner type in control record is default"

Hi all,
I am Getting 56 Error"Receiver partner type in control record is default".
When I go to that perticular IDoc under control record under parter tab I am providing "PARTNER TYP" AND PORT.When I save these details th idoc is getting posted.
The port ifo is present in we21.I checked RFC Destination,It is fine.
Now where to give this information centrally since I have to manually enter this every time.
Thanks,
SrinivasaP

Hi,
If error is 56.
Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.
If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process
Please check receiver IDoc Adapter is configured with the said details are not.
And if possible map the values in EDI_DC40 control record.then you need not to give these details every time.
Regards
Chilla..

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

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

IDoc sending/receiving - XML v/s text IDocs

.NETters,
SAP .NET Connector supports sending and receiving IDocs.
1. For IDoc receiving, can we receive text IDocs as well as XML IDocs?
2. For IDoc sending, can we send text IDocs as well as XML IDocs?
Thank you in advance for enlightening me.
Pradeep

Hi Pradeep,
for NCo help on IDOCs, please read
http://help.sap.com/saphelp_nw2004s/helpdata/en/79/d0b51753406d4d86470debdf027c68/content.htm
SAPIDocReceiver
http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/8d23ec676fa74993d16c4a195c76a7/content.htm
IDoc Receiver
http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/0f499a4221604fb10200f24772c82a/content.htm
IDoc Submitter
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/fc646926adcd40bce23a981317374e/content.htm
the idoc's sent can be in text form as well as xml, that will depend on the charecteristics of the listener & the sender.
usually keeping them in xml should make parsing simpler for you.
with respect,
amit

56 error,EDI: Receiver partner type in control record is default

Hi all,
When I trying to post the IDOC the 56 error is shown.
I checked the partner profiles and found fine.Please clarify.
Thanks,
Srinivasa

Hi,
this means that your IDOC has some errors
you can see it by clicking on the status in We02
then you will know exactly where the error is located
in inbound processing you should see status 53 - successful
BTW
to check IDOC errros with XI:
/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi
Regards,
michal

Idoc segments and Partner types

Hi Experts,
Will we be able to find the partner details from the IDoc segments.
Thanks in Advance.
Regards,
Sridevi

Hi,
I want to get a list of partners to whom a particular IDoc segment is sent.
Thanks,
Sridevi

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

Inconsistent IDOC status some partner getting status 30 randomly ?

Hi,
I have developed customize IDOC and distribute to around 100+ receiver partner type KU. There is always idoc with status 30 in between randomly (not always the same KU).
I have implemented below code :
COMMIT WORK.
CALL FUNCTION 'DEQUEUE_ALL'.
Base on note Note 150202 - ALE: IDoc outbound - IDocs remain in status 30
One possible cause of this is a lock that is released too late:
First, you execute the COMMIT WORK and then a DEQUEUE ALL or EDI_DOCUMENT_DEQUEUE_LATER.
However, when you execute the COMMIT, the asynchronous processes are started that must first lock the IDoc again.
Some forum mention using code below:
IDoc status as 30
Used
CALL FUNCTION 'DB_COMMIT'.
CALL FUNCTION 'DEQUEUE_ALL'.
After FM 'MASTER_IDOC_DISTRIBUTE' and before COMMIT WORK.
Please advise ? is that the process is to fast ?
Thank you in advance
Fernand

Hi Vinay parakala
Schedule back ground job to program RSEOUT00 regularly to process the 30 status idoc....
Your program generates the idoc ... and RSEOUT00 will process you idocs which are in 30 status...
i hope above info helps you
Note: enter Message type BOMMAT in program RSEOUT00
Thanks
Ramesh

Idoc partner type LI to File Scenario.

Hello Experts .
I have the following scenario.
IDOC partner type LI to xml (file).
So we are not atlking about logical system here and we may have to use parties.
But I am not sure as to how to go about this approach.
For now we have Idoc coming into XI but failing after that .(Outbinding) error in reciver agreement (not to be confused with a cache issue .).
But I understand it is because of the parties not defined properly.
So I have defined a party and assigned my ECC system to the same.File was basically a service.Do I need to define another party for it or several other identifier
Tried to follow How Tou2026
Sample IDoc-XI
Scenarios document but it is to confusing.
Kindly help

Thanks for your reply.
Well I have already tried this approach.
That is
Created a party :Sender_party.
Identifiers :
<sapid><client> :*ALE#LI* :<venderno> actually ALE#LI #LF "otherwise I end up with party service not found.
Receiver determination:
sender party
<BS/service> i.e. <sapid><client> to mail_service (for testing to see if I recieve a payload)
<interface>
<urn>
Interafce determination
sender party
<BS/service> i.e. <sapid><client> amd <interface> interface mapping
<urn>
Reciever agreement.
mail_service : reciever mail adapter.
Error recieved.

- <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_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>-DMGCLNT400</SAP:P1>
<SAP:P2>Sender_Party-,urn:sap-com:document:sap:idoc:messages.Z_DELL_PO.ORDERS05.Z_DELL_POX</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver agreement found for sender -DMGCLNT400 to receiver Sender_Party-,urn:sap-com:document:sap:idoc:messages.Z_DELL_PO.ORDERS05.Z_DELL_POX</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Kindly note nothing is wrong with cache .
It is strange DMGCLNT400 is already assigned to the party . .

IDoc (Sender ) to File (Receiver): No receiver could be determined

Hi, Dear Friends,
Im implementing scenario Idoc-to-File by means XI.
I try to follow this scenario:
Satish Jaiswal. 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
But I have an error.
In sender system I send IDoc by transaction WE19. After that in transaction WE05 I see IDoc with status 03 (successful).
After that in XI system:
1) in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))
2) in transaction SXMB_MONI I see my message with error.
Status - System error.
In detail view at stage "Receiver Identification" in item "Error" I see: "No receiver could be determined"
Unfortunately I'm not expert in IDoc.
Can you recommend me what I need to verify?
Or advice me link on another full good example with IDoc.
What I need to read for quick start in IDoc understanding.
Thank you in advance.
Natalia Maslova.

Try these steps:
ALE Settings
SAP 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 (IDX1)
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 XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP 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 (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.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Message was edited by:
Raghavesh Reddy
null

Posting IDOCs with partner type SP ?

We have to post IDOCs to SAP where the partner type is SP . How do we configure XI to achieve this ?
We are disabling the control record and so not looking at the option of hardcoding the EDI_DC record.
I understand we need to specify Alternate identifiers in IDOC channel and also choose header mapping in receiver agreement, however am not very clear on the steps.
Can neone help me with the steps.
Thanks
Saravana

I need values something like below to be in the control record of the IDOC and could not find a way of doing it
<SNDPOR>PORT1</SNDPOR>
<SNDPRT>SP</SNDPRT>
<SNDPRN>ServiceProvider1</SNDPRN>
<RCVPOR>SAPS32</RCVPOR>
<RCVPRT>SP</RCVPRT>
<RCVPRN>ServiceProvider2</RCVPRN>
By default , the SNDPRT & RCVPRT carry the constant "LS"(i still do not get y this is enforced by the IDOC adapter). Our sender system is a FTP server & receiever is SAP system. We have the Business Systems defined as service without party.
I tried hardcoding the values in EDI_DC40 in message mapping, but the IDOC adapter removes(!!) it and creates its own header(inspite of the chk box being unchecked or checked!!?? in the communication channel configuration)
Christoph , i could not make out much out of the thread u ve pointed to.
Thanks
Saravana

Outbound INVOIC idoc to partner type LS

Hello,
We are trying to issue outbound invoices( Message type INVOIC / basic type INVOIC02) to a 3rd party who will be doing the billing on our behalf. We are trying to issue an ALE output type to a LS (logical system) partner type and we are receiving a message B1131, that says that partner type LS cannot be used here, only KU and LI partner types allowed.
We can create the idocs if we setup our partner as a KU customer. However, given that we are sending these to a 3rd party system, it seems that we should be using LS. Does anybody know if there is some configuration where we can choose to be able to send an idoc of message type INVOIC to a partner type LS - logical system?
Thanks in advance.
Mark Monroe

Hi Mark,
For your requirement you, create partner profile for LS with following steps :
Create New Partner profile and give your respective TY (User Type), Agent & Language and then follow maintain following parameters under Outbound Parameters :
Message Type : INVOIC
Under Outbound Option u2013 Tab
Receiver Port : <Mention your receiving port here, to create Receiver port you have to go to WE21 transaction>
Pack Size : 1
Transfer IDoc Immediately (Select)
Basic Type : INVOIC02
Cancel Processing After Syntax Error (Select)
Under Message Control - Tab
Application : V3
Message Type : RD00
Process Code : SD09
Hope, your problem will get resolve.
Regards..
Imran

IDoc Sender - XI - Proxy Receiver with EOIO?

Hi all,
1) I'm sending custom Message Type/IDoc to XI using function module MASTER_IDOC_DISTRIBUTE from 4.7 ERP/6.2 Basis system.
2) In XI's integration engine I will be mapping the IDoc record layout to my proxy record layout. XI is Netweaver 04/6.4 Basis
3) The last step is to use the Proxy adapter to send the data to my receiver which is a BW Netweaver 04S/7.0 Basis system.
I know how to guarantee EOIO during step 3 and within my receiving system. Can I guarantee steps (1) and (2) above use QoS EOIO? If so any thoughts/discussion on how to do that would be appreciated.
Thanks!

Hi Shaun,
unfortunately in this case there is no chance..
You could pack idocs and send them all togheter, this is a queue-like processing but is not a robust and stable approach.
All you can do is to enqueue starting from XI configuring the right entries in table IDXQUEUE.
Regards,
Sergio

IDOC sender/receiver partner type LS?

Similar Messages

Maybe you are looking for