UNDT000007-SC2 SC Code List. Identifier The identification of a list of codes. Code List Identification Identifier string UNDT000007-SC3 SC Code List. Agency. Identifier An agency that maintains one or more lists of codes. Code List Agency Identifier string Defaults to the UN/EDIFACT data element 3055 code list. UNDT000007-SC4 SC Code List. Agency Name. Text The name of the agency that maintains the list of codes. Code List Agency Name Text string UNDT000007-SC5 SC Code List. Name. Text The name of a list of codes. Code List Name Text string UNDT000007-SC6 SC Code List. Version. Identifier The version of the list of codes. Code List Version Identifier string UNDT000007-SC7 SC Code. Name. Text The textual equivalent of the code content component. Code Name Text string UNDT000007-SC8 SC Language. Identifier The identifier of the language used in the code name. Language Identification Identifier string UNDT000007-SC9 SC Code List. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list is located. Code List Uniform Resource Identifier Identifier string UNDT000007-SC10 SC Code List Scheme. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list scheme is located. Code List Scheme Uniform Resource Identifier Identifier string Is where the information that the BOD message carries is provided, in this case ShowCarrierRoute. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CarrierRoute). Is the schema based inheritance for all BODs. The logical model would also include the DataArea. OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. Indicates the version of the given BOD defintion. Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). Indicates the language that the contents of the BOD is in unless otherwise stated. Is the date that is used to identify the actual date and time a shipment occurs. Is the date that is used to identify the actual date and time a shipment occurs. Is the date that the business partner is requesting delivery of goods to arrive. Is the date that the business partner is requesting delivery of goods to arrive. Is the date that the supplier business partner promises delivery of goods Is the date that the business partner is supplying goods promises delivery of goods to arrive. Is the date that is used to mark the date and time a shipment loading process is complete. Is the date that is used to mark the date and time a shipment loading process is complete. This identifies the earliest possible date at which a shipment can be made. This may be used in conjunction with the ShipPriorToDueDateInd which indicates that the item, shipping unit or delivery may be shipped early. This identifies the earliest possible date at which a shipment can be made. This may be used in conjunction with the ShipPriorToDueDateInd which indicates that the item, shipping unit or delivery may be shipped early. Is the date the business partner supplying goods is promising goods to be shipped. Identifies the date on which the goods are scheduled to be shipped. The abstract Header type that is the basis for all non-statusable OAGIS Document Headers When a seller ships something via common to a buyer in accordance with the Uniform Commerical Code and international legal agreements, you must specify a particular "phrase" that states who assumes the risk of shipment, who is responsible for loading and unloading the goods, where ownership or title to the goods passes, who paid or pays the carrirer, etc. Examples of these "phrases" include: - "FOB Origin Prepaid and Add" (Free On Board - no cost for loading, title passes at seller's dock, seller prepaid freight cost and delivery insurance, seller will freight costs to cost of goods) - "FOB Destination" or "FOB Destination Prepaid" (Free On Board - no cost for loading, title passes at buyer's dock, seller prepaid freight cost and delivery insurance) In software applications, this phrase is commonly split into two coded pieces, a "legal terms" risk and responsibility component for use with common carriers (FOB Destination) and some kind of qualifying component (Prepaid and Add). Indicates the type of container. StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. AllowanceChargeABIEType is based on the UN/CEFACT TBG17 AllowanceChargeType that can be found the Reusable Aggregate Business Information Entity (RUABIE) XML Schema files. Identifies the type of charge that the given instance of Charge/Allowance. Identifies the sender of the given BOD instance Allows any digital Signatures to be added to the Instance of the BOD Instance in order to sign for any portion of the BOD content. This is the ID assigned to the document by the creator of the document. QDT000000 QDT Description_ Text. Type 1.0 Text Description A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified. QDT000000 QDT Incoterms_ Code. Type 1.0 Code Incoterms QDT000000 QDT Freight Terms_ Code. Type 1.0 Code Freight Terms ReturnCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned. ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD's noun exemplar. ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns. That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated. The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies. LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. Identifies the exchange rate between two currencies HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. CalculationABIEType is logically derived fom the UN/CEFACT TBG 17 ABIE CalculationType, which is defined in the Reusabale Aggregate Business Information Enitity (RUABIE) XML Schema file. Base type for all currency conversions. Is the conversion from one one currency to another currency Identifing the conversion factor and the source in which it was obtained, the date in which the conversion factor was set, and the effective period in which it is to be used. Used to distiguish the rate, based on the nature of the business process of the transaction. (e.g. Daily, End of Period, Corporate.) QDT000000 QDT Response_ Code. Type 1.0 Code Response CurrencyExchangeABIEType is logically derived from UN/CEFACT TBG17 ABIE CurrencyExchangeType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT Temperature_ Measure. Type 1.0 Measure Temperature The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. Address BaseType provides the information about the address or semantic address of an associated entity. ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT State_ Code. Type 1.0 Code State QDT000000 QDT Currency_ Code. Type 1.0 Code Currency Contains the sequenced identifier for the associated component or noun. QDT000000 QDT Delivery Point_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Delivery Point QDT000000 QDT Country Subdivision_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Country Subdivision QDT000000 QDT Country_ Code. Type 1.0 Code Country PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The purpose of the ShowCarrierRoute is to enable an application to provide a specific Carrier Route information from another business application module. The response to the GetCarrierRoute is the ShowCarrierRoute. The Show verb is used when sending the information about a specific instance of a business document or entity. The Show verb may be used to respond to a Get request or it can be used in a publish scenario, where it pushes information to other applications based on a business event.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the Show decides to use the information it receives to update. This is entirely the decision of the receiving software component and is not forbidden.The behavior of the Show verb is quite straight forward with one exception. The Show response to any Get request needs to read the request carefully to ensure the response is returning the requested Data Types. Describes a scheduled journey that a particular goods transportation service provider (freight carrier) is requested to perform on the behalf of a shipper, customer or other transportation corrdinator. The journey may contain one or more stops. There are many possible business applications in several environments that may use this capability. A CarrierRoute is typically generated by a transportation planning system to coordinate and optimize the movement of many goods shipment to reduce overall freight cost, improve overall delivery schedules, and ensure that a carrier's equipment is utilized efficiently. Other business systems typically interested in a CarrierRoute document include supply chain execution, supply chain visibility, warehouse management, and transportaion management systems. Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. TRACKINGID is a unique identifier for the purpose of tracking an individual package or shipment Examples of a valid TRACKINGID include: •An express parcel tracking number as typically assigned by UPS, DHL, Fedex or other similar carriers. •A UCC (Uniform Code Council) Serialized Shipping Container (SCC-18) identifier, as assigned by the shipper. •A "Pro Number" (Progressive Number), as assigned by an LTL (less-than-truckload) freight carrier. Since the same Pro Number can be assigned to multiple shipping units within an LTL shipment, the SHIPUNITSEQ and SHIPUNITTOT field identifiers may be used to identify the individual pieces. •The unique identifier of a motor freight trailer, railroad box or tank car, ocean freight container or other transportation vessel. Inidicates the shipping date and time of the line item. The scheduled delivery date provided by the supplier. Is the actual delivery date and time of the line item. Indicates the date in which the buyer/customer requests the order to be delivered. Indicates the date in which the order line was promised to be delivered to the customer. Identifies the date and time a shipment loading process is complete. This indicates the earliest possible date at which a shipment can be made for the line item Indicates the date in which the order line was promised to be shipped from the supplier to the customer. The scheduled date to be shipped provided by the supplier. Identifies the location shipped goods are to be loaded. Identifies the location the goods are to be shipped. Identifies the location goods are to be placed prior to loading for shipment. Identifies the general type of carrier transportation used to deliver goods. When a seller ships something via common to a buyer in accordance with the Uniform Commerical Code and international legal agreements, you must specify a particular "phrase" that states who assumes the risk of shipment, who is responsible for loading and unloading the goods, where ownership or title to the goods passes, who paid or pays the carrirer, etc. Examples of these "phrases" include: - "FOB Origin Prepaid and Add" (Free On Board - no cost for loading, title passes at seller's dock, seller prepaid freight cost and delivery insurance, seller will freight costs to cost of goods) - "FOB Destination" or "FOB Destination Prepaid" (Free On Board - no cost for loading, title passes at buyer's dock, seller prepaid freight cost and delivery insurance) In software applications, this phrase is commonly split into two coded pieces, a "legal terms" risk and responsibility component for use with common carriers (FOB Destination) and some kind of qu alifying component (Prepaid and Add). Uniquely identifies a shipping container Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. Represents the different Charges that may be applied to the associated document. A generic Party for non-validated or application-validated parties. A work-around for situations where Schema-validation of Parties is not feasible or not desired. Provides information pertaining to a particular pickup or delivery stop along the journey of a routed shipment. Each instance of the RouteStop pertains to a single physical destination shipping location and requires a subordinate ShipToParty. Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS. This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document. The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline. A copy of the ApplicationArea for the original BOD that was processed. Present either as additional reference information, or for use in identifying the BOD in situations where a BODReference is not known. The datetime on which the object was last modified The date that document was created within the system of record. Tare weight of the associated Entity. The Tare weight is the weight of the packaging when empty (in the case of a pallet the weight of the empty pallet) that when subtracted from the Gross weight results in the Net weight. Net weight of the associaed item. The net weight is calculated by subtracting the tare weight or the weight of the container from the GrossWeight. Gross weight of the associated entity. The total weight of the entity without reduction of packaging or container. I.e The Gross wieght of a pallet of goods includes the weight of the pallet. Quantifies the volume, or amount of space, that is occupied by an item, container or shipment. Identifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD. is the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document. If the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature. This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace. This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs. The BODId provides a place to carry a Globally Unique Identifier (GUID) that will make each Business Object Document instance uniquely identifiable. This is a critical success factor to enable software developers to use the Globally Unique Identifier (GUID) to build the following services or capabilities: 1. Legally binding transactions, 2. Transaction logging, 3. Exception handling, 4. Re-sending, 5. Reporting, 6. Confirmations, 7. Security. Is the primary document id for the document associated. Is the alternate document id for the associated document. The Attachment represents binary data files that may be included within a BOD. These files replace the paper specifications and drawings attached to a BOD definition to clearly communicate design requirements. This Data Type is optional. Attachment usage is further defined by its position. Is a contractual code used to describe the point where delivery occurs (goods ownership is transferred) in a contract of sale. It identifies the rights and obligations of each partner (supplier, carrier and customer) in the transaction and may specify the requirements to assume ownership (i.e. paying for the cost of the goods and/or transportation). The United Nations Trade Facilitation Information Exchange (UN/TraFIX) has established the following codes (INCOTERMS 1990) for use in international trade to Europe, Asia and the Pacific. (See http://www.unece.org/trade/rec/rec05en.htm). These terms may also be found in the United States Uniform Commercial Code (UCC). EXAMPLES EXW - Ex Works ... (named place) FCA - Free Carrier ... (named place) FAS - Free Along Ship ... (named port of shipment) FOB - Free On Board ... (named port of shipment) CFR - Cost and Freight ... (named port of destination) CIF - Cost, Insurance and Freight ... (named port of destination) CPT - Carriage Paid To ... (named place of destination) CIP - Carriage and Insurance Paid to ... (named place of destination) DAF - Delivered At Frontier ... (named place) DES - Delivered Ex Ship ... (named port of destination) DEQ - Delivered Ex Quay (Duty Paid) ... (named port of destination) DDU - Delivered Duty Unpaid ... (named place of destination) DDP - Delivered Duty Paid ... (named place of destination) Identifies the place where the transfer of ownership takes place. Describes how the freight cost for a shipment of goods should be billed. EXAMPLES: Prepaid, Collect, Third Party, Prepaid and Add, Consignee Billed Is the Identifiers of the given instance of an entity within the scope of the integration. The providedBy attribute identifies the party that provided or knows this party by the given identifier. Identifies the sequence in which the associated entity is to occur with in a given operation, step or business process.. The unique identifier of a container that holds the associated entity. A container is typically used for shipping material. Whether they be raw material or finished goods or piece parts. Provides the Hazardous Material Code and description. Identifies the materials used in the packing of a product within a container or package. Examples are styrofoam, bubble wrap etc Identifies and decribes the material used to build a shipping unit or container. The ID identifies the material of the container or the shipment package The Description describes the material or container a product or item is shipped in. This is most often used for cases where a product is shipped in a returnable container. Examples include: Steel Case Rail Road Car Special Hazardous Material Case An explicit period of time for the bucket. Is the base amount from which the charge/allowance is derived. Is the base quantityfrom which the charge/allowance is derived. The monetary value of the object in which the amount is associated Allows the sender to indicate how the Charge/Allowance was calculated. Identifies the reason for an activity Identifies the exchange rate between two currencies. For the transaction in which this is associated. Provides the logical location of the server and applications from which the Business Object Document originated. It can be used to establish a logical to physical mapping, however its use is optional. Each system or combination of systems should maintain an external central reference table containing the logical names or logical addresses of the application systems in the integration configuration. This enables the logical names to be mapped to the physical network addresses of the resources needed on the network. Note: The technical implementation of this Domain Naming Service is not dictated by this specification. This logical to physical mapping may be done at execution time by the application itself or by a middleware transport mechanism, depending on the integration architecture used. This provides for a simple but effective directory access capability while maintaining application independence from the physical location of those resources on the network Provides a finer level of control than Logical Identifier and represents the business application that issued the Business Object Document. Its use is optional. The Open Applications Group has not constructed the list of valid Component names. A suggestion for naming is to use the application component names used in the scenario diagrams in section two of OAGIS. Example Components may be Inventory, or Payroll. Describes the business event that initiated the need for the Business Object Document to be created. Its use is optional. Although the Task may differ depending on the specific implementation, it is important to enable drill back capability. Example Tasks may be Receipt or Adjustment. Enables the sending application to indicate the instance identifier of the event or task that caused the BOD to be created. This allows drill back from the BOD message into the sending application. The may be required in environments where an audit trail must be maintained for all transactions. Is an option controlled by the Sender business application. It is a request to the receiving application to send back a confirmation BOD to the sender. The confirmation Business Object Document may indicate the successful processing of the original Business Object Document or return error conditions if the original Business Object Document was unsuccessful. The confirmation request has the following valid values: Never - No confirmation Business Object Document requested OnError - OnError send back a confirmation Business Object Document only if an error has occurred Always - Always send a confirmation Business Object Document regardless Identifyies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized be the receiving system indicates what can be done on the receiving system(s). Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. Element for the communication of all codes. This is the DateTime the associated object is made effective Contains the set of possible identifiers for an associated Party. Identifies the Name of the object in which associated. The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. Contacts are the point of communication with the given party. In the case of an organization it may be the requestioner, the buyer, customer service, etc. Is the bill of lading identifier. Identifies the ShipToParty for the document or the line. In a lot of cases, this is the same as the CustomerParty. In multi-organization purchasing, the CustomerParty may be different from the BuyerParty Is a reference to a Shipment. Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Used to identify a Medical First Aid Guide (MFAG) for hazardous substance. Is the Technical name of the associated entity. The placard endorsement that is to be shown on shipping papers for hazardous materials. Can also be used for the number of the orange placard (lower part) require on transport. The placard notation that is to be shown on shipping papers for hazardous materials. Can also be used for the number of the orange placard (upper part) require on transport. Specifies the level of marine pollution for this hazardous substance. A code identifying the Inhalation Toxicity Hazard Zone for the hazardous substance, this is generally identfied by a government agency in the United States this is provided by the US Department of Transportation. Temperature of the associated entity. FlashpointTemperature is related to hazadous substances or goods, indicates the temperature at which the associated substance of goods become flammable, explossive or toxic.. The primary entry route by which the Hazardous Material gains access to the human body. Allows the data to be embedded directly into the BOD instance. Indicates the name of the File being referenced. Allows a reference to an ISBN. Identifies the type of the file type of the attachment. Specifies how big the file is. Is the title of the person. For example Dr.. Start timestamp indicating the starting point of the event. Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. Is the ending timestamp of the event. Is the multiplier to convert the source units to the target units. (e.g.) The conversion of one currency to another currency monitary amount in the from currency is multiplied by the CalculationRateNumeric to calcultate the monitary amount in the to currency. Another example maybe the conversion between units of measure. Idenfifies the source that brought the associated entity. Indicates the time period in which the associated component is effective. Indicates the type of the object in which assoicated. Identifies the item number assigned to the type of goods for the purposes of freight classification and cost calculation. Is a unique identifier for the purpose of tracking an individual package or shipment. Indicates when the status change occured. The source Currency Code for the monetary amount to be converted. Specifies the unit base of the source currency for currencies with small denominations. The target Currency Code for the monetary amount to be converted. Specifies the unit base of the target currency for currencies with small denominations. Identifies the date in which the conversion factor was set by the Issueing agency. Identifier for a business or individual provided by the government. This maybe a FIIN, Social Security Number, or Drivers License Number to name a few. Identifier for business provided by Dun and Bradstreet. The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. Is the value and unit of measure in the z-axis in a thrre dimensional system. Examples of this maybe the Altitude in the case of a map of the world, or the height or shelf in a rack system in the case of a manufacturing or warehouse facility. Is the system in which the userid applies. Format Code indicates the format of the address. Examples are US Military, US Formatted Address, European Formatted Address etc. There is no intent to decode the address formats - these are informational only. No list of valid values exists or is proposed here. The name of the person or organization that the associated entity is intended. The name that the associated entity is sent by. The Number of the building or house on the street that identifies where to deliver mail. For example, Building 300 on Standards Parkway The building or house name on the street that identifies where to deliver mail The Street Name where the building/ house is located Identifies the apartment number or office suite. The floor where the housename is located Identifies a Post Office Box number Identifies the Dock or the Mail Stop or Lane or any other specific Delivery Point. Qualifies the further division of the City, example a city may have many districts or Boroughs. The type attribute identifies the type of this entity e.g. City, Borough etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Identifies the town or the city Qualifies the further division of the Country. These may be Districts, Regions, States, Provinces etc. A possible list of values is as specified in ISO 3166-2. The type attribute identifies the type of this e.g. District, Region etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Country in which the Address is in. A possible list of values is as specified in ISO 3166-2. Postal Code of the Address. Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc A text description of the responsibility of the associated entity. A value expressing the value of a Sequence. Identifies the channel in which the associated entity comes. Code identifying the usage of the contact point e.g. business, private, etc. The country dialing code for a communication number. The area dialing code for a communication number. The commication number, not including country dialing or area dialing codes. The extension of the assoicated communication number. The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70. Indicates that the associated entity preferrs HTML format. Is a message to the reader about the object associated. This is the net weight of the goods or materials being shipped. Quantifies the volume, or amount of space, that is occupied by an item, container or shipment. Provides the Identifier(s) of the document being communicated. Uniquily identifies a Document within an organization. Typically there is only an ID for a document within one system. However, with the use of different business applications there maybe different ids assigned to the same document within an organization from the different systems and in the case of B2B transactions different businesses may have different Identifiers for the same document. This construct is designed to allow for these different identifications. Common Free Form Text elements that occur together. Common References to DocumentReferences and Attachements Contain the ids for a given party. These ids may be assigned by multiple organizations. Indicates the ID of the associated component or noun. QDT000000 QDT Month_ Date. Type 1.0 A particular point in the progression of time together with the relevant supplementary information. Provides the XML Schema simpleType that allows either just the Date or the Date and Time to be provided in the elements that are based on this type and/or types that use this as their base. Date Month