Invalid data
Wrong units, out-of-site locations, held lots and duplicate source IDs require explicit outcomes.
TRUSTED FACTORYFLOW
Receive demand, map data and return outcomes through reconcilable transactions.
| Data | Owner by deployment | Exchange outcome |
|---|---|---|
| PO / ASN / SO | Selected ERP or ordering system | Retain source ID/revision, receipt state and processed quantities. |
| Production / work order | MES | Retain operation and BOM/recipe references and return identified consumption/results. |
| Stock / reservation | FactoryFlow WMS or existing WMS | One ledger; execution evidence is checked before transaction posting. |
| Execution / mission | WCS / Fleet | Retain task/execution/mission mapping; ACK is not ERP confirmation. |
Agree item codes, UOM, lot/serial, site/warehouse/location, timestamps and enums. Unit conversion uses an approved map; quarantine invalid lines and retain permitted payloads for investigation. Mapping changes need revision, compatibility tests and a replay plan.
Deduplicate source transactions using agreed identifiers and scope. On API timeout query the outcome before replacement transactions. On ERP/WMS differences compare documents, quantities and revisions; ledger owners decide adjustments, not adapters.
Wrong units, out-of-site locations, held lots and duplicate source IDs require explicit outcomes.
Test lost responses, late callbacks, consumer lag and replay and verify one ledger effect.
Trace one source order to task, execution, mission and confirmation records in both systems.