© 2018 ProgM

Nachricht UTILMD: D

NameUTILMD
VersionD
Release18B
BeschreibungUtilities master data message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A service segment starting and uniquely identifying a message. The message type code for the Utilities master data message is UTILMD. Note: Utilities master data messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 UTILMD D B UNMandatory
BGM0A segment by which the sender uniquely identifies the Utilities master data message by means of its name and number and its function.Mandatory
DTM0A segment specifying general dates related to the whole message and the time zone used in the message. The segment must be specified at least once to specify the message date as allocated by the sender.Mandatory
MKS0A segment to specify to which market the object relates.Optional
FTX0A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.Optional
TSR0A segment to identify the transport service such as express or normal when the message is used to provide transport routing information for multiple transport products. This information may determine which transport route might be used to carry goods from one shipper to one location.Optional
SG10SG1Optional
RFF1A segment identifying a reference by its type and number, such as references to an earlier sent messages or a contract number.Mandatory
DTM1A segment specifying the date/time related to the referenced information.Optional
SG20SG2Optional
NAD1A segment for specifying the identification and/or the name and the address of the party, in coded or clear form, and the function relevant to the message. It is recommended that, if possible, only the coded form of the party ID should be specified.Mandatory
RFF1A segment for inclusion of any references related to the current party, such as fiscal number or government reference number.Optional
FII1A segment to identify an account and a related financial institution connected to the current party.Optional
ATT1A segment used to identify attributes of the relevant party, such as additional functions of the sender or receiver.Optional
SG31SG3Optional
CTA2A segment to identify a person and/or department, and their function, to whom communications should be directed.Mandatory
COM2A segment to identify a communication type and number for the contact specified.Optional
SG40SG4Optional
IDE1A segment starting a new set of master data for an object, and identifying the type of object, such as a metering point.Mandatory
LIN1A segment providing identification of the quantity in the lower- level object specified, such as a product code.Optional
PIA1A segment providing additional identification to the object specified.Optional
IMD1A segment for describing the object being reported. The segment may be used for specification of the use of the object (e.g. the type of consumption or production in the object).Optional
DTM1A segment to specify dates associated with the object.Optional
PRC1A segment to specify to which business activity phase the object relates.Optional
STS1A segment giving a status for the object, such as active or closed.Optional
TAX1A segment to specify relevant duty/tax/fee information, such as value added tax percentage.Optional
PTY1A segment for communication of priority information, such as if an installation is disconnectable or not.Optional
FTX1A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.Optional
AGR1A segment for specifying agreement details connected to the object, such as the type of contract.Optional
INP1A segment to specify parties to an instruction, the instruction, or both, such as instruction to read a meter.Optional
TSR1A segment to identify the transport service such as express or normal when the message is used to provide transport routing information. This information may determine which transport route might be used to carry goods from one shipper to one location.Optional
SG51SG5Optional
LOC2A segment to identify locations connected to the object, such as a metered grid area or a metering point.Mandatory
HYN2A segment to identify hierarchical connections from a given location to a higher or lower leveled location, such as the connections between an aggregated metering point to the lover level metering points.Optional
SG61SG6Optional
RFF2A segment identifying any references related to the object, such as a transaction reference number or a reference to a time series.Mandatory
DTM2A segment to specify any dates associated with the current reference.Optional
SG71SG7Optional
CCI2A segment to identify characteristic and/or the characteristic name and characteristic relevance for the object, such as method for balance settlement or measurement method, number of digits of a meter etc.Mandatory
CAV2A segment to specify the value of the characteristic previously defined in either coded form or in free format.Optional
SG81SG8Optional
SEQ2A segment to provide a sequence number of the lower-level objects, such as the register number within a meter.Mandatory
RFF2A segment identifying any references related to the lower- level object, such as a register number or a reference to a contract.Optional
PIA2A segment providing additional product identification connected to the lower-level object, such as a register of a meter.Optional
SG92SG9Optional
QTY3A segment identifying the quantity details, such as estimated annual consumption or production.Mandatory
DTM3A segment to specify dates or periods related to the previously specified quantity information.Optional
STS3A segment giving the status for the quantity, such as metered, estimated or corrected.Optional
LIN3A segment providing identification of the quantity in the lower-level object specified, such as a product code.Optional
SG102SG10Optional
CCI3A segment to identify a characteristic and/or the characteristic name and characteristic relevance for the lower-level object, such as number of digits of a meter etc.Mandatory
CAV3A segment to specify the value of the characteristic previously defined in either coded form or in free format.Optional
SG111SG11Optional
MOA2A segment for specifying monetary amounts related to the object.Mandatory
RFF2A segment for identifying a reference to the amount.Optional
DTM2A segment specifying the date/time related to the referenced information.Optional
SG121SG12Optional
NAD2A segment for specifying the identification and/or the name and address of the party, in coded or clear form, and the functions relevant to the object or service. It is recommended that, if possible, only the coded form of the party identification should be specified.Mandatory
RFF2A segment for inclusion of any references related to the current party, such as fiscal number or government reference number.Optional
DTM2A segment specifying the date and/or the time related to the referenced information, such as the date of birth for the end user.Optional
FII2A segment to identify an account and a related financial institution connected to the current party.Optional
LAN2A segment to indicate the langauges for the specified party.Optional
SG132SG13Optional
CTA3A segment to identify a person and/or department, and their function, to whom communications should be directed.Mandatory
COM3A segment to identify a communication type and number for the contact specified.Optional
CNT0A segment by which control totals may be sent by the sender for checking by the receiver.Optional
UNT0A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.Mandatory