Order Base in OTM represents the total amount of product ordered.Its a requirement for movement of goods from one location to another location.
Order Base can be created in OTM in two ways
If inbound order base and order release XML integrations does not have ReleaseMethodGid element, then OTM will default the release method to SHIP_UNIT_LINES for orders with ship units and ONE_TO_ONE for orders with order lines only. These defaults may be changed via the glog.releasemethod.shipunit.default and glog.releasemethod.line.default properties
Constraints
Order Base can be created in OTM in two ways
- Sending TransOrder XML from External Application
- Create Order Bases via OTM UI
Processing Code will be sent only via TransOrder XML interface.
- PLN value indicates planning of shipments happen automatically
- NOPLN value indicates planning of shipments to be done manually
Order Configuration determines how ship units are created on order bases/releases and
how calculations(Weight/Volume) are to be performed when an order is being built
Release instructions decide how many ship units/lines should be released to create order release and can be entered on Order Base Ship Unit or Order Base Line.
Constraints
- Order-level constraints only impact the planning of the primary leg. Leg-level constraints can be used to influence the planning of any other itinerary leg
- If Rate Offering and Itinerary Constraints are entered on Order Base, these entries override the "Active" state of those business objects as well as any effective or expiration dates
- Multiple Orders with same Ship With Group values can be grouped for shipment creation. Orders with different Ship With Group values cannot be grouped together for Shipment Creation.
No comments:
Post a Comment