L4-ICS2-01 - Register filing
Emplacement : Documentation ICS2 > BPM L4 Process Description
Liée aux US :
- Organisation: National Customs Administration of the Responsible Member State
- Input: Received ENS filing
- Description: The ENS filing is validated in an automated process. The validation comprises semantical and syntactical checks in order to ensure workability and data consistency as well as the identification of the kind of filing. If the ENS filing is not valid: it is rejected; the person filing is notified of the rejection and of the errors that caused the rejection. If the ENS filing is valid: It is registered; an MRN is generated and allocated to the received filing. The Person filing is notified of the registration and the MRN which was allocated to the filing. When the Carrier is different from the Person filing and the Carrier can be identified from the data derived from the filing, and the Carrier has requested to be notified and is connected to the system he will also be notified.
- Output (Final situation): The filing is either registered or rejected.
1.1 Business Process Model
Figure 2: L4-ICS2-01 Register filing sub-process
1.2 Tasks
1.2.1 T-01-01 – Perform syntactical and semantical validation
- System component: TI
- Input: ENS filing
- Description: The received ENS filing is validated in an automated process. It comprises the validation against the message rules and conditions, as well as the relevant reference data which are valid at the date of the reception. The messages rules and conditions and relevant reference data are defined in [R02] ICS2 Information Exchange Messages. In case the ENS filing contains characters which are not Cyrillic, Latin or Greek, the ENS filing is rejected with “102” “Not allowed Unicode character” with pointer(s) to the elements resulting in the rejection.
- Output (Final situation): The validation will have the following possible outcomes: · Successful; · Unsuccessful, in which case o the error description will be generated o the ENS filing will obtain the state 'Rejected'
1.2.2 T-01-02 – Register ENS filing and assign MRN
- System component: TI
- Input: Valid ENS filing
- Description: Valid ENS filing obtains the state 'Registered'; an MRN is generated and assigned to the received ENS filing.
- Output (Final situation): The ENS filing was registered and MRN has been generated and assigned to it.
1.2.3 T-01-03 – Submit registered ENS filing
- System component: TI
- Input: Registered ENS filing
- Description: The registered ENS filing is submitted from the TI to the CR for further processing via the message IE4FXX [Msg: C_ENS_xxx_DEC] (The xxx is placeholder for the number of the filing, i.e. F10).
- Output (Final situation): The ENS filing is available at the CR.
1.2.4 T-01-04 – Notify successful registration and MRN to Person filing
- System component: TI
- Input: Registered ENS filing
- Description: The registration of the ENS filing and the MRN assigned to it are notified to the Person filing via the message IE3R01 [Msg: E_ENS_REG_RSP].
- Output (Final situation): The Person filing is notified about the registration of the ENS filing and the MRN assigned to it.
1.2.5 T-01-05 – Notify successful registration and MRN to Carrier
- System component: TI
- Input: Registered ENS filing
- Description: The registration of the ENS filing and the MRN assigned to it are notified to the Carrier via the message IE3R01 [Msg: E_ENS_REG_RSP].
- Output (Final situation): The Carrier is notified about the registration of the ENS filing and the MRN assigned to it.
1.2.6 T-01-06 - Notify error
- System component: TI
- Input: ENS filing with unsuccessful validation results
- Description: The Person filing is notified about the fact that the ENS filing was rejected and about the errors that caused its rejection via the message IE3N99 [Msg: E_ERR_NOT].
- Output (Final situation): The notification of error is generated and sent to the Person filing.
1.2.7 T-01-09 – Notify ENS lifecycle validation error
- System component: TI
- Input: Unsuccessful validation results
- Description: An error was sent by the CR and it is communicated to the Person filing through the TI. The error notification will be sent via the message IE3N01 [Msg: E_ELF_VLD_NOT] which includes the indication(s)/explanation(s) of the error(s) which caused the failure of the validity check of the ENS filing.
- Output (Final situation): The Person filing is notified of the errors of the ENS filing.
1.3 Events
1.3.1 E-01-01 – ENS filing received
- System component: TI
- Description: A person lodges an ENS filing.
1.3.2 E-01-02 – ENS filing registered
- System component: TI
- Description: ENS filing is registered and, where applicable, MRN is generated.
1.3.3 E-01-03 – ENS filing rejected
- System component: TI
- Description: ENS filing is rejected.
1.3.4 E-01-06 – ENS filing acceptance notification received
- System component: TI
- Description: The ENS filing acceptance notification is received by the TI.
1.3.5 E-01-07 – ENS lifecycle validation error notification received
- System component: TI
- Description: The ENS lifecycle validation error is sent to the TI.
1.3.6 E-01-08 – ENS lifecycle validation error notified
- System component: TI
- Description: The ENS filing rejection is notified to the Person filing.
1.3.7 E-01-09 – ENS filing acceptance notification for Carrier received
- System component: TI
- Description: ENS filing acceptance notification for Carrier is received by the TI from the CR.
1.3.8 E-01-10 – ENS filing registration notified to Carrier
- System component: TI
- Description: ENS filing registration is notified to Carrier
1.3.9 E-01-11 – ENS filing rejection due to low quality data received
- System component: TI
- Description: ENS filing rejection due to low quality data is received from the CR via the message IE4N99 [Msg: C_ERR_NOT].
1.4 Gateways
1.4.1 G-01-01 - Syntactical & semantical validation successful?
- System component: TI
- Input: Outcome of Task: T-01-01 – Perform syntactical and semantical validation
- Description: In case the validation was successful, the answer is 'Yes', otherwise it is 'No'.
1.4.2 G-01-02 - Carrier to be notified about successful registration?
- System component: TI
- Input: Validated ENS filing
- Description: The carrier is to be notified when · Carrier is connected to the TI; · Carrier has requested to receive 'ENS registration' notification messages IE3R01 [Msg: E_ENS_ REG_RSP]. This preference is stored in IE3R01 [Msg: E_ENS_REG_RSP].
Source : https://mgi-team.atlassian.net/wiki/spaces/DOCI5/pages/3280306225