B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1...

129
B2B EDI Interchange SIAM-ACMA Initiative

Transcript of B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1...

Page 1: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

B2B EDI Interchange SIAM-ACMA Initiative

Page 2: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

2

Contents

1 SIAM – ACMA Business 2 Business Electronic Data Interchange

Initiative 5

1.1 Overview of the Initiative 5

1.2 Existing State of Data Interchange in the Industry 5

1.3 Business Case for Standardized Electronic Interchange 7

1.4 Proposed Standard 8

1.5 Benefits Envisaged 9

2 Proposed Data interchange flow 11

3 The EDI Standards 11

3.1 EDI Document– Purchase Order 11

3.1.1 Pre Requisite for the EDI – Sender’s End 11

3.1.2 Pre Requisite for the EDI – Receiver’s End 11

3.1.3 Triggers at Sender’s End 11

3.1.4 Triggers at Receiver’s End 11

3.1.5 Governance 11

3.1.6 High Level Document Flow 13

3.1.7 Definition of EDI Standards 14

3.2 EDI Document - DELFOR 21

3.2.1 Pre Requisite for the EDI – Sender’s End 21

3.2.2 Pre Requisite for the EDI – Receiver’s End 21

3.2.3 Triggers at Sender’s End 21

3.2.4 Triggers at Receiver’s End 21

3.2.5 Governance 21

3.2.6 High Level Document Flow 22

3.2.7 Definition of EDI Standard 23

3.3 EDI Document - DELJIT 28

3.3.1 Pre Requisite for the EDI – Sender’s End 28

3.3.2 Pre Requisite for the EDI – Receiver’s End 28

3.3.3 Triggers at Sender’s End 28

3.3.4 Triggers at Receiver’s End 28

3.3.5 Governance 28

3.3.6 High Level Document Flow 30

3.3.7 Definition of EDI Standard 31

3.4 EDI Document – Consignment Number (DESADV) 36

3.4.1 Pre Requisite for the EDI – Sender’s End (Method 1) 36

3.4.2 Pre Requisite for the EDI – Receiver’s End (Method 1) 36

3.4.3 Triggers at Sender’s End (Method 1) 36

3.4.4 Triggers at Receiver’s End (Method 1) 36

Page 3: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

3

3.4.5 High Level Document Flow - Method 1 (Consignment Number generated

by OEM) 37

3.4.6 Pre Requisite for the EDI – Sender’s End (Method 2) 38

3.4.7 Pre Requisite for the EDI – Receiver’s End (Method 2) 38

3.4.8 Triggers at Sender’s End (Method 2) 38

3.4.9 Triggers at Receiver’s End (Method 2) 38

3.4.10 Governance (Method 2) 38

3.4.11 High Level Document Flow - Method 2 (Consignment Number generated

by Supplier) 40

3.4.12 Definition of EDI Standard 41

3.5 EDI document - Invoice 47

3.5.1 Pre Requisite for the EDI – Sender’s End 47

3.5.2 Pre Requisite for the EDI – Receiver’s End 47

3.5.3 Triggers at Sender’s End 47

3.5.4 Triggers at Receiver’s End 47

3.5.5 Governance 48

3.5.6 High Level Document Flow 49

3.5.7 Definition of EDI Standards 50

3.6 EDI Document – Gate Pass 59

3.6.1 Pre Requisite for the EDI – Sender’s End 59

3.6.2 Pre Requisite for the EDI – Receiver’s End 59

3.6.3 Triggers at Sender’s End 59

3.6.4 Triggers at Receiver’s End 59

3.6.5 Governance 59

3.6.6 Definition of EDI Standard 60

3.7 EDI Document – Goods Inspection Report 62

3.7.1 Pre Requisite for the EDI – Sender’s End 62

3.7.2 Pre Requisite for the EDI – Receiver’s End 62

3.7.3 Triggers at Sender’s End 62

3.7.4 Triggers at Receiver’s End 62

3.7.5 Governance 62

3.7.6 High Level Document Flow 64

3.7.7 Definition of EDI Standards 65

3.8 EDI Document – Goods Receipt Note 69

3.8.1 Pre Requisite for the EDI – Sender’s End 69

3.8.2 Pre Requisite for the EDI – Receiver’s End 69

3.8.3 Triggers at Sender’s End 69

3.8.4 Triggers at Receiver’s End 69

3.8.5 Governance 69

3.8.6 High Level Document Flow 71

3.8.7 Definition of EDI Standard 72

3.9 EDI document-Goods Rejection Note 78

3.9.1 Pre Requisite for the EDI – Sender’s End 78

3.9.2 Pre Requisite for the EDI – Receiver’s End 78

3.9.3 Triggers at Sender’s End 78

3.9.4 Triggers at Receiver’s End 78

Page 4: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

4

3.9.5 Governance 78

3.9.6 High Level Document Flow 80

3.9.7 Definition of EDI Standard 81

3.10 EDI Document – Debit Note 89

3.10.1 Pre Requisite for the EDI – Sender’s End 89

3.10.2 Pre Requisite for the EDI – Receiver’s End 89

3.10.3 Triggers at Sender’s End 89

3.10.4 Triggers at Receiver’s End 89

3.10.5 Governance 89

3.10.6 High Level Document Flow 90

3.10.7 Definition of EDI Standard 91

3.11 EDI Document – Credit Note 96

3.11.1 Pre Requisite for the EDI – Sender’s End 96

3.11.2 Pre Requisite for the EDI – Receiver’s End 96

3.11.3 Triggers at Sender’s End 96

3.11.4 Triggers at Receiver’s End 96

3.11.5 Governance 96

3.11.6 High Level Document Flow 97

3.11.7 Definition of EDI Standard 98

3.12 EDI Document – Remittance Advice 103

3.12.1 Pre Requisite for the EDI – Sender’s End 103

3.12.2 Pre Requisite for the EDI – Receiver’s End 103

3.12.3 Triggers at Sender’s End 103

3.12.4 Triggers at Receiver’s End 103

3.12.5 Governance 103

3.12.6 High Level Document Flow 104

3.12.7 Definition of EDI Standard 105

3.13 EDI Document – Purchase Order Amendment 110

3.13.1 Pre Requisite for the EDI – Sender’s End 110

3.13.2 Pre Requisite for the EDI – Receiver’s End 110

3.13.3 Triggers at Sender’s End 110

3.13.4 Triggers at Receiver’s End 110

3.13.5 Governance 110

3.13.6 Definition of EDI Standard 111

3.14 EDI Document – Price Catalogue 121

3.14.1 Pre Requisite for the EDI – Sender’s End 121

3.14.2 Pre Requisite for the EDI – Receiver’s End 121

3.14.3 Triggers at Sender’s End 121

3.14.4 Triggers at Receiver’s End 121

3.14.5 Governance 121

3.14.6 Definition of EDI Standard 122

4 List of Contributors 127

4.1.1 Report Contribution 127

4.1.2 Survey and/or Workshop Contribution 128

Page 5: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

5

1 SIAM – ACMA Business 2 Business Electronic Data Interchange Initiative

1.1 Overview of the Initiative

Society of Indian Automobile Manufacturers (SIAM) and Automotive Component Manufacturers

Association of India (ACMA) have agreed to adopt an industry standard data interchange

mechanism for all OEMs and suppliers to exchange data. The mechanism based on Electronic Data

Interchange (EDI) standard adopted from international standards and localized specifically for

Indian Automotive Industry is recommended for implementation at OEMs and suppliers to ensure

consistency of data interchange.

In the first phase of this project, the data interchange standard covers the Purchase to Pay Cycle at

Automobile Manufacturers and the Order to Cash Cycle at Automotive Component Manufacturers.

The draft standard is published herewith. We invite the Automobile Manufacturers and

Automotive Component Manufacturers to review the draft standard, and provide us with inputs

before 31st December 2011in order to finalize the same.

Society of Indian Automobile Manufacturers

(SIAM)

Amit Kumar

Automotive Component Manufacturers

Association of India (ACMA)

Chairman IT Manager (Tech) Society of Indian Automobile Manufacturers Core 4B, 5th Floor, India Habitat Centre Lodi Road, New Delhi – 110003, India Phone: +91-11-47103021, Email: [email protected]

The Capital Court

6th Floor, Olof Palme Marg,

Munirka,

New Delhi – 110067

Email : [email protected]

1.2 Existing State of Data Interchange in the Industry

Supply predictability, ease of inventory movement recording, electronic transmission of supply and

commercial information to avoid duplication of data entry, have been important drivers for the

Indian Automotive Industry which has seen a number of steps that have been taken to improve

systems interfaces. Some typical transactions include:

• Scheduling of delivery of auto components

• Information on quality inspection data

• Delivery of invoicing instructions

• Dispatch intimation

Page 6: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

6

• Payment intimation

While such innovations have aided supply chain efficiencies, the lack of an industry-wide standard

mechanism of data interchange has led to process or people related inefficiencies due to a variety of

factors, including:

• Multiplicity of applications and portals

• Difference in transaction data formats

• Front end technology mismatches

• Limited integration

• Change management across multiple platforms

Consider the figure below:

Page 7: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

7

1.3 Business Case for Standardized Electronic Interchange

Limited integration between applications, multiplicity of data interchange mechanisms and

formats, can result in supply chain visibility issues, which can lead to:

• Inefficient inventory management of similar parts used by different OEMs resulting in part

shortages or excess capacity.

• Inefficient and ineffective management of product failure information from different OEMs

resulting in higher warranty costs.

• Increased manpower to manage and process supply chain transactions across multiple

platforms

• Duplication of data entry especially where data is still communicated through phone, fax or e-

mail based mechanisms

Page 8: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

8

• Higher risk to business because systems and processes become person dependent.

• Problems in reconciliation of debits/ credits.

• Problems in bank reconciliation, etc.

A common industry platform and solution for data interchange can help in reducing these supply

chain inefficiencies.

1.4 Proposed Standard

Given these imperatives, SIAM and ACMA have conducted a study to understand the current state of

data interchange, problems and challenges faced, and have arrived at the UN/EDIFACT standard as

a reference model. The following steps were undertaken:

• Arrive at a list of EDIFACT transactions that are required in the current OEM Purchase to Pay

and Component Manufacturer’s Order to Cash Cycle

• Perform a survey of selected OEM and Component Manufacturers to understand current forms

of data interchange, data formats and fields exchanged, in order to identify unique fields that

are specific to the Indian automotive industry or are statutorily applicable in India.

• Perform workshops across Chennai, Bangalore, Pune and Delhi with selected OEM and

Component Manufacturers in order to debrief the survey findings as well as discuss the new

standard proposed, which added India localization fields to the EDIFACT standard

• Identify document types that are not available in EDIFACT but are widely interchanged in India.

The Gate Pass (IND_GP) document type was hence identified.

Based on feedback received from the workshops, the draft standards have been published herewith

for feedback. The draft standards include the following EDI transaction types:

• Purchase Order (ORDERS)

• Purchase Order Amendment (ORDCHG)

• Delivery Forecast (DELFOR)

• Delivery Schedule (DELJIT)

• Consignment Number (DESADV)

Page 9: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

9

• Supplier Invoice (INVOIC)

• Gate Pass (IND_GP)

• Goods Inspection Report (INSRPT)

• Goods Receipt Note (RECADV)

• Goods Rejection Note (RETANN)

• Debit Note (DEBADV)

• Credit Note (CREADV)

• Remittance Advice (REMADV)

• Price Catalogue (PRICAT)

1.5 Benefits Envisaged

It is envisaged that the B2B Initiative would lead to better responsiveness and more robust

exchange of data. Cost savings would come from sharing of system resources and improved

effectiveness of system support staff.

Following benefits are envisioned as a result of a standard data interchange mechanism:

• The processes would be streamlined as implementation of EDI would mandate changes in the

method of processing business documents and elimination of processes built around manual

paper handling.

• The structure of documents would be standardized for exchange between OEMs and Suppliers.

This would create an efficient ecosystem for running business.

• The trading partners would be able to make informed decisions due to improved flow of

important and relevant information. This would ultimately result in reduced cycle times.

Page 10: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

10

• Since, each EDI message type would have pre-requisites and triggers to other EDI message

types, it would be easy to link relevant the business documents thereby resulting in reduction of

payment reconciliation issues.

• EDI messages would act as the single source for data exchanged between the trading partners.

Communication via other media such as email, hard copies (in case documents are not legal and

hence require hard formats), phone etc would be eliminated resulting in effective planning and

reporting.

• Since each EDI message references an earlier EDI in the supply chain transaction ID, the entire

cycle of purchase orders through payments becomes easier for reconciliation.

• Data inconsistencies and process inefficiencies can be reduced by elimination of multiple

manual interventions for data entry.

Page 11: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

11

2 Proposed Data interchange flow

The data interchange flow proposed below would be based on the new EDI standards defined as a part of the project. The RED text highlights the reference numbers that will help in financial reconciliations.

Supplier

OEM

Page 12: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

11

3 The EDI Standards

3.1 EDI Document– Purchase Order

3.1.1 Pre Requisite for the EDI – Sender’s End

After the finalization of contract between OEM and supplier, EDI for contract would have

been triggered from OEM to the supplier. The negotiated price details are available in the

contract number. Production Plan or an MRP run would trigger the need for PO, if

required.

3.1.2 Pre Requisite for the EDI – Receiver’s End

The customer contract reference number should have been updated in the supplier’s

system/ ERP. The incoming PO EDI message would need to be referenced with the

customer contract reference.

3.1.3 Triggers at Sender’s End

PO number would be mapped to the contract number and the negotiated price details as

per the contract would be available for the parts ordered in the PO. This makes the parts

available for delivery forecast and delivery scheduling.

3.1.4 Triggers at Receiver’s End

PO generated by the OEM in its system/ ERP, would trigger the EDI message type for PO

with details such as goods and the related quantity ordered, negotiated price, payment

and delivery terms etc. As is understood, that static data such as Customer name, Tax

details, Legal Registration Numbers (TIN, ESS, PAN etc) Amount in words etc. will not be

passed through EDI process but would be stored in Masters both at OEM and Supplier’s

end.

The PO details would be converted to the Sales Order details for the supplier and an SO

number is generated.

The approved PO details (as per EDI) would be available for suppliers to update the same

in their ERP system. The details would be utilized for Delivery Schedules.

All updates to negotiated price would trigger a notification to the supplier.

3.1.5 Governance

• Sender

Page 13: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

12

- PO number should be mapped to the contract number.

- The negotiated price as per the contract should be updated in the ERP.

- Changes in pricing should be notified to the supplier for updating the price

master. An amendment PO would be created which would be mapped to the

blanket PO.

• Receiver

- Sales Order (SO) should be created exactly as per the details in the PO.

- PO details to be mapped to Sales Order Number for referencing.

- Parts/ assemblies to be delivered to the OEM based on the PO details

mentioned in the delivery schedule

Page 14: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

13

3.1.6 High Level Document Flow

Page 15: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

14

3.1.7 Definition of EDI Standards

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header- Purchase

Order

UNH-062 A service segment starting

and uniquely identifying a

message. The message type

code for purchase orders is

"Orders"

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group (If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group (If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group (If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier -

Controlling Agency Coded.

UNH-S009-0051 The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group(If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Purchase Order Name BGM-C002-1001-105 To indicate the type and

function of a message and to

transmit the identifying

number.

Header Mandatory Alphanumeric 3

Page 16: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

15

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

7

Parties and Instruction

Customer code INP-C849-3301 - 4 To identify the party

enacting an instruction

Header Mandatory Alphanumeric 3

8

Parties and Instruction

Supplier /Vendor Code INP-C849-3301 - 5 Code qualifying a reference Header Mandatory Alphanumeric 3

9 Reference fields – PO Purchase Order Number RFF-C506-1153-OP To indicate the type and

function of a message and to

transmit the identifying

number.

Header Mandatory Alphanumeric 3

10 Reference Field Amendment number RFF-C506-1153- To specify a reference. Header Optional Alphanumeric 3

11 Reference Field Party Ref No. REF-C506-1153- To specify a reference Header Mandatory Alphanumeric 3

12 Date/Time/Period PO Date DTM-C507-2005-4 To specify a date, and or time

period

Header Mandatory Alphanumeric 3

13 Date/Time/Period Date of Amendment DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

14 Date/Time/Period Expected Del. Date DTM-2005-2 To specify a reference Header Mandatory Alphanumeric 3

15 Date/Time/Period Party Ref Date DTM-C507-2005 To specify date, and or Time Header Mandatory Alphanumeric 3

16 Date/Time/Period Print Date DTM-C507-2005 To specify a date, and or time

period

Header Mandatory Alphanumeric 3

Page 17: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

16

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

17 Name and Address Bill To Address NAD-3035-AA To Specify the name/address

and their related function .

Header Mandatory Alphanumeric 3

18 Name and Address Ship To address NAD-3035-ST To Specify the name/address

and their related function .

Header Mandatory Alphanumeric 3

19 Free Text Information Sales of good strictly prohibited FTX-C108 - 4440 To provide free form or

coded text information

Header Optional Alphanumeric 512

20 Document/Message Details.1 DOC-C002-1001-105 To identify documents and

details directly related to it.

Header Mandatory Alphanumeric 3

21 PO Category Name India Unique To Header Mandatory Alphanumeric 20

22 Contact Information Contact Person CTA- 3139- To identify a person or a

department to whom

communication should be

directed.

Header Mandatory Alphanumeric 35

23 Communication Contact Buyer E-mail, Telephone COM-C076-3148 To identify a communication

number of a department or a

person to whom

communication should be

addressed.

Header Optional Alphanumeric 512

24 Communication Contact Buyer Contact No. CTA-C056-3412 To identify a communication

number of a department or a

person to whom

communication should be

addressed.

Header Optional Alphanumeric 17

25 Free Text Part Category: Mass Production,

after sales, raw materials,proto-type

,vendor tooling.

FTX-C108 - 4440 To provide free form or

coded text information

Header Optional Alphanumeric 512

26 Duty/Tax/Fee Details Sales Tax TAX-C241-5153- Code specifying a type of

duty, tax or fee.

Detail Optional Alphanumeric 3

27 Duty/Tax/Fee Details Excise duty/Tax TAX-C241-5153-EXC Code specifying a type of

duty, tax or fee.

Detail Optional Alphanumeric 3

28 Currency INR- Currency CUX-C504-6437 To specify currencies used in

transaction and relevant

details for the rate of

exchange

Header Mandatory Alphanumeric 3

29 Payment Terms Payment Terms PYT - 4279 To specify the terms of

payment

Header Mandatory Alphanumeric 3

30 Monetary Details MOA-C516 To specify a monetary

amount

Header Mandatory

1 This field may be useful in future

Page 18: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

17

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

31 Transport Information TDT-8051 To Specify information

regarding the transport such

as mode of transport.

Header Mandatory Alphanumeric 3

32 Location /Place Identification Plant Dc/Name/Storage location LOC-3227 To Identify a place or a

location and or related

locations.

Detail Mandatory Alphanumeric 3

33 Terms of Delivery Terms of delivery notification TOD-4055 To specify terms of delivery Header Mandatory Alphanumeric 3

34 Package Details PAC-7224 To describe the number and

type of package/physical

units.

Header Mandatory

35 Package Identification PCI-C210-7102 To specify marking and

labels on individual packages

or physical units.

Header Mandatory Alphanumeric 35

36 Equipment Details EQD-8053 To identify a unit of

equipment

Header Mandatory Alphanumeric 3

37 Scheduling conditions. SCH-4017 To specify scheduling

conditions.

Header Mandatory Alphanumeric 3

38 Quantity QTY-C186-6063 To specify a pertinent

quantity

Header Mandatory Alphanumeric 3

39 Quantity Measurement Unit code QTY-C186-6411 To specify a pertinent

quantity

Detail Optional Alphanumeric 3

40 Additional Price information Price Terms Apr-43 To provide information

concerning pricing related to

class of trade.

Header Mandatory Alphanumeric 3

41 Allowance or Charge ALC-5463 To Identify an allowance or

charge details

Header Mandatory Alphanumeric 3

42 Quantity QTY-C186-6063 To specify a pertinent

quantity

Header Mandatory Alphanumeric 3

43 Percentage Details PCD-C501-5245 To specify percentage

Information

Header Mandatory Alphanumeric 3

44 Monetary Details MOA-C516 To specify a monetary

amount

Header Mandatory

45 Rate Details. RTE-C128-5420 To specify rate information Header Mandatory Numeric 15

46 Tax/Duty/Fee details TAX-5283 To specify relevant

duty/tax/fee information.

Header Mandatory Alphanumeric 3

47 Requirement and conditions RCS-7293 To specify sector/subject

requirements and conditions

Header Mandatory Alphanumeric 3

48 Dangerous goods DGS-C205 To identify dangerous goods. Header Mandatory Alphanumeric 3

Page 19: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

18

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

49 Lin No. Sr.No LIN-7143-SN To Identify a line Item and

configuration

Detail Mandatory Alphanumeric 3

50 Additional Product ID Part No. PIA-7143-BH Coded identification of an

item type

Detail Optional Alphanumeric 3

51 Item Description Item Code IMD- C272-7081 To describe an item in either

an industry or free format

Detail Optional Alphanumeric 17

52 Additional Product ID Material Code/Part Code PIA-7143-BH Coded identification of an

item type

Detail Optional Alphanumeric 3

53 Additional Product ID Part Description/Material

description

PIA-7143-PD Coded identification of an

item type

Detail Optional Alphanumeric 3

54 Measurements Unit of Measure` MEA-6311-ABW Code qualifying the purpose

of the measurement.

Detail Optional Alphanumeric 3

55 Characteristic/Class ID CCI-7059 To Identify and describe a

specific characteristic.

Detail Mandatory Alphanumeric 3

56 Payment Terms PYT-C019-2152 To specify the terms of

payment

Detail Mandatory Alphanumeric 3

57 Monetary Details Sub Total/Line items total MOA-C516-5125-66 To specify a monetary

amount

Detail Mandatory Alphanumeric 3

58 Price Details. Price of line item per unit PRI-C509-5379-PU Code qualifying the type of

monetary amount.

Detail Mandatory Alphanumeric 3

59 Monetary Details Good line item amount MOA-C516-5025-66 To describe a pertinent

amount

Detail Mandatory Alphanumeric 3

60 Monetary Details Total line Amount MOA-C516-5025-79 To describe a pertinent

amount

Detail Mandatory Alphanumeric 3

61 Date/Time/Period Price effective date DTE-C507-2005 To specify a date, and or time

period

Detail Optional Alphanumeric 3

62 Reference Field REF-C506-1153 To specify a reference. Detail Mandatory Alphanumeric 3

63 Package Details PAC-7224 To describe the number and

type of package/physical

units.

Detail Mandatory

64 Reference Field REF-C506-1153 To specify a reference. Detail Mandatory Alphanumeric 3

65 Quantity Measurements/Unit QTY-C185-6411 To specify a pertinent

Quantity

Detail Mandatory Alphanumeric 8

Page 20: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

19

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

66 Package Identification Container type PCI-C531-7233 To specify marking and

labels on individual packages

or physical units.

Detail Mandatory Alphanumeric 35

67 Location /Place Identification Plant Dc/Name/Storage location LOC-3227 To Identify a place or a

location and or related

locations.

Detail Mandatory Alphanumeric 3

68 Tax/Duty/Fee details Excise duty/Tax TAX-C241-5153-EXC Code specifying a type of

duty, tax or fee.

Detail Optional Alphanumeric 3

69 Name and Address NAD-3035 To specify the name/address

and their related function.

Detail Mandatory Alphanumeric 3

70 Reference Field Drawing doc number REF-C506-1153-AAL To specify a reference. Detail Mandatory Alphanumeric 3

71 Document/Message Details. DOC-C002 To identify documents and

details directly related to it.

Detail Mandatory Alphanumeric 3

72 Contact Information Contact Person name/department CTA-C3139 To indentify a person or

department to whom the

communication should be

directed.

Detail Mandatory Alphanumeric 3

73 Allowance or Charge ALC-5463 To Identify an allowance or

charge details

Detail Mandatory Alphanumeric 3

74 Quantity PO Quantity QTY-C186-6060 To specify a pertinent

quantity.

Detail Mandatory Alphanumeric 35

75 Percentage Details Discount expressed as percentage PCD-C501-5245-12 To specify percentage

Information

Detail Mandatory Alphanumeric 3

76 Monetary Details Total Amount/Value MOA-C516-5025-77 To specify a monetary

amount

Detail Mandatory Alphanumeric 35

77 Rate Details Rate RTE-C128- 5420 To specify rate information. Detail Mandatory Numeric 15

78 Terms of Delivery Terms of delivery notification TOD-4055 To specify terms of delivery Detail Mandatory Alphanumeric 3

79 Equipment Details EQD-8053 To identify a unit of

equipment

Detail Mandatory Alphanumeric 3

80 Scheduling conditions. SCH-4017 To specify scheduling

conditions.

Detail Mandatory Alphanumeric 3

81 Quantity QTY-C6060 To specify a pertinent

quantity.

Detail Mandatory Alphanumeric 35

82 Requirement and conditions RCS-7293 To specify sector/subject

requirements and conditions

Detail Mandatory Alphanumeric 3

Page 21: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

20

Purchase Order (ORDERS)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

83 Stages STG-9421 To provide information

related to the kind of stage

in process.

Detail Mandatory Alphanumeric 3

84 Quantity QTY-C6060 To specify a pertinent

quantity.

Detail Mandatory Alphanumeric 35

85 Dangerous goods DGS-8273 To identify dangerous goods. Detail Mandatory Alphanumeric 3

86 Contact Information CTA-C3139- To indentify a person or

department to whom the

communication should be

directed.

Detail Mandatory Alphanumeric 3

87 Section Control UNS-0081 To separate the header,

detail and summary sections

of the message.

Trailer Mandatory Alphanumeric 1

88 Allowance or Charge ALC-5463 To Identify an allowance or

charge details

Trailer Mandatory Alphanumeric 3

89 Free Text Information Amount in words MOAC516-5025 To provide free form or

coded text information

Detail Optional Alphanumeric 512

90 Free Text Information Terms of conditions FTX-C108 - 4440 To provide free form or

coded text information

Trailer Optional Alphanumeric 512

91 Free Text Information Authorized Signatory FTX-C108 - 4440 To provide free form or

coded text information

Trailer Optional Alphanumeric 512

92 Message trailer UNT-0074 To end and check the

completeness of the message

Trailer Mandatory Alphanumeric 10

93 Message trailer UNT-0062 To end and check the

completeness of the message

Trailer Mandatory Alphanumeric 14

Page 22: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

21

3.2 EDI Document - DELFOR

3.2.1 Pre Requisite for the EDI – Sender’s End

Delivery forecast is prepared based on the MRP generated for the production plan. The PO

EDI message type should have been executed for parts for which forecast is generated.

3.2.2 Pre Requisite for the EDI – Receiver’s End

EDI message type for an SO number should have been created for the delivery forecast to

be referenced to the SO number.

3.2.3 Triggers at Sender’s End

Generation of delivery forecast would provide a trigger for production planning at the

supplier’s end. EDI for delivery schedule (DELJIT) would be triggered by the OEM after the

EDI for delivery forecast has been shared with the supplier.

3.2.4 Triggers at Receiver’s End

Once the EDI for delivery forecast is received by the supplier, it is required to acknowledge

the receipt of the forecast details which is provided using the EDI message for

acknowledgement (such as APERAK in UN/ EDIFACT).

Delivery forecast would then be referenced to the internal Sales Order Number (optional).

3.2.5 Governance

• Sender

- Frequency of forecasting and the forecast period needs to be fixed by each OEM

at its end.

- Delivery Schedule should not be created before the creation of the Delivery

Forecast

• Receiver

- Delivery forecast can be referenced to the Sales Order number of the supplier

which in turn would be referenced to the PO number. However, this

requirement is not mandatory and can be implemented based on business

need.

- Parts/ assemblies to be delivered to the OEM based on the PO details

mentioned in the delivery schedule

Page 23: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

22

3.2.6 High Level Document Flow

Note - The Consignment number could be sent with DELJIT or could be created by the supplier after the confirmation of the delivery. This would depend on the

process agreed between the trading partners.

Page 24: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

23

3.2.7 Definition of EDI Standard

Delivery Forecast (DELFOR)

Origin of Document - OEM

S. No EDIFACT - Field Name Provided Sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header UNH-062 To head ,identify and specify a

message - DELFOR

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not used,

within the interchange, for the

purpose of acknowledgement. -

DELFOR

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not used,

within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not used,

within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

Page 25: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

24

Delivery Forecast (DELFOR)

Origin of Document - OEM

S. No EDIFACT - Field Name Provided Sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not used,

within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Devilry Schedule BGM-C002-1001-236 To indicate the type and function of

a message and to transmit the

identifying a number

Header Mandatory Alphanumeric 3

7 Free Text Information Text Information FTX-C108-444- To specify free text information or

coded text information

Header Optional Alphanumeric 512

8 Name and Address Supplier name NAD-3035-VN To specify the name/address and

their related function.

Header Mandatory Alphanumeric 3

9 Name and Address Buyer name and

address printed.

NAD-3035-BY To specify the name/address and

their related function.

Header Mandatory Alphanumeric 3

10 Free Text Information Free Text FTX-C108-444- To provide free text information Header Optional Alphanumeric 512

11 Date/Time/Period Forecast Period DTM-C507-2005-419 To specify a date/time period. Header Mandatory Alphanumeric 3

12 Date/Time/Period Forecast Period Start DTM-C507-2005-663 To specify a date/time period. Header Mandatory Alphanumeric 3

13 Date/Time/Period Forecast Period End DTM-C507-2005-674 To specify a date/time period. Header Mandatory Alphanumeric 3

14 Reference Field Supplier code REF-C506-1153-VR To specify a reference Header Mandatory Alphanumeric 3

15 Contact Information CTA-3139 To identify a person or a

department to whom the

communication should be directed.

Header Mandatory Alphanumeric 3

Page 26: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

25

Delivery Forecast (DELFOR)

Origin of Document - OEM

S. No EDIFACT - Field Name Provided Sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

16 Transport Information TDT-8051 To specify information regarding

transport such as mode of

transport, means of transport etc..

Header Mandatory Alphanumeric 3

17 Processing Information GEI-9649 To indentify processing

information.

Header Mandatory Alphanumeric 3

18 Name and Address Supplier Information NAD-3035-VN

To specify the name/address and

their related function. Header Mandatory Alphanumeric 3

19 Reference Field REF-C506-1153 To specify a reference Header Mandatory Alphanumeric 3

20 Document /Message Details DOC-C002-1001-236

To identify documents and details

directly related to it. Header Mandatory Alphanumeric 3

21 Contact Information CTA-3139

To identify a person or a

department to whom the

communication should be directed. Header Mandatory Alphanumeric 3

22 Transport Information TDT-8051

To specify information regarding

transport such as mode of

transport, means of transport etc.. Header Mandatory Alphanumeric 3

23 Line item Sr.No.

LIN-7143-SN To Indentify a line item and

configuration Detail Mandatory Alphanumeric 3

24 Item Description Part name IMD-7077

To describe an item in either an

industry or free format Detail Optional Alphanumeric 3

25 Item Description Engine Type IMD-7077

To describe an item in either an

industry or free format Detail Optional Alphanumeric 3

26 Item Description Model IMD-7077

To describe an item in either an

industry or free format Detail Optional Alphanumeric 3

27 Adina Product Part No.

PIA-7143-BH To describe an item in either an

industry or free format Detail Optional Alphanumeric 3

Page 27: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

26

Delivery Forecast (DELFOR)

Origin of Document - OEM

S. No EDIFACT - Field Name Provided Sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

28 Reference Field REF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

29 Contact Information CTA-3139

To identify a person or a

department to whom the

communication should be directed. Detail Mandatory Alphanumeric 3

30 Transport Information TDT-8051

To specify information regarding

transport such as mode of

transport, means of transport etc.. Detail Mandatory Alphanumeric 3

31 Quantity Confirmed quantity QTY-C186-6063- To specify a pertinent quantity Detail Mandatory Alphanumeric 3

32 Quantity Line Wise total QTY-C186-6063-142 To specify a pertinent quantity Detail Optional Alphanumeric 3

33 Reference Field REF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

34 Scheduling conditions - Firm Firm Schedule SCH - 4017- 1 To specify scheduling conditions Detail Mandatory Alphanumeric 3

35 Quantity

Standard Invoice

quantity

QTY-C186-6063-47 To specify a pertinent quantity Detail Mandatory Alphanumeric 3

36 Reference Field REF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

37 Package Information PAC-C402-7077 TO describe the number and type of Detail Mandatory Alphanumeric 3

38 Package identification PCI-C210-7102

To specify markings and labels on

individual packages Detail Mandatory Alphanumeric 35

39 Name and Address NAD-3035

To specify the name/address and

their related function. Detail Mandatory Alphanumeric 3

40 Document /Message Details DOC-C002-1001

To identify documents and details

directly related to it. Detail Mandatory Alphanumeric 3

41 Contact Information CTA-3139

To identify a person or a

department to whom the

communication should be directed. Detail Mandatory Alphanumeric 3

Page 28: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

27

Delivery Forecast (DELFOR)

Origin of Document - OEM

S. No EDIFACT - Field Name Provided Sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

42 Quantity Planned quantity QTY-C186-6063-135 To specify a pertinent quantity Detail Optional Alphanumeric 3

43 Reference Field REF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

44 Scheduling conditions

Tentative schedules-

Month

SCC - 4017- 12 To specify scheduling conditions Detail Mandatory Alphanumeric

45 Quantity Total Quantity QTY-C186-6063 To specify a pertinent quantity Detail Mandatory Alphanumeric 3

46 Reference Field REF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

47 Transport Information TDT-8051

To specify information regarding

transport such as mode of

transport, means of transport etc.. Detail Mandatory Alphanumeric 3

48 Price Information PRI-C509-5125 To specify price Information Detail Mandatory Alphanumeric 3

49 Message trailer UNT-0074 Number of segments in a message Trailer Mandatory Numeric 10

50 Message trailer UNT-0062

To end and check the completeness

of the message Trailer Mandatory Alphanumeric 14

Page 29: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

28

3.3 EDI Document - DELJIT

3.3.1 Pre Requisite for the EDI – Sender’s End

• DELFOR should have been triggered before the delivery schedule is created.

• Purchase Order details for the parts required as per the delivery schedule should be

available in the system. Creation of a delivery schedule based on the Master Production

Schedule (MPS) would trigger the EDI message type for delivery schedule. A delivery

schedule number would be created.

3.3.2 Pre Requisite for the EDI – Receiver’s End

PO and SO details should have been updated in the supplier’s system.

3.3.3 Triggers at Sender’s End

Consignment number can be sent as a part of the DELJIT if generated by the OEM or would

be generated by the supplier after the delivery has been confirmed. This would depend on

the process agreed.

3.3.4 Triggers at Receiver’s End

Once the EDI for delivery schedule is received by the supplier, it is required to

acknowledge the receipt of the schedule details which is provided using the EDI message

for acknowledgement (such as APERAK in UN/ EDIFACT). This is a system

acknowledgment of receipt of file.

The delivery order would be created at the supplier’s end. The delivery order is an internal

document.

3.3.5 Governance

• Sender

- The delivery schedule number would be mapped to the PO numbers for the

parts requested as per the delivery schedule.

- Depending on the process agreed between the supplier and the OEM:

• A Consignment number mapped to the delivery schedule number to be

generated when the supplier accepts the delivery. In this case,

Consignment number would be generated by the OEM and sent as part

of delivery schedule.

Page 30: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

29

• Consignment number could be generated by the supplier after

confirming the delivery as per the delivery schedule.

- Any changes to the Delivery Schedule by the OEM should be done prior to the

generation of Consignment number.

• Receiver

- Parts/ assemblies to be scheduled for delivery to the OEM only after the

generation of the Consignment number.

- Delivery schedule to be referenced to the Sales Order number of the supplier

which in turn is referenced to the PO number.

The requirement for a functional acknowledgement (APERAK) for communicating

application related errors would be made optional. The trading partners would need to

agree on the transactions for which APERAK would be made mandatory. However,

acknowledgement on the receipt of DELJIT and DESADV would be made mandatory

Page 31: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

30

3.3.6 High Level Document Flow

* Note – Consignment number may be created as a part of the DELJIT by the OEM or may be created by the Supplier after confirming the delivery. The EDI

message definition for Consignment Number would be covered under DESADV

Page 32: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

31

3.3.7 Definition of EDI Standard

Delivery Schedule (DELJIT)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character Length

1 Message Header UNH-062 To head ,identify and specify a message Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement. - DELJIT

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Delivery Schedule – Name BGM-C002-1001-242 To indicate the type and function of a message

and to transmit the identifying a number

Header Mandatory Alphanumeric 3

7 Date/Time/Period Current Date DTM-C507-2005-130 To specify a date ,and to time, or period Header Mandatory Alphanumeric 3

Page 33: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

32

Delivery Schedule (DELJIT)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character Length

8

Date/Time/Period

Schedule Dates DTM- C507-2005 To specify date ,and or time, or period Header Mandatory Alphanumeric 3

9

Date/Time/Period

Delivery or supply date/time DTM- C507-2005-02 To specify date ,and or time, or period Header Mandatory Alphanumeric 3

10 Reference Field - Scheduling

number

Supplier/vendor code REF-C506-1153-VR To specify a reference Detail Mandatory Alphanumeric 3

11 Name and Address OEM Code NAD-3035-BY To provide free form or coded text

information

Header Mandatory Alphanumeric 3

12 Name and Address Supplier Address and Name NAD-3035-SU To specify the name/address and their related

function.

Header Optional Alphanumeric 3

13 Contact Information Fax Number, Phone Number CTA-3139 To identify a person or a department to whom

the communication should be directed.

Header Mandatory Alphanumeric 3

14 Sequence Details SEQ-1050 To provide details relating to the sequence Detail Mandatory Alphanumeric 10

15 Package Information PAC-7224 TO describe the number and type of Detail Mandatory Numeric 3

16 Free Text Instructions given out. FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

17 Package identification PCI-C210-7102 To specify markings and labels on individual

packages

Detail Mandatory Alphanumeric 35

Page 34: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

33

Delivery Schedule (DELJIT)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character Length

18

Good Identity Number -

KANBAN Number KANBAN Number GIN-7405-AL

To give specific identification numbers, either

as single number or ranges Detail Optional Alphanumeric 3

19 Line Item No. Sr.No LIN-7143-SN To identify a line item and configuration. Detail Mandatory Alphanumeric 3

20 Item Description Item Description IMD-7077 To describe an item in either an industry or

free format

Detail Optional Alphanumeric 3

21 Additional Product ID Item Code/Part Code PIA-7143-PD To describe an item in either an industry or

free format

Detail Optional Alphanumeric 3

22 Reference Field Delivery schedule Number REF-C506-1153-AAN To specify a reference Header Mandatory Alphanumeric 3

23 Transport Information TDT-8051 To specify information regarding transport

such as mode of transport, means of transport

etc..

Detail Mandatory Alphanumeric 3

24 Location Details Plant details NAD-3035-SK Name and address Header Optional Alphanumeric 3

25 Location Details Unloading Location LOC-3227 To identify a place or a location and or related

locations

Detail Mandatory Alphanumeric 3

26 Contact Information Phone Numbers details CTA-3139 To identify a person or a department to whom

the communication should be directed.

Detail Mandatory Alphanumeric 3

27 Quantity Quantity Details Month wise QTY-C186-6060 To specify a pertinent quantity Detail Mandatory Alphanumeric 3

Page 35: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

34

Delivery Schedule (DELJIT)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character Length

28 Quantity quantity per Pack QTY-C186-6063-52 To specify a pertinent quantity Detail Mandatory Alphanumeric 3

29 Quantity Confirmed quantity QTY-C186-6063- To specify a pertinent quantity Detail Mandatory Alphanumeric 3

30 Quantity Planned quantity QTY-C186-6063- To specify a pertinent quantity Detail Mandatory Alphanumeric 3

31 Quantity - Minimum order

quantity

MOQ QTY-C186-6063-53 To specify a pertinent quantity Detail Mandatory Alphanumeric 3

32 Schedule conditions - Frequency

Code

Current month, next month SCH - C329-2013 To specify scheduling conditions Detail Mandatory Alphanumeric 3

33 Scheduling conditions - Firm Firm Schedule/Pend Schedule SCC - 4017- 1 To specify scheduling conditions Detail Mandatory Alphanumeric 3

34 Scheduling conditions - Planning Tentative schedules- Month SCC - 4017- 12 To specify scheduling conditions Detail Mandatory Alphanumeric 3

35 Reference Field Agreement number REF-C506-1153-AJS To specify a reference Detail Mandatory Alphanumeric 3

36 Price Information PRI-C509-5125 To specify price Information Detail Mandatory Alphanumeric 3

37 Message trailer UNT-0074 Number of segments in a message Trailer Mandatory Numeric 10

Page 36: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

35

Delivery Schedule (DELJIT)

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character Length

38 Message trailer UNT-0062 To end and check the completeness of the

message

Trailer Mandatory Alphanumeric 14

39 Free Text Authorized Signature FTX-C108 - 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

40 Reference Number Line Item Number REF-C506-1153-LI To specify a reference Detail Optional Alphanumeric 3

41 Reference Number SBU - Strategic business Unit

Number

REF-C506-1153- To specify a reference Detail Optional Alphanumeric 3

42 Reference Field PO number REF-C506-1153-OP To specify a reference Header Mandatory Alphanumeric 3

43 Reference Field Invoice Number REF-C506-1153-IV To specify a reference Detail Mandatory Alphanumeric 3

44 Free Text Instruction - In the form of

test/Remarks

FTX-C108 - 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

Page 37: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

36

3.4 EDI Document – Consignment Number (DESADV)

3.4.1 Pre Requisite for the EDI – Sender’s End (Method 1)

• When the OEM shares the delivery schedule with the supplier, the supplier should

have acknowledged and accepted the schedule. The EDI message type for

acknowledgement (APERAK) should have been generated.

3.4.2 Pre Requisite for the EDI – Receiver’s End (Method 1)

EDI for delivery schedule (DELJIT) should have been shared with the supplier. The

Consignment Number should have been generated by the OEM and communicated to the

supplier. Acknowledgement of delivery schedule (APERAK) should have been provided by

the supplier.

3.4.3 Triggers at Sender’s End (Method 1)

Once the DESADV has been triggered by the supplier, the supplier would prepare and

dispatch the consignment according to the packing details, transporter details etc

mentioned in the EDI. This sets the stage for creation of an invoice for the consignment

and generation of message type INVOIC.

3.4.4 Triggers at Receiver’s End (Method 1)

Generation of Consignment number by the OEM would mark the status of the line items in

the delivery schedule to ‘Pending for delivery’. Generation of Consignment number by the

OEM and DESADV, subsequently, by the supplier acts as the pre-requisite for the creation

of Goods Receipt Note (GRN) and the EDI message type RECAVD at the receiving area/

stores of the OEM

Page 38: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

37

3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM)

Method 1 is recommended when the OEM and suppliers agree on an arrangement whereby parts/ assemblies are supplied under JIT/ pull/ Kanban

systems

Page 39: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

38

3.4.6 Pre Requisite for the EDI – Sender’s End (Method 2)

• When the OEM shares the delivery schedule with the supplier, the supplier should

have acknowledged and accepted the schedule which would mean that the supplier

has confirmed its ability to meet the demand of the OEM as per the delivery schedule.

The EDI message type for acknowledgement (APERAK) should have been generated.

3.4.7 Pre Requisite for the EDI – Receiver’s End (Method 2)

EDI for delivery schedule (DELJIT) should have been shared with the supplier.

Acknowledgement of delivery schedule (APERAK) should have been provided by the

supplier.

3.4.8 Triggers at Sender’s End (Method 2)

Generation of Consignment number by the supplier acts as the pre-requisite for the

creation of Supplier’s invoice and of the EDI message type INVOIC.

3.4.9 Triggers at Receiver’s End (Method 2)

After creation of Consignment number by the supplier, the supplier would prepare and

dispatch the consignment according to the packing details, transporter details etc

mentioned in the EDI for Consignment Number. This would be a precursor to creation of

Goods Inspection Report by the OEM

3.4.10 Governance (Method 2)

• Sender

- A Consignment number referenced to the delivery schedule number should be

generated only when the delivery schedule is acceptable to the supplier and the

supplier has enough resources to supply as per the delivery schedule.

- Any changes to the Delivery Schedule by the OEM should be done prior to the

generation of Consignment number.

• Receiver

- Parts/ assemblies to be scheduled for delivery to the OEM only after the receipt

of the Consignment number from the OEM if the Consignment number is

required to be generated by the OEM.

- Invoice for the material to be shipped to the OEM should be created after the

generation of the Consignment number. There, also, may be a scenario where

Page 40: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

39

invoice number is generated by the supplier without the Consignment Number

being generated by the supplier itself.

- Invoice number should be referenced to the Consignment number.

The requirement for a functional acknowledgement (APERAK) for communicating

application related errors would be made optional. The trading partners would need to

agree on the transactions for which APERAK would be made mandatory. However,

acknowledgement on the receipt of DELJIT and DESADV would be made mandatory

Page 41: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

40

3.4.11 High Level Document Flow - Method 2 (Consignment Number generated by Supplier)

Su

pp

lie

r (S

en

de

r)O

EM

(R

ece

ive

r)

Method 2 is recommended when components are supplied as a per a pre-defined and agreed delivery schedule which is not based on JIT/ pull/

Kanban systems

Page 42: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

41

3.4.12 Definition of EDI Standard

Consignment Number - DESADV

Origin of Document - Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header- Balance

Enquiry - DESADV

UNH-062 A service segment starting and

uniquely identifying a message.

The message type code for

Invoices is "DESADV"

Header Mandatory Alphanumeric 14

2 Message Identifier -

Message Type

UNH-S009-0065 .The combination of data

elements in 0062 and S009 shall

be used to identify uniquely the

message within is group(If used)

if not used, within the

interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier -

Message version number

UNH-S009-0052 The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not

used, within the interchange, for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier -

Message release number

UNH-S009-0054 The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not

used, within the interchange, for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

Page 43: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

42

Consignment Number - DESADV

Origin of Document - Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

5 Message Identifier -

Controlling Agency Coded.

UNH-S009-0051 The combination of data elements

in 0062 and S009 shall be used to

identify uniquely the message

within is group(If used) if not

used, within the interchange, for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the Message Name of the Document -

Despatch Advice Message

BGM-C002-1001-351 To indicate the type and function

of a message and to transmit the

identifying number.

Header Mandatory Alphanumeric 3

7

Date/Time Period Delivery Date and Time DTM-C506-2005-2

To specify date, and/or time,

or period Header Mandatory Alphanumeric 3

8 Reference Field Party reference Number RFF-C506-1153-AUB To specify a reference Header Mandatory Alphanumeric 3

9 Name and Address Consignee name and address NAD-3035-SU To specify , the name/address

and their related functionality.

Header Mandatory Alphanumeric

3

10 Reference Field Consignment No. RFF-C506-1153-AUB To specify a reference Header Optional Alphanumeric 3

11 Reference Field Party Code RFF-C506-1153-ACK To specify a reference Header Mandatory Alphanumeric 3

12 Contact Information CTA-3139 TO identify the person or

department to whom the

communication should be

directed.

Header Mandatory Alphanumeric 3

13 Terms of Delivery TOD-4055 To specify the terms of delivery of

transport

Header Mandatory Alphanumeric

3

Page 44: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

43

Consignment Number - DESADV

Origin of Document - Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

14 Transport Information

Mode of Transport TDT-8051

To specify information regarding

transport such as mode of

transport, means of transport

etc.. Header Mandatory Alphanumeric 3

15 Location Details

LOC-3227- To identify a place or a location

and/or related

locations.

Detail Mandatory Alphanumeric

3

16 Equipment Details EQD-8053 To identify a unit of equipment Detail Mandatory Alphanumeric 3

17 Handling Instructions HAN-C524 To specify handling and where

necessary, notify

hazards

Header Mandatory Alphanumeric

3

18 Consignment packing

Sequence

Header Mandatory

19 Package Header Mandatory

20 Handling Instructions HAN-C524 To specify handling and where

necessary, notify

hazards

Header Mandatory Alphanumeric

3

21 Package Identification

PCI-C210-7102

To specify markings and labels on

individual packages Detail Mandatory Alphanumeric 35

22 Related Identification

Numbers

GIR-C206 To specify a set of related

identification numbers

Header Mandatory Alphanumeric

3

23 Goods Identity Number GIN-7405 To give specific identification

numbers ,either as a single

numbers or ranges

Header Mandatory Alphanumeric 3

24 Component Details COD-C823-7504 To provide component details of

an object (e.g. product, container)

such as its type and the

material of which it is

composed

Header Mandatory Alphanumeric

3

Page 45: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

44

Consignment Number - DESADV

Origin of Document - Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

25 Line Item Sr.no LIN-1082-SN To identify a line item and

configuration.

Detail Mandatory Alphanumeric

3

26 Additional Product ID Part No./Code Number PIA-7143-BH Coded identification of an item

type

Detail Optional Alphanumeric

3

27 Item Description Part Description/Material

description

PIA-7143-PD Coded identification of an item

type

Detail Optional Alphanumeric

3

28 Measurement Per Unit MEA-C174-6411 To specify physical

measurements, including

dimension tolerances, weights

and counts

Detail Optional Alphanumeric

3

29 Quantity Ordered Quantity QTY-C186-6063-21 To specify a pertinent quantity Detail Optional Alphanumeric 3

30 Quantity Shipped Quantity QTY-C186-6063- To specify a pertinent quantity Detail Optional Alphanumeric 3

31 Quantity Received quantity QTY-C186-6063- To specify a pertinent quantity Detail Optional Alphanumeric 3

32 Quantity Quantity despatched QTY-C186-6063-12 To specify a pertinent quantity Detail Optional Alphanumeric 3

33 Quantity Quantity Advised QTY-C186-6063-151 To specify a pertinent quantity Detail Optional Alphanumeric 3

34 Quantity Quantity manufactured QTY-C186-6063-308 To specify a pertinent quantity Detail Optional Alphanumeric 3

35 Reference Field PO number RFF-C506-1153-OP To specify a reference Detail Optional Alphanumeric 3

36 Reference Field GR No. RFF-C506-1153- To specify a reference Detail Optional Alphanumeric 3

37 Reference Field Challan No. RFF-C506-1153- To specify a reference Detail Optional Alphanumeric 3

38 Date/Time Period GR Date DTM-C506-2005- To specify a date/time period. Detail Optional Alphanumeric 3

39 Additional Product ID Incoming Part No. PIA-7143-BH Coded identification of an item

type

Detail Optional Alphanumeric

3

40 Reference Field W.O No. RFF-C506-1153- To specify a reference Detail Optional Alphanumeric 3

Page 46: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

45

Consignment Number - DESADV

Origin of Document - Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

41 Rate per unit India Unique Detail Mandatory Alphanumeric 3

42 Monetary amount Amount MOA-C516-5004 To specify a monetary amount Detail Optional Alphanumeric 35

43 Monetary amount Invoice Amount/Total Amount RFF-C506-1153-IV To specify a reference Detail Optional Alphanumeric

3

44 Reference Field RFF-C507-1153 To specify a reference Detail Mandatory Alphanumeric 3

45 Dangerous Goods DGS-8273 To identify dangerous goods Detail Mandatory Alphanumeric 3

46 Place/Location Unloading Location LOC-3227- To identify a place or a location

and/or related

locations.

Detail Mandatory Alphanumeric

3

47 Split good Placement SGP-C237 To specify the placement of goods

in relation to

equipment.

Detail Mandatory Alphanumeric

3

48 Package Identification

PCI-C210-7102

To specify markings and labels on

individual packages Detail Mandatory Alphanumeric 35

49 Goods Identity Number GIN-7405 To give specific identification

numbers ,either as a single

numbers or ranges

Detail Mandatory Alphanumeric 3

50 Handling Instructions HAN-C524 To specify handling and where

necessary, notify

hazards

Detail Mandatory Alphanumeric

3

51 Free Text Free Text Information - Ensure

Availability of material..etc

FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

52 Free Text Advised by - Signature FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

53 Free Text Name and Telephone No. FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

Page 47: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

46

Consignment Number - DESADV

Origin of Document - Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

54 Free Text Signature FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

55 Quantity Variances QVR-C279-6064 To specify items details relating

to quantity variances

Detail Mandatory Numeric

15

56 Message Trailer UNT-0074 Number of Segments in a

message

Trailer Mandatory Numeric 10

57 Message trailer UNT-0062 To end and check the

completeness of the message

Trailer Mandatory Alphanumeric 14

Page 48: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

47

3.5 EDI document - Invoice

3.5.1 Pre Requisite for the EDI – Sender’s End

• Once the supplier generates an Invoice in his system/ ERP, the EDI for invoice gets

triggered and the message type file would reach the OEM. Please note the business

rules for Invoice creation remain unchanged irrespective of the implementation of EDI

standards.

• The Consignment number should have been generated by the supplier or the OEM as

decided between the trading partners.

3.5.2 Pre Requisite for the EDI – Receiver’s End

PO number should be available in the OEM’s system. EDI message type for delivery

schedule should have been created.

3.5.3 Triggers at Sender’s End

Creation of invoice would generate an invoice number. The creation of invoice provides

the trigger for creation of Gate Pass which will be mapped to PO number, Invoice Number

and Consignment Number.

3.5.4 Triggers at Receiver’s End

Invoice generated by the supplier in his system/ ERP, would trigger the EDI message type

for invoice with details such as goods and the related quantity dispatched, transporter

details etc. to be sent to the OEM. There is an understanding that static data like Customer

name, Tax details, Amount in words etc. will not be passed through EDI process but would

be stored as Masters both at OEM and Supplier’s end.

The invoice details (as per EDI) would be available for updating in the OEM’s system only

after the goods have been accepted at the gate.

Invoice creation would set the stage for creation of EDI for Quality Inspection Report.

As a statutory requirement, the hard copy of the invoice would still need to be furnished as

a legal document.

Page 49: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

48

3.5.5 Governance

• Sender

- The invoiced quantity should be as per the accepted Delivery Schedule and the

ASN details.

- Invoice number should be mapped to the ASN number.

- CENVAT details should be included in the EDI message for Invoice. The OEM

claims the CENVAT based on invoice value.

• Receiver

- GRN number should be mapped to the invoice number.

- Invoice number should be referenced with the PO number

Page 50: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

49

3.5.6 High Level Document Flow

Invoice - INVOIC

Supplier(Sender)

OEM(Receiver)

Supplier Invoice (INVOIC)

Supplier Invoice Number

PO Number

Part Number

Consignment Number

Invoiced Quantity

Tax and excise details

Supplier Price

CENVAT

Bill to and ship to location

PO Number and Date

OEM and Supplier Details

Part Details

Price Details

Payment Terms

Delivery Terms

PO (ORDERS)

Goods Inspection Report Number

Part Number

Consignment Number

Dimension

Accepted/ Rejected codes

Goods Inspection Report (INSRPT)

Supplier’s Invoice Number and

date

Part Number

Consignment Number

Quantity

No. of packages

Gate Pass (IND_GP)

Consignment Number

Part Number

Ordered and Shipped Quantity

Delivery Date and time

Tax and excise details

Consignment Number (DESADV)

Out of Scope EDI

Red Text – EDI Transaction Reference Number(s)

Blue Text – Internal Reference Number(s)

Black Text – Details in document

Not Mandatory

In-Scope EDI

Page 51: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

50

3.5.7 Definition of EDI Standards

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header- Invoice -

INVOIC

UNH-065 A service segment starting and uniquely

identifying a message. The message type

code for Invoices is "INVOIC"

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Tax Invoice BGM-1001-388 To indicate the type and function of a

message

and to transmit the identifying

number.

Header Mandatory Alphanumeric 3

7 Free Text Information for buyer BGM -C-11225 - 9 To indicate the type and function of a

message and to transmit the identifying

number. Code indicating the function of the

message.

Header Mandatory Alphanumeric 3

Page 52: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

51

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

8 Beginning of the message for Transporter BGM -C-1225 - 7 To indicate the type and function of a

message and to transmit the identifying

number. Code indicating the function of the

message.

Header Optional Alphanumeric 3

9 Beginning of the message for Assessee BGM -C-1125 - 31 To indicate the type and function of a

message and to transmit the identifying

number. Code indicating the function of the

message.

Header Optional Alphanumeric 3

10 Free Text Information Information pertaining to

invoice - laws

FTX-C108 - 4440 To provide free form or coded text

information

Header Optional Alphanumeric 512

11 Name and Address OEM Code NAD-030-3124 To provide free form or coded text

information

Header Optional Alphanumeric 35

12 Parties and Instruction. Supplier name and Code INP-C849-3301 - 5 To identify the party enacting an instruction Detail Mandatory Alphanumeric 3

13 Item Description Item Code description IMD-C273-7009 To describe an Item in either an industry or

free format.

Detail Optional Alphanumeric 3

14 Item Description Item Description IMD-C273-7008 To describe an Item in either an industry or

free format.

Detail Optional Alphanumeric 3

15 Reference - Invoice Number Invoice Number RFF-1153-IV To indicate the type and function of a

message

Header Mandatory Alphanumeric 3

16 Date/Time Period Invoice Date DTM-C2379-4 To specify a date, and or time period Header Mandatory Alphanumeric 3

17 Reference Field Customer Purchase Order

Number

RFF-C506-1153-OP To specify a reference Header Mandatory Alphanumeric 3

Page 53: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

52

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

18 Date/Time Period Time of Removal DTM-C2379-402 To specify date, and/or time, or period Header Mandatory Alphanumeric 3

19 Reference Field System document Number REF-C506-1153 - ACL To specify a reference. Header Mandatory Alphanumeric 3

20 Reference Field Road Permit Form No. RFF -1153- To specify a reference. Header Optional Alphanumeric 3

21 Name and Address Sold to Party NAD-3035 - SO To specify the name/address and their

related function.

Header Mandatory Alphanumeric 3

22 Name and Address Sold to Address. NAD-C059,NAD -

3164,NAD - C3251

To specify the name/address and their

related function.

Header Mandatory Alphanumeric 3

23 Name and Address Shipped to Party name NAD-3035 - ST To specify the name/address and their

related function.

Header Mandatory Alphanumeric 3

24 Name and Address Shipped to Party Address. NAD-C059,NAD -

3164,NAD - C3251

To specify the name/address and their

related function.

Header Mandatory Alphanumeric 3

25 Reference Field RR/GR Number REF-C506-1153 To specify a reference. Header Mandatory Alphanumeric 3

26 Document/Message Details. DOC-C503-1373 To identify documents and details directly

related to it.

Header Optional Alphanumeric 3

27 Contact Information Phone No/Fax No. CTA-3139 -(Code) To indentify a person or department to

whom the communication should be

directed.

Header Mandatory Alphanumeric 3

28 Currency Bill Amount - Rupees CUX-6343-14 To specify currencies used in transaction

and relevant details for the rate of

exchange.

Header Mandatory Alphanumeric 3

29 Payment Terms Payment Terms Date PYT - 4279 - 45 To specify the terms of payment Header Mandatory Alphanumeric 3

30 Transport Information. Transport Information. TDT-8051 To Specify information regarding the

transport such as mode of transport, means

of transport etc.

Header Mandatory Alphanumeric 3

31 Transport Information. Carrier TDT-C040-3128 To specify information regarding the

transport

Header Optional Alphanumeric 17

Page 54: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

53

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

such as mode of transport, means of

transport its conveyance reference

number and the identification of

the means of transport

32 Reference Field - Vehicle

number license

Vehicle Number RFF-1153-ABZ To specify information regarding the

transport

such as mode of transport, means of

transport its conveyance reference

number and the identification of

the means of transport

Header Optional Alphanumeric 3

33 Reference Field-Transport

document number

Road Permit Form No. - LR

No

RFF-1153-AAS To specify information regarding the

transport

such as mode of transport, means of

transport its conveyance reference

number and the identification of

the means of transport

Header Optional Alphanumeric 3

34 Location /Place Identification -

Place of Destination

Destination LOC-3227-8 To specify a place or location and /or

related locations.

Header Mandatory Alphanumeric 3

35 Date/Time Period LR Date DTM-2005-11 To specify a reference. Header Mandatory Alphanumeric 3

36 Location-Details - Plant Plant LOC-3227-19 Code identifying the function of a location. Header Optional Alphanumeric 3

37 Equipment details EQD-8053 To identify a unit of Equipment. Header Mandatory Alphanumeric 3

38 Package Details PAC-7224 To describe the number and type of

package/physical units.

Header Mandatory

39 Package Identification PCI-C210-7102 To specify marking and labels on individual

packages or physical units.

Header Mandatory Alphanumeric 35

40 Allowance or Charge ALC-5463-M To indentify allowance or charge details. Header Mandatory Alphanumeric 3

41 Quantity/Case Invoice Quantity QTY-C186-6063-47 To specify a pertinent quantity Header Mandatory Alphanumeric 3

42 Reference number EDI Number RFF-1153-SAD To specify a reference. Header Mandatory Alphanumeric 3

Page 55: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

54

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

43 Reference Field - Vendor Code Vendor Code RFF-1153-VR To specify a reference. Header Mandatory Alphanumeric 3

44 Reference Field PO No. RFF-C506-1153-OP To specify a reference Header Mandatory Alphanumeric 3

45 Reference NO Line Item No. RFF-C506-1153- To specify a reference Header Optional Alphanumeric 3

46 Rate Details Rate(Rs.) RTE-C128-5420 To specify rate information Header Mandatory Numeric 15

47 Rate Detail Rate RTE -C128 To specify rate information Detail Optional Alphanumeric 15

48 Tax/Duty/Fee details Tax Details TAX-5283 To specify relevant duty/tax/fee

information.

Header Mandatory Alphanumeric 3

49 Monetary Details Bill Amount MOA-C516-5025-77 To specify a monetary amount Header Optional Numeric 3

50 Requirements and Conditions RCS-7293 To specify sector/subject requirement and

conditions.

Header Mandatory Alphanumeric 3

51 Adjustments Details AJT-4465 To Identify the reason for an adjustment Header Mandatory Alphanumeric 3

52 Line Item Sr.No LIN-7143-SN Coded identification of an item type. Detail Mandatory Alphanumeric 6

53 Item Code Item Code IMD-C272 To describe an item in either an industry or

free format

Detail Optional Alphanumeric 3

54 Quantity/Case Total Quantity QTY-C186-6063-169 To specify a pertinent quantity Header Mandatory Alphanumeric 3

55 Measurements Unit of Measure` MEA-6311-ABW Code qualifying the purpose of the

measurement.

Detail Optional Alphanumeric 3

56 Measurements Weight - Invoice Quantity MEA-6311-WT Code qualifying the purpose of the

measurement.

Detail Optional Alphanumeric 3

57 Item Description Item Description IMD- C272 To describe an item in either an industry or

free format

Detail Optional Alphanumeric 3

58 Monetary Details Good item total MOA-C516-5025-66 To describe a pertinent amount Detail Optional Alphanumeric 3

59 Monetary Details Total line Amount MOA-C516-5025-79 To describe a pertinent amount Detail Optional Alphanumeric 3

Page 56: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

55

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

60 Duty/Tax Information E.Cess TAX-C241-5153-OTH Code specifying a type of duty, tax or fee. Detail Optional Alphanumeric 3

61 Duty/Tax Information H.E.Cess TAX-C241-5153-OTH Code specifying a type of duty, tax or fee. Detail Optional Alphanumeric 3

62 Duty/Tax Information Basic Excise Duty TAX-C241-5153-EXC Code specifying a type of duty, tax or fee. Detail Optional Alphanumeric 3

63 Price Details Sales Rate/UOM -Basic price

per unit.

PRI-C509-5379-PU Code qualifying the type of monetary

amount.

Detail Optional Alphanumeric 3

64 Monetary Details Sub Total MOA-C516-5025-499 Code qualifying the type of monetary

amount.

Detail Optional Alphanumeric 3

65 Tax/Duty/Fee details Numerical value for VAT in

detailed section

TAX-5153-VAT Code specifying the basis for a duty or tax

or fee

rate.

Detail Optional Alphanumeric 3

66 Duty/Tax Information VAT Percentage TAX-5273-1 Code specifying the basis for a duty or tax

or fee rate.

Detail Optional Alphanumeric 12

67 Duty/Tax Information Freight Charges TAX-5283 To specify relevant duty/tax/fee

information.

Detail Mandatory Alphanumeric 3

68 Duty/Tax Information Additional Excise duty TAX-C241-5153-EXC Code specifying a type of duty, tax or fee. Detail Optional Alphanumeric 3

69 Monetary Details Total Amount MOA-C516-5025-77 To specify a monetary amount Detail Mandatory Numeric 35

70 Payment Terms PYT – 4279 To Specify terms of payment Detail Mandatory Alphanumeric 3

71 Price Details Ass. Value PRI-C509-5125-AAD To specify price information Detail Optional Alphanumeric 3

72 Reference Field REF-C506-1153 To specify a reference. Detail Mandatory Alphanumeric 3

73 Package No. of cases PAC-7224 To describe the number and type of

package/physical unites

Detail Mandatory Numeric 8

74 Package Identification PCI-C210-7102 To specify marking and labels on individual

packages or physical units.

Detail Mandatory Alphanumeric 35

75 Location /Place Identification LOC-3227 To Identify a place or a location and or

related locations.

Detail Mandatory Alphanumeric 3

Page 57: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

56

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

76 Name and Address NAD-3035 To specify the name/address and their

related function.

Detail Mandatory Alphanumeric 3

77 Reference Field REF-C506-1153 To specify a reference. Detail Mandatory Alphanumeric 3

78 Document/Message Details. DOC-C002 To identify documents and details directly

related to it.

Detail Mandatory

79 Contact Information CTA-C3139 To indentify a person or department to

whom the communication should be

directed.

Detail Mandatory

80 Allowance or Charge ALC-5463 To Identify an allowance or charge details Detail Mandatory Alphanumeric 3

81 Percentage Details PCD-C501-5245 To specify percentage Information Detail Mandatory Alphanumeric 3

82 Transport Information. Transporter mode TDT-C001-8179 To specify information regarding the

transport

such as mode of transport, means of

transport its conveyance reference

number and the identification of

the means of transport

Detail Mandatory Alphanumeric 3

83 Transport Information. Transporter Name TDT-C040-3128 To specify information regarding the

transport

such as mode of transport, means of

transport its conveyance reference

number and the identification of

the means of transport

Detail Optional Alphanumeric 3

84 Location /Place Identification LOC-3227 To identify a place or a location. Detail Mandatory Alphanumeric 3

85 Requirements and Conditions RCS-7293 To specify sector/subject requirement and

conditions.

Detail Mandatory Alphanumeric 3

86 Processing Information GEI-C012-7365 To identify processing information Detail Mandatory Alphanumeric 3

87 Section Control UNS-0081 Section Identification Trailer Mandatory

88 Free Text Information Grand Total IN words FTX-C108 - 4440 To provide free form or coded text Trailer Optional Alphanumeric 512

Page 58: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

57

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

information

89 Free Text Information Remarks FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

90 Free Text Information Excise Duty in Words FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

91 Free Text Information Invoice/Gross Amount In

words

FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

92 Duty/Tax Information Excise Duty Percentage TAX-5273-1 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

93 Duty/Tax Information Education Cess percentage TAX-5273-1 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

94 Duty/Tax Information Higher Education Cess

percentage

TAX-5273-1 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

95 Free Text Information VAT Percentage FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

96 Free Text Information Statement Certifying the

authenticity of the

Information provided

FTX-C108 - 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

97 Free Text Information Pre-Printed Information -

Range, Division.

FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

98 Free Text Information Pre-Printed Information -

Excise Duty Notification

FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

99 Free Text Information Pre-Printed Information -

VATSUR Percentage

FTX-C108 - 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

100 Free Text Information Pre-Printed Information -

Authorized Signatory

FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

101 Allowance or Charge ALC-5643 To identify allowance or charge details. trailer Mandatory Alphanumeric 3

Page 59: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

58

Invoice - INVOIC

Origin of Document - Supplier

S. No EDIFACT - Field Name Provided Sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

102 Message Trailer UNT-0074 Number of Segments in a message Trailer Mandatory Numeric 10

103 Message trailer UNT-0074 To end and check the completeness of the

message

Trailer Mandatory Alphanumeric 14

104 Message trailer Commodity India Unique Trailer Mandatory Alphanumeric 20

Page 60: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

59

3.6 EDI Document – Gate Pass

3.6.1 Pre Requisite for the EDI – Sender’s End

• Consignment number should have been generated by the OEM or the supplier, as the case

may be, for the goods to be dispatched by the supplier.

• Invoice number for the goods to be dispatched should have been created.

3.6.2 Pre Requisite for the EDI – Receiver’s End

The Gate Pass is an internal document so no pre-requisites from the receiver’s end are expected.

3.6.3 Triggers at Sender’s End

The creation of Gate Pass should map the Gate Pass Number with the Invoice Number.

3.6.4 Triggers at Receiver’s End

The Gate Pass is an internal document so no action is triggered at the receiver’s end.

3.6.5 Governance

• Sender

- It is recommended that the Gate Pass number be mapped to the Invoice Number for

the items to be released for shipment. However, this requirement is optional is left to

the discretion of the party generating the Gate Pass.

- It is a standard practice to release the material for shipment only after the creation of

the Gate Pass. Going forward, this requirement is again left to the good judgment and

internal processes of the parties generating the Gate Pass.

Page 61: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

60

3.6.6 Definition of EDI Standard

Returnable Gate Pass – IND_GP

Origin of Document - Supplier

S. No Field Name Sample Provided - Field

Name

EDIFACT Code/Tag

Name

Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

1 Reference Field Gate Pass Number RFF-C506-1153- To specify a reference Header Mandatory Alphanumeric 3

2 Reference Field Vehicle Details - Vehicle

Number

RFF-C506-1153-ABZ To specify information

regarding the transport

such as mode of

transport, means of

transport its

conveyance reference

number and the

identification of the

means of transport

Header Optional Alphanumeric 3

3 Date/time Date DTM-C507-2005-130 To specify a date, and or

time period

Header Mandatory Alphanumeric 3

4 Location Details - Plant Location LOC-3227-19 Code identifying the

function of a location.

Header Mandatory Alphanumeric 3

5 Date/time Time DTM-C507-2005-130 To specify a date, and or

time period

Header Mandatory Alphanumeric 3

6 Line Item Serial No. LIN-7143-SN Coded identification of an

item type.

Detail Mandatory Alphanumeric 3

7 Reference Field Invoice Number RFF-C506-1153-IV To specify a reference Detail Mandatory Alphanumeric 3

8 Date/time Invoice Date DTM-C507-2005-3 To specify a date, and or

time period

Detail Mandatory Alphanumeric 3

Page 62: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

61

Returnable Gate Pass – IND_GP

Origin of Document - Supplier

S. No Field Name Sample Provided - Field

Name

EDIFACT Code/Tag

Name

Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

9 Item Description Item Code IMD-C272- To describe an item in

either an industry or free

format

Detail Mandatory Alphanumeric 3

10 Package No. of Cases PAC-7224 To describe the number

and type of

package/physical unites

Detail Mandatory Numeric 8

11 Quantity Quantity /Case QTY-C186-6063- To specify a pertinent

quantity

Detail Mandatory Alphanumeric 3

12 Quantity Actual Quantity QTY-C186-6063- To specify a pertinent

quantity

Detail Mandatory Alphanumeric 3

13 Monetary Amount Line Amount MOA-C516-5025-79 To describe a pertinent

amount

Detail Mandatory Alphanumeric 3

14 Pallet Type Detail Optional

15 Free Text Amount in Words FTX-C108 - 4440 To provide free form or

coded text information

Detail Mandatory Alphanumeric 512

18 Free Text Dispatcher Name FTX-C108 - 4440 Trailer Optional

19 Free Text Driver FTX-C108 - 4440 To provide free form or

coded text information

Trailer Optional Alphanumeric 512

Page 63: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

62

3.7 EDI Document – Goods Inspection Report

3.7.1 Pre Requisite for the EDI – Sender’s End

• No pre-requisite from Sender’s End.

It is worth noting that the creation of Goods Inspection Report depends on the agreed upon

arrangement between the OEM and the supplier. Accordingly, the Sender and Receiver would

change.

3.7.2 Pre Requisite for the EDI – Receiver’s End

Invoice number should have been generated for the goods dispatched by the supplier. EDI

message type for Invoice should have been sent to OEM by the supplier.

3.7.3 Triggers at Sender’s End

• Creation of goods inspection report in the OEM’s system would generate a Quality

Inspection Report Number and an EDI message similar to INSRPT definition as in UN/

EDIFACT would be created. The OEM would then send this EDI file to the supplier for

keeping a record of the quality complaint for which an item may have been rejected.

• After the EDI for Goods Inspection Report, the OEM’s system becomes ready to create

the GRN and Rejection Note/ Invoice.

3.7.4 Triggers at Receiver’s End

The supplier is required to acknowledge the receipt of the Goods Inspection Report by

triggering an EDI for Acknowledgement (APERAK).

3.7.5 Governance

• Sender

- The OEM should capture results of the quality parameters and the reasons for

rejection, if required.

- The Goods Inspection Report Number should be referenced with the Invoice

Number of the consignment, the Consignment number and the Goods Rejection

Note/ Invoice Number.

- The code value for ‘Accepted’ or ‘Rejected’ should be captured in the Quality

Inspection Report.

- GRN can be created before or after the creation of the Quality Inspection Report

depending on the arrangement between the trading parties. While preparing

Page 64: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

63

the GRN, the quantities accepted and rejected (if any) are entered into the

OEM’s system.

• Receiver

- GRN should be created as per the supplier’s invoice. GRN number should be

mapped to the invoice number

Page 65: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

64

3.7.6 High Level Document Flow

Su

pp

lie

r (R

ece

ive

r)O

EM

(S

en

de

r)

Page 66: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

65

3.7.7 Definition of EDI Standards

Goods Inspection Report - INSRPT

Origin of Document – OEM/ Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header UNH-062 To head ,identify and specify a message Header Mandatory Alphanumeric 14

2 Message Identifier -

Message Type

UNH-S009-0065 .The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement. - INSPRT

Header Mandatory Alphanumeric 6

3 Message Identifier -

Message version number

UNH-S009-0052 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier -

Message release number

UNH-S009-0054 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier -

Controlling Agency

Coded.

UNH-S009-0051 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the purpose

of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Goods Inspection Report BGM-C002-1001-162 To indicate the type and function of a

message and to transmit the identifying a

number

Header Mandatory Alphanumeric 3

Page 67: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

66

Goods Inspection Report - INSRPT

Origin of Document – OEM/ Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

7 Date/Time/Period Inspection Date DTM-C507-2005-351 To specify a date ,and to time, or period Header Mandatory Alphanumeric 3

8 Date/Time/Period LTR Date DTM-C507-2005- To specify a date ,and to time, or period Header Mandatory Alphanumeric 3

9 Date/Time/Period Drawing-Date DTM-2005-380 To specify a date ,and to time, or period Header Mandatory Alphanumeric 3

10 Reference Field Reference number/GIN RFF-C156-1153- To specify a reference Header Mandatory Alphanumeric 3

11 Reference Field Invoice No. REF-C506-1153-IV To specify a reference Header Mandatory Alphanumeric 3

12 Name and Address Name of the Buyer NAD-3035-BY To provide free form or coded text

information

Header Mandatory Alphanumeric 3

13 Document /Message

Details

DOC-C002-1001 To identify documents and details directly

related to it.

Header Mandatory Alphanumeric 3

14 Reference Field Drg-No - Drawing number RFF-C156-1153-AAL To specify a reference Header Mandatory Alphanumeric 3

15 Name and Address Suppliers name NAD-3035-SU To specify the name/address and their

related function.

Header Optional Alphanumeric 3

Page 68: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

67

Goods Inspection Report - INSRPT

Origin of Document – OEM/ Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

16 Contact Information Department name CTA-C056-3412 To identify a person or a department to

whom the communication should be directed.

Header Mandatory Alphanumeric 3

17 Line Item Sr.No LIN-7143-SN To identify a line item and configuration. Detail Mandatory Alphanumeric 3

18 Item Description Particulars/Parameter

IMD-C273-7008

To describe an item in either a industry or

free format Detail Optional Alphanumeric

35

19 Additional Product ID Part No. PIA-7143-BH Coded identification of an item type Detail Optional Alphanumeric 3

20 Additional Product ID Part Name/Description PIA-7143-PD Coded identification of an item type Detail Optional Alphanumeric 3

21 Quantity Quantity Received QTY-6063-48 To specify a pertinent quantity Detail Optional Alphanumeric 3

22 Condition of Supply India Unique Detail Optional Alphanumeric 3

23 Measurements Test dimensions MEA-6311-ABM To specify additional or substitution item

identification information

Detail Optional Alphanumeric 3

24 Measurements Drg. Dimension in MM MEA-4347 To specify additional or substitution item

identification information

Detail Optional Alphanumeric 3

25 Measurements Actual Dimension MEA-4347 To specify additional or substitution item

identification information

Detail Optional Alphanumeric 3

26 Free Text Inspection Method

FTX-C108 - 4440

To provide free form or coded text

information

Detail Optional Alphanumeric 512

27 Characteristic class India Unique Detail Optional Alphanumeric 20

28 Class/Sample Size India Unique Detail Optional Alphanumeric 20

29 Free Text Remarks FTX-C108 - 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

30 Name of the Inspector India Unique Detail Optional Alphanumeric 20

31 Name and Address Customer name NAD-3035 To specify the name/address and their

related function.

Header Mandatory Alphanumeric 3

32 Good Identity Number GIN-7405 To give specific identification numbers ,either Detail Mandatory Alphanumeric 3

Page 69: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

68

Goods Inspection Report - INSRPT

Origin of Document – OEM/ Supplier

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

as a single numbers or ranges

33 Reference Field LTR No. RFF-C156-1153- To specify a reference Detail Optional Alphanumeric 3

34 Measurements Unit MEA-6311-ABW Code qualifying the purpose of the

measurement.

Detail Optional Alphanumeric 3

35 Lower Limit India Unique Detail Mandatory Alphanumeric 10

36 Upper Limit India Unique Detail Mandatory Alphanumeric 10

37 Measurements Test dimensions MEA-6311-ABM To specify additional or substitution item

identification information

Detail Optional Alphanumeric 3

38 Status Result: Approved STS-C555-4405-39 To specify the status of a project or service Detail Optional Alphanumeric 3

39 Status Result: Rejected STS-C555-4405-41 To specify the status of a project or service Detail Optional Alphanumeric 3

40 Free Text Remarks FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

41 Message trailer UNT-0074 Number of segments in a message Trailer Mandatory Numeric 10

42 Message trailer UNT-0062 To end and check the completeness of the

message

Trailer Mandatory Alphanumeric 14

Page 70: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

69

3.8 EDI Document – Goods Receipt Note

3.8.1 Pre Requisite for the EDI – Sender’s End

• Consignment number should have been generated for the goods to be dispatched by

the supplier.

• Creation of Goods Inspection Report would be optional depending on the agreement

between the trading partners.

3.8.2 Pre Requisite for the EDI – Receiver’s End

Invoice number should have been generated for the goods dispatched by the supplier. EDI

message type for Invoice should have been sent to OEM by the supplier.

3.8.3 Triggers at Sender’s End

• Once the GRN is created, the OEM needs to send an acknowledgement to the supplier

for the receipt of items. For this, an EDI message for acknowledgement (APERAK)

should be triggered.

• While creating the GRN, the quantities accepted and quantities rejected are captured.

For the quantities that have been rejected, a Goods Rejection Note needs to be

prepared which would create an EDI message RETANN as is available under the UN/

EDIFACT standard.

• After the creation of GRN, the OEM may be required to create a credit note or a debit

note for which EDI message types for CREADV or DEBADV may need to be triggered as

the case may require.

3.8.4 Triggers at Receiver’s End

No triggers at the receiver’s end after the creation of the GRN by the OEM.

3.8.5 Governance

• Sender

- The OEM should capture results of the quality parameters.

- The Goods Inspection Report Number should be referenced with the Invoice

Number of the consignment, the Consignment number and the Goods Rejection

Note/ Invoice Number.

- The code value for ‘Accepted’ or ‘Rejected’ should be captured in the Quality

Inspection Report.

Page 71: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

70

- Creation of GRN can be done before or after the preparation of the Quality

Inspection Report. This would depend on the arrangement between the trading

parties. While preparing the GRN, the quantities received, accepted, rejected (if

any), destroyed should be entered into the OEM’s system.

• Receiver

- GRN should be created as per the supplier’s invoice. GRN number should be

mapped to the invoice number.

Page 72: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

71

3.8.6 High Level Document Flow

Page 73: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

72

3.8.7 Definition of EDI Standard

Goods Receipt Note - RECADV

Origin Of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header UNH-062 To head ,identify and specify a message -

RECADV

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements in 0062 and

S009 shall be used to identify uniquely the

message within is group(If used) if not used,

within the interchange, for the purpose of

acknowledgement. - DELJIT

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in 0062 and

S009 shall be used to identify uniquely the

message within is group(If used) if not used,

within the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in 0062 and

S009 shall be used to identify uniquely the

message within is group(If used) if not used,

within the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data elements in 0062 and

S009 shall be used to identify uniquely the

message within is group(If used) if not used,

within the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Goods receipt Note BGM-C002-1001-632 To indicate the type and function of a message

and to transmit the identifying a number

Header Mandatory Alphanumeric 3

7 Date/Time/Period Goods Receipt Date DTM-C507-2005-50 To specify a date ,and to time, or period Header Mandatory Alphanumeric 3

Page 74: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

73

Goods Receipt Note - RECADV

Origin Of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

8 Date/Time/Period Warehouse receipt date DTM-C507-2005-242 To specify a date ,and to time, or period Detail Optional Alphanumeric 3

9 Date/Time/Period Challan Date DTM-C507-2005- To specify a date ,and to time, or period Header Mandatory Alphanumeric 3

10 Reference Field - GR No. Goods receipt Number/GR No. RFF-1153- To specify a reference. Header Mandatory Alphanumeric 3

11 Reference fields - PO Purchase Order Number RFF-C506-1153-OP To indicate the type and function of a message

and to transmit the identifying number.

Header Mandatory Alphanumeric 3

12 Reference fields - Challan challan No/Dispatch No. RFF-C506-1153- To indicate the type and function of a message

and to transmit the identifying number.

Header Optional Alphanumeric 3

13 Reference fields - PO Line Item PO Line item No. RFF-C506-1153-LI To indicate the type and function of a message

and to transmit the identifying number.

Optional Mandatory Alphanumeric 3

14 Reference Field - Vendor Code Supplier Code/Vendor Code RFF-1153-VR To specify a reference. Optional Mandatory Alphanumeric 3

15 Document /Message Details DOC-C002-1001-632 To identify documents and details directly

related to it.

Header Mandatory Alphanumeric 3

16 Physical or logical state CDI-7001 To describe a physical or logical state Header Mandatory Alphanumeric 3

17 Name and Address Plant Name NAD-C058-3124 To specify the name/address and their related

function.

Header Mandatory Alphanumeric 3

Page 75: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

74

Goods Receipt Note - RECADV

Origin Of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

18 Contact Information Fax Number and Contact details CTA-3139 To identify a person or a department to whom

the communication should be directed.

Header Mandatory Alphanumeric 3

19

Terms of Delivery TOD-4055 To specify terms of delivery Header Mandatory Alphanumeric 3

20

Location /Place Identification

Unloading location/Plant

Location LOC-3227-

To Identify a place or a location and or related

locations. Header Mandatory Alphanumeric 3

21

Transport Information Transporter TDT-8051

To Specify information regarding the transport

such as mode of transport. Header Mandatory Alphanumeric 3

22

Equipment Details EQD-8053 To identify a unit of equipment Header Mandatory Alphanumeric 3

23

Physical or logical state CDI-7001 To describe a physical or logical state Header Mandatory Alphanumeric 3

24

Seal Number SEL

To specify the seal number or a range of seal

numbers Header Mandatory

25

Equipment Attached EQA-8053 To specify attached or related Equipment Header Mandatory Alphanumeric 3

26

Consignment Packing Sequence CPS

To identify the sequence in which physical

packing is presented in the consignment, and

optionally to identify the hierarchical

relationship in the packing layers. Header Mandatory Alphanumeric 35

27

Reference Field

Warehouse receipt No RFF-C506-1153-WR To specify a reference Detail Mandatory Alphanumeric 3

Page 76: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

75

Goods Receipt Note - RECADV

Origin Of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

28

Transport Information TDT-8051

To Specify information regarding the transport

such as mode of transport. Header Mandatory Alphanumeric 3

29

Name and Address SBU Name NAD-3035-SU

To specify the name/address and their related

function. Header Mandatory Alphanumeric 3

30

Package Information PAC-C402-7077 TO describe the number and type of Header Mandatory Alphanumeric 3

31

Package identification PCI-C210-7102

To specify markings and labels on individual

packages Header Mandatory Alphanumeric 35

32

Goods Identity Number GIN-7405

To specify the identification number either in

single or in ranges Header Mandatory Alphanumeric 3

33

Line Item Sr.No.

LIN-7143-SN

To Indentify a line item and configuration Detail Mandatory Alphanumeric 3

34

Item Description Part Description

IMD- C272-7081 To describe an item in either an industry or free

format

Detail Optional Alphanumeric 17

35

Additional Product ID Part No

PIA-7143-BH

To describe an item in either an industry or free

format Detail Optional Alphanumeric 3

36

Quantity

Challan quantity/Dispatched

quantity

QTY-C186-6063-190

To specify a pertinent quantity Detail Optional Alphanumeric 3

37 Quantity Accepted Quantity QTY-C186-6063-190 To Specify a pertinent quantity Detail Optional Alphanumeric 3

Page 77: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

76

Goods Receipt Note - RECADV

Origin Of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

38 Quantity Rejected Qty. QTY-C186-6063-185 To Specify a pertinent quantity Detail Optional Alphanumeric 3

39 Quantity Scrap Quantity QTY-C186-6063-64 To Specify a pertinent quantity Detail Optional Alphanumeric 3

40 Quantity Warehouse Recpt Quantity QTY-C186-6063-48 To Specify a pertinent quantity Detail Optional Alphanumeric 3

41

Quantity Unit

Unit of measurement of

quantity

QTY-C186-6411

Code Specifying the unit of measurement Detail Optional Alphanumeric 8

42 Price Details Price PRI-5118 To specify price information Detail Optional Numeric 15

43

Name and Address NAD-3035

To specify the name/address and their related

function. Detail Mandatory Alphanumeric 3

44

Contact Information CTA-3139

To identify a person or a department to whom

the communication should be directed. Detail Mandatory Alphanumeric 3

45

Physical or logical state CDI-7001 To describe a physical or logical state Detail Mandatory Alphanumeric 3

46

Document /Message Details DOC-C002-1001-632

To identify documents and details directly

related to it. Detail Mandatory Alphanumeric 3

47

Goods Identity Number GIN-7405

To specify the identification number either in

single or in ranges Detail Mandatory Alphanumeric 3

Page 78: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

77

Goods Receipt Note - RECADV

Origin Of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT

Standard

Character Type

EDIFACT

Standard

Character

Length

48

Reference Field

Consignment No.

REF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

49

Package identification PCI-C210-7102

To specify markings and labels on individual

packages Header Mandatory Alphanumeric 35

50

Goods Identity Number GIN-7405

To specify the identification number either in

single or in ranges Detail Mandatory Alphanumeric 3

51

Reference Field Bill of Lading REF-C506-1153-BM To specify a reference Detail Mandatory Alphanumeric 3

52

Message trailer UNT-0074 Number of segments in a message Trailer Mandatory Numeric 10

53

Message trailer UNT-0062

To end and check the completeness of the

message Trailer Mandatory Alphanumeric 14

54 Reference Field Lot No. RFF-C506-1153 To specify a reference Detail Mandatory Alphanumeric 3

55 GR Tag India Unique Detail Mandatory Alphanumeric 10

56 Bin No. India Unique Detail Mandatory Alphanumeric 10

57 Free Text No Inspection, Class Details

FTX-C108 - 4440 To provide free form or coded text information Detail Optional Alphanumeric 512

58 Free Text Sample Usage FTX-C108 - 4440 To provide free form or coded text information Detail Optional Alphanumeric 512

59 Free Text Amount in Words FTX-C108 - 4440 To provide free form or coded text information Detail Optional Alphanumeric 512

60 Free Text Reason Code FTX-C108 - 4440 To provide free form or coded text information Detail Optional Alphanumeric 512

Page 79: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

78

3.9 EDI document-Goods Rejection Note

3.9.1 Pre Requisite for the EDI – Sender’s End

• Goods Inspection Report should have been created and the EDI for Goods Inspection

Report should have been shared with the supplier. Creation of EDI for Goods

Inspection is optional and depends on the arrangement between the supplier and the

OEM.

• Acknowledgement of GRN creation should be sent to the supplier

3.9.2 Pre Requisite for the EDI – Receiver’s End

Acknowledgement (APERAK) for receipt of Goods Inspection Report message should have

been triggered by the supplier.

3.9.3 Triggers at Sender’s End

• A Goods Rejection Note Number is generated as a result of the creation of the Goods

Rejection Note. The OEM creates a Debit Note to recover the cost of the items rejected

as mentioned in the Goods Rejection Note. The EDI similar to DEBADV as is defined in

UN/ EDIFACT is created for the Debit note details to be shared with the supplier.

3.9.4 Triggers at Receiver’s End

Receipt of a Goods Rejection note does not trigger any transaction at the receiver’s end

3.9.5 Governance

• Sender

- Goods Rejection Note should be created only after the receipt of the Goods

Inspection Report and the reason code values for rejection/ return should be

captured in the Rejection Note.

- The Goods Rejection Note should be based on the quantity rejected as

mentioned in the GRN created for the invoice from the supplier.

- The Goods Rejection Note Number should be referenced with the GRN Number,

Quality Inspection Report Number and the Debit Note Number.

• Receiver

Page 80: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

79

- The accounts receivables statement should be adjusted/ updated according to

the details mentioned in the Goods Rejection Note.

Page 81: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

80

3.9.6 High Level Document Flow

Su

pp

lie

r (R

ece

ive

r)O

EM

(S

en

de

r)

Page 82: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

81

3.9.7 Definition of EDI Standard

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

1 Message Header- Rejection Note UNH-062 A service segment starting and

uniquely identifying a message. The

message type code for purchase

orders is "Orders"

Header Mandatory Alphanumeric 14

2 Message Identifier - Message Type UNH-S009-0065 .The combination of data elements in

0062 and S009 shall be used to

identify uniquely the message within

is group(If used) if not used, within

the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in

0062 and S009 shall be used to

identify uniquely the message within

is group(If used) if not used, within

the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in

0062 and S009 shall be used to

identify uniquely the message within

is group(If used) if not used, within

the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data elements in

0062 and S009 shall be used to

identify uniquely the message within

is group(If used) if not used, within

the interchange, for the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Buyer BGM -C-11225 - 9 To indicate the type and function of a

message and to transmit the

identifying number. Code indicating

the function of the message.

Header Mandatory Alphanumeric 3

Page 83: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

82

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

7 Beginning of the message for Transporter BGM -C-1225 - 7 To indicate the type and function of a

message and to transmit the

identifying number. Code indicating

the function of the message.

Header Optional Alphanumeric 3

8 Beginning of the message for Assesse BGM -C-1125 - 31 To indicate the type and function of a

message and to transmit the

identifying number. Code indicating

the function of the message.

Header Optional Alphanumeric 3

9 Beginning of the message Name of the Doc - Goods

Rejection Note- Tax

Invoice

BGM -C002-1001-388 To specify the name/address and

their related function

Header Optional Alphanumeric 3

10 Date/Time Period Debit Date DTM-C507-2005- To specify the date/time period Header Mandatory Alphanumeric 3

11 Date/Time Period PO Date DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

12 Date/Time Period Date of Removal DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

13 Date/Time Period Time of Removal DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

14 Name and Address Address of OEM NAD-3035-BY To specify the name/address and

their related function.

Header Mandatory Alphanumeric 3

15 Reference Field Tariff Head No. RFF-1153-IV To indicate the type and function of a

message

Header Optional Alphanumeric 3

16 Reference Field Invoice Number RFF-1153-IV To indicate the type and function of a

message

Header Mandatory Alphanumeric 3

17 Name and Address Vendor Name and

address

NAD-3035-VN To specify the name/address and

their related function.

Header Optional Alphanumeric 3

Page 84: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

83

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

18 Reference Field Vendor Code RFF-1153-VR To indicate the type and function of a

message

Header Mandatory Alphanumeric 3

19 Reference Field Exc Invoice No. RFF-1153- To indicate the type and function of a

message

Header Optional Alphanumeric 3

20 Date/Time Period Excise Invoice Date DTM-C2005-3 To specify the date/time period Header Mandatory Alphanumeric 3

21 Reference Field Rej Note No REF-C506-1153-ALQ TO specify a coded reference Header Optional Alphanumeric 3

22 Date/Time Period Rejection Date DTM-C507-557 To specify the date/time period Header Mandatory Alphanumeric 3

23 Date/Time Period return date DTM-C507-557 To specify the date/time period Header Mandatory Alphanumeric 3

24 Reference Field Excise Reference Doc RFF-1153- To indicate the type and function of a

message

Header Optional Alphanumeric 3

25 Reference Field Sup.Excise Invoice

Number

RFF-1153- To indicate the type and function of a

message

Header Optional Alphanumeric 3

26 Document/Message Details. GR Mat Doc. DOC-C002-632 To identify documents and details

directly related to it.

Header Mandatory Alphanumeric 3

27 Date/Time Period Good receipt Date DTM-C507-50 To specify the date/time period Header Mandatory Alphanumeric 3

28 Reference Field PO No. RFF-C156-1153-OP To specify a reference. Header Optional Alphanumeric 3

29 Reference Field PO reference number RFF-1153- To indicate the type and function of a

message

Header Optional Alphanumeric 3

30 Document/Message Details. Document Number DOC-C002- To identify documents and details

directly related to it.

Header Mandatory Alphanumeric 3

31 Reference Field PO Line Item Number RFF-C156-1153 To specify a reference. Header Optional Alphanumeric 3

32 Reference Field PLA No. RFF-C156-1153 To specify a reference. Header Optional Alphanumeric 3

33 Reference Field Despatch Advice No. RFF-C156-1153 To specify a reference. Header Optional Alphanumeric 3

34 Location details Destination LOC-3227 To identify a place or a location or

related locations

Header Mandatory Alphanumeric 3

Page 85: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

84

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

35 Reference Field Registration No. RFF-C156-1153 To specify a reference. Header Optional Alphanumeric 3

36 Reference Field Despatch Advice No. RFF-1153- To indicate the type and function of a

message

Header Optional Alphanumeric 3

37 Reference Field Lot Number/ RFF-C156-153-BT To specify a reference. Header Optional Alphanumeric 3

38 Contact Information Customer Name and

address

CTA-C056-3412 To Identify a person or department

to whom the communication should

be directed

Header Mandatory Alphanumeric 35

39 Transport Information Name of the Transporter TDT-8051 To Specify information regarding the

transport such as mode of transport.

Header Optional Alphanumeric 3

40 Reference Field Vehicle Number RFF-1153-ABZ To specify information regarding the

transport

such as mode of transport, means

of transport its conveyance

reference number and the

identification of the means of

transport

Header Optional Alphanumeric 3

41 Reference Field Lorry Receipt No. RFF-1153- To indicate the type and function of a

message

Header Optional Alphanumeric 3

42 Transport Information Name of the Transporter TDT-8051 To Specify information regarding the

transport such as mode of transport.

Header Optional Alphanumeric 3

43 Transport Information Carrie name TDT-C040-3128 To specify information regarding the

transport

such as mode of transport, means

of transport its conveyance

reference number and the

identification of the means of

transport

Header Optional Alphanumeric 17

44 Terms of Delivery TOD-4055 To specify terms of delivery Header Mandatory Alphanumeric 3

45 Equipment Details EQD-8053 To identify a unit of equipment Header Mandatory Alphanumeric 3

46 Allowance or Charge ALC-5463 To Identify an allowance or charge

details

Header Mandatory Alphanumeric 3

Page 86: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

85

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

47 Duty/Tax/Fee details TAX-5283 To specify relevant duty/tax/fee

information.

Header Mandatory Alphanumeric 3

48 Currency Currency – INR CUX-6343-14 To specify currencies used in

transaction and relevant details for

the rate of exchange.

Header Optional Alphanumeric 3

49 Net Weight India Unique Detail Optional Alphanumeric 3

50 Line item Sr.No. LIN-7143-SN To identify a line item and

configuration.

Detail Mandatory Alphanumeric 3

51 Item Description Material

Code/Description of

goods

IMD-7077 To describe an item in an industry or

a free format

Detail Optional Alphanumeric 3

52 Additional product Information Part No. PIA-7143-PD To describe an item in either an

industry or free format

Detail Optional Alphanumeric 3

53 Item Description Model IMD-7077 To describe an item in either an

industry or free format

Detail Optional Alphanumeric 3

54 Item Description Description of Goods IMD-7077 To describe an item in either an

industry or free format

Detail Optional Alphanumeric 3

55 Measurements Unit of Measure` MEA-6311-ABW Code qualifying the purpose of the

measurement.

Detail Optional Alphanumeric 2

56 Measurements Weight - Invoice

Quantity

MEA-6311-WT Code qualifying the purpose of the

measurement.

Detail Optional Alphanumeric 3

57 Monetary Details Good item total MOA-C516-5025-66 To describe a pertinent amount Detail Optional Alphanumeric 3

58 Monetary Details Total line Amount MOA-C516-5025-79 To describe a pertinent amount Detail Optional Alphanumeric 3

59 Duty/Tax Information E.Cess TAX-C241-5153-OTH Code specifying a type of duty, tax or

fee.

Detail Mandatory Alphanumeric 3

60 Duty/Tax Information H.E.Cess TAX-C241-5153-OTH Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 3

61 Duty/Tax Information Basic Excise Duty TAX-C241-5153-EXC Code specifying a type of duty, tax or

fee.

Detail Mandatory Alphanumeric 3

Page 87: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

86

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

62 Price Details Sales Rate/UOM -Basic

price per unit.

PRI-C509-5379-PU Code qualifying the type of monetary

amount.

Detail Optional Alphanumeric 3

63 Monetary Details Sub Total MOA-C516-5025-499 Code qualifying the type of monetary

amount.

Detail Optional Alphanumeric 3

64 Duty/Tax Information Freight Charges TAX-5283 To specify relevant duty/tax/fee

information.

Detail Mandatory Alphanumeric 3

65 Duty/Tax Information Additional Excise duty TAX-C241-5153-EXC Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 3

66 Duty/Tax Information SED% TAX-C241-5153-EXC Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 3

67 Monetary Details Total Amount MOA-C516-5025-77 To specify a monetary amount Detail Mandatory Numeric 35

68 Quantity Quantity QTY-C186-6063-169 To specify a pertinent quantity Header Mandatory Alphanumeric 3

69 Document/Message Details. DOC-C002-1001-388 To identify documents and details

directly related to it.

Detail Mandatory Alphanumeric 3

70 Reference Field REF-C506-1153 To specify a reference. Header Mandatory Alphanumeric 3

71 Dangerous goods DGS-8273 To identify dangerous goods. Detail Mandatory Alphanumeric 3

72 Handling Instructions HAN-C524 To specify Handling where possible

to notify results

Detail Mandatory Alphanumeric

73 Package No. of Cases PAC-7224 To describe the number and type of

packages.

Detail Mandatory Alphanumeric 3

74 Package Type of packing PAC-3202 To describe the number and type of

packages.

Detail Optional Alphanumeric 3

75 Package Identification PCI-C210-7102 To specify marking and labels on

individual packages or physical units.

Detail Mandatory Alphanumeric 35

76 Transport Information Mode of Transport TDT-8051 To Specify information regarding the

transport such as mode of transport.

Detail Mandatory Alphanumeric 3

Page 88: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

87

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

77 Equipment Details EQD-8053 To identify a unit of equipment Detail Mandatory Alphanumeric 3

78 Allowance or Charge ALC-5463 To Identify an allowance or charge

details

Detail Mandatory Alphanumeric 3

79 Free text Excise Duty Percentage TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 512

80 Free text Sales Tax TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 512

81 Free text Other Charges TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 512

82 Free text Total amount in Words FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

83 Free text Duty in words FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

84 Free text Material Collected by: - FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

85 Free Text Education Cess

percentage

TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 512

86 Free Text Higher Education Cess

percentage

TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 512

87 Free Text Freight rate TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Detail Optional Alphanumeric 512

88 Free text Date and time of

Preparation

FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

89 Free Text Total amount in Words FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

90 Free Text Excise duty in words FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

Page 89: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

88

Goods Rejection Note - RETANN

Origin of Document - OEM

S. No EDIFACT- Field Name

Provider sample Field

Name

EDIFACT Code/Tag

Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT Standard

Character Length

91 Free Text remarks FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

92 Free text Authorized Signatory FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

93 Duty/Tax Information Tax TAX-C241-5153- Code specifying a type of duty, tax or

fee.

Trailer Optional Alphanumeric 3

94 Section Control UNS-0081 Section Identification Trailer Mandatory Alphanumeric 3

95 Free text Statement of certification FTX-C108 – 4440 To provide free form or coded text

information

Detail Optional Alphanumeric 512

96 Message Trailer UNT-0074 Number of segments in a message Trailer Mandatory Numeric 10

97 Message trailer UNT-0062 To end and check the completeness

of the message

Trailer Mandatory Alphanumeric 14

Page 90: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

89

3.10 EDI Document – Debit Note

3.10.1 Pre Requisite for the EDI – Sender’s End

Goods Rejection Note should have been created and the EDI for Goods Rejection Note

should have been shared with the supplier

3.10.2 Pre Requisite for the EDI – Receiver’s End

The Debit Note would need to be referenced to the Invoice EDI created by the supplier.

3.10.3 Triggers at Sender’s End

The OEM would compile the debit notes and credit notes created for a supplier and

prepare a Payment Order for instructing the bank to make payments.

3.10.4 Triggers at Receiver’s End

Receipt of a debit note does not trigger any transaction at the receiver’s end.

3.10.5 Governance

• Sender

- Debit Note Number should be referenced to the Goods Rejection note and the

line item number in the Goods Rejection Note.

- The reason for debit/ deduction should be documented as a part of the Debit

Note.

Page 91: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

90

3.10.6 High Level Document Flow

Su

pp

lie

r (R

ece

ive

r)O

EM

(S

en

de

r)

Page 92: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

91

3.10.7 Definition of EDI Standard

Debit Note - DEBADV

Origin of Document - OEM

S. No EDIFACT - Field Name Sample Provided Field Name EDIFACT Code/Tag

Name Description

Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Header - Code name of the

document - Debit Note - DEBADV.

UNH-0062 The message code for Debit

advise message is DEBADV

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group(If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group(If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group(If used) if not used,

within the interchange, for

the purpose of

acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data

elements in 0062 and S009

shall be used to identify

uniquely the message within

is group(If used) if not used,

within the interchange, for

the purpose of

Header Mandatory Alphanumeric 3

Page 93: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

92

Debit Note - DEBADV

Origin of Document - OEM

S. No EDIFACT - Field Name Sample Provided Field Name EDIFACT Code/Tag

Name Description

Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

acknowledgement.

6 Beginning of the message Name of the Document -(Debit

Note)

BGM-C002-1001-383 To identify the type and

function of a message and to

transmit the indentifying

number.

Header Mandatory Alphanumeric 3

7

Date/Time Period - Debit Date

Reference Date DTM- C507 To specify date, and/or time,

or period

Header Mandatory Alphanumeric 3

8 Date/Time Period - Debit Date Date of Debit DTM-C507-2005-228 To specify a date, and or time

period

Header Mandatory Alphanumeric 3

9 Name and Address Address of the OEM in debit

note

NAD-3035-BY To provide free form or coded

text information

Header Optional Alphanumeric 3

10

Parties and Instruction

Supplier Name INP-C849-3301 - 5 To identify the party enacting

an instruction

Header Mandatory Alphanumeric 3

11

Parties and Instruction

Party code INP-C489-3301-4 To identify the party enacting

an instruction

Header Optional Alphanumeric 3

12

Reference Field -Debit

Debit Note Number RFF-1153-DL To indicate the type and

function of the message to be

transmitted

Header Mandatory Alphanumeric 3

13 Reference Field Reference number REF-C506-1153-ACD To specify a reference. Header Mandatory Alphanumeric 3

14 Date/Time Period - Debit Date Reference date DTM-C2379-4 To specify a date, and or time

period

Header Mandatory Alphanumeric 3

Page 94: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

93

Debit Note - DEBADV

Origin of Document - OEM

S. No EDIFACT - Field Name Sample Provided Field Name EDIFACT Code/Tag

Name Description

Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

15 Payment Instruction Payment instructions for debit

note

PAI-C534-4439 To specify the terms for

payment.

Header Mandatory Alphanumeric 3

16 Monetary Amount Amount to be debited MOA-C516-5025-211 To Specify a monetary

amount

Header Mandatory Alphanumeric 3

17 Financial Institution Information FII-C3035 To indentify an account and a

related financial institution.

Header Mandatory Alphanumeric 3

18 Contact Information Phone No. of contact CTA-C056-3412 To Identify a person or a

department to whom the

contact should be directed.

Header Optional Alphanumeric 35

19

Contact Information

Customer Dispatch Details CTA-C056-3412 To Identify a person or a

department to whom the

contact should be directed.

Header Optional Alphanumeric 35

20 Parties and Instruction Vendor Code INP-C489-3301-5 To specify parties to an

instruction, the intruction,or

both.

Header Mandatory Alphanumeric 35

21 Processing Information GEI-C9649 To identify processing

information.

Header Mandatory Alphanumeric 3

22 Financial charges Allocation. FCA-4471 Description of allocation of

charges.

Detail Mandatory Alphanumeric 3

23 Allowance or Charge ALC -5643 To identify allowance or

charge Details.

Detail Mandatory Alphanumeric 3

24 Reference Field Invoice Date REF-C506-1153 To specify a reference. Header Optional Alphanumeric 3

25

Document/Message Details

Doc. Ref No. DOC-C002 To identify documents and

details directly related to it

Header Mandatory Alphanumeric 35

26 Date/Time Period - Debit Date

Doc. Ref Date DTM-C507 -2005 To specify date, and/or time,

or period

Header Optional Alphanumeric 3

27 Particulars : Item Code

Reference

India Unique Detail Optional Alphanumeric 20

Page 95: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

94

Debit Note - DEBADV

Origin of Document - OEM

S. No EDIFACT - Field Name Sample Provided Field Name EDIFACT Code/Tag

Name Description

Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

28 Description India Unique Detail Optional Alphanumeric 20

29 Particulars : Quantity India Unique Detail Optional Alphanumeric 10

30 Particulars : Rate India Unique Detail Optional Alphanumeric 10

31 Particulars : Value India Unique Detail Optional Alphanumeric 10

32 Duty/Tax details Particulars : ED & Tax TAX-C5283 To specify relevant

duty/tax/fee information

Detail Mandatory Alphanumeric 3

33 Monetary Amount Basic Amount MOA-C516-5025-499 Code qualifying the type of

monetary amount.

Detail Optional Alphanumeric 3

34

Monetary Amount

Particulars : Total Amount MOA-C516-5025-77 To specify a monetary

amount

Detail Optional Numeric 3

35

Free Text

Amount in Words FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

36

Duty/Tax details

VAT value TAX-5153-VAT Code specifying the basis for a

duty or tax or fee

rate.

Detail Optional Alphanumeric 3

37 Reference Field Invoice Number RFF-1153-IV To specify a reference. Header Optional Alphanumeric 3

38 Reference field GRA No. REF-C506-1153 To specify a reference. Header Optional Alphanumeric 3

39 Reference Field PO Reference Number REF-C506-1153-OP To specify a reference. Header Optional Alphanumeric 3

40 Authentication Result Statement Certifying the

authenticity of the information

provided

AUT-9280 To specify results of the

application of an

authentication procedure.

Trailer Mandatory Alphanumeric 35

41

Free Text

Approved By FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

42

Free Text

Authorized Signatory FTX-C108 - 4440 To provide free form or coded

text information

Detail Optional Alphanumeric 512

43 Message trailer UNT-0074 To end and check the

completeness of the message

Trailer Mandatory Alphanumeric 14

Page 96: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

95

Debit Note - DEBADV

Origin of Document - OEM

S. No EDIFACT - Field Name Sample Provided Field Name EDIFACT Code/Tag

Name Description

Part of the EDIFACT

Standard Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

44 Message trailer UNT-0062 To end and check the

completeness of the message

Trailer Mandatory Alphanumeric 14

Page 97: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

96

3.11 EDI Document – Credit Note

3.11.1 Pre Requisite for the EDI – Sender’s End

• GRN should have been created by the OEM and the EDI for GRN should have been

created.

• GRN acknowledgment (APERAK) should have been sent to the supplier.

3.11.2 Pre Requisite for the EDI – Receiver’s End

The Credit Note would need to be referenced to the Invoice EDI created by the supplier.

3.11.3 Triggers at Sender’s End

The OEM would compile the debit notes and credit notes created for a supplier and

prepare a Payment Order for instructing the bank to make payments.

3.11.4 Triggers at Receiver’s End

Receipt of a credit note does not trigger any transaction at the receiver’s end.

3.11.5 Governance

• Sender

- Credit Note Number should be referenced with the Supplier’s invoice number.

- The reason for credit should be documented as a part of the Credit Note.

Page 98: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

97

3.11.6 High Level Document Flow

Su

pp

lie

r (R

ece

ive

r)O

EM

(S

en

de

r)

Page 99: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

98

3.11.7 Definition of EDI Standard

Credit Note - CREADV

Origin of Document - OEM

S. No EDIFACT Field Name Provided Sample Fields Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

1 Header - Code name of the

document - Debit Note -

CREADV.

UNH-0062 The message code for Debit advise

message is CREADV

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements in

0062 and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in 0062

and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in 0062

and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier -

Controlling Agency Coded.

UNH-S009-0051 The combination of data elements in 0062

and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the Message Name of the Document -(Debit

Note)

BGM-C002-1001-381 To identify the type and function of a

message and to transmit the indentifying

number.

Header Mandatory Alphanumeric 3

7 Name and Address Name of the OEM NAD-3035-BY To provide free form or coded text

information

Header Optional Alphanumeric 3

Page 100: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

99

Credit Note - CREADV

Origin of Document - OEM

S. No EDIFACT Field Name Provided Sample Fields Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

8 Parties and Instruction Supplier Name INP-C849-3301 - 5 To identify the party enacting an

instruction

Header Mandatory Alphanumeric 35

9 Reference Field Credit Note Number REF-C506-1153-CD To specify a reference. Header Mandatory Alphanumeric 3

10 Date/Time Period GRA Date DTM-C507-2005- To specify a date/time period Header Optional Alphanumeric 3

11 Date/Time Period WC Date DTM-C507-2005- To specify a date/time period Header Optional Alphanumeric 3

12 Date/Time Period Approval Date DTM-C507-2005- To specify a date/time period Header Optional Alphanumeric 3

13 Date/Time Period Date of Credit DTM-C2379-4 To specify a date, and or time period Header Mandatory Alphanumeric 3

14 Monetary Amount Amount MOA-C516-5025-210 To Specify a monetary amount Header Mandatory Alphanumeric 3

15 Financial Institution

Information

FII-C3035 To indentify an account and a related

financial institution.

Header Mandatory Alphanumeric 3

16 Contact Details Customer Dispatch Details CTA-C056-3412 To identify a person or department to

whom the communication should be

directed.

Detail Optional Alphanumeric 35

17 Reference Field - Document

Reference number

Doc. Ref No. REF-C506-1153-ACD To specify a reference. Header Mandatory Alphanumeric 3

18 Date/Time Period Doc. Ref Date DTM-C2379-4 To specify a date, and or time period Header Mandatory Alphanumeric 3

Page 101: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

100

Credit Note - CREADV

Origin of Document - OEM

S. No EDIFACT Field Name Provided Sample Fields Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

19 Processing Information GEI-C9649 To identify processing information. Header Mandatory Alphanumeric 3

20 Financial charges Allocation. FCA-C4471 Description of allocation of charges. Detail Mandatory Alphanumeric 3

21 Allowance or Charge ALC -5643 To identify allowance or charge Details. Detail Mandatory Alphanumeric 3

22 Duty/Tax Details Particulars : ED & Tax TAX-C5283 To specify relevant duty/tax/fee

information

Detail Mandatory Alphanumeric 3

23 Monetary Amount Particulars : Total Amount MOA-C516-5025-210 To Specify a monetary amount Header Mandatory Alphanumeric 3

24 Parties and Instruction Vendor Code INP-C849-3301 - 5 To identify the party enacting an

instruction

Header Mandatory Alphanumeric 3

25 Reference Field Invoice Number REF-C506-1153-IV To specify a reference. Header Mandatory Alphanumeric 3

26 Date/Time Period Invoice Date DTM-C To specify a date, and or time period Header Mandatory Alphanumeric 3

27 Particulars : Item Code Reference India Unique Detail Optional Alphanumeric 20

28 Description : Particulars India Unique Detail Optional Alphanumeric 20

29 Particulars : Quantity India Unique Detail Optional Alphanumeric 10

Page 102: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

101

Credit Note - CREADV

Origin of Document - OEM

S. No EDIFACT Field Name Provided Sample Fields Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

30 Particulars : Rate India Unique Detail Optional Alphanumeric 10

31 Particulars : Value India Unique Detail Optional Alphanumeric 10

32 Free Text Amount in Words FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

33 Duty/Tax Details VAT Value TAX-5153-VAT Code specifying the basis for a duty or tax

or fee

rate.

Detail Optional Alphanumeric 3

34 Document /message details DOC-C002 To identify documents and details directly

related to it.

Trailer Mandatory Alphanumeric 35

35 Reference Field Depot No. RFF-C506-1153- To specify a reference. Header Optional Alphanumeric 3

36 Reference Field GRA No. REF-C506-1153 To specify a reference. Header Optional Alphanumeric 3

37 Reference Field WC No. REF-C506-1153 To specify a reference. Header Optional Alphanumeric 3

38 Reference Field Approval No. REF-C506-1153 To specify a reference. Header Optional Alphanumeric 3

39 Way Bill Number India Unique Header Optional Alphanumeric 3

40 Authentication statement Statement Certifying the authencity

of the Information provided

AUT-C9280 To specify results of the application of an

authentication procedure.

Trailer Mandatory Alphanumeric 35

Page 103: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

102

Credit Note - CREADV

Origin of Document - OEM

S. No EDIFACT Field Name Provided Sample Fields Name EDIFACT Code/Tag

Name

Description Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

41 Free Text Approved By FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

42 Free Text Authorized Signatory FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

43 Message Trailer UNT-0074 Number of Segments in a message Trailer Mandatory Numeric 10

44 Message trailer UNT-0074 To end and check the completeness of the

message

Trailer Mandatory Alphanumeric 14

Page 104: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

103

3.12 EDI Document – Remittance Advice

3.12.1 Pre Requisite for the EDI – Sender’s End

• EDI details debit and credit notes should have been shared with the supplier.

• The OEM should have provided required instructions to the bank for making payments

to the supplier by triggering the EDI transaction PAYORD (this is beyond the scope of

the project).

3.12.2 Pre Requisite for the EDI – Receiver’s End

All the required invoices should have been shared with the OEM.

3.12.3 Triggers at Sender’s End

The accounts payables/ receivables are updated after the payments have been made.

3.12.4 Triggers at Receiver’s End

After the receipt of the payment from the bank, the accounts can be updated.

3.12.5 Governance

• Sender

- The details for the deduction and payments should be linked line item-wise to

appropriate document number such as invoice number/ invoice rejection

number/ debit note number/ credit note number.

- Reason code values should be captured for the deductions.

- Other business rules remain the same.

- In case of payments made through NEFT/ RTGS mode, Unique Transaction

Number (UTN) is provided by the banker to the OEM. The OEM would include

this UTN Number in the Remittance Advice.

Page 105: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

104

3.12.6 High Level Document Flow

Su

pp

lie

r (R

ece

ive

r)O

EM

(S

en

de

r)

Page 106: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

105

3.12.7 Definition of EDI Standard

Remittance Advice - REMADV

Origin of Document - OEM

S. No EDIFACT - Field Name Provider Sample Field

Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header- Purchase

Order

UNH-062 A service segment starting and uniquely

identifying a message. The message type

code for Informing fund transfers is

REMADV

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements in

0062 and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in

0062 and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in

0062 and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

Page 107: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

106

Remittance Advice - REMADV

Origin of Document - OEM

S. No EDIFACT - Field Name Provider Sample Field

Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

5 Message Identifier -

Controlling Agency Coded.

UNH-S009-0051 The combination of data elements in

0062 and S009 shall be used to identify

uniquely the message within is group(If

used) if not used, within the interchange,

for the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6

Beginning of the message

Document Name -

Remittance Advice

BGM-C002-1001-481 To indicate the type and function of a

message and to transmit the identifying

number.

Header Mandatory

7 Date/Time/Period Date of Amendment DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

8 Date/Time/Period Receipt Date DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

9 Date/Time/Period GI Date DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

10 Date/Time/Period Cheque date DTM-C507 To specify date, and or Time Header Mandatory Alphanumeric 3

11

Free Text Information Name of the Supplier: Pre

printed Information

FTX-C108 - 4440 To provide free form or coded text

information

Header Optional Alphanumeric 512

12

Free Text Information Address of the Supplier :

Pre Printed Information

FTX-C108 - 4440 To provide free form or coded text

information

Header Optional Alphanumeric 512

13 Free Text Information

Text Information: Email

FTX-C108 - 4440 To provide free form or coded text

information

Header Optional Alphanumeric 512

14

Name and Address

Bill To and Ship To address NAD-C080-3124 To specify the name/address and their

related function

Header Mandatory Alphanumeric 35

15 Reference Field REF-C506-1153 To specify a reference. Header Mandatory Alphanumeric 3

Page 108: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

107

Remittance Advice - REMADV

Origin of Document - OEM

S. No EDIFACT - Field Name Provider Sample Field

Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

16 Contact Information Contact Person CTA- To Identify a person or department to

whom the communication should be

directed

Header Mandatory

17 Currency CUX-C504-6437 To specify currencies used in transaction

and relevant details for the rate of

exchange

Header Mandatory Alphanumeric 3

18 Financial Institution

Information

Account Number FII-3035-SU To identify an account and a related

financial institution.

Header Mandatory Alphanumeric 3

19 Document/Message Details. DOC-C002 To identify documents and details

directly related to it.

Detail Mandatory Alphanumeric 3

20 Currency CUX-C504-6437 To specify currencies used in transaction

and relevant details for the rate of

exchange

Detail Mandatory Alphanumeric 3

21 Adjustment Details AJT-4465 To identify a reason for an adjustment Detail Mandatory Alphanumeric 3

22 Monetary Amount Amount MOA-C516-5004 To specify a monetary amount Detail Mandatory Numeric 35

23 Monetary Amount Advance Adj. MOA-C516-5004 To specify a monetary amount Detail Optional Numeric 35

24 Duty/Tax Information

TDS/ASN

TAX-5283 To specify relevant duty/tax/fee

information.

Detail Mandatory Alphanumeric 3

25 Parties and Instruction

INP-C849-3301 To specify parties to an instruction, the

instruction, or both

Detail Mandatory Alphanumeric 35`

26

Document Line Identification

To identify the processing mode of a

specific line within an documents

Detail Mandatory Alphanumeric 3

27 Currency CUX-C504-6437 To specify currencies used in transaction

and relevant details for the rate of

exchange

Detail Mandatory Alphanumeric 3

Page 109: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

108

Remittance Advice - REMADV

Origin of Document - OEM

S. No EDIFACT - Field Name Provider Sample Field

Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

28 Reference Field Document Date DTM-C2379-4 To specify a reference. Header Mandatory Alphanumeric 3

29 Reference Field Document Number -

Invoice Number

/Supplementary

Number/Good Rejection

No.

RFF-1153 To indicate the type and function of a

message

Detail Mandatory Alphanumeric 3

30 Adjustment Details Reason Code AJT-4465 To identify a reason for an adjustment Detail Mandatory Alphanumeric 3

31 Duty/Tax Information

TAX-5283 To specify relevant duty/tax/fee

information.

Detail Mandatory Alphanumeric 3

32 Monetary Amount Amount to be Paid MOA-C516-5004 To specify a monetary amount Detail Mandatory Numeric 35

33 Monetary Amount Total MOA-C516-5004 To specify a monetary amount Detail Mandatory Numeric 35

34 Section Control UNS-0081 Section Identification Trailer Mandatory

35 Allowance or Charge ALC-5463 To Identify an allowance or charge

details

Detail Mandatory Alphanumeric 3

36 Message Trailer UNT-0074 Number of Segments in a message Trailer Mandatory Numeric 10

37 Message trailer UNT-0062 To end and check the completeness of

the message

Trailer Mandatory Alphanumeric 14

38 Cheque Number India Unique Trailer Mandatory Numeric 35

39 Cheque Amount India Unique Trailer Mandatory Numeric 35

40 Voucher Number India Unique Trailer Mandatory Numeric 35

41 Vendor Site India Unique Trailer Mandatory Numeric 35

42 Reference Field GI Date RFF-C506-1153 To specify a reference. Header Optional Alphanumeric 3

43 Supplier Number India Unique Trailer Mandatory Numeric 35

Page 110: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

109

Remittance Advice - REMADV

Origin of Document - OEM

S. No EDIFACT - Field Name Provider Sample Field

Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

44

Reference Field UTN Number RFF-C506-1153-ANU To specify a financial transaction number Detail Mandatory Alphanumeric 3

45

Name and Address

Accounts Dept.Addres

details NAD-C080-3124

To specify the name/address and their

related function Detail Optional Alphanumeric 3

Page 111: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

110

3.13 EDI Document – Purchase Order Amendment

3.13.1 Pre Requisite for the EDI – Sender’s End

• EDI details for original/ blanket PO should be available.

• The price master should have been updated, if required.

3.13.2 Pre Requisite for the EDI – Receiver’s End

After the receipt of the EDI message for original PO from the OEM, the ‘APERAK’ message

type for PO acknowledgement should have been triggered by the supplier. The original PO

details should have been updated in the ERP of the supplier. This is required because the

amendment PO needs to be mapped to the original PO.

3.13.3 Triggers at Sender’s End

When the amended PO is created in the ERP of the OEM, an EDI for Amended PO would be

triggered. This would capture details such as amended PO number and the PO number to

which the amended PO is mapped, changes in the price/ quantity/ item etc and the date

from which the PO would be effected.

3.13.4 Triggers at Receiver’s End

When the EDI file for the amended PO reaches the supplier, it would be required to

acknowledge the receipt of the amended PO details. The acknowledgement triggered is

sent using the EDI message type APERAK.

3.13.5 Governance

• Sender

- The amended PO number should be mapped/ linked to the original/ blanket PO

number.

- The changes to price and/or payment terms and/ or delivery terms should be

updated in the ERP of the OEM before creating the amended PO.

- The amended PO should contain details such as the line item of the original PO

to which the change is applicable.

Page 112: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

111

3.13.6 Definition of EDI Standard

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

1 Message Header- Purchase Order

Change - ORDCHG

UNH-062 A service segment starting and uniquely

identifying a message. The message type

code for purchase orders is "Orders"

Header Mandatory Alphanumeric 14

2 Message Identifier - Message

Type

UNH-S009-0065 .The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message

release number

UNH-S009-0054 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controlling

Agency Coded.

UNH-S009-0051 The combination of data elements in 0062

and S009 shall be used to identify uniquely

the message within is group(If used) if not

used, within the interchange, for the

purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message Purchase Order Name BGM-C002-1001-230 To indicate the type and function of a

message and to transmit the identifying

number.

Header Mandatory Alphanumeric 3

7 Name and Address Name of the OEM's NAD-030-3124 To provide free form or coded text

information

Header Optional Alphanumeric 35

Page 113: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

112

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

8 Name and Address Address of the OEM NAD-C058-BY To provide free form or coded text

information

Header Optional Alphanumeric 35

9 Parties and Instruction Supplier Code/Vendor Code INP-C849-3301 - 5 Code qualifying a reference Header Mandatory Alphanumeric 3

10 Reference Field Amendment number RFF-C516-1153-PP To specify a reference. Header Mandatory Alphanumeric 3

11 Date/Time/Period PO Date DTM-C507-2005-4 To specify date, and/or time, or period. Header Mandatory Alphanumeric 3

12 Date/Time/Period Print Date DTM-C507-2005 To specify a date, and or time period Header Mandatory Alphanumeric 3

13 Date/Time/Period Amendment Date DTM-C507-2005-388 To specify date, and/or time, or period. Header Mandatory Alphanumeric 3

14 Free Text Information Statement - "Sales pof goods …." FTX-C108 - 4440 To provide free form or coded text

information

Header Optional Alphanumeric 512

15 Free Text Information Pre-Printed statutory information FTX-C108 - 4440 To provide free form or coded text

information

Header Optional Alphanumeric 512

16 Reference Field Reference Details and numbers REF-C506-1153 To specify a reference. Header Mandatory Alphanumeric 3

17 Name and Address Bill To NAD-3035-AA To Specify the name/address and their

related function .

Header Mandatory Alphanumeric 3

Page 114: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

113

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

18 Name and Address Ship to NAD-3035-ST To Specify the name/address and their

related function .

Header Mandatory Alphanumeric 3

19 Name and Address Supplier Name NAD-C058-3124 To Specify the name/address and their

related function .

Header Optional Alphanumeric 35

20 Document/Message Details. DOC-C002-1001-230 To identify documents and details directly

related to it.

Header Mandatory Alphanumeric 3

21 Contact Information Contact Person CTA- C3139 To identify a person or a department to

whom communication should be directed.

Header Mandatory Alphanumeric 35

22 Communication Contact Buyer E-mail, Telephone COM-C076-3148 To identify a communication number of a

department or a person to whom

communication should be addressed.

Header Optional Alphanumeric 3

23 Communication Contact Buyer Contact No. CTA-C056-3412 To identify a communication number of a

department or a person to whom

communication should be addressed.

Header Optional Alphanumeric 17

24 Duty/Tax/Fee Details TAX-5283 To specify relevant duty/tax/fee

information.

Header Mandatory Alphanumeric 3

25 Supplier CST reg No.

26 Currency INR/Rs. CUX-C504-6347 To specify currencies used in transaction

and relevant details for the rate of exchange.

Header Mandatory Alphanumeric 3

27 Payment Terms Payment Terms PYT - 4279 To specify the terms of payment Header Mandatory Alphanumeric 3

Page 115: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

114

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

28 Monetary Details MOA-C516 To specify a monetary amount Header Mandatory Alphanumeric 3

29 Transport Information TDT-8051 To Specify information regarding the

transport such as mode of transport.

Header Mandatory Alphanumeric 3

30 Location /Place Identification Plant Dc/Name/Storage location LOC-3227 To Identify a place or a location and or

related locations.

Header Mandatory Alphanumeric 3

31 Terms of Delivery Terms of delivery notification TOD-4055 To specify terms of delivery Header Mandatory Alphanumeric 3

32 Package Details PAC-7224 To describe the number and type of

package/physical units.

Header Mandatory

33 Package Identification PCI-C210-7102 To specify marking and labels on individual

packages or physical units.

Header Mandatory Alphanumeric 35

34 Equipment Details EQD-8053 To identify a unit of equipment Header Mandatory Alphanumeric 3

35 Scheduling conditions. SCH-4017 To specify scheduling conditions. Header Mandatory Alphanumeric 3

36 Quantity QTY-C186-6060 To specify a pertinent quantity Header Mandatory Alphanumeric 35

37 Additional Price information Apr-43 To provide information concerning pricing

related to class of trade.

Header Mandatory Alphanumeric 3

Page 116: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

115

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

38 Allowance or Charge ALC-5463 To Identify an allowance or charge details Header Mandatory Alphanumeric 3

39 Quantity QTY-C186-6060 To specify a pertinent quantity Header Mandatory Alphanumeric 35

40 Percentage Details PCD-C501-5245 To specify percentage Information Header Mandatory Alphanumeric 3

41 Monetary Details MOA-C516 To specify a monetary amount Header Mandatory Alphanumeric 3

42 Rate Details. RTE-C128-5420 To specify rate information Header Mandatory Numeric 15

43 Tax/Duty/Fee details TAX-5283 To specify relevant duty/tax/fee

information.

Header Mandatory Alphanumeric 3

44 Requirement and conditions RCS-7293 To specify sector/subject requirements and

conditions

Header Mandatory Alphanumeric 3

45 Dangerous goods DGS-8273 To identify dangerous goods. Header Mandatory Alphanumeric 3

46 Contact Information CTA-C3139 To indentify a person or department to

whom the communication should be

directed.

Header Mandatory Alphanumeric 3

47 Lin No. Sr.No LIN-7143-SN To Identify a line Item and configuration Detail Mandatory Alphanumeric 6

Page 117: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

116

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

48 Item Description Item Description IMD- C272 To describe an item in either an industry or

free format

Detail Optional Alphanumeric 17

49 Additional Product ID Part No. PIA-7143-BH Coded identification of an item type Detail Optional Alphanumeric 3

50 Additional Product ID Material description PIA-7143-PD To describe an item in either an industry or

free format

Detail Optional Alphanumeric 17

51 Measurements Unit of Measure` MEA-6311-ABW Code qualifying the purpose of the

measurement.

Detail Optional Alphanumeric 3

52 Characteristic/Class ID CCI-7059 To Identify and describe a specific

characteristic.

Detail Mandatory Alphanumeric 3

53 Monetary Details Sub Total/Line items total MOA-C516-5125-66 To specify a monetary amount Detail Mandatory Alphanumeric 3

54 Price Details. Price of line item per unit PRI-C509-5379-PU Code qualifying the type of monetary

amount.

Detail Mandatory Alphanumeric 3

55 Monetary Details Good line item amount MOA-C516-5025-66 To describe a pertinent amount Detail Mandatory Alphanumeric 3

56 Monetary Details Total line Amount MOA-C516-5025-79 To describe a pertinent amount Detail Mandatory Alphanumeric 3

57 Date/Time/Period Price effective date DTE-C507-2005 To specify a date, and or time period Detail Optional Alphanumeric 3

Page 118: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

117

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

58 Payment Terms PYT-4279 To specify the terms of payment Detail Mandatory Alphanumeric 3

59 Monetary Details Amount MOA-C516 To specify a monetary amount Detail Mandatory Alphanumeric 3

60 Price Details. Old rate PRI-C509-5379-PU Code qualifying the type of monetary

amount.

Detail Optional Alphanumeric 3

61 Price Details. New rate PRI-C509-5379-PU Code qualifying the type of monetary

amount.

Detail Optional Alphanumeric 3

62 Date/Time/Period New effective date - Price DTM-C507-2005-7 To specify date, and/or time, or period. Detail Optional Alphanumeric 3

63 Date/Time/Period Current Effective date-Price DTM-C507-2005-7 To specify date, and/or time, or period. Detail Optional Alphanumeric 3

64 Price Details. New Value and Old Value of Po's PRI-C509-5125 To specify price information. Detail Mandatory Alphanumeric 3

65 Reference Field REF-C506-1153 To specify a reference. Detail Mandatory Alphanumeric 3

66 Package Details PAC-7224 To describe the number and type of

package/physical units.

Detail Mandatory Alphanumeric 3

67 Reference Field REF-C506-1153 To specify a reference. Detail Mandatory Alphanumeric 3

Page 119: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

118

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

68 Quantity Measurements/Unit QTY-C185-6411 To specify a pertinent Quantity Detail Mandatory Alphanumeric 8

69 Package Identification Container type PCI-C531-7233 To specify marking and labels on individual

packages or physical units.

Detail Mandatory Alphanumeric 3

70 Location /Place Identification Plant Dc/Name/Storage location LOC-3227 To Identify a place or a location and or

related locations.

Detail Mandatory Alphanumeric 3

71 Tax/Duty/Fee details Excise duty/Tax TAX-C241-5153-EXC Code specifying a type of duty, tax or fee. Detail Optional Alphanumeric 3

72 Reference Field Drawing doc number REF-C506-1153-AAL To specify a reference. Detail Mandatory Alphanumeric 3

73 Document/Message Details. DOC-C002 To identify documents and details directly

related to it.

Detail Mandatory Alphanumeric 3

74 Contact Information Contact Person

name/department

CTA-C3139 To indentify a person or department to

whom the communication should be

directed.

Detail Mandatory Alphanumeric 3

75 Allowance or Charge ALC-5463 To Identify an allowance or charge details Detail Mandatory Alphanumeric 3

76 Quantity Amended quantity QTY-C6060 To specify a pertinent quantity. Detail Mandatory Alphanumeric 35

77 Percentage Details PCD-C501-5245 To specify percentage Information Detail Mandatory Alphanumeric 3

Page 120: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

119

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

78 Monetary Details Total Amount/Revised Value MOAC516-5025-77 To specify a monetary amount Detail Mandatory Alphanumeric 35

79 Rate Details Per Unit Price RTE-C128- 5420 To specify rate information. Detail Mandatory Numeric 15

80 Tax/Duty/Fee details TAX-5283 To specify relevant duty/tax/fee

information.

Detail Mandatory Alphanumeric 3

81 Terms of Delivery Terms of delivery notification TOD-4055 To specify terms of delivery Detail Mandatory Alphanumeric 3

82 Equipment Details EQD-8053 To identify a unit of equipment Detail Mandatory Alphanumeric 3

83 Scheduling conditions. SCH-4017 To specify scheduling conditions. Detail Mandatory Alphanumeric 3

84 Requirement and conditions RCS-7293 To specify sector/subject requirements and

conditions

Detail Mandatory Alphanumeric 3

85 Transport Information TDT-8051 To specify transport Particulars Detail Mandatory Alphanumeric 3

86 Stages STG-9421 To provide information related to the kind

of stage in process.

Detail Mandatory Alphanumeric 3

87 Quantity QTY-C6060 To specify a pertinent quantity. Detail Mandatory Alphanumeric 35

Page 121: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

120

PO Amendment - ORDCHG

Origin of Document - OEM

S. No EDIFACT - Field Name Provider sample Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT

Standard

Structure

EDIFACT Standard

(Mandatory/Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character

Length

88 Dangerous goods DGS-8273 To identify dangerous goods. Detail Mandatory Alphanumeric 3

89 Contact Information Contact Person name CTA-C3139- To indentify a person or department to

whom the communication should be

directed.

Detail Mandatory Alphanumeric 3

90 Section Control UNS-0081 To separate the header, detail and summary

sections of the message.

Trailer Mandatory Alphanumeric 1

91 Allowance or Charge ALC-5463 To Identify an allowance or charge details Detail Mandatory Alphanumeric 3

92 Free Text Information Amount in words FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

93 Free Text Information Terms and conditions FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

94 Free Text Information Authorized Signatory FTX-C108 - 4440 To provide free form or coded text

information

Trailer Optional Alphanumeric 512

95 Message trailer UNT-0074 To end and check the completeness of the

message

Trailer Mandatory Alphanumeric 10

96 Message trailer UNT-0062 To end and check the completeness of the

message

Trailer Mandatory Alphanumeric 14

Page 122: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

121

3.14 EDI Document – Price Catalogue

3.14.1 Pre Requisite for the EDI – Sender’s End

• If the Price Catalogue sender is a Supplier, the price catalogue is published from the

price master, and if the sender of the EDI message is an OEM, the price catalogue is

either published from the material master where each Supplier’s price is maintained

for an item, or from the Vendor Master, where prices for all materials supplied by a

Vendor are maintained.

• The receiving party details should exist in the application/ ERP.

3.14.2 Pre Requisite for the EDI – Receiver’s End

The receiver can receive the data in any of the masters as indicated above, depending on

whether the receiver is a Supplier or an OEM.

3.14.3 Triggers at Sender’s End

The product master data in the internal application/ ERP would be updated as per the

agreed price catalogue.

3.14.4 Triggers at Receiver’s End

• Receipt of PRICAT should trigger the EDI message type APERAK at the receiver’s end

to inform the sender that the message has been received by the receiver’s application.

• The product master data in the internal application/ ERP would be updated as per the

new and agreed price catalogue.

3.14.5 Governance

• The Price/ Sales Catalogue message may be applicable to the entire list of products or a

group of products/ items offered. The trading partners would need to agree on

whether the EDI would be triggered only to notify the particular change to the

catalogue or the EDI should contain information on complete list of the offered items.

However, the EDI should be triggered each time a change is made to the pricing

catalogue.

• Only the base price of the material/ component would be transmitted as a part of the

EDI message. Tax component of the overall price would be excluded.

• The receiver of the EDI should provide an acknowledgement to the sender if the Price

Catalogue is acceptable. Basis this acknowledgement, the pricing and catalogue details

would be used as reference in subsequent EDI interchanges.

Page 123: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

122

3.14.6 Definition of EDI Standard

S.No EDIFACT - Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/ Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

1 Message Header- Price Catalogue UNH-062 A service segment starting and uniquely identifying a

message. The message type code for the Price/sales

catalogue message is PRICAT.

Header Mandatory Alphanumeric 14

2 Message Identifier - Message Type UNH-S009-0065 The combination of data elements in 0062 and S009

shall be used to identify uniquely the message within

is group(If used) if not used,within the interchange,for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 6

3 Message Identifier - Message

version number

UNH-S009-0052 The combination of data elements in 0062 and S009

shall be used to identify uniquely the message within

is group(If used) if not used,within the interchange,for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

4 Message Identifier - Message release

number

UNH-S009-0054 The combination of data elements in 0062 and S009

shall be used to identify uniquely the message within

is group(If used) if not used,within the interchange,for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

5 Message Identifier - Controling

Agency Coded.

UNH-S009-0051 The combination of data elements in 0062 and S009

shall be used to identify uniquely the message within

is group(If used) if not used,within the interchange,for

the purpose of acknowledgement.

Header Mandatory Alphanumeric 3

6 Beginning of the message BGM-C002-1001-9 To indicate the type and function of a message and to

transmit the identifying number.

Header Mandatory Alphanumeric 3

7 Date/Time/Period DTM-C507-2005-299 To specify date, and/or time, or period. Header Mandatory Alphanumeric 3

8 Additional Information ALI-3239 To indicate that special conditions due to the origin,

customs preference, fiscal or commercial factors are

applicable.

Header Optional Alphanumeric 3

Page 124: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

123

S.No EDIFACT - Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/ Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

9 Free Text Information FTX-4451 To provide free form or coded text information. Header Mandatory Alphanumeric 3

10 Reference REF-C506-1153 To specify a reference. Header Mandatory Alphanumeric 3

11 Date/Time/Period DTM-C507-2005 To specify date, and/or time, or period. Header Mandatory Alphanumeric 3

12 Name and Address NAD-3035 To specify the name/address and their related

function, either by C082 only and/or unstructured by

C058 or structured by C080 through 3207.

Header Mandatory Alphanumeric 3

13 Place/ Location Identification LOC-3227 To identify a place or a location and/or related

locations

Header Mandatory Alphanumeric 3

14 Reference REF-C506-1153 To specify a reference. Header Mandatory Alphanumeric 3

15 Date/Time/Period DTM-C507-2005 To specify the date and/or time related to the

reference.

Header Mandatory Alphanumeric 3

16 Contact Information CTA-3139 To identify a person or a department to whom

communication should be directed.

Header Optional Alphanumeric 3

17 Communication Contact COM-C076-3148 To identify a communication number of a department

or a person to whom communication should be

directed.

Header Mandatory Alphanumeric 512

18 Monetary amount MOA-C516-5025 To specify a monetary amount. Header Mandatory Alphanumeric 3

19 Date/Time/Period DTM-C507-2005 To indicate the date of application of the specified tax.

Header Mandatory Alphanumeric 3

20 Currencies CUR-C504-6347 To specify currencies used in the transaction and

relevant details for the rate of exchange.

Header Mandatory Alphanumeric 3

21 Date/Time/Period DTM-C507-2005 To specify the date/time/period related to the rate of

exchange.

Header Mandatory Alphanumeric 3

22 Payment Term Basis PAT-4279 To specify the payment terms basis Header Mandatory Alphanumeric 3

23 Date/Time/Period DTM-C507-2005 To give the specific date/time/period, if needed,

of any payments, discounts, installments etc

Header Mandatory Alphanumeric 3

Page 125: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

124

S.No EDIFACT - Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/ Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

24 Monetary amount MOA-C516-5025 To specify amounts related to payment discounts,

penalties or installments.

Header Mandatory Alphanumeric 3

25 Details of transport TDT-8051 To specify the transport details such as mode of

transport, means of transport, its conveyance

reference number and the identification of the means

of transport.

Header Mandatory Alphanumeric 3

26 Place/ Location Identification LOC-3227 To identify locations relevant to the transport

specified in the TDT segment, e.g. place of departure

or

border crossing point.

Header Mandatory Alphanumeric 3

27 Terms of delivery or transport TOD-4055 To specify terms of delivery or transport Header Optional Alphanumeric 3

28 Place/ Location Identification LOC-3227 To identify locations relevant to the delivery terms

specified in the TOD segment.

Header Mandatory Alphanumeric 3

29 Allowance or Charge ALC-5463 To identify allowance or charge details Header Mandatory Alphanumeric 3

30 Additional Information ALI To indicate that the allowance or charge specified is

subject to special conditions owing to origin, customs

preference or commercial factors.

Header Optional Alphanumeric 3

31 Date/Time/Period DTM-C507-2005 To indicate any dates, times or periods applicable to

the allowances and charges specified at heading level

Header Mandatory Alphanumeric 3

32 Quantity QTY-C186-6063 To specify a pertinent quantity Header Mandatory Alphanumeric 3

33 Range Details RNG-6167 To specify, if required, the range to which the

allowance or charge applies

Header Mandatory Alphanumeric 3

34 Rate Details RTE-C128-5419 To specify the rate per unit and the basis for

calculation

Header Mandatory Alphanumeric 3

35 Product Group Information PGI-5379 To indicate the group in which a product belongs Details Mandatory Alphanumeric 3

Page 126: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

125

S.No EDIFACT - Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/ Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

36 Date/Time/Period DTM-C507-2005 To indicate date/time/period related to the price

group. e.g. expiration date/time or validity period for

the price group. Lead time of the goods/services

mentioned in the price group can also be provided by

the DTM segment

Details Mandatory Alphanumeric 3

37 Quantity QTY-C186-6063 To specify pertinent quantities related to the specified

price group, e.g. minimum order quantity

Details Mandatory Alphanumeric 3

38 Free Text Information FTX-4451 To provide free form or coded text information. Details Optional Alphanumeric 512

39 Price Details PRI-C509-5125 To provide either the unit or reference price and the

price type, valid for the pricing group

Details Mandatory Alphanumeric 3

40 Additional Price Information APR-4043 To identify additional pricing information related to

the class or type of trade and additionally

identifying the reason for any change

Details Optional Alphanumeric 3

41 Package PAC-7224

To describe the number and type of

packages/physical units

Details Optional Numeric 8

42 Measurements MEA-6311 To specify physical measurements, including

dimension tolerances, weights and counts

Details Mandatory Alphanumeric 3

43 Handling Instructions HAN To specify handling and where necessary, notify

hazards

Details Optional Numeric 70

44 Line item LIN-C212 To identify a line item and configuration Details Optional Numeric 35

45 Additional Product Id PIA-4347 To specify additional or substitutional item

identification codes

Details Mandatory Alphanumeric 3

Page 127: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

126

S.No EDIFACT - Field Name EDIFACT Code/Tag Name Description

Part of the

EDIFACT Standard

Structure

EDIFACT Standard

(Mandatory/ Optional)

EDIFACT Standard

Character Type

EDIFACT

Standard

Character Length

46 Item Description IMD-7077 To describe an item in either an industry or free

format

Details Optional Numeric 3

47 Characteristic/ Class ID CCI-7059 To identify and describe a specific characteristic and

its relevance for subsequent business processes

Details Optional Numeric 3

48 Characteristic value CAV-7110 To provide the value of a characteristic Details Optional Alphanumeric 3

49 Hierarchy Information HYN-7173 To identify hierarchical connections from a given

item to a higher or lower levelled item or to

identify dependencies among the content of

hierarchically related data

Details Mandatory Alphanumeric 3

50 Message Trailer UNT-0074 Number of Segments in a message Trailer Mandatory Numeric 10

51 Message trailer UNT-0062 To end and check the completeness of the message Trailer Mandatory Alphanumeric 14

Page 128: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

127

4 List of Contributors

4.1.1 Report Contribution

The following individuals contributed to the development, review and finalization of this report:

Name Organization

NareshAudukoori KPMG

N Chandrasekaran Ashok Leyland Limited

AbhilashaGoel Maruti Suzuki India Limited

VarunGulati KPMG

Sri Karumbati StumppSchuele&Somappa Springs Private Limited

Amit Kumar Society of Indian Automobile Manufacturers (SIAM)

Naveen Nathaniel KPMG

NeerajaRao Automotive Component Manufacturers Association of India (ACMA)

SaurabhRohilla Society of Indian Automobile Manufacturers (SIAM)

Vijay Sethi Hero MotoCorp Limited

S Srinivasan Sundaram Fasteners Limited

Rajesh Uppal Maruti Suzuki India Limited

Anil Kumar Unni Automotive Component Manufacturers Association of India (ACMA)

S Vijay KPMG

Page 129: B2B EDI Interchange - AcmaIT · 2011-12-14 · 3 3.4.5 High Level Document Flow - Method 1 (Consignment Number generated by OEM) 37 3.4.6 Pre Requisite for the EDI – Sender’s

128

4.1.2 Survey and/or Workshop Contribution

The following organizations either participated in the industry survey on B2B document interchange and/ or participated in the regional workshops:

Automobile OEMs Automotive Suppliers Others

Ashok Leyland Limited Anand Automotive Limited TVS Logistics Services Limited

Bajaj Auto Limited Asahi India Glass Limited

Hero MotoCorp Limited Bosch Limited

Maruti Suzuki India Limited Brakes India Limited

Mahindra Navistar Automotives Limited Eaton Technologies Private Limited

Tata Motors Limited Ganage Pressings Private Limited

Toyota Kirloskar Motor Private Limited Gold Seal Engineering Products Private Limited

TVS Motor Company Limited Hi-Tech Gears Limited

India Pistons Limited

Lucas-TVS Limited

Rane Holdings Limited

Rane TRW Steering Systems Limited

Rico Auto Industries Limited

Sansera Engineering Private Limited

Shriram Pistons & Rings Limited

Sono Koyo Steering Systems Limited

StumppSchuele&Somappa Springs Private Limited

Sundaram Fasteners Limited

Toyota Kirloskar Auto Parts Private Limited