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

Similar Messages

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

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

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.

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

TS3074 im can u please help me out this issue im trying to install iTunes in windows 7 some error showing " windows installer package problem DLL require to complete this installation" this message showing.

im can u please help me out this issue im trying to install iTunes in windows 7 some error showing " windows installer package problem DLL require to complete this installation" this message showing.

Try the following user tip:
" ... A DLL required for this installation to complete could not be run ..." error messages when installing iTunes for Windows

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

URGENT- IDoc Packaging - Que- Michal blog

Hi,
I was following Micahl's blog - for idoc packaging -
/people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
But there is another blog, which also by Michal.
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change ,
which is also mentioned in OSS note: Note 814393 - Multiple IDoc instances in an XI message.
Do I need to do both of them to achieve the Idoc Packaging.
I also noticed that in the first blog, it is about pushing Idocs out of R/3 system and in the second blog it is the other way round.
Can any one please clarify.
reg

with the first blog, how does sxmb_moni screen looks like - R3 system, XI. On XI it should not make any diff as XI is still splitting the packages.
Yes you are right...On R3 system, if packaging is done, then you will find all IDOCs as single message. As you said on XI it will not make any difference.
With the 2nd blog, XI would show single message for each package, but with more instances of the Idoc payload. (As shown in the first blog - look at the 2nd pic). Which means that you saving the queues but the payload size is more here in this case.
Yes..It show single message with more instance of IDOCs. You are right about saving the queues and payload size is also more

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 Packaging Problem

Similar Messages

Maybe you are looking for