Solution : https://service.sap.com/sap/support/notes/1027907 (SAP Service marketplace login required)
Summary :
When utilizing BADI_SCD_SAVE with the AT_SAVE method for saving shipment cost documents, an issue arises during the use of mass processing transactions V104, V105, V106, or V107. These transactions update the shipment cost document status despite the 'NO_SAVE' exception being activated. This issue does not occur with manual processing via transactions V101 or V102. Additionally, using automatic processing level 'D' generates a service entry sheet relevant to settlement but does not update the status STABR. The underlying cause is identified as a program error, corrected by implementing changes from the Support Packages for releases 4.70, 5.00, and 6.00.
Key words :
call transaction se37 'function builder, - transfer shipment cost item' level, mass processing transactions v104, shipment cost document, prepare specific objects, service entry sheet, attached correction instructions, 'sd_scds_save' function module, function module, shipment costs
Related Notes :
| 1224859 | Dump in BADI_SCD_SAVE when exception NO_SAVE is triggered |
| 896098 | VI12: Shipment cost document created twice |
| 746612 | INFO: => LE-TRA-FC-PRO (processing/dialog) |
| 746604 | INFORMATION: => LE-TRA-FC-CP (collective processing) |