Unqualified data types (UDT)

Table of Contents

UpAmount

Definition A number of monetary units specified in a currency where the unit of the currency is explicit or implied.

Attribute: currencyID

Definition Identification of a currency according to ISO 4217.
Usage note Mandatory

UpCode

Definition 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.
Usage note When using codes other than predefined qualified data types, a codelist must be identified by using attributes.

Attribute: listID

Definition Identification of a code list.
Usage note Optional, but required if UBL hasn't predefined a code list. If required, possible values are listed in the documentation.

Attribute: listAgencyID

Definition Identification of an agency maintaining a code list according to UN/ECE 3055.
Usage note Optional, but required if UBL hasn't predefined a code list. If required, possible values are listed in the documentation.

UpDate

Definition One calendar day according the Gregorian calendar.
Usage note Dates are presented according to the ISO 8601 standard format of “YYYY-MM-DD” e.g. “2006-08-18” for the date of August 18th 2006. When specified in Period, Dates are inclusive i.e. a Period with a Start and End Date is inclusive of both.

UpIdentifier

Definition A character string to identify and distinguish uniquely, one instance of an object in an identification scheme from all other objects in the same scheme together with relevant supplementary information.
Usage note When using identifiers that belong to either the sender or the recipient, the attribute schemeAgencyID is recommended. When using identifiers issued by third parties the attribute schemeID is mandatory and the attribute schemeAgencyID is recommended.

Attribute: schemeID

Definition Identification of an identification scheme.
Usage note Optional. If required, possible values are listed in the documentation.

Attribute: schemeAgencyID

Definition Identification of an agency maintaining an identification scheme according to UN/ECE 3055.
Usage note Optional. If required, possible values are listed in the documentation.

UpIndicator

Definition A list of two mutually exclusive Boolean values that express the only possible states of a property.
Usage note Values used are “true” to specify that the indicator is active, valid, or selected and “false” to specify that an indicator is invalid, inactive or not selected. Note that “false” does not have the same meaning as “rejected”, which implies a decision. Default value for indicators is “false”.

UpMeasure

Definition A numeric value determined by measuring an object along with the specified unit of measure.

Attribute: unitCode

Definition Code stating a measure unit according UN/ECE rec 20 revision 4.
Usage note Mandatory

UpName

Definition A character string that consititues the distinctive designation of a person, place, thing or concept.

UpPercent

Definition Numeric information that is assigned or is determined by calculation, counting, or sequencing. It does not require a unit of quantity or unit of measure.
Usage note Percentages are given as fractions of a hundred e.g. the value "34.78" in percentage terms equates to a numeric value of "0.3478". Percentages are specified to no more than 4 decimals, e.g. “34.7812”.

UpQuantity

Definition A counted number of non-monetary units possibly including fractions.
Usage note When UOM for quantity is time (days, hours, minutes), the value is given as a decimal figure e.g, 4 hours and 45 minutes is expressed as 4.75 hours.

Attribute: unitCode

Definition Code stating a quantity unit according UN/ECE rec 20 revision 4.
Usage note Mandatory

UpText

Definition A character string (i.e. a finite set of characters) generally in the form of words of a language.

UpTime

Definition The instance of time that occurs every day.
Usage note The presentation of time is according to ISO 8601 standard format “hh:mm:ss”. In cases of transactions that traverse time zones, the following format should be used, e.g. “09:30:00+1:00” to give the time half past nine in Copenhagen. All formats of xsd:time are allowed.