Supported documents
| Document | Direction | What it does in the ERP |
|---|---|---|
| 830 Planning schedule | In | Replaces the releases from the previous 830 for each part; firm and forecast are kept apart. |
| 862 Shipping schedule | In | Replaces the firm releases from the previous 862 for each part. |
| 850 Purchase order | In | Creates a blanket or spot sales order, and queues an 855 if the customer wants one. |
| 860 PO change | In | Adds or cancels lines, and changes quantity, price or date. |
| 855 PO acknowledgment | Out | Accepts the purchase order. |
| 856 Ship notice (ASN) | Out | Ship, order and item levels, with each container's label serial. |
| 810 Invoice | Out | One line per shipped part at the order price. |
| 997 Acknowledgment | Both | Sent for every inbound group; inbound 997s mark your documents accepted or rejected. |
How EDI flows through the plant
- Releases from an 830 or 862 go onto the customer's open blanket order for the part, or a new one.
- Jobs, MRP and the schedule plan production against those releases.
- Packed containers get 4 x 6 inch labels with serials; shipping scans them and fills releases oldest-due first.
- The 856 and 810 go out from the shipment you scanned, so the paperwork matches the truck.
Connections
- Upload or paste a file from a customer portal or email.
- Post files to the REST API from a translator, VAN or AS2 gateway.
- Exchange files with VAN mailboxes over SFTP, FTPS or FTP.
Setting up a trading partner
- Enter your ISA qualifier and ID in the EDI settings.
- Mark the customer as an EDI trading partner and enter their qualifier and ID.
- Set each part's customer part number.
- Set each ship-to's EDI location code.
When a document has a problem
Each transaction set is applied in its own database transaction, so it is applied fully or not at all. If a document fails (an unknown part, an unknown PO, a bad date), its 997 rejects it and the reason is logged.