Description:
ELMS does not currently fully support the DLMS Mark-for Party when generating, modifying, or processing requisitions. Without full Mark-for support, ELMS may not consistently identify the intended end recipient within the ship-to location. This can create gaps in requisition processing, delivery routing, shipment documentation, supply and shipment status visibility, and downstream receipt processing.
Recommended:
ELMS should implement end-to-end support for the DLMS Mark-for Party across the requisition lifecycle. The solution should capture, validate, store, display, and perpetuate Mark-for information when it is provided, ensuring it remains separate from the ship-to address while identifying the intended recipient or destination within the ship-to location. This support should include applicable DLMS transactions such as 511R, 511M, 869F, 869A, 870S, 856S, 940R, 945A, and 527D where required. The full Mark For should also be included in the printing of the DD Form 1348.
Mission Critical:
Ensures ELMS is compliant with DOW policy.
Benefits:
Supports Mark For which is required for shipping sensitive items.
Frequency:
Daily
Users:
All users who use the Mark For
Disclaimer | Accessibility