How to use the new NF-e monitor to solve some issues
Hello Guys,
With the latest SP’s in GRC, SP16-18, and also the last one of this year, SP19 to be released in the last week of december, we have introduced several new monitors for NF-e and batch processing with new functionalities.
In order to make the usage easier we compiled the main changes in this blog post:
1- New outbound monitors for Nfe 3.10
1.1 New outbound monitor for NF-e
/XNFE/NFE_OUTB_MONITOR
1.2 New outbound monitor for NF-e Batch
/XNFE/NFE_BATCH_MONITOR
2- New authorization object for the NF-e monitor and Event Outbound monitor:
2.1 Authorization object /XNFE/NFE6 with the parameters below:
● /XNFE/CNPJ
Your own tax number
● ACTVT
Allowed Activity
More details can be seen in the GRC NFE 10.0 Security Guide.
3- New functionalities in the monitors
3.1 New functionalities on the Outbound NF-e Monitor
-Continue Process
-Continue B2B Process
-More functions
-Request Status Check
-Update Feeder System
-Repeat Process Step
-Finish Skipping
-Send XML File
-Request Events
The details of each functionality can be reviewed in the GRC help page
3.2 New functionalities in the Batch Outbound Monitor
-Restart
-Finish Batch Process
The details of each functionality can be reviewed in the GRC help page
4- Special scenarios ( Most common errors )
4.1 Special Scenarios for NF-e in processing
| 108 | -> Service Interrupted Momentarily |
| 109 | -> Service Interrupted Indefinitely |
| 204 | -> Rejection: Duplicated NF-e |
| 205 | -> Rejection: NF-e is already denied on the SEFAZ database |
| 206 | -> NF-e is already skipped in the SEFAZ database |
| 217 | -> Rejection: NF-e does not exist on the SEFAZ database |
| 256 | -> An NF-e number in the range is already skipped in the SEFAZ database |
| 563 | -> There is an existing skipping request for the same range |
| 656 | -> Improper Consumption (wait at least 3 minutes before try again) |
| 999 | -> Rejection: Unexpected Error |
The details on how to proceed with each one of the scenarios are in the GRC help page
4.2 Special Scenarios for Batches in processing
| 108 | -> Service Interrupted Momentarily |
| 109 | -> Service Interrupted Indefinitely |
| 215 | -> Rejection: XML schema validation error |
| 426 | -> Rejection: Failure decompressing the data area |
| 426 | -> Rejection: Failure decompressing the data area |
| 516 | -> Rejection: XML schema validation error |
| 517 | -> Rejection: XML schema validation error |
| 545 | -> Rejection: XML schema validation error |
| 656 | -> Improper Consumption (wait at least 3 minutes before trying again) |
| 999 |
-> Rejection: Unexpected Error |
The details on how to proceed with each one of the scenarios are in the GRC help page
In order to make the scenarios a little bit clear we have created the following videos showing how to handle specific rejections/errors that might occur in the NF-e processing:
What to do when NF-e is rejected with status 204 in SAP GRC NFe
What to do when NF-e is APPROVED in GRC and waiting for response in ERP
What to do when NF-e is APPROVED in GRC, but with ERROR in last step and waiting for response in ERP
What to do when BATCH is in process for a long time with no response – Option 1
What to do when BATCH is in process for a long time with no response – Option 2
What to do when BATCH is with error status in GRC
What to do when BATCH is with error status in GRC due to rejection 999
Best regards,
On behalf of Renan Correa
Hi Thiago and Renan,
I could not find in the new monitors a view/place to show the message IDs from the event's B2B. Is it available somewhere?
If not, what procedure you recommend to ask for this? Idea Place only?
Here is what I could check and where I don't have the message ID:
-> Event monitor (with B2B error):
Status Overview:
History:
B2B Status overview:
B2B History:
Thank you!
PS.: if you prefer I can open a thread for this.
Kind regards,
Eduardo Hartmann
Hi Eduardo,
This info isn't available in the event outbound monitor. I'm afraid the only option would be the idea place.
regards,
Renan Correa
Hi NFe Experts Team,
We went live with XML 3.10 Version recently and it was a very smooth transition. Thank you for all the help & guidance provided during this transition.
I need your help in one issue where NF-e is approved by SEFAZ and is green in GRC and still waiting for response in ERP. We tried the steps provided in one of the above video (video # 3) but were still not able to process the document in ERP.
We got below error :
Doc. status "Autorizado" is not allowed for document XXXX with sys. comm. status "Não enviado". "Message no. J1B_NFE044"
Can you suggest/ guide with some more pointers for this kind of issue.
We tried to replicate these cases in Test environment but were not successful and have only 2 such cases in Production environment.
Regards,
Nishikant Nibandhe
Hi Nishikant,
Good to hear that everything is working fine.
I believe that in your case it should be video 2, no? I mean, is the process completed in GRC? If so, it should be video 2 instead of 3. Anyway, for the error it seems that the statuses in ERP are not consistent for waiting a response. Normally, for approval it should be:
Action Required = ' ' (blank)
DOCSTA = ' ' (blank)
SCSSTA = '0'
MSSSTA = 'A'
If that is not the case, it is probably to reason for the error.
Best regards,
Tiago.