Event scenario – missing tag
This post is for everyone that uses GRC as the messaging system. You probably already had an issue on the response of the event request due to the missing tag <tpEvento>. Of course, this only happens to some SEFAZ, not all. In those cases, it was necessary to abandon the batch process and then request a status query, but checking the monitor we couldn’t understand the reason for the rejection.
This week, we have released SAP Note 2074727 – Complete missing fields in event batch answer for rejected events. With this Note, now there are two possibilities:
1 ) During the response of the batch, GRC tries to find the correct NF-e (if there is only one in the batch for example) and if this is successufuly the rejection is finished and ERP is updated;
2 ) If that is not possible, the Event will have an error in the Event Monitor (as before), but the status will be set to ‘999’ and then the user has perform the status query and the rejection should return to ERP.
Let us know if you have questions on the scenario.