/
3.1.3.7. eDocument self-management on Invoice IDs changes

3.1.3.7. eDocument self-management on Invoice IDs changes

This functionality works as follows:
When a change is performed for a FI accounting document (this improvement does not include modifications to FI-CA documents) the following logic applies:

  1. Checks if the functionality is activated through the parameter "CHANGE_ID_FACTURA" with the flag "X" in the transaction "/EDGE/SII_CU_011 - Parametrización MW in SII". Otherwise the functionality will not be applied.
  2. Checks if there is a new eDocument of Invoice Issued, Invoice Received, Investment Good or Intercommunal Operation, otherwise the process ends at this point.
  3. Check if there has been a change in the Invoice ID fields. For this, the previous and new data are mapped and compares for changes, otherwise the process ends at this point.
  4. Set if its needed to generate a cancelled or an annulment eDocument because of the changes in the Invoice ID. To do this, the status history is checked for the original eDocument. In the case the is a register status for "Accepted" or "Accepted with errors", without the status "To include batch", then the cancellation or annulment eDocument is generated for the Invoice ID, these eDocuments must be included in batches and sent following the usual flow.
  5. The original eDocument status will be reset to the "Include Batch" status.
  6. The previous entry in the relationship table between eDocuments and Invoice IDs will be deleted and the new management of obsolete for the new invoice ID will be made.

Manual actions to activate the functionality.

1.   Installation of orders.

Installation of the corresponding version with the usual procedure.

2.   Activation of new eDocument types for company.

When transporting the order, new types of eDocument are added for the losses by change of Invoice ID, these types have to be activated for the companies of the project. For this we use the transaction "/EDGE/SII_CARGA_SOC" with description "SII - Charge of companies param."
The entries corresponding to the companies will have been marked in yellow:
 
You must mark the entries and press the "Reload Company" button, then we will select the transport order for the transport to the different systems, if we start the transaction again we will see the entries marked in green:

3.   Add the batch determination inputs for intermediate.

Since new types of batch are added with their respective mapping for new declines by change in Invoice ID, the conditions must be added to create such batches, the recommended logic is that it be done only for intermediate type. For this we will enter the transaction "/EDGE/SII_CU_007 - Conditions for SII lots" and we will create the following entries:
Write-offs for change in Invoice ID for FE.

And the conditions for the criterion.

Write-offs for change in Invoice ID for FR.

And the conditions for the criterion.

Write-offs due to change in Invoice ID for BI.

And the conditions for the criterion.

Write-offs due to change in Invoice ID for OI.

And the conditions for the criterion.

4.   Activation of the parameter CHANGE_ID_FACTURE.

Finally, the parameter "CHANGE_ID_FACTURE" must be activated in the transaction "/EDGE/SII_CU_011 - MW parameterization in SII". This parameter serves as a switch and allows us to activate and deactivate the functionality quickly. In order for the functionality to be active, the value "X" must be given to this parameter:

Avvale 2024