Alarms b+ dgtal SII

Open

This parameterization should be done in project because its configuration is system and project requeriments specific.

In this documentation page will be explained possible examples of how to parameterize alarms for each trigger/alarm type provided by b+dgtal SII product. Should be kept in mind that this parameterization is offered by the own product, but it can be adapted to the needed of each project.

Expiration (CADUCIDAD) alarms for FC/FI/SD/MM Invoice

To parameterize an alarm of this type, it will be necessary to create an entry in this table and choose alarm type ‘CADUCIDAD’ and the appropiate product object, for example ‘FACTURA FI’ for FI Invoice.

Open

In ‘Alarm conditions’ table may include entries to set invoices conditions. For example, Company, or other field that belongs to the object extraction table (edocument).

In that way several expiration alarms can be created, setting in each one of them an alarm condition, for example, a specific Company (in case it is necessary, for example, to send several expiration alarms to different recipients, depending on the Company).

In the ‘Initial values’ table it will necessary to create a single entry indicating the days (natural) that need to pass for an entry (not sent) trigger an expiration alarm together with factory calendar (if it is required).

In the ‘Final values’ table it will necessary to indicate all the status that should not create expiration alarm, that is, invoices final status. Therefore, for that status no expiration alarms will be created and, if at some point they were created, when they change to that status, they will turn off.

Status (ESTADO) alarms for FC/FI/SD/MM Invoice

To have status alarms for invoices it will be necessary to create an entry in this table for the alarm type ‘ESTADO’ and the appropiate product object, for example ‘FACTURA FI’ for FI Invoice.

In ‘Alarm conditions’ table may include entries to set invoices conditions. For example, Company, or other field that belongs to the object extraction table (edocument).

In that way several status alarms can be created, setting in each one of them an alarm condition, for example, a specific Company.

In the ‘Initial values’ table it will necessary to indicate the different status you want they trigger an alarm. Status shown in this table will create the alarms.

In the ‘Final values’ table it will necessary to indicate all the status that will turn off the alarm.

Status (ESTADO) alarms for batches (LOTES)

To have status alarms for batches it will necessary to create an entry in this table for the alarm type ‘ESTADO’ an product object ‘LOTE’.

In ‘Alarm conditions’ table may include entries to set batches conditions. For example, Company, or other field that belongs to the object extraction table (edocument).

In that way several status alarms can be created, setting in each one of them an alarm condition, for example, a specific Company.

In the ‘Initial values’ table it will necessary to indicate the different status you want they trigger an alarm. Status shown in this table will create the alarms.

In the ‘Final values’ table it will necessary to indicate all the status that will turn off the alarm.

Note: In Alarms SII old module there were alarms for invoices accepted with errors, because these had a time limit for correction higher than the others. With this new alarms module, this alarms type can be configurated as another status alarm.

Below are listed possible status for invoices and batches.

Invoices

Batches