1 / 39

DISCOVER AND USE EDIFACT

DISCOVER AND USE EDIFACT. UNIVERSAL AND STANDARDIZED EDIFACT LANGUAGE. EDIFACT : ISO, CEN & AFNOR STANDARD. Electronic. ISO 9735 = "GRAMMAR". Data. (SYNTAX RULES, ETC.). ISO 7372 = "VOCABULARY". Interchange. (DATA DICTIONNARIES, MESSAGES SEGMENTS,. ETC.). For. ISO 6422 = LAYOUT KEY.

nitza
Download Presentation

DISCOVER AND USE EDIFACT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DISCOVER AND USE EDIFACT

  2. UNIVERSAL AND STANDARDIZED EDIFACT LANGUAGE EDIFACT : ISO, CEN & AFNOR STANDARD Electronic ISO 9735 = "GRAMMAR" Data (SYNTAX RULES, ETC.) ISO 7372 = "VOCABULARY" Interchange (DATA DICTIONNARIES, MESSAGES SEGMENTS, ETC.) For ISO 6422 = LAYOUT KEY Administration PRINTING STANDARDIZED FORMAT OF SALES DOCUMENTS Commerce & Transport ISO: International Standard Organisation CEN: European Committee of Standardization

  3. EDIFACT language: • EDIFACT • Language of standard messages description for inter-companies exchanges. • Consists of: • Vocabulary • Grammar rules • A basis of messages classic example

  4. EDIFACT language: • Vocabulary : • UNTDED : The United Nations Trade Data Elements Directory ISO 7372. Directory of sales data elements which consists of: • Messages • Segments • Composites • Data elements • Codes list • Grammar rules: • EDIFACT Message Design Guidelines • UNTDID : The United Nations Trade Data Interchange Directory • ISO 9735 UN/EDIFACT Syntax rules

  5. Interchange S é m a n t i c S y n t a x E d i f a c t Messages Segments Composites data Elementary data Splitter Files structure Directory of sales data elements ISO 7372 ISO 646-83 Characters set Communication layer: OSI EDIFACT language: the elements of language

  6. EDIFACT language: the lements of language • Elementary data • EDE (Electronic Data Element Directory) • Composites data • EDCD (Electronic Data Composite Directory) • Segments • EDSD (Electronic Data Segment Directory) • Codes • EDCL (Electronic Data Code List) • Messages • EDMD (Electronic Data Message Directory) • Syntax rules • ISO 9735 • Rules of conduct • UNCID (Uniform rules of Conduct for Interchange of trade Data by teletransmission) • Message conception guide • Syntax use guide

  7. Making out Exchange End UNA UNB Functionnal group Messages UNZ UNG Message Messages UNE UNH Segment Segment Segment UNT TAG Composite date + Segment ‘ EDIFACT language: syntax Value Data : Data Value Value

  8. EDIFACT languageservice segments UNA: interchange characteristics (optional) UNB: beginning of interchange UNE: end of functionnal group (optional) UNH: beginning of message UNS: Splitter of message main parts (optional) UNT: End of functional group UNZ: End of interchange

  9. EDIFACT languageservice segments Interchange (UNA) UNB Functionnal group (UNG) UNH Message Fin du message UNT Fin de groupe fonctionnel (UNE) Fin d’interchange UNZ

  10. EDIFACT languageservice segments Interchange(UNA) UNB Functionnal group (UNG) UNH message User data segment(s) (Header).xxx yyy Section (UNS) User data segment (s).(detail). zzz www Section (UNS) User data segment (s).(résumé). vvvuuu Fin du message UNT Fin de groupe fonctionnel (UNE) Fin d’interchange UNZ

  11. EDIFACT languageBasis rules • Unity of location • Data are grouped together on the creator’s initiative. • Users are always at the root of the messages elaboration • Unity of time • Data are grouped together as far as they can be: • Generated • Stored • Transmitted… at the same time • Unité of action • Information concerning a same task or a same action is grouped together. • Intereactions between messages • Traceability of messages between them

  12. EDIFACT languageConception rules • DATA COMPONENTS • Using existing data components rather than creating new ones • Name and format assignment to a data component must respect rules of presentation of the EDICFACT/ONU data components directory: • Qualifier name must be preceded by the « …qualifier » term: currency qualifier • Qualifiers format is « an..3 » • The codes list for the qualifier must be specified in the EDCL. • The coded component name must be followed by « coded »: currency, coded • Other date components name must end with « Identification »: Risk code identification • Plainly data components must get these formats: an..17, an..35, an..70. They must be named according to the profession needs.

  13. EDIFACT languageConception rules • Data components • There are 2 types of coded date • a components: • Data components with a qualifier function • Generic date components. They are, in this case, associated to 1131/3055 conditional components in the composite data.

  14. EDIFACT languageConception rules • Composite data • Grouping of several data components, in a structured form of information linked to a same concept: the unity of function • Before creating new composite data, it is advisable to check if similar or close structures exist. • It’s possible to ask for adaptations for close structures. In that case additional components are added at the end of the composite data. • A new composite data component must be conceived in a way that allow as many applications as possible. • If a composite data has to be qualified, the qualifier must be placed right after the component.

  15. EDIFACT languageConception rules • Composite data • Mandatory constituent components of a composite data must be placed in the header. • The number of repetitions of a constituent component can’t be more than 5. • A component whose format is «  an..70 » can’t be repeted, or a FTX segment has to be used.

  16. EDIFACT languageConception rules • Segments • To conceive a message, already existing segments has to be used if possible. It speeds up the conception process. • If a segment has to be modified, additional components are to be added at the end of the segment. • If a new component has to be conceived, it has to be done in a generic way as much as possible. • Mandatory data of a segment must appear before conditional data. • If a segment has to be qualified, the qualifier must be placed first in data components. • Simple or composite data components can’t be repeated within the segment. The segment is the one that has to be repeated. If this repetition is however necessary, it can’t be done more than five times.

  17. EDIFACT languageConception rules • Messages • Messages must be conceived in order to be used at an international level. • A unique identifier of 6 letters has to be allocated to the message. • Messages are composed of a group of segments. The latter must begin with a non repetitive mandatory segment. • Group of segments can be interlinked. In that case, it’s not possible to get in an lower group of segments without having entered in the one right before it. • If identical segments are used at several places in the message, it’s advised to avoid collision by inserting madatory segments of different nature. • A message must begin with UNH and end with UNT. • The UNS service segment must be used to avoid collision between « header », « detail » and « recapitulation » segments.

  18. UNH BGM DTM UNT M 1 M 1 M 2 M 1 Address Segments Group EDIFACT languageExample of message structure

  19. UNH BGM DTM UNT M 1 M 1 M 2 M 1 SG1 M 3 NAD M 1 Segments CTA COM Group of segments C C 4 1 Le langage EDIFACTConnectiondiagram

  20. SG4 FFF DDD SG6 C 9 C 9 C 1 C 9 CCC GGG M 1 M 1 Risk of collision SG5 C 9 HHH DDD C 1 M 1 EDIFACT languageRules of conception: Collision !

  21. Code Name Status Dir Status Dir UNH Message header M 1 BGM Beginning of message M 1 DTM Date/Time/Period M 2 Group 001 M 3 NAD Name and address M 1 CAT Contact Information C 1 COM Communication Contact C 4 UNT End of message M 1 EDIFACT languageSegments table M=Mandatory C= Conditionnal

  22. Code Name Status Dir Status Dir UNH Message header M 1 BGM Beginning of message M 1 DTM Date/Time/Period M 2 Group 001 M 3 NAD Name and address M 1 CAT Contact Information C 1 COM Communication Contact C 4 UNT End of message M 1 EDIFACT languageSegments table • This group of segments is: • Mandatory • Iterable 3 times

  23. Code Name Status Dir Status Dir UNH Message header M 1 BGM Beginning of message M 1 DTM Date/Time/Period M 2 Group 001 M 3 NAD Name and address M 1 CAT Contact Information C 1 COM Communication Contact C 4 UNT End of message M 1 EDIFACT languageSegments table The address is: - Mandatory - Repeatable once

  24. Code Name Status Dir Status Dir UNH Message header M 1 BGM Beginning of message M 1 DTM Date/Time/Period M 2 Group 001 M 3 NAD Name and address M 1 CAT Contact Information C 1 COM Communication Contact C 4 UNT End of message M 1 EDIFACT languageSegments table If the COM segment is used, it is repeated at least once and up to four times.

  25. Code Name Status Dir Status Dir UNH Message header M 1 BGM Beginning of message M 1 DTM Date/Time/Period M 2 Group 001 M 3 NAD Name and address M 1 GROUP NAD CAT Contact Information C 1 COM Communication Contact C 4 UNT End of message M 1 EDIFACT languageSegments table

  26. 3035 3164 City name Party qualifier C M an..35 an..3 C082 3229 Party identification details Country sub-entity identification C C an..9 3251 C058 Name and address Post-code C an..9 C C080 3207 Country, coded Party name C C an..3 C059 Street C EDIFACT languageNAD Segment Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru 3207

  27. 3035 3164 Party qualifier City name C M an..35 an..3 C082 3229 Country sub-entity identification Party identification details C C an..9 3251 C058 Post-code Name and address C an..9 C C080 3207 Party name Country, coded C C an..3 C059 Street C EDIFACT languageNAD Segment Elementary data Composite data Function : To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru 3207

  28. 3035 3164 Party qualifier City name C M an..35 an..3 C082 3229 Country sub-entity identification Party identification details C C an..9 3251 C058 Post-code Name and address C an..9 C C080 3207 Party name Country, coded C C an..3 C059 Street C EDIFACT languageNAD Segment Mandatory or optional data character Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru 3207

  29. 3164 3035 City name Party qualifier C M an..35 an..3 3229 C082 Country sub-entity identification Party identification details C C an..9 3251 C058 Name and address Post-code C an..9 C 3207 C080 Country, coded Party name C an..3 C C059 Street C EDIFACT languageNAD Segment Data structure Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru 3207

  30. 3164 3035 City name Party qualifier C M an..35 an..3 3229 C082 Country sub-entity identification Party identification details C C an..9 3251 C058 Name and address Post-code C an..9 C 3207 C080 Country, coded Party name C C an..3 C059 Street C EDIFACT languageNAD Segment Data structure Number of characters Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru 3207

  31. 3164 3035 City name Party qualifier C M an..35 an..3 3229 C082 Country sub-entity identification Party identification details C C an..9 3251 C058 Name and address Post-code C an..9 C 3207 C080 Country, coded Party name C an..3 C C059 Street C 3035 C082 C058 EDIFACT languageNAD Segment Function: To specify the name/address and their related function, either by CO82 only and/or unstructured by CO58 or structured by CO80 thru 3207

  32. C082 Party identification C 3039 Party id. identification M an..35 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 EDIFACT languageComposite component Details of a composite data = C082 data = party identification

  33. C082 Party identification C 3039 Party id. identification M an..35 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 EDIFACT languageComposite component Data reference number Coded data can only take its values in the standard codes list. Details of a composite data = C082 data = party identification

  34. C082 Party identification C 3039 Party id. identification M an..35 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 EDIFACT language Composite component Representation a = alphabetical n = numerical an = alphanumerical .. = variable lenght 3 = maximum number of characters Status O= Obligatoire = M = Mandatory Details of a composite data = C082 data = party identification

  35. C082 Party identification C 3039 Party id. identification M an..35 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 1131 3055 EDIFACT languageComposite component Details of a composite data = C082 data = party identification

  36. EDIFACT languageCodes • Use of 1131 and 3055 codes • Theses codes allow indicating dynamically a codification. • In case of a third party, the latter can be identified by a code that is not defined in the standard. • The agency which is identified in the 3055 code is in the standard. • Example: SIRECT code use • Data use is done this way: • Party SIRET number • 100 code means SIRET code for the INSEE • 3055: 107 is the INSEE code as maintenance agency of SIRET code • 1131 and 3055 codes allow using all existing codifications.

  37. ORDERS –PHYTOS MESSAGE

  38. Message construction:Message aim The Order (ORDERS) is sent by the client to the supplier to order one or several items and to specify quantities and date and place of delivery. Each order corresponds to one supplier and one client. It concerns n products, which give rise to x deliveries and x invoices.

  39. Message constructionORDERS • Adaptation of the message to the needs • Segments choice • Iterations restrictions • Adaptation of codes lists to managed concepts • Differentiation between group of segments and segments

More Related