User Exits Part 5: MV50AFZ1 — Delivery User Exit Patterns

📌 KEY POINTS
✅ MV50AFZ1 contains the delivery exits of SAPMV50A: USEREXIT_SAVE_DOCUMENT_PREPARE and USEREXIT_SAVE_DOCUMENT are the most used.
✅ Data: LIKP (header), XLIPS/YLIPS (items new/old with UPDKZ), XVBPA (partners), XVBFA (document flow).
✅ Deliveries are often created in background (VL10 collective processing) and via IDocs — exits must not rely on dialog.
⚠️ For many delivery requirements, SAP's classic BAdI LE_SHP_DELIVERY_PROC offers cleaner methods — check it first.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered sales orders. Deliveries follow the same pattern with different tables and more background processing.

━━━━━━━━━━━━━━━━━━━━
▶ 1. KEY FORMS

• USEREXIT_SAVE_DOCUMENT_PREPARE — checks and final changes before save (e.g. block delivery, set a Z field, validate batches).
• USEREXIT_SAVE_DOCUMENT — during save; write own tables via update task.
• USEREXIT_MOVE_FIELD_TO_LIKP / _LIPS — fill header/item fields during creation (these FORMs are in MV50AFZ1 / related includes depending on release).

━━━━━━━━━━━━━━━━━━━━
▶ 2. ITEMS AND BATCH SPLIT

• XLIPS contains main items and batch split sub-items (UECHA = higher-level item).
• For quantity checks use the main item or sum the split items — not both.
• Skip deleted items (UPDKZ = 'D').

━━━━━━━━━━━━━━━━━━━━
▶ 3. BACKGROUND AND INTERFACES

• VL10 creates many deliveries in one run; the exit runs per delivery.
• An error message in SAVE_DOCUMENT_PREPARE prevents that delivery from being created and appears in the collective processing log.
• No popups; buffer lookups (Part 8).\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 4. LE_SHP_DELIVERY_PROC (CLASSIC BADI)\nMethods such as CHANGE_DELIVERY_HEADER, CHANGE_DELIVERY_ITEM, SAVE_DOCUMENT_PREPARE, SAVE_AND_PUBLISH_DOCUMENT and CHECK_ITEM_DELETION give parameter-based access. Prefer it for new requirements where it offers the needed point.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TYPICAL REQUIREMENTS

• Block deliveries for customers with a Z flag (set LIKP-LIFSK or raise error).
• Fill a Z field in LIKP from the sales order (via XVBFA/VBAK read).
• Validate that batches are assigned before PGI (better: incompletion/checks in customizing where possible).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. SE38: display MV50AFZ1 and read the FORM comments.
2. Debug VL02N save; inspect LIKP, XLIPS (with batch split) and UPDKZ.
3. Implement the batch check from the code example in a sandbox and test via VL10.

✅ CHECKPOINT: you can implement delivery checks that work online, in VL10 and for IDocs.

A batch check in the delivery exit rejected valid deliveries in VL10 runs. The code checked all XLIPS entries, including batch split sub-items whose main item had no batch by design.
Restricting the check to main items (UECHA initial) and looking for sub-items fixed it. The collective processing log now showed only real errors, and the warehouse stopped bypassing the check manually.

• Treating batch split sub-items as separate items.
• Popups or dialog-only logic in delivery exits.
• Ignoring deleted items.
• Changing LIKP/XLIPS in SAVE_DOCUMENT (too late).
• Not considering LE_SHP_DELIVERY_PROC for new logic.

• Guard by delivery type.
• Handle main items and split items deliberately.
• Test online, VL10 and IDoc creation.
• Own tables via update task.
• Prefer LE_SHP_DELIVERY_PROC where suitable.

Questions: "Which user exit do you use for delivery checks?", "What are XLIPS and UECHA?", "LE_SHP_DELIVERY_PROC?"
Strong answer: MV50AFZ1 USEREXIT_SAVE_DOCUMENT_PREPARE for checks/changes with LIKP and XLIPS/YLIPS (UPDKZ), SAVE_DOCUMENT for own tables via update task; batch split items have UECHA; exits run in VL10/IDoc without dialog; classic BAdI LE_SHP_DELIVERY_PROC offers parameter-based methods and is often preferable.