ࡱ> :;  !"#$%&'()*+,-./0123456789Root Entry F82uR@Workbook*jOle SummaryInformation( Oh+'0Px   $ 0 <HUBL Receipt Advice.BL  UBL Library Content SubcommitteBL  v 1.0-alpha 1.User-al38r@.œ@ @S0@"l՜.+,0H @\pUser Ba==Z?N*8X@"1Arial1Arial1Arial1Arial1Arial1Arial1Arial1Arial1Arial1Arial1Arial"$"#,##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_-;_-@_-FA_-* #,##0.00\ "DM"_-;\-* #,##0.00\ "DM"_-;_-* "-"??\ "DM"_-;_-@_-FA_-* #,##0.00\ _D_M_-;\-* #,##0.00\ _D_M_-;_-* "-"??\ _D_M_-;_-@_-                      *1* (1(1(1*1***Z1       1 1   1       1         1   1 (83f3ffff̙̙3f3fff3f3f33333f33333\` ReceiptAdvice0 BuiltIn_AutoFilter___1;   ;#  ;`iZR3  @@  [ 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 exclusivedigitsReceipt AdviceDetailsDetailsABIEFthe document that advises the goods received and accepted by the buyerraReceipt Advice Identifier Identifier1..1BBIEholds the unique number that identifies the receipt advice, typically according to the buyer's system that generated the receipt adviceReceipt AdviceCopy Indicator0..1BBIE=Indicates whether a document is a copy (true) or not (false) Receipt AdviceGlobally Unique Identifier Identifier0..1BBIEYa computer generated unique identifier for the document, which is guaranteed to be uniqueReceipt AdviceIssueDateDate1..1BBIE,the date when the receipt advice was issued.Receipt AdviceDocumentStatusCode0..1BBIEHIdentifies the status of the document with regard to its original state.% Unchanged  Revision  Cancellation statReceipt AdviceNoteText0..1BBIEnotes or any other textual information, pertinent to the entire receipt advice, that is not contained explicitly in another structure. Receipt AdviceOrder Reference0..nASBIEIassociates the receipt advice with one or more Orders that it relates to.Receipt AdviceDespatchDespatchDocument Reference0..nASBIESassociates the receipt advice with one or more Despatch advices that it relates to.Receipt Advice Buyer Party1..1ASBIERassociates the Order with information about the buyer involved in the transaction.Receipt Advice Seller Party1..1ASBIESassociates the Order with information about the seller involved in the transaction.Receipt AdviceFreight ForwarderFreight ForwarderParty0..1ASBIEgassociates the receipt advice with information about the freight forwarder involved in the transaction.Receipt AdviceDelivery0..nASBIE?associates the receipt advice with a delivery (or deliveries).Receipt AdviceReceivedReceivedTransport Handling Unit0..nASBIEassociates the receipt advice with zero or more transport handling units (THU). The advice may be organised in this way with receipt 'lines' within each THU.Receipt Advice Receipt Line1..nASBIEreceipt '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 receipt 'lines' with no THU annotation.ENDData Type Qualifier Data Type bg',<AFKQVDI   8= @ "<  dMbP?_*+%&L&F&C&P (&N)&R&D GMT &T&333333?'333333?(?)?M*Canon Bubble-Jet BJC-210SPLC od,,LetterDINU"44NUJB8" 7 ,,??U}  }  }  } I }   } m  }  m  }  }  } $  } m } $ } $  }  } $ }   } m  }   }   } m  }  } #m $$(@$$$@$$$@$$ $ $ $ $ $$$e$          A A                       ! " #!` KJD DBPBDBP Bx'Bx ReceiptAdviceX KBD D_ BPBD . DetailsBPReceipt Advice. Details! !" !! !#! !$ !!!!!! !% "&"  '(# !$$$$$$$!!!!!!!#%KLGlobally Unique  GU ,BLLL , BLL Identifier  ID,LText  ,BBBPBP Bx'BxID%KL. LL5LL L B$ .   B BLL(LL  .  _B BLL L. BPBLBPReceipt Advice. Identifier& &( && &)& &* &&&&& &+ &, &-,'()*&+++++++&&&&&&&#%K CopyIndicator%8K"Receipt Advice. Copy. Indicator+ ,. ,, ,/, ,0 ,,,,, ,1 ,2 -3,((.................#%xKGUID%K.+Receipt Advice. Globally Unique. Identifier& &4 &5 &6& &7 &&&&& &8 &9 &:,'*)*&+++++++&&&&&&&#%K IssueDate%KReceipt Advice. Issue. Date& &;& &< &=& &> &&&&& &? &@ 'A,'*)*&+++++++&&&&&&&#%(KDocumentStatusCode%PK(%Receipt Advice. Document_Status. Code+ ,B, ,C ,D, ,E ,,,,, ,F ,G -H (I (J(.................#%KNote%KReceipt Advice. Note. Text& &K && &L& &M &&&&& &N &O &P,'*)*&+++++++&&&&&&&#/KTJL  L BPBL BP Bx'BxOrderReference/KtjL L_ BPBL. L  L _ BPBL BP"Receipt Advice. Order Reference0 0Q 00/@KLOrder Reference0/`K LOrder Reference  //0  1R 0 0S 0T 2U,2/3/044444440000000# /K DespatchDocumentReference /K /,Receipt Advice. Despatch_ Document Reference 0 0V 0W 0 /K Document Reference 0 /8K Document Reference // 0X 1Y 0 0Z 0[ 2\, 2/3/044444440000000# /`K  BuyerParty /xK Receipt Advice. Buyer Party 0 0] 10 /K  Buyer Party 0 /K  Buyer Party //1 1^ 1 5_ 5` 6a, 2/3/044444440000000# 7K  SellerParty 7K Receipt Advice. Seller Party 1 0b 10 /4K  Seller Party 0 /PK  Seller Party //1 1c 1 5d 5e 6f, 6757188888881111111# /lK FreightForwarderParty /K +(Receipt Advice. Freight Forwarder_ Party 0 0g 0h 0 /K Party 0 /K Party // 0i 0j 0 3k 3l 2m, 2/3/044444440000000# /K  Delivery /K Receipt Advice. Delivery 0 0n 11 7LK  Delivery 1 7`K Delivery 771 1o 1 5p 0q 2r, 2/3/044444440000000#/tK ReceivedTransportHandlingUnit/K41Receipt Advice. Received_ Transport Handling Unit0 0s 0t0/ KTransport Handling Unit0/D KTransport Handling Unit  //  0u  0v 0 0w 0x 2y,2/3/044444440000000#/t K ReceiptLine/ KReceipt Advice. Receipt Line0 0z 00/ K Receipt Line0/ K Receipt Line  //0  0{ 0 0| 0} 2~,2/3/044444440000000#$99999:99:::::;< =.>>>?@:9999999:::::::#&L@254_$z  (  x  66XPP? )w]46XI  <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)<xx  6*XPP? )w]4*I 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. <xx  6L+XPP? )w]4L+@I 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.<xx  6/XPP? #w]4/I 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). < xx  6.XPP?  w]4.pI 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.<xx  6T(XPP?  w]4T( I 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.<~xx  6QXPP?  w]4Q I 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.<xx  6RXPP?  w]4R8 I 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.<xx   6TRXPP?   +w]4 TR I 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. <xx   6RXPP? S}]4 Rh I 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.<xx   6SXPP? }(}]4 S I 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.<xx   6SXPP? (}]4 S I 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.<]xx   6SXPP? $}]4 S0 I X Z<[Occurrence: The optionality and/or cardinality of the BIE. Expressed in XML Schema syntax.<Zxx  6HTXPP? }]4HT I 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!)<xx  6TXPP? s}]4T`I X b<cUBL Definition: This is the unique semantic business meaning of that Business Information Entity. <bxx  6UXPP? *}]4UI X <Documentary Namespace Prefix: This contains reference information suitable for the integration of the NDR Code Lists architecture.<xx  6tUXPP? 3}]4tUI 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<~xx  6UXPP? }]4U(I 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.<xx  6@d  7 DocumentSummaryInformation8CompObj fP X`hp x  ReceiptAdvice  Worksheets FMicrosoft Excel WorksheetBiff8Excel.Sheet.89q