Integrations
What a plant connects to a manufacturing ERP, and how each connection works here: CAD and PLM, EDI, accounting, scanners, machines, carriers and e-commerce.
These are the connections to scope when configuring Manufacturing ERP. Each integration needs an agreed document mapping, its own identity and acceptance checks against the configured application’s API.
- Engineering
- CAD and PLMin
- Customers and suppliers
- EDIPurchaseOrders, MatchExceptions · in
- Supplier portalSuppliers, Certificates · in and out
- E-commerce and marketplacesSalesOrders · back
- The floor
- Barcode and RFIDin and out
- Machines and sensorsin
- Labelsout
- Money
- Accountingout
- Bankingin and out
- Taxout
- Shipping
- Carriersback
- Agents
- Your agentWorks within the permissions you assign
Engineering
- CAD and PLM. Items, bills and revisions are imported from the design system; the engineering change process here approves and applies them. The design system stays the master for geometry; the ERP is the master for what is planned and built.
Customers and suppliers
- EDI. Map purchase orders, acknowledgements, advance ship notices and invoices in the trading partner’s required format. Transport or mapping failures belong in the integration’s error queue; MatchExceptions is reserved for differences found during invoice matching.
- Supplier portal. Suppliers acknowledge orders, update dates and attach certificates without EDI.
- E-commerce and marketplaces. Orders arrive as sales orders with the channel as a dimension; stock availability is published back.
Approval conditions
The assigned Approver reviews submitted requisitions and POs, records the decision in Approvals, and approves the purchase (Status: Submitted → Approved).
- PO-55389 VND-020 8 d
- PO-89371 VND-208 9 d
- PO-68571 VND-238 8 d
- PO-24669 VND-207 3 d
- PO-82651 VND-231 4 d
- Vendor
- VND-020
- OrderDate
- 09 Sep
- RequiredDate
- 15 Sep
- TotalAmount
- 9,911.53
- Buyer
- TL
Approval waits for the approver.
The floor
- Barcode and RFID. Receipts, issues, completions and counts are scanned. A scan is a movement with the same reference as a keyed one.
- Machines and sensors. Counters and states from machines feed production logs and downtime, which is where OEE comes from.
- Labels. Lot, serial and shipping labels are generated from the record and printed at the station.
- 10 · Cut to lengthWC-12017 Sep → 25 SepPending
- 80 · Weld frameWC-11012 Sep → 21 SepInProgress
- 40 · Drill and tapWC-11017 Sep → 20 SepPending
- 70 · DeburrWC-13015 Sep → 24 SepInProgress
- 50 · AssembleWC-12017 Sep → 22 SepPending
Money
- Accounting. The ledger is included. If the group consolidates elsewhere, journals are exported by period to the group ledger.
- Banking. Statements in for reconciliation; payment files out for the payment run.
- Tax. Rates by jurisdiction; filings exported.
Approval conditions
Visible to: Accountant. Visibility does not establish approval authority.
- JE-33179 Issue to WIP 14 d
- JE-30548 Completion at standard 4 d
- JE-69432 Goods receipt 12 d
- JE-11285 Scrap 10 d
- JE-29785 Bill match 14 d
- Date
- 03 Sep
- Description
- Issue to WIP
- TotalDebit
- 11,718.45
- TotalCredit
- 11,718.45
- ReferenceType
- StockMovement
Approval conditions.
Shipping
- Carriers. Rates, labels and tracking from the delivery record; proof of delivery back onto it.
How connections are governed
service accounts, audit, pausingGive each integration a service account with a scoped role and an audit trail. Agree its retry policy and duplicate detection before enabling writes. Rehearse a failed message and a replay, verify that the operator can inspect the error, and confirm that pausing the connection leaves existing records usable.
The API is one more client of the same interface. Agent and API →