Hierarchy
SLL-NFE (Software Component) xNFE⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring⤷
/XNFE/CUS (Package) Customizing
IMG Activity
| ID | /XNFE/TCUFNF | NF-e: Define Service Status Request for Authority (SEFAZ) |
| Transaction Code | /XNFE/83000035 | (empty) |
| Created on | 20140103 | |
| Customizing Attributes | /XNFE/TCUFNF | NF-e: Define Service Status Request for Authority (SEFAZ) |
| Customizing Activity | /XNFE/TCUFNF | NF-e: Define Service Status Request for Authority (SEFAZ) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /XNFE/NFE_TSRV |
Use
In this Customizing activity, you configure the settings that the system needs for the automatic request of system availability for NF-es of the SEFAZ system and the responsible contingency system. You are required to request this status and can control the status request dependent on your batch planning or document volume. To do so, you can use the following parameters for each combination of Brazilian region and system environment:
- Frequency of status request in seconds
- Version for XML data for NF-es
- Time zone
- Testing of the contingency system: The following options are available:
- SEFAZ has priority, contingency system is also checked: The system availability of the SEFAZ system is tested first; if SEFAZ is unavailable, the responsible contingency system is tested. If both systems are available, the NF-es are sent to SEFAZ.
- SEFAZ has priority, contingency system is not checked: The system availability of the SEFAZ system is tested first; the responsible contingency system is not tested. If the SEFAZ system is unavailable, the NF-es cannot be sent to the contingency system.
- Contingency system has priority, SEFAZ is also checked: The system availability of the contingency system is tested first; if the contingency system is unavailable, SEFAZ is tested. If both systems are available, the NF-es are sent to the contingency system.
If the status request reports that the system is available, SAP Nota Fiscal Eletronica (SAP NFE) continues the electronic communication process. If the system is unavailable, you can continue the process manually in the monitors of the application.
- Definition of the responsible contingency system:
- 43 Rio Grande do Sul (RS, tpemis = 7)
- 91 National (AN, tpemis = 6)
- SC SCAN System (tpemis = 3)
Requirements
To be able to run the service status check, data must be maintained in the following Customizing activities:
Standard settings
Activities
Specify the region whose SEFAZ system you want to query and define whether you want to locate an available live or test system in the region.
Specify the control parameters for the service status request.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /XNFE/V_TCUFNF | V - View | SM30 |
History
| Last changed by/on | BEUNINGS | 20140103 |
| SAP Release Created in | 900 |
