2.1.20 Sending Obsoletes to Dashboard

Sending obsolete invoices to the dashboard can be asynchronous or synchronous. To indicate which mode to use, the middleware table must be set as described on page 8.1.2.1.8.1. MW Customizing in SII

Synchronous operation works as follows. When a document becomes obsolete, either due to the creation of its retirement or a new acquisition with the same invoice ID, the invoice information is now sent to the Dashboard to be marked as obsolete and aligned with the SAP system. This only happens when the invoice has been previously sent. If the invoice was not in a sent batch, the invoice is not registered in the Dashboard so this information cannot reach the Dashboard.

On the other hand, the asynchronous operation what it is, to store in the table /edge/sii_obs_db the data of the invoice to be sent to the Dashboard in the future. Subsequently, there is a report that can be scheduled periodically as a job to send the invoices stored in this table to the Dashboard to be marked as obsolete.

With product version 1.7.5, a new functionality is enabled. Sending obsolete files to the Dashboard through exceptional processing. In addition to the existing operation mentioned in the previous lines, from this version on, when the status of an eDocument is changed in the cockpit to Aceptado→Obsoleto or Obsolete, the process of sending obsolete documents to the Dashboard is carried out. This means that, if it is set to be synchronous, the data of this invoice will be sent to the Dashboard to be marked as obsolete. If, on the other hand, it is set to be asynchronous, it will be stored in the /edge/sii_obs_db table for later sending.

If at this time, when the invoice is in the Obsolete or Aceptado→Obsoleto state, the exceptional processing is undone, this process will be executed again to send the information to the Dashboard and leave the invoice "not obsolete" again. The process is the same, if the parameterization is synchronous, the information will be sent to the Dashboard at that time, if it is asynchronous, the entry in the /edge/sii_obs_db table will be deleted so that it is not sent to the Dashboard.

This new functionality for exceptional obsolete Dashboard submissions also works exclusively for invoices that are included in the batch and have been sent to the Dashboard at some point.