Solution : https://service.sap.com/sap/support/notes/524919 (SAP Service marketplace login required)
Summary :
When transferring sales orders from R/3 to APO, deadlocks may occur, signaled by SQL error 60 impacting the /SAPAPO/PEGKEY table. This issue arises particularly during backorder processing (BOP) when simultaneous alterations to the planning file entries for PPDS or SNP and changes to order data occur. This has been identified as a program error. The recommended solution is a program correction to resolve these deadlocks by managing how data conflicts are handled during concurrent data transfers and processing.
Key words :
sql error 60 table /sapapo/pegkey, changed sales order data, solution implement program correction, table /sapapo/pegkey, /sapapo/dm_changed_pegid_flush reason, planning file entries, planning file entry, /sapapo/pegkey, program error, sales orders