IDOC packaging in 7.1 - structure problems

Hi guys,
I am using the new PI 7.1 IDOC packaging functionality. On backend side everything looks fine and the IDOCs are received by
PI in single package. However, if I use as an Outbound interface the IDOC definition,  in Message Mapping the occurences of <IDOC> will be 1..1, however in the packaged message there are many <IDOC>s - 1..n.
How can I overgo the fact that if I use the IDOC basis objects interface in order that receiver &  interface determinations to be
found and used, and still the message structure to reflect the fact that I am using packaging..? Thanks
Best Regards,
Lalo

>>in Message Mapping the occurences of <IDOC> will be 1..1, however in the packaged message there are many <IDOC>s - 1..n.
It does not matter. You can use the standard idoc (with 1..1) occurance in both your message mapping as well as interface.
The reason is the occurance of the source message is not validated by Message Mapping.
Regards
Jai

Similar Messages

  • IDOC Packaging Problem

    Hello all,
    I have below scenario,
    collect multiple IDOCs and process them in single file. I did all the configuration for message Packaging. The messages are getting executed after the specified interval but not in single message they processed seperatly and and creating file per IDOC.
    Is there any one came across this scenario. please help me out in this. What is going wrong in this?

    Hi,
    >>>Actully, i am using below configuration, does anyone know if this configuration will work for IDOC packaging.
    no, the blog you mention has nothing to do with IDOC packaging into one file
    only this one works:
    /people/shabarish.vijayakumar/blog/2010/01/22/idoc-packaging--sap-pi-71-ehp1-and-above
    but as I already mentioned it I guess you're not reading my answers
    Regards,
    Michal Krawczyk

  • Query realted to IDOC packaging in case of  IDOC-SAPPI- FILE scenario

    Hi,
    I have requirement related to IDOC packaging, i.e. SAP ECC -SAP PI - FTP server.
    I have done the following settings:
    1) In WE20, I put the partner profile settings to collect mode.
    2) I am using RSEOUT00 to trigger the collected IDOCs for example 2 idocs together.
    3) In SAP PI, I have done the following settings
    a) I added the the parameter in sxmb-adm, RUNTIME , PACKAGING & Value 1
    b) I have used IDXPW t-code to activate the message packages for IDOC
    c) I run the job through sxmb_adm t-code, configure event driven message filtering
    d) I exported the xsd of ORDERS05 and changed occurence of source structure to 0 to Unbounded and imported it in Integration Repository.
    e) I am not using mapping & interface mapping as I just want to post the IDOC structure as it to the receiving FTP server. Therefore when I changed the occurence of ORDERS05 xsd to 0 to unbounded my idea was that in the outbound message interface it will be reflected which will be ultimately reflected in Integration directory.
    Problem Details:
    When I test for the 2 PO idoc from SAP ECC, it generates 2 messages in SAP PI and also 2 files in FTP server but actually it should generate one output file containing both the IDOC details.
    Note: I am just trying to merge 2 idocs of PO as IDOC package into one output message.
    Can anybody what configuration settings I am missing for the packaging.
    Thanks & Regards
    Prabhat

    Hi Prabhat,
    If you are using PI 7.0 EHp1 or PI 7.1 Ehp1, you can configure packaging parameter and create single file for multiple idocs without using BPM.
    In other case, you have to use BPM.
    But recommended approach would be to create XML file port on SAP ECC and create IDOC XML file.
    You must have set collect IDOCs option in partner profile.
    Now you can execute RSEOUT00 report program and specify IDOC type and number IDOCs to be collected.
    This configuration will generate IDOC XML file for number IDOCs you specified in RSEOUT00 report program.
    In PI you can use File adapter to pick the file.
    Here is the nice blog explaining entire process:
    /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
    Best Regards,
    Divyesh

  • IDOC DELVRY05 TO EDI 856 - Mapping problem

    Hi all,
    i'm currently working on a outbound mapping with the delivery idoc (DELVRY05) and the EDI 856 (Advance Shipping Notice Definition)
    The problem is that i can't map the items for every pack in the structure because the ocurrency doesn't match.
    The EDI 856 has a segment called G_SHL (ocurrence 0.200000), that i replicated 4 times for shipping, order, pack and item data
    And this segment has a subsegment called  G_SHL/S_HL (ocurrence 0.1)
    RESULT DESIRED GIVEN BY THE CLIENT: (1 pack/1item)
    3     HL1*S~                        ======> S: shipping, 1 hierarchy)
    4     TD1CTN251***G223.997*LB~
    5     TD5*2ABFSM*CC~
    6     REFBM003030987~
    7     REFCN086044619~
    8     DTM01120080128*180610~
    9     DTM06720080204~
    10     FOB*PP~
    11     N1SFStiefel Labs~
    12     N4DULUTHGA*30096~
    13     HL21*O~ ======> O: order, 2 hierarchy, 1 was the previous hierarchy)
    14     PRF*4064561~
    15     HL32*P~ ======> P : Pack, 3 hierarchy, 2 was the previous hierarchy
    16     MANGM00000734620052976193~
    17     HL43*I~  ======> I: Item , 4 hierchay, 3 was the previous hierarchy
    31     LIN*UP073462150651LT45X5147ND00145150605~
    32     SN1*12EA~
    33     DTM03620090930~
    34     HL52*P~  ======> P : Pack, 5 hierarchy, 2 was the previous hierarchy
    35     MANGM00000734620052975189~
    36     HL65*I~ ======> I: Item , 6 hierchay, 5 was the previous hierarchy
    37     LIN*UP073462150651LT45X5147ND00145150605~
    38     SN1*12EA~
    39     DTM03620090930~
    40     HL72*P~ ======> P : Pack,7 hierarchy, 2 was the previous hierarchy
    41     MANGM00000734620052975196~
    42     HL87*I~ ======> I: Item , 8 hierarchay, 7 was the previous hierarchy
    43     LIN*UP073462150651LT45X5147ND00145150605~
    44     SN1*12EA~
    45     DTM03620090930~
    46     CTT*8~
    47     SE479220014~
    As u see, all packs belong to "2 hierarchy" (order), and items to their correposding pack
    (has a comment, the "hierarchy number" is always given by a counter so u won't find the exact number again)
    so, the client wants us to create an structure that is like this..
    1º Pack
    1º item
    2º item
    2º Pack
    1º item
    2º item
    (the example has only one item, but they say that is going to be with many items)
    - The problem is that the structure data of the Idoc doesnt match EDI 856 structure
    E1EDL37 (0.99999)  -
    Pack data -
    G_SHL (0.200000)
    E1EDL37/E1EDL44 (0.99999) -
    Item data -
    G_SHL/HL (0.1) <====
    i was doing different G_SHL for pack and items but that leaves me with a wrong structure, and with all the hierarchy data wrong for items (since the mapping can't see which item belong to his pack)
    1º Pack
    2º Pack
    3º Pack
    1º Item
    2º Item
    3º Item
    - How can i map the structure Pack/item if in the idoc got too many item positions for only one EDI corresponding segment??
    Thanks in advance!

    Alains,
    We have the same tear, pack and item problem with one of our customer in one of my project. To acheive this result with the standard schema is not possible because this is a custom one.
    So I would suggest to change the schema in BIC like the occurrence and within the third G_SHL you should have S_HL and within this you should have a S_HL so that for every pack you will have multipe items.
    The bottom line is to have the schema as required by your mapping. Once you change the schema deploy the maps in J2EE and use them else it will throw an error in RWB.
    Regards,
    ---Satish

  • IDOC packaging/No packaging - need either/or depending on receiver

    Hello IDOC adapter gurus,
    We have an existing scenario with IDOC packaging, in which the message goes to multiple receivers . The client wants to OMIT idoc packaging for a single one of the receivers. Since the packaging is done in the sender adapter, how can I accomplish this in XI? A separate Partner Profile is already set up for this receiver in the sending system, so that side is not a problem.
    One idea I'm exploring would be to create a new sender comm channel without packaging and a new Sender Agreement with Virtual Receiver and select the receiver in question, however I can't find enough documentation on the VR feature. Would that work? Any other ideas?
    Thanks in advance.
    Carlos

    >
    Carlos Herrera wrote:
    > Hi Ravikanth,
    >
    > Yes, I intend to do that, but the question is, will that be enough since it will still go through the comm channel that has idoc packaging configured? In other words, will the comm channel package size act as a "max size" or "min size"?
    >
    > Thanks.
    > Carlos
    if it is configured to be not do the collect at the partner profile end, you dont have to worry.
    the IDoc adapter will not do any collect even if the package size is set.

  • 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

  • Idoc packaging questions

    Hi
    I am aware that in Idoc packaging how Sender Idoc adapter packaging is done and also know that it is available from PI7.11
    I have 2 questions...
    1. Suppose there is a data issue with a single idoc ,,because of that entire package will fail...then it would call for finding the erroneous idoc ...correct the data and resend all the Idocs again..
      This problem can occur again and again...and because of this the entire package will be stopped..
    So is it a good option to not do packaging and send a single Idoc and insert it as a record in target database.
    2. In case i am doing idoc packaging the occurence of IDOC in mapping will still be 1..1.
        How do i manage my mapping such that each Idoc in the package should insert a separate record in the database table
    Hema

    >
    > 2. In case i am doing idoc packaging the occurence of IDOC in mapping will still be 1..1.
    >
    >     How do i manage my mapping such that each Idoc in the package should insert a separate record in the database table
    >
    Map IDoc to access tag, in this case one record for each IDoc will get inserted.

  • IDoc Packaging + Ack ALEAUD = bad behavior ?

    Hi,
    I'm in version PI 7.11 and I'm studying the IDoc packaging of EhP1 with Acknowledgment (ALEAUD).
    My scenario is a basic one: File -> PI --> ECC (100 idocs). And then ECC returns Ack.
    So for the returned Acknowledgment, I have that:
    - on ECC, I did ALE config, and I run programs RBDSTATE / RSEOUT00 to create one IDoc ALEAUD (Ack).
    - In PI, I use a sender CC (Idoc adapter) by using option "Idoc Packaging".
    - In PI, I use a Sender Agreement with Idoc ECC's ALEAUD and this sender CC.
    - In PI, I use program IDX_ALEREQUEST on ECC's ALEAUD idoc.
    My problem is:
    ECC send me ONE idoc ALEAUD which contains 100 segments corresponding to 100 Idocs received at the first step. BUT even if I used the "Idoc Packaging"... in IDX5 of PI, I have not one idoc ALEAUD, but I have 100 Idocs ALEAUD !
    And so after that my mapping is run 100 times instead of one ! Image if I need to return an email... with this PI behaviour, I will send 100 "Ack" emails.
    So does somebody know why IDoc Packaging does not work with ALEAUD whereas program IDX_ALEREQUEST is correctly used ?
    Thanks
    Mickael
    Note: I don't want to have to create a BPM to collect my ALEAUD Idocs. That's too heavy...
    And (for the moment), I don't want to create a specific ZALEAUD idoc...

    Hi Prashant,
    yes, I did not precise it, but of course IDXNOALE is used, else PI will generate an Ack of this ECC's ALEAUD... so a ack of a ack... but it's not really my problem.
    what I say is:
    - Request : PI -> 100 idocs MATMAS (for instance)
    - Ack : ECC return to PI only one idoc ALEAUD with 100 segments "E1STATE" corresponding to the 100 idocs MATMAS.
    - Ack : PI receive this only one ALEAUD... but in IDX5 and in SXI_MONITOR, we see in fact 100 IDocs ALEAUD with 1 segment E1STATE, instead of having only one idoc ALEAUD (like in ECC side) !
    So I'm searching a way to keep in PI the only one Idoc ALEAUD sent by ECC, in order to be able (for instance) to send only one email (and not 100 emails like it's the case for the moment).
    Regards
    Mickael

  • IDOC Packaging Sender CC

    Hi Gurus,
    I've been using IDOC packaging in the IDOC sender communication channel very well without any problems so far.
    Most of my scenarios I have to group several IDOCS and generate just one file, and using the new functionality I can reach my scenario easily and with good performance.
    However I am trying to configure this same thing for a new IDOC, but it's not working.
    So, I've checked the option in IDOC sender communication channel as usual, set up the size for 9999, I go to we20 and change the partner profile to collect IDOCs and also set it up to 9999 as package size.  Following this blog. IDoc Packaging - SAP PI 7.1 EHP1 (and above)
    However for this new configuration, when I trigger 2 or 3 IDOCS at the same time it creates 2 or 3 messages in PI as well, and it should create just ONE message in PI. What make me confuse is If I trigger 2 or 3 IDOCS for the other type of IDOC, regarding the old configuration it works...just one message is created in PI
    So I am really confused why for this IDOC is not working and for the OLD configuration is working. Am I missing something ?
    Thanks
    BEst REgards
    Diego

    Hi All,
    Yes, I had done everything
    In fact I wanted to see the IDOC being collapsed with several IDOC nodes in the monitoring.
    So the problem was solved quite easily I was triggering the IDOC through the program and the OutPut node was in blank and by default is set to 2 (transfer immediately) it skips the configuration that you have done in we20 and do it by itself.
    So I put the propoer Output mode (4) and it worked well
    Thank you for the answers
    Regards
    Diego

  • IDoc Package from XI to R/3

    Hello,
    Is it possible to send an IDoc package from XI to R/3?
    I saw the following some time back in a tuning guide (Feb 2005):
    "In SP11, a solution will be available for IDoc adapter outbound processing to collect IDoc-XML messages and transfer them as an IDoc package, as in the traditional IDoc world. The IDoc adapter is designed to be able to process IDoc-XML structures that represent IDoc packages. This enables IDoc-XML packages to be generated during mapping if the inbound data structure of a message already includes the package data. This structure can then be processed by the outbound IDoc adapter and sent as an IDoc package to the receiver application."
    Does anyone know if this got released?  Where is this set up in XI?  Tuning, IDoc adapter, mapping, BPM?
    What is meant by "... if the inbound data structure of a message already includes the package data"?  Is there a setting in the data type for this?
    Thanks,
    Lisa

    Alexander,
    If the data has gone out of XI successfully and IDOC has been recieved by R/3, you cannot track the same in XI.
    In R/3, you can look at the list of IDOCS using WE02 transaction. Please take a look at the status of the IDOC and it should tell you what could be the error.
    Regards
    Ravi

  • IDoc Packaging on Event Driven Message Processing Message Filter

    Hi Experts,
    I am testing IDoc Packaging on Event Driven Message Processing and I got struck at scheduling the job.
    My scenario is IDoc to File. I have created sender and receiver id with coresponding interfaces. While creating the message filter I have selected outbound channel --> IDoc Packaging Option n I have took 10 as Package Size in Messages. In SM 36 I have created JOB and in the step I have selected SXMS_START_JOBS.
    Now my problem is while creating the JOB in SM36 what condition should I select? How do I test this event driven message processing with IDoc packaging??
    Please guide me...
    Regards
    SAPTOTAL

    in the event, you should also have a job for RSEOUT00 scheduled so that the IDocs are send out as a package

  • WE20 - Pack size not working/IDOC packaging not working - PI 7.1

    Hi all,
    My requirement is to collect idocs and send to PI at one point of time in a day.
    I kept Pack.Size = 100 in partner profile (WE20), in PI 7.1 - Sender Communication channel I assigned the same value 100 to pack size.
    Now the problem is when I create more than 10 idocs and trigger manually by rseout00. for example
    15 idocs are pushed to PI by executing RSEOUT00. In PI when I check IDX5 or SXMB_MONI, 2 message ID's are generated one with 10 idocs and the other with 5 idocs.
    It works fine meaning creates only one message id if the total count of IDOC's are 10 or <10.
    Any ideas/suggestions appreciated.
    Thanks,
    Krishna

    Yes Prateek,
    In Sender Communication channel - IDOC package size is assigned as '100' and only 10 idocs are collecting for one message id.
    I checked the assignment and it was correct. I changed the description, saved and activated Sender agreement & Sender Communication Channel.
    No luck.
    Regards,
    Krishna

  • Difference between IDOC Bundling and IDOC Packaging

    Hi,
    Can anybody please explain the difference between IDOC bundling and IDOC packaging?
    Thanks,
    Loveena.

    Hi,
    IDoc Bundling is the changing the occurance of IDoc.
    In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
    1.Import the IDoc to XI.
    2.Export the IDoc(i.e XSD format) and save it to the local machine.
    3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
    4.Save it as an XSD file Itself.
    5.Import the XSD file in the IR under the External Defination.
    6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
    Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
    IDoc Packing is collecting of IDoc
    <a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
    Regards
    Santhosh
    Remember to set the thread to solved when you have received a solution
    [url=Use a Good Subject Line, One Question Per Posting - Award Points;  Use a Good Subject Line, One Question Per Posting - Award Points[/url]

  • Unable to update itunes. help. error message when trying to update to latest version of itunes. "the installer has encountered an unexpected error installing this package. this may indicate a problem with this package. error code 2721"

    unable to update itunes. help. error message when trying to update to latest version of itunes. "the installer has encountered an unexpected error installing this package. this may indicate a problem with this package. error code 2721"

    Hello chae84swangin,
    I recommend following the steps in the article below when getting an error message trying to install iTunes:
    Trouble installing iTunes or QuickTime for Windows
    http://support.apple.com/kb/HT1926
    Thank you for using Apple Support Communities.
    Best,
    Sheila M.

  • Idoc data in flat file structure

    Dear Experts,
             We have  idoc data in flat file structure. We need to fetch it using ftp and map it to an idoc.
    please tell me how to proceed .
    Thanks,
    Aju

    Hi,
    For flat file you need to use the File content conversion parameters.
    Refer the blog,
    SAP Network Blog: How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
    How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
    Thanks
    Swarup

Maybe you are looking for