What is an EDIFACT DELFOR Message?

Find out how the EDIFACT DELFOR message is reshaping the purchasing process.

The EDIFACT DELFOR (DELivery FORecast) message is used in particular for exchanging delivery schedule information. A DELFOR message is an electronic planning schedule sent from the customer to the supplier. It follows the EDI message standard UN/EDIFACT and is a key message type for the electronic purchasing process in manufacturing industries.

Manufacturers use the DELFOR standard to notify suppliers of the predicted demands via Electronic Data Interchange (EDI). The message represents a forecast, which consists of multiple segments containing data and quantities for the requested materials.

Forecasts normally come from the ERP system by a planning disposition process and are exported into an ERP-specific data format, for example IDoc in case the ERP is SAP R/3 ECC. EDIFACT DELFOR messages are then converted from e.g. SAP IDoc and sent to the suppliers by the EDI solution. When received by the supplier the DELFOR message will trigger or modify planning schedules and populate the information on possible order releases. This way an incoming EDIFACT DELFOR message will always replace the schedule of the previous planning schedule message.

Planning schedules contain the so called segments and elements as specified for EDIFACT DELFOR. An EDI planning schedule message is sent, received, and processed by an EDI solution. The solution can be an EDI Cloud Service or an EDI software for in-house usage. It is key to follow the defined EDIFACT DELFOR standards to avoid errors and to pave the way that the document reaches the supplier.

A typical EDIFACT DELFOR Message includes:

Information concerning parts that are ordered (material no., material description)
Several lines specifying dates and quantities of deliveries (What should be delivered when?)
Contract-/purchase order number
Material- and/or production releases
Ship to address (plant and dock/gate addresses)

UNA:+.? '
UNB+UNOC:3+O0013SEEBURGER:14+O0013ECONTEA+200114:0506+102'
UNH+1+DELFOR:D:04A:UN:SEE'
BGM+241:::LAB123+102+9'
DTM+137:20200114:102'
DTM+2:20200124:102'
FTX+AAI+++VERY TASTY ON DARK RYE BREAD'
NAD+BY+4019315000007++SEEBURGER AG+EDISONSTRASSE 1+BRETTEN++75015+DE'
NAD+SE+4019315000007++ECONTEA GMBH+RAHEL HIRSCH STRASSE 10+BERLIN++10557+DE'
RFF+ANK:1234501'
NAD+SF+4019315000007++ECONTEA GMBH+RAHEL HIRSCH STRASSE 10+BERLIN++10557+DE'
RFF+ANK:1234501'
GEI+3+37'
NAD+ST+4019315000007++SEEBURGER AG+KONRAD ADENAUER ALLEE 13+ATHEN++06366+DE'
LOC+11+DA::92'
LOC+7+DA::92:SEEBURGER AG'
LIN+1++BLACK FOREST HAM:IN'
IMD+F+11+::272:YUMMY'
RFF+ON:123456'
RFF+AAN:7'
DTM+171:20200113:102'
RFF+AIF:6'
DTM+171:20200112:102'
CTA+SC+ZZZ:SEEBURGER INFO'
COM+INFO@SEEBURGER.COM:EM'
COM+07252960:TE'
QTY+194:168:PCE'
DTM+50:20200111:102'
RFF+AAU:10558206'
DTM+171:20200106:102'
QTY+194:504:PCE'
DTM+50:20200104:102'
RFF+AAU:10556505'
DTM+171:202001230:102'
SCC+24'
QTY+113:0:PCE'
DTM+2:20200114:102'
UNT+36+1'
UNZ+1+102'

After receiving the DELFOR EDI message, the supplier’s EDI system will check the document against the EDIFACT DELFOR specification and send back a functional acknowledgement confirming the receipt of a planning schedule.

EDIFACT DELFOR vs EDIFACT DELJIT message

After the DELFOR message is received the supplier can also receive an EDIFACT DELJIT message as a supplement to the EDIFACT DELFOR message. In case that both message types are sent to a supplier, then the DELFOR message typically gives a longer (sometimes several months) planning forecast for the supplier and the DELJIT message gives for a shorter timeframe (of e.g. 10 days) the to be delivered quantities for each day (the daily call off).

EDIFACT DELFOR example in the EDI workflow

Documents which are exchanged between business partners over EDI follow a typical sequence of steps, depending on the industry vertical. The flow below shows an EDIFACT standard DELFOR together with other message types in a manufacturing scenario:

Typical problems which appear with exchanging the planning schedules come from wrong or unknown master data. In case an EDIFACT DELFOR message is not expected in the supplier’s ERP system this will result in an issue that needs manual correction:

New parts are requested where the part identification is not available in the supplier’s ERP system
Latest dock or gate codes are used on the customer side but have not been added in supplier’s ERP

VDA messages are still commonly used in the automotive industry. VDA 4984 and VDA 4905 are representations of delivery schedule messages serving a similar purpose. EDIFACT and VDA message types are used in Europe, whereas only EDIFACT standards are popular in Asia. The ANSI X12 standard is very common in the NAFTA region.

Reduce employee workload

by avoiding manual disposition

Avoid issues

because data is derived automatically by the ERP and EDI systems w/o human mistakes

Avoid paper based work

less administrative overhead

Companies can focus on strategic tasks due to having more time

Less interaction with suppliers for correcting typing errors

Update to the planning schedules goes faster so out-of-stock or over delivery scenarios happen far less often

Delivery planning is done faster and less error-prone

Avoidance of wrong or missing deliveries due to human errors

Better supplier ratings

Saves time and reduce costs due to automatic integration of delivery schedule

When you look into replacing your legacy EDI solution with latest and greatest technology, you should evaluate your options how to operate in a cost effective way. SEEBURGER provides you all options booking it as an EDI Cloud Service in the SEEBURGER Cloud or in public cloud environments like the ones from Google, Azure, AWS etc. as well as an on-premises software solution.