MK Order-to-Packing Composition Baseline¶
- Evidence date:
2026-07-17 - Evidence class: source reconstruction; no runtime, API, DB, browser, provider, production or deployment action
- Scope: current Client-2 OMS/TMS/YMS/BMS ownership split for the MK composite process
Composite Boundary¶
PROC-OMS-ORDER-TO-PACKING-MK is the stable cross-process identity, not a second atomic owner. It reconciles child outcomes for purchase/sales work and one-step Export Brokerage. Order Schedule is an Inbound/Outbound projection, Doortrade reuses Inbound, and purchase-inbound finalization remains within the Inbound owner while Scale owns physical ticket state.
Atomic Owners¶
| Owner | Current authority |
|---|---|
| Commercial Order | Purchase/sales agreements: T_COMMERCIAL_ORDER* |
| Inbound Purchase to Inventory | inbound header/item, receipt result, T_LOAD*, T_TRANSLOAD, T_INVENTORY_LOT |
| Export Brokerage | child orchestration and compensating cancel; no dedicated business table |
| Outbound Sales / Allocation | outbound T_LOAD* lifecycle and lot balance consumption |
| Booking / Packing | booking/container lifecycle and current packing/invoice projection/print |
| Packing Rate / Outbound Cost | outbound item rate correction and outbound-linked AP cost |
| Scale / Trade / Output children | physical ticket state, derived trade reconciliation, conditional invoice/confirmation/weight-ticket projections |
Source Boundaries Observed¶
- Commercial routes enforce same-tenant opposite-agreement linkage and reject unsafe type/item replacement or delete after linked execution.
- Inbound routes own order/item CRUD and no-scale completion; the helper creates receipt state and rejects delete after scale, transload, lot, allocation or ledger progress.
- Export routes orchestrate child owners and compensating cancel; generated records retain child data authority.
- Booking helper owns booking writes; outbound helper owns item/allocation writes and cost helper owns cost writes.
- Packing render is server-side and does not use generic packing file APIs. Scale check-out and inbound finalization remain separate recovery boundaries.
Constraints And Unknowns¶
- Scale applies only to physical yard work; document outputs are conditional and have no durable print-completion state.
- No transaction, stored status, lock or rollback spans all children. A child result must be reread before retrying only that child boundary.
- Commercial transitions, inbound/scale/lot unified state, allocation reversal, booking state, output acknowledgement, scale policy, generic ticket isolation and field-role coverage were not proven by this source reconstruction.
- Legacy MK material is business-intent evidence only and does not establish current API/data authority.
---¶
Source:
docs/research/mk/2026-07-17/MK_ORDER_TO_PACKING_COMPOSITION_BASELINE.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.