EDI 862 Shipping Schedule
In Electronic Document Interchange (EDI), the EDI 862 Shipping Schedule transaction set details the defined shipping requirements and serves to replace any shipping details projected in a previous EDI 830 Planning Schedule With Release Capability. However, it does not replace the 830 transactions as part of the order and documentation process. The two EDI mappings work in tandem to support Just-in-Time (JIT) manufacturing. The forecasted data that an 830 transaction provides enables the supplier to better manage materials and other resources. An 862 transaction supplements the 830 by updating and detailing shipping requirements as the order progresses towards fulfillment. Additionally, when inventory levels pass a certain threshold, an 862 can serve to notify a supplier to replenish the item(s) without delay.
Shipping Schedule Format
In a real-time manufacturing environment, shipping instructions can change frequently depending on an array of factors. The 862 ensures that all parties involved are made aware of:
• A Decrease in an order quantity
• An Increase in an order quantity
• A Change in the ship date
An EDI 862 ensures that inventory is available when a supplier receives instructions from a customer to ship an item and provides the most up-to-date shipment details. It is important to note that the details contained in an EDI 862 shipping schedule will supersede the contents of an EDI 830 Planning Schedule.
The shipping Schedule document is organized into segment and data elements. Each segment contains at least one data element. These elements can include, but are not limited to:
• Order numbers
It is important to note that the Shipping Schedule does not influence or authorize the utilization of labor, materials, or other resources. After the 862 Shipping Schedule is received by the shipper, an EDI 997 Functional Acknowledgment is sent back from the shipper indicating that the 862 Shipping Schedule was successfully received.
Shipping Schedule Benefits
The Shipping Schedule is most frequently used in a daily shipping environment, as opposed to a weekly or monthly one. It also enables the customer to designate shipping requirements to multiple customer locations, whereas an 830 is more consolidated. An 862 transaction supplements the 830 by updating and detailing shipping requirements as the order progresses towards fulfillment. Additionally, when inventory levels pass a certain threshold, an 862 can serve to notify a supplier to replenish the item(s) without delay.
About Encompass Solutions
Encompass Solutions is a business and software consulting firm that specializes in ERP systems, EDI, and Managed Services support for Manufacturers and Distributors. Serving small and medium-sized businesses since 2001, Encompass modernizes operations and automates processes for hundreds of customers across the globe. Whether undertaking full-scale implementation, integration, and renovation of existing systems, Encompass provides a specialized approach to every client’s needs. By identifying customer requirements and addressing them with the right solutions, we ensure our clients are equipped to match the pace of Industry.