The purpose of the ProcessInvoice is to transmit an invoice from a supplier to a customer. Indicating that the receiver of the Invoice is to Process the Invoice for payment. Is where the information that the BOD message carries is provided, in this case ProcessInvoice. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Invoice). Is the schema based inheritance for all BODs. The logical model would also include the DataArea. 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. OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. Indicates the version of the given BOD definition. 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. 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. 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. Identifies the intended receiver of the given BOD instance. 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 through 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. 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. Identifies the sender of the given BOD instance 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). 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 IDType_D995CD 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 QDT000000 QDT Response_ Code. Type 1.0 Code Response Allows the user to use any of the codes that OAGi defines or add additional values. The acknowledge values that OAGi defines for OAGIS. 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 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). Identifies the intended receiver of the given BOD instance. Identifies the intended receiver of the given BOD instance. 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. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. B98233 1.0 Number. Type A mathematical number that is assigned or is determined by calculation. Number A mathematical number that is assigned or is determined by calculation. False Integer 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. 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. 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 through 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. The Process verb is used to request processing of the associated noun by the receiving application or business to party. In a typical external exchange scenario a Process BOD is considered to be a legally binding message. For example, if a customer sends a ProcessPurchaseOrder BOD to a supplier and the supplier acknowlegdes with a positive AcknowledgePurchaseOrder, then the customer is obligated to fullfil the agreement, unless of course other BODs are allowed to cancel or change the original order. Identifies with the ActionExpression the level by carrying a value of the expressionLanguage (this is typically XPath) within the BOD that the actionCode is to be performed. The ChangeStatus communicates just that the Change Status. Identifies with the ActionExpression the level by carrying a value of the expressionLanguage (this is typically XPath) within the BOD that the actionCode is to be performed. The ChangeStatus communicates just that the Change Status. 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. Allows the user to use any of the codes that OAGi defines or add additional values. The action values that OAGi defines for OAGIS. 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 through 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. Element for the communication of all codes. This is the DateTime the associated object is made effective Identifies the reason for an activity Element for the communication of all codes. CodeType_1DEB05 QDT000000 QDT Description_ Text. Type 1.0 Text Description 62S0B4 1.0 Text. Type Text is a character string such as a finite set of characters generally in the form of words of a language Text A character string generally in the form of words of a language True String 0..1 Text. Language. Code The language used in the corresponding text string Language Code Text True ISO6392 2008-11-07 5 False This is the DateTime the associated object is made effective Identifies the reason for an activity Indicates when the status change occured. 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 through 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. QDT000000 QDT State_ Code. Type 1.0 Code State Indicates when the status change occured. Common Free Form Text elements that occur together. 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. CVW231 1.0 Indicator. Type An indicator is a list of two mutually exclusive Boolean values that express the only possible states of a property Indicator The value of the indicator True Boolean The Invoice is used to invoice a customer for goods/services the have been provided. Information that applies to the entire invoice document. The Header supports summary amounts for line items, charges, taxes and allowances. It also supports itemizing Header level charges, taxes and allowances for use in credit or debit invoices. In this case Line items are not needed. The summary amounts in the Header include the Line level amounts and Header level amounts. In general an Invoice Line can be aligned with Order Lines. The ItemQuantity and Price are used to compute the Total. The Total is a sum of the Total and any Charges, Taxes or Allowances. Information that applies to the entire invoice document. The Header supports summary amounts for line items, charges, taxes and allowances. It also supports itemizing Header level charges, taxes and allowances for use in credit or debit invoices. In this case Line items are not needed. The summary amounts in the Header include the Line level amounts and Header level amounts. The InvoiceHeader type supports summary amounts for line items, charges and allowances. Indicates the type of the object in which assoicated. Is an amount not including taxes or charges. In the case of orders, this is typically the Unit Price times the Order Quantity. Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes. Identifies the supplier organization/entity of the items or inventory for the associated transaction. In most cases there is one SupplierParty per transaction. i.e. one SupplierParty for a given PurchaseOrder. However in the cases where an transaction Broker is involved there are cases where a single transaction may have different SupplierParties at the line level or in the case of a Catalog for the Catalog. Is the organization that is the end customer of the goods or services being provided in the associated transaction. Identifies the party or location that the payment is to be remitted to or sent to. 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 Idenitfies the party that serves as the carrier of the goods or services for the transaction. Identifies the party that the bill or invoice is to be sent. In most cases this is the same as the CustomerParty however there are many cases where the CustomerParty and the BillToParty will be different. Identifies the party that the goods or services are being shipped or sent from. 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. Identifies the reason for an activity Is a reference to a PurchaseOrder Is a reference to a contract Identifies the payment term for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays. Indicates the tax for the object associated. 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. Represents the different Charges that may be applied to the associated document. Identifies the discount or allowance that the Customer is to receive off of the TotalAmount owed as a result of the associated document or sub-portion of a document. 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 qualifying component (Prepaid and Add). 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 through 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 status of the associated object by providing the Status Code along with a description and when the status is effective. The abstract Header type that is the basis for all non-statusable OAGIS Document Headers The datetime on which the object was last modified The date that document was created within the system of record. 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. Is the primary document id for the document associated. Is the alternate document id for the associated document. Is the primary document id for the document associated. This is the ID assigned to the document by the creator of the document. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID 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. Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. Is the alternate document id for the associated document. The datetime on which the object was last modified The date that document was created within the system of record. Common References to DocumentReferences and Attachements 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 Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. The Item identifiers that uniquily identify a given item. These identifiers may be specific to the party in which they make reference. 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 the Lot and Setial numbers for the items contained in the associated component by identifing the number of items and the uniques serial number of those items that belong to a given Lot. Is a reference to a SalesOrder Is a reference to a PurchaseOrder 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 organization/entity that issued/ created the document Is reference to a ProductionOrder Reference to a Routing. Is a reference to an associated work-in-process operation. Identifies the Release Number in the case of Blanket POs 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. Indicates the time period in which the associated component is effective. Identifies the Item associated with the Line or Detail of a transaction. The item provides the details of the generic Item component information. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. 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. The quantity of product requested. Total number of line items. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes. An indicator specifying a requirement for a document reference. Specifies effectivity of an associated object. Effectivity is expressed may be expressed as: multiple ranges, values, time period or as associated to a specific Item. 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 through 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. StatusCode is being deprecated in favor of the Status as of 9.1. The date that document was created within the system of record. Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. 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 through 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. StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicates the type of the object in which assoicated. An explicit period of time for the bucket. Indicates the type of the object in which assoicated. An explicit period of time for the bucket. Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The InclusiveIndicator element is used to identify whether the SearchValue should be an included or excluded component of the result set. For example, if a user was looking for ballpoint pens, but NOT red ballpoint pens, the transaction would contain two instances of the SearchTerm data type one containing a SearchValue of ‘Ballpoint’ and an SearchValueInclusive of 'Inclusive' and one containing a SearchValue of ‘Red’ and an SearchValueInclusive of 'Exclusive' 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. The InclusiveIndicator element is used to identify whether the SearchValue should be an included or excluded component of the result set. For example, if a user was looking for ballpoint pens, but NOT red ballpoint pens, the transaction would contain two instances of the SearchTerm data type one containing a SearchValue of ‘Ballpoint’ and an SearchValueInclusive of 'Inclusive' and one containing a SearchValue of ‘Red’ and an SearchValueInclusive of 'Exclusive' 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. JJ5401 1.0 Duration. Type A duration is the specification of a length of time without a fixed start or end time, expressed in Gregorian calendar time units (Year, Month, Week, Day) and Hours, Minutes or Second The particular representation of duration True TimeDuration ISO 8601 format: nW Is the ending timestamp of the event. Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. The Item identifiers that uniquily identify a given item. These identifiers may be specific to the party in which they make reference. Contains the Item IDs for an associated item. 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. 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 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. 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 through 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. Identifies the Name of the object in which associated. Contains the sequenced identifier for the associated component or noun. Indicates the ID of the associated component or noun. Identifies the Name of the object in which associated. NameType_02FC2Z When a Name occurs multiple times, this sequence integer can be used to provide the order in which the Names are meaningful. 02FC2Z 1.0 Name. Type A name is a word or phrase that constitutes the distinctive designation of a person, place, thing or concept Name A word or phrase that represents a designation of a person, place, thing or concept True String 0..1 Name. Language. Code The language used in the corresponding text string Language Code Name True ISO6392 2008-11-07 5 False BE4776 1.0 Number. Type A mathematical number that is assigned or is determined by calculation. Number A mathematical number that is assigned or is determined by calculation. True Decimal 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 through 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. Address BaseType provides the information about the address or semantic address of an associated entity. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. 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 name attribute identifies the name 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. Indicates the status of the associated object by providing the Status Code along with a description and when the status 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. Element for the communication of all codes. 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. 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 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 name attribute identifies the name 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 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 Country in which the Address is in. A possible list of values is as specified in ISO 3166-2. QDT000000 QDT Country_ Code. Type 1.0 Code Country Postal Code of the Address. 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 through 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. PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. A value expressing the value of a Sequence. Indicates the time period in which the associated component is effective. A value expressing the value of a Sequence. Indicates the time period in which the associated component is effective. 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 through 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. The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. 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. 201230 1.0 Measure. Type A measure is a numeric value determined by measuring an object along with the specified unit of measure Measure The numeric value determined by measuring an object True Decimal 0..1 Measure. Unit. Code The unit of measure Unit Code Code True Recommendation20 6 6 False 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. Is the Lot and Setial numbers for the items contained in the associated component by identifing the number of items and the uniques serial number of those items that belong to a given Lot. Is used to describe the quantity of item's, products or resources being budgeted, produced, purchased, received, sold, or used. Identifies the Lot that a given Item Instance belongs to. Indicates whether an item is active, inactive, or in other various states. Examples of values for this field include: Active, Inactive, Hold, Deleted, Obsolete Unique serial number assigned to the given item instance by the manufacturer. Is the parent's serial number of the given item. This allows the traking of serialized components of an assembly. 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 through 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. Is used to describe the quantity of item's, products or resources being budgeted, produced, purchased, received, sold, or used. 201230 1.0 Quantity. Type A quantity is a counted number of non-monetary units, possibly including fractions Quantity A counted number of non-monetary units possibly including fractions True Decimal 0..1 Quantity. Unit. Code The unit of measure Unit Code Code True Recommendation20 6 6 False Identifies the Lot that a given Item Instance belongs to. Identifies the Lot Identifiers of all of the lots that are contained in the associated set of items. Indicates the time period in which the associated component is effective. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. Unique serial number assigned to the given item instance by the manufacturer. Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. Indicates whether an item is active, inactive, or in other various states. Examples of values for this field include: Active, Inactive, Hold, Deleted, Obsolete 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 through 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. Identifies the Lot Identifiers of all of the lots that are contained in the associated set of items. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. Unique serial number assigned to the given item instance by the manufacturer. Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. Indicates whether an item is active, inactive, or in other various states. Examples of values for this field include: Active, Inactive, Hold, Deleted, Obsolete Is the parent's serial number of the given item. This allows the traking of serialized components of an assembly. Is a reference to a SalesOrder 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. Is the quantity of a material or product ordered by the customer. 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 through 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. Identifies the Release Number in the case of Blanket POs 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. Is the quantity of a material or product ordered by the customer. Is a reference to a PurchaseOrder 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 organization/entity that issued/ created the document 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 through 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. Contains the set of possible identifiers for an associated Party. Identifier of the account 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. Contains the set of possible identifiers for an associated Party. Contain the ids for a given party. These ids may be assigned by multiple organizations. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. 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 Commercial and Government Entity (CAGE) code is a five-character ID number used extensively within the Department of Defense to identify specific companies. DoDAAC (Dept. of Defense Activity Address Code) is a unique six-position, alphanumeric string that uniquely identifies departments, locations, units, and so on within the military. This identifier serves the same purpose as a company The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. The Standard Carrier Alpha Code, a two-to-four digit identification, is used by (in the United States) transportation industry to identify freight carriers in computer systems and shipping documents such as Bill of Lading, Freight Bill, Packing List, and Purchase Order. 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 Commercial and Government Entity (CAGE) code is a five-character ID number used extensively within the Department of Defense to identify specific companies. DoDAAC (Dept. of Defense Activity Address Code) is a unique six-position, alphanumeric string that uniquely identifies departments, locations, units, and so on within the military. This identifier serves the same purpose as a company The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. The Standard Carrier Alpha Code, a two-to-four digit identification, is used by (in the United States) transportation industry to identify freight carriers in computer systems and shipping documents such as Bill of Lading, Freight Bill, Packing List, and Purchase Order. Identifier of the account The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. 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 through 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. 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 Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. Identifies the Name of the object in which associated. 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. 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. ** deprecated ** OAGi deprecated all type attributes effective in OAGIS 9.5 release. All complexTypes that have the type attribute has a Type element that is to be used instead. 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 through 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. ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. Identifies the Name of the object in which associated. 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 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. 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 through 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. CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. 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. 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. 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. 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 through 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. Code identifying the usage of the contact point e.g. business, private, etc. An identifier that identifies an electronic mail address. Indicates that the associated entity preferrs HTML format. 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 through 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. An identifier that identifies an electronic mail address. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Code identifying the usage of the contact point e.g. business, private, etc. 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 through 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. UTC+01:00 Azores UTC-02:00 UTC-03:00 Brazil East Greenland St Pierre and Miquelon Newfoundland UTC-04:00 Brazil West Chile Western Greenland Paraguay Atlantic Time (Halifax) UTC-05:00 Brazil Andes Cuba Eastern Time (New York) UTC-06:00 Chile Easter Island Central Time (Dallas) UTC-07:00 Mountain Time (Denver) UTC-08:00 Pacific Time (Los Angeles) UTC-08:30 UTC-09:00 Alaska (Anchorage) UTC-10:00 Hawaii / Alaska (Aleutian) UTC-11:00 UTC-12:00 UTC Western Europe UTC+01:00 Central Europe Namibia UTC+02:00 Egypt Eastern Europe Israel Jordan Syria UTC+03:00 Russia (Moscow) Iraq Iran UTC+04:00 Russia (UTC+04) UTC+04:30 UTC+05:00 Russia (UTC+05) UTC+05:30 UTC+05:45 UTC+06:00 Russia (UTC+06) UTC+06:30 UTC+07:00 Russia (UTC+07) UTC+08:00 Russia (UTC+08) UTC+09:00 Russia (UTC+09) UTC+09:30 Australia South Australia UTC+10:00 Australia Capital Territories Australia Lord Howe Island Russia (UTC+10) UTC+11:00 Russia (UTC+11) UTC+12:00 Russia (UTC+12) New Zealand New Zealand Chatham Islands UTC+13:00 Russia (UTC+13) UTC+14:00 This list of Party Categories. Is reference to a ProductionOrder Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. The Item identifiers that uniquily identify a given item. These identifiers may be specific to the party in which they make reference. 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 the Lot and Setial numbers for the items contained in the associated component by identifing the number of items and the uniques serial number of those items that belong to a given Lot. Is a reference to a SalesOrder Is a reference to a PurchaseOrder 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 through 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. Reference to a Routing. Is reference to a ProductionOrder Is a reference to an associated work-in-process operation. 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 through 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. Is a reference to an associated work-in-process operation. 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 through 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. 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.. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. 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. 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 through 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. Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. 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. Identifies the Item associated with the Line or Detail of a transaction. The item provides the details of the generic Item component information. Represents the identifier of the country of origin of an item, service or shipment 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 the Lot that a given Item Instance belongs to. 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 through 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. Is the basis for Items. 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. Provides the dimensions of the associated component. 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 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 through 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. 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 Indicates the type of the object in which assoicated. Identifies the specification of an entity. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. Represents the Properties or Features of the associated entity 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 through 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. Represents the Properties or Features of the associated entity Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Is the tag and information of the new information to be passed. Specifies effectivity of an associated object. Effectivity is expressed may be expressed as: multiple ranges, values, time period or as associated to a specific Item. Indicates the time period in which the associated component is effective. 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 through 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. Is the tag and information of the new information to be passed. 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. Specifies effectivity of an associated object. Effectivity is expressed may be expressed as: multiple ranges, values, time period or as associated to a specific Item. Indicates the type of the object in which assoicated. Identifies the Name of the object in which associated. Expresses effectivity as a list of discrete values with no relationship between the values. Additional sequence value can be defined to prioritize the order in which the values are evalued during processing Expresses effectivity as a range of ordered values, such as a range of serial numbers or lot numbers. The absence of a Start identifier indicates the item is effective to all referenced items whose sequence identifier precedes the End Value. The absence of an End identifier indicates the item is effective to all referenced items whose sequence identifier succeeds the Start Value. Multiple ranges are possible, they may be contiguous or disjoint. Indicates the time period in which the associated component is effective. Expresses effectivity as a list of discrete values with no relationship between the values. Additional sequence value can be defined to prioritize the order in which the values are evalued during processing The InclusiveIndicator element is used to identify whether the SearchValue should be an included or excluded component of the result set. For example, if a user was looking for ballpoint pens, but NOT red ballpoint pens, the transaction would contain two instances of the SearchTerm data type one containing a SearchValue of ‘Ballpoint’ and an SearchValueInclusive of 'Inclusive' and one containing a SearchValue of ‘Red’ and an SearchValueInclusive of 'Exclusive' Expresses effectivity as a range of ordered values, such as a range of serial numbers or lot numbers. The absence of a Start identifier indicates the item is effective to all referenced items whose sequence identifier precedes the End Value. The absence of an End identifier indicates the item is effective to all referenced items whose sequence identifier succeeds the Start Value. Multiple ranges are possible, they may be contiguous or disjoint. The InclusiveIndicator element is used to identify whether the SearchValue should be an included or excluded component of the result set. For example, if a user was looking for ballpoint pens, but NOT red ballpoint pens, the transaction would contain two instances of the SearchTerm data type one containing a SearchValue of ‘Ballpoint’ and an SearchValueInclusive of 'Inclusive' and one containing a SearchValue of ‘Red’ and an SearchValueInclusive of 'Exclusive' A numeric specifying a count of identifiers in a range. A numeric specifying a count of identifiers in a range. Provides the Hazardous Material Code and description. 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 through 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. HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. 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. 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.. TemperatureMeasureType is logically derived from UN/CEFACT TBG17 ABIE TemperatureType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The primary entry route by which the Hazardous Material gains access to the human body. Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. 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 through 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 type of the object in which assoicated. 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. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Provides the dimensions of the associated component. An indicator specifying random sizes in the dimensions. 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 through 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. DimensionABIEType is logically derived from UN/CEFACT TBG17 ABIE DimensionType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicates the type of the object in which assoicated. Indicates the width of an object Indicates the length of an object Indicates the Height of an object Indicates the width of an object Indicates the length of an object Indicates the Height of an object An indicator specifying random sizes in the dimensions. A measure specifying the under size of a dimension. A measure specifying the over size of a dimension. A measure specifying the under size of a dimension. A measure specifying the over size of a dimension. 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. Represents the identifier of the country of origin of an item, service or shipment The quantity of product requested. Total number of line items. Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes. 0723C8 1.0 Amount. Type An amount is a number of monetary units specified in a currency Amount A number of monetary units Decimal True 0..1 Amount. Currency. Code The currency of the amount Currency Code Amount True 42173A 2009-03-05 5 True Dirham Afghani Lek Dram Netherlands Antillian Guilder Kwanza Argentine Peso Australian Dollar Aruban Guilder Azerbaijanian Manat Convertible Mark Barbados Dollar Taka Bulgarian Lev Bahraini Dinar Burundi Franc Bermudian Dollar (customarily: Bermuda Dollar) Brunei Dollar Boliviano Brazilian Real Bahamian Dollar Ngultrum Pula Belarussian Ruble Belize Dollar Canadian Dollar Franc Congolais Swiss Franc Chilean Peso Yuan Renminbi Colombian Peso Costa Rican Colon Cuban Peso Cape Verde Escudo Cyprus Pound Czech Koruna Djibouti Franc Danish Krone Dominican Peso Algerian Dinar Kroon Egyptian Pound Nakfa Ethopian Birr Euro Fiji Dollar Falkland Islands Pound Pound Sterling Lari Cedi Gibraltar Pound Dalasi Guinea Franc Quetzal Guyana Dollar Honk Kong Dollar Lempira Kuna Gourde Forint Rupiah New Israeli Sheqel Indian Rupee Iraqi Dinar Iranian Rial Iceland Krona Jamaican Dollar Jordanian Dinar Yen Kenyan Shilling Som Riel Comoro Franc North Korean Won Won Kuwaiti Dinar Cayman Islands Dollar Tenge Kip Lebanese Pound Sri Lanka Rupee Liberian Dollar Loti Lithuanian Litas Latvian Lats Libyan Dinar Morrocan Dirham Moldovan Leu Malagasy Franc Denar Kyat Tugrik Pataca Ouguiya Maltese Lira Mauritius Rupee Rufiyaa Kwacha Mexican Peso Malaysian Ringgit Metical Namibia Dollar Naira Cordoba Oro Norwegian Krone Nepalese Rupee New Zealand Dollar Rial Omani Balboa Nuevo Sol Kina Philippine Peso Pakistan Rupee Zloty Guarani Qatari Rial Leu New Leu Russian Ruble Rwanda Franc Saudi Riyal Solomon Islands Dollar Seychelles Rupee Sudanese Dinar Swedish Krona Singapore Dollar St. Helena Pound Tolar Slovak Koruna Leone Somali Shilling Suriname Guilder Dobra El Salvador Colon Syrian Pound Lilangeni Baht Somoni Manat Tunisian Dinar Pa'anga Turkish Lira Turkish Lira Trinidad and Tobago Dollar New Taiwan Dollar Tanzanian Shilling Hryvnia Uganda Shilling US Dollar Peso Uruguayo Uzbekistan Sum Bolivar Bolivar Fuerte Dong Vatu Tala CFA Franc Silver Gold East Carribean Dollar SDR CFA Franc Palladium CFP Franc Platinum Yemeni Rial New Dinar Rand Kwacha Zimbabwe Dollar An indicator specifying a requirement for a document reference. 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. Indicates the type of the object in which assoicated. 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 through 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. Allows the data to be embedded directly into the BOD instance. Allows a reference to an ISBN. Indicates the name of the File being referenced. The date that document was created within the system of record. 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.. Allows the data to be embedded directly into the BOD instance. Allows a reference to an ISBN. Indicates the name of the File being referenced. 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 an amount not including taxes or charges. In the case of orders, this is typically the Unit Price times the Order Quantity. Indicates the type of the object in which assoicated. Indicates an amount of discount that is available against a price The monetary value of the object in which the amount is associated Identifies the percentage of the Line Price applicable to the distribution line. This is used to derive the Amount on the distribution line. Indicates an amount of discount that is available against a price The monetary value of the object in which the amount is associated Identifies the percentage of the Line Price applicable to the distribution line. This is used to derive the Amount on the distribution line. 481002 1.0 Percent. Type A percent is a value representing a fraction of one hundred, expressed as a quotient Percent Numeric information that is assigned or is determined by percent True Decimal Identifies the supplier organization/entity of the items or inventory for the associated transaction. In most cases there is one SupplierParty per transaction. i.e. one SupplierParty for a given PurchaseOrder. However in the cases where an transaction Broker is involved there are cases where a single transaction may have different SupplierParties at the line level or in the case of a Catalog for the Catalog. Identifies the sales contact and sales department/organization that is responsible for the sale that the instance is associated. Identifies the contact information of the person, organization, department, or group that is to shipping the contents communicated by the document or line. Identifies the contact information of the person, organization, department, or group that is responsible for customer service. 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 through 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. Identifies the sales contact and sales department/organization that is responsible for the sale that the instance is associated. Identifies the contact information of the person, organization, department, or group that is to shipping the contents communicated by the document or line. Identifies the contact information of the person, organization, department, or group that is responsible for customer service. Is the organization that is the end customer of the goods or services being provided in the associated transaction. Identifies the contact information for the requesting person, organization, department, or group on the associated document or line. Identifies the contact information of the person, organization, department, or group that planned for the timing of the exchange of goods/services that this document is associated at the document or line level. Identifies the contact information for the buying person, organization, department, or group on the associated document or line. Identifies the contact information of the person, organization, department, or group that is to receive the contents communicated by the document or line. 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 through 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 is the Account Identification assigned to the customer (Payer) by the Supplier (Payee) This is the Account Identification assigned to the customer (Payer) by the Supplier (Payee) Identifies the contact information for the requesting person, organization, department, or group on the associated document or line. Identifies the contact information of the person, organization, department, or group that planned for the timing of the exchange of goods/services that this document is associated at the document or line level. Identifies the contact information for the buying person, organization, department, or group on the associated document or line. Identifies the contact information of the person, organization, department, or group that is to receive the contents communicated by the document or line. Identifies the party or location that the payment is to be remitted to or sent to. Provides bank account details. 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 through 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. Provides bank account details. Specifies the currency code of the object in which it is associated. Identifies the Name of the object in which associated. Indicates the type of the object in which assoicated. 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 through 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. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Associated account of the associated entity. Associated account of the associated entity. Specifies the currency code of the object in which it is associated. QDT000000 QDT Currency_ Code. Type 1.0 Code Currency 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 An indicator specifying an appointment is required. 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 through 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. An indicator specifying an appointment is required. Idenitfies the party that serves as the carrier of the goods or services for the transaction. Identifies the party that the bill or invoice is to be sent. In most cases this is the same as the CustomerParty however there are many cases where the CustomerParty and the BillToParty will be different. Identifies the party that the goods or services are being shipped or sent from. 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. 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 through 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 list is the agreed to Party Roles. Is a reference to a contract Identifies the payment term for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays. Indicates the code type of payment terms. Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment. Identifies the Discount the time and number of payments and the amount or percentage of the discount from the payment. Identifies the Peanlty what happen when the time and number of payments and the amount or percentage of the penalty to add to the payment. 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 through 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 code type of payment terms. QDT000000 QDT Payment Term_ Code. Type 1.0 Code Payment Term Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment. If Billing Date is March 15, and the payment is due by April 21. The ProxMonth would be 1 and the ProxDayOfMonth would be 21. The number of months beyond the Billing Date in which payment is due. The daywithin the ProxMonth beyond the Billing Date in which payment is due. 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 through 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. TermsABIEType is logically derived from UN/CEFACT TBG17 ABIE PaymentTermsType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. This is the DateTime the associated object is made effective The date and time that the production order is to be completed. The date and time when the payment terms go into effect. Used in conjunction with NumberOfDays 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. Indicates a percentage of discount that is available against a price The penalty rate (percentage) charged for late payment. The monetary value of the object in which the amount is associated The date and time that the production order is to be completed. The date and time when the payment terms go into effect. Used in conjunction with NumberOfDays QDT000000 QDT Payment Basis_ Code. Type 1.0 Code Payment Basis This list is the agreed to sub set of Payment Term Basis Codes from X12 Element 333. Indicates a percentage of discount that is available against a price The penalty rate (percentage) charged for late payment. The number of months beyond the Billing Date in which payment is due. The daywithin the ProxMonth beyond the Billing Date in which payment is due. ISO 8601 format: ---DD Identifies the Discount the time and number of payments and the amount or percentage of the discount from the payment. Identifies the Peanlty what happen when the time and number of payments and the amount or percentage of the penalty to add to the payment. The monetary value of the object in which the amount is associated 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 through 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. Credit Card account information. Electronic Funds Transfer information Is a reference to a PurchaseOrder Identifies the cheque number. 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 through 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. The bank account routing number. The name of the bank. Indicates the type of the object in which assoicated. Account Number, depending upon the context used this may be the credit card number of the checking account number, etc. Indicates the name on the account, in the case of a credit card the name exactly as it appears on the credit card. Account Number, depending upon the context used this may be the credit card number of the checking account number, etc. Indicates the name on the account, in the case of a credit card the name exactly as it appears on the credit card. The bank account routing number. The name of the bank. Identifies the cheque number. Credit Card account information. CardCode or Card Id field that can be optionally provided to use additional security features of credit card authorization. It is typically a 3 digit number located on the back of most credit cards. For American Express, it is a 4 digit number on the front. 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 through 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 expiration month and year of the credit card. Company name on the credit card. If the method of payment was authorized (credit Card or EFT), this is the authorization information that was passed back from the 3rd party. Indicates the expiration month and year of the credit card. Expiration month on Card. Is the financial year in which this accounting period occurs. Generally a period of 12 months for which the company regularly has to create financial statements Expiration month on Card. ISO 8601 format: --MM-- Is the financial year in which this accounting period occurs. Generally a period of 12 months for which the company regularly has to create financial statements ISO 8601 format: YYYY Company name on the credit card. If the method of payment was authorized (credit Card or EFT), this is the authorization information that was passed back from the 3rd party. 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 through 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. The unique number assigned to the authorization transaction in the back office. This number must be re-used when placing the order for reference purposes. The revenue source to be used in the payment authorization. In some instance this field indicates the division. Identifies the Bank in which the PaymentAuthorization needs is to send the money. AuthorizationABIEType is based on UN/CEFACT TBG17 ABIE AuthorizationType which is found in the RUABIE file. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. The response code of the payment authorization (for either credit cards or EFT). The date and time of the payment authorization. The monetary value of the object in which the amount is associated The response code of the payment authorization (for either credit cards or EFT). The date and time of the payment authorization. 1A9053 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year, week, day Date The particular point in the progression of date True TimePoint 30CB24 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: century Date The particular point in the progression of date True TimePoint ISO 8601 format: CC FX0L23 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year, month, week, day Date The particular point in the progression of date True TimePoint ISO 8601 format: YYYY-MM-DD 37D62E 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: week, day of week Date The particular point in the progression of date True TimePoint ISO 8601 format: -W-D D46DBA 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: day of year Date The particular point in the progression of date True TimePoint ISO 8601 format: -DDD DB95C8 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: day of month Date The particular point in the progression of date True TimePoint 5B057B 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: month, day Date The particular point in the progression of date True TimePoint ISO 8601 format: --MM-DD 0C267D 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: month Date The particular point in the progression of date True TimePoint 2841F8 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: week Date The particular point in the progression of date True TimePoint ISO 8601 format: -Www 4A071E 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: week, day of week Date The particular point in the progression of date True TimePoint ISO 8601 format: -Www-D B950EA 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year, day of year Date The particular point in the progression of date True TimePoint ISO 8601 format: YYYY-DDD BBCC14 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year, month Date The particular point in the progression of date True TimePoint ISO 8601 format: YYYY-MM 57D5E1 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year Date The particular point in the progression of date True TimePoint 3B6616 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year, week Date The particular point in the progression of date True TimePoint ISO 8601 format: YYYY-Www 1A9053 1.0 Date. Type A date is a gregorian calendar representation in various common resolutions: year, week, day Date The particular point in the progression of date True TimePoint ISO 8601 format: YYYY-Www-D The unique number assigned to the authorization transaction in the back office. This number must be re-used when placing the order for reference purposes. The revenue source to be used in the payment authorization. In some instance this field indicates the division. Identifies the Bank in which the PaymentAuthorization needs is to send the money. CardCode or Card Id field that can be optionally provided to use additional security features of credit card authorization. It is typically a 3 digit number located on the back of most credit cards. For American Express, it is a 4 digit number on the front. 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 through 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. Electronic Funds Transfer information Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. 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 through 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 tax for the object associated. 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 through 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. TaxABIEType is logically derived from UN/CEFACT TBG17 ABIE TaxType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. Is the base amount from which the charge/allowance is derived. Is the base quantityfrom which the charge/allowance is derived. Allows the sender to indicate how the Charge/Allowance was calculated. This is used to represent the tax amount in the currency of the taxing authority in addition to the transactional tax amount which may be in a different currency. The monetary value of the object in which the amount is associated Identifies the exchange rate between two currencies. For the transaction in which this is associated. Is the base amount from which the charge/allowance is derived. Is the base quantityfrom which the charge/allowance is derived. Allows the sender to indicate how the Charge/Allowance was calculated. 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 through 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. 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. 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. 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. Uniquely identifies the exemption along with the agency that defines the excemption. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. The monetary value of the object in which the amount is associated 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 through 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 is used to represent the tax amount in the currency of the taxing authority in addition to the transactional tax amount which may be in a different currency. Identifies the exchange rate between two currencies. For the transaction in which this is associated. Identifies the exchange rate between two currencies 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 through 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. 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. Indicates the type of the object in which assoicated. Idenfifies the source that brought the associated entity. Indicates the time period in which the associated component is effective. CurrencyExchangeABIEType is logically derived from UN/CEFACT TBG17 ABIE CurrencyExchangeType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. 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. 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. Identifies the date in which the conversion factor was set by the Issueing agency. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. 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. Idenfifies the source that brought the associated entity. 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. 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 through 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. AllowanceChargeABIEType is based on the UN/CEFACT TBG17 AllowanceChargeType that can be found the Reusable Aggregate Business Information Entity (RUABIE) XML Schema files. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. Indicates the type of the object in which assoicated. 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. An explicit period of time for the bucket. 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. A distribution identifies how monetary amounts are distributed accross an organization. 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 project that is associated with the given component. 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 through 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. Identifies the financial ledger to be used when updating balances Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc. Accounting code elements This group identifies an entity within an enterprise from both the financial and operational perspective 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 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 Identifies the agiven portion of an organization. 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 Accounting code elements 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 through 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. 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 Identifies a project that is associated with the given component. 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. 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 through 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. ProjectABIEType is logically derived from UN/CEFACT TBG17 ABIE ProjectType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicates the type of the object in which assoicated. The monetary value of the object in which the amount is associated 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. A group that contains the identifier for the associated component or noun. Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier. 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. 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. 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 through 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. Represents the different Charges that may be applied to the associated document. 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 through 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. Identifies the discount or allowance that the Customer is to receive off of the TotalAmount owed as a result of the associated document or sub-portion of a document. 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 through 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. 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 qualifying component (Prepaid and Add). 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). 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 2010) for use in international trade. (See http://www.unece.org/cefact/recommendations/rec_index.htm). These terms may also be found in the United States Uniform Commercial Code (UCC). EXAMPLES General transport EXW - Ex Works ... (named place) FCA - Free Carrier ... (named place) CPT - Carriage Paid ... (named place of destination) CIP - Carriage and Insurance Paid To ... (named place of destination) DAT - Delivered at Terminal DAP - Delivered at Place ... (named place of destination) DDP - Delivered Duty Paid ... (destination place) Water transportation 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) Identifies the place where the transfer of ownership takes place. Is a generic code that specifies a particular type or quality of carrier delivery service to be used for transporting goods. A generic service level code is often established by shippers to consolidate various equivalent, but differently named, carrier service levels for comparison when "rate shopping" for the lowest cost transportation provider. See CarrierServiceLevel for specifying the carrier's actual service level code. Describes how the freight cost for a shipment of goods should be billed. EXAMPLES: Prepaid, Collect, Third Party, Prepaid and Add, Consignee Billed An indicator specifying a geographic locations basis of a freight charge. 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 2010) for use in international trade. (See http://www.unece.org/cefact/recommendations/rec_index.htm). These terms may also be found in the United States Uniform Commercial Code (UCC). EXAMPLES General transport EXW - Ex Works ... (named place) FCA - Free Carrier ... (named place) CPT - Carriage Paid ... (named place of destination) CIP - Carriage and Insurance Paid To ... (named place of destination) DAT - Delivered at Terminal DAP - Delivered at Place ... (named place of destination) DDP - Delivered Duty Paid ... (destination place) Water transportation 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) QDT000000 QDT Incoterms_ Code. Type 1.0 Code Incoterms Identifies the place where the transfer of ownership takes place. Is a generic code that specifies a particular type or quality of carrier delivery service to be used for transporting goods. A generic service level code is often established by shippers to consolidate various equivalent, but differently named, carrier service levels for comparison when "rate shopping" for the lowest cost transportation provider. See CarrierServiceLevel for specifying the carrier's actual service level code. Describes how the freight cost for a shipment of goods should be billed. EXAMPLES: Prepaid, Collect, Third Party, Prepaid and Add, Consignee Billed QDT000000 QDT Freight Terms_ Code. Type 1.0 Code Freight Terms An indicator specifying a geographic locations basis of a freight charge. 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. 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. 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. 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 through 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. In general an Invoice Line can be aligned with Order Lines. The ItemQuantity and Price are used to compute the Total. The Total is a sum of the Total and any Charges, Taxes or Allowances. The InvoiceLine type supports order line invoicing. Idenitfies the party that serves as the carrier of the goods or services for the transaction. 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 Identifies the party that the goods or services are being shipped or sent from. Identifies the party that the bill or invoice is to be sent. In most cases this is the same as the CustomerParty however there are many cases where the CustomerParty and the BillToParty will be different. 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). Is a SubLine of the InvoiceLine in order to provide a finer grained breakdown of the items being invoiced. 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 through 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. 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 quantity of the associated service or item that is addresses by the component in which the quantity is associated. Unit price of the item for the number of items in the unitCode specified in the PerQuantity elements. In most cases the unitCode of the PerQuantity is the same as the unitCode of the Quantity element above. Is a reference to a PurchaseOrder 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. Is a reference to a contract Is an amount not including taxes or charges. In the case of orders, this is typically the Unit Price times the Order Quantity. Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes. Indicates that the line is an open item and is not to be included in the document total. Indicates the tax for the object associated. 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. A datetime specifying a goods receipt. A datetime specifying a services receipt. Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. The abstract Line type that is the basis for all non-statusable OAGIS Document Lines Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. Unit price of the item for the number of items in the unitCode specified in the PerQuantity elements. In most cases the unitCode of the PerQuantity is the same as the unitCode of the Quantity element above. PriceABIEType is logically derived from UN/CEFACT TBG17 ABIE PriceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Element for the communication of all codes. An explicit period of time for the bucket. 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. The monetary value of the object in which the amount is associated 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. 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. Indicates that the line is an open item and is not to be included in the document total. Indicates the tax for the object associated. 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. 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 through 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 datetime specifying a goods receipt. A datetime specifying a services receipt. Is a SubLine of the InvoiceLine in order to provide a finer grained breakdown of the items being invoiced. 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 through 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. 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 through 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 type of the object in which assoicated. 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 through 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.