Passer au contenu
Français
Portail client
Contact
  • Il n'y a aucune suggestion car le champ de recherche est vide.

SOA Service Specification Document

Emplacement : Documentation ICS2

Sources :

CD3-ICS2-STI-SSD-eu_ics2_c2t-SfA-v5.20 (24/01/2022)

CD3-ICS2-STI-SSD-eu_ics2_t2c-SfA-v5.00 (24/01/2022)

4. ICS2-HTI-IE-(2022-05-04)-v2.02

  • IE3Axx — Name : E_ENS_xxx_AMD ; Full name : ENS filing amendment ; Process where it is used : L4-ICS2-07 Amend filing
  • IE3Fxx — Name : E_ENS_xxx_DEC ; Full name : ENS filing ; Process where it is used : L4-ICS2-01 Register filing
  • IE3N01 — Name : E_ELF_VLD_NOT ; Full name : ENS lifecycle validation error notification ; Process where it is used : L4-ICS2-01 Register filing
  • IE3N02 — Name : E_ENS_NCP_NOT ; Full name : ENS Not complete notification ; Process where it is used : L4-ICS2-02-01 Relate ENS filings
  • IE3N03 — Name : E_ASM_CMP_NOT ; Full name : Assessment complete notification ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • IE3N04 — Name : E_REF_RFI_NOT ; Full name : Additional information request notification ; Process where it is used : L4-ICS2-03-01 Send referral
  • IE3N05 — Name : E_REF_RFS_NOT ; Full name : High Risk Cargo & Mail screening request notification ; Process where it is used : L4-ICS2-03-01 Send referral
  • IE3N06 — Name : E_ARV_NOT ; Full name : Arrival notification ; Process where it is used : L4-ICS2-04 Process arrival of means of transport
  • IE3N07 — Name : E_HCS_INC_NOT ; Full name : House consignment in incorrect state notification ; Process where it is used : L4-ICS2-04 Process arrival of means of transport
  • IE3N08 — Name : E_CON_NOT ; Full name : Control notification ; Process where it is used : L4-ICS2-04 Process arrival of means of transport
  • IE3N09 — Name : E_AEO_CON_NOT ; Full name : Authorised Economic Operator control notification ; Process where it is used : L4-ICS2-06-01 Handle AEO notification
  • IE3N10 — Name : E_AMD_NOT ; Full name : Amendment Notification ; Process where it is used : L4-ICS2-07 Amend filing
  • IE3N11 — Name : E_ENS_PND_NOT ; Full name : ENS pending notification ; Process where it is used : L4-ICS2-02-01 Relate ENS filings
  • IE3N99 — Name : E_ERR_NOT ; Full name : Error notification ; Process where it is used : L4-ICS2-01 Register filing
  • L4-ICS2-04 Process arrival of means of transport
  • L4-ICS2-07 Amend filing
  • L4-ICS2-08 Invalidate filing
  • IE3Q01 — Name : E_DNL_REQ ; Full name : Do Not Load request ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • IE3Q02 — Name : E_REF_RFI_REQ ; Full name : Additional information request ; Process where it is used : L4-ICS2-03-01 Send referral
  • IE3Q03 — Name : E_REF_RFS_REQ ; Full name : High Risk Cargo & Mail screening request ; Process where it is used : L4-ICS2-03-01 Send referral
  • IE3Q04 — Name : E_INV_REQ ; Full name : Invalidation Request ; Process where it is used : L4-ICS2-08 Invalidate filing
  • IE3Q05 — Name : E_ENS_CNS ; Full name : ENS Consultation ; Process where it is used : L4-ICS2-13 Consult ENS
  • IE3R01 — Name : E_ENS_REG_RSP ; Full name : ENS Registration Response ; Process where it is used : L4-ICS2-01 Register filing
  • IE3R02 — Name : E_REF_RFI_RSP ; Full name : Additional information response ; Process where it is used : L4-ICS2-03-01 Send referral
  • IE3R03 — Name : E_REF_RFS_RSP ; Full name : High Risk Cargo & Mail screening response ; Process where it is used : L4-ICS2-03-01 Send referral
  • IE3R04 — Name : E_ARV_REG_RSP ; Full name : Arrival Registration Response ; Process where it is used : L4-ICS2-04 Process arrival of means of transport
  • IE3R07 — Name : E_INV_ACC_RSP ; Full name : Invalidation Acceptance Response ; Process where it is used : L4-ICS2-08 Invalidate filing
  • IE3R08 — Name : E_ENS_CNS_RES ; Full name : ENS Consultation results ; Process where it is used : L4-ICS2-13 Consult ENS
  • B — Message ID : IE4Fxx ; Message Name : C_ENS_xxx_DEC ; Message name full : ENS filing ; Process where it is used : L4-ICS2-01 Register filing ; Equivalent ED message : IE3Fxx
  • B — Message ID : IE4Axx ; Message Name : C_ENS_xxx_AMD ; Message name full : ENS filing amendment ; Process where it is used : L4-ICS2-07 Amend filing ; Equivalent ED message : IE3Axx
  • B — Message ID : IE4Q01 ; Message Name : C_ESC_REQ ; Message name full : e-Screening request ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • B — Message ID : IE4Q02 ; Message Name : C_ERA_REQ ; Message name full : e-risk analysis request ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • A — Message ID : IE4Q03 ; Message Name : C_DNL_REQ ; Message name full : Do Not Load request ; Process where it is used : L4-ICS2-03 Perform risk analysis ; Equivalent ED message : IE3Q01
  • B — Message ID : IE4Q04 ; Message Name : C_REF_RFI_REQ ; Message name full : Additional information request ; Process where it is used : L4-ICS2-03-01 Send referral ; Equivalent ED message : IE3Q02/IE3N04
  • A — Message ID : IE4Q05 ; Message Name : C_REF_RFS_REQ ; Message name full : High Risk Cargo & Mail screening request ; Process where it is used : L4-ICS2-03-01 Send referral ; Equivalent ED message : IE3Q03/IE3N05
  • C — Message ID : IE4Q06 ; Message Name : C_INV_REQ ; Message name full : Invalidation request ; Process where it is used : L4-ICS2-08 Invalidate filing ; Equivalent ED message : IE3Q04
  • B — Message ID : IE4Q07 ; Message Name : C_OMS_REQ ; Message name full : OMS request to perform e- Screening ; Process where it is used : L4-ICS2-09 e-Screening by OMS
  • C — Message ID : IE4Q08 ; Message Name : C_PRS_RVK_REQ ; Message name full : Presentation revocation request ; Process where it is used : L4-ICS2-12 Revoke presentation of goods
  • B — Message ID : IE4Q10 ; Message Name : C_ENS_QUE ; Message name full : Query for ENS ; Process where it is used : L4-ICS2-14 Query for ENS
  • B — Message ID : IE4R01 ; Message Name : C_ENS_ACC_RSP ; Message name full : ENS acceptance response ; Process where it is used : L4-ICS2-02 Prepare ENS for risk analysis
  • B — Message ID : IE4R02 ; Message Name : C_REF_RFI_RSP ; Message name full : Additional information response ; Process where it is used : L4-ICS2-03-01 Send referral ; Equivalent ED message : IE3R02
  • A — Message ID : IE4R03 ; Message Name : C_REF_RFS_RSP ; Message name full : High Risk Cargo & Mail screening response ; Process where it is used : L4-ICS2-03-01 Send referral ; Equivalent ED message : IE3R03
  • C — Message ID : IE4R04 ; Message Name : C_INV_ACC_RSP ; Message name full : Invalidation acceptance response ; Process where it is used : L4-ICS2-08 Invalidate filing ; Equivalent ED message : IE3R07
  • B — Message ID : IE4R05 ; Message Name : C_ENS_QUE_RES ; Message name full : ENS query results ; Process where it is used : L4-ICS2-14 Query for ENS
  • B — Message ID : IE4S01 ; Message Name : C_ESC_ASM_RES ; Message name full : e-Screening results ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • A — Message ID : IE4S02 ; Message Name : C_RSK_RES ; Message name full : Risk analysis results ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • C — Message ID : IE4S03 ; Message Name : C_CON_RES ; Message name full : Control results ; Process where it is used : L4-ICS2-04 Process arrival of means of transport
  • L4-ICS2-06 Process control decision and results
  • B — Message ID : IE4N01 ; Message Name : C_ELF_VLD_NOT ; Message name full : ENS lifecycle validation error notification ; Process where it is used : L4-ICS2-02 Prepare ENS for risk analysis ; Equivalent ED message : IE3N01
  • A — Message ID : IE4N03 ; Message Name : C_ERA_HIT_NOT ; Message name full : e-risk analysis hit notification ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • A — Message ID : IE4N04 ; Message Name : C_ASM_CMP_NOT ; Message name full : Assessment complete notification ; Process where it is used : L4-ICS2-03 Perform risk analysis ; Equivalent ED message : IE3N03
  • B — Message ID : IE4N05 ; Message Name : C_CON_RCM_NOT ; Message name full : Control recommendation notification ; Process where it is used : L4-ICS2-03 Perform risk analysis
  • L4-ICS2-04 Process arrival of means of transport
  • L4-ICS2-05 Process presentation of goods
  • L4-ICS2-06 Process control decision and results
  • B — Message ID : IE4N06 ; Message Name : C_REF_AMD_NOT ; Message name full : Amendment after referral reception notification ; Process where it is used : L4-ICS2-03-01 Send referral
  • B — Message ID : IE4N10 ; Message Name : C_PRS_INF ; Message name full : Presentation information ; Process where it is used : L4-ICS2-05 Process presentation of goods
  • C — Message ID : IE4N11 ; Message Name : C_AEO_CON_NOT ; Message name full : Authorised Economic Operator control notification ; Process where it is used : L4-ICS2-06-01 Handle AEO notification ; Equivalent ED message : IE3N09
  • C — Message ID : IE4N12 ; Message Name : C_AMD_NOT ; Message name full : Amendment completion notification ; Process where it is used : L4-ICS2-07 Amend filing ; Equivalent ED message : IE3N10
  • C — Message ID : IE4N13 ; Message Name : C_INV_NOT ; Message name full : ENS filing invalidation notification ; Process where it is used : L4-ICS2-08 Invalidate filing ; Equivalent ED message : IE3N99
  • B — Message ID : IE4N99 ; Message Name : C_ERR_NOT ; Message name full : Error notification ; Process where it is used : L4-ICS2-07 Amend filing
  • L4-ICS2-08 Invalidate filing
  • L4-ICS2-12 Revoke presentation of goods

IE3Fxx : Register filing

  • Name — Values : IE3Fxx, where ‘xx’ stands for the ID of the filing type which is comprised in between 10 and 51.
  • Description — Values : Realised BPMs: L4-ICS2-01 – Register filing. Triggered Task/Event: E-01-01 - ENS filing received event. High level description of the tasks realised by the action after the reception of an ENS Filing Message: Semantic and syntactic validation is performed on the received message; The ENS Filing is registered and a MRN is assigned to it; (NOT IN BPM) The IE4Fxx message is built based on the received message (IE3Fxx message); The ENS Filing (IE4Fxx message) is submitted to the CR application.
  • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
  • Payloads — Values : This action receives the message IE3Fxx as payload. Details on the message are available in the Technical Service Contract Document [R02].
  • Post-conditions — Values : The possible post-conditions are the following: An error has been identified during the validation and an error notification is submitted to the EO system (T-01-06 - Notify Error task). The ENS filing is rejected (E-01-03 - ENS filing rejected event). The validation succeeded and the ENS filing is submitted to the ICS2 Common Repository Application (T-01-03 - Submit registered ENS filing task).

The available registration Actions are:

    • Mode of transport: Sea and inland waterways
    • IE3F10 — Message Id : IE3F10 ; Short Description : Complete dataset – Straight bill of lading containing the necessary information from consignee ; Payload Description : An ENS Filing Message is submitted by the EO system and is received by the ICS2 TI Application. An ENS Filing means either partial or full ENS data set required by the legislation per specific mode of transport or business model. In case the reader wishes to find detailed information regarding the content (payload) of each message, they can refer to the ICS2 Information Exchange Specifications document [R04] and look-up the relevant messageID
    • IE3F11 — Message Id : IE3F11 ; Short Description : Complete dataset – Master bill of lading with underlying house bill(s) of lading containing the necessary information from consignee at the level of the lowest house bill of lading
    • IE3F12 — Message Id : IE3F12 ; Short Description : Partial dataset – Master bill of lading only
    • IE3F13 — Message Id : IE3F13 ; Short Description : Partial dataset – Straight bill of lading only
    • IE3F14 — Message Id : IE3F14 ; Short Description : Partial dataset – House bill of lading only
    • IE3F15 — Message Id : IE3F15 ; Short Description : Partial dataset – House bill of lading with the necessary information from consignee
    • IE3F16 — Message Id : IE3F16 ; Short Description : Partial dataset – Necessary information required to be provided by consignee at the lowest level of transport contract (the lowest house bill of lading)
    • IE3F17 — Message Id : IE3F17 ; Short Description : Partial dataset – Necessary information required to be provided by consignee at the lowest level of transport contract (straight bill)

    ICS2 R3 ENS filing types

    • F11 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Complete dataset – Master bill of lading with underlying house bill(s) of lading containing the necessary information from consignee at the level of the lowest house bill of lading
    • F12 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Partial dataset – Master bill of lading only
    • F13 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Partial dataset – Straight bill of lading only
    • F14 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Partial dataset – House bill of lading only
    • F15 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Partial dataset – House bill of lading with the necessary information from consignee
    • F16 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Partial dataset – Necessary information required to be provided by consignee at the lowest level of transport contract (the lowest house bill of lading)
    • F17 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Sea and inland waterways – Partial dataset – Necessary information required to be provided by consignee at the lowest level of transport contract (straight bill)
    • F20 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) – Complete dataset lodged pre-loading
    • F21 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) – Partial dataset – Master air waybill lodged pre-arrival
    • F22 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) – Partial dataset – House air waybill lodged pre-arrival
    • F23 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Partial dataset — Minimum dataset lodged pre- loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446 without master air waybill reference number
    • F24 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Partial dataset — Minimum dataset lodged pre- loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446 with master air waybill reference number
    • F25 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Partial dataset — Master air waybill reference number lodged pre-loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446
    • F26 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Partial dataset — Minimum dataset lodged pre- loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446 and containing additional house air waybill information
    • F27 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Complete dataset lodged pre-arrival
    • F28 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Complete dataset lodged pre-loading – Direct air waybill
    • F29 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Air cargo (general) — Complete dataset lodged pre-arrival – Direct air waybill
    • F30 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Express consignments — Complete dataset lodged pre-arrival
    • F31 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Express consignments on air cargo general – Complete dataset lodged pre-arrival by the express operator
    • F32 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Express consignments — Partial dataset — Minimum dataset lodged pre-loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446
    • F33 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Express consignments on air cargo general – Partial dataset – House air waybill lodged pre-arrival by a person pursuant to Article 127(6) of the Code and in accordance with Article 113(1)
    • F34 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Express consignments on road – Complete dataset lodged pre-arrival
    • F40 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Postal consignments – Partial dataset – Road Master bill of lading
    • F41 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Postal consignments – Partial dataset – Rail master transport document information
    • F42 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Postal consignments – Partial dataset - Master air waybill containing necessary postal air waybill information lodged in accordance with the time-limits applicable for the mode of transport concerned
    • F43 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Postal consignments — Partial dataset — Minimum dataset lodged pre- loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446
    • F44 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Postal consignment — Partial dataset — Receptacle identification number lodged pre-loading in accordance with Article 106(1) second subparagraph of Delegated Regulation (EU) 2015/2446
    • F45 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Postal consignments – Partial dataset – Sea and inland waterways
    • F50 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Road mode of transport
    • F51 — Sea and inland waterways – Complete dataset – Straight bill of lading containing the necessary information from consignee : Rail mode of transport

    IE3Axx : Amend ENS filing

    • Name — Values : IE3Axx, where ‘xx’ stands for the ID of the filing type which is comprised in between 10 and 51.
    • Description — Values : Realised BPMs: L4-ICS2-07 Amend ENS filing. Triggered Task/Event: E-07-01 – Amendment of ENS filing received event. High level description of the tasks triggered by the action after the reception of an ENS Amendment message: Semantic and syntactic validation is performed on the received message; (NOT IN BPM) The IE4Axx message is built based on the received message (IE3Axx message); The ENS amendment message (IEA4xx message) is submitted to the Common Repository.
    • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
    • Payloads — Values : This action receives the message IE3Axx as payload. Details on the message are available in the Technical Service Contract Document [R02].
    • Post-conditions — Values : The possible post-conditions are the following: An error has been identified during the validation and an error notification is submitted to the EO system (T-07-04 – Notify error in amendment of ENS filing task). The Amendment of the ENS filing is rejected (E-07-05 – Amendment of ENS filing rejected event); The validation succeeded and the amendment of the ENS filing is submitted to the ICS2 Common Repository Application (T-07-02- Submit amendment of ENS filing to CR task and E-07-02 - Amendment of ENS filing submitted event).

    The available amendment actions are:

      Messages en détails

      IE3R01

      • Name — Values : IE3R01
      • Description — Values : Realised BPM: L4-ICS2-01 – Register filing. Triggering Task/Event: T-01-04 - Notify successful registration and MRN to Person filing and T-01-05 - Notify successful registration and MRN to Carrier. High level description of the tasks realised by the action: The Person filing is notified about the successful registration of the ENS Filing and the corresponding MRN. Furthermore, the Carrier is potentially notified about the successful registration of the ENS Filing and the corresponding MRN.
      • Pre-conditions — Values : The MRN has been assigned and the registration has been performed successfully in the Common Repository. An ENS Acceptance Response has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3R01 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an ENS Registration Response has been received by the EO system of the Person Filing and (potentially) the EO system of the Carrier.

      IE3N01

      • Name — Values : IE3N01
      • Description — Values : Realised BPMs: L4-ICS2-01 Register filing, L4-ICS2-07 Amend ENS filing, L4-ICS2-08 Invalidate filing. Triggering Task/Event: T-01-09 - Notify ENS lifecycle validation error, T-07-05 Notify ENS lifecycle validation error and T-08-04 - Notify ENS lifecycle validation error tasks respectively. High level description of the tasks realised by the action: The Person filing is notified about the ENS lifecycle validation error.
      • Pre-conditions — Values : An ENS Lifecycle Validation Error Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N01 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an ENS Lifecycle Validation Error Notification has been received by the EO system.

      IE3N99

      • Name — Values : IE3N99
      • Description — Values : Realised BPM: L4-ICS2-01 – Register filing, L4-ICS2-07 Amend ENS filing, L4-ICS2-08 Invalidate filing and L4-ICS2-04 Process arrival of means of transport processes. Triggering Task/Event: T-01-06 - Notify Error, T-07-04 - Notify Error, T-07-14 – Notify Error, T-08-02 - Notify error in invalidation of ENS filing and T 04-02 - Notify Error respectively. Other cases related to BRs: E-03-01-08-BR01, T-03-01-11-BR01, T-13-03-BR01. High level description of the tasks realised by the action: The Person filing is notified about an error that occurred during the validation of his initial submission.
      • Pre-conditions — Values : N/A
      • Payloads — Values : This action receives the message IE3N99 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Error Notification has been received by the EO system.

      IE3N10

      • Name — Values : IE3N10
      • Description — Values : Realised BPM: L4-ICS2-07 Amend ENS filing. Triggering Task/Event: T-07-03 - Notify Completion of amendment of ENS filing task. High level description of the tasks realised by the action: The Person filing is notified about the completion of the ENS filing amendment.
      • Pre-conditions — Values : An Amendment Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N10 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Amendment Notification has been received by the EO system.

      IE3R07

      • Name — Values : IE3R07
      • Description — Values : Realised BPM: L4-ICS2-08 Invalidate filing. Triggering Task/Event: T-08-05 - Notify invalidation of ENS filing completion task. High level description of the tasks realised by the action: The Person filing is notified about the completion of the ENS filing invalidation.
      • Pre-conditions — Values : An Invalidation Acceptance Response has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3R07 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Invalidation Acceptance Response has been received by the EO system.

      IE3N02

      • Name — Values : IE3N02
      • Description — Values : Realised BPM: L4-ICS2-02-01 Relate ENS filings. Triggering Task/Event: T-02-01-01 - Notify ENS not complete to Person filing. High level description of the tasks realised by the action: The Person filing is notified about the non-completion of the ENS Filling.
      • Pre-conditions — Values : An ENS Not Complete Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N02 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an ENS Not Complete Notification has been received by the EO system.

      IE3N11

      • Name — Values : IE3N11
      • Description — Values : Realised BPM: L4-ICS2-02-01 Relate ENS filings. Triggering Task/Event: T-02-01-03 - Notify ENS filing pending to Person that has not yet filled task. High level description of the tasks realised by the action: The Person that has not yet filled the ENS Filing is notified about its pending for completion.
      • Pre-conditions — Values : An ENS Not Complete Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N11 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an ENS Pending Notification has been received by the EO system.

      IE3N03

      • Name — Values : IE3N03
      • Description — Values : Realised BPM: L4-ICS2-03 Perform risk analysis. Triggering Task/Event: T-03-01 - Notify assessment complete to Person filing and T-03-02 Notify assessment complete to Carrier tasks. High level description of the tasks realised by the action: The Person filing and potentially the Carrier are notified about the assessment completion.
      • Pre-conditions — Values : An Assessment Complete Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N03 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Assessment Complete Notification has been received by the EO system.

      IE3Q01

      • Name — Values : IE3Q01
      • Description — Values : Realised BPM: L4-ICS2-03 Perform risk analysis. Triggering Task/Event: T-03-03 - Notify DNL to Person filing and T-03-04 - Notify DNL to Carrier tasks. High level description of the tasks realised by the action: A Do Not Load notification is submitted to the Person filing and to the Carrier.
      • Pre-conditions — Values : A Do Not Load Request has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3Q01 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, a Do Not Load Request has been received by the EO system.

      IE3Q02

      • Name — Values : IE3Q02
      • Description — Values : Realised BPM: L4-ICS2-03-01 Send referral. Triggering Task/Event: T-03-01-01 - Request additional information from Person filing task. High level description of the tasks realised by the action: The Person filing is notified about the request for additional information.
      • Pre-conditions — Values : An Additional Information Request has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3Q02 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Additional Information Request has been received by the EO system.

      IE3N04

      • Name — Values : IE3N04
      • Description — Values : Realised BPM: L4-ICS2-03-01 Send referral. Triggering Task/Event: T-03-01-02 - Notify additional information request to Carrier task. High level description of the tasks realised by the action: The Carrier is notified about the request for additional information submitted to the Person filing.
      • Pre-conditions — Values : An Additional Information Request has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N04 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Additional Information Request Notification has been received by the EO system.

      IE3Q03

      • Name — Values : IE3Q03
      • Description — Values : Realised BPM: L4-ICS2-03-01 Send referral. Triggering Task/Event: T-03-01-04 - Request HRCM screening from Person filing task. High level description of the tasks realised by the action: The Person filing is notified about the HRCM screening request.
      • Pre-conditions — Values : A High Risk Cargo and Mail Screening Request has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3Q03 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, a High Risk Cargo and Mail Screening Request has been received by the EO system.

      IE3N05

      • Name — Values : IE3N05
      • Description — Values : Realised BPM: L4-ICS2-03-01 Send referral. Triggering Task/Event: T-03-01-05 - Notify HRCM screening request to Carrier task. High level description of the tasks realised by the action: The Carrier is notified about the HRCM screening request submitted to the Person filing.
      • Pre-conditions — Values : A High Risk Cargo and Mail Screening Request has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N05 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, a High Risk Cargo and Mail Screening Request Notification has been received by the EO system.

      IE3R04

      • Name — Values : IE3R04
      • Description — Values : Realised BPM: L4-ICS2-04 Process arrival of means of transport. Triggering Task/Event: T-04-05 - Notify successful registration and MRN to Person filing task. High level description of the tasks realised by the action: The Person filing is notified about the successful registration of the Arrival notification and the corresponding MRN.
      • Pre-conditions — Values : An Arrival Notification has been received from the EO system and this notification has been semantically and syntactically validated.
      • Payloads — Values : This action receives the message IE3R04 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an Arrival Registration Response has been received by the EO system.

      IE3N08

      • Name — Values : IE3N08
      • Description — Values : Realised BPM: L4-ICS2-04 Process arrival of means of transport. Triggering Task/Event: T-04-07 - Notify control to Person filing task. High level description of the tasks realised by the action: The Person filing is notified about controls.
      • Pre-conditions — Values : A Control Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N08 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, a Control Notification has been received by the EO system.

      IE3N09

      • Name — Values : IE3N09
      • Description — Values : Realised BPM: L4-ICS2-06-01 Handle AEO notification. Triggering Task/Event: T-06-01-01 Notify Person filing (AEOS) about controls and T-06-01-02 - Notify Carrier (AEOS) about controls tasks. High level description of the tasks realised by the action: Both the Person filing and the Carrier are potentially notified about controls.
      • Pre-conditions — Values : An AEO Control Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N09 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an AEO Control Notification has been received by the EO system.

      IE3N07

      • Name — Values : IE3N07
      • Description — Values : Realised BPM: L4-ICS2-04 Process arrival of means of transport. Triggering Task/Event: T-04-06 - Notify House consignments in incorrect state to Person notifying the arrival and (as of Release 3) T-04-29 - Notify House consignments in incorrect state to Person filing and T-04-33 - Notify House consignments in incorrect state to Notify Party High level description of the tasks realised by the action: The Person notifying the arrival and, as of Release 3, (potentially) the Notify Party and (potentially) the Person filing are notified about the incorrect state of the House consignments.
      • Pre-conditions — Values : An ENS in Incorrect State Notification has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3N07 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an ENS in Incorrect State Notification has been received by the EO system of the Person notifying the arrival and, as of Release 3, (potentially) by the EO system of the Notify Party and (potentially) by the EO system of Person filing.

      IE3R08

      • Name — Values : IE3R08
      • Description — Values : Realised BPM: L4-ICS2-13 ENS Consultation. Triggering Task/Event: T-13-02 – Send ENS consultation results. High level description of the tasks realised by the action: The Party requesting consultation is notified about the consultation results.
      • Pre-conditions — Values : An ENS consultation results (IE4R06) has been submitted by the ICS2 CR Application, received and forwarded by the ICS2 TI Application.
      • Payloads — Values : This action receives the message IE3R08 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : Upon successful execution of this service action, an ENS consultation results has been received by the EO system.

      IE3Q04

      • Name — Values : IE3Q04
      • Description — Values : Realised BPM: L4-ICS2-08 Invalidate filing. Triggered Task/Event: E-08-01 - ENS filing Invalidation Request Received event. High level description of the tasks triggered by the Action after the reception of an ENS Invalidation Request message: Semantic and syntactic validation is performed on the received message; (NOT IN BPM) The IE4Q06 message is built based on the received message (IE3Q04 message); The ENS Invalidation message (IE4Q06 message) is submitted to the Common Repository.
      • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
      • Payloads — Values : This Action receives the message IE3Q04 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : The possible post-conditions are the following: An error has been identified during the validation and an error notification is submitted to the EO system (T-08-02 Notify error in invalidation of ENS filing task). The ENS filing invalidation is rejected (E-08-07 ENS filing invalidation request rejected event); The validation succeeded and the invalidation of the ENS filing is submitted to the ICS2 Common Repository Application (T-08-03 – Submit ENS filing invalidation request to CR task and E-08-02 - ENS filing invalidation request submitted event).

      IE3Q05

      • Name — Values : IE3Q05
      • Description — Values : Realised BPM: L4-ICS2-13 Consult ENS. Triggered Task/Event: E-13-01 - ENS consultation request received event. High level description of the tasks triggered by the Action after the reception of an ENS consultation request: (NOT IN BPM) Semantic and syntactic validation is performed on the received message; (NOT IN BPM) The IE4Q09 message is built based on the received message (IE3Q05 message); The ENS consultation request message (IE4Q09 message) is submitted to the Common Repository.
      • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
      • Payloads — Values : This Action receives the message IE3Q05 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : The possible post-conditions are the following: The consultation of the ENS filing is submitted to the ICS2 Common Repository Application (T-13-01 – Submit ENS consultation request to CR task and E-13-04 – ENS consultation request received from HTI). An error has been identified during the validation and an error notification is submitted to the EO system.

      IE3N06

      • Name — Values : IE3N06
      • Description — Values : Realised BPM: L4-ICS2-04 Process arrival of means of transport. Triggered Task/Event: E-04-01 - Arrival notification of the means of transport received event. High level description of the tasks triggered by the Action after the reception of an Arrival notifications of the means of transport message: Semantic and syntactic validation is performed on the received message; The Arrival notification is registered and a MRN is assigned to it; (NOT IN BPM) The IE4N07 message is built based on the received message (IE3N06 message); The Arrival notification (IE4N07 message) is submitted to the Common Repository; (NOT IN BPM) The IE3R04 message is built based on the received message (IE3N06 message); The Person Filing is notified about the successful registration and the MRN (IE3R04 message).
      • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
      • Payloads — Values : This action receives the message IE3N06 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : The possible post-conditions are the following: An error has been identified during the validation and an error notification is submitted to the EO system (T-04-02 – Notify Error task). The Arrival of means of transport notification is rejected (E-04-02 –Arrival of means transport notification rejected event); The validation succeeded, the invalidation of the ENS filing is submitted to the ICS2 Common Repository Application (T-04-04 – Submit arrival notification task) and the EO system is notified about the successful validation (T-04-05 – Notify successful registration and MRN to Person filing task, Notify Party EO systems are conditionally notified about the succesful registration (T-04-26) and E-04-03 Arrival notification submitted event).

      IE3R02

      • Name — Values : IE3R02
      • Description — Values : Realised BPM: L4-ICS2-03-01 Send referral. Triggered Task/Event: E-03-01-02 Additional information response from Person filing received event. High level description of the tasks triggered by the action after the reception of an Additional Information response message: (NOT IN BPM) Semantic and syntactic validation is performed on the received message; (NOT IN BPM) The IE4R02   message is built based on the received message (IE3R02 message); The Additional Information Response message (IE4R02 message) is submitted to the Common Repository.
      • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
      • Payloads — Values : This action receives the message IE3R02 as payload (mind that this payload may contain binary files). Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : The additional information response from Person filing is submitted to the ICS2 Common Repository application (T-03-01-03 – Submit additional information response from Person filing task and E-03-01-03 Additional information response provided event).

      IE3R03

      • Name — Values : IE3R03
      • Description — Values : Realised BPM: L4-ICS2-03-01 Send referral. Triggered Task/Event: E-03-01-05 - HRCM screening outcome received from Person filing event. High level description of the tasks triggered by the action after the reception of an HRCM screening outcome message: (NOT IN BPM) Semantic and syntactic validation is performed on the received message; (NOT IN BPM) The IE4R03 message is built based on the received message (IE3R03 message); The HRCM Screening outcome (IE4R03 message) is submitted to the Common Repository.
      • Pre-conditions — Values : The sender of the ENS Filing Message has been authorised by Customs by registering its certificate via the UUM&DS system.
      • Payloads — Values : This action receives the message IE3R03 as payload. Details on the message are available in the Technical Service Contract Document [R02].
      • Post-conditions — Values : The HRCM screening outcome is submitted to the ICS2 Common Repository application (T-03-01-06 Submit HRCM screening outcome task and E-03-01-06 HRCM screening outcome provided event).

      Liste des messages

      ‌

      ‌

      Source : https://mgi-team.atlassian.net/wiki/spaces/DOCI5/pages/3269099523