When business requirements necessitate additional validation for delivery creation—beyond standard schedule line confirmations and stock availability—you should implement custom logic within user exit EXIT_SAPLV50P_001 . This exit allows you to intercept the delivery creation process for specific sales order items and enforce unique parameters or business constraints before the document is generated. Technical Summary & Context In standard SAP, the delivery creation process primarily looks at the Material Availability Date and the Confirmed Quantity at the schedule line level. However, many organizations require "smarter" logic. Key Scenarios for EXIT_SAPLV50P_001: Credit/Block Checks: Preventing delivery if the customer has specific financial standing issues not caught by standard credit management. Item Grouping: Ensuring that Item B is never delivered unless Item A is also fully available Custom Attribute Validation: Checking custom fields (Z-fields) in the Sales...
When business requirements dictate that shipment status or date calculations must bypass standard SAP protocols in favor of custom business rules, you should utilize the functional exit EXIT_SAPLV56F_011 . This exit provides the necessary hook to intercept shipment processing and inject your own logic to manipulate header or stage data before the document is finalized. Some of the sample requirements : Stage Level: Automatically update the shipment 'Planning' start and end dates at the stage level based on new delivery dates. Header Level: Once the shipment end date for the final stage is determined, that value must propagate to and update the shipment header.