Solutions
EDI for job shops, without the translator
Most small shops do EDI by hand: a release lands in a Web-EDI inbox, someone keys it into the ERP, and when the truck leaves someone keys the ASN back. The cum, the ASN deadline and the label serial are where it goes wrong, and a missed ASN can be a $250 chargeback. STRYKE reads each transaction into the ERP and sends the replies from the Order and the Packing list.
What arrives
The transactions a Tier 1 or an OEM sends, through a VAN, a Web-EDI portal or an emailed file.
- 850 purchase orders and 860 changes against a blanket
- 830 weekly forecasts and 862 daily firm releases, each carrying the last cum received and the last packing slip
- 824 rejections when an ASN fails a check, such as a dock code written 7 instead of 07
- 820 remittances when the customer pays
- The same releases keyed into Plex, Covisint, SupplyWEB or SupplySync, if that is how your customer works today
What STRYKE does
Read the segments the way a translator would, and check them the way your scheduler does.
- Any delimiters and any envelope, including the trading partner whose separators are inverted
- Firm and planning quantities split by FST code, and a release's cum compared to what your ERP has shipped
- A week that dropped from the previous forecast is shown as a change, not silently replaced
- Fabrication and material authorizations carried as the limit you can build and buy at the customer's risk
- A 997 queued the moment a transaction is received; some OEM specs want it within five minutes
Where it lands
In the ERP as Orders and releases, with the EDI file kept.
- An Order or a release against the blanket in JobBOSS², E2, Epicor, Global Shop, Plex or your ERP
- Ship-to plant and dock code from the release, checked against what the ERP already knows for that customer
- The raw interchange stored next to the Order, with the control numbers, for the day the customer disputes it
- A 997 and an 855 sent, and both recorded with the Order
What goes back out
The replies go out when the ERP says the event happened, not when someone remembers.
- 855 when the Order posts, with the per-line status the partner expects
- 856 ASN when the Packing list closes, with the packing slip number as the shipment ID and the shipped and cum quantities per line
- 810 Invoice when the Invoice posts, or no 810 at all for a customer that pays off the ASN
- 997 on every inbound set, every time
Questions shops ask
Do we need an EDI translator or a VAN account?
No translator. STRYKE reads and writes X12 itself. If your customer requires a VAN, STRYKE connects to the VAN mailbox you already have; if they send through a Web-EDI portal or an emailed file, it reads from there.
What about the cum?
Each release carries the customer's last cum received and last packing slip. STRYKE compares both to what your ERP has shipped before entering the release, and holds the release when they disagree, so a catch-up shipment is a decision a person makes, not a surprise on Monday.
Does our ERP need an EDI module?
No. The ERPs small shops run mostly have no native X12. STRYKE enters the release through the API, the import file or the Order screen, the same three doors it uses for every other document.
