{
  "url": "https://openlegislation.uk/eu-regulation-2019-1744/annex/appendix-3",
  "json_url": "https://openlegislation.uk/eu-regulation-2019-1744/annex/appendix-3.json",
  "legislation": "eur/2019/1744",
  "legislation_title": "Commission Implementing Regulation (EU) 2019/1744 of 17 September 2019 on technical specifications for electronic ship reporting in inland navigation and repealing Regulation (EU) No 164/2010",
  "legislation_url": "https://openlegislation.uk/eu-regulation-2019-1744",
  "path": "annex/appendix/3",
  "kind": "appendix",
  "number": "3",
  "heading": "ERINOT response and receipt message (APERAK) — ERIRSP",
  "text": "1.\nAPERAK GENERAL RESPONSE AND RECEIPT MESSAGE\nThis message shall be used to provide where required answering and response functions to sent messages.\nThe function of this message is:\n(a) to inform a message issuer that his message has been received by the addressee’s application and has been rejected due to errors encountered during its processing in the application;\n(b) to acknowledge to a message issuer the receipt of his message by the addressee’s application.\n1.1.\nField of application\nThe application error and acknowledgement message can be used for both national and international applications. It is not dependent on the type of business or industry, neither it is a legal requirement: it is based on business practices related to administration and transport.\n1.2.\nPrinciples\nA message can first be controlled at system level (e.g. the CONTRL message) to detect syntax errors and to acknowledge its receipt. It shall be then transmitted to the application process to be processed.\nWhen an acknowledgement is necessary an APERAK message shall be sent specifying the reasons of acknowledgement. If an error is detected at the application level, which prevents its complete processing, an APERAK message shall be sent to the original message issuer providing details of the error(s) encountered. In case of application error, the APERAK message shall be transmitted manually.\nIn case of acknowledgement the APERAK message shall be processed automatically or manually, at recipient’s discretion.\n2.\nERI RESPONSE MESSAGE ERIRSP\nThe ERIRSP message is derived from the UN/EDIFACT APERAK message. The response messages to the functions (new, modification or cancellation) of the notification message ERINOT have all the same structure. The response to a ‘modification’ or a ‘cancellation’ contains information whether or not the ‘modification’ or ‘cancellation’ has been processed by the receiving system. A response is required only if the NAD (1)/COM segment, with qualifier ‘EI’, contains the mailbox number, or with qualifier ‘EM’, contains the email address where the response is to be returned to.\n2.1\nSegment index (alphabetical sequence by tag)\nBGM Beginning of message\nCOM Communication contact\nDTM Date/time/period\nERC Application error information\nFTX Free text\nNAD Name and address\nRFF Reference\nUNH Message header\nUNT Message trailer\n2.2.\nSegment table\nPos\nTag\nName\nS\nR\nUNB\nM\n1\n0010\nUNH\nMessage header\nM\n1\n0020\nBGM\nBeginning of message\nM\n1\n0030\nDTM\nDate/time/period\nM\n1\n0060\nSegment group 1\nC\n2\n0070\nRFF\nReference\nM\n1\n0090\nSegment group 2\nC\n1\n0100\nNAD\nName and address\nM\n1\n0120\nCOM\nCommunication contact\nC\n3\n0130\nSegment group 3\nD[1]\n9\n0140\nERC\nApplication error information\nM\n1\n0150\nFTX\nFree text\nM\n1\n0190\nUNT\nMessage trailer\nM\n1\nBusiness rules\nD[1]\nThis segment-group is to be used if any application error(s) occur.\n2.3\nBranching Diagram\n2.4\nERIRSP message structure\nTable 2 defines the segments of the ERI response messages.\nTable 2: ERI response message ERIRSP\nSegment Group\nSegmentComposite data element (C)Data elementTAG\nLevel\nStatus\nFormat\nName\nDescriptionQualifiers in quotation marks\n1\n2\n3\n4\n5\n6\n7\nUNB\n0\nM\nINTERCHANGE HEADER\nS001\nM\nSYNTAX IDENTIFIER\n0001\nM\na4\nSyntax identifier\n‘UNOA’ Controlling agency\n0002\nM\nn1\nSyntax version number\n‘2’\nS002\nM\nINTERCHANGE SENDER\n0004\nM\nan..35\n(an25)\nSender identification\nMailbox number or unique name or the unique identifier of a RIS-centre or traffic post\n0007\nan..4\nPartner identification code qualifier\nn.a.\n0008\nan..14\nAddress for reverse routing\nn.a.\nS003\nM\nINTERCHANGE RECIPIENT\n0010\nM\nan..35\n(an25)\nRecipient identification\nMailbox number or unique name or the unique identifier of a RIS-centre or traffic post\n0007\nan..4\nPartner identification code qualifier\nn.a.\n0014\nan..14\nRouting address\nn.a.\nS004\nM\nDATE/TIME OF PREPARATION\n0017\nM\nn6\nDate\nGeneration date, YYMMDD\n0019\nM\nn4\nTime\nGeneration time, HHMM\n0020\nM\nan..14\nInterchange control reference\nFirst 14 positions of the message reference number\nS005\nRECIPIENTS REFERENCE, PASSWORD\n0022\nan..14\nRecipient’s reference/password\nn.a.\n0025\nan2\nRecipient’s reference, password qualifier\nn.a.\n0026\nan..14\nApplication reference\nn.a.\n0029\na1\nProcessing priority code\nn.a.\n0031\nn1\nAcknowledgement request\nn.a.\n0032\nan..35\nCommunications agreement id\nn.a.\n0035\nC\nn1\nTest indicator\n‘1’ = the interchange relates to a test message\nUNH\n0\nM\nMESSAGE HEADER\nIdentification, specification and heading of a message\n0062\nM\nan..14\nMessage reference number\nFirst 14 positions of the message reference number\nS009\nM\nMESSAGE IDENTIFIER\n0065\nM\nan..6\nMessage type\n‘APERAK’, message type\n0052\nM\nan..3\nMessage version number\n‘D’\n0054\nM\nan..3\nMessage release number\n‘98B’\n0051\nM\nan..2\nControlling agency\n‘UN’\n0057\nM\nan..6\nAssociation assigned code\n‘ERI13’, ERI Version 1.3\n0068\nan..35\nCommon access reference\nn.a.\nS010\nSTATUS OF THE TRANSFER\n0070\nn..2\nSequence of transfers\nn.a.\n0073\na1\nFirst and last transfer\nn.a.\nBGM\n0\nM\nBEGINNING OF MESSAGE\nIdentification of the type and function of the message\nC002\nM\nDOCUMENT/MESSAGE NAME\n1001\nM\nan..3\nDocument/message name code\nType of message received for which this message contains the acknowledgement information:\n‘VES’, from vessel to RIS authority message\n‘CAR’, from carrier to RIS authority message\n‘PAS’, passage report from RIS authority to RIS authority\n1131\nan..3\nCode list qualifier\nn.a.\n3055\nan..3\nCode list responsible agency\nn.a.\n1000\nan..35\nDocument/message name\nn.a.\nC106\nM\nDOCUMENT/MESSAGE IDENTIFICATION\n1004\nM\nan..35\n(an15)\nDocument identifier\nMessage reference number. This number shall be as unique as possible, both for sender and for receiver. If a message is received and then passed on to another receiver, the original message reference number shall be used. The transitional system shall in this case not generate another message reference number.\n1056\nan..9\nVersion\nn.a.\n1060\nan..6\nRevision number\nn.a.\n1225\nM\nan..3\nMessage function code\nFunction of message: ‘9’ = new message (original)\n4343\nM\nan..3\nResponse type code\n‘AP’ accepted\n‘RE’ rejected.\nThe notification is rejected if the transport is already arrived at its destination.\nDTM\n1\nM\nDATE/TIME/PERIOD\nThe date/time that the receiving application encounters the approval or rejection\nC507\nM\nDATE/TIME/PERIOD\n2005\nM\nan..3\nDate or time or period function code qualifier\n‘137’ for document/message date/time\n2380\nM\nan..35\nDate or time period value\nValue of arrival time: YYMMDDHHMM\n2379\nM\nan..3\nDate or time or period format code\n‘201’ for YYMMDDHHMM\nGRP 1\nRFF (1)\n1\nC\nREFERENCE\nReference to previous message\nC506\nM\nREFERENCE\n1153\nM\nan..3\nReference qualifier\n‘ACW’ for reference number to previous message\n1154\nM\nan..35\nReference number\nMessage reference number from BGM, TAG 1004 of the message this message refers to\n1156\nan..6\nLine number\nn.a.\n4000\nan..35\nReference version number\nn.a.\n1060\nan..6\nRevision number\nn.a.\nGRP 1\nRFF (2)\n1\nC\nREFERENCE\nReference to transaction/invoice number\nC506\nM\nREFERENCE\n1153\nM\nan..3\nReference qualifier\n‘AAY’ for reference number to transaction\n1154\nM\nan..35\nReference number\nReference number assigned by the receiving authority. The reference number shall start with the UN country code followed by three positions for the assigning system. The final part is the actual reference number.\n1156\nan..6\nLine number\nn.a.\n4000\nan..35\nReference version number\nn.a.\n1060\nan..6\nRevision number\nn.a.\nGRP 2\nNAD\n1\nM\nNAME and ADDRESS\nName and address of the sender of the notification\n3035\nM\nan..3\nParty function code qualifier\n‘MS’ for message sender\nC082\nPARTY IDENTIFICATION DETAILS\nn.a.\n3039\nan..35\nParty identification\nn.a.\n1131\nan..3\nCode list qualifier\nn.a.\n3055\nan..3\nCode list responsible agency\nn.a.\nC058\nNAME AND ADDRESS\nn.a.\n3124\nan..35\nName and address line\nn.a.\n3124\nan..35\nName and address line\nn.a.\n3124\nan..35\nName and address line\nn.a.\n3124\nan..35\nName and address line\nn.a.\n3124\nan..35\nName and address line\nn.a.\nC080\nM\nPARTY NAME\n3036\nM\nan..35\nParty name\nName of the sender of the notification\n3036\nan..35\nParty name\nn.a.\n3036\nan..35\nParty name\nn.a.\n3036\nan..35\nParty name\nn.a.\n3036\nan..35\nParty name\nn.a.\n3045\nan..3\nParty name format, coded\nn.a.\nC059\nC\nSTREET\n3042\nM\nan..35\nStreet and number/PO box\nStreet and number or post office box\n3042\nan..35\nStreet and number/PO box\nn.a.\n3042\nan..35\nStreet and number/PO box\nn.a.\n3042\nan..35\nStreet and number/PO box\nn.a.\n3164\nC\nan..35\nCity name\nCity\n3229\nan..9\nCountry sub-entity identification\nn.a.\n3251\nC\nan..9\nPostcode identification\nPostal identification code\n3207\nC\nan..3\nCountry\nISO 3166-1 two alpha country code, see Annex, Chapter 2.3.8\nNAD\nCOM\n2\nC\nCOMMUNICATION CONTACT\nSender communication contact details (maximum 3 times)\nC076\nM\nCOMMUNICATION CONTACT\n3148\nM\nan..70\nCommunication number\nCommunication number\n3155\nM\nan..3\nCommunication channel qualifier\n‘TE’ for telephone number\n‘FX’ for fax number\n‘EM’ for Email address\nGRP 3\nERC\n1\nC\nAPPLICATION ERROR INFORMATION\nC901\nM\nAPPLICATION ERROR DETAIL\n9321\nM\nan..8\nApplication error\nApplication error code\n1131\nan..3\nCode list qualifier\nn.a.\n3055\nan..3\nCode list responsible agency\nn.a.\nERC\nFTX\n2\nM\nFREE TEXT\nTo communicate the reason for rejection\n4451\nM\nan..3\nText subject code qualifier\n‘AAO’ for free text error description\n4453\nan..3\nFree text function code\nn.a.\nC107\nTEXT REFERENCE\n4441\nan..17\nFree text identification\nn.a.\n1131\nan..3\nCode list qualifier\nn.a.\n3055\nan..3\nCode list responsible agency\nn.a.\nC108\nC\nTEXT LITERAL\nText\n4440\nM\nan..70\nFree text\nFurther description\n4440\nC\nan..70\nFree text\nFurther description\n4440\nC\nan..70\nFree text\nFurther description\n4440\nC\nan..70\nFree text\nFurther description\n4440\nC\nan..70\nFree text\nFurther description\n3453\nan..3\nLanguage, coded\nn.a.\n4447\nan..3\nText formatting, coded\nn.a.\nUNT\nM\nMESSAGE TRAILER\nEnd and control of completeness of the message\n0074\nM\nn..6\nNumber of segments in a message\n0062\nM\nan..14\nMessage reference number\nFirst 14 positions of the message reference number\nUNZ\nM\nINTERCHANGE TRAILER\nEnd and control of the interchange\n0036\nM\nn..6\nInterchange control count\n‘1’ for number of messages contained in the interchange\n0020\nM\nan..14\nInterchange control reference\nFirst 14 positions of the message reference number\n3.\nERROR CODES\nFor data attribute: MESSAGE REFERENCE ANSWERED TO ERROR DESCR CODE, the error codes available electronically in the European Reference Data Management System (ERDMS) operated by the European Commission shall be used in in segment ERC, data element 9321.",
  "extent": "E+W+S+N.I.",
  "status": null,
  "version": "current",
  "annotations": [],
  "outstanding_effects": [],
  "provenance": {
    "source": "legislation.gov.uk",
    "source_url": "https://www.legislation.gov.uk/eur/2019/1744/annex/appendix/3",
    "retrieved_at": "2026-11-01T14:43:07.241335+00:00"
  },
  "licence": "Open Government Licence v3.0",
  "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "attribution": "Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives."
}