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 UpdateMaintenanceOrder. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (MaintenanceOrder). 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. Identifies the priority of the MaintenanceOrder Indicates the maintenance order that proceeded this order or from which this maintenance order originated after further investigation or work was performed. Identifies when the work to be done in this work order was reported Indicates the date by which a response is expected for this maintenance order Timestamp in which the maintenance order was changed. Indicates the timestamp when the machine failed or broke down such that it was no longer useable. Indicates the Planned TimePeriod in which the maintenance order is planned to be performed. Is the TimePeriod in which the work is Scheduled to be performed. Is the TimePeriod in which the work was actually done. There maybe multiple occurances of this compound if part of the work was completed and the remainder performed at another time. This may happen when a part needs to be ordered. Is the monetary amount budgeted for the MaintenanceOrder. Is the EstimatedAmount of the MaintenanceOrder. Is the ActualAmount of the MaintenanceOrder. Is an estimate as to how long it will take to complete the MaintenanceOrder. Is the total time spent working on the MaintenanceOrder. Is all of the sum of all the occurances of the ActualTimePeriod. Time needed to complete the MaintenanceOrder. Indicates the status of the machine. Is a identifier that describes the specific type of job sequence being performed/requested. Describes the specific type of preventive maintenance sequence being performed/requested. Identifies the maintenance calendar used when scheduling this maintenance order Indicates whether an operation in a maintenance order have to be performed all at once or can be split into non-contiguous work segments. This identifies resources that are required to perform the maintenance operation. Resource Requirements can be specified for the entire maintenance order or for each operation within the order This identifies the actual usage of resources against the requirements estimated for the work order This is the identifier of the Maintenance Operation Is the total time spent working on the MaintenanceOrder. Is all of the sum of all the occurances of the ActualTimePeriod. Time needed to complete the MaintenanceOrder. Is an estimate as to how long it will take to complete the MaintenanceOrder. Is the timestamp that indicates when the MaintenanceOrder was completed. This identifies the actual usage of resources against the requirements estimated for the work order The abstract Header type that is the basis for all non-statusable OAGIS Document Headers The abstract Line type that is the basis for all non-statusable OAGIS Document Lines 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. Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. A distribution identifies how monetary amounts are distributed accross an organization. This identifies the problem that is reported on an asset, equipment, facility or location This is the ID assigned to the document by the creator of the document. Identifies the meter that was measured Is the measurement value of the maintenance operation. Is the timestamp in which the measurement was recorded. 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. TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. This identifies the problem This is a classification or grouping of the failure id into different categories 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. Contains the sequenced identifier for the associated component or noun. 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. Definition of a Hazard Is the identifier of the Hazard This is a grouping of the Hazard Id into different types QDT000000 QDT Response_ Code. Type 1.0 Code Response Identifies the agiven portion of an organization. This identifies the symptoms that are associated with a problem This is the identifier of a symptom This is a grouping of the Symptom id into different types This is a classification or grouping of the failure id into different categories This identifies a possible cause of a particular problem. This is an identifier of a Cause associated with a problem This is a grouping of the failurecause into different types This is a classification or grouping of the failure id into different categories This identifies a Remedy for a specific problem This is the identifier of the Remedy This is a classification or grouping of the failure id into different categories StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Address BaseType provides the information about the address or semantic address of an associated entity. The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. Identifies the precautions to be taken in dealing with a hazard Is the identifier of the Precaution associated in dealing with a Hazard This is a grouping of the Precuation ID into different types QDT000000 QDT State_ Code. Type 1.0 Code State 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 LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. PriceABIEType is logically derived from UN/CEFACT TBG17 ABIE PriceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the basis for Items. 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. 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 Indicates the cost or price of something represented as a value per a number of units. The price of eggs for example would be 1.29 per 1 dozen. PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT Temperature_ Measure. Type 1.0 Measure Temperature DimensionABIEType is logically derived from UN/CEFACT TBG17 ABIE DimensionType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType 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 UpdateMaintenanceOrder is to publish to a business application component or system the need to create or update a Maintenance Order. One possible scenario is the synchronization of Maintenance Order between field devices, service trucks, etc. with a CMMS system. 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. A Maintenance Order is an order for a machine, building, tooling or fixed asset to be repaired or for preventitive maintenance to be performed. 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. Information that generally describes the maintenance order 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. Indicates the priority or urgency of the associated entity. Indicates the maintenance order that proceeded this order or from which this maintenance order originated after further investigation or work was performed. Identifies when the work to be done in this work order was reported Indicates the date by which a response is expected for this maintenance order Indicates when the status change occured. Indicates the timestamp when the machine failed or broke down such that it was no longer useable. Is the TimePeriod in which the work is Scheduled to be performed. The budgeted amount of performing this activity. Is the EstimatedAmount of the MaintenanceOrder. Is the ActualAmount of the MaintenanceOrder. The duration of time estimated for performing an activity The actual duration of time taken for carrying out an activity The dutation of time remaining to carry out an activity Idenitifies a machine. A Facility identifies a location within an entity. The facility may have sub-locators identified using a sequenced identification notation e.g. Warehouse A100 Sub-Location 11, Row R10 would be represented as an array of three Facility elements with values as A100, 11, R10, name attribute as Warehouse, Sub-Location and Row and sequence attribute as 1,2 and 3 respectively. Is a identifier that describes the specific type of job sequence being performed/requested. Describes the specific type of preventive maintenance sequence being performed/requested. Identifies the maintenance calendar used when scheduling this maintenance order Indicates whether an operation in a maintenance order have to be performed all at once or can be split into non-contiguous work segments. Indicates the planner of the Maintenance Order. Is the person supervising/managing the maintenance work being performed/requested. Identifies a project that is associated with the given component. 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. This identifies resources that are required to perform the maintenance operation. Resource Requirements can be specified for the entire maintenance order or for each operation within the order Identifies the safety related information associated with a machine, location or any other entity, or with performing an activity on any of the above entities Information on the problem, possible symptoms that may lead to the problem, and the cause and remedy for the problem. Causes and/or remedies could be reported against a failure in a multi-level hierarchical reporting. For example, failure analysis could be recorded as follows; for failure A, causes P and Q are the factors and remedies X, Y and Z are to be taken. Is the identifier of a specific operation. Possible examples of use are in the Manufacturing Routing or the Maintenance Order. or WorkINProcessOperation. Is the timestamp that indicates when the MaintenanceOrder was completed. The datetime on which the object was last modified The date that document was created within the system of record. Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. 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 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. 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. 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. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. The monetary value of the object in which the amount is associated Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc. Accounting code elements Identifies a Hazard associated with a machine, location or any other entity and/or with performing an activity on any of the above entities 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 revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. Unique Identifier for a meter Identifies the value recorded for the meter at a specific point of time Identifies the timestamp at which an event or measurement is recorded Identifies the person that carried out the measurement 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 fixed asset code of the machine. Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. Identifies the Name of the object in which associated. 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 Indicates the type of the object in which assoicated. This identifies the symptoms that are associated with a problem This identifies a possible cause of a particular problem. This identifies a Remedy for a specific problem Element for the communication of all codes. This is the DateTime the associated object is made effective Identifies the reason for an activity Represents the Properties or Features of the associated entity 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 The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. An explicit period of time for the bucket. Identifies the Item associated with the Line or Detail of a transaction. The item provides the details of the generic Item component information. Identifies the Labour needed for a given task. Is a reference to an associated work-in-process operation. Identifies the tool needed for a given task. Total amount of break time used by all Labour involved with the associated entity. Total time that the associated entity or entities was down during the associated task or operation. Identifies the precautions to be taken to deal with the specific hazard Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. 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 The incremental cost of the resource. The quantity required of the associated entity. The period of time the resource is required. Note: This is inapplicable for an ItemResource. The total cost of this project, as either an entered amount (no activity costing) or calculated as the sum of the activity costs. This field is updated by the LoadProjectAccounting BOD. 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.. Is the tag and information of the new information to be passed. Indicates the time period in which the associated component is effective. 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 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. 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. Identifies if the Item is a Service 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. Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc This is a grouping of similar or equivalent job descriptions A text description of the responsibility of the associated entity. Is the department in which the associated entity belongs within the given organization. Provides a list of category codes that identify the capabilities and features of the associated object. Represents the response to selection criteria that will be used to evaluate the Party. It may also represent capabilities the party offers which are not requested. Examples include quality certifications (ISO-9000), CAD data compatibility (Pro/E), manufacturing operations (JIT), company size, and performance ratings. Provides the information on the skills of the associated component. 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.. Indicates the PerQuantity side of this Amount. Typically, this value is 1 with a uom of each, meaning that, e.g., a UnitPrice with the Amount 1.29 would be the price per each or simply $1.29 each. For pricing wire, the UnitPrice Amount might be $7.00 with a PerQuantity of 100 and a uom of LinearFeet, meaning the unit price would be $7 per 100 linear feet. 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. A value expressing the value of a Sequence. The Calendar year in which the qualification was acheived Inidicates the competency level Last time the employee used this skill. Indicates the dates in which training was received for this skill. 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. 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. 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 This group identifies an entity within an enterprise from both the financial and operational perspective Indicates the ID of the associated component or noun. A group that contains the identifier for the associated component or noun. Contains the Item IDs for an associated item. 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