Tracking IDOC reprocessing

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

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

Similar Messages

Idoc reprocess issue

Hi,
I have a problem with idoc reprocessing .An idoc contains the date field which shows the system date.I t always shows the default system date as Thursday.
But when we reprocess some idocs ...they are not showing the default system date (Thurs day) showing the current date .
Pls advice.
Regards,
Somenath

hi
use
report RBDAPP01
to change status from 51(application document not posted)
to 53(application document posted)
reward for use ful points
regards
Nagesh.Paruchuri

How to track IDOC

Hi Experts,
I use WE19 to reprocess an existing IDOC (source IDOC). WE19 will generate a new IDOC. My question is how can I track the source IDOC of this new IDOC? Is there any way to get the source IDOC regarding this new IDOC number generated by WE19?
Thanks a lot.
Yu

Thanks George! But I couldn't find the original IDOC through BD87. My example is: original inbound IDOC 9001, run WE19, change few segments' value, get new inbound IDOC 74001.
Can you kindly let me know in BD87 how to get the original IDOC?
Thanks again.
Yu

Idoc reprocessing in Custom program

I have a custom program which displays the IDoc data for the message type = ZSTLSP in the ALV format.
Requiremt is that I shall select a record and change one of the coulmn contents . A button 'Reprocess' will be
made available , when clicked it needs to reprocess the Idoc . The reprocessed idoc will be strored with the new values entered
and the original idoc will be stored with status 70.
Kindly let me know how to reporcess the IDoc in the custom program.
p.s.: Function module IDOC_INPUT does also reprocess ..but it does not disoplays the updated status.

Hello,
You may call standard program RBDAPP01 to reprocess the IDOCs using SUBMIT statement. Pass the IDOC Number, Message type etc. while submitting the program.
Thanks,
Venu

Tracking idoc

I have a jms-xi-idoc scenario. I am sending lot of idoc's to ECC through XI. There is a time lag
by the time idoc's reaches to ECC from XI. Is there any way to track the XI message with idoc number
with out seeing the segments of the idoc ?? By using message id of the XI can we track the corresponding
idoc ??
thanks
kumar

Hi Palanati Kumar,
I got your requirement.
If you know the IDOC Number and if you want to find the corresponding XI Nessage, Follow the following steps.
In the backend system
1) Go to WE02 and give the idoc number and press F8.
2) Double click on the control record and go to DEtails tab.
3) Copy the Identification number (Exclusinh the First 3 characters ).
4) The Identification number is nothing but the message id of the message in XI.
Go to XI system
1) Go to IDX5 transaction.
2) GIve the message ID that was copied from Identification number.
3) Press F8 and double click on the record that displays after wards.
Regards,
Ravi

IDOC reprocessing with new conversion rules

Hi All,
we've created IDOCs and after the creation the conversion rules are changed. Now we want to reprocess the IDOC's and in the reprocessing we want to use the new conversion rules.
I've tried just reprocessing, I also tried WE19, but with these 2 the conversion rules seem to left untouched.
Has anyone a solution were I can reprocess making use of the new rules?
kind regards,
Pieter

Hi,
I've debugged the reprocessing of the idoc and it seems indeed I had to change the status, however not all statusses result in reprocessing of the rules. Status '29' Error in ALE Service works. So my problem is solved.
Thank you.
kind regards,
Pieter

Tracking Idoc status in target system from XI

Hi
We have done File to IDOC Scenario succesfully i.e HR
data from file has been mapped to HR Idoc(HRMD_A06) .
Now when Idoc is posted to R/3 , SXMB_MONI shows
successful status(Idoc posted successfully) .
But when we check in R/3 in WE05 transaction ,though
the idoc is present but it shows status 51/52
with message "Idoc could not be posted" /"IDOC not
fully posted" .
In this case how can we track in XI whether the Idoc
is properly posted in the target system(i.e R/3) .
Since XI only shows that Idoc was successfully sent
irrespective of the status in R/3 .
Please suggest as we are new to XI .
Regards,
Shikha

Hi
Thanks for the guide.
we are not sure of the steps to configure it in R/3
system so that it sends the acknowledgement back to XI
system.
When we tried to configure it as per the guide , for
test purposes we executed the program RBDSTATE but it
gave message "No parties are interested in the selected
data" .
Please guide us on this .
Thanks
Shikha
Message was edited by: Shikha Jain

Outbound error IDoc reprocessing

I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
1. In general scenario how do we handle outbound error idocs?
2. Is system process codes are used only for notifications or error processing?
Inputs will be appreciated regd outbound error reprocessing .
Thanks.

Hi Indira,
1. In general scenario how do we handle outbound error idocs?
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
2. Is system process codes are used only for notifications or error processing?
The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
Hoep this will help.
Regards,
Ferry Lianto

Idoc reprocess status 03

hello
i need to reprocess idocs in status 03 through bd87
but it is not allowing
please help

Hi Manu,
Looks like you are trying to reprocess the IDOC which is already processed correctly.
Unfortunately there is no way by which you can do it.
I can give you a work around though:
1) Go to WE19 enter your IDOC number which already has status 03 and execute.
2) On next screen it will display the IDOC, choose approporate button on toolbar (standard Function Module) to process it.
3) This will generate the new IDOC similar to the one which was posted completely.
4) Now the new IDOC should have status ready (Unless you have clicked Process Immediately in WE21 for this message type, it shud be execute by Background Job).
This approch is applicable for testing.
Let me know if it solves your query.
Regards
Shital

RBDMANI2 Idoc Reprocessing IDOC Failure Notification

Hi SAP Friends,
I developed an inbound interface for LIV electronic invoice(MIRO) with basic type INVOIC02. At present everything going smooth.
i scheduled a background job with the program RBDMANI2 to reprocess the failed IDOCS. i.e if any failed idocs required SAP side changes, users will complete the changes. Then the scheduled job will process the failed IDOC.
IDOC will process if corrected data is satisfying else IDOC will fail again with Status 51.
Now the failed IDOC notification we are not getting any notfication.
If IDOC is failing first time idoc failure notification will come. At that point Object Type IDOCINVOIC & Event INPUTERROROCCURREDMM is triggering.
When i am reprocessing through the scheduled job of program RBDMANI2 , i am not getting any failed notification.
Can anyone help me out where i am missing the event. i need to activate any other event linkage for the reprocessing.
I tried with SWELS, i did not get any event when i execting the program RBDMANI2.
Appreciate your help and valuable inputs.
Thanks & Regards,
Srinivas Bhavanam

Srinivas, per my understanding the failure event is only triggered once. You can attest this yourself by executing the associated workflow. If you select the process option and all errors were not addressed, the current work item remains active ; eventually the error message will be changed in case the IDOC is now failing for another reason. There is only one workflow instance for the same IDOC ; the failed batch processing does not generate any new workflow or IDOCs, it only updates the current instances (workflow) and add an entry to the IDOC status table (EDIDS)

IDOC Reprocess,

Hi Gurus,
I have a problem wiht IDOCs. One of my End User is reporcessing IDOC of other country. When I look into his authorizations, he don't have authorization for that particular country where he is reprocessing. Even when I asked user, he don't know what exactly going on, but in reports system is howing user id.
If any one have any idea how it is allowing user to repocess pl let me know.
Regards
Jayakar Reddy

BD87 - is used to reprocess the Idocs.

IDOC reprocessing

I have a File to IDOC interface. 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 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

Hi All,
Thanks for all the responses.
I'm using We02 for such a long time , didnt know i could edit the IDOC directly there.. thanks a lot!
I used this method to change and reprocess the IDOC and it worked great!
I also think the Workflow approach is a neat one.
Rajesh,
Could you give me links to any such scenarios?
I will explain the scenario in detail.
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?

IDOC reprocessing including conversion rules

with BD87 you can reprocess a IDOC, which was not properly processed because of any reasons.
For me it looks like that using BD87 conversion rules maintained for the IDOC message type are not reprocessed again. Is there any way to force the system to include the processing of conversion rules in the reprocess step.
Thanks for any help
Marita

Hi Marita,
Have you tried with the application RBDMANI2
Shylesh

INBOUND IDOC REPROCESSING IN CUSTOM PROGRAM

Hello,
I have a custom program which displays the INBOUND IDoc data for the message type = ZSTLSP in the ALV format.
Requiremt is that I shall select a record and change one of the coulmn contents . A button 'Reprocess' will be
made available , when clicked it needs to reprocess the Idoc . The reprocessed idoc will be strored with the new values entered
and the original idoc will be stored with status 70.
Kindly let me know how to reporcess the IDoc in the custom program.
Note that If I try to cakk l standard program RBDAPP01 to reprocess the IDOCs using SUBMIT statement. We can pass the IDOC Number, Message type etc. while submitting the program but CANNNT pass the changed SDATA field.
Thanks in Advance!!
Senthil

I am able to change the value using FM IDOC_INPUT , but the changed values is not updateing in the databse.
Maybe I need to do commit. kindly let me know how to do commit in this scenario.
Senthil

Regarding errpr idoc reprocess

Hi Experts,
    Currently iam working on inbound idoc 'ORDERS04'.
    For background process we have the sap standard program 'RBDAPP01'.
how can i achive the following requirement.i have created one custom table for this req with idoc number,PO number and Status.
     Check on the table to see idoc program is running
     If idoc program is running, exit
     Else set the table and call the idoc program to process new and re-process error idocs
     When the idoc program is done and control is back to the control program, clear the status in the table and exit
Rgds,
Krishna.

Hi Balakrishna,
All the inbound Idocs will be updated in the tables EDIDC,EDID4,EDIDS at first.
So, create internal table for any of the above tables and dont forget to select the fields time and date.
Capture all the Idocs created at that time. Now, for these Idocs you need to check whether the
background job has processed them or not. Is that correct?
So, to check whether the background job which runs RBDAPP01 program is running or not you can do manipulations on the table TBTCO. This table will have the status whether the job is running or not.
If not, you can schedule a job by inserting an entry in the table TBTCS or you can also call the job by using JOB_OPEN FM
Hope you got the clue how to do that. I think you can avoid the custom table to achieve this.
Thanks,
Babu Kilari

Tracking IDOC reprocessing

Similar Messages

Maybe you are looking for