Is the primary document id for the document associated. 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. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions 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 A generic reference that uses the 'type' attribute which contains the noun name of the referenced object. 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 current state of the associated object. This field uniquely identifies a product. It will contain strings like “ERP LN” or “ERP SL8”. This field uniquely identifies an installed instance of a product, e.g.: “FullyQualifiedHostname:/path/of/software/install” The default values can be used to reduce the size of the transmitted BOD. Fields that are known to have a 'constant' value in the context of one BOD or even an environment can be put in this section. They don't need to be put in the individual Event entries anymore. If they are however mentioned in an individual event, that value will overrule the default. To say it otherwise: each value in the 'Defaults' section is considered to be part of each of the Event entries, unless it is explicitly specified in the Event itself. Contains license events information obtained from auditing. Validates the BOD being sent by the application. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Identifies the engineering change revision that this entity addresses. Uniform Resource Identifier. Identifies files and locations on the web. This can also be used for email address under contact. Indicates the name of the File being referenced. The date that document was created within the system of record. Free form text that describes the object and repeats as needed to provide support for multilingual descriptions 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.. When this attribute is true the attachment is stored in the EmbeddedSata element. When it is false an external reference is used. This attribute contains the Code List ListID for the code that it is associated with. GenericStatus Contains the name that identifies a user. This is for example the SSO user ID like 'jdoe'. It is not the full name or description (like "John Doe"). Together with the userID and the Tenant, this uniquely defines a concurrent user. This can be e.g. an identifier for the browser session of the user or an identifier of the desktop of the user. contains a time in seconds. If individual event records are not further apart than this distance, they can be aggregated to one time interval. zero or more 'SoftwareID' specific properties. This is required for language codes other than 'en-us' when the element that includes this attribute is used. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Identifies the engineering change revision that this entity addresses. An identifier for an object. The ID has a number of possible attributes to further define how it should be used.. Identifies the engineering change revision that this entity addresses. Is the primary document id for the document associated. Is the alternate document id for the associated document. The date that document was created within the system of record. Is the identifier of the given Line Component within the document The type attribute is required on all DocumentReference elements and must be a valid noun name. The valid noun names are in the "Noun Name" code list for validation. 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. The unit-of-measure (UOM) code associated with a quantity. This is based upon the ISO standard. 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. 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. 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. Contains information that is associated with each license event. This field uniquely identifies a product. It will contain strings like “ERP LN” or “ERP SL8”. This describes the type of event that is taking place. contains the name that identifies a user. Together with the userID and the Tenant, this uniquely defines a concurrent user. contains a time in seconds. If individual event records are not further apart than this distance, they can be aggregated to one time interval. This is allows the LMA to manage the Request/Release pair efficiently. zero or more 'SoftwareID' specific properties. Identifies the name attribute used by the NameValue element. 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. This is required for language codes other than 'en-us' when the element that includes this attribute is used. Identifies where the note is used and is associated to an Infor defined code list, 'NoteType,' that indicates the processes that might use the note. 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 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. 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. 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 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. Indicates the time period in which the associated component is effective. This attribute contains the Code List ID for the codes that are associated with corresponding entity. Workflow Properties 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. 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 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 is required for language codes other than 'en-us' when the element that includes this attribute is used. empty type