GB/Z 25114.1-2010 Business Messages Based on ebXML Part 1: Trade Items GB/Z25114.1-2010 Standard Download Decompression Password: www.bzxz.net
This part specifies the rules for writing business messages based on ebXML, as well as the trade item messages transmitted in business messages. Applicable to the compilation of business messages for trade items.

ICS35.040
National standardization guidance technical documents of the People's Republic of China GB/Z25114.1--2010
Business message based on ebXML
Part 1: Trade items
ebxMLbasedbusinessmessage
Part1:Coreitem
Published on September 2, 2010
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Administration of Standardization of the People's Republic of China
Implementation on December 1, 2010
Normative references
Terms, definitions, abbreviations·
ebXML business message writing rules -
Core trade item message details
Core trade item document class diagram
Core trade item high-level class diagram
Core trade item detail level class diagram
Data dictionary
FMCG trade item extension
Trade item related data extension··
Trade item message example based on ebXML business message 12
Rules for writing ebXML business messages
Appendix A (normative appendix)
Appendix B (normative appendix)
Appendix C (normative appendix)
Appendix D (informative appendix)
FMCG trade item extension.
Trade item related data extension
Trade item message example based on ebXML (Item.xsd)GB/Z 25114.1—2010
《Business Messages Based on ebXML》 is currently divided into three parts: Part 1: Trade Items; Part 2: Participant Information; Part 3: Orders.
New parts may be added in the future.
This part is Part 1 of 《Business Messages Based on ebXML》. GB/Z25114.1—2010
This part modifies and adopts the core trade item part of the ebXML Business Message Series Standard 1.0 issued by GS1 (International Article Numbering Association). The trade item message transmitted in the exchange of business messages based on ebXML is given. The main differences between this part and the original international standard are as follows: the message writing rules in the GS1 standard are included as Appendix A of this part; - Normative reference documents are added;
- Terms, definitions and abbreviations are added. Appendix A, Appendix B and Appendix C of this part are normative appendices, and Appendix D is an informative appendix. This part is proposed and coordinated by the National Logistics Information Management Standardization Technical Committee. The drafting unit of this part: China Article Coding Center. The main drafters of this part: Li E, Zhang Nan. 1 Scope
Business messages based on ebXML
Part 1: Trade items
GB/Z25114.12010
This part specifies the rules for writing business messages based on ebXML, as well as the trade item messages transmitted in business messages. This part applies to the compilation of business messages for trade items. 2 Normative references
The clauses in the following documents become the clauses of this part through reference in this part. For any dated referenced document, all subsequent amendments (excluding errata) or revisions are not applicable to this part. However, the parties to the agreement based on this part are encouraged to study whether the latest versions of these documents can be used. For any undated referenced document, the latest version applies to the part. GB/T2659--2000 Codes for country and region names of the world (eqvISO3166-1:1997) GB/T4880.1-2005 Language name codes Part 1: 2-letter codes GB/T7408-2005 Data elements and exchange formats Information exchange date and time representation GB/T12406-2008
3 Codes for currency and funds
GB/T16828-2007
GB/T192512003
Commodity barcoding Participation position coding and barcode representation Guidelines for coding and symbol representation of trade items GB/Z25114.2--2010 ebXML-based business messages Part 2: Party information 3 Terms and definitions, abbreviations
3.1 Terms and definitions
The following terms and definitions apply to this part. 3.1.1
Core Trade Item
coreitem
A trade item is a product or service for which predefined information is required and which can be priced, ordered or invoiced at any point in the supply chain for all trading partners to trade. It includes various forms of individual items and their different packaging types.
Required attributes for consistent trade item information between trading partners. These data attributes maintain the integrity of the primary product identification and the identification of the trade item or service.
Global Trade Item Numberglobaltradeitemnumber;GTIN is used to uniquely identify trade items worldwide. 3.1.3
Global Trade Participant Location Numbergloballocationnumber;GLNA code that identifies a legal entity, a functional entity, or a physical entity. 3.2 Abbreviations
FMCG fast moving consumer goods GLN global location number global trade participant location code GTIN global trade item number global trade item code UML unified modeling language
Unified modeling language
GB/Z25114.1—2010
4 ebXML business message writing rules
4.1 Business process architecture
See A.1 for business process architecture.
4.2 Writing rules
See A.2 for writing rules.
4.3 Message architecture
See A.3 for message architecture.
5 Details of core trade item messages
The content of core trade item messages includes essential data elements such as product identification code, trade item description, measurement unit and trade item classification.
The data format in the message shall comply with the provisions in Appendix A. 5.1 General Information
Information that is common to all messages and is transmitted at the beginning of a trade item message. 5.1.1 Document Class
Used to describe basic information about the content of the message, including version number, creation date and time. contentVersion - the version number of the document content. contentVersion is mandatory. creationDate The date the message was created. The format is: "YYYYMMDDTHHMMSS". creationDate is mandatory. documentStructureVersion - the version number of the document structure. documentStructureVersion is mandatory. 1lastUpdateDate - the date of the latest update. The format is: YYYYMMDD". LastUpdateDate is a mandatory item. 5.1.1.1 DocumentStatus class is used to indicate whether the document is a source document or a copy. COPY - a copy of the source document.
ORIGINAL - the source version of the document.
5.2 ItemInformation class ItemInformation describes the attributes required for consistent information of trade items between trading partners. For core trade items, three levels of classes are used: ItemDescription, PartyIdentification and ItemIdentification. 5.3 ItemDescription class ItemDescription attributes include: brandName, discriptionShort, itemName, etc. Each attribute consists of a language code and text. The text language uses GB/T4880.1-2005 two-letter code. additionalAttributeDescription—Free text used to record additional product attributes. It can be used to identify any additional information that the information provider needs to transmit, such as the manufacturer's name, etc. additionalAttributeDescription is optional, brandName is the product name. brandName is optional. descriptionShort---A brief description of the trade item, used for products in the POS system. descriptionShort is mandatory. itemDescription-——A description of the product provided by the information provider. itemDescription is optional. itemName-—A more complete product name than the product name. itemName is optional. 5.3.1Classification Classification of trade items is mandatory and can be repeated as needed. Classification includes the following attributes: classificationAgency The group responsible for the classification code. classificationAgency is mandatory. 5.3.1.1ClassificationCategory ClassificationCategoryCode
Provides the code assigned by the agency responsible for classification and used to classify the trade item. classificationCategoryCode is mandatory. GB/Z25114.1—2010
classificationName--Text description of the classification name, including the language indicator expressed in ISO code. classificationName is a mandatory item. 5.3.1.2ClassificationAttribute (classification attribute) class ClassificationAttribute provides the code and text description of the classification of trade items or services. classificationItemCode--The classification code of the trade item assigned by the classification management agency. classificationltemCode is a mandatory item.
classificationItemName Text description of the classification of trade items or services. classificationltemName is a mandatory item. 5.4PartyIdentification (Party Identification) class Global Location Number (GLN) or AlternatePartyIdentification can be used to identify a trade party. Each party can only use one primary party identifier. For the party message data format, please refer to GB/Z25114.2.
5.4.1GlobalLocationNumber (Global Trade Party Location Code) ClassGlobalLocationNumber (GLN) is a 13-digit number used to uniquely identify a location. For the specific encoding structure, see GB/T16828-2007.
glnSpecific GlobalLocationNumber. gln or AlternatePartyIdentificationType is a mandatory item. 5.4.2AIternatePartyldentification (Other Party Identification) Classvalue—AlternatePartyldentification defines alternative party identification. 5.4.2.1AlternatePartyldentificationType (Other Party Identification Type) ClassAlternatePartyldentificationType describes the type of alternative party identification and uses AlternatePartyIdentificationTypeList.
5.5ItemIdentification (Trade Item Identification) ClassIdentifies a trade item or service. A trade item can use either GlobalTradeItemNumber (GTIN) or AlternateItemIdentification, but not both at the same time. 5.5.1GlobalTradeItemNumber ClassGlobalTradeItemNumber is the primary identifier of a trade item. It must be used once a GlobalTradeItemNumber (GTIN) code is assigned. And only one primary trade item identifier can be used. For the specific encoding structure, see GB/T19251-2003.
gtin—a specific GlobalTradeItemNumber. gtin or AlternateItemIdentification is a mandatory item. 5.5.2AlternateItemIdentification ClassAlternateltemldentificationAlternate trade item identification. When there is no GTIN, use AIternateItemIdentifi-cation.
See B.2.5 in Appendix B.
5.5.3UnitOfMeasure ClassUnitOfMeasure describes the physical characteristics of a trade item (such as each, each pair, each box, each roll, each set and each box, etc.). A Trade Item can have only one UnitOfMeasure, mandatory. netContent - the net content of the Trade Item, mandatory. grossWeight - the gross weight of the Trade Item, including packaging, mandatory. packagingWeight - the packaging weight of the Trade Item, mandatory. depth - the length of the Trade Item, optional. diameter
the diameter of the Trade Item, optional.
GB/Z25114.1—2010
heightthe height of the Trade Item, optional. pegHorizontal -
the horizontal distance of the peg. The horizontal distance from the edge of the Trade Item to the center of the hole for the peg when the Trade Item is fixed to the display board, optional.
pegVertical -
the vertical distance of the peg. The vertical distance from the edge of the Trade Item to the center of the hole for the peg when the Trade Item is fixed to the display board, optional.
the width of the Trade Item, optional.
6 Core trade project document class diagram
Based on the definition of trade project messages, the static class diagram is established using the Unified Modeling Language (UML) method. The core trade project document class diagram is shown in Figure 1.
Document
.optional.contenrVersion：String=i.ocreationDate:DateAndTime
optionaldocumentStructureVecsioString
optionallastUpdateDateSimpleDateParty
DatchAd
+ documentStatus
Figure 1 Core trade project document class diagram
KenumerationvalueNet
DocumentStatu
COPY:String
ORIGINAL:String
equestForPaymer
Simpleinvoie
Core trade project high-level class diagram
GB/Z25114.1—2010
According to the definition of trade item message, the static class diagram is established using the Unified Modeling Language (UML) method. The high-level class diagram of the core trade item is shown in Figure 2.
Partyldentficatior
UnitOfMeasure
+manufacturer
+unitOfMeasure
GlobalTradeltemNumber
+replacedltem
mDescnptior
+itemDescriptionbzxz.net
+ itemInformation
+itemldentification
Interface>
Itemldentification
High-level class diagram of core trade item
+ classification
Classification
FMCGExtensions
GB/Z25114.1—2010
Core trade item detail layer class diagram
8.1 Core trade item detail layer class diagram
Based on the definition of trade item message, the static class diagram is established using the Unified Modeling Language (UML) method. The core trade item detail layer class diagram is shown in Figure 3.
netContent :Measurement
gross Weight:Measurement
packagingWeight:Measuremen
Koptional)> depth:Measuremen
Measurement<optional>width:Meas
Partyldentificatic
GlobaTradeltemNumt
+Itemldentification
<addhtionalAttributeDeseription:TextDescriptionKoptional)>brandName:TextDescriptiondescriptionShont :TextDescription《optional>itemDescription:TextDeseription《optional)>itemName:TextDescriptionossificationAgencyString
+classificationCategory
ClassificationCalegory
classificationCategoryCode:StringlassificationName:TextDescniptionFigure 3 Class diagram of the core trade item detail layer||tt ||(classificationAttribute
ClassificationArtnbute
classificationtemCode:StringclassificationltemName:TextDescription8.2
Participant Identification Class Diagram
GB/Z25114.1—2010
According to The definition of trade project messages uses the Unified Modeling Language (UML) method to establish a static class diagram, and the participant identification class diagram is shown in Figure 4.
Par tyldentification
+additionalPartyldentification0.
AltematcPartyldentification
value:String
gln:Suring
data dictionary
trade item information||tt| |Classification
classificationAgency
ClassificationAttribute
classificationltemCode
classificationltemName
ClassificationCategory
classificationCategoryCode
classificationName
ItemDescription
additionalAttributeDescriptionbrandName
descriptionShort
itemDescription
itemName
+ altermatePartyidentificationAltermatePartyldentificationType《enumeration value)》
AlternateParyldentificationTypeListvalue:String
Participant identification class diagram
Data type
Required/Optional
GB/Z25114.1 —2010
Trade Item Identification
UnitOfMeasure
netContent
grossWeight
packagingWeight
diameter
height||tt| |pegHorizontal
pegVertical
GlobalTrade ltemNumber
Data Type
Measurement
Measurement
Measurement
Measurement
Measurement
Measurement
Measurement
Measurement
Measurement
Integer
Required/Optional
Note: Trade items can be identified using Global Trade Item Number (GTIN) or Alternate Item Identification. But the two cannot be used at the same time. For the AlternateItemIdentificaiton class, see Appendix B. 9.3
Party Identification
AltermatePartyIdentificationvalue
AlternatePartyldentificationTypevalue
GlobalLocationNumber
Data Type
Required/Optional||tt| |Note 1: Parties may be identified using either the GlobalLocationNumber (GLN) or the AlternatePartyldentification, but only one primary identifier may be used for each party.
Note 2: In the case where the class contains an enumeration value , you must choose one of these values ​​(only one). Enumeration values ​​are represented in uppercase, that is, all letters are uppercase and each word is separated by an underscore. For example, REQUESTED_DELIVERY. 9.4
Trade Item Document Information
Document
contentVersion
creationDate
documentStructureVersion
lastUpdateDate
DocumentStatus||tt| |ORIGINAL
Data Type
DateAndTime
Required/Optional
Note 3: If the class contains enumeration values, it must be between these values. Select one (only one) from the list. Enumeration values ​​are capitalized, i.e. all letters are capitalized and each word is separated by an underscore, such as REQUESTED_DELIVERY. 10
FMCG Trade Item Extension||tt ||For the content of FMCG trade item extension, please refer to Appendix B. Trade item linked data extension
Trade item linked data extension includes trade item attributes other than core trade items, please refer to Appendix C. Example of a Trade Item Message Based on ebXML Business Message This section gives an example of a message. The content is shown in Appendix D.
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.