| Info | ||
|---|---|---|
| ||
Note1: This functionality is not yet available for FUSE. It will be notified when it is active. Note2: This new functionality is available from version 1.7. |
1.TimeOut Problem AEAT
Depending on the traffic that occurs on the Tax Agency's servers, when the traffic is high, when waiting for a response, it returns a TimeOut, and in the case of a synchronous service, it is not possible to make a new request to retrieve the response. However, they process the Invoice as a server, but as long as it takes to process it, the connection cannot be kept open and ends up being closed, leaving the response incomplete.
This creates an inconsistency in the statements of the invoices between AEAT and SAP, since in AEAT these invoices have been processed, and since they are not able to return the response to the middleware, the statements of these invoices in SAP are not updated and remain in "Included in Batch" status.
We have been informed that the AEAT cannot do anything to improve the situation, so it is possible that this problem will be repeated on more than one occasion.
2. How to solve the problem of Time Out.
A process has been developed from the product to help customers deal with this problem. A new state has been created for the batches, "Time Out", so that when a response TimeOut occurs between the middleware and the AEAT, this error is picked up by FUSE or PI which sends a specific error code to SAP to mark the batch with this new state:
This change of status only affects batches, not intermediates.
If this happens, the invoices in SAP are in an "Included in Batch" status, as you can see in the image above, while in AEAT these invoices will have been processed and will have a status, either Accepted or Accepted with Errors, or without registering if any invoice has been rejected.
To resolve these state inconsistencies you have to do certain manual actions: