Solution : https://service.sap.com/sap/support/notes/385830 (SAP Service marketplace login required)
Summary :
SAP Note addresses issues where goods movements aren't fully updated, causing discrepancies such as material documents lacking associated accounting documents. The problem originates from the backend execution through SAP-internal function modules MB_CREATE_GOODS_MOVEMENT and MB_POST_GOODS_MOVEMENT which sometimes, if improperly handled or due to custom non-released third-party enhancements, leads to partial data updates marked for updating. This situation is exacerbated when termination messages (MESSAGE A...) fail to halt erroneous updates, especially when EXCEPTIONS ERROR_MESSAGE is used, trapping the termination messages. Therefore, a program change is mandated to ensure errors trigger an immediate termination (MESSAGE_TYPE_X), a robust approach compared to the previous requirement for the initiator's coding discipline. This change may impact how application logs and IDocs process terminations. SAP emphasizes the misuse of their internal modules by customers voids support, urging adherence to module release statuses in SE37.
Key words :
sap-internal function modules mb_create_goods_movement, additional key words mminkon, global sy fields, important additional information, customer-specific programs, original sap programs, symptom goods movements, idocs'status unchanged, unconditional program ending, marked program parts
Related Notes :
| 1315985 | FAQ: BAdI MB_DOCUMENT_BADI |
| 556000 | Short dump due to note 385830 |
| 442394 | DI: Work In Process (WIP) becomes negative or lower |
| 386152 | MESSAGE_TYPE_X in SAPLMBWL/LMBWLU21/MB_POST_GOODS_MOVEMENT |