Solution : https://service.sap.com/sap/support/notes/1002904 (SAP Service marketplace login required)
Summary :
When saving a document, inconsistencies in control tables (TMC2P, TMC2Q, TMC2F) may cause update terminations as described in Note 99507. The issue affects customer-specific update programs (RMCXxxxx) for SAP standard and customer namespace structures (S500 to S999). To detect and resolve these inconsistencies, detailed steps involve analyzing affected update programs through transaction ST22, identifying information structures using SE16, comparing entries in control tables, and verifying table consistency. This note provides guidelines only for customer-specific implementations.
Key words :
transaction 'abap runtime errors', customer-specific update programs, information structure selection criterion, customer-specific rules, transaction code st22, start transaction mc26, stafo/fprog selection, client-specific unlike, customer namespace s500, start transaction se16
Related Notes :
| 99507 | Update terminations after upgrade/client copy |