cancel
Showing results for 
Search instead for 
Did you mean: 

Please help me in understanding the EDIFACT D96A format for INVOICE

Former Member
0 Kudos
2,331

Hi,

Im doing an INVOICE02 IDOC to EDIFACT D96A INVOIC scenario. Im new to EDI.

Pls Pls Pls Pls

kindly help me in understanding the following EDIFACT D96A file.

UNBUNOA:35410033000055:145400110000009:14070612:085511137INV96A+EANCOM1'

UNH1INVOIC:D:96A:UN:EAN008'

BGM3805010237529+9'

DTM+137:200706120000:203'

DTM+35:20070612:102'

DTM+454:20070612:102'

RFF+ON:32210'

DTM+171:20070612:102'

RFF+DQ:000030585715'

DTM+171:20070612:102'

NADSU5410148000001::9+BVBA Unilever Belgium SPRLBl.De L?'Humanité 292 292Bruxelles1190BE'

RFF+VA:BE438390312'

RFF+ARA:0438390312'

NADBY5400110000009::9+D.L.L.RUE OSSEGHEM 53-MOLENBEEKMOLENBEEK-SAINT-JEAN1080BE'

NADDP5400110000009::9+D.L.L.RUE OSSEGHEM 53-MOLENBEEKMOLENBEEK-SAINT-JEAN1080BE'

NADIV5400110000009::9+DELHAIZE FRS. CENTRALESRUE OSSEGHEM , 53BRUSSEL-MOLENBEEK1080BE'

RFF+VA:BE402206045'

RFF+ARA:0402206045'

CUX+2:EUR:4'

LIN10+8000920900987:EN'

PIA1000000000019009801:SA'

IMDF+IN:::IGLO POELEE LEGUMES CHAMPIGNONS 6X8'

QTY+47:81'

QTY+46:81'

MOA+203:1584.4'

PRI+AAA:19.56'

PRI+AAB:21.24'

TAX7VAT+++:::6.000'

MOA+125:1584.4'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN20+5410148126459:EN'

PIA1000000000011264501:SA'

IMDF+IN:::Epinards hachis en portions '

QTY+47:112'

QTY+46:112'

MOA+203:1061.01'

PRI+AAA:9.47'

PRI+AAB:10.96'

TAX7VAT+++:::6.000'

MOA+125:1061.01'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN40+5410148013452:EN'

PIA1000000000010134500:SA'

IMDF+IN:::15 Fish Sticks Colin d?'Alaska '

QTY+47:256'

QTY+46:256'

MOA+203:4937.63'

PRI+AAA:19.29'

PRI+AAB:20.16'

TAX7VAT+++:::6.000'

MOA+125:4937.63'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

LIN50+5414807999958:EN'

PIA1000000000019999501:SA'

IMDF+IN:::Iglo Poisson Pané Epinards 7X400g'

QTY+47:180'

QTY+46:180'

MOA+203:4160.31'

PRI+AAA:23.11'

PRI+AAB:24.08'

TAX7VAT+++:::6.000'

MOA+125:4160.31'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

LIN60+5410148120952:EN'

PIA1000000000011209501:SA'

IMDF+IN:::Epinards Crhme en Portions '

QTY+47:112'

QTY+46:112'

MOA+203:1594.69'

PRI+AAA:14.24'

PRI+AAB:15.92'

TAX7VAT+++:::6.000'

MOA+125:1594.69'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN70+5410148124158:EN'

PIA1000000000011241503:SA'

IMDF+IN:::EPINARDS HACHES EN PORTIONS 450G'

QTY+47:144'

QTY+46:144'

MOA+203:938.01'

PRI+AAA:6.51'

PRI+AAB:7.44'

TAX7VAT+++:::6.000'

MOA+125:938.01'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN120+5410148016729:EN'

PIA1000000000010167201:SA'

IMDF+IN:::Macaroni Fromage/Jambon '

QTY+47:260'

QTY+46:260'

MOA+203:4337.55'

PRI+AAA:16.68'

PRI+AAB:17.58'

TAX7VAT+++:::6.000'

MOA+125:4337.55'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

LIN130+5410148441255:EN'

PIA1000000000014412503:SA'

IMDF+IN:::CHOUX ROUGES AUX POMMES 450G'

QTY+47:144'

QTY+46:144'

MOA+203:1756.99'

PRI+AAA:12.2'

PRI+AAB:13.36'

TAX7VAT+++:::6.000'

MOA+125:1756.99'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN140+5410148017702:EN'

PIA1000000000010177001:SA'

IMDF+IN:::Frit?'Kot 1'

QTY+47:60'

QTY+46:60'

MOA+203:1102.6'

PRI+AAA:18.38'

PRI+AAB:22'

TAX7VAT+++:::6.000'

MOA+125:1102.6'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:4.9:1'

LIN180+8000920801796:EN'

PIA1000000000018017901:SA'

IMDF+IN:::EPINARDS EN BRANCHES 10 X 450'

QTY+47:190'

QTY+46:190'

MOA+203:2204.2'

PRI+AAA:11.6'

PRI+AAB:12.9'

TAX7VAT+++:::6.000'

MOA+125:2204.2'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN200+5410148014268:EN'

PIA1000000000010142602:SA'

IMDF+IN:::PETITS POIS EXTRA FINS 450G'

QTY+47:238'

QTY+46:238'

MOA+203:1999.6'

PRI+AAA:8.4'

PRI+AAB:9.24'

TAX7VAT+++:::6.000'

MOA+125:1999.6'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

ALCA++1'

PCD+1:1.96:1'

LIN230+8000920807248:EN'

PIA1000000000018072403:SA'

IMDF+IN:::IGLO POUL ET PENNE AUX LEG.SOLEI. 6'

QTY+47:99'

QTY+46:99'

MOA+203:1727.54'

PRI+AAA:17.45'

PRI+AAB:18.3'

TAX7VAT+++:::6.000'

MOA+125:1727.54'

ALCA++1'

PCD+1:0:1'

ALCA++1'

PCD+1:1.97:1'

UNS+S'

CNT+2:12'

MOA+124:1644.27'

MOA+86:29048.8'

MOA+79:27404.53'

MOA+125:27404.53'

TAX7VAT++:::6.000S'

MOA+125:27404.50'

MOA+124:1644.27'

UNT2121'

UNZ111137'

Advance appreciations,

Ram.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Its very simple:

UNB-segment : Interchange Header

S001 SYNTAX IDENTIFIER

0001 Syntax Identifier “UNOA”

0002 Syntax version number “2”

S002 INTERCHANGE RECIPIENT

0004 Sender Identification “8711382000091” (= GLN Code Tilburg)

0007 Identification Code Qualifier “14”

S003 INTERCHANGE SENDER

0004 Recipient Identification “8711700400008”(= GLN Code Unilever)

0007 Identification Code Qualifier “14”

S004 DATE/TIME OF PREPARATION

0017 Date YYMMDD

0019 Time HHMM

0020 INTERCHANGE CTRL REF. Unique message reference number

0026 APPLICATION REFERENCE “WMS0330”

UNH-segment: Message header

0062 MESSAGE REFERENCE NUMBER Unique sequence numbe within UNB

S009 MESSAGE IDENTIFIER

0065 Message type identifier “INVRPT”

0052 Message type version number “D”

0054 Message type release number “96A”

0051 Controlling agency “EN”

0057 Association assigned code “EAN004”

BGM-segment: Beginning of message

C002 DOCUMENT/MESSAGE NAME

1001 Document/message name, coded 35” (= Inventory report)

3055 Code list responsible agency, coded “9” (= EAN)

1004 DOCUMENT/MESSAGE NUMBER Unique Number assigned by CS (= Date/Time CCYYMMDDHHMMSS)

1225 MESSAGE FUNCTION, CODED “9” (= Original)

DTM-segment: Date/time/period

C507 DATE/TIME/PERIOD

2005 Date/time/period qualifier 137” (=Document/message date/time)

2380 Date/time/period Document date

2379 Date/time/period format qualifier “102” (= CCYYMMDD)

RFF-segment: Reference

C506 REFERENCE

1153 Reference code qualifier “ON” (= Order number)

1154 Reference identifier Agreement number

NAD-segment: Name and address

3035 PARTY QUALIFIER “GY” (= Inventory reporting party = CS)

“GM” (= Inventory controller = XYZ)

C082 PARTY IDENTIFICATION DETAILS

3039 Party id. identification GLN code

3055 Code list responsible agency, coded “9” (= EAN)

LIN-segment: Line item

1082 LINE ITEM NUMBER Unique Line Number

C212 ITEM NUMBER IDENTIFICATION

7140 Item number EAN Material code

7143 Item number type, coded “EN” (= EAN)

PIA-segment: Additional Product Information

4347 PRODUCT ID FUNCTION IDENTIFIER "1"(= Additional Information)

C212 ITEM NUMBER IDENTIFICATION

7140 Item number Promotional Variant

7143 Item number type, coded "PV” (= Promotional variant)

QTY-segment: Quantity

C186 QUANTITY DETAILS

6063 Quantity qualifier “12” (= Despatch quantity)

6060 Quantity Number of stock units

PRI: Represent price

TAX: represent tax.

Try to go to the below website where you will able to get the information regarding all the sgements and elements of Invocie.

http://www.edifactory.de/messages.php?s=D96A

Also refer the below link for EDI understanding:

http://www.gxs.com/pdfs/Tutorial/Tutor_EDIFACT_GXS.pdf

Thnx

Chirag Gohil

Former Member
0 Kudos

Hi Chirag,

Thanks alot for ur quick response.Its really helpful.

I have a doubt here.

Could u pls explain what are S001,0001,0002,S002 etc in the UNB segment and how r they related to my given EDIFACT message.

Please try explain me in comparison with my EDIFACT output file.

Thanks in adavance.

Former Member
0 Kudos

Hi,

Its a payload information like we have in IDOC control record. It holds the sender and receiver information along with the date and time when it is created and the version of the message and which std it follows.

UNBUNOA:35410033000055:145400110000009:14070612:085511137INV96A+EANCOM1'

In the above ex:

INV96A is the message

EANCOM is the std used it is similar to EDIFACT UN std.

Do let me know if you need more info.

Thnx

Chirag Gohil

Former Member
0 Kudos

Hi Chirag,

Thanks for response.

In my mapping sheet there are totally six columns for the terget side.

They are:

Structure, Field, Segment qualifier, element qualifier, Lenght and type.

What are these segment and element qualifiers.

They have given one value each for all segm qual and also for few elem qual.

Could u pls locate them in my output edifact file?

thanks in advance.

Former Member
0 Kudos

Hi,

Segment qualifier is represented by + sign and element qualifier is represented by : sign.

Take a below example:

UNB-segment : Interchange Header

S001 SYNTAX IDENTIFIER

0001 Syntax Identifier

0002 Syntax version number

S002 INTERCHANGE RECIPIENT

0004 Sender Identification

“8711382000091”

In the above example S001 is the segment and 0001 and 0002 is the element of that segment. Similarly S002 is the segment and 0004 is the element of that segment.

Now in EDI how this will be represented.

UNB123:12'

Now UNB represent the interchange header segment. NOw + represented the start of segment S001 and 123 represented the systex identifier and it will be seperated by :. now for the next segment S0002 it will again start with + and the element will be separated by :.

' represented the end of the message header.

Length and type that defines the whether how many length it has and type defines whether it is string, integer etc.

So this infor will help you in mapping the source and target strucutre in XI.

Thanks and Regards,

Chirag Gohil

Former Member
0 Kudos

Hi,

In EDIFACT four service characters (extracted from UNOA) have a special meaning and act as the default separators for EDIFACT

Apostrophe ' = segment terminator

Plus sign + = segment tag and data element separator

Colon : = component data element separator

Question Mark ? =release character; immediately preceding one of the service characters, it restores their normal meaning.

E.g. 10?10=20 means 1010=20. Question mark is represented by ??

DTM+137:200706120000:203' means..

DTM = Tag of the "Date/Time Period" segment;

+ = separator;

137 = Qualifier to indicate the date is the Document/Message Date/Time;

: = separator of data elements within a composite (here, the date qualifier and the date);

20070612 = the date;

0000 = the time;

: = separator of data elements within a composite (here, the date and the date format qualifier);

203 = Qualifier to indicate the format of the date (12th June 2007 at 00:00);

' = Segment terminator.

Hope this info will help u to locate ur segment and element qualifiers.

Regards,

Anoop

Former Member
0 Kudos

Hi Anoop,

Thanks alot for ur reply.Its really helpful.

Can u please more clear about the '?' symbol?

Also in my sample file I find '+' and '++'. Pls explain these if u have any idea.

Thanks again.

Former Member
0 Kudos

Hi,

A segment consists of:

1.A segment tag: identifies the segment type

2.Data element separators

3.Simple, composite, or component data elements

4.A segment terminator

Data elements can be defined as having a fixed or variable length.

A composite data element contains two or more component data elements.

A component data element is a simple data element used in a composite data element.

Now,for say m assuming

TAG = segment tag; DE = data element; CE = component data element.

Now there are many cases for understanding them:-

1.Exclusion of data elements by omission - Data elements are identified by their sequential position within the segments. If a conditional data element is omitted and followed by another data element, its position shall be indicated by retention of its data element separator.

Eg: TAGDEDEDECE:CE:CE' complete segment including all data elements

TAGDEDECE:CE:CE' - so one DE has been omitted in between,but it's '+' seperator has been still kept.

2.Exclusion of data elements by truncation - If one or more conditional data elements at the end of a segment are omitted, the segment may be truncated by the segment terminator.

Eg: TAGDEDEDEDE' Original including all data elements

TAGDEDE' - truncation.So,no need to keep seperator here as removed from end.

3.Exclusion of component data elements by omission - If a conditional CE is omitted and followed by another CE, its given position must be represented by its CE separator.

Eg: TAGDEDECE:CE:CE' Original including all CE's

TAGDEDECE::CE' - One CE has been omitted but it's seperator ':' has been kept as CE is removed in between.

4.Exclusion of component data elements by truncation - One or more conditional CE at the end of a composite DE may be excluded by truncation by the DE separator or, if at the end of a segment, by the segment separator.

Eg: TAGDEDECE:CE:CE' Original including last CE

TAGDEDECE:CE' - Here it's CE truncation as it's removed from end.So no keeping of seperator ':' this time.

Hope this info will help u understand those symbols in ur sample file.

Regards,

Anoop

Former Member
0 Kudos

Hi chirag,

Could u please explain me the following segment of my output file.

NADSU5410148000001::9+BVBA Unilever Belgium SPRLBl.De L?'Humanité 292 292Bruxelles1190BE'.

Please compare the above with the NAD segment structure that u gave.

Thanks in Advance

Former Member
0 Kudos

Hi Chirag,

Can u pls give me ur personnel or official mail id so that i can I can send u my sample file and mapping sheet n discuss with u regarding the same in details?

Thanks in advance,

Ram,

9902069880.

Former Member
0 Kudos

HI,

This is not possible as this forum can help others in future. You can explain me your doubts I will try to revert back to you through forum only.

Please go through the edifactory link and compare the NAD segment with your data you will understand each and everything very ealisy.

Thnx

Chirag Gohil.

Answers (0)