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

Similar Messages

  • Idoc Packaging from sender side Idocs

    Hey,
    Can anybody suggest me the best approach/practice to do the idoc packaging with PI 7.0 SP 15.
    -Esha

    Hi,
    Refer
    SAP Network Blog: XI/PI: sender IDOC adapter packaging ?
    The specified item was not found.
    Message Packaging with Process Integration Component of SAP NetWeaver 7.0 - Webinar Powerpoint
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40a10c62-d000-2a10-c1a6-dbb3ce727300
    Thanks
    Swarup

  • IDoc Packaging from XI/PI to SAP instance - possible?

    Hello,
    I'm looking for a way to package IDocs into a single tRFC call from XI/PI to a SAP instance, has anyone done something similar previously? So far all I've been able to find are solutions for the IDoc Sender Adapter (SAP to XI/PI).
    Messages are sent into PI via the XI protocol one at a time, then mapped and sent to an SAP instance - I do not want to introduce ccBPM into my scenario and we are not at a sufficent SP level to use message packaging. Any ideas?
    Many thanks,
    - Ian

    Hi,
    ahh sorry then:)  then it's even easier this works in standard with any SP:)
    have a look at my blog:
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    also described in my book with screenshots:
    http://www.sap-press.com/product.cfm?account=&product=H1935
    this approach is very easy
    Regards,
    Michal Krawczyk

  • 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

  • Deactivate Idoc packaging in PI 7.1

    Hi,
    We know that Packaging by default enabled in PI 7.1 but we want to turn off this feature for Idoc processing. Could you please help me in turning off this feature? Thank you very much in advance.

    From 7.1 forth, the IDOC packaging is the same as the regular packaging. So, to disable for IDOC scenarios, please go to the SXMS_BCM transaction and set the interfaces that shouldn't have packaging to "NO". This should disable the packaging for specific scenarios.

  • PI 7.1 EHP1 : IDoc packaging

    Guys
    I am currently on PI 7.1 EHP1 , Trying to do Idoc packaging for one scenario , I am not sure what size I have to put in the tab
    ( IDoc package size ) in sender IDoc channel . I  also donot know the frequency of IDocs . I saw one video in it it was told that the package size shouldnot exceed 2MB size .
    Please help in this regard
    Regards
    Ninad

    Hi Ninad,
    I had used IDOC packaging in one of my scenario, which is very similar to yours. I dont know how many idoc are coming from source system. I put 100 in the IDOC package size parameter. when you put 100 in this parameter it will create a file wil maximum 100 idocs if your system is sending more than 100 than it will create send file
    For example from source system you are getting 150 idocs so 2 files will be created
    file1 conatins 100 idocs, file2 contains 50 idocs
    Regards,
    Shradha

  • 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

  • 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

  • IDOC and IDOC Package

    Hi Experts,
    I'm refering the following web blog /people/prasadbabu.nemalikanti3/blog/2006/02/24/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-1 and a bit confused. My questions are.
    Q1. in section 6. the author is saying "CREMAS.CREMAS03 can be used as a single IDoc and not as a package"  wht does an IDOC package represents and why he is using IDOC Package instead of Std. IDOC i.e., CREMAS03.
    Q2. wht is the purpose of step 7.
    Q3. in step 9. under 9.1  the mapping is created between File message type and CREMAS03 instead of CREMAS03_package.
    Q4. in 9.2 "Interface mapping between File Interface and abstract interface of File".  why  mapping is required between file interface and abstract interface of file?
    Q5. in 9.5 "Message mapping between Original IDoc and CREMAS_package, make it as multi mapping" why this mapping is required?
    Regards
    Faisal

    Hi Abdil,
    IDoc Message Packages
    Use
    This function enables you to activate IDoc message packages quickly and efficiently. You use IDoc message packages to process and send messages from the IDoc adapter as packages rather than individually.
    Integration
    You can define filters for selecting messages for message packages and jobs for processing these packages by using event-driven message processing.
    Prerequisites
    In the menu Exchange Infrastructure ® Administration you have called the transaction IDoc Message Packages (IDXPW) and are on the Activation of IDoc Message Packages initial screen.
    Features
    You use this function to specify a message and do the following:
    ·        Test whether filters are already defined to filter this message at runtime
    ·        Test which of the defined filters actually filters this message at runtime
    ·        Define and activate a filter if none exists for this message
    The message that you specify must be a message that has been processed successfully by the receiver IDoc adapter.
    Activities
    To activate an IDoc message package, you must first specify the ID of a message. You have the following options:
    ·        Enter a known message ID manually.
    ·        Use the input help to select a message ID.
    The entered or selected message is used as a template for activating a message package.
    To check whether a filter has already been defined for the message, choose Filter Test. If a filter exists, the entire filter data is displayed in a separate window. If multiple filters exist, the data is displayed for the filter that actually filters the message at runtime.
    To continue with the activation of the message package, exit the filter display and choose ENTER on the initial screen. The system displays the following:
    ·        If a filter has already been defined for the specified message (one package activated), the remaining fields are filled with the values of this filter. You can now only edit the values in the following fields:
    ¡        Maximum Package Size
    ¡        Job Period
    ¡        Period Unit
    ¡        Start Immediatelycheckbox
    ·        If only parts of a filter have been defined for the specified message, the corresponding fields are filled with the defined values and the remaining fields contain default values, which you can accept or change.
    ·        If no filters have been defined for the specified message, you can edit all fields.
    Make your entries and changes and choose Execute.
    This activates the package for the specified message and schedules the specified job automatically. The current filter data is displayed in a separate window.
    Go through this link...
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/bab13bb3acd607e10000000a11402f/content.htm
    Thanks,
    Satya Kumar
    Reward if it is useful

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

  • Huge no. of IDocs flow from XI to R/3

    Hi,
    One of my customer wants to run certain jobs that will create IDocs of around 90K and those will first reach XI prod box and from there messages/IDocs gets transferred to R/3 production server. I have two questions on this :-
    <Sender R/3 server> -> <XI Prod> -> <Receiver R/3 prod server>
    1) At sending R/3 system I can run bgd jobs at certain intervals to control IDoc generation flow towards my XI server. But in XI servers all messages shows in queues (SXMB_MONI) one after another. Is there any way bundle them a range (date/time wise) and then ensure those group of messages delivery towards destination i.e. towards R/3 production server.
    2) Any of you observed 90K+ IDocs flow from XI prod box to R/3 prod server ? Is possibility for performance bottleneck at R/3 prod server end ? Anything to take care at XI end for this ?
    Any insight on this will be highly appreciated.

    Is there any way bundle them a
    Few options
    /people/michal.krawczyk2/blog/2009/05/21/xipi-collecting-idocs--possible-ways-with-pros-and-cons--5-ways
    If on Ehp1, choose idoc packaging (the last option)

  • IDOC Package

    Hi Guys,
    I have the following scenario WS->XI->IDOC but in this scenario there will be several calls from WS and we want to send an IDOC Package.
    I have seen some blogs regarding the collector pattern on BPM but in some of them I have seen that there is a performance issue with this solution.
    I saw also the  Srayva's Blog XI:IDOC Message Package but the scenario is IDOC-XI-File and I was wondering if I can apply this solution to my scenario? or do you know more solutions?
    Thanks
    Omar Hernandez

    hi,
    if you call WS several times you need to use collect pattern
    you can find more about IDOC bundling in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • R/3 connection to BIW - No Idocs arrived from the source system

    Question,
    Hi Team,
    I have issues during loading attribute data from R/3 source system to BI,
    I go to the path
    Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
    Later I select the following options
    Full Update = select
    On the Processing tab page, select only PSA.
    On the Schedule tab page, choose Start Data Load Immediately and start the data load.
    Till here everything is in active version and saved, and connection to the source system is active and working fine.
    However when I do loading I received following messages, what I observed in Monitor window,
    Data was requested OK
    Request still running
    Diagnosis
    No errors found. The current process has probably not finished yet.
    System Response
    The ALE inbox of BI is identical to the ALE outbox of the source system
    or
    the maximum wait time for this request has not yet been exceeded
    or
    the background job has not yet finished in the source system.
    Current status
    No Idocs arrived from the source system.
    When I go to detail tab, under transfer section, I receive the following message
    Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
    But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
    But when I chose to run the transformation I donu2019t get data here,
    Kindly help me to resolve this issue,
    Regards,
    BluSKy

    Hi,
    the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
    i am not sure about transactions settings about r/3 side,
    could you plz throw some light on this issue,
    regards
    blusky

  • 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]

Maybe you are looking for