Jun 2023
EDI 862
(Last Updated On: June 12, 2024)

Introduction: What is EDI X12 862 Shipping Schedule?

In today’s digital world, efficient communication and streamlined processes are paramount for successful supply chain management. One of the key tools that facilitate this seamless exchange of information is Electronic Data Interchange (EDI).

Among the various EDI transaction sets, the EDI 862 transaction, also known as the Shipping Schedule, plays a crucial role in coordinating shipments and ensuring timely delivery.

The Shipping Schedule (EDI 862) provides essential data related to the delivery of goods, allowing suppliers and customers to efficiently plan and manage their inventory and logistics operations.

Let’s explore the definition, structure, standards, processing, and benefits of the EDI 862 Shipping Schedule.

EDI 862 Shipping Schedule – Definition

The EDI 862 Shipping Schedule is a standardized electronic document sent from a supplier to a buyer; it contains specific details regarding the shipping requirements for a particular order or set of orders. It typically includes information such as:

  • shipment dates,
  • quantities,
  • packaging instructions,
  • carrier details, and other relevant logistics data.

EDI X12 862 (EDIFACT DELJIT) – Structure & Standards

The structure of an EDI 862 document follows the ANSI ASC X12 standard. In the UN/EDIFACT standards, the DELJIT (Delivery Just-In-Time) message performs a similar function. It consists of data segments, elements, and sub-elements arranged in a hierarchical format.

The structure defines the order and format in which the information is transmitted, ensuring compatibility and interoperability between different systems.

ANSI ASC X12 standard is prevalent in North America, while UN/EDIFACT is widely adopted globally.

These standards provide a common language for data exchange, ensuring consistency and compatibility between trading partners.

EDI 862 Shipping Schedule – Processing

The processing of the EDI 862 Shipping Schedule involves the exchange of structured electronic data between the sender and the receiver. Here’s a general overview of the processing steps:

Data Preparation: The shipping schedule data is collected and formatted according to the specific EDI standard, such as ANSI ASC X12 or UN/EDIFACT.

Translation: Data is translated into the appropriate EDI format, usually companies use the services of an EDI Provider. This can be either a Fully Managed EDI Service or an EDI Web Service.

This step ensures that the information is correctly encoded and compliant with the selected standard.

Learn more about how to choose the right EDI solution for you in this article: Business Automation: How to Choose the Right EDI Solution

Transmission: The translated EDI document is transmitted securely by the EDI Provider to the trading partner using a communication protocol such as AS2, FTP, or VAN (Value Added Network).

Receipt and Validation: The recipient’s system receives the EDI 862 document and performs validation checks to ensure the data integrity and compliance with the standard.

Processing and Integration: The received shipping schedule information is processed and integrated into the recipient’s internal systems, such as enterprise resource planning (ERP) or warehouse management systems (WMS).

Acknowledgment: A functional acknowledgment (e.g., EDI 997) is generated and sent back to the sender to confirm the successful receipt and processing of the EDI 862 document.

Sample EDI 862 Data for the Shipping Schedule Transaction Set

The EDI 862 document represents a Shipping Schedule, which provides information about scheduled shipments.

ISA*00*          *00*          *12*Sender         *ZZ*Receiver       *210429*0402*U*00401*000000003*0*P*>



BSS*00*2019-12-17 13:15:19*20191217*DL*20210429*20210429****P302289











PER*EX*Company’s Help Team*EM*email@lcopany.com*TE*1-800-123-123








TD3***SHIP DIRECT******1783662





Let’s break down the segments and elements within the provided EDI 862 file:

ISA: Interchange Control Header segment. It contains information about the sender and receiver of the interchange, along with control information such as the date and version of the EDI standards used.

GS: Functional Group Header segment. It provides information about the sender and receiver. The segment also includes a group control number and the version of the EDI standards used.

ST: Transaction Set Header segment. It indicates the start of a specific transaction set, in this case, the Shipping Schedule (862).

BSS: Beginning Segment for Shipment Schedule. It contains general information about the shipment, such as the scheduled shipment date, the delivery date, and other relevant details.

N1: Name segment. It provides information about the entities involved in the transaction.

LIN: Item Identification segment. It identifies a specific line item or product being shipped, including details like the item number and item type.

UIT: Unit Detail segment. It provides information about the unit of measure for the item being shipped.

REF: Reference Identification segment. It includes additional references related to the shipment.

PER: Administrative Communications Contact segment. It specifies the contact person or department responsible for communication-related to the transaction, including their name, email, and phone number.

FST: Forecast Schedule segment. It contains forecast information related to the shipment.

DTM: Date/Time Reference segment. It provides date and time information associated with the shipment, such as order dates, delivery dates, and ship dates.

SHP: Shipped/Received Information segment. It includes details about the shipment, such as the number of units shipped, the packaging code, and the shipment date.

TD3: Carrier Details (Equipment) segment. It provides information about the transportation equipment used for the shipment, including any special handling requirements.

TD5: Carrier Details (Routing Sequence/Transit Time) segment. It specifies details about the carrier, such as the carrier code, routing information, and transit time.

SE: Transaction Set Trailer segment. It marks the end of the transaction set (Shipping Schedule in this case) and includes a control number and the number of segments in the set.

GE: Functional Group Trailer segment. It marks the end of the functional group and includes a control number and the number of transaction sets within the group.

IEA: Interchange Control Trailer segment. It marks the end of the interchange and includes a control number and the number of functional groups within the interchange.

Each segment is composed of elements separated by asterisks (*). The elements

What is the Difference Between EDI 830 and EDI 862? (EDI 862 vs EDI 830)

The EDI 830 and EDI 862 are both important EDI documents used in supply chain management, but they serve different purposes and convey different types of information. Here’s a breakdown of the differences between the two:

EDI 830 – Planning Schedule with Release Capability

The EDI 830, also known as the Planning Schedule with Release Capability, is used by the customer (buyer) to communicate their long-term production to the supplier. It provides a forecast of the customer’s anticipated demand for goods over a specific period, typically weeks or months in advance. The EDI 830 includes information such as item quantities, delivery schedules, and any changes or updates to the forecasted demand.

The main purpose of the EDI 830 is to help suppliers plan their production schedules, capacity requirements, and raw material procurement based on the anticipated demand from the customer. It allows suppliers to align their resources and inventory levels to meet the customer’s needs efficiently.

EDI 862 – Shipping Schedule Transactions

On the other hand, the EDI 862, also known as the Shipping Schedule, is used to communicate detailed shipping information to the supplier. It provides specific instructions regarding the shipment of goods. Thus, the purpose of the EDI 862 Shipping Schedule is to convey specific shipping instructions (delivery date, carrier info, destination facility…). It’s important to note that the 862 does not replace the 830; rather, it complements it.

The primary purpose of EDI 862 is to inform the supplier about the planned shipping activities and enable the customer to efficiently plan their inventory and logistics operations. It helps the customer prepare for the receipt of goods, allocate warehouse space, and coordinate their internal processes accordingly.

In summary, the key differences between the EDI 830 and EDI 862 are:

Content: The EDI 830 focuses on providing forecasted demand and long-term production requirements, while the EDI 862 provides detailed shipping information and instructions.

It is important to note that the specific roles and responsibilities for sending and receiving EDI 862 can vary depending on the business relationship and agreement between trading partners. It is ultimately determined by the specific arrangement and practices between the buyer and supplier.

Planning vs. Execution: The EDI 830 is more related to production planning and demand forecasting, whereas the EDI 862 is more focused on the execution and coordination of shipments and deliveries.

Both documents play crucial roles in supply chain management, helping trading partners effectively plan, communicate, and coordinate their production and logistics activities.

EDI 862 Shipping Schedule Benefits

The EDI 862 Shipping Schedule offers several benefits to trading partners in the supply chain:

Improved Efficiency

By automating the exchange of shipping information, the EDI 862 reduces manual data entry and paperwork, resulting in faster and more accurate processing of shipping schedules.

Enhanced Visibility

The shipping schedule provides real-time visibility into upcoming deliveries, enabling better planning and coordination of resources.

Reduced Errors

With standardized data formats and automated validation, the EDI 862 helps eliminate errors and discrepancies that can occur during manual data entry or paper-based processes.

Streamlined Logistics

The timely and accurate transmission of shipping information allows suppliers and customers to optimize their logistics operations, reducing lead times and improving order fulfillment.

Inventory Optimization

By having access to precise shipping schedules, organizations can manage their inventory levels more effectively, minimizing stockouts and excess inventory.

Stronger Trading Partner Relationships

EDI 862 promotes collaboration and trust between trading partners by enabling seamless information exchange, leading to improved business relationships.

Overall, the EDI 862 Shipping Schedule plays a vital role in supply chain management by facilitating efficient communication of shipping requirements, reducing errors, and enhancing operational effectiveness for businesses involved in the movement of goods.

Automate 862 Shipping Schedule with EDI Services from EDI2XML

We have been offering EDI services for more than 22 years, making us highly experienced in implementing EDI projects. Our services cover a wide range of options, including fully managed EDI, EDI web service, and EDI on-premises solutions.

Whether you need comprehensive support or specific EDI services, we have the expertise to meet your requirements.

Contact us today for a free initial consultation to discuss how our EDI solutions can streamline your operations.

Sorry no comment yet.


Your email address will not be published. Required fields are marked *