Configuring SII alarms
Transaction:
/EDGE/SII_CU_002
...
Alarm Master
At this point the alarm types are defined, for there are three origins for which the alarm occurs:
- Status: The alarm is created when an e document reaches a certain status (retained, released, rejected with errors, accepted with errors, accepted submission).
- Expiration: The alarm is created according to the number of days elapsed to control that the shipment occurs within the period established by the AEAT.
- Scaling: This alarm is created when a previous alarm has produced a number of notifications without correcting the risk situation.
...
Once the alarm master is configured, the following assignments could be made:
- Triggers by state:
...
- eDoc. Process: /EDGE/SII - Sistema Información Impuestos
- Company: Company Code
- Process Step: Create batch, Accept batch, Reject batch, etc.
- Expiration Triggers
The expiration is set, to be notified periodically, or when the expiration is near.
- Alarm-channel relationships
For each alarm the channel to be used is indicated. By default the mail will be configured. Each time an alarm occurs, a notification will be sent to the users who have the role.
- Communiction chanels
At this point you must configure the mode by which the notification is to be made. The classes for the channels will be provided by the technical team.
- EDoc final states
At this point the states that are considered final are parameterized for which they will cease to issue expiration alarms and that when they are reached they will produce the shutdown of the existing alarms.
