13) NF-e: Maintain Version of Message Types
Here it is determined which XML version is used for individual message types when communicating with authorities.
SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Maintain Version of Message Types (/XNFE/V_XMLVERNF)
If you are issuing Outbound NFe you need to maintain the entries below:
If you are also using the “Receiver Acknowledgment” you need to maintain 4 new EVE:
210200 – Confirmação da Operação
210210 – Ciência da Operação
210220 – Desconhecimento da Operação
210240 – Operação não Realizada
14) NF-e: Define Query for Service Status for Authority
Enter here the settings to automatic query of system availability for NF-e on SEFAZ and the responsible contingency system. You are required to query this status and can control the status query dependent on your batch planning or document volume.
SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Define Query for Service Status for Authority (/XNFE/V_TCUFNF)
To each cUF where you will issue a NF from you have to maintain an entry here.
Maintain the Interval in seconds and the timezone according to where the Business Place region is located and for contingency system you maintain 43, 91 or SC where:
43 – SVC Rio Grande do Sul
91 – SVC Ambiente Nacional
SC – SCAN
– cUF using SVC-AN (91) – Sefaz Virtual de Contingência Ambiente Nacional: AC, AL, AP, DF, ES, MG, PB, RJ, RO, RR, RS, SC, SE, SP, TO
– cUF using SVC-RS (43) – Sefaz Virtual de Contingência Rio Grande do Sul: AM, BA, CE, ES, GO, MA, MS, MT, PA, PE, PI, PR, RN
You can still use the SCAN in parallet with the SVC contingency mode (I will talk later about SVC)
15) NF-e: Maintain Batch Parameters
Define the parameters for collecting NF-es in batches and perform the batch request for each region used in your company.
These parameters have a high influence on the CPU usage, disk usage, and overall performance of SAP NFE. Therefore, change the parameters according to your business needs and try to create the batches with the highest NF-e number in an acceptable time. Be aware that using small values for Max. Collecting Time, Max. Batch Size or Max. Number of NF-es increases the number of batches. This can provoke processing performance problems. The creation of NF-e batches is also influenced by the way you scheduled the job for the batch report.
SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Maintain Batch Parameters (/XNFE/V_BATCHPAR)
What that means?
You are sending 1 NF per batch.
How that affects performance then?
If you issue 100 NFes on ECC there are 100 NFes to be signed which means +/- 4 Messages exchanged with PI to each document, or a total of 400 XML (the signature is individual)
In a scenario of 1 NF per batch as above, 100 batches , each batch will have +/- 6 messages sent to XI to be sent to SEFAZ and +/- 6 Messages at the XI to answer back to the GRC, that gives you 1200 XML between PI and GRC and 200 communications between PI x SEFAZ.
In the proposed (recommended) scenario below, with 50 NFes per batch to the same 100 NFes:
2 Batches, 24 XML exchanged with PI and 4 communication with the Internet/SEFAZ
With more NFes per batch will save some CPU and database and less communication with the Internet:
16) NF-e: Maintain Process Determination for Outbound NF-es
SAP NFE offers several processes for issuing an NF-e (as designed by the brazilian authorities). If you have to deal with many NF-es, NF-es can be sent in batches to reduce your data traffic and to speed up the overall processing time. If you have to deal with only few NF-es, these NF-es can be sent individually without batch. The determination of the issuing process takes place when the NF-e is received from the feeder system according to this customizing at SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Maintain Process Determination for Outbound NF-es (/XNFE/V_OUTBPD))
The following processes are available:
Issue of NF-e with Batch
Issue of NF-e without Batch
Issue of NF-e Cancellation
Issue of NF-e Skipping
Send NF.e to Business Partner
Send NF-e Cancellation to Business Partner
Issue of NF.e Number Gap Skipping
Issue of NF-e with EPEC and Batch
For more details of every individual process, refer to the link below (where I copied the information above because I was too lazy to explain with my own words):
Looks easy so far right? You don’t need to jump to an abyss anymore…