Parallel IDoc Processing

Hi all,
I want to know about Parallel Processing in IDoc.
ie., what is parallel idoc processing
 what is the advantage,
 how to use,
 how it differs from mass data processing in IDoc,
whether we need to have in configure or by coding we need to have parallel idoc processing......
I got this <a class="jive-link-external" href="http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a662d507d11d18ee90000e8366fc2/frameset.htm" target="_newWindow">link</a> but as im new to idoc i could able to understand
Thanks,
Vichu

http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a662d507d11d18ee90000e8366fc2/content.htm

Similar Messages

IDoc Processing in SAP

Hi Team,
I have question about SAP Idoc processing ,
1) How does SAP process Idocs when it gets around 20 Idocs all in a fraction of secodes for same Idoc/process code and message type . Will SAP process them one by one , or it will process them all together in parallel processing. Please help me out with this.
2) We have SAP 3.1 released used for creating delivery when an Inbound Idoc get in to SAP. Most of the time we see Idocs creating delivery but some time Idocs does not create delivery in production, we never had this issue in quality. What can be probale cause of this isse?
3) We are facing a strange problem , We have one Inbound Idoc which perform following activity :
1.       Change delivery (Already created Delivery )
2.       MB1C (add Inventory )
3.       Picking
4.       PGI
In the above flow next step will be executed only when preceding steps is successful .Every process is doing itu2019s job in Test /Quality /Production system as expected . But in production some time we are getting some problem while performing Change delivery / Picking . I would like to know from you people have you ever came across such scenario or you have something to add to the process then please share the approach to minimizes the cause.
Please share your views.
Thanks,
Raj

Hi,
The no of IDocs processed at a time is based on the Packet Size that is specified in the configuration of the Partner Profile(WE20). Likewise the specification of the Output Mode is given as either Transfer IDocs Immediately or Collect IDocs in which case the IDoc would go to 30 status and it would have to be processed using RSEOUT00.
Thanks
Krithika

Idoc processing best practices - use of RBDAPP01 and RBDMANI2

We are having performance problems in the processing of inbound idocs. The message type is SHPCON, and transaction volume is very high. I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time. We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked. Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing. The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system. I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses. I have been told that setting the messages to trigger immediately in WE20 can result in poor performance. So I am wondering if the best practice is to:
1)     Set messages in WE20 to Trigger by background program
2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable. Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem. I would welcome any comments.
This appeared to be the correct area for this discussion based upon other discussions. If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it. Thank you for your help.

Hi Bob,
Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
Also I believe we had a designated server for the background jobs, which helped with the resource availability.
As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
Hope this helps.

Optimize inbound idoc process

Hi everybody.
Im trying to improve perfomance at inbound idoc process:
For instance I have scheduled the program RBDAPP01to process inbound ORDERS every 5 minutes. (The number of inbound orders to proces are 300 aprox.).
I have some question to choose the best variant to this job:
- What's better in transaction BD51 set the FM as mass process or single process? I think to choose mass process It´d be better because the FM would be call less times.
- What packing size I have to choose. I hope SAP recommends between 20-100.
- Should I choose parallelling process? It´d help me to improve the process???
Thanks a lot.
Regards

INBOUND_IDOC_PROCESS is the function module to be used before release SAP R/3 4.0; since release 4.0 you should use IDOC_INBOUND_ASYNCHRONOUS instead.
Similarly as indicated by the previous posting IDOC_INBOUND_SINGLE replaces function module IDOC_INBOUND_SYNCHRONOUS for posting a single IDoc.
Best wishes, harald

Creation of rfilr ports in WE21 from LSMW IDOC Processing

Hi,
I am trying to defile a file port for INBOUND IDOC processing status in LSMW.
Now when I go to create a file port in WE21, I give some dummy Physical directory name. But what should I give in
Function module field and Outbound file field ? Is it compulsary to put something in these fields...
Please help.....

Hi,
Function module field is used to define the path functionality of file generated.
EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
Hope this helps.
Thanks.
Mark points if helpful.

IDOC process in QM

Hi,
Can any one help me to understand the use of IDOC Process in QM???
In which scenarios we will use IDOC in QM.

Hi,
May be this link will help you.
http://scn.sap.com/thread/171671
sandip

Basic doubts in ALE/IDOC processing

Hi All,
1.How are IDOC Type and Message Type related? Many to one or One to Many?
2. what is the prominence of msg code and msg function in ALE outbound processing?
3. During outbound processing what is the startegy followed by the ALE service layer to pick up the customer model?
It would be great if any one can answer these questions in plain words rather than referring links. Reward guaranteed.

Hi Ravi,
1.Can'te we assign more than one IDOC to the same msg type if the IDOC's are of different versions?
Yes we can. Doesn't SAP do that? For example, ORDERS01, ORDERS02 ... ORDERS05 are having the same message type ORDERS. You can also create your own IDoc type or extend the standard IDoc type.
3. When we run a stand alone program to trigger IDOC processing the only mandatory field will be the message type, so how can the sending system identify the receiving system?
You need to setup partner profile (t/code WE20) and distribution model (t/code BD64). Once this configuration are done, The system will populate automatically the IDoc Control Record for sender and recepient system information when the IDoc generated based partner profile setup.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Inbound idoc processing by workflow

Hello,
How can I find if an inbound IDoc has been processed via workflow ?
following are details -
1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
2)manual re process in test system using WE19 has all four status records by login user ID.
3)BD67 values for this process code was checked for the start events.
4)I checked standard task 30200090 following oss note 325361
5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020
I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
thank you very much in advance,
Bhakti

Hello,
How can I find if an inbound IDoc has been processed via workflow ?
following are details -
1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
2)manual re process in test system using WE19 has all four status records by login user ID.
3)BD67 values for this process code was checked for the start events.
4)I checked standard task 30200090 following oss note 325361
5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020
I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
thank you very much in advance,
Bhakti

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Send mail to a specific user group when an Inbound Idoc processing fails

I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

RBDAP001 causing a short dump when submitted in a FM for IDOC processing

Hi All Gurus,
I have a situation wherein I need to automate the processing of failed INBOUND IDOCS.
So the status of failed IDOCS could be 51 or 64 or anything like that.
I tried using statement 'SUBMIT RBDAP001 with......'. in a custom FM , however I got a short dump.
When I debugged I realised that RBDAP001 pops up a screen with the final IDOC processing result which probably may be the cause of dump. Dump message is 'CNTL_ERROR'.
So is there a way how I can suppress this screen OR use any other function module to process these inbound Idocs.
Appreciate your advise on same.
Thanks and Regards
RK

Hi Rajiv,
Please use program RBDMANI2 to reprocess IDoc with status 51.
Also check program RBDINPUT for reprocessing IDoc with other statuses.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

How to control IDOC processing in XI

hi
I have scenario where File --> XI --> IDOC
Source structure
Header           1...1
    Detail         0..unbounded
Trailer             1..1
For every detail i need to generate 1 doc
My requirement is that i dont want to send all the IDOCs at one shot from XI.
trfc connection should be open just once for all the IDOCs and not single IDOCs are posted.
Is there any transaction from where i can control my IDOC processing.
Need urgent help.
Thanks ,
Loveena

Hi Loveena,
in a scenario, for instance, where you send IDOCs of type LS (logical system):
1. In the sender system, call transaction WE05 to display the outbound IDoc. The IDoc partner type of both receiver and sender is LS.
2. On the Integration Server, call transaction SXMB_MONI (Integration Engine Monitoring Monitor for Processed XML Messages) to display the message.
3. In the receiver system, call transaction WE05 to display the inbound IDoc.
if it helpful reward points are appreciated

Function module creation for IDOC processing...

hi Experts,
             i want to create a function module for idoc processing..
message type: zashpmnt
idoc type : shpmnt05
plz tell me which standard FM is used... and tell me what changes i want to do in it....
Tnx in Advance..

Hello,
         If you are trying to process an Outbound IDoc for the SHIPMNT05 IDoc Type with an Extension, you can use the IDOC_OUTPUT_SHPMNT Function Module which is assigned to SHPM Process Code.
       In Addition, since you have an IDoc Extension, you are required to populate the Custom Segment / Fields. For this, there is a Customer Function / Exit called EXIT_SAPLV56K_002 which you can use it for adding your Custom Segments to the IDoc ZSHPMNT05.
       If you are writing code in this exit, make sure to create a Project in CMOD.
       Also, ensure that you've made the assignment in WE82 with the Message Type , IDoc Type & the Extension.
       For Inbound, if you would like to Create a Custom Function Module, you can follow the Naming Convention Z_IDOC_INPUT_SHPMNT for which you are required follow the below Steps.
1. Register the FM as Inbound FM in BD51 T-Code.
2. Assign the FM to IDoc Type & Extension in WE57.
3. You'll need to Create a Custom Process Code in WE42 in which you are required to make add your FM.
4. Maintain Partner Profiles in WE20.
5. Have the Process Code Migrated to the Testing Environment as creation of Custom Process Code is a Customizing Activity and it requires a Customizing Request to be created / Migrated.
6. Define the Parameters as defined in the Standard Inbound Function Modules such as IDOC_INPUT_ORDERS , IDOC_INPUT_DELVRY etc.
Thanks and Regards,
Venkat Phani Prasad K

MIRO / F-53 in IDOC process

we have a requirement where in we need to post invoice using idoc_input_invoic_mrm FM (coming as INVOIC02 IDoc) and once posted successfully, immediately clear the document using F-53..
What is the best approach to do this?
1) clone IDOC FM and call BAPI to post F-53? Do we need to issue COmmit work before F-53 to ensure that invoice posting is commited?
Or this is not feasible?

Generally inbound IDocs handler FM is called by number of ALE layer FMs which manage also commit to data base.
The call stack for immediate IDoc processing:
- program RBDAPP01
- FM APPLICATION_IDOC_POST_IMMEDIAT
- IDOC_START_INBOUND
- IDOC_INPUT
-- form IDOCS_PROCESS (here customizing is resolved and actual IDoc handler FM is dynamically called)
--- FM TRANSACTION_END with actual COMMIT WORK
This is an example which shows that you have to do your own commit after calling IDOC_INPUT_INVOIC_MRM and before document clearing. In addition all "create" routines inside IDOC_INPUT_INVOIC_MRM are called with addition ON COMMIT - so actual commit is out of control of IDOC_INPUT_INVOIC_MRM.
Regards,
Maxim.

Strange result of IDoc processing in the LSMW

Hi
I am using MATMAS_MASS_BAPI IDoc in the LSMW to transfer material master data into client's SAP system. After IDoc processing I got green message with text that application document was successfully processed (IDoc
status = 53). But I can't view created materials using MM03 transaction. Then, records number in the MARA table before and after launching of LSMW is equal. What may be a reason of this situation? How to solve this problem?
Edited by: Marat on Nov 4, 2008 5:24 PM

Hi there
take a look at the Idoc overview, there should be a t100 message in there if there is a data issue with the idoc BAPI load. However this could be something inconclusive such as 'Inconsistent characteristics' or suchlike. In which case you'll have to check the data and that it matches the requirement for the object

Parallel IDoc Processing

Similar Messages

Maybe you are looking for