IDoc packets in SP11

Hi -
Support for collecting and sending IDocs in packets was supposed to be part of SP11.
The tuning guide mentions it on page 13:
"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."
Was this actually implemented in SP11? I don't see any notes about it or any new parameters in the IDoc Communication Channel.
Thanks,
Jesse

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.

Similar Messages

IDoc included in IDoc packet containing an error: transfer it separately

Hi Gurus,
I'm having this problem in our ECC side. I already did what Michal said in his blog:
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
I have bundled the multiple IDOCs into 1 MATMAS.
But I'm still having the error IDoc included in IDoc packet containing an error: transfer it separately.
I've searched in the forums and none of them worked for me.
Thanks in advance!

Disable packaging or change the Partner Profile on WE02 transaction to "process immediately" the IDOCS.
When you process the IDOCS in background mode, it will create packages (it is enabled by default), and in case any of them fail you won't be able to see the root cause, but will have to go to BD97 transaction to process them again. Therefore, please use the "process immediately" or disable packaging and then you will be able to either see the error or process it because it won't fail because of another IDOC.

Getting error 51 saying 'IDoc included in IDoc packet containing an error'

When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.
Can any one tell me how to resolve this.

Hi,
Change the packet size to 1 then process again.

Getting error saying 'IDoc included in IDoc packet containing an error'.

hi experts
When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.I changed the packet size also but it was not resolved.
Can any one tell me how to resolve this.

Hi,
Check below link......
Getting error 51 saying 'IDoc included in IDoc packet containing an error'
even this link is not solving problem then check the aplication log to get exact error text.
Thanks,
Asit Purbey.

Idoc packet size inbound

any idea on setting the inbound idoc packet size while mass processing

Hi,
If you set packet size as 10, if 1000 idocs reached to the system ,then 100 backgrounds jobs(program RBDAPP01 )will be executed to process these 1000 idocs.
Check this link :
http://www.dataxstream.com/doclib/ALEOptimization.pdf
Regards
L Appana

Set idoc Packet Size to always be a single packet

Hi All,
WE20 config has a field for packet size. If I set it to 1, the system will create 1 packet/LUW for each idoc.
If I set it to two, it will wait until there are 2 idocs available and then create 1 packet/LUW for both idocs. however, if that second idoc is never created, the first idoc will never be sent.
Is there a way to specify that the system always send 1 packet/LUW for any number of idocs? So lets say today I created 10 idocs - the system would send that as 1 LUW. Tomorrow, I create 25 idocs, and the system would send that as 1 LUW.
I'm guessing the answer to this is NO, because the system will never know when to stop waiting for more idocs and send them to the receiving system already. The PI developers here are looking for a way to avoid implementing BPM, because they say it will cause performance issues. This was suggested as an alternative. As I said, I doubt it's possible, but I wanted to make certain before going back to them with that info.
Thanks,
Bryan

For some reason I was under the impression that RSEOUT00 wouldn't send the idocs unless the number had been reached, but I see that is not the case.
I always make things more complicated than they need to be.
Thanks!

Processing large volume of idocs using BPM Processing

Hi,
I have a scenario in which SAP R/3 sends large volume say 30,000 DEBMAS Idocs to XI. XI then sends data to 3 legacy systems using jdbc adapter.
I created a BPM Process which waits for 4 hrs to collect all the idocs. This is what my BPM does:
1. Wait for 4 hrs Collect the idocs
2. For every idoc do a IDOC->JDBC Message transformation.
3. Append to a Big List
4. Loop at the Big list from step 4 and in the loop for
5. Start counter from 0 and increment. Append to a Small List.
6. if counter reaches 100 then send a Batch JDBC Message in send step.
7. Reset counter after every send.
8. Process remaining list i.e if there was an odd count of say 5300 idoc then the remaining 53 idocs will be sent in anther block.
After sending 5000 idocs to above BPM following problems are there:
1. I cannot read the workflow log as system does not respond.
2. In the For Each loop which loops through the big list of say 5000 idocs only first pass of 100 was processed after that the workflow item is not moving ahead. It remains in the status as "STARTED" but I do not see further processing.
Please tell me why certain Work Items are stuck is it becuase I have reached upper limit and is this the right approach? The Main BPM Process is also hanging from last 2 days.
I have concerns about using BPM for processing such high volume of idocs in production. Please advice and thanks in advance.
Regards
Ashish

Hi Ashish,
Please read SAPs Checklist for proper usage of BPMs: http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm
One point i'm wondering about is why do you send the IDocs out of R/3 one by one and don't use packaging there? From a performance stand point this is much better than a bpm.
The SAP Checklist states the following:
<i>"No Replacement for Mass Interfaces
Check whether it would not be better to execute particular processing steps, for example, collecting messages, on the sender or receiver system.
If you only want to collect the messages from one business system to forward them together to a second business system, you should do so by using a mass interface and not an integration process.
If you want to split a message up into lots of individual messages, also use a mass interface instead of an integration process. A mass interface requires only a fraction of the back-end system and Integration-Server resources that an integration process would require to carry out the same task. "</i>
Also you might want to have a look at the IDoc packaging capabilities within XI (available since SP14 i believe): http://help.sap.com/saphelp_nw04/helpdata/en/7a/00143f011f4b2ee10000000a114084/content.htm
And here is Sravyas good blog about this topic: /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
If for whatever reason you can't or don't want to use the IDoc packets from R/3 or XI there are other points on which you can focus for optimizing your process:
In the section "Using the Integration Server Efficiently" there is an overview on which steps are costly and which steps are not so costly in their resource consumption. Mappings are one of the steps that tend to consume a lot of resources and unless it is a multi mapping that can not be executed outside a BPM there is always the option to do the mapping in the interface determination either before or after the BPM. So i would sugges if your step 2 is not a multi mapping you should try to execute it before entering the BPM and just handle the JDBC Messages in the BPM.
Wait steps are also costly steps, so reducing the time in your wait step could potentially lead to better performance. Or if possible you could omitt the wait step and just create a process that waits for 100 messages and then processes them.
Regards
Christine

Partner profile settings - Trigger Immediate or Collect Idocs ??

Hi All,
We have EDI Setup between SAP and a EDI system and Idocs flowing with port type TCP/IP connection.
we are facing issue at some times where in the Idoc is created and is in status 03 / 12 (trfc queue is cleared) but not found in the EDI system.
what I have observed is the issue has occurred for only few vendors where partner profile setting in trigger immediately
and it has not occurred t for every Idoc created, only some Idocs were missing in EDI system.
issue was not present in case where partner profile setting in collect Idocs.
So it that do we have a best practice to set partner profile to collect Idocs (packet size ~ 20) when sending to EDI subsystem?

Hi,
It seems the issue is not because of your partner profile setting since your status of the IDOC is 03 0r 12.
Output mode 'Transfer Idoc Immediate': Single Idoc is transfered immediately to the EDI system when the output triggered
'Collect Idoc': Idocs generated for the particular message type will be collected in a single file and are triggered to EDI system at a scheduled time. Here no of Idocs sent in a file will be decied based on packet size.
It may be problem with your network connectivity.If are using a EDI substem then you use file port not trfc port.
Check how the EDI sytem is reading the Idoc files which are created in R/3 OS level is it through FTP???
Regards
Praveen

IDOC failure in R/3 Inbound processing

Hi
I was able to successfully generate XML files from Syndicator, but when it comes for processing in R/3 side it get fails all the time with the IDOC err msg : "IDoc included in IDoc packet containing an error: transfer it separate ".
Kindly adivce how to solve the same.
thanks in adv
Alexander

Hi Ravi
Let me explain in detail.
From R/3 to MDM --> All materials in one XML file.
while from MDM to R/3 --> 3 diiferent IDOC am able to
see, one for each material in Inbound Processing.
kindly advice me how to fix the same.
thanks
Alexander

IDOC Receiver Adapter, getting Lock Table Overflow to CRM System

Hello SDN!!!
This scenario is for PI to process a file and send to CRM via IDOC. The IDOCu2019s are only being created and not processed until later.
Problem: I am getting a Lock Table Overflow error in method IDOC_INBOUND_ASYNCHRONOUS via sm58 in PI which points to the CRM box.
I have been searching many forums and every solution seems to indicate increasing the lock table, the problem with that solution is we are currently trying to create (not process yet) 80000 IDOCu2019s. This would allocate too much for the lock table.
So my question is this, Shouldnu2019t the lock be released when the IDOC gets created or none the less when a packet of IDOCu2019s via content management (breaking up the file in 1000 increments) finish. The lock table in CRM keeps increasing until all rows from the file, sent via IDOC adapter in 80 messages with 1000 IDOCu2019s per messagein the table are complete (80 separate messages in sxmb_moni).
Background:
IDOC was imported, changed to include unbounded and reimported.
Content Management breaks the file into 80 different segments, thus creating 80 distinct mappings with distinct MessageIdu2019s.
80 IDOC packets are sent to CRM, via IDOC adapter and sm58.
TCODE sm12 in CRM shows the table to keep growing and locks not released until full message is complete.
Any help would be appreciated
Cheers
Devlin

The only way to process the IDOCs in this case is by increasing the "enque/table_size" parameter in order to create the required IDOCs. You can increase the value for this parameter up to 102400 (beyond that can cause performance issues). Since you need to handle 80000, this shouldn't be an issue.
Please refer to the notes below for more information about the lock queue overflow and management.
[Note 552289 - FAQ: R/3 Lock management|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=552289]
[Note 13907 - System error in the block handler, overflow lock table|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=13907]

Passing IDOC to BAPI

Is there any way of passing an IDOC contents to a BAPI directly, rather than reading the data from the IDOC segments and populating the BAPI structures manually?
The IDOC is generated from a Purchase Order created in the same client and so cannot be looped back into the system as an Inbound document. Instead I am sending the outbound IDOC (generated from the PO) to an ABAP function module port which will create the Sales Order.
Useful suggestions will be rewarded.
Regds
Thiru

Check with the fillowing bapi's
BAPI_IDOC_INPUT1 Inbound BAPI IDoc: Individual Processing
BAPI_IDOC_INPUTP Inbound BAPI IDoc: Packet Processing
Reward points if useful.

WAIT statement used, IDOC output time still same

HI All,
I have created a Zprog to trigger zIDOCs from R/3 to XI.
In my program, multiple idocs of same type are created as the processing is within a loop statement.
Due to this fact 5-6 idocs are created within a second and sent out immediately to XI.
However I want idocs to go to XI in 1 sec intervals, so I introduced the WAIT statem,ent in the loop.
But when I check WE02, again all IDOCS are craeted in the same time(second), so I do not see any time delay.
I wanted to know if theer is a way to introduce REAL DELAY in sending IDOCs from R/3 to XI as currently all my idocs are going out at same time inspite of using WAIT statement.
In my partner profile I have tried the scenatio with Process immediately and also with collect Idocs(packet size 1), but its not helping.
Any suggestions, how to make the idocs leave R/3 witha time delay of 1 sec each between them?
Appreciate any suggestions/pointers.
Many thanks
Shirin

Hi Swastik,
Will WAIT UP TO 60 SECONDS help and send idocs in 1 sec interval.
I do not want a very long delay between these idocs.
Or is it that wait upto 60 ecs translates to 1 sec internally....just trying to understand.
Appreciate if you could clarify.
Many thanks
Shirin

Idocs take time to reach XI from R/3.

Idocs trigerred from R/3 takes around 45 mins to reach XI.
What could be the possible reasons for the same??

Hi,
Check this from SAP help regarding mass IDOCs settings.
Mass processing refers to bundling IDocs into packets that are then dispatched and processing in the receiving SAP system. Only one RFC call is needed to transfer several IDocs. Performance is considerably better if you dispatch optimal packet sizes.
To set mass processing parameters, in ALE Customizing choose: Modeling and Implementing Business Processes ® Partner Profiles ® Generate Partner Profiles. For a given message type you can define the outbound parameters, packet size and processing mode.
If the processing mode is set to Collect IDocs and transfer, outbound IDocs of the same message type and receiver are sent in a scheduled background job in an appropriately sized IDoc packet. The IDocs can be dispatched in a scheduled background job or in ALE Administration.
Some distribution scenarios cannot support mass processing of inbound IDoc packets. This is especially true if the application sending the IDocs uses the ABAP command CALL TRANSACTION USING. In this case the outbound parameter PACKETSIZE must be set to "1".
You can find a list of function modules for mass processing in ALE Development by choosing IDocs ® Inbound processing ® Function module ® Define attributes (BD51). These function modules have input type 0.
Check this note as well
Note 706521 - IDoc: Performance improvement when you create IDocs
Regards,
Venkata S Pagolu

IDoc error handling via WorkFlow. What is missing?

Hi All,
My problem is when an error occured I don't receive anything in the Workplace.
I did the following:
When I created the process code I gave an object type(based on IDOCAPPL) for the function module's IDoc part. For the start event I gave the INPUTERROROCCURED event and for the end event the INPUTFINISHED.
I created a standard task where the triggering event is the object type->inputerroroccured and the terminating event is object type->inputfinished and the object method is the object type->inputforeground. I use a standard role with a "Z" function module to determine the agent.
I tested the role with an IDoc number and it worked. It gave me back a position where is my userid is the only id. The concistency check shows me 2 red line: the missing IDoc Packet section (I think it's not needed) and at the Role assignment (I think it's good so I don't understand this).
So, Do you have any idea what is wrong?
Thanks for your help in advance.
Regards,
Gyula

Hi Gyula
Can you tell how you are actually raising that event .?
I assume that you have created a process code and attached it to some function module and therein wherever you are getting error(when you want to trigger workflow) you are raising an event for your object type and its event .
Since i cant check out your code , it guess you can try setting your task as General Task first to just get sure whether the event linkage is active for event or not and your workflow if at all is really getting triggered or not . If these things work fine with out then certainly your role determination function module needs to be checked.
Kind Regards
Shovit

MATMAS IDOC

Hello all,
Iam working on Material master Data Upload using the IDOCs.
-There are about 3K records.
-I have collected the IDOCs and executing the RBDAPP01
-in background with Parallel processing and with Packet size as 5.
All the IDOCs processed these way are going to in to an Error :
IDoc included in IDoc packet containing an error: transfer it separately
Regards
GangaPrasad

HI,
Inorder to package or bundle IDOC u can go for two methods.
Idoc Packaging:
Consider a file to IDOC scenario, where 1 file will contain multiple IDOCs. So, you need to send these multiple IDOC s to R3 system.
Now, one way would be to use a BPM, but a better way is to use the PACKAGINg where these multiple IDOCs are packaged as one IDOC and then on R3 , there are unpacked into multiple IDOCs.
1) In XI where u need to do a configuration
Please find weblog link on Idoc Packaging
/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
2) U can collect the IDOC in R3 and put the IDOC XML file into R3 server and use the file adapter communication channel to pull that file.
FOr more information please go through the below weblog:
1)Collecting IDocs without using BPM By Stefan grube's
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
I think u have the same requirement.
Thnx
Chirag

IDoc packets in SP11

Similar Messages

Maybe you are looking for