EDI X12 856 Advance Ship Notice Skeleton Generator for Distributors
An 856 advance ship notice tells a customer what is on the truck before it arrives. Distributors send it to retail, government and large contractor customers, and the first draft of a map often starts from a skeleton like this one.
Fill in
856 skeleton
ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *261020*0900*U*00401*000000101*0*P*>~ GS*SH*SENDERID*RECEIVERID*20261020*0900*101*X*004010~ ST*856*0001~ BSN*00*SH100234*20261020*0900~ HL*1**S~ TD1*CTN*3~ DTM*011*20261020~ HL*2*1*O~ PRF*PO778123~ HL*3*2*I~ LIN*1*BP*BP-4471~ SN1*1*24*EA~ CTT*3~ SE*13*0001~ GE*1*101~ IEA*1*000000101~
This is a generic skeleton. Trading partners publish their own implementation guides that fix the version, required segments, qualifiers, carton (pack) loops and ID formats. Fix the ISA padding to the exact field widths of your partner, update the SE segment count, and test with the partner before production use.
Review your EDI mapping
Optional: send your partner guide and ERP fields and we can talk through how the ASN data could be assembled and checked.
Optional. The tool and every export work without this. No spam.
How to use it
Fill in sender and receiver IDs, shipment ID, ship date, PO, part and quantity. Copy the output as the target structure for your EDI mapper or as a sample test file. Then compare it with the partner's implementation guide line by line. Their guide wins over any generic example.
- Use the partner's ISA qualifiers and widths
- Count segments and update the SE value
- Add pack loops if the partner requires them
- Test in the partner's sandbox first
The hierarchy
The 856 uses HL segments to build a tree. Here HL 1 is the shipment level, HL 2 is the order level under it, and HL 3 is the item level under the order. Many partners require a pack level (P) between order and item, or tare and pack levels, so confirm the required hierarchy. Each HL carries an ID, a parent ID and a level code.
Reading the sample
BSN carries the purpose, shipment ID and date. TD1 gives packaging, DTM gives the ship date, PRF references the purchase order, LIN identifies the buyer part with a qualifier, and SN1 gives the shipped quantity and unit. CTT counts the HL segments. SE counts all segments from ST to SE inclusive, so recount after you add loops.
Common mistakes
Frequent errors are wrong segment counts, mismatched control numbers between ISA and IEA, dates in the wrong format, and sending quantities that do not match the invoice later. Another is sending an ASN before the shipment is confirmed in the ERP, which makes the customer receive data for goods not yet shipped.
Frequently Asked Questions
Is this skeleton ready to send to a customer?
No. It is a teaching and starting point. Customers define required segments, qualifiers and IDs in their guides, and most will reject a file that does not follow them. Treat it as a draft for your mapper.
What does the HL segment do?
HL builds the hierarchy of the document. Each one has its own ID, a parent ID and a level code such as S for shipment, O for order, P for pack and I for item. The tree tells the receiver what is inside what.
How do I count the SE value?
Count every segment from ST through SE, including both. In the sample that is 13. If you add or remove any segment, recount before you send.
Do I need an EDI provider?
Most distributors use a VAN or an EDI service or an ERP module to handle transport, acknowledgments and mapping. The skeleton helps you plan the map, not replace that connectivity.
If your ASN data is rebuilt by hand from ERP shipments, we can help review the mapping and automate the extract with approval before anything is sent.
Related Tools
Prophet 21 Open Order and Backorder SQL Generator
Builds a read-only SQL pattern that lists open sales order lines, ordered versus shipped quantity and age.
EpicorProphet 21 Order to Cash Go-Live Test Checklist
A test script outline for the order-to-cash cycle in Prophet 21 before cutover, from quote to cash application.
Supply Chain & InventoryDistribution KPI Formula Reference
A searchable lookup of the standard KPI formulas a distributor tracks, with units, direction of good and common data traps.
Supply Chain & InventoryDistributor Pricing and Rebate Terms Glossary
Plain definitions of the pricing, cost and rebate terms that appear in distributor ERP setup and vendor agreements.
More Supply Chain & Inventory tools
See all- Distribution ERP Fill Rate Calculator
- Distributor Rebate Tracking Worksheet
- Branch Transfer Planning Worksheet
- Distributor ABC Inventory Classification Worksheet
- Oracle Fusion Inventory Turns and Carrying Cost Calculator
- Distributor Slow-Moving Inventory Review Worksheet
- Distributor Vendor Performance Scorecard Worksheet
- Distributor GMROI Calculator
- Distributor Backorder Cost and Fill Rate Calculator
Keep exploring
Free tools
- X12 856 Advance Ship Notice GeneratorFill in shipment, carrier and item details and get a clean X12 856 skeleton with shipment, order and item hierarchy to use as a test file.
- EDI X12 850 Purchase Order Skeleton GeneratorFill in the partner IDs, PO number and one line item to generate a valid-looking X12 850 test message in 005010 format.
- X12 810 Invoice EDI Template GeneratorFill in invoice, PO and line details and get a clean X12 810 invoice skeleton with envelope and matching control numbers.
ERP fixes and how-tos
- How to Set Up an EDI Trading Partner in Plex SystemsHow to configure a new EDI trading partner in Plex EDI Data Manager, map document types like 850, 830, 862, and 856, and test before going live.
- Epicor Eclipse or Prophet 21: how a distributor should make the decisionA blunt decision guide for CIOs on Epicor Eclipse versus Prophet 21: what to ask Epicor, which factors matter, and how to avoid a costly migration mistake.
Runs with your ERP
- TrueCommerce EDI and Infor M3TrueCommerce managed EDI for Infor M3 (also VISUAL and other Infor ERPs): documents, data flows, setup steps, pitfalls, alternatives and where AI helps.
- SPS Commerce Fulfillment and SAP S/4HANA: EDI for retail partnersHow SPS Commerce Fulfillment connects SAP S/4HANA and ECC to retail trading partners: IDoc flow, managed maps, setup steps, pitfalls, alternatives and AI.
- SPS Commerce Fulfillment with JD Edwards: Retail EDI Without Writing MapsHow SPS Commerce Fulfillment connects to JD Edwards EnterpriseOne and World for retail EDI: orders, ASNs and invoices, setup steps, pitfalls and an AI layer.
Guides
- SyteLine EDI Transaction Sets: Configuring 850, 810 & 856Configure EDI transaction sets 850, 810, and 856 in Infor SyteLine. Step-by-step guide for purchase orders, invoices, and ASN documents with IDO mapping.
- EDI Implementation for Manufacturers: A Practical GuideEDI implementation for manufacturers: map 850, 856, and 810 transactions to your ERP, pick a VAN or AS2, and go live with trading partners in 90 days.
- EDI Transaction Sets Every Manufacturer Should KnowA manufacturer reference to EDI transaction sets: what 850, 855, 856, 810, 862, and 830 documents contain and how each maps into ERP order and shipping data.
AI on your ERP
- AI for SPS Commerce: EDI Order, ASN and Chargeback Questions Answered From Your ERPAdd private AI to SPS Commerce EDI: reconcile 850 orders to ERP, catch ASN errors before chargebacks and answer retailer compliance questions.
- AI for Infor Distribution FACTS, Without Replacing the SystemAdd a private AI layer to Infor Distribution FACTS: plain-language order and inventory answers on IBM i, agents for exceptions, on-prem deployment.