IDoc Tips—Change Pointers and Reprocessing IDocs
IDoc reprocessing in SAP IDoc: Reprocessing IDocs and Change Pointers—Valuable Exchanges
Reviewing the Fruitful IDocs again
We are unable to reprocess successful IDocs using BD87, but occasionally, particular problems may require us to resend a usually handled, successful IDoc.
BD21 – Making IDoc Types from Change Pointers (Change Pointers and Reprocessing IDocs )
At times a great deal of Progress Pointer gets made, yet neglects to get handled because of framework issues.
This t-code is very useful to create IDocs from natural change pointers. The situation with change pointer can undoubtedly be checked from BDCPV table/view.
BD22 – Erase Change Pointers (Change Pointers and Reprocessing IDocs )
In the creation climate, this one is also quite helpful. We occasionally encounter circumstances where a significant number of progress indicators are generated due to incorrect configuration or settings. This t-code is really helpful to remove them from the framework and clean up the associated data.
Additionally, you can retransmit documents from the relevant application, such as Shipment, Conveyance, and Buy Request, by going back over the Result Type if the number of documents that need to be retransmitted is limited.
Be that as it may, when we really want to send different IDocs, utilizing the standard program RC1_IDOC_SET_STATUS is very useful.
You can go to WE02 or WE09, duplicate all the handled IDoc numbers and glue them in the wake of executing this program in SE38. You would likewise have to indicate the new IDoc status.
On the off chance that you really want to handle this IDoc again utilizing BD87, you can’t straightforwardly set something very similar to 30 (IDoc prepared for dispatch), as BD87 recalls the last status (which was ’53’- Application archive posted) and consequently wouldn’t again deal with this IDoc.
Consequently we can change the status to say some transitional one like 32 – (IDoc was altered) and afterward again run this program and change the status t0 30 from 32.
How to find BADIs?
From that point forward, we can again deal with this IDocs utilizing BD87 and yet again send them to the outer framework like EDI.
YOU MAY BE INTERESTED IN