High- Level Specification

Functional Overview

Outbound Delivery creation will be happened through background job, which will be run periodically to automatically determine the suitable batch. At the time of outbound delivery creation, system will try to allocate the batch based on the predefined rules. 

•  If any one of the line item batches not available during outbound delivery creation then Outbound delivery need to update (LIKP-VLSTK as ““) When the delivery is saved. 
• Once all Line item batches are updated/determine during outbound delivery change then Outbound delivery need to update (LIKP-VLSTK as “A“) When the delivery is saved.

Distribute Outbound Delivery:

Once all the batches have been allocated to outbound delivery, distribute the outbound delivery to EWM (Report: WS_MONITOR_OUTB_DEL_DIST).

Note: the distribution is for the whole outbound delivery, not for the individual delivery item.

Scope and Objectives

Objective
To Implement an automated check during Outbound Delivery processing that inspects all line items. If no item has a batch (LIPS-CHARG is initial for all relevant items), update the delivery header field LIKP-VLSTK to blank (“ ”).

• In scope: Outbound deliveries (document category LF), across all shipping points unless otherwise restricted.
• Out of scope: Inbound deliveries, returns, shipments, stock transport deliveries unless explicitly included.
• Organizational scope: Global unless restricted via customizing.

Assumptions

Dependencies

Security, Integrity and Controls

Configuration Requirements

Language Requirements

Special Requirements

Design Rationale

Functional Requirements

To Implement an automated check during Outbound Delivery processing that inspects all line items. If no item has a batch (LIPS-CHARG is initial for all relevant items), update the delivery header field LIKP-VLSTK to blank (“ ”).

Proposed Technology to Use

1. User Exit (Classic):

   • Include: MV50AFZ1
   • Exit: USEREXIT_SAVE_DOCUMENT_PREPARE
   • Pros: Simple and widely used for delivery save logic.
   • Cons: Procedural; ensure no conflict with other enhancements.

2. BAdI (Preferred Modern):

   • BAdI: LE_SHP_DELIVERY_PROC
   • Method(s): CHANGE_DELIVERY_HEADER or SAVE_DOCUMENT_PREPARE (depending on exact need)
   • Pros: Object-oriented, multiple implementations, filter capability (e.g., shipping point).

3. Implicit enhancement / Exit in SAPMV50A flow:

   • Only if prior options are constrained.

Recommendation: Use LE_SHP_DELIVERY_PROC with method SAVE_DOCUMENT_PREPARE to evaluate items and set header before commit.

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

Volumetrics

Performance Considerations

• Use in-memory item tables where possible.
• Single SELECT for MARA-XCHPF with FOR ALL ENTRIES.
• Early exit as soon as one batch is found.

Error Handling

• Info message (optional):
  • “No batch allocated in any batch-relevant item; header status set to blank.”
• No hard error. Do not block save unless explicitly required.
• Logging: Add to application log (BAL) with object LE and sub object DELIVERY.

Testing

How to Test

1. All items batch-relevant, none with batch:

   • Expect: LIKP-VLSTK = ' ' set on save.

2. Mixed: batch-relevant + non-relevant items; none of the relevant have batch:

   • Expect: LIKP-VLSTK = ' ' set.

3. At least one batch-relevant item has CHARG set:

   • Expect: LIKP-VLSTK unchanged.

4. All items non-batch-relevant:

   • Expect: LIKP-VLSTK unchanged (business can choose to still set blank—confirm).

5. After PGI:

   • Ensure enhancement does not reset the field post-PGI (confirm trigger points).

6. Mass change / background job:

   • Batch job processing should apply same logic.

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Change log