Description
You should run this report whenever you discover that an evaluation runhas written incorrect data to the tables for some reason. However, you should think very carefully about running this report ifyou have already posted the data to FI. It is recommended that you always execute a test run that will showwhat data will actually be deleted in a productive run. Warning Never undo/delete a run that has a successor within a remittanceprocess. You must undo/delete the last run of a complete remittance runfirst and then undo/delete each of its predecessors. Do not use at anytime the flag to reset the number range when undoing/deleting a runthat exists within a list of runs. You can choose the option to reset the number ranges and the numberrange objects RP_REMIT REM1 (evaluation runs), REM2 (posting runs),REM4 (acknowledgement runs) or RP_REMIT1 (remittance origin link) areset back to where they were before these runs took place. Using theflag 'Reset number ranges' within a list of existing runs can causesevere data inconsistencies (lost links to existing postings) due tothe number range reset. Undo evaluation run Undo posting run Undo acknowledgement run Generic undo Precondition Output |
943691 | MSC: Error with Undo Process in ERP2004 and higher |
836050 | MSC: Performance issues with undo program |
647576 | MSC: Undo failed with wrong error message |
624031 | MSC: Wrong status after undo |
426479 | GEN: Reversing posting runs: incorrect error message |
497365 | GEN: Undo eval. program fails to clear all tables. |
392559 | GEN: Remittance posting documents deleted |
392443 | Third-party remittance: Reversal of posting documents |
302616 | GEN: Undo run option "Reset number range" confusing |