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

Similar Messages

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

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. <b>Note</b> 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 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

Converted PDF file to WORD but have characters in WORD not in original file---can't type in correct places in WORD--what to do?

HELPPPPPPPPPPPPPPPPPPPPPPPP!!!

In Ingknife29,
Are you able to select the text in Word if you triple-click it? If not, is it possible that the original PDF was created from a scanned document? If so, the text could be image text, rather than selectable/editable text. ExportPDF converts image text to selectable text by default, but that option can be disabled if you convert the file via Reader. So, I would make sure that you are allowing ExportPDF to perform OCR, and make sure the the correct language is selected for Text Recognition.
Please let us know if you need additional help.
Best,
Sara

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

Multiple IDOCS of same message type To Single File

Hi Sap All.
here i have got a tricky situation of sending Multiple IDOC's of same type to a Single File via PI.
the Integration architect has created an Integration Gudeline of how to do this.
from the SAP-ECC side the follwing below are the steps thatr he mentioned
To allow IDOCu2019s to be processed sequentially in a queue, the queue processing option on the partner profile must be selected. In addition the rule name which is used to create queue names must be specified.
NB On the partner profile (for the partner / message type) you must also set the output mode as collect IDOCu2019s (it cannot be set to transfer immediately) u2013 This means the IDOCu2019s are created but not sent to out (to SAP PI)
As standard there are two rule names delivered CONSTANT:EDIQUEUE and FIRST_16_OF_MESTYP. These rule names are linked to a SAP function module and therefore custom queue names can be build either as an u201Chardcodedu201D name or based on the data in the IDOC.
The program RSEOUT00 should be run to transfer the IDOCu2019s to PI. The IDOCu2019s will be placed in the SAP ERP qRFC (rather than the standard RFC)
My Questions :
1. how and where we can select the Queue Processing option on partner profile in SAP-ECC as mentioned above
2.how and where we can define the Rule name as mentioned above
3.how and where we can set the output mode as Collect IDOC's in SAP-ECC as mentioned above
4.what does the EDIQUEUE and FIRST_16_OF_MESTYP will do and how they linked to SAP Function modules
will be waiitng for a the best solutions.
Regards.
Varma

/people/michal.krawczyk2/blog/2009/05/21/xipi-collecting-idocs--possible-ways-with-pros-and-cons--5-ways - you will need to do a collect

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 Scenario Partner type not LS

Hi experts ,
we have gone through https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a&overridelayout=true for idoc scenario where idoc partner type is not a logical system .Now we are working on case2 scenario in above document.we have some confusion in the configurations at R/3 side.Can somebody explain the step by step configuration at R/3 side.
Thanks.

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

Can you plz tell m how to write Design Strategy in the scenario IDoc-- File

Hi,
can any body plz tell me how to write Design strategy, Preprocessing logic and post processing logic in the scenario IDoc-->File.
    My idoc is:
            Message Type: ZMMIPORDCHG
            Basic Type : ORDERS05.
lookup's are available.

Hi,
take a look at this document for an IDOC to IDOC Scenario,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Use it as a template to design one side of the Interface and also take a look at this blog,
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Bhavesh

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 question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

IDoc Acknowledgement - ALEAUDIT for partner type B

Hi,
I have a scenario where ALEAUD ack required for partner type B instead of LS.
What are the ways by which i can configure ALEAUD ack for partner type B?
Regards,
Anurag

Hi Anurag,
ALE AUDIT is the technique of using IDocs for communication.
ALE Audit it is used to check the cross-system IDoc flow and posting the data in the partner system.
please gone through this related blog blog , it may be helpful for you.
http://wiki.sdn.sap.com/wiki/display/Snippets/ALEAuditfor+DEBMAS
Regards,
Sudeepth

IDOC-File Can Partner Type be KU or LI ?

Similar Messages

Maybe you are looking for