ALERT CONFIGURATION IN SAP NFE (NFE_ALRT_CAT)

For a correct error handling, it is essential to send negative acknowledgments from PI to NFE if a communication problem occurs (Due to the fact that the outbound scenario relies on asynchronous messages from NFE to PI). For PI double-stack installations, the alert category NFE_ALRT_CAT has to be created using transaction ALRTCATDEF (see SAP Note 1741486). This is not required for AEX (Java-only) PI installations.

You can also use the alerts function in SAP NetWeaver Process Integration (SAP NetWeaver PI) to send e-mail notifications to the responsible persons in your company about possible communication problems. The e-mail relays the error status message. You can specify the e-mail notification recipients for each integration scenario.

For more information about configuring alerts in SAP NetWeaver PI, see Alert Configuration in the SAP Library under  Functional View SAP NetWeaver by Key Capability Process Integration by Key Capability SAP NetWeaver Exchange Infrastructure Runtime Central Monitoring .

ü  RISKS / IMPACTS
- In case of errors when transmitting data to SEFAZ during authorization, cancellation and skipping processes, it will not be possible to use restart message functionality in SAP BO NF-e 10.0 monitors.
- Potential risk of losing transactional data.

ü  RISKS / IMPACTS
- Execute transaction ALRTCATDEF and create alert category NFE_ALRT_CAT. It should look like this:

Additionality, please verify the SAP Note “1741486"- Communication issues between GRC NFE, PI and SEFAZ.

Fonte 1: Alert Configuration in SAP NFE 
Complementar: Importância da Configuração do Lote (SAP NFE-GRC 10.0)