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

L4-ICS2-07 – Amend filing

Emplacement : Documentation ICS2 > BPM L4 Process Description

Liée aux US :

:yellow_star: https://mgi-team.atlassian.net/browse/US-2413

https://mgi-team.atlassian.net/browse/US-2418

:yellow_star: https://mgi-team.atlassian.net/browse/US-2438

https://mgi-team.atlassian.net/browse/US-2420

  • Organisation: National Customs Administration of Responsible Member State
  • Input: Amendment of ENS filing
  • Description: An original ENS filing can be amended by an amendment filing which refers to the original filing by its MRN. The amendment of an ENS has to be filed by the declarant or the representative that filed the original ENS filing.
  • Output (Final situation): The ENS filing is amended and processed again with the amended data depending on the lifecycle of the original ENS.

1.1 Business Process Model

Figure 8: L4-ICS2-07 Amend ENS filing sub-process

1.2 Tasks

1.2.1 T-07-01 – Perform syntactical & semantical validation on amendment of ENS filing

  • System component: TI
  • Input: Amendment of ENS filing received
  • Description: The received amendment is validated in an automated process. It comprises the validation against the message rules and conditions, as well as the relevant reference data which is 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 the error description will be generated

1.2.2 T-07-02 – Submit amendment of ENS filing to CR

  • System component: TI
  • Input: Positively validated amendment of ENS filing
  • Description: The amendment of ENS filing is submitted to the CR via the message IE4AXX [Msg: C_ENS_xxx_AMD].
  • Output (Final situation): The amendment of ENS filing was submitted to the CR.

1.2.3 T-07-03 - Notify completion of amendment of ENS filing

  • System component: TI
  • Input: Amendment of ENS filing completion notification received
  • Description: The message IE3N10 [Msg: E_AMD_NOT] is generated and sent to the Person filing the amendment. It informs about successful amendment of the ENS filing.
  • Output (Final situation): The Person filing is notified that the amendment of ENS filing was processed successfully.

1.2.4 T-07-04 – Notify error in amendment of ENS filing

  • System component: TI
  • Input: Notification of error in amendment of ENS filing received
  • Description: The information about a validation error is sent to the Person filing the amendment via the message IE3N99 [Msg: E_ERR_NOT].
  • Output (Final situation): The Person filing the amendment is informed about unsuccessful ENS lifecycle validation of the amendment of ENS filing.

1.2.5 T-07-05 – Notify ENS lifecycle validation error

  • System component: TI
  • Input: ENS lifecycle validation error received
  • Description: The information about unsuccessful ENS lifecycle validation is sent to the Person filing the amendment via the message IE3N01 [Msg: E_ELF_VLD_NOT].
  • Output (Final situation): The Person filing the amendment is informed about unsuccessful ENS lifecycle validation of the amendment of ENS filing.

1.2.6 T-07-14 – Notify error

  • System component: TI
  • Input: ENS filing amendment rejection received
  • Description: The Person filing is notified about the fact that the ENS filing amendment was rejected due to low quality data 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.3 Events

1.3.1 E-07-01 – Amendment of ENS filing received by TI

  • System component: TI
  • Description: An amendment of an original ENS filing is received by the TI.

1.3.2 E-07-02 - Amendment of ENS filing submitted

  • System component: TI
  • Description: An amendment of an original ENS filing is submitted to the CR.

1.3.3 E-07-03 – Amendment of ENS filing completion notification received

  • System component: TI
  • Description: TI received information that the original ENS filing was amended by the CR.

1.3.4 E-07-04 – Completion of amendment of ENS filing notified

  • System component: TI
  • Description: The completion of amendment of ENS filing was notified to the Person filing.

1.3.5 E-07-05 – Amendment of ENS filing rejected

  • System component: TI
  • Description: The amendment of ENS filing is rejected.

1.3.6 E-07-06 – ENS lifecycle validation error received

  • System component: TI
  • Description: TI received information that the ENS lifecycle validation of the amendment of ENS filing in the CR was not successful.

1.3.7 E-07-07 – ENS lifecycle validation error notified

  • System component: TI
  • Description: TI notifies the Person filing an amendment of an ENS filing that the ENS lifecycle validation of the amendment of ENS filing in the CR was not successful.

1.3.8 E-07-12 – ENS filing amendment rejection received

  • System component: TI
  • Description: The ENS filing amendment was rejected due to low quality data.

1.3.9 E-07-13 – ENS filing amendment rejected

  • System component: TI
  • Description: The ENS filing amendment was rejected due to low quality data via the message IE3N99 [Msg: E_ERR_NOT].

1.4 Gateways

1.4.1 G-07-01 – Syntactical & semantical validation successful?

  • System component: TI
  • Input: Validation results
  • Description: In case the results were positive, the answer is 'Yes', otherwise it is 'No'.

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