Idoc package size

Hi Guys,
We are using Idoc adapter packaging (sender side) thanks to Mike.
The problem is we want a package size bigger than 10k and ECC limits that to 9999 (4 digits)
What are the options for us?
We are planning to go with XML-File or XML-HTTP.
But if the standard packaging size can be increased somehow to overcome the 9999 restriction, we will be more than happy to go with that solution.
What are your experiences with this?
Thanks
Jai

Vaas,
Many thanks.
If I understand correclty, the approach described by Sravya will only enable processing all idocs at the same time.
It will still process them as separate messages and hence creating as many files.
Is my understanding not correct?
Thanks
Jai

Similar Messages

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

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

Query on Idoc Packaging with PI7.1 EHP1

HI PI Experts,
I have a scenario where batch run triggers the 100's of Idocs in R3 in few milli seconds, which means all Idocs are triggered in one go From R3.
Do we still need to set Check box for Collect Idocs in Partner Profile in R3 for Idoc Packaging ?
I want to make out the difference in 2 configs for Idoc Packaging where
A) All Idocs are sent via Report run of RSEOUT00 at a go after collection.
B) All Idocs are triggered at same time via Batch Run at same time.
Assumption:
PI is configured to use Sender Idoc Adapter with Idoc Package Size of 10.
OR
I frame my Query in other way"
What does Collect Idoc and running Report RSEOUT00 achieve to make sure that Multiple IDOC Nodes come into 1 XML message? OR Its only PI Sender Idoc Adpater take care of it when multiple Idocs of same type comes through PI?
Please reply .
Regards,
Anurag

Hi Anurag,
In the sender IDOC adapter if the packaging option is not activated, then the IDoc packages get split into single PI messages, one PI message per IDoc. IDoc sender functionality is enhanced to preserve and process IDoc packages without splitting the IDoc package into individual PI messages. I.e. single PI message contains multiple IDocs including control records. Where as running the report RSEOUT00 will just send all the IDOCs that are in waiting state to their respective destinations.
For the sender IDoc adapter to be able to process packages, it should receive the IDocs in a group. I.e. in the sender partner profile the packaging option has to be activated. Though you've activated the packaging option in the sender partner profile, If you dont check collect option in sendet IDOC adapter then the IDOCs get splitted into individual PI messages.
Regards,
Priyanka

Package Size parameter in Partner Profile

Hello guys,
I'd need your advice. We have 2 systems (SAP and Non-SAP) and we need to connect them by mean of HR-PDC interface (IDoc communication is supported). We can create new Partner Profile in SAP and we can add a few IDoc types as Inbound Parameters of the partner profile. Then it is possible to define maximal package size for several IDoc types. I suppose that the Non-SAP system reads the Partner Profile and the "Package Size" parameter for the particular IDoc type before it sends some IDoc to SAP system. IDoc's size is limited by the parameter.
And now our problem. We need to insert XI between these 2 systems. XI should only forward IDocs and nothing else. How could I set up limitation of IDoc's size? Do you thing that following scenarion could be working?
I would define Partner Profile in XI same way as in the previous case in SAP. XI is configured to process IDocs in Integration Server by means of IDoc adapter. My expectation is that the Non-SAP system would read the partner profile in XI (including "Package Size" parameter) and then it would send IDoc to XI. Then XI would process the received IDocs in IDoc adapter.
How can be "Package Size" parameter useful for inbound IDocs?
Best Regards,
Zbynek

Hello ,
Check the blog below
/people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
Rajesh

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

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.

Maximum package size for data packages was exceeded and Process terminated

Hello Guru,
When i am execute the process chain i got this message Maximum package size for data packages was exceeded and Process terminated,any body help to me in this case how can i proceed.
Thanks & Regards,
Suresh.

Hi,
When the load is not getiing processed due to huge volume of data, or more number of records per data packet, Please try the below option.
1) Reduce the IDOC size to 8000 and number of data packets per IDOC as 10. This can be done in info package settings.
2) Run the load only to PSA.
3) Once the load is succesfull , then push the data to targets.
In this way you can overcome this issue.
You can also try RSCUSTV* where * is an integer to change data load settings.
Change Datapackage size for extraction, use Transaction RSCUSTV6.
Change Datapackage size when upload from an R/3 system, set this value in R/3 Customizing (SBIW -> General settings -> Control parameters for data transfer).
IN R/3, T-Code SBIW --> Genaral settings --> Maintain Control Parameters for Data Transfer (source system specific)
Hope this helps.
Thanks,
JituK

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

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 message No Package size option

I'm maintain partner profile-->outbound parameters, but I can't find a option to set the package size.
NetWeaver2004s(in the SAP Discovery system)
Anybody can help me?

As far as my knowledge, Package size (collect idoc)is generally not visible when, either ur messge type or basic type is not mentioned correctly,
Also check ur receiver port.
Regards,
Pratibha
Message was edited by:
Pratibha

Partners profile - outbound parameters - package size ?

Hi,
My scenario: IDOC(R/3)-XI-File.
R/3 settings: WE20 - While filling out outbound parameters in partners set up i am getting error "<b>please enter a value for package size</b>" highlighting <b>Receiver port</b> in red. My receiver port is tRFC type whose RFC destination would be XI server.
I have created logical systems(SALE) for sender(R/3) and receiver(XI) as well assigned them to clients.
Please help.

Hi Bhavesh,
This is what exactly I did and I ended up getting this error message. I did some research on how to generate partner profiles on sdn.
"transaction SALE), choose Modeling and Implementing Business Processes ®Maintain Distribution Model and Distribution Views (transaction BD64)."
So,I have created a model view called "EC4_TO_PI1".
Then I chose Environment----> Generate Partner profiles. Now, I have to select two model views. (From & To). From Model View I have selected the above model view " EC4_TO_PI1". I am not sure about TO field.
Can you please guide me to helpful documentation ? I am not even sure what is distribution model is. Thank you for your help.
By the by, I have already created logical systems for sender(R/3) and receiver(XI). fyi.

Value of package size issue with partner

Hi
Iam trying to configure idoc type in the partner, but when i try to save it, is giving the following error
"Please enter a value for package size".

Hi Kalyan,
Check we20 (partner profiles) and the mode (in outbound) it it is collect you need top specify a size for package
Check this thread too
Re: ale/idoc setting
Regards
Suraj
Edited by: S.R.Suraj on Oct 12, 2009 12:09 PM

Info on package size

Hi,
I would like to understand what does this setting means in infopackage
Maximum size of a data packet in kByte = 50000?
How do I determine what is the package size that is going to come from the source system? Is there any documentation or notes that tells what the suitable package size is?
Number of data packets per Info-IDoc = 10
How does records get divided per package? On what logic?
I extracted the data into PSA.
DP 1 = 8000 records
DP2 = 9500
DP3 = 8400.
The number of records is not same in all the packages. How does it work?
Thanks
Annie

The individual records are sent in packages of varying sizes in the data transfer to the Business Information Warehouse. Using these parameters you determine the maximum size of such a package and therefore how much of the main memory may be used for the creation of the data package.
SAP recommends a data package size between 10 and 50 MB.
if you transfer a lot of fields, you can transfer less lines...
if you transfer less fields, you transfer more lines,...
more info :
http://help.sap.com/saphelp_nw70/helpdata/en/51/85d6cf842825469a51b9a666442339/content.htm
M.

Idoc package size

Similar Messages

Maybe you are looking for