Solution : https://service.sap.com/sap/support/notes/22577 (Connexion à SAP Service Marketplace requise)
Résumé :
SAP Note elucidates an issue where simultaneously releasing a marked cost estimate (CK21) and executing a cost estimate (CK11, CK64, or SAPRCK10) with identical overhead keys can lead to database inconsistencies. Specifically, material master's valuation segment shows a released standard price without a matching cost record in the database. This can subsequently trigger CK162 error indicating non-existence of the current cost estimate. The root cause is identified as insufficient transaction blocking by CK-record releasing transactions. The error resolution involves updating the ENQUEUE_ECKEKOE module in the CK_F_MBEW_KEKO_COLLECT function to effectively block concurrent transactions, applicable from SAP releases 2.2F and 3.0A onward, and inserting specific code lines indicated by P22K005536. For earlier release versions, data inconsistencies might be corrected using the SAPRKEKO report configured with logical database MSM.
Mots Clés :
additional key words future planned price, error message ck162, prerequisites transaction ck21, blocking module enqueue_eckekoe, function module ck_f_mbew_keko_collect, report saprkeko added, logical database msm, attributes enter 'ms', found - inconsistent data, block simultaneous costing
Notes associées :
| 134955 | Collective note: error message CK162 or CK214 |
| 101422 | Blocking problem for release of stnd. cost estimate |
| 62574 | Material recosted, despite released cost estimate |