A copy of the ApplicationArea for the original BOD that was processed. Present either as additional reference information, or for use in identifying the BOD in situations where a BODReference is not known. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A freeform note The processing of the BOD has failed. Provides a list of error and warning messages that explain the failure. Specific outcomes of processing each noun are reported in each of the NounOutcome elements The processing of the BOD was a success. Possible, non-fatal warning messages may appear here. Specific outcomes of processing each noun are reported in each of the NounOutcome elements. The processing of at least one noun in the BOD has failed. Error and warning messages may explain the failure. Specific outcomes of processing each noun are reported in each of the NounOutcome elements. Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS. Indicates the current state of the associated object. Identifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD. is the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document. 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. 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 Identifies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized by the receiving system indicates what can be done on the receiving system(s). When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. This attribute contains the Code List ID for the codes that are associated with corresponding entity. This is required for language codes other than ""en-us"" when the element that includes this attribute is used. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. This is required for language codes other than ""en-us"" when the element that includes this attribute is used. An optional identifier, that when used can uniquely identify each instance of a note within a BOD. It is only unique within the context of where it is used in the document. Indicates if the note should be published externally or if it is for internal use only. It may have the values ''Internal'' and ''External''. Person who created the note Entry date and time in GMT. Status of a note. Indicates what type of note is being specified and is associated to an Infor defined code list, ''Note Types,'' This is required for language codes other than ""en-us"" when the element that includes this attribute is used. Error message encountered during processing. Non-fatal warning message encountered during processing Indicates that the processing of this noun has failed, and provides error and warning messages that arose during the processing of the noun. Indicates that the processing of this noun has succeeded; may provide non-fatal warning messages that arose during the processing of the noun. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A freeform note Indicates the type of the object in which assoicated. Identifies the reason for an activity When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. The location that is associated with the maintenance of this instance of the noun. This attribute must not be included on the ID of objects that are maintained at the tenant or accounting entity level. The number of times this object has been published with these attributes for the accounting entity and location. The LID of the system where the object can be maintained. This can be used by BIS to help automate the drill back process. This attribute contains the Code List ID for the codes that are associated with corresponding entity. This attribute contains the Code List ID for the codes that are associated with corresponding entity. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A freeform note Error message encountered during processing. Non-fatal warning message encountered during processing. Non-fatal warning message encountered during processing. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A freeform note Non-fatal warning message encountered during processing. Indicates that the processing of this noun has succeeded; may provide non-fatal warning messages that arose during the processing of the noun. The processing of at least one noun in the BOD has failed. Error and warning messages may explain the failure. Specific outcomes of processing each noun are reported in each of the NounOutcome elements. Non-fatal warning message encountered during processing. Indicates that the processing of this noun has failed, and provides error and warning messages that arose during the processing of the noun. Indicates that the processing of this noun has succeeded; may provide non-fatal warning messages that arose during the processing of the noun. Error message encountered during processing. Non-fatal warning message encountered during processing Non-fatal warning message encountered during processing This is defined as a string type, but the data should be a base 64 encoded string wrapped with a CDATA wrapper. Element that contains name value pairs. It also includes a data type, unit of measure code, and currencyID Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A freeform note The sequence attribute is used for the ordering of elements within a document. It is not intended to be used as an identifier. This attribute contains the Code List ID for the codes that are associated with corresponding entity. This is the identifier for this Property within this document. Identifies the data type of the value of this property. The unit-of-measure (UOM) code associated with a quantity. This is based upon the ISO standard. The code for the currency associated with an amount. This attribute contains the Code List ID for the codes that are associated with corresponding entity. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. Code used to define the status of this document. See the code list associated to this code for the list of valid codes and their meanings. date and time this document becomes effective Identifies the reason for an activity Indicator that determines if the BOD has been archived. The default value is false so there is no need to explicitly set this to false. This attribute contains the Code List ID for the codes that are associated with corresponding entity. This attribute contains the Code List ID for the codes that are associated with corresponding entity. The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. Is the tag and information of the new information to be passed. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions A freeform note Indicates the time period in which the associated component is effective. The sequence attribute is used for the ordering of elements within a document. It is not intended to be used as an identifier. This attribute contains the Code List ID for the codes that are associated with corresponding entity. Workflow Properties This is the identifier for this Property within this document. Identifies the data type of the value of this property. The unit-of-measure (UOM) code associated with a quantity. This is based upon the ISO standard. The code for the currency associated with an amount. This attribute contains the Code List ID for the codes that are associated with corresponding entity. Dimension The accounting entity that is associated with the maintenance of this instance of the noun. For objects that are maintained at the tenant level this attribute must not be included in the document. When no schemeName exists this is the default ID for the enterprise at the level where this object is maintained. The value of the ID must uniquely identify this object throughout the enterprise within the scope of the level where it is maintained (tenant, accounting entity or location). The specific values for this attribute are determined by the individual noun. This is required for language codes other than ""en-us"" when the element that includes this attribute is used. An optional identifier, that when used can uniquely identify each instance of a note within a BOD. It is only unique within the context of where it is used in the document. Indicates if the note should be published externally or if it is for internal use only. It may have the values ''Internal'' and ''External''. Person who created the note Entry date and time in GMT. Status of a note. Indicates what type of note is being specified and is associated to an Infor defined code list, ''Note Types,'' This is required for language codes other than ""en-us"" when the element that includes this attribute is used. The timestamp marking the beginning of a time period during which a related entity or status is effective or applicable. 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. This can be used in place of the EndDateTime, but not in conjunction with it. Is the ending timestamp of the event. This can be used in place of the Duration, but not with it.