IDoc processing options

Hi,
We have a invoic message type outbound IDoc. My question is, which option is better amount below 2 options. In most of the business scenarios, which do we prefer and why ?
Option 1 - Send IDoc immediately
Option 2 - Collectively send iDoc. (Which background program do we need to select if we select this option ?)
Regards
Sudhaker

hi,
Option 1 is better as when you will select option 2 , the data will be sent in a huge amount if there is a long list of invoices. In most of the business scenarios, we are using Option 1.
For Option 2, for outbound idoc, I hope there is no need for background program selection for Outbound Idoc.
reward points, if helpful,
regards,
Sandeep Kaushik

Similar Messages

Receiving IDocs in XI from a system with Queue Processing option

I am trying to use the Queue Processing option that can be set in a partner profile for IDoc sending, so that qRFC is used.
I have set up the Rule Name as one of the defaults that come with the system, but when I execute the sending of the IDoc, it gets stuck with status 30 (ready for dispatch). I have configured the Output Mode of the IDoc as "Transfer IDoc Immediately".
SAP Documentation states that:
"When you send by qRFC, the IDocs are first put in an outbound queue in the sending system, and then in an inbound queue in the recipient system. You can assign IDocs to various queues and specify queue name rules. "
Is there something I also have to do in the XI system that is receiving the IDoc?
Kind Regards,
Tony.

Hi Anthony,
Now I have the same problem in between ECC6.0 and PI7.11.
If you solving the problem,
Please let us know how you did.
Best Regards,

Processing options for EDI vendor Invoices

I'm trying to get a better understanding of what my options are for processing EDI vendor invoices and would appreciate some help. I'm using message type INVOIC02 with process code INVL and in configuration I've set the processing option in table T076S to 4 (tolerence corresponding to online processing). When an invoice fails either the vendor specific tolerance check or the payment blocking checks the invoice gets parked with error status 3. This is behaving as I would expect. The issue I have is the price on the parked invoice is the price from the PO and not the price from the EDI segment. Is there anyway to change this? This makes it difficult to analyze the cause of the error without going back to the Idoc segments. I've tried playing with the other processing options but they also enter the PO price in the parked invoice. If it's not possible to change this are there any tricks that i'm missing that can help the users analyze the cause of the errors without going back into the idoc?
thanks,

If anyone has any expierence with this, I would appreciate any advice you may have.
thanks,

Scheduling inbound and outbound idoc processing

Hi everybody.
I ´d ike to know which is the best way to schecule the outbound and inbound idoc process.
Nowadays we are using this:
INBOUND PROCESSING
- In WE20 the idocs are checked with "Trigger with a background program".
- The program RBDAPP01 is scheduled with a job to trigger the process of the inbound idocs.
OUTBOUND PROCESSING
- The program RBDMIDOC is scheduled to create the idocs than have been created with change pointers.
- The program RSEOUT00 is scheduled with a job to trigger the process of the outbound idocs.
Is there any better option to improve de perfomance????
Edited by: Christian Abad Chico on Nov 13, 2009 10:09 AM

Any answer

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.

IDoc processing Delay

Hello guys,
we have a problem in our client for the IDoc processing. It is a critical process that have to be finished as soon as possible.
We take data from a Oracle Database, and do a transformation in PI 7.1 to a Z IDoc which is sent to R/3.
The problem is that seeing time execution there is a delay from the process in PI 7.1 and R/3.
For example: in our process PI execution is about 1 second, seeing monitoring it starts at 11:11:53 and finishes at 11:11:54.
The problem is in the IDoc creation, if we take a look at the IDoc the first entry with status 50 (IDoc created) is at 11:19.
The IDoc is Z and has option trigger immediately with a Z process code and a Z execution for the IDoc.
This interface is executed every 30 secons more or less, and the delay only occurs 1 time every week more or less, but they can't wait 8 minutes because it is a critical process.
We have an IDoc adapter with an RFC created at SM59, and the RFC is executed in milliseconds.
Do you know where could be the problem? There is any way to see where could be the problem or how to avoid it?
Many thanks in advance.
Regards,
Xavi.
Edited by: Xavi Carb on May 24, 2011 3:03 PM

Hello,
this message has a prioritized queue.
Seeing the IDocs in R/3, this interface creates IDocs every minute, but in a moment and for 10 minutes no IDoc is created, and after this time, 8-9 Idocs arrive at the same time.
It seems that the RFC queue is stopped or waiting for these minutes.
Creating another RFC for this interface would be the same?
Many thanks.
Regards,
Xavi.

Data Transfer using LSMW IDOC processing with multiple segments

we need to post the document data (Header structure, BP item structure, G/L item structure..etc) using LSMW IDOC processing.
is it possible to transfer data for all these structures (Segments) in single file?

Thanks for the reply.
I am assuming when we are specifying the file in LSMW we are going to give the option to generate the file with include all structures.
could you please elaborate further is there any thing specific we need to do while configuring LSMW to get the file for all segments in the IDOC with field names which we are going to populate with data, so that we can use it for data transfer.
any help document will be helpful.

Mail after IDOC Processing...

HI,
After processing an IDOC, whether it is successful or failure I need to send a mail to the respective user about that IDOC status. How we can achieve this please help me.
Thx

Hi Pandu,
You can have workflow in place for Idoc Error handling wherein it will send email to respective user.
you can refer links:
Send alert to business users when IDOC receiver processing fails in SAP ERP
http://www.erpgenie.com/sap-technical/workflow/display-workflow-log-for-an-idoc
http://www.scribd.com/doc/7179710/Error-Handling-on-Inbound-Idocs
Other option is you can go for BPM in PI side.
Regards,
Vivek

Trx.: WLF_IDOC - IDoc Processing

Hallo together,
I've a question regarding the transaction WLF_IDOC - Idoc processing.
It should be possible to edit an Idoc, for example an idoc with status 51.
If i mark an entry and press icon EDIT IDOC I get a new screen with the detail information of the idoc, but
it is not possible to edit any field. All fields are blocked.
Thanks in advance for your feedback.
Best regards
Frank

Hi Frank,
There is no WLF_IDOC transaction that exists and not sure which one you are referring to.
However you can go to WLFEIR transaction and provide the idoc number,wherein you will have the following options
1.Change Control Record
2.Change Status
3.Change View - This will take you to WE02 and you can change/edit any relevant segment and then save and then come back to initial screen and process it Online/using B87 or even in background
PS : There are also other options like sending idoc using RFC and comparison of idocs etc.
Hope it helps,
Best Regards,
Aram.

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

IDoc processing options

Similar Messages

Maybe you are looking for