Solution : https://service.sap.com/sap/support/notes/308863 (SAP Service marketplace login required)
Summary :
In SAP systems, garnishment remittances may fail during a posting run if the garnishment record is modified rather than properly delimited as required for specific changes. This mismanagement often prevents data from being transferred to Financial Accounting (FI). The root cause is the system's allowance for modifications to garnishment master data before the remittance process concludes. SAP proposes implementing a remittance posting status to monitor such changes. It's recommended to integrate specific messages into message class '5U' to guide the remittance process and prevent such issues as outlined in the detailed procedures within the solution notes.
Key words :
rpurmp00]remittance posting run[/] garnishment remittance [ds, rpurmp00]remittance posting run[/] garnishment remittance [ds, additional key words garnishment remittance, rpurmu00]store evaluation run[/] [ds, rpurmu00]store evaluation run[/] [ds, rpurmp00]remittance posting run[/], remittance posting run, store evaluation run, garnishment remittance [ds, remittance posting status
Related Notes :
| 532744 | Q&A: Master Note for U.S. Third-Party Remittance |
| 521751 | Q&A: Master Note for Canadian Third-Party Remittance |
| 371119 | ITY2001: Remittance Rule not being validated |
| 371113 | GRN: When updating vendor on IT 66, program aborts. |
| 371099 | ITY2001: When updating vendor on IT 194, program aborts. |
| 121138 | FAQ: Third-Party Remittance |