EDI 862 Shipping Schedule for Automotive JIT Suppliers

A seat-frame supplier receives four 862 shipping schedules from the same assembly plant between Monday evening and Tuesday noon. The translator loads each one as new demand, the ERP adds them together, and the warehouse stages 960 pieces for a 06:00 window that actually needs 240. A day later the opposite happens: a revised schedule moves a window forward by eight hours, nobody sees it, and the only way to make the line is a dedicated van at four times the normal freight cost.

Both failures come from treating the 862 as an order rather than as what X12 says it is: a precise, frequently replaced shipping schedule that supplements the weekly 830 planning schedule. Once the supplier's system replaces, not adds, each schedule by part and ship-to, and runs a timed slack check against every firm window, premium freight becomes an exception with a named cause instead of a weekly habit.

• What this guide covers: the BSS, FST, REF, SDP and SHP segments in an automotive 862; replacement logic; the supplier's clock from receipt to dock; and the Indian invoice and e-way bill steps that follow each call-off.
• What it adds: an annotated sample transaction, a premium freight trigger formula, a timed incident, a dollar and rupee expedite calculation and a map test plan.

What an 862 carries that a weekly 830 release cannot

The 862 narrows the 830's forecast into exact quantities, dates and often times of day for the next few days. It overrides the 830 for shipping and delivery detail within its horizon but never replaces the 830 or authorises material.

The X12 description of transaction set 862 says it lets a customer convey precise shipping schedule requirements to a supplier and is intended to supplement the 830. It supersedes certain shipping and delivery information from a previous planning schedule, does not replace the 830, and shall not be used to authorise labour, materials or other resources. X12 gives daily shipping schedules versus weekly planning schedules as the typical pattern for just-in-time supply.

Our guide to the X12 830 planning schedule explains forecast buckets, authorisations and cumulative reconciliation in depth. This article assumes the 830 is already loaded and follows what changes when the daily 862 arrives on top of it.

BSS header: purpose code, delivery or ship basis and the horizon

The BSS segment tells the supplier three things before any part appears: whether this schedule replaces an earlier one, whether its dates are arrival or departure dates, and which days it covers. Getting any of the three wrong shifts every quantity that follows.

In Adient's published 004010 guide, BSS01 is the transaction set purpose code with value 05, Replace; BSS02 is the ship schedule number; BSS03 is the creation date; BSS04 is the schedule type qualifier, DL for delivery based or SH for shipment based; BSS05 and BSS06 are the horizon start and end; BSS07 is the release number; and BSS11 is the schedule quantity qualifier, A for actual discrete quantities. Benteler's 4010 guide uses 00 for an original schedule.

• Purpose code 05: the new schedule replaces the previous one for the same ship-to and parts; the translator must not add it to open demand.
• Schedule type DL: FST dates are the dates goods must arrive at the plant, so the supplier subtracts transit time to find the ship date.
• Schedule type SH: FST dates are ship dates; transit risk sits with whoever owns the freight under the contract.
• Horizon dates: requirements outside BSS05 to BSS06 still come from the latest 830; inside it, the 862 governs.
• Quantity qualifier A: quantities are discrete per line, not cumulative totals, so they are summed only across different dates.

FST lines with hour-level windows and the pickup sheet reference

Each FST line inside an item loop gives a quantity, a firm or planning flag, a date and, for just-in-time plants, a time of day. Some buyers also attach a pickup reference that must come back on the advance ship notice.

Adient's guide defines FST01 as quantity, FST02 as forecast qualifier with C for firm and D for planning, FST03 as timing qualifier with D for discrete, W for weekly bucket and M for monthly bucket, and FST04 as the date. FST06 qualifies the time in FST07, with 002 for delivery requested or 010 for requested ship. FST08 value P8 marks a pickup reference number in FST09, which Adient says must be returned on the ASN.

ST*862*0001~
BSS*05*20261112-002*20261112*DL*20261113*20261120*20261112-002****A~
N1*SI*BUYER SEATING PLANT*1*987654321~
N1*ST*BUYER SEATING PLANT*92*4410~
N1*SU*FRAME SUPPLIER*92*552210~
LIN**BP*7731-4402*PO*55039093*EC*C~
UIT*EA~
REF*DK*D07~
REF*LF*L22~
FST*240*C*D*20261113**002*0600*P8*PS-118804~
FST*240*C*D*20261113**002*1400*P8*PS-118805~
FST*480*C*D*20261114**002*0600*P8*PS-118806~
FST*1200*D*W*20261116~
SHP*01*480*050*20261112~
SHP*02*96480*051*20260105**20261112~
REF*SI*SH-552210-3391~
CTT*1*2160~
SE*18*0001~

Supplier-side checks on receipt (per ship-to, buyer part):
  replace_set   = all open 862 lines with the same N1*ST and LIN BP   (purpose 05)
  hash_ok       = CTT02 == sum(FST01)            -> 240+240+480+1200 = 2160
  firm_lines    = FST02 == "C" and FST04 within BSS05..BSS06
  ship_due(i)   = FST04/FST07 of line i - transit_hours   (because BSS04 = DL)
  slack(i)      = ship_due(i) - (now + pick_pack_h + load_h)
  premium_flag  = any firm line with slack(i) < 0 on the contracted carrier

The sample is illustrative, built in the 004010 layout of the Adient guide. REF qualifiers DK and LF give the dock and the assembly line feed location, which drive label content rather than quantity. The final FST line is a weekly planning bucket and should not be picked; it sits in the schedule only to show near-term direction.

An EDI 862 shipping schedule in the X12 004010 layout carries firm FST lines with qualifier C, a delivery-requested time in FST07 and often a P8 pickup reference that must return on the 856 ASN, so the supplier's ERP should reject any schedule whose CTT02 hash differs from the FST01 total by even 1 unit.

Replace, not add: how each new 862 supersedes the last

A supplier system must hold exactly one current schedule per ship-to and buyer part. Every new 862 with purpose code 05 deletes the open lines of the previous one for that pair and loads its own, and a log keeps the replaced lines for disputes.

Ordering matters as much as replacement. Interchanges can arrive out of sequence after a network delay, so the supplier should compare the creation date in BSS03 and the schedule number in BSS02 before replacing anything. A schedule older than the one already loaded is logged and ignored, and the scheduler is told. Without that check, a delayed Monday schedule can overwrite Tuesday's.

• Replacement key: ship-to code from N1*ST plus buyer part from LIN, not the purchase order alone, because one PO can feed several docks.
• Sequence test: accept only a schedule with a later BSS03 date, or the same date and a higher suffix in BSS02.
• Dropped parts: a part present in the old schedule and absent from the new one has zero demand in the horizon; it does not keep its old lines.
• Horizon edges: lines after BSS06 revert to the 830, so the planner sees one combined demand picture, clearly labelled by source.

Schedule replacement for an X12 004010 EDI 862 with BSS01 purpose code 05 should run in the supplier ERP keyed on the N1*ST ship-to and LIN buyer part, accepting only a later BSS03 date, so a reissued schedule changes open demand by 0 units and an older file is never applied.

Functional acknowledgements belong in the same design. A 997 tells the plant the schedule was received and parsed; it does not mean the supplier can meet it. Our page on the EDI 997 functional acknowledgment explains what an accepted, partially accepted or rejected acknowledgement does and does not confirm.

From call-off to dock: the supplier's clock for a daily schedule

For each firm line the supplier works backwards from the requested time: transit, loading, packing and picking must all fit before the window, or the line needs premium freight. The check should run on receipt of every schedule, not once per shift.

The trigger compares the ship-due time with the earliest moment the parts can be ready and on the contracted carrier. When slack falls below zero, the choices are to ask the plant for relief, split the quantity, or book a faster mode. Each choice needs an owner and a time limit, because a plant that learns of a shortage at 04:00 for a 06:00 window has no options left.

Thursday trace: a replaced schedule loaded as extra quantity

The trace is illustrative, but each step uses segment values from the published guides above. The supplier's EDI map was correct for the 830 and wrong for the 862 in one setting.

1. Wed 18:20, translator: schedule 20261112-001 arrives for ship-to 4410, part 7731-4402, with a firm line of 240 pieces delivery requested 06:00 Thursday. The ERP creates a sales schedule line for 240.
2. Wed 21:45, translator: schedule 20261112-002 arrives with purpose code 05 and the same line. The map treats it as new and adds another 240. The 997 goes back accepted within minutes.
3. Thu 01:30, shipping: the pick list shows 480 for the 06:00 window. The rack holds 300. The shift lead raises a shortage and calls in two pickers on overtime to pack from a later batch.
4. Thu 03:10, logistics: with 180 pieces "short", a dedicated van is booked for 04:30 to carry the balance. ASN SH-552210-3391 is sent for 480 pieces with pickup reference PS-118804.
5. Thu 06:05, plant dock: the receiving clerk accepts 240 against the schedule and flags 240 as over-shipment. The supplier pays the van, the overtime and the return freight for 240 pieces nobody ordered.

The controlled version changes one map setting and adds one test. Purpose code 05 triggers deletion of open lines for ship-to 4410 and part 7731-4402 before loading, and the test pack below includes a reissued schedule with identical lines, which must leave demand unchanged.

Premium freight exposure from one missed window in dollars and rupees

An expedite for one short window costs a fixed amount whatever the quantity, so it hits low-priced parts hardest. Measuring it per piece shows whether a supplier's schedule handling, not its production, is eroding margin.

The example below assumes 240 pieces missed a 06:00 window and had to travel on a dedicated vehicle instead of the scheduled milk run. Distances, rates, wages and piece prices are illustrative assumptions, not market rates. Contract terms decide whether the plant can also recover its own costs from the supplier; those are left out here.

Premium freight on an EDI 862 firm line, recorded in the supplier ERP against the call-off and its ASN, cost an illustrative $955.50 or ₹8,345 for 240 pieces, equal to 35.5% of US revenue and 7.2% of Indian revenue on those pieces, so the slack check should flag lines at under 4 hours.

The gap between the two percentages comes from the assumed freight-to-price ratio, not from either market being safer. A supplier should track the per-piece expedite cost by root cause: map error, late schedule from the plant, production shortfall, or carrier failure. Only the first is fixed by EDI work, and in many audits it is the largest.

Dispatch paperwork when an Indian assembly plant calls parts daily

India has no statutory format for a just-in-time call-off; each OEM chooses its own channel, whether an X12 862, another EDI message, a supplier portal or a spreadsheet. What the law does fix is the paperwork for every physical dispatch the call-off produces.

Section 31(1)(a) of the CGST Act requires a registered supplier to issue a tax invoice before or at the time of removal of goods where the supply involves movement. CGST Rule 138(1) requires an e-way bill before movement where the consignment value exceeds fifty thousand rupees. A schedule that splits one day into two windows therefore produces two dispatches, two invoices and, above the threshold, two e-way bills.

• One window, one invoice: map each firm FST line that ships separately to its own dispatch, so invoice quantity equals the line's quantity and the plant's goods receipt matches.
• Expedited balance: the 240-piece van in the example carries ₹1,15,200 of taxable value at the assumed price, above the ₹50,000 e-way bill threshold before tax is even added.
• Milk-run pickups: when the plant's transporter collects from several suppliers in one truck, each supplier's bill can be listed on a consolidated e-way bill by that transporter.
• Pickup reference: where the plant uses a pickup sheet number, print it on the invoice and the transporter's document so all three records join at the plant gate.

Translator rules, planner calls and who signs each schedule change

Parsing, replacing and hash-checking a schedule are fixed rules that the translator and ERP must apply without discretion. Deciding what to do about a schedule that cannot be met is a human call, made by a named role within a set time.

Testing an 862 map before the first live call-off

A map that passes syntax checks can still double demand, so test with business scenarios, not just with sample files. Each case below has an expected ERP result that a scheduler can verify without reading raw X12.

The ASN side deserves its own test pack. Our guide to EDI 856 ASN schema mapping and error handling covers the hierarchy and label data that must match what the 862 asked for. More integration guides are on the logistics and supply chain hub, and if you are replacing a schedule-handling process for automotive customers, you can describe your requirements to us.