When Posting Goods Issue from Outbound Delivery via "Post Goods Issue" (VL01N) the BADI FIN_CODING_BLOCK_SUBSTITUTION does not contain the accountingdocexternalreference filled with the Delivery number. Using app "Manage Outbound Deliveries" (app ID F0867A) accountingdocexternalreference is filled with the Delivery number.
S/4 HANA Cloud
The delivery document number is only available after the delivery has been saved to the database. Hence, it is not possible to provide the delivery document number in the Cloud BAdI BADI FIN_CODING_BLOCK_SUBSTITUTION in case it is processed in the context of delivery creation. This also includes posting the goods issue during delivery creation.
Workaround if using FIN_CODING_BLOCK_SUBSTITUTION in relation accountingdocexternalreference for the delivery note number is to save the delivery document first and then post it in two steps:
- Create Outbound Delivery (App ID VL01N)
- Change Outbound Delivery (App ID VL02N) - [Post Goods Issue]
- You can also use Manage Outbound Deliveries (App ID F0867A)
FIN_CODING_BLOCK_SUBSTITUTION, SUBSTITUTION, VL02N, ACCOUNTINGDOCEXTERNALREFERENCE, FINS_COBL_HEADER_IN, COBL-XBLNR, MKPF-XBLNR, AC_DOCUMENT_CREATE, MKPF-XBLNR, BADI, custom fields and Logic , KBA , FI-SL-VSR , Validation, Substitution and Rules , LE-SHP , Shipping , LE-SHP-GI , Goods Issue , Problem