Solution : https://service.sap.com/sap/support/notes/538423 (SAP Service marketplace login required)
Summary :
The SAP Note addresses an issue where the ZZ_PEGKEY_DELETE report fails to delete corresponding planning areas in the liveCache after deleting entries from the /SAPAPO/PEGKEY table, causing inconsistencies visible in transaction /sapapo/om17. This defect is due to a problem in the report's code up to Version 14 as detailed in note 390151. The solution recommended is to update the report's source code as per the correction instructions given in the latest version of the same note, including updating to text symbol 004 to resolve the inconsistency.
Key words :
terms peg area, correction instructions contained, /sapapo/pegkey table, note 390151 deletes entries, transaction /sapapo/om17, /sapapo/om17, zz_pegkey_delete report, planning areas, pegging areas, database reason
Related Notes :
| 607311 | ZZ_PEGKEY_DELETE: Pegareas for matrix demands are deleted |
| 575958 | Composite SAP note: Avoiding data inconsistencies in APO |
| 524602 | /SAPAPO/PEGKEY_REORG: Pegareas are only deleted on DB |
| 390151 |