Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

IDoc packets size

Former Member
0 Likes
5,204

Dear all,

I may need your expert advice to verify if i have the correct thoughts for IDoc packets size as below:

Outbound

I set the packets size to 100 in WE20 and the Output Mode is "Collect IDocs". During execution of program RSEOUT00, let's say the program founds total 120 IDocs that need for outbound sending.

So how the pre-set packets size 100 work here?

Will program RSEOUT00 send out as 2 batches ? That is, 1st batch it sends 100 IDocs with single LUW, and 2nd batch send 20 IDocs with another single LUW?

Inbound

For Inbound, i set the processing mode to "Trigger by background program". In the selection screen of program RBDAPP01, i key in 100 to parameter "Pack. Size". Let's say during the execution of program RBDAPP01, it founds 120 incoming IDocs.

So how the pre-set packets size 100 work here?

Will program RBDAPP01 process the Inbound as 2 batches? That is, 1st batch it process 100 IDocs with single LUW, and 2nd batch process 20 IDocs with another single LUW?

Kindly comment.

7 REPLIES 7
Read only

Former Member
0 Likes
2,389

Hi

for IDoc packages look at:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/2a6661507d11d18ee90000e8366fc2/frameset.htm

max size of the IDoc is 1000 Bytes.

check the field SDATA in EDID4 table.

"Size" of Idoc depends on the message type.

Regards

Kiran Sure

Read only

Former Member
0 Likes
2,389

Hi Kiran,

Thanks for your post. I have fully understand the link that you attached.

Basically my main concern now is on LUW that i mentioned in my earlier post. According to the eg that i given in my earlier post there are 120 total IDocs read, and 100 is the packets size that input in selection screen of program RBDAPP01.

So for this case, i know that program will process IDocs into 2 batches, 100 IDocs for 1st batch and 20 IDocs for 2nd batch. Since i have read through some source from internet(can't recall the web add) by saying that for the scenario above, program will post the 1st batch into single LUW and 2nd batch into another single LUW.

For this statement and example, im expecting if one of the IDoc facing update error in 1st batch (100 IDocs), then there is no update for the rest of 99. I have tested for this case, but system doesn't bundle them into single LUW. The result is 1 IDoc failed, the rest of 99 still got updated into system.

The result is totally conflict with what i have read. I'm banging my head now by reading the SAP std code to figure how the LUW works with Packets Size.

Could you please advice if i left out any config or my concept is wrong totally?

Thank you.

Read only

0 Likes
2,389

I don't think there is anything wrong with your concept. I sure would mind if of 100 idocs only ONE was processed due to some small error in the first IDoc.

So I'm not sure about the other web site, which was talking about a SINGLE LUW for the first and a SINGLE LUW for the second batch.

Read only

0 Likes
2,389

Hi Guys,

This is the url link mentioning about the IDocs update in same LUW:

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6688507d11d18ee90000e8366fc2/content.htm

Please comment. Thanks.

Read only

0 Likes
2,389

Ok, but the way I read it, it says that the COMMIT will only be done once. All documents will be posted in one go, but if one of them fails, this won't matter. It has no influence on the others.

Read only

0 Likes
2,389

Hi Micky,

I have been thinking too much till i misunderstood the statement that stated in the link. Thanks for pointing me out, I'm now understand that irregardless of how many batches of IDocs being executed during the same session, there will be only SINGLE/SAME LUW that handling the update. This is fine.

But I'm still quite not agree with the statement "SAME LUW" mentioning in the link. As i understand from the SAP bundling concept, SINGLE/SAME LUW update will conclude in this way:

1. Status of update is conclude as Success if it pass all of the update .

2. Status of update is conclude as Fail if one of the update failed .

I'm adopting this concept into IDocs-Packet size here. Back to the eg given in my initial post where if one of the IDoc failed in Batch 1 (100 IDocs), system shouldn't update anything.

Please point me out again if i can not relate SAP bundling concept into IDocs-Packet size.

Sorry for asking silly question again, but i want to get my concept and expectation right.

Thank you again.

Read only

0 Likes
2,389

Guys any idea?