SEEBURGER Business Integration Suite Accelerate Business-Driven Innovation with IntegrationDownload whitepaper now
SEEBURGER Customer Portal We provide Cloud Services to make your company more flexible and agile.
Log InSign Up
How can we help you? Rely on highly qualified support – around the clock.
Support HotlineService Portal
BIS 6.7 – Now Available! Customers using BIS 6.7 benefit from agile and scalable integration solutions for the digital shift and a variety of operating models.More about the Major Release
Jobs at SEEBURGER – Shape your future with us. The "Who is who" of the economy rely on SEEBURGER – you can trust in SEEBURGER as an employer
The ANSI X12 EDI 862 message represents Just-in-time information that is sent to suppliers by their customers via EDI. The message is based on the ANSI X12EDI message standard and is a supplement document for electronic purchasing processes based on delivery schedules commonly used in the manufacturing and automotive industries.
In order to further reduce stock levels and therefore exchanging precise delivery information manufacturing companies send demand information not just on a per day level but even more precisely on a time slot level during a specific day. To achieve this the customers use the EDI 862 format which consist of segments containing date, time and quantity information for required materials in order to inform their suppliers.
The ANSI X12 EDI 862 message is crucial when fulfilling the Just-in-time (JIT) process of manufacturing companies. Because of that it is also referred as “Just-in-time”- or JIT message. In JIT environments EDI 862 messages are used as supplement to delivery planning sent by an ANSI X12 EDI 830 message. The EDI 862 messages are sent very frequently to communicate exact shipping times and quantities. Also changes to date, time and quantities of previous EDI 862 transmissions can be exchanged within a new message.
Only suppliers who can guarantee a high delivery quality are eligible for serving JIT processes of manufacturers and automotive OEMs. The ability of automatically processing ANSI X12 EDI 862 messages is one key factor to achieve this level of delivery quality and the according supplier rating.
Download the guide
JIT messages consist of segments and elements specified by the ANSI X12 EDI 862 guideline. EDI solutions – which can either be an on-premises solution or EDI Cloud Service – send, receive and process EDI messages like EDI 862. In order to ensure a high quality of the process it is mandatory to follow the ANSI X12 EDI 862 standards which is vital for time critical processes like the Just-in-Time delivery.
A typical ANSI X12 EDI 862 Message includes:
The EDI 862 message is generated on customer side and sent from there to the respective supplier. The supplier’s receiving system validates the message against ANSI X12 EDI 862 specifications after reception and sends back a functional acknowledgement (ANSI X12 997 message type). The functional acknowledgement confirms the reception of the JIT message. After master data validation the information from the EDI 862 message will update the supplier’s planning by adding or updating existing schedules.
In JIT processes orders information are never just exchanged with ANSI X12 862 messages. The JIT processes usually start with an ANSI X12 EDI 830 message defining a long term delivery planning. The EDI 862 messages are used to extend the long term planning with precise time information for the shipments in the near future. This way the EDI 862 document provides the details of the EDI 830 shipping schedule.
In general the documents which are exchanged between EDI trading partners follow a typical sequence of business processes, which depends on the type of industry. The table below shows the role of an ANSI X12 EDI 862 standard message and which other message types are used in a manufacturing scenario:
The ANSI X12 standard is an EDI standard widely used in the Northern America region. In other regions like EU or ASIA EDIFACT and VDA messages are more common. For exchanging JIT information the EDIFACT DELJIT standard is common there. In the automotive industries the VDA4985 and VDA4915 standard messages are widely spread to exchange JIT demands.
Benefits exchanging JIT demands via ANSI X12 EDI 862 for both - the customer and the supplier - are:
Problems that occur when exchanging JIT messages are commonly based on wrong or missing master data. If data is transmitted inside an ANSI X12 EDI 862 messages that is unknown in the supplier’s ERP system, an error on processing step will be the result. Typical issues in context of EDI 862 messages are:
The reliable handling of the EDI 862 shipping schedule is essential for the highly integrated manufacturing in the automotive industry. Customers must ensure their production and suppliers they must protect their supplier ratings. Evaluate all options how to optimize your mission critical EDI solution. With SEEBURGER you have plenty of options including on-premises as an in-house operation, or booking it as an EDI Cloud Service in the SEEBURGER Cloud with very high SLAs.
What is EDI?
EDI Message Standards – An Overview
What is EDIFACT
What is AS2?
What is AS4?
What is OFTP2?
What Is the Meaning of Being EDI Capable?
EDI Operating Models: On-Premises, iPaaS or Full Service EDI
Do you have any questions?
Please contact us!
Thank you for your message
We appreciate your interest in SEEBURGER.