Skip to content

Scale And Weight — Current Source Reconciliation

  • Status: SOURCE_RECONCILED WITH TARGET POLICY BLOCKERS
  • Parent Task: NS0-003
  • Reviewed source revision: qa/master@1529bce22ae39c7c2c11e1b9b07e457e1e4c4355
  • Profiles: ctc-execution, mk-order
  • Restriction delta: RD-000 / NONE
  • Effects: documentation/catalog only

1. Authority Result

Current source supports the following narrow authority statement:

T_SCALE_TICKET
= current accepted gross/tare ticket evidence

T_SCALE_TICKET_EVENT
= selected correction/void/reversal event adapter
  when the expected schema is present

Scale is independent from the business processes that consume accepted weight.

Scale Ticket saved
!= Material Receipt confirmed
!= Inventory Lot materialized
!= Allocation applied
!= Transload completed
!= Shipment dispatched
!= Settlement calculated

2. Current Source Family

app/systems/BMS/scale-ticket/**
app/systems/OMS/inbound-order/purchase_execution_helper.php
app/systems/TMS/transload/**
app/systems/WMS/inventory/**
current Scale Portal and closing surfaces

Current compatibility links include:

T_TRANSLOAD.SCALE_TICKET_ID
T_LOAD.TICKET_NUMBER and related scale fields
T_EQUIPMENT_LOAD.SCALE_TICKET_ID
delivery/Yard Closing scale handoffs

A compatibility link does not transfer Scale authority to Transload, Inventory, Delivery or Equipment.

3. Measurement Dimensions

The target must preserve distinct dimensions:

gross axle readings
tare axle readings
gross total
tare total
net weight
commodity quantity
allocation weight
UOM
precision / rounding
device/manual provenance
operator/time/location provenance

No universal conversion between quantity and weight is approved.

4. Current Correction Evidence

Current source contains reason-bearing correction, void and reversal event paths for selected stages. This does not prove:

  • live T_SCALE_TICKET_EVENT schema in every environment;
  • one complete correction policy;
  • all downstream consumers are reconciled;
  • a void automatically reverses Inventory, Allocation, Delivery or Settlement.

Candidate target command family:

CaptureScaleReading
AcceptScaleTicket
CorrectScaleReading
VoidScaleTicket
ReverseScaleTicket
AllocateAcceptedWeight
ReconcileScaleConsequences

5. Concurrency And Unknown Result

Selected current stage writes use current-row comparison values and conditional update behavior. Runtime isolation/deadlock/retry outcomes were not executed.

Unknown result contract:

missing response
-> reread exact Scale Ticket
-> reread correction event when applicable
-> reread linked business record only as a consumer
-> classify committed / missing / conflicting / partial
-> retry only the missing owner command

6. Target Ownership

Target scale owns:

WeighSession
ScaleReading
ScaleTicket
ScaleCorrection
ScaleVoid
WeightAllocation

It must not own:

Inventory ownership
Commercial price
Shipment delivery
Container return
Settlement completion

7. CTC / MK Variation

Concern CTC MK Type
scale use conditional/core in selected operations conditional receipt/outbound policy
device/manual current mixed adapters current mixed/Office paths provenance fact
capture actor field/office varies Office common typed policy
accepted weight consumer service/execution/custody receipt/inventory/allocation explicit command/link

8. Open Decisions

  • accepted gross/tare/net precision and rounding;
  • UOM and conversion registry;
  • scale ticket lifecycle and terminal states;
  • reweigh versus correction versus reversal;
  • downstream consequence reconciliation;
  • manual/device authority and offline capture;
  • timezone and timestamp precision;
  • role/action matrix;
  • duplicate ticket identity and idempotency.

9. Page And Wiki Boundary

No Runtime screen changed in this packet; page test scripts, screenshots, in-app Wiki and page history are NOT_APPLICABLE.

---

Source: new-system/docs/reconstruction/SCALE_WEIGHT_SOURCE_RECONCILED.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.