Sap layout 4.0 nota fiscal eletronica full version#

In the proposed (recommended) scenario below, with 50 NFes per batch to the same 100 NFes:Ģ Batches, 24 XML exchanged with PI and 4 communication with the Internet/SEFAZ 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. 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) SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Maintain Batch Parameters (/XNFE/V_BATCHPAR) The creation of NF-e batches is also influenced by the way you scheduled the job for the batch report. This can provoke processing performance problems. Number of NF-es increases the number of batches. Be aware that using small values for Max. 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. These parameters have a high influence on the CPU usage, disk usage, and overall performance of SAP NFE. You can still use the SCAN in parallet with the SVC contingency mode (I will talk later about SVC)ĭefine the parameters for collecting NF-es in batches and perform the batch request for each region used in your company. – 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 – 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 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: To each cUF where you will issue a NF from you have to maintain an entry here.

SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Define Query for Service Status for Authority (/XNFE/V_TCUFNF) You are required to query this status and can control the status query dependent on your batch planning or document volume.

If you are also using the “Receiver Acknowledgment” you need to maintain 4 new EVE:ġ4) NF-e: Define Query for Service Status for AuthorityĮnter here the settings to automatic query of system availability for NF-e on SEFAZ and the responsible contingency system. If you are issuing Outbound NFe you need to maintain the entries below: SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Maintain Version of Message Types (/XNFE/V_XMLVERNF) Here it is determined which XML version is used for individual message types when communicating with authorities. Visit SAP Support Portal's SAP Notes and KBA Search.This post is a sequence of NFe Outbound / NFe 10.0 / NFe GRC – Part 2 and NFe Outbound / NFe 10.0 / NFe GRC – Part 1ġ3) NF-e: Maintain Version of Message Types

Sap layout 4.0 nota fiscal eletronica full version#

Click more to access the full version on SAP for Me (Login

This is a preview of a SAP Knowledge Base Article. NT2021.004, Legal Change, 2021004, NF, NF-e, Brazil, TN, NT, Nota Técnica, Vehicle Usage, Vehicle Type, Espécie de Veículo, Tipo de Veículo, Tipo do Ato Concessório, Grupo de observações de uso livre para o item, Fisco, Contribuinte, UDO, DDIC, Brazil, Brasil, localization, localização, KBA, nt2021.004, legal change, 2021004, nf, nf-e, tn, nt, nota técnica, vehicle usage, vehicle type, espécie de veículo, tipo de veículo, tipo do ato concessório, contribuinte, fisco, udo, ddic, brazil, brasil, localização, localization, FI-LOC-NFE-BR-OUT, Outbound, XX-CSC-BR-NFE, Use FI-LOC-NFE-BR-OUT, XX-CSC-BR-SD, Use FI-LOC-SD-BR, CA-GTF-CSC-EDO-BR, Document Compliance Brazil, FI-LOC-NFE-BR-IN, Inbound, FI-LOC-SD-BR, Brazil, SLL-NFE, Nota Fiscal Electronica (NFe), XX-CSC-BR-NFEIN, Use FI-LOC-NFE-BR-IN, LOD-LH-NFE, SAP Document Compliance outbound nota fiscal, Bug Filed About this page