Fusion order management, pricing, and procurement mapped to D365 trade

How Fusion's Distributed Order Orchestration, Pricing Administration, and procurement objects — blanket purchase agreements, contract purchase agreements, and order management — map to D365's sales order lifecycle, trade agreements, purchase agreements, and the fundamental difference that Fusion DOO has no direct D365 equivalent and must be retired and rebuilt.

What you will be able to do

• Explain why Fusion's Distributed Order Orchestration has no D365 equivalent and describe what compensating design is needed
• Map Fusion Pricing Administration constructs to D365 trade agreements
• Translate Fusion blanket and contract purchase agreements to D365 purchase agreements and release orders
• Identify the TCA customer account unbundling steps that the trade migration depends on

Introduction

Fusion's order-management and trade landscape is dominated by one capability that has no equivalent in D365: Distributed Order Orchestration (DOO). DOO is a rule-driven engine that manages fulfilment sequences — back-order handling, conditional sourcing, order-split logic, substitution rules — as configurable orchestration processes.

Distributed Order Orchestration: the headline difference

Fusion DOO manages the post-booking lifecycle of a sales order through configurable orchestration processes. An orchestration process is a sequence of steps with conditional branching:

Pricing Administration

Price lists — item or item-category prices with effective-date ranges, currencies, and UOM specifications. Pricing strategies — link a price list and discount list to a pricing segment (customer group). Pricing algorithms — formulas that compute price from attributes such as customer spend, item weight, or custom scoring models.

Procurement: agreements, requisitions, and purchase orders

Blanket Purchase Agreement (BPA) — commits to a maximum quantity or value per item over a period. Release orders are raised against the BPA to consume the committed amount. Contract Purchase Agreement (CPA) — defines a contractual spend commitment, potentially without specific item quantities.

Supplier and customer master

Fusion's TCA (Trading Community Architecture) model — Party → Customer Account → Account Site — must be unbundled into D365's per-legal-entity customer and vendor records (see the Organisation Modelling module for the full TCA unbundling treatment).

Intercompany trade and charges

Intercompany trade in Fusion is configured between Legal Entities via intercompany relationships and sourcing rules. A sales order in one Legal Entity triggers a corresponding supply chain action (internal transfer or intercompany purchase) in another.

Knowledge check

Summary

Fusion's trade domain translates to D365 with two notable design gaps: DOO orchestration (no equivalent engine) and algorithm-based pricing (no equivalent formula engine).