IDOC (LI) To IDOC (KU)

Hi Experts,
                   I am configuring a IDOC to IDOC interface as sender partner type is LI and receiver partner type is KU(customer).
what are the necessaryu configuarations need to be done for party KU .i did all normal things an didoc is reaching but it is recahing at partner type LS.
Regards
Rao

Hi,
The Partner profile (for sender partner) created at the receiver R3 system should be of type LI.....
Rec partner type wont be of much importance......
also in the rec idoc adapter check the take payload from sender field....
and in mapping map the partner type field for sender in the target idoc..by constant LI
Regards,
Sushil.

Similar Messages

  • Doubt while importing idoc (file 2 idoc scenario)

    hi,
    In IR, Imported objects..>Idocs
    while importing idoc there are two options to import
    according to software componet version,
    Overwrite sever info temporarily
    which one i have to use ? what circumstances i have to each option?

    Praba,
    Also please check this SAP help for the difference between these two:
    http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
    Regards,
    ---Satish

  • IDoc included in IDoc packet containing an error: transfer it separately

    Hi Gurus,
    I'm having this problem in our ECC side. I already did what Michal said in his blog:
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    I have bundled the multiple IDOCs into 1 MATMAS.
    But I'm still having the error IDoc included in IDoc packet containing an error: transfer it separately.
    I've searched in the forums and none of them worked for me.
    Thanks in advance!

    Disable packaging or change the Partner Profile on WE02 transaction to "process immediately" the IDOCS.
    When you process the IDOCS in background mode, it will create packages (it is enabled by default), and in case any of them fail you won't be able to see the root cause, but will have to go to BD97 transaction to process them again. Therefore, please use the "process immediately" or disable packaging and then you will be able to either see the error or process it because it won't fail because of another IDOC.

  • IDoc Packaging in IDoc 2 IDoc Scenario

    Hi every one,
    Can anyone please throw some light on the following:
    Use of Idoc packaging in an Idoc2Idoc scenario. I dont have any clue about this.
    Reg,

    This should be rather straight forward, if you are using XI to pass IDocs from system to system then you actually don't really have to do any mapping.  There are some other good discussions on this topic:
    idoc to idoc
    IDOC packaging
    Re: IDOC to IDOC Scenario
    This is a good document on the topic:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    You can import the IDoc data types and go about creating the rest of your scenario, usnig the IDoc adapters and ALE
    I would definitely also check out this document on configuring the IDoc adapter:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

  • IDoc Collection Scenario (IDoc to Mail Interface)

    Hi,
    I am configuring IDoc to Mail Scenario using BPM.
    I gone through following link for develop the scenario. I am still unable to complete the scenario.
    Collect Idoc
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    I have done following steps in my configuration. Please correct my steps if i am wrong.
    Source is Outbound Invoice IDoc (SAP System).
    Target is Inbound EDI 810 format send as a email(Mail System).
    1. Create an Abstract Interface for Invoice IDoc(MI_IDoc_ABS)
    2. Create a Message Interface for EDI 810 for Inbound(MI_EDI810_IN)
    3. Create an Abstract Interface for EDI 810(MI_EDI810_ABS)
    4. Message Mapping between Outbound IDoc and Abstract Invoice IDoc.  I did this as per one of the above link. but did not understand the importance of this. On Message tab of Message Mapping, it shows the occurance as 1 for both source and target. I did not see the mention of this mapping in the BPM. Not sure if this was required?(MM_IDoc_ABS)
    5. Message mapping between Abstract Invoice IDoc to Abstract EDI 810. On the message tab of message mapping, occurance of Source message is changed to 0-unbounded and occurance of target is kept as 1.(MM_EDI810_ABS)
    6. Define Interface Mapping for above mappings
    a) IM_IDoc_ABS - Outbound Invoice IDoc + MI_IDoc_ABS
                                  MM_IDoc_ABS
    b) IM_EDI810_ABS - MI_IDoc_ABS + MI_EDI810_ABS
                                 MM_EDI810_ABS
    7. Create a BPM in Integration process. Define 3 Containers namely
    a) collectIDoc - Abstract Interface - MI_IDoc_ABS
    b) collectIDocList - Abstract Interface - MI_IDoc_ABS(Multiline)
    c) targetFile - Abstract Interface - MI_EDI810_ABS
    8. Create a Block and define a infinite while loop with Block. Condition to be defined as (1=1)
    9. Define a deadline block withing Block with duration = 5minutes
    10. Define a Correlation in Correlation editor as SNDPOR as a ID.
    11. Define a recieve step inside infinite while loop with following properties
    Message = collectIDoc
    Start Process = Checked
    Use Correlation = Correlation
    Activate Correlation = Correlation
    Correlation
    SNDPOR = collectIDoc./INVOIC02/IDOC/EDI_DC40/SNDPOR
    12. Define Container operation next to recieve step. properties are
    Target = collectIDocList
    Operation = Append
    expression = collectIDoc
    13. Outside the block, there is Transformation Step with following properties
    Interface Mapping = IM_EDI810_ABS
    Source message = collectIDocList
    Target message = targetFile
    Acknowledgement = None
    Reciever From = Send Context
    Now the next step is to define Communication Channel and Receiver determination, Interface determination in the Integration Directory.
    I don't know, how to go further on these steps.
    In addition, could you please validate my above steps.
    I appreciate your help.
    Thanks,
    Gowri

    Hi Bhavesh,
    Thanks for the directions and help. I appreciate your help. I understand the steps but i am unable to implement it.
    I have few more questions on above answer.
    a) Do i have to create Sender Agreement?
    b) Do i have to import bmp process in Integration Process in Integration Directory?
    The steps that i carried out in Integration Directory.
    1. Create a Scenario EDI810_Scenario
    2. Create a party called EDI810_Party and EDI810_Service.
    3. In EDI810_Service, Receiver tab has interfaces defined. MI_EDI_IN and MI_IDoc_ABS. In sender tab, it is INVOIC.INVOICE02 (IDoc) and MI_EDI810_ABS.
    4. Define a receiver communication channel CC_EDI810_Receiver(RFC).
    5. Business System for SAP is defined in Service without Party.
    6. Defined Sender communication channel CC_IDoc_Sender(IDoc)
    7. Create Interface Determination (First)
    Properties are
    Sender Service : SAP Business System
    Sender Interface : INVOIC.INVOICE02 (IDoc)
    Sender Namespace : IDoc namespace
    Receiver Party : EDI810_Party
    Receiver Service : EDI810_Service
    Configured Inbound Interface is
    MI_IDoc_ABS and IM_IDoc_ABS
    8. Create Interface Determination Determination (Second)
    Properties are
    Sender Service : BPM_IP (Bpm process is imported in Integratio directory)
    Sender Interface : MI_EDI810_ABS
    Receiver Party : EDI810_Party
    Receiver Service : EDI810_Service
    Configured Inbound Interface is
    MI_EDI_IN. I do not see IM_EDI_ABS in the list. How do i get that.
    What step did i miss?
    Thanks,
    Gowri

  • Automate flat IDOC to XML IDOC using one interface

    Hello all,
    We are currently going through a migration process where XI will be replacing a legacy system.  As part of our testing procedure, we are using historical data pairings from the legacy system and using an automated tool to compare if the interfaces we develop in XI match.  The catch is we need the data that we are comparing in XML format for the automated tool to be able to do the comparison, and unfortunately the legacy data is a flat format.  So now I would like to automate a way to convert this data to XML format.
    Specifically for IDOCs, I would like to have an interface which picks up the flat files, transforms them to XML, and then drops them back into another file directory in the XML format.  It would need to be able to pick up any kind of IDOC (given that XI has the metadata already imported), recognize what message type it is, then do the conversion.
    I have been reading on SDN and found that there is a standard tool to do the conversion, but it appears it can only handle one kind of IDOC at a time, and it appears it only picks up one specifically named file at a time.
    Has anybody tried to implement a scenario like this?  Any help is appreciated (A walkthrough would be the best!).
    Thanks in advance,
    Mike

    Mike,
    What version of PI will you be using? PI 7.11 can now auto-convert Flat File IDocs to XML IDoc and vice versa.
    Here is the documentation:
    http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm (flat to XML)
    http://help.sap.com/saphelp_nwpi711/helpdata/en/74/a45bc07e2043fb9b63295229178903/frameset.htm (XML to flat)
    I have not tried this personally, but seems like you might be able to use a "File to File" scenario with no mapping, and use the "IDOCFlatToXmlConvertor" Module in your File Adapter Comms Channel and it may just work, giving you files that are the IDoc XML version of the flat file it is reading. It looks like it does an RFC call to the back-end SAP system where the IDocs are originally from (or could be any system as long as you know the IDocs in there are identical), and reads the IDoc metadata (which has always included flat file field offsets for each IDoc Segment Field), and applies that either to convert from flat file IDoc to XML IDoc, or XML IDoc to flat file IDoc.
    It does mention that there is a limitation that there can only be one IDoc in the source flat file - could be a problem if you have many in one file, which is pretty typical.
    Regards,
    Brendan

  • SM58 - IDoc adapter inbound: IDoc data record table contains no entries

    Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
    Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
    IDoc adapter inbound: IDoc data record table contains no entries
    I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
    Please point me in the right direction.

    hi,
    i think in sm 58 u can find entries only when there is some failure in login credential .
    if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
    please check the logical system name pointing to the your requird target system....
    please also verify thet your port should not be blocked.
    pls find the link it may help
    Monitoring the IDOC Adapter in XI/PI using IDX5
    regards,
    navneet

  • File to Idoc Scenario and Idoc to File Scenario's

    Hi Friends ,
    This is Shalini Shah,
    Please give me the details of how many busines sytems required in File to Idoc Scenario and Idoc to File sceanrio's.
    In business system , what is the name of Integration server(this name is related to XI ot Third Party)
    Please give me the full details of these two scenarios from Scratch.
    Thanks in Advance.
    Regards,
    Shalini Shah.

    Hi
    These r few links which gives u complete scenarios...
    for idoc to file:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
    for file to idoc:
    part1
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    part2
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    part 3
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    This link is also good:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
    Troubleshooting File-to-IDOC Scenario in XI.
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    kindly rewards points if helpful.

  • Idoc to idoc scenario with idoc tunneling

    IN idoc to idoc scenario with idoc tunneling  the XML_CONVERSION parameter to value 2  is set whish means An IDoc is converted to IDoc-XML if requested by the service
    I want to know where we specify this and how we specify?

    1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
    ref these weblogs.
    It is given under;
    <i>TCODE - SXMB_ADM
    - Integration Engine configuration
    - set the XML_CONVERSION parameter to value 2</i>

  • XML IDOC to Native IDOC Conversion

    Hi,
    We have a scenario, where we need to convert XML idoc into native idoc and write to a file. I am doing this based on
    How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0.
    When I first executed the scenario, I was getting the following error
    Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.
    After including the try-catch block, now i am just getting a blank file without any conversion.
    Can anyone help me on this?
    Regards,
    Ravi

    Hi,
    It looks to be error in ABAP mapping
    To test ABAP mapping in XI use the transaction SXI_MAPPING_TEST after creating a little scenario in the directory.
    Or even you could do this with below sample code
    Lets create one ABAP mapping class with the method IF_MAPPING~EXECUTE
    data: obj type ref to zcl_abap_mapping_test.
    data: source type xstring,
    result type xstring.
    data: param type ref to IF_MAPPING_PARAM,
    trace type ref to IF_MAPPING_trace.
    create object obj.
    try.
    CALL METHOD obj->IF_MAPPING~EXECUTE
    EXPORTING
    SOURCE = source
    PARAM = param
    TRACE = trace
    IMPORTING
    RESULT = result.
    CATCH CX_MAPPING_FAULT .
    ENDTRY.
    This is a link very useful for ABAP Mapping :
    http://help.sap.com/saphelp_nw04/helpdata/en/86/8280ba12d511d5991b00508b6b8b11/frameset.htm
    Or may be  think this exception you need to catch it in the ABAP..
    This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
    just cross verify with this guide-
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
    Thanks
    swarup

  • Idoc Acknowledgements and Idoc Packaging

    All,
    I am implementing a requirement wherein we need to post 2 different types of Idoc's from our BPM.  The Business requirements is such that until the Idoc 1 is not processed by the R3 system, the Idoc 2 should not be posted from XI as there is dependency in the data.
    This can be addressed using  Application Acknowledgements. The solution to this is to use the send step in my BPM with application acknowlegement. Until the application acknowledgement is not received for the first send step , the next send  step will not be processed and so things will / should work fine.
    The problem comes in the fact that the Idoc's being sent out of XI use Idoc Packaging, ie., the First Send Step uses Idoc Packaging to post multiple Idoc's to the target system.  A question that arises due to Idoc packaging and Idoc ack's are,
    <i><b>How will the Idoc Ack's be sent back to XI?</b></i>
    I have read through the online help and it states that every ALE AUDIT Idoc can contain the status of maximum 500 Idoc's. Now, in  my  case , when using my Idoc packaging, if the number of Idoc's are greater than 500, how will the Application Acknowledgement for the Idoc's work?  Will I still get a single acknowlegement in my BPM or will I get multiple acknowledgements? Will Send Step with Application acknowledgement still hold good?
    Any ideas, thoughts / experiences on using idoc ack's with idoc packaging?
    Regards
    Bhavesh

    If I undestatood correcty you have 2 send step, the first send a message containing multiple IDoc (IDoc Packaging). In this first send step you set the application Acknowledgements.
    I think that this is not managed from the BPM, bacause the acknowledgements will come someone positive and someone negative, and so when the first send step will be completed ?
    I think that the solution must to be changed a little bit, or removing the IDoc Packaging, or removing the wait of Acknowledgements.
    Also take in mind that if you use a BPM with many possible correlation (Acknowledgements) you will have bed performances.
    Regards,
    Sandro

  • Multiple IDOC to Multiple IDOC scenario without BPM steps????

    Hi
    Could you please give me the solution for this ???
    I want steps for sending all IDOCs at a time- ---"Multiple IDOC to Multiple IDOC scenario without using BPM".???
    thanks
    3nadh

    Hello,
    Refer the below, for certain details!
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi     ALE configuration for pushing idocs from SAP to XI
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change     XI: IDOC bundling - the "trick" with the occurance change
    Regards,
    Jilan

  • What is the difference beween idoc package and idoc collection

    Hi friends,
        i am unable to understand difference betwen Idoc package and Idoc cillection.
        Please give me clear clarification.
    Thanks and regards
    Bhanu

    Hi Bhanu,
    Apart from the replies above, in case you're looking for an answer from ECC perspective, here are some inputs: (ECC is considered as sender here)
    1. IDoc Collection:
       This will collect the IDocs and will not immediately send it to the target system after they are created. Program RSEOUT00 can be later scheduled for these collected IDocs to deliver them to the target. You can treat this as a park and process approach which proves useful in several business scenarios.
    This standard link gives more insight:
    SAP Library - IDoc Interface/ALE
    2. IDoc Packaging:
        This defines the number of IDocs to be packed and sent in 1 RFC call (tRFC). If you set is as 20, then 20 IDocs will be sent in 1 tRFC request. This doesn't connote whether the IDocs will be triggered immediately or later, this just talks about the bundling of IDocs per RFC call.
    Hope this helps.
    Regards,
    Abhishek

  • Two idocs with same idoc number in idx5

    We are using an idoc to file scenario where idocs are bundled using bpm and posted to ftp. here the issue is we are getting two idocs with same idoc number in idx5. due to which the file in ftp is getting overwritten.
    Could anyone suggest me what to do in this regard.

    Hi,
    >>>check your sender system is sending same IDoc twice ?
    if you send the same IDOC twice they both get different numbers as IDOC number is taken from the IDOC num range
    unless you're able to send the same IDOC twice with the same IDOC num somehow
    Regards,
    Michal Krawczyk

  • Idoc-xml to Idoc

    Hi,
    Sender is a 'party' which generates an Idoc. Some of the fields from this idoc has to be fetched by XI and passed to the receiver R/3 system.
    Requirement :
    Party -
    > Idoc-xml -
    >XI--> Idoc--
    > R/3
                           (XI - Adapter Sender)      ( IDOC Recevier Adapter)
    1) what are the initial setting to be done in Xi & R/3 systems?
    2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
    Also, here party is an 'R/3 system', who sends the data as an Idoc.
    3) How should i convert the idoc to Idoc-xml?  In other words how would i create my source DT,MT and MI ?
    Appreciate Ur comments,
    Thanks,
    Raggy

    Hi,
    Here are the answers pointwise.
    1) what are the initial setting to be done in Xi & R/3 systems?
    Initial settings are Port and partner configuration in both XI and R/3 systems. You have to configure the RFC destication also.
    2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
    Also, here party is an 'R/3 system', who sends the data as an Idoc.
    Why are you using XI - adapter???any specific reason?
    If party is an R/3 system then you can use IDOC adapter and if not then you can use FILE adapter to pick up the IDOC-XML file.
    3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
    You do not need to convert the idoc to idoc-xml. IDOC adapter will do it automatically.
    IDOC will act as a MT and also as a MI.
    Hope it clarifies your doubts.
    Br,
    Madan Agrawal

  • Why message type if  idoc type or idoc is already there.

    Experts.
    this has been posted several times and i gone through so many threads but stil some confusion . So anyone can tell in simple terms what is the difference and why sap has given this two instead of one.
    Diff. with IDOC type
    An IDoc type specifies the structure of the data.
    A message type specifies the meaning of the data
    *****from the above statements , by seeing the name of the idoc type ex matmas01 also we ca n say that it is used for material data, then why message type matmas needed?

    Hi,
    Idoc type means combination of segements
    Message type means Combination of idoc type
                              or
    Message type mean combination of Idoc type + Extension idoc type( Custom segments added to idoc type)..
    Example:-
    If you want to fill the data to custom segment which is available at exension idoc ...
    then first check the message type then check basic idoc type then check it contains exetension idoc type ..then fill the segment
    Generally the communication occurs between system through message type...
    Prabhudas

Maybe you are looking for