SEND corrected NFe's which were REJECTED by SEFAZ.

[kiran_chowdary3]

Hello All,

We are facing below issues while sending(FROM ECC) the Rejected Nfe's from SEFAZ after correcting the error.

Please check the below steps we were following and help us overcome this issue.

1. NFe is sent with wrong data(intentionally).
2. SEFAZ rejects the Nfe with status code 531 with MSS status A (Request for authorization received by MS).
3. NFe is corrected from J1B2N and again sent through J1BNFE(Using SEND).
4. Momentarily we observed MSS status as A(Request for authorization received by MS).
5. Post that, ON REFRESH we could not see any records in the document history section in J1BNFE for the current user action.
6. Post that, we could see the error "Doc. status "Authorized" is not allowed for document <XXXXXXX> with sys. comm. status "Not sent".
7. However we could see the same, entries in J_1BNFE_INVALID for the Nfe document with status 100, which means successfully processed, but the same is not reflected in J1BNFE in ECC and Batch monitor in GRC.
8. In Batch Monitor in GRC, the status of the activity is ERROR and status code is 100.

These issues are only for the REJECTED==>CORRECTED==>SEND issues cases.

Regards

Kiran Kumar P

[former_member227801]

Hi Kumar,

I didn't understand fully what you want to achieve. If you're "intentionally" changing the data inside NFe doc to force an error, you have to be aware of the reflections of this error you're creating in both systems ECC/GRC. Otherwise, both systems may not understand the internal errors you are forcing and you will get stuck in something that it doesn't make sense for the NFe doc that you're testing.

Regards

Simeão Delphino