EDIFACT DELFOR D99B Guideline



Similar documents
PURCHASE ORDER RESPONSE

Bulk EDIFACT ASN MESSAGE FORMAT

Adobe - EDIFACT D97.A ORDERS

Media Saturn EDI Application Documentation

Grundfos EDIFACT D.96.A

Purchase Orders Message ORDERS (EDIFACT D97A)

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

EDIFACT DESADV D.97A for suppliers (Benteler Europe)

INVOIC Invoice message

Hella EDIFACT INVRPT

INVENTORY REPORT MESSAGE INVRPT. Version 1.2. agreed-upon by EDI Working Group of ECR Poland

THE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A

DELJIT D97A / CALDEL

This document is for EDI-administrators who will implement this EDI-guide to be able to receive EDIFACT orders from Bosch Rexroth AG.

PARTY INFORMATION MESSAGE. PARTIN Version 1.0. agreed-upon by EDI Working Group of ECR Poland

R.2 STRUCTURE OF AN EDIFACT TRANSMISSION

ORDERS Purchase Order Message

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

PRICE/SALES CATALOGUE MESSAGE PRICAT. Version 1.0. agreed-upon by EDI Working Group of ECR Poland

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

EANCOM INVOICES CROSS DOCK MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS

EDI Guideline KION Group Orders based on EDIFACT ORDERS D.96A Version

ZF Group North American Operations. EDI Implementation Guide

DELFOR. Forecast/Calloff outbound UNH M 1 UNS M 1 UNB BGM M 1 UNS M 1 UNT UNZ M 1 M 1 M 1 SG18 R 9999 SG1 SG2 R 5 D 4 RFF NAD DTM LIN M 1 R 1 M 1 M 1

E A N C O M - MESSAGE

EDI Guideline KION Group DESADV based on EDIFACT DESADV D.96A Version

Magyar Hipermarket Kft. EDI guide PURCHASE ORDER MESSAGE ORDERS EDIFACT D.96A

Hella EDIFACT ORDERS

EDI F GROUP A/S INVOICE. Fona. Document: EDIFACT UserGuide GB-INVOIC_IBM-draft1 Date: 5/ Version: V1.0.0A Page 0 of 43. ecommerce ServiceCenter

Issue 1.1, February agreed-upon by EDI Working Group of ECR Poland

EDI Guideline Orders for configurable materials based on EDIFACT ORDERS D.96A Version

Issue 1.9, April agreed-upon by EDI Working Group of ECR Poland

ADOBE - EDIFACT D97A INVOIC

ORDERS Purchase Order

Global EDI Clearing Center (GECC)

GLOBAL INVOIC (EDIFACT INVOIC D.07A / VDA4938)

5.0 Detailed guidelines of purchase order response (ORDRSP Version 1 EDIFACT D 96B) usage within Volvo.

ORDCHG Purchase Order Change Message Subject for application in the European Steel Industry

COPRAR EDIFACT User Guide Page 2

Revision : 1 Date :

EANCOM D.96A Version: 007 Print: EAN ORDERS D.96A DE

EDIFACT MESSAGE IMPLEMENTATION GUIDELINES RECEP:0:2:FH:

INTRODUCTION TO EDIFACT. presented by EIDX

Issue 6.7, April agreed-upon by EDI Working Group of ECR Poland

Economic and Social Council

T.8 USING THE INVOICE FOR BILLING AND FOR DEBIT AND CREDIT NOTES

GENERAL MOTORS DE MEXICO SPOM

Payment on Receipt EDIFACT INVOIC D97.A

ORDERS. Purchase order message. Edition 2014

DSV IFTMIN S93A. Message Implementation Guideline. based on. IFTMIN Instruction message UN S.93A S3

Post Danmark and DPD

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

Status Message (EDIFACT IFTSTA) Business Integration for the Port of Hamburg. Mattentwiete Hamburg

NAF Nätverk för Affärsutveckling i Försörjningskedjan

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

Contents 1. Introduction 2. Segment description 4. Summary of segments used 13. Summary of segments not used 13. Comparison VDA 4906 => ODETTE 13

B/L-EDIFACT. EDI-Scenarios (Confirmation Messages For The Transmission Of B/L Data) Version 2.0e

TABLE OF CONTENTS. 1. Message structure INVOIC BUSINESS TERMS Segment description INVOIC Example INVOIC...

Message Implementation Guideline ORDERS Purchase Order PHARMA Initiative Austria EANCOM 2002 Syntax 3 Version 1.1. Directory Version:

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

Mapping orders from your library management system to EDI

Issue 6.4, December agreed-upon by EDI Working Group of ECR Poland

EANCOM 2002 PART III

Generic Implementation Information Recommendation of Swiss Financial Institutions for the use of the UN/EDIFACT Messages. Version 1.2 from

INVOIC. Invoice message. Edition 2014

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

EPIC. EDI Core Standards VM

GS1 Germany EDI Recommendation

Aleph Requirements for EDI -Outgoing and Incoming Messages

EDIFACT. Version 1.7

TEXAS INSTRUMENTS. Acknowledge / Rejection Advice Message CONTRL. Based on EDIFICE Issue 1 (Based on EDIFACT Version 92.1)

EDIFACT Standards Overview Tutorial Learn About Key E-commerce Trends and Technologies at Your Own Pace

DESADV DESPATCH ADVICE. BCBG Profile. Message Implementation Guidelines Version: 1.2 Draft

CUSRES Customs Response Message

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

DESADV. Despatch advice message. Edition 2014

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

ANSI X12 version Advance Ship Notice

EANCOM- Spezifikation ORDERS D 96A (EDI-Nachrichtenstandard 2)

EDIFACT Standards Overview Tutorial

Invoice. Transaction Set (810) (Outbound from TI)

ANSI X12 version Text Message

Mazda North American Operations EDI Supplier Documentation October 20, 2015

Manor EDI-Manuel. Purchase Orders ORDERS D96.A EANCOM. Manor AG EDI : Purchase Orders EINFÜHRUNG. 1. Manor Adresse Identifikation. 2.

Portland General Electric Implementation Standard

EDI Implementation Guidelines for Library Book Supply Changes, since issue 1.2

Appendix report 1: Syntax and structure of EDIFACT and XML messages Regulation F1:

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

EDI Compliance Report

ANSI X Product Transfer and Resale Report

EDI specifications. between. BLANCO GmbH + Co KG referred to in the following as BLANCO. and its business partners (suppliers)

D a n s k e B a n k M e s s a g e I m p l e m e n t a t i o n G u i d e

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

810 Invoice ANSI ASC X12 Version 4010

ANSI X12 version Planning Schedule with Release Capability

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

ANSI X12 version Remittance Advice

810 Invoice Revised 01/26/15

Transcription:

EDIFACT DELFOR D99B Guideline 17.09.2013 Version 1.0 www.powersolutions.danfoss.com

Introduction... 2 Legend:... 3 UNB - INTERCHANGE HEADER... 5 UNH - MESSAGE HEADER... 6 BGM - BEGINNING OF MESSAGE... 7 DTM - DATE/TIME/PERIOD... 8 NAD - NAME AND ADDRESS... 9 NAD - NAME AND ADDRESS... 10 GIS - GENERAL INDICATOR... 11 LIN - LINE ITEM... 12 IMD - ITEM DESCRIPTION... 13 SCC - SCHEDULING CONDITIONS... 14 QTY - QUANTITY... 15 DTM - DATE/TIME/PERIOD... 16 UNT MESSAGE TRAILER... 17 UNZ INTERCHANGE TRAILER... 18 Version 1.0 Page 1 from 19

Introduction This document describes the message of a forecast from Danfoss Power Solutions. Due to process changes in purchasing, Danfoss Power Solutions will send only forecast requirements with DELFOR D99B and send firmed (fixed) requirements with the ORDERS D99B message. Danfoss Power Solutions uses the EDIFACT standard D99B. This specification is included as well as examples of its uses. Technical communication Danfoss Power Solutions offers only two communication channels: Value Added Network (VAN) Danfoss Power Solutions currently uses the IBM Sterling B2B Integration network, including interconnects to other networks and communication protocols. Please contact srhelp@us.ibm.com or visit http://www.ibm.com/support. UNB Information Test UNB ID qualifier: ZZ UNB receiver-id: DANFOSSPSTST Production UNB ID qualifier: ZZ UNB receiver-id: DANFOSSPS EDI-Contact: PS.EDI@Danfoss.com Version 1.0 Page 2 from 19

Legend: The following abbreviations are used: Status : M = Mandatory C = Conditional R = Required N = not used Format : an = alphanumeric n = numeric Examples: an..14 n8 alphanumeric, up to 14 digits numeric, eight digits long Version 1.0 Page 3 from 19

Groups UNH Message header M 1 BGM Beginning of message M 1 DTM Date/time/period M 10 ----- Segment group 2 ------------------ C 99---------- NAD Name and address M 1 ----------------------------------------------------------+ ----- Segment group 6 ------------------ C 9999-------- GIS General indicator M 1 ----- Segment group 12 ------------------ C 9999------- LIN Line item M 1 IMD Item description C 10 ----- Segment group 17 ------------------ C 999------- SCC Scheduling conditions M 1 ----- Segment group 18 ------------------ C 999------ QTY Quantity M 1 DTM Date/time/period C 2 --------------------------------------------- 1-------- --------------------------------------------------------- UNT Message trailer M 1 Abbreviations: S = Status, R = Repetitions C = Conditional, M = Mandatory Version 1.0 Page 4 from 19

UNB - INTERCHANGE HEADER Function: To identify an interchange Required Implementation S001 SYNTAX IDENTIFIER M 0001 Syntax identifier M an..4 UNOC 0002 Syntax version number M an..1 3 S002 INTERCHANGE M SENDER 0004 Interchange sender identification M an..35 DANFOSSPS or DANFOSSPSTST 0007 Identification code qualifier 0008 Interchange sender internal identification N N an..4 an..35 S003 INTERCHANGE M RECIPIENT 0010 Interchange recipient M an..35 Sender-ID identification 0007 Identification code N an..4 qualifier 0014 Interchange recipient N an..35 internal identification S004 DATE AND TIME OF M PREPARATION 0017 Date M N6 Actual date (Format = YYMMDD) 0019 Time M n4 Actual time (Format = hhmm) 0020 Interchange control M an..14 Sequential number reference S005 RECIPIENT'S REFERENCE/PASSWO RD DETAILS N C 0022 Recipient M an..14 reference/password 0025 Recipient C an..2 reference/password qualifier 0026 Application reference N an..14 0029 Processing priority code N an..1 0031 Acknowledgement N an..1 request 0032 Interchange agreement N an..35 identifier 0035 Test indicator R n1 1 = TEST, 0 = PROD Version 1.0 Page 5 from 19

UNH - MESSAGE HEADER Function: To identify ans specify a message Required Implementation 0062 Message reference M an..14 Message reference number number S009 MESSAGE M IDENTIFIER 0065 Message type M an..6 DELFOR 0052 Message version M an..3 D number 0054 Message release M an..3 99B number 0051 Controlling agency, M an..3 UN coded 0057 Association assigned N an..6 code 0068 Common access N an..35 reference S010 STATUS OF THE N TRANSFER 0070 Sequence of transfers M n..2 0073 First and last transfer C a1 Version 1.0 Page 6 from 19

BGM - BEGINNING OF MESSAGE Function: To indicate the type and function of a message and to transmit the identifying number. Required Implementation C002 DOCUMENT/MESSAGE R NAME 1001 Document name code R an..3 "241" Delivery schedule 1131 Code list identification code N an..3 3055 Code list responsible N an..3 agency code 1000 Document name N an..35 C106 DOCUMENT/MESSAGE R IDENTIFICATION 1004 Document/message R an..35 Version Number number 1056 Version N an..9 1060 Revision number N an..6 1225 MESSAGE FUNCTION N an..3 CODE 4343 RESPONSE TYPE CODE N an..3 Version 1.0 Page 7 from 19

DTM - DATE/TIME/PERIOD Function: To specify date, and/or time, or period. Required implementation C507 DATE/TIME/PERIOD M 2005 Date/time/period function M an..3 "137" Document/message date/time code qualifier document date 2380 Date/time/period value R an..35 (Format = CCYYMMDDHHMM ) 2379 Date/time/period format code R an..3 "203" Version 1.0 Page 8 from 19

NAD - NAME AND ADDRESS Function: To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207. Required implementation 3035 PARTY FUNCTION CODE M an..3 "ST" (Ship-to-Party) QUALIFIER C082 PARTY IDENTIFICATION R DETAILS 3039 Party identifier M an..35 ship-to-party-number 1131 Code list identification code R an..3 3055 Code list responsible R an..3 "92" assigned by buyer agency code C058 NAME AND ADDRESS N 3124 Name and address line M an..35 3124 Name and address line C an..35 3124 Name and address line C an..35 3124 Name and address line C an..35 3124 Name and address line C an..35 C080 PARTY NAME R 3036 Party name M an..35 party name 3036 Party name N an..35 3036 Party name N an..35 3036 Party name N an..35 3036 Party name N an..35 3045 Party name format code N an..3 C059 STREET R 3042 Street and number/p.o. box M an..35 Street and number 3042 Street and number/p.o. box N an..35 3042 Street and number/p.o. box N an..35 3042 Street and number/p.o. box N an..35 3164 CITY NAME R an..35 City C819 COUNTRY SUB-ENTITY N DETAILS 3229 Country sub-entity name C an..9 code 1131 Code list identification code C an..3 3055 Code list responsible C an..3 agency code 3228 Country sub-entity name C an..35 3251 POSTAL IDENTIFICATION R an..17 Zip code CODE 3207 COUNTRY NAME CODE R an..3 country code Version 1.0 Page 9 from 19

NAD - NAME AND ADDRESS Function: To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 thru 3207. Required implementation 3035 PARTY FUNCTION CODE M an..3 "SU" (Supplier) QUALIFIER C082 PARTY IDENTIFICATION R DETAILS 3039 Party identifier M an..35 Supplier-number 1131 Code list identification code R an..3 3055 Code list responsible R an..3 "92" assigned by buyer agency code C058 NAME AND ADDRESS N 3124 Name and address line M an..35 3124 Name and address line C an..35 3124 Name and address line C an..35 3124 Name and address line C an..35 3124 Name and address line C an..35 C080 PARTY NAME R 3036 Party name M an..35 party name 3036 Party name N an..35 3036 Party name N an..35 3036 Party name N an..35 3036 Party name N an..35 3045 Party name format code N an..3 C059 STREET R 3042 Street and number/p.o. box M an..35 Street and number 3042 Street and number/p.o. box N an..35 3042 Street and number/p.o. box N an..35 3042 Street and number/p.o. box N an..35 3164 CITY NAME R an..35 City C819 COUNTRY SUB-ENTITY N DETAILS 3229 Country sub-entity name C an..9 code 1131 Code list identification code C an..3 3055 Code list responsible C an..3 agency code 3228 Country sub-entity name C an..35 3251 POSTAL IDENTIFICATION R an..17 Zip code CODE 3207 COUNTRY NAME CODE R an..3 country code Version 1.0 Page 10 from 19

GIS - GENERAL INDICATOR Function: To transmit a processing indicator. Required implementation C529 PROCESSING M INDICATOR 7365 Processing indicator M an..3 "37" Complete information description code 1131 Code list identification code N an..3 3055 Code list responsible N an..3 agency code 7187 Process type description code N an..17 Version 1.0 Page 11 from 19

LIN - LINE ITEM Function: To identify a line item and configuration Required implementation 1082 LINE ITEM NUMBER N an..6 1229 ACTION N an..3 REQUEST/NOTIFICATION DESCRIPTION CODE C212 ITEM NUMBER R IDENTIFICATION 7140 Item number R an..35 item number 7143 Item type identification R an..3 "IN" Buyer's item number code 1131 Code list identification code N an..3 3055 Code list responsible N an..3 agency code C829 SUB-LINE INFORMATION N 5495 Sub-line indicator, coded C an..3 1082 Line item number C an..6 1222 CONFIGURATION LEVEL N n..2 7083 CONFIGURATION, CODED N an..3 Version 1.0 Page 12 from 19

IMD - ITEM DESCRIPTION Function: To describe an item in either an industry or free format Required implementation 7077 ITEM DESCRIPTION N an..3 TYPE, CODED C272 ITEM CHARACTERISTIC N 7081 Item characteristic code C an..3 1131 Code list identification code C an..3 3055 Code list responsible C an..3 agency code C273 ITEM DESCRIPTION R 7009 Item description N an..17 BP Buyer s part identification 1131 Code list identification code N an..3 3055 Code list responsible N an..3 agency code 7008 Item description R an..256 Article description 7008 Item description N an..256 3453 Language name code N an..3 7383 SURFACE/LAYER CODE N an..3 Version 1.0 Page 13 from 19

SCC - SCHEDULING CONDITIONS Function: To specify scheduling conditions. Required implementation 4017 DELIVERY PLAN M an..3 "4" Planning / forecast COMMITMENT LEVEL CODE 4493 DELIVERY INSTRUCTION, N an..3 CODED C329 PATTERN DESCRIPTION N 2013 Frequency code C an..3 2015 Despatch pattern, coded C an..3 2017 Despatch pattern timing, coded C an..3 Danfoss Power Solutions will send only forecast requirements with DELFOR D99B and send firmed (fixed) requirements with the ORDERS D99B message. Version 1.0 Page 14 from 19

QTY - QUANTITY Function: To specify a pertinent quantity. Required implementation C186 QUANTITY DETAILS M 6063 Quantity type code qualifier M an..3 "113" quantity to be delivered 6060 Quantity M an..35 quantity 6411 Measurement unit code R an..3 "PCE / MTR / KGM / a.s.o." Version 1.0 Page 15 from 19

DTM - DATE/TIME/PERIOD Function: To specify date, and/or time, or period. Required implementation C507 DATE/TIME/PERIOD M 2005 Date/time/period function M an..3 "2 Delivery date / time, requested code qualifier 2380 Date/time/period value R an..35 Requested deilvery date (Format CCYYMMDD ) 2379 Date/time/period format code R an..3 "102" Version 1.0 Page 16 from 19

UNT MESSAGE TRAILER Function: To end and check the completeness of a message. Required Implementation 0074 Number of segments in a M n..10 message 0062 Message reference number M an..14 Version 1.0 Page 17 from 19

UNZ INTERCHANGE TRAILER Function: To end and check the completeness of an interchange. Required Implementation Interchange control M n..6 0036 count 0020 Interchange control reference M An..14 Version 1.0 Page 18 from 19

Overview of a file with groups and notes ----------------------- SG02 ----------------------- SG02 UNH+<Message reference number>+delfor:d:99b:un' BGM+241+<Number>+5' DTM+137:<Document date>:203' NAD+ST+<Ship to>::92++<ship-tp party name+ <Street>+<City>++<Zip Code>+<Country>' NAD+SU+<Supplier>::92++<Supplier+ <Street>+<City>++<Zip Code>+<Country>' ----------------------- SG06 GIS+37' ------------------ SG12 LIN+++<Danfoss material number>:in' IMD+++:::<Article description>' ------------ SG17 SCC+4' 4 = Forecast ------ SG18 QTY+1:<Quantity>:PCE' DTM+2:<requested delivery date>:102' ---- ----- ----- ------ UNT+12+<Message reference number>' The following abbreviations are used: Status : M = Mandatory, C = Conditional, R = Required, N = not used Format : an = alphanumeric, n = numeric Examples: an..14 alphanumeric, up to 14 digits N8 numeric, eight digits long Version 1.0 Page 19 from 19