Tracking IDOC reprocessing

[Former Member]

I have developed a File to IDOC interface in PI/XI. The file I pick up will contain a list of invoices from a vendor system ,

that I convert into ACLPAY IDOCs and post invoices.

When the IDOCs are posted into our SAP system some of the IDOCs fail and some of them are successful.

At the end of a business day the user will execute txn we05 to see the status of the IDOCs that came in for that day.

If any of the IDOCs failed the user would use WE19 to correct the data and reprocess the IDOC again.

The problem is the old IDOC that came in still has a error status and the new IDOC created by modifying the old IDOC doesnu2019t have any reference to the older IDOC.

Is there a way to see if and IDOC was created by reprocessing an already existing IDOC?

Or is there a better method to handle my scenario?

Thanks

Siva

[Former Member]

Hi,

for reprocessing error Idoc instead of going to WE19, try to change the error idoc and provide correct value.

editing the values can be done as below.

select the idoc and the segment and double click on the segement. then EDIT from menu.

after editing save the idoc and reprocess it from BD87.

a new IDoc will be created with the original data(status 70) and thecurrent idoc will be sucessful and there will be link between the two idocs for tracking purpose.

Regds,

Suresh

[Former Member]

Hi Suresh,

Thanks alot for your answer. It worked like a charm!

Just need some more information.

I'm both the XI and ABAP developer.

I am able to pick invoices and submit them as ACLPAY IDOCs. The inbound process code for ACLPAY IDoc is a custom one.

I do a BDC call transaction which parks the invoice in FV60.

If the parking fails due to some reason i plan to trigger a workflow.

Is there an example which i could use for my scenario?

[Former Member]

Hi siva,

there are different programs and t-codes available to reprocess the error Idocs

with out creating new idocs.

Program RBDMANI2 for status 51 & 52

Program RBDAPP01 for status 64 ,66

Program RBDAGAIE for status 32 and 69 (Edited IDocs)

Program RBDSYNER for status 26

BALE - ALE Distribution Administration

WE05 - IDoc overview

BD87 - Inbound IDoc reprocessing

BD88 - Outbound IDoc reprocessing

BDM2 - IDoc Trace

BDM7 - IDoc Audit Analysis

BD21 - Create IDocs from change pointers

SM58 - Schedule RFC Failures

Basic config for Distributed data:

BD64: Maintain a Distributed Model

BD82: Generate Partner Profile

BD64: Distribute the distribution Model

Programs

RBDMIDOC - Creating IDoc Type from Change Pointers

RSEOUT00 - Process all selected IDocs (EDI)

RBDAPP01 - Inbound Processing of IDocs Ready for Transfer

RSARFCEX - Execute Calls Not Yet Executed

RBDMOIND - Status Conversion with Successful tRFC Execution

RBDMANIN - Start error handling for non-posted IDocs

RBDSTATE - Send Audit Confirmations

FOr testing you can use WE19.

Program RSEOUT00 for status 30

re-process IDocs failing in 29 status, use program RBDAGAIN.

transactions WEINBQUEUE and WEOUTQUEUE to control the individual queues

Prabhudas

[Former Member]

Used the following to resolve my problem

http://wiki.sdn.sap.com/wiki/display/Snippets/ALEEDIErrorHandlingvia+Workflow