CTR-ERP-MM · version 2
Group ERP — Materials and Inventory — Material movements
Feeds inventory and commitment figures on the supply chain cockpit.
What the contract says
These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.
Review state
Neither review is performed by the team that wrote the contract.
Validation and drift
Drift is only detectable on a contract that has been read against a sample.
The field list
6 fields · 1 key · 0 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.
| Field | Source | Target | Type | Flags | Drift | Validation |
|---|---|---|---|---|---|---|
| Material document | MKPF-MBLNR | movement.documentRef | string(10) | keyinternal | In contract | Ten characters. Must be unique within the fiscal year. |
| Movement type | MSEG-BWART | movement.kind | string(3) | internal | In contract | Must be one of the 41 movement types declared in the mapping table. An unmapped type is rejected, not guessed. |
| Material | MSEG-MATNR | movement.materialRef | string(18) | internal | In contract | Must resolve against the material master already in the spine. |
| Quantity | MSEG-MENGE | movement.quantity | decimal(13,3) | internal | In contract | Signed by movement type. A positive quantity on an issue type is a contract violation. |
| Plant | MSEG-WERKS | movement.siteCode | string(4) | internal | In contract | Must resolve to a site with a declared jurisdiction, because residency depends on it. |
| Posting date | MKPF-BUDAT | movement.postedOn | date | internal | In contract | Inside the extract window or the batch is replayed. |
What has passed the staging boundary against this contract
1 batch · 8,140 arrived · 7,962 admitted · 46 quarantined · 132 rejected
| Batch | Arrived | In | Admitted | Quarantined | Rejected | Result | Gate |
|---|---|---|---|---|---|---|---|
| STG-0003 | Aug 18, 06:00 | 8,140 | 7,962 | 46 | 132 | Partly admitted | 7,962 admitted · 46 quarantined · 132 rejected outright. |
Rejects raised against these batches
2 reasons covering 178 records. Each one names a field, what was observed and what the contract expected.
Replay windows
1 window recorded against this contract.
Write-back routes into this system
1 route designed against Group ERP — Materials and Inventory.
What goes stale when this feed does
2 asserted figures depend on Group ERP — Materials and Inventory. The rule on each row is what the surface does when the feed misses its commitment.
| Figure | Where it is shown | Role | On stale | Note |
|---|---|---|---|---|
| Open purchase order commitment | Reconciliation ledger REC-02 | primary | Suppress the figure | Commitment is a materials-ledger balance. There is no second source for it. |
| Active supplier records | Procurement cockpit | contributing | Mark it stale | Purchasing organization assignment comes from the materials side. |
A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.
The last validation read 12,000 records 18 days ago, which is 13% of a single day at the declared volume. A sample proves the shape of what it read and nothing beyond it.