The message header section contains the relevant information on the sender,
receiver, the type of information being transmitted and the transmission date.
This is a section header for the message header. This section assumes the
establishment of an EDI trading partnership agreement that will help define the
message number, sender ID, receiver ID, message date.
This section describes the general data about the acknowledgement and the original message
The code associated to message we are sending the acknowledgement by EV System
The Message Number of the message, Locally Assigned, we are sending the acknowledgement
The Message Sender Identifier of the message we are sending the acknowledgement
The Message Receiver Identifier of the message we are sending the acknowledgement
The format of the Original Message Date.
The unique value admitted is "204" corresponding at "CCYYMMDDHHMMSS"
The Original Message Date.
01= All Reports loaded into database 02 = EVPR Error, not all reports loaded into the database, check section B 03= SGML parsing error, no data extracted
This field contains the description when happened an error. It's mandatory when transmission acknowledgment code is 03.
This section contains information about the acknowledgment of each part of message.
This field says the type section of message
This field is the number assigned by the sender to identify report in the position of XML file. May be Null for no Inserts, and it's mandatory for Inserts.
This field is the number assigned by the EVMPD in case of an INSERT or by the sender, in all other cases, to identify the report in the EVMPD. May be Null for the insucessfull Inserts (see operationresult)
This field says which operation type wanted to do in each section (1=Insert, 2=Update, 3=Variation, 4=Nullify, 5=Change Ownership, 6=Withdrawn).
This field says the operation result of a particular section
This field says the description operation result of a particular section
The section reportcomments contains the list of errors and warnings detected by the message parsing process
The message parsing process will add a specific report comment element for each parsing warning or error detected during the validation process
The severity flag describes if the report comment is an error or a warning
The XML message section which the comment is referred to
This field contains the field's name in which was produced the first error (if exists)
This field contains the value of field in which was produced the first error (if exists)
This field contains the value substituted for the value in fieldvalue(G.7.1.4a)
This field contains a comment about the error type
This field contain a detailed explanation of the error
Message Type
The message type contains information on the type of information being
transmitted. When creating a message, the value of this field should be "EVPRM".
Message Format Version
The message format version contains the version number of the SCHEMA.
Message Format Release
The message format release contains the release number of the message
format version number of the SCHEMA.
Message Number
The message number is a unique tracking number assigned to a specific
product message file transmitted by the sender.
This message number is unique to the sender.
Message Sender Identifier
This field identifies the sender of the message, e.g., company name
identifier or regulatory authority name identifier.
Message Receiver Identifier
This field identifies the intended recipient of the transmission of the message, e.g., company name identifier or regulatory authority name identifier.
The Original Message Date.
The unique value admitted is "204" corresponding at "CCYYMMDDHHMMSS"
Message Date
The message date is the date on which the message was initiated.