аЯрЁБс>ўџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ§џџџ<ўџџџ=  !"#$%&'()*+,-./0123456789:;ўџџџўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ РFоЯжuў‘Уа Жv’У@WorkbookџџџџoOle џџџџџџџџSummaryInformation(џџџџџџџџ€ўџџџўџџџ ўџџџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџўџр…ŸђљOhЋ‘+'Гй0Px€œЈам№ќ   $ 0 <HфUBL Despatch AdviceBL  UBL Library Content SubcommitteBL  v 1.0-alpha 1.User-al46r@€Йћ”@€ ЖјѓЩС@ŒЙSД0С@JЊv’УўџеЭеœ.“—+,љЎ0ИH ЏЭй@сАСт\pUser BАaР=œЏМ=рZЯ?N*8X@"Зк1ШџArial1ШџArial1ШџArial1ШџArial1ДArial1ДArial1 Arial1ШArial1 Arial1 МArial1ШМArial"$"#,##0_);\("$"#,##0\)!"$"#,##0_);[Red]\("$"#,##0\)""$"#,##0.00_);\("$"#,##0.00\)'""$"#,##0.00_);[Red]\("$"#,##0.00\)7*2_("$"* #,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_).))_(* #,##0_);_(* \(#,##0\);_(* "-"_);_(@_)?,:_("$"* #,##0.00_);_("$"* \(#,##0.00\);_("$"* "-"??_);_(@_)6+1_(* #,##0.00_);_(* \(#,##0.00\);_(* "-"??_);_(@_)Є#,##0\ "DM";\-#,##0\ "DM"#Ѕ#,##0\ "DM";[Red]\-#,##0\ "DM"$І#,##0.00\ "DM";\-#,##0.00\ "DM")Ї$#,##0.00\ "DM";[Red]\-#,##0.00\ "DM">Ј9_-* #,##0\ "DM"_-;\-* #,##0\ "DM"_-;_-* "-"\ "DM"_-;_-@_->Љ9_-* #,##0\ _D_M_-;\-* #,##0\ _D_M_-;_-* "-"\ _D_M_-;_-@_-FЊA_-* #,##0.00\ "DM"_-;\-* #,##0.00\ "DM"_-;_-* "-"??\ "DM"_-;_-@_-FЋA_-* #,##0.00\ _D_M_-;\-* #,##0.00\ _D_M_-;_-* "-"??\ _D_M_-;_-@_-рѕџ Р рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР рѕџ єР р Р рЋѕџ јР рЉѕџ јР рЊѕџ јР рЈѕџ јР р ѕџ јР р Šр*Žр1*Žр Žр(Žр1(Žр1(Šр1*Šр1*Šр*Šр*ZŠр1 р р р  р р 1ррр1р рр р рр р1ŒрŒр р1 р Œр ŒрŒрŒр  р р р р р  р   р  р1 р  р1 р(Ž“€џ“€џ“€џ“€џ“€џ“€џ’т83fџРРРЫћЫЬџЬј˜Шџџџџџџџџ€€€€€€€€РРР€€€™™џ™3fџџЬЬџџffџ€€fЬЬЬџ€џџџџџџ€€€€€џЬџЬџџЬџЬџџ™™Ьџџ™ЬЬ™џџЬ™3fџ3ЬЬ™ЬџЬџ™џfff™–––3f3™f333™3™3f33™333\џџџ`…nDespatchAdviceŒЎ0 BuiltIn_AutoFilter___1;   ;#  ;џСС`iыZ№R№3 №П Р@@ё  їќЄЃЃUBL NameBIE Dictionary Entry NameObject Class Qualifier Object ClassProperty QualifierProperty Term Possessive(s)Property Term NounRepresentation Term QualifierRepresentation Term!Associated Object Class QualifierAssociated Object ClassBusiness Terms (Synonyms) OccurrenceBIE TypeUBL DefinitionExamplesDocumentary Namespace Prefix Analyst NotesCandidate CC IDContext: Business ProcessContext: Region (Geopolitical)Context: Official ConstraintsContext: ProductContext: Industry Context: RoleContext: Supporting RoleContext: System ConstraintEditor's Noteslengthpattern enumeration inclusive exclusivedigitsDespatch AdviceDetailsDetails:Ship Note, Packing Slip, Dispatch Advice, Consignment NoteABIE8the document that describes the content of goods shippeddaDespatch Advice Identifier Identifier1..1BBIEŠholds the unique number that identifies the Despatch Advice, typically according to the seller's system that generated the Despatch AdviceDespatch AdviceCopy Indicator0..1BBIE=Indicates whether a document is a copy (true) or not (false) Despatch AdviceGlobally Unique Identifier Identifier0..1BBIEYa computer generated unique identifier for the document, which is guaranteed to be uniqueDespatch AdviceIssueDateDate1..1BBIE-the date when the Despatch Advice was issued.Despatch AdviceDocumentStatusCode0..1BBIEHIdentifies the status of the document with regard to its original state.% Unchanged  Revision  Cancellation statDespatch AdviceDespatch Advice TypeCode0..1BBIE+Identifies the type of the Despatch Advice."Actual","Planned"datypDespatch AdviceNoteText0..1BBIEхcontains any free form text pertinent to the entire Despatch Advice or to the Despatch Advice message itself. This element may contain notes or any other similar information that is not contained explicitly in another structure. 3"Please send additional copies to accounts payable"Despatch AdviceLineItemCountQuantity0..1BBIEthe number of line itemsDespatch AdviceOrder Reference0..nASBIE5Identifies one or more Orders for the Despatch AdviceDespatch Advice Buyer Party1..1ASBIERassociates the Order with information about the buyer involved in the transaction.Despatch Advice Seller Party1..1ASBIESassociates the Order with information about the seller involved in the transaction.Despatch AdviceFreight ForwarderPartyPartyFreight ForwarderParty0..1ASBIEhassociates the despatch advice with information about the freight forwarder involved in the transaction.Despatch AdviceDelivery0..nASBIE@associates the despatch advice with a delivery (or deliveries).Despatch AdviceDelivery TermsDelivery TermsDelivery Terms0..1ASBIEsassociates the despatch advice with the terms agreed between seller and buyer with regard to the delivery of goods.Despatch Advice DespatchedTransport Handling UnitTransport Handling Unit DespatchedTransport Handling Unit0..nASBIEŸassociates the despatch advice with zero or more transport handling units (THU). The advice may be organised in this way with despatch 'lines' within each THU.Despatch AdviceActualShipmentShipmentActualShipment0..1ASBIEДassociates the despatch advice with actual shipment detail. (Note that this relationship comes into play when the transaction has moved from the order state to the delivery state.)Despatch Advice Despatch Line Despatch Line Despatch Line1..nASBIEИdespatch 'line(s)', annotated to show which transport handling units (THU) each line is within. If THUs are not used, there is just a series of despatch 'lines' with no THU annotation.ENDData Type Qualifier Data TypeџЊ  зУ{g@,ЦВ€l^J№м{экЦS?Џ›C/ ял Ÿ‹ ˆt dP }i бН ”€ ЏЭй@ А"cC  dќЉёвMbP?_*+‚€%џСџџ&L&F&C&P (&N)&R&D GMT &Tƒ„&333333г?'333333г?(š™™™™™й?)š™™™™™й?M*Canon Bubble-Jet BJC-210SPмLCя€ ъ od,,LetterDINU"4њт4NUJB8Ё" 7 ,,р?р?U} Ж }  }  } I } ’  } m  }  m  } ’ } m } $  } m } $ } $  } ’ } $ }   } m  } л  } m  } л } #m $$d@$F$„$@$Ѓ$Т$@$Т$F $Т $Т $Т $Т $Ѓ$Т$Ѓ$„$e$e$џ§ § § § § § § § § § BЁ§ BЂ§  §  §  §  §  § § § § § § § § § § § § § § § § § § !§ " § #!` d/џџўJDР DРBPBDРBP Bx'BxDespatchAdviceX „/џџџBDР DР_ BPBDР . DetailsBPDespatch Advice. Details!§ !"О !!§ !#!§ !$О !!!! §  !%!§ !&§ "'"§  (О(# !$$$$$$$!!!!!!!#%И/џџџМд ЪLРGlobally Unique  GU ,РBLРLРLР ,Р BLРLР Identifier  ID,LРText  ,РBBBPBP Bx'BxID%Р/џџџМр жLР. LРLР5LРLР LР B$ .   B BLРLР(LРLР  .  _B BLРLР LР. BPBLРBPDespatch Advice. Identifier&§ &)О &&§ &*&§ &+О &&&&& § &,§ &-§ &.О,'()(&*******&&&&&&&#%ј/џџџ CopyIndicator%/џџџ# Despatch Advice. Copy. Indicator*§ +/О ++§ +0+§ +1О +++++ § +2§ +3§ ,4О,--.................#%X/џџџGUID%d/џџџ/,Despatch Advice. Globally Unique. Identifier&§ &5§ &6§ &7&§ &8О &&&&& § &9§ &:§ &;О,'()(&*******&&&&&&&#%Р/џџџ IssueDate%д/џџџDespatch Advice. Issue. Date&§ &<&§ &=§ &>&§ &?О &&&&& § &@§ &A§ 'BО,'()(&*******&&&&&&&#%/џџџDocumentStatusCode%8/џџџ)&Despatch Advice. Document_Status. Code*§ +C+§ +D§ +E+§ +FО +++++ § +G§ +H§ ,I§ -J§ -KО(.................#%ˆ/џџџDespatchAdviceTypeCode%И/џџџ/,Despatch Advice. Despatch Advice _Type. Code&§ &L&§ &M§ &N&§ &OО &&&&& § &P§ &Q§ &R§ 'S§ -TО()(&*******&&&&&&&#%/џџџNote% /џџ џDespatch Advice. Note. Text&§ &UО &&§ &V&§ &WО &&&&& § &X§ &Y§ &Z§ '[О*()(&*******&&&&&&&# %X/џџ џLineItemCountQuantity %„/џџ џ,)Despatch Advice. LineItem_Count. Quantity &§ &\ &§ &]§ &^ &§ &_О &&&&) § )`§ )a§ 'bО, '()(&*******&&&&&&&# /и/џџ џ МT  JL Р L РBPBL РBP Bx'BxOrderReference /ј/џџ џ Мt  jLР LР_ BPBLР. L Р L Р_ BPBL РBP# Despatch Advice. Order Reference 0§ 1cО 02 2</џџ џD РOrder Reference 1 2\/џџ џD РOrder ReferenceО 220 § 0d 0§ 1e§ 3f§ 4gО, 4/3/055555550000000# /|/џџ џ  BuyerParty /”/џџ џ Despatch Advice. Buyer Party 0§ 1hО 01 2а/џџ џD Р Buyer Party 1 2ш/џџ џD Р Buyer PartyО 220 § 0i 0§ 3j§ 3k§ 6lО, 6/3/055555550000000# //џџ џ  SellerParty //џџ џ  Despatch Advice. Seller Party 0§ 1mО 01 2T/џџ џD Р Seller Party 1 2p/џџ џD Р Seller PartyО 220 § 0n 0§ 3o§ 3p§ 6qО, 6/3/055555550000000# 2Œ/џџ џ FreightForwarderParty 2И/џџџ ,)Despatch Advice. Freight Forwarder_ Party 1§ 1r§ 1s 1§ 1t 1§ 1uО 11 § 1v§ 1w 1§ 7x§ 7y§ 8zО, 8272199999991111111#2 /џџџ  Delivery2 /џџџ Despatch Advice. Delivery1§ 1{О 00/T/џџџD Р Delivery0/h/џџџD Р DeliveryО  //0 §  0| 0§ 3}§ 1~§ 8О,8272199999991111111#2|/џџџ  DeliveryTerms2˜/џџџ "Despatch Advice. Delivery Terms1§ 1€О 11§ 11§ 1‚О  111 §  1ƒ 1§ 1„§ 1…§ 8†О,8272199999991111111#2и/џџџ "DespatchedTransportHandlingUnit2 /џџџ 74Despatch Advice. Despatched_ Transport Handling Unit1§ 1‡§ 1ˆ1§ 1‰1§ 1ŠО  11 §  1‹§  1Œ 1§ 1§ 1Ž§ 8О,8272199999991111111#2„ /џџџ ActualShipment2Є /џџџ $!Despatch Advice. Actual_ Shipment1§ 1§ 1‘1§ 1’1§ 1“О  11 §  1”§  1• 1§ 1–§ 1—§ 8˜О,8272199999991111111#2ш /џџџ  DespatchLine2 /џџ§ !Despatch Advice. Despatch Line1§ 1™О 11§ 1š1§ 1›О  111 §  1œ 1§ 1§ 1ž§ 8ŸО,8272199999991111111#О$:::::;::;;;;;<=§ > О.???@A;:::::::;;;;;;;#з,K|јЪп365`j1Nf†Šn{Fƒ_DьШ№H №№0 №( № №№xЂ № “ №6€­ПXPƒPП?П №У)w№]4­РML ь №Жл<мUBL Name: These are derived from the rules of the UBL Naming and Design Rules subcommittee. The formula used here is not the definitive version. The definitive UBL Name is generated automatically when the schemas are created. This value is provided here for guidance only. If any disparity exists between the UBL Name here and those in the schemas, the schema should be considered the correct UBL Name. (NB columns with grey headings are not part of the normative schemas)<льx№xЂ № “ №6€$ВПXPƒPП?П №У)w№]4$ВNL Xь №ЖЫ<ЬBIE Dictionary Entry Name: These are built following the rules of the ebXML Core Component Technical Specification. This is the unique official name of the Business Information Entity in the dictionary. <Ыьx№xЂ № “ №6€РАПXPƒPП?П №У)w№]4РАЈNL Xь №Жи<йObject Class Qualifier: A qualifier is a word or words which help define and differentiate a Business Information Entity fromother Business Information Entities. For example, when the BIE is used in another context.<иьx№xЂ № “ №6€lЊПXPƒPП?П №У#w№]4lЊ@OL Xь №Ж < Object Class: The use of this metadata is specified by the ebXML CCTS which in turn extends the ISO 11179 naming rules. An Object Class represents the logical data grouping or aggregation (in a logical data model) to which a Property belongs. Object Classes have explicit boundaries and meaning and their Properties and behaviour follow the same rules. Each Object Class is an ABIE. We also refer to these things Re-usable Types, and they are also known as Classes (to the UML) or Tables/Entities (to database designers). < ьx№xЂ № “ №6€ЗПXPƒPП?П №Т w№]4Зє(L Xь №Ж< Property Qualifier: A qualifier is a word or words which help define and differentiate a Business Information Entity fromother Business Information Entities. Qualifiers specialise or modify the Property Term. For example, when the BIE is used in another context.<хьx№xЂ № “ №6€ИжПXPƒPП?П №Ф w№]4ИжиOL Xь №Ж~<Property Term Adjective(s). The use of this metadata is specified by the ebXML CCTS which in turn extends the ISO 11179 naming rules. Property Term represents the distinguishing characteristic or Property of the Object Class and shall occur naturally in the definition. Also known as an attribute (to database designers). The combination of Object Class and its Property Term, should give the basic semantic meaning of the item. The Property Term may consist of one or more possessive nouns preceeding the mandatory noun. This ownership creates a meaninginful refinement of the noun to make a meaningful and recognisable business name.<~ьx№xЂ № “ №6€зПXPƒPП?П №Ф w№]4зpPL Xь №Жж<зProperty Term Noun. The use of this metadata is specified by the ebXML CCTS which in turn extends the ISO 11179 naming rules. Property Term represents the distinguishing characteristic or Property of the Object Class and shall occur naturally in the definition. Also known as an attribute (to database designers). The combination of Object Class and its Property Term, should give the basic semantic meaning of the item. The Property Term must contain at least a noun. It may also have one or more adjectives preceeding the noun to make a meaningful and recognisable business name. In generating BIE dictionary entry and UBL default names, the Representation Term may be dropped if the Noun and RT are effectively identical.<жьx№xЂ № “ №6€lзПXPƒPП?П №М єw№]4lзQL Xь №ЖР<СA qualifier is a word or words which help define and differentiate a Business Information Entity fromother Business Information Entities. For example, when the BIE is used in another context.<Рьx№xЂ №  “ №6€азПXPƒPП?П № М &w№]4 аз QL Xь №Жя<№Representation Term: The use of this metadata is specified by the ebXML CCTS which in turn extends the ISO 11179 naming rules. A Representation Term is an element of the name which describes the form in which the property is represented. <яьx№xЂ №  “ №6€4иПXPƒPП?П №•Чw№]4 4и8RL Xь №Жч<шAssociated Object Class Qualifier: A qualifier is a word or words which help define and differentiate a Business Information Entity fromother Business Information Entities. For example, when the BIE is used in another context. Associated Object Class Qualifiers describe the 'context' of the relationship with another ABIE. That is, it is the role this Object Class plays within its association with another Object Class. In such cases, they then duplicate the Property Class Qualifier.<чьx№xЂ №  “ №6€˜иПXPƒPП?П №}(w№]4 ˜иаRL Xь №Ж˜<™Associated Object Class: Associated Object Class is the Object Class at the other end of this association. It will refer to another ABIE in this model.<˜ьx№xЂ №  “ №6€ќиПXPƒPП?П №(w№]4 ќиhSL Xь №Ж]<^Business Term: (Optional). This is a synonym term under which the Business Information Entity is commonly known and used in the business for a specific Context. A Business Information Entity may have several Business Terms or synonyms. These may be used to 'map' BIEs to a controlled vocabulary, other vocabularies or labels for forms presentation.<]ьx№xЂ №  “ №6€`йПXPƒPП?П №$щw№]4 `йTL Xь №ЖZ<[Occurrence: The optionality and/or cardinality of the BIE. Expressed in XML Schema syntax.<Zьx№xЂ № “ №6€ФйПXPƒPП?П №›w№]4Фй˜TL Xь №Жъ<еBIE Type: There are three choices here: Basic (BBIE  white rows), Associate(ASBIE- green rows) or Aggregate BIE (ABIE -pink rows). This column is used to automatically generate the XSD schemas. (the program cannot read colours!)<ъьx№xЂ № “ №6€(кПXPƒPП?П №ў‡w№]4(к0UL Xь №Жb<cUBL Definition: This is the unique semantic business meaning of that Business Information Entity. <bьx№xЂ № “ №6€ŒкПXPƒPП?П №Сюw№]4ŒкШUL Xь №Ж‚<ƒDocumentary Namespace Prefix: This contains reference information suitable for the integration of the NDR Code Lists architecture.<‚ьx№xЂ № “ №6€№кПXPƒPП?П №хђw№]4№к`VL Xь №Ж~<Analyst Notes: This is a list of comments, queries and notes made as the work is done. It is not part of the normative schemas<~ьx№xЂ № “ №6€TлПXPƒPП?П №ФJw№]4TлјVL Xь №ЖЙ<КCore Component UID: This is the UID of the correlated core component, in those cases where a direct correlation exists. This information is found in the current Core Component Catalog.<Йьx№xЂ № “ №6€ИлПXPƒPП?П №Уj)С№]4ИлWL Xь №Ж’<“Line colour: This colour denotes an ABIE - Aggregate Business Information Entity - line. This is also denoted by "ABIE" in the "BIE Type" column.<’ьx№xЂ № “ №6€мПXPƒPП?П №У f) С№]4м(XL Xь №Ж–<—Line colour: This colour denotes an ASBIE - Associated Business Information Entity - line. This is also denoted by "ASBIE" in the "BIE Type" column. <–TMTMTMTMTMTMTMTM TM TM TM TM TMTMTM TTMTMTM TM>Ж@d   я7 DocumentSummaryInformation8џџџџџџџџџџџџшCompObjџџџџџџџџџџџџ fџџџџџџџџџџџџџџџџџџџџџџџџP X`hp x “ф  DespatchAdvice  Worksheetsўџ џџџџ РFMicrosoft Excel WorksheetBiff8Excel.Sheet.8є9Вq