SAP Logistics

Issue  System is not creating outbound delivery orders due to the error message /SCWM/DELIVERY_CONF050 ODO split is not supported in combination with TU assignment even though no TU relevancy exist for this document type Resolution Check if the PDO doctype has the flag 'Outbound SPlit' = 'O - ODO split'.  The ODO split is not allowed with TUs.  If you use TU please change the flag 'Outbound SPlit' to Default Logic.  If you don't use TUs please deactivate the DTU status. 

 At times, there will be a requirement where business want to block the delivery as soon as delivery is created based on certain parameters. As standard system doesnt block the delivery after the delivery creation to accomplish this requirement, custom logic need to be built.  From technical standpoint, Program 'MV50AFZ1' and User exit 'USEREXIT_MOVE_FIELD_TO_LIKP' need to be leveraged in this situation to accomplish this requirement

At times, business requires to determine storage location through various parameters apart from the standard configuration setup. In this situation, as we cannot accomplish this requirement through standard SAP functionality so we need to leverage customer exit 'EXIT_SAPLV02V_002' to accomplish this. In parallel, from technical level we can achieve the same through BADI 'LE_SHP_DELIVERY_PROC~FILL_DELIVERY_ITEM' to accomplish this requirement.

When SAP performs an ATP check, it follows standard rules (checking groups, checking sections, etc.). However, businesses often have "special sauce" requirements that the standard configuration can't handle.  In that situation, Exit 'EXIT_SAPLATPC_002' need to be leveraged to accomplish the custom requirement to build custom rules.

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.