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 UpdateReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (ReceiveDelivery). 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. ReceiveDelivery typically report on the ReceiveDeliveryItems. Provides general information about the ReceiveDelivery document that is used to receive a specific quantity of material goods The EffectiveDateTime is the date/time the received material is posted to other business systems as being available for use. ReceiptLine represents the goods line item detail of the receipt document. THis can be used by itself for traditional receiving against Purchase Orders or other line-item oriented buisness documents, or in conjunction with the ReceiptUnit element to summarize ship unit item detail at line level Provides information that identifies and describes a particular shipping unit being received. This information usually directly references a DeliveryUnit on an OAGIS Delivery message or other shipping document. May also be used to provide context to adequately detail inventory discrepancies or compliance charges for a particular shipping unit The Warehouse Location identifies the place from where the goods are shipped Contains the quantity of units or things shipped. This represents the container(s), not the product shipped. An example of this is "4 truck loads" or "2 wooden crates". Is the storage facility for inventory. Is the storage facility for inventory. 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. The estimated weight of an item or container. An estimate is provided as a processing alternative when the actual weight of an item is not known or cannot be calculated exactly. The estimated weight of an item or container. An estimate is provided as a processing alternative when the actual weight of an item is not known or cannot be calculated exactly. This is the net weight at loading time of the container in which the materials are being shipped. Identifies the general type of carrier transportation used to deliver goods. The estimated weight of an item or container. An estimate is provided as a processing alternative when the actual weight of an item is not known or cannot be calculated exactly. The estimated weight of an item or container. An estimate is provided as a processing alternative when the actual weight of an item is not known or cannot be calculated exactly. This is the net weight at loading time of the container in which the materials are being shipped. 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 identifies discrepancy information for the receipt. The Type identifies the discrepancy type. The ReasonCode Identifies the reason for the discrepancy. If the discrepancy applies to specific quantities of the item, then the quantity can be specified. If no quantity is specified, the discrepancy applies to the inventory occurence as a whole This is an exception classification that codifies the general problem encountered during a business process, such as receiving goods Identifies the reason for the discrepancy. If the discrepancy applies to specific quantities of the item, then the quantity can be specified. If no quantity is specified, the discrepancy applies to the inventory occurence as a whole Extends the ItemBaseType to identify a set of Items along with their SerialNumbers and/or Lot information. Provides information about a specific quantity of goods inventory contained within a shipping unit. RECEIPTITM is used to provide a detailed breakdown of RECEIPTLN inventory for inventory discrepancies or compliance charges for a particular shipping unit 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. The abstract Header type that is the basis for all non-statusable OAGIS Document Headers QDT000000 QDT Country_ Code. Type 1.0 Code Country 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 Freight Terms_ Code. Type 1.0 Code Freight Terms Indicates the type of container. LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the basis for Items. StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT Description_ Text. Type 1.0 Text Description 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 a unique serial number and/or lot number for an item QDT000000 QDT Response_ Code. Type 1.0 Code Response A distribution identifies how monetary amounts are distributed accross an organization. Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. This is the ID assigned to the document by the creator of the document. Identifies the exchange rate between two currencies 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. The ClassificationCodes that identify a single or hierarchical association of classifications. For example, Pump, Centrifugal would be represented by two Codes, the first one as Pump, the second as Centrifugal. The Sequence attribute of the Code identifies the hierarchical position of the identifier in the case of multi-level codes. The name attribute identifies the name of the corresponding classification level. Possible examples are ROOT, BRANCH, LEAF HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Contains the sequenced identifier for the associated component or noun. TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT State_ Code. Type 1.0 Code State 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.) ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. CurrencyExchangeABIEType is logically derived from UN/CEFACT TBG17 ABIE CurrencyExchangeType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Identifies the agiven portion of an organization. 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 Temperature_ Measure. Type 1.0 Measure Temperature ProjectABIEType is logically derived from UN/CEFACT TBG17 ABIE ProjectType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicate the type of project. PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the tag and information of the new information to be passed. Is the name of the tag for the information being passed. Is the type of the information being passed in the NameValue. DimensionABIEType is logically derived from UN/CEFACT TBG17 ABIE DimensionType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT Currency_ Code. Type 1.0 Code Currency CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The UpdateReceiveDelivery may be used to update the receiver's internal receiving and order management business applications to indicate that the requested material has arrived, including any unexpected quantity, condition or other exception discrepancies. There are many other possible business applications in several environments that may use this capability. For example: 1. A Purchasing application may use this BOD to notify an Accounts Payable application of a specific delivery. This will enable the Accounts Payable application to accurately calculate the amount it needs to pay a business partner. 2. A Purchasing application could use this to notify a MRP, Inventory, or Manufacturing business application that a delivery has occurred and the goods are available for use or inspection, etc. 3. An MRP/Inventory system could use this BSR to communicate changes on a physical receipt in inventory to the Purchasing system. The UpdateReceiveDelivery supports receipts at either the line item level and/or the ship unit level. Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents. The Update verb is used to describe specific processing in a more fine-grained manner beyond add, change or delete processing. An example is the update of inspection information from one business application to another. The event is not adding a document, or changing fields per se, it is communicating the occurrence of an event as well as the corresponding data that accompanies the event. Represents a transaction for the receiving of goods or services. It may be used to indicate receipt of goods in conjunction with a purchase order system. The Delivery document contains CHARGE and DISTRIBUTN elements at various levels to support the assessment of receiving service or compliance penalty charges. Several large retailers that demand receiving efficiency commonly assess penalty charges for supplier deliveries that are not compliant with the retailer's policies. Charges may be incurred for deliveries, ship units or items that contain discrepancies from what was ordered or electronically manifested, for improper labeling of items and ship units and the incorrect packing or loading of ship units. 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. Provides general information about the ReceiveDelivery receipt document that is used to receive a specific quantity of material goods from a supplier. Provides general information about the item inventory being delivered, including the requested and actual quantities. This information usually directly references a line item or Delivery schedule line on a sales order, purchase order or other inventory transfer document. 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. 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. This indicates the receiving service charge associated with the receiving document either as a whole, or at line level dpending on usage This is the DateTime the associated object is made effective The date and time that the associated object was received. Is the bill of lading identifier. Uniquely identifies a shipping container 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. This is the Party (the person or organization) to receive delivery of a the associated entitys. This can be goods, services, cheques, etc. Several examples of the value of this field include an office number, a complete address, or a person This identifies a physical or logical point of receipt within a receiving organization This identifies an Advanced Shipment Notice document Provides receiving discrepancy information for the ReceiveDelivery header as a whole, for a particular ReceiptLine, for the receipt of a shipping unit as a whole ReceiptLine, or to a particular item within the shipping unit (ReceiptUnit). Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. This is the quantity that is shown on the Packing Slip when goods are received from a supplier. This information is generally obtained from the supplier's Advance Ship Notice (ASN) or manually entered on receipt Is the number of items that have been received for the associated entity. Is the quantity of items returned to inventory. Or when used in logistics: The the quantity of the item for which the customer refused delivery. This determines the receipt routing of an item or part. Examples of values include: Customer consignment Inspection Vendor consignment Blocked Bonded User defined SYNONYMS Material Status Material Condition Code This contains the quantity of units or things shipped. This represents the container(s), not the product shipped. An example of this is "4 truck loads" or "2 wooden crates" Is the storage facility for inventory. 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. The estimated weight of an item or object. An estimate is provided as a processing alternative when the actual weight is not known or cannot be calculated exactly. This is the net weight at loading time of a container in which the materials are being shipped. Provides the hazardous material codes that are associated with the given instance of the item. Represents the identifier of the country of origin of an item, service or shipment Indicates the DistributionCenter that the Seller will ship the items from. Identifies the general type of carrier transportation used to deliver goods. This describes any special, physical handling needs that the freight might have. For example, the need for a lift gate Idenitifies the loading dock that the associate entity is to be taken. Identifies the party that the goods or services are being shipped or sent from. Idenitfies the party that serves as the carrier of the goods or services for the transaction. Describes how the freight cost for a shipment of goods should be billed. EXAMPLES: Prepaid, Collect, Third Party, Prepaid and Add, Consignee Billed 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. Communicates the need for an import license on a good or service. Valid values are '0' for no license required, and '1' for license required. Is the quantity of a material or product ordered by the customer. Is the quantity that is shipped. This segment is used to describe the quantity of item’s, products or resources open to processing on a document header or line. The open quantity may refer to the quantity’s being budgeted, produced, purchased, received, sold, or used This is the quantity of product or item that is on back order. Is used to identify who or which organization owns the item or part. The content of this Field is user defined based on a specific Customer or Supplier. Is a reference to a Requisition Is a reference to a PurchaseOrder Is a reference to a SalesOrder Identifies the lot number and serial number details for a specific quantity of items. This can be used to identify either all the serial numbers within a given lot, or lot numbers and serial numbers independent of each other This is the actual weight of the ReceivedQuantity for the Item if the NetWeightQuantity cannot be calculated precisely via arithmetic because the goods do not have a consistent per unit weight. This quantity is generally used with the CatchWeightConversion Factor. The catch weight conversion factor is a stock keeping conversion factor for inventory goods. This is a special conversion factor for when the units of measure can not be converted using arithmetic. This conversion factor is used with the CatchWeightQuantity. Examples of the use of this factor include: Number of Chickens to a Box Number of units of a chemical in a barrel Is the declared monetary value of the contents of a shipping unit or a delivery for insurance purposes. Is the timestamp that indicates when the associated entity(ies) are shipped. Communicates the need for an export license on a good or service. Valid values are '0' for no license required, and '1' for license required. 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). 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. Indicates the type of the object in which assoicated. Identifies the reason for an activity Is used to describe the quantity of item's, products or resources being budgeted, produced, purchased, received, sold, or used. Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. Unique serial number assigned to the given item instance by the manufacturer. This can be used in three ways: specify multiple serial numbers for a given lot, or specify multiple lots without serial numbers, or specify multiple serial numbers without a LotID. Typically, the parent element that uses LotSerial also provides the ability to provide a single lot number and serial number pair, which can be used for the cases where there are no multiple lots or serial numbers involved In a set of similar shipping units for a delivery, ShipUnitSequenceId represents a particular unit out of the total set. When used in conjunction with ShipUnitTotalId and printed on a shipping unit label or packing list, the receiving partner can easily ascertain whether or not the delivery was complete. In a set of similar shipping units for a delivery, ShipUnitTotalId represents the total or final unit in the set. When used in conjunction with ShipUnitSequenceId and printed on a shipping unit label or packing list, the receiving partner can easily ascertain whether or not the delivery was complete. 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. Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. The datetime on which the object was last modified The date that document was created within the system of record. Is a reference to an associated work-in-process operation. Element for the communication of all codes. The accounting distribution information associated with a Business Object Document. The position of the Distribution within a Business Object Document provides the context and additional meaning. 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 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 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. Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Identifies if the Item is a Service This identifies the classification of an entity. An entity may be classified into mulitple groups for different reasons. Examples of Classification include Commodity Codes, Freight Classifications, Product Line classifications and so on. Suggested Values are COMMODITY, FREIGHT, PRODUCTLINE Identifies the specification of an entity. Provides the Hazardous Material Code and description. Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. Identifies the Release Number in the case of Blanket POs Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. Is the ScheduleLineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated by the DocumentId under DocumentIds. Is the SublineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated by the DocumentId under DocumentIds. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. An explicit period of time for the bucket. 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 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 exchange rate between two currencies. For the transaction in which this is associated. Is the primary item Identifier associated with the given item within the scope of the given integration as provided by the Party or entity that has created this document instance. Is the identifier provided by the customer for the item. Is the identifier provided by Manufacturer for the Item. One example may be the model number. Is the identifier provided by the supplier for the item. Allows an instance of an item to have a UPC identifier associated. Allows an instance of an item to communicate the ElectronicProductCodeID that it was assigned. The ElectronicProductCodeID is one of the major RadioFrequency Identifiers used. Identifies the Lot Identifiers of all of the lots that are contained in the associated set of items. Indicates when the status change occured. Identifies the financial ledger to be used when updating balances Identifies the percentage of the Line Price applicable to the distribution line. This is used to derive the Amount on the distribution line. Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc. Accounting code elements Identifies a project that is associated with the given component. Represents the Properties or Features of the associated entity Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. Identifies a grouping of entities together. An example usage may be a grouping of Operatations for a Routing. Identifies the sequence in which the associated entity is to occur with in a given operation, step or business process.. Identifies the step of the operation being reported against. Indicates the type of step that the operations reference is.. Identifies the agiven portion of an organization. Some commonly defined Units are identified here. These units are typically used to track financial data in reporting systems within an organization. Similar to Business Units, Organizational Units are only relevant within an enterprise 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. 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. Provides the dimensions of the associated component. Is the number of instances of the item in the unit of measure contained with in the package. Is the maximum number of instances of an item in the unit of measure that maybe contained within the package. 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. Identifies the Activity that is associated to the Project in which the distribution is to be assigned.. An ActivityId cannot occur with out a ProjectId. 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. Is the tag and information of the new information to be passed. 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.. 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. The Cost Center is an accumulator of cost information that may be an organizational unit or area of responsibility. It is an organization code that allows a grouping of expenses and costs. The Profit Center is an accumulator of revenue information that may be an organizational unit or area of responsibility. A profit center can be used for internal management control. Profit centers can calculate operating profit using the cost-of-sales accounting and/or period accounting methods A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law. It is normally the primary balancing segment of the GL Account structure. Typically, this is the owning entity for the transaction. Synonyms are Business Unit, Fund, G/L Company, Joint Venture, Non-Profit Association Name A value expressing the value of a Sequence. Indicates the width of an object Indicates the length of an object Indicates the Height of an object 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. Contains the TrackingID and the two optional elements that uniquely identify a ship unit Common Free Form Text elements that occur together. 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 References to DocumentReferences and Attachements Contains the Item IDs for an associated item. This group identifies an entity within an enterprise from both the financial and operational perspective Contain the ids for a given party. These ids may be assigned by multiple organizations. Indicates the ID of the associated component or noun. A group that contains the identifier for 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