IDoc : Change Pointers and Reprocessing IDocs – Helpful Exchanges
Going back over Fruitful IDocs once more
Utilizing BD87, we can’t re-process effective IDocs once more, yet here and there specific issues might expect us to re-send a generally handled fruitful 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 )
This one is additionally very supportive in the creation climate. At times we can have situations where a great deal of progress pointers gets made because of some mistaken setup or settings. To eliminate them from the framework and clear up the related tables, this t-code is very useful.
Additionally, in the event that the quantity of IDocs that should have been retransmitted is restricted, you can retransmit them from the concerned application like Shipment, Conveyance, and Buy Request by Going back over the Result Type.
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.
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
Just a key and two clicks for ALV consistency check
Message Processing and Transformation in SAP PO
WhatsApp us