How LN's configurable order-type activity chains for sales, purchase, and warehousing orders compare with D365's fixed document lifecycle, and how price/discount matrices, sales and purchase contracts, landed costs, intercompany trade, and payment terms translate between the two platforms.
Sales and purchase order management looks deceptively familiar in D365 to an LN practitioner. Both systems have sales orders, purchase orders, delivery schedules, price lists, and contracts.
An LN order type is a named configuration object that defines the activity chain — the ordered sequence of actions — that a sales, purchase, or warehousing order must follow. The activity chain is built from activity codes, each of which may be optional or mandatory, blocking or non-blocking.
LN organises pricing in price books: tables of list prices keyed by item, customer, currency, quantity break, and effective date. Multiple price books can exist simultaneously for different customer segments, sales channels, or promotional periods. The order type determines which price books are searched and in what sequence.
LN sales contracts are blanket agreements with a customer, committing to deliver a total quantity or value of items over a period. Releases against the contract generate sales orders, which in turn generate warehousing orders for fulfilment.
LN's additional costs functionality attaches freight, insurance, duty, and handling charges to purchase orders and warehousing receipts. Charges can be allocated to receipt lines by quantity, weight, volume, or value. The posting drives landed cost into inventory valuation (for standard cost or MAUC methods) or to expense accounts.
LN intercompany trade between logistic companies of the same enterprise uses a dedicated intercompany order type. An intercompany sales order in the selling company automatically generates a matching intercompany purchase order in the buying company.
LN's trade and order management model is process-rich and configurable. D365's is simpler and more rigid, but extended by workflow and policy. The migration is not about losing capability — it is about redistributing configuration from LN's order-type activity chains to D365's workflow, policies, and agreements.