Map the SYSPRO order estate — sales orders, blanket orders with releases, purchase orders and the RMA and return-to-supplier processes — into D365 order, agreement and return structures, and reconstruct the open book at cutover.
Trade is the domain where the migration becomes visible to people outside the company. Finance failures are internal. Manufacturing failures are internal for a while. An order that cannot be shipped, a price that is wrong, a credit that does not appear — those are customer conversations on day one.
The sales order structure maps directly. SalesTable carries the header, SalesLine carries the lines, and the concept mapping rates the correspondence high confidence.
SYSPRO's blanket sales orders with releases become sales agreements with release orders, held in SalesAgreementHeader and SalesAgreementLine. The concept mapping rates this a composite construct, and the reshape is worth understanding rather than treating as a naming change.
Purchase orders map directly into PurchTable and PurchLine, rated high confidence, with two named validation items.
Returns are the domain's most interesting mapping, because the target ties together three decisions the source may separate.
The order structures are containers; the reference data is where trading behaviour actually lives. The migration inventory for this domain includes:
The playbook places open purchase orders, open sales orders and blanket releases in wave five, alongside on-hand and lots, gated on inventory and order reconciliation.
The customisation register lists the SYSPRO Supply Chain Portal alongside the tax and document connectors as an ISV or partner-solution triage item, and the associated gap notes that the target architecture for portal and connector capability is undecided with low confidence.
Trade maps well structurally and takes its time in the behaviour attached to the structures.