Sap Brazil Grc Nfe Overview 3a5v5h

SAP Brazil GRC NFE Overview January 15, 2014

Introduction :    

Companies selling products in Brazil must send each invoice electronically to the government for validation before shipping their goods. Companies purchasing goods in Brazil must check the electronic invoice at the government before receiving the goods. Bottom line: The government wants to be sure they are getting all of their tax revenue. Companies need to handle these activities with an automated solution that can scale to high volumes of invoices and meet their business process requirements.

Architecture of SAP GRC NFE : The SAP GRC NFE solution is usually installed on a separate SAP application server and utilizes SAP Net weaver PI to encrypt and send the data to the Brazilian SEFAZ agency.

Software Components:    

NFE Core application : Software Component SAPBO SLL NFE 10.0 for the core application of SAP Business Objects NFE. This includes three software units : SAP_ABA 7.02 SAP_BASIS 7.02 PI_BASIS 7.02 PI ESR Content SAPBO SLL-NFE 10.0 on SAP Net Weaver PI system. Adobe Document services (ADS) installation is optional for displaying preview of the forms to be printed.

Integration: Based on the system landscape we can connect one or several logistics system to NFE such as SAP ERP. Integration Steps:

  







Setup of system communication between SAP ERP – NFE – SAP PI: RFC connections need to be setup in SM59 so that the three systems can communicate with each other for data communication. Business partners in SAP NFE : Business partners that will be taking part in the electronic exchange of NFE need to be setup in the core application. Status code information is also stored in the core application. SLD Setup : The SLD is mandatory for using SAP Nota Fiscal Electronica content in SAP Net Weaver PI. This is required to maintain details of the business systems/technical systems which will be involved in the process. ESR Import : SAP Standard software component SLL-NFE 10.0 import is required in SAP Net weaver PI. Note : The ESR content will be SAP standard so there is no need to develop integration objects in ESR. Integration Directory Configuration : ID configuration is required to create configuration scenarios based on integration scenarios from ESR. We have to maintain the adapter configuration like SOAP/HTTP/XI which are required for end to end communication between SAP , Authorities and business partners. Digital Signature Service : The authorities require that all request messages like authorization, cancellation, and skipping requests are digitally signed. A web service for g the messages need to be deployed at a Net Weaver java server. This service can then be reached by SAP PI for g the documents.

Process Explained(Sending NFE):

The Process explains the following steps : 

Creating electronic invoice billing document in SAP ECC.

     

Sending digitally signed packaged NFE to authorities for their approval. These packages must be grouped as per format and size restrictions of the authorities. The communication will be setup using a web service call from SAP PI to authorities system. Sending a status request for the sent NFE’s to authorities after a certain time frame. Updating the status of billing document in ECC based upon the response received from Authorities. The status can be either authorized or denied. One can send only the authorized NEF’s to their business partners using agreed PI adapters such as FTP/HTTP/SOAP. In the similar manner we can receive authorized NFE’s from business partners in to SAP ERP system. The main processes are sending/receiving a new NFE, Cancellation of NFE, skipping of NFE and events for additional information.

Summary : By integrating to the relevant systems, SAP Nota Fiscal Electronica is a centralized data store for the message exchange, regarding the communication with the authorities, and other companies systems in the B2B scenarios. SAP NFE is the central platform for the legally required storage of the exchanged files.

Monitoring and Alerting: SAP NFE Monitors : NF-e monitor Batch Monitor B2B Monitor Service status monitor SAP PI Monitoring: Queue monitoring(SMQ1/SMQ2) Adapter monitoring Message monitoring(SXMB_MONI) RWB monitoring Alerting : For error handling it is necessary to setup alerts in SAP PI for any communication failure alerts. Alert category NFE_ALRT_CAT has to be created using transaction ALRTCATDEF for achieving this.

References : SAP help : http://help.sap.com/saphelp_grcnfe10/helpdata/en/93/cc40a6f0434083a64e23823175a8ff/frameset. htm Master Guide : https://websmp207.sapag.de/~sapidb/011000358700000299122008E/NFE10_MASTER_GUIDE.pdf Thanks Gaurav Ranjan

NFe Outbound / NFe 10.0 / NFe GRC – Part 1 Date: July 12, 2015Author: leandropia

https://sapbr.com/

The first NFe (Electronic Nota Fiscal) was issued in Brasil in September, 2006 and that became mandatory for most of the companies in 2009/2010. While official Layout changed from 1.00 to 2.00 and then to 3.10 (actual) along of those years, SAP delivered and has been enhancing over the years the NFe Solution to follow those changes and meet the legal requirements. Many people that I know still reject to engage in a NFe Project because they are afraid to fail for not having the opportunity to do it before.

The idea of this (and the next postings) it is to show you that implementing the NFe changes can be simple if you think simple. Before coming to this blog, there are several other sources of information that you can go first. I would recommend checking them first: SCN NF-e & SPED Community – Content is in portuguese but you can always use google translator or use that as an excuse to learn Portuguese (I’m kidding, don’t waste your time learning portuguese)

NFE Boas discussões – Leia antes de postar – Here a list of several different topics, a little bit out of date but still good to review SAP Nota Fiscal Eletrônica – Directly from SAP Help Before you start configuring, I also recommend to review the OSS Notes below: 2056762 – Guidelines for NF-e layout 3.10 SAP Notes installation 2057942 – Guideline for NF-e layout 3.10 implementation in ERP and SAP NFE 2060171 – [3.10] Announcement Note – NF-e Layout 3.10 2123768 – KBA [3.10] NF-e 3.10 go-live checklist for SAP NF-e GRC 2125859 – KBA [3.10] NF-e 3.10 go-live checklist for SAP ERP And don’t forget to implement the latest SLL-NFE Package (currently SP21) 2170295 – SAPK-90021INSLLNFE: Package 21 for SLL-NFE I am not going to discuss a scenario in specific. You will see here only the general concept, but keep in mind that before start configuring, you should work on an assessment, map the scenarios, the different processes and requirements for issuing NFe in your company/customer. So, let’s see how to configure the NFe system (Aka GRC NFe). Most (but not all of them) of the Configuration in SPRO are organized as following:

1) Maintain Own Tax Numbers It couldn’t be simpler than that: Here you enter your company’s CNPJ (one entry per business place), Type a description (Business Place Name for instance), and the UF region in which the CNPJ is ed.

Table: /XNFE/V_TCNPJ SPRO > Nota Fiscal Eletronica > General Settings > Maintain Own Tax Numbers

2) Digital Signature Configuration This is usually maintained by Basis, so, if you are not comfortable handling it or you don’t have the proper authorization, don’t get shy asking someone on Basis’s team to do that for you… 3) Maintain System Security Information For every Secure Store and Forward (SSF) application, you must import the certificates that you have purchased from the authorities. This is done in the Trust Manager. Here define and monitor the personal security environments (PSEs) in the SAP system, which are used for digital signatures and encryption in SAP systems. SPRO > Nota Fiscal > General Settings > Signature > Maintain System Security Information 4) Maintain Application-Dependent SSF Information You receive an overview of existing SSF applications and you must create entries for each of your own tax numbers. Here you specify the applicationindependent parameters for using the SSF (secure store and forward) functions.

The applications that use the SSF functions do not all have to use the same security environment. SPRO > Nota Fiscal > General Settings > Signature >Maintain ApplicationDependent SSF Information

5) Name the Logical Destination Here is one more activity that it is usually maintained by someone on Basis team, the RFC connection. Starting from naming the logical destinations, create the Logical Destination entries to be used in the RFC connection in this customizing. SPRO > Nota Fiscal > Communication to ERP Back End System > Name the Logical Destination Define the logical systems to which you want to connect your SAP Nota Fiscal Eletronica (SAP NFE) system. A logical system needs to be defined for each back-end (ERP) system to enable your SAP Nota Fiscal Eletronica system to establish a connection with the ERP system. 6) Create RFC Connection

The parameters of an RFC destination are used to control the Remote Function Call (RFC). That’s how the NFe, ECC and PI clients will exchange communication between them. You need an RFC destination for each logical system that you want to connect with your SAP Nota Fiscal Eletronica system. 7) Maintain System Response for Own Tax Numbers You use the tax number of your company to define the storage location of the digital certificate that you will use for digital signatures, and whether or not you use the productive or homologation system environment, the digital certificate is required. SPRO > NOTA FISCAL > OUTBOUND > MAINTAIN SYSTEM RESPONSE FOR OWN TAX NUMBERS

For each CNPJ, maintain the Business Place description, KeyStorageView, Key Storage Element and SSF Application (ask Basis if you don’t know).

8) Define Authority’s Tax Code Here it is defined the codes and their descriptions that the authorities can use as answers to an electronic message in communication for handling notas fiscais. Based on this list, you can see in the application how official code affects the status of the NF-e. The assignment of a code to a clear description makes it easier for you to initiate follow-on activities and fix issues. SPRO > Nota Fiscal > Outbound > NFe > NF-e: Define Authority’s Status Code Table /XNFE/TSTAT

You can find an updated list here in this link:

Tabela atualizada das mensagens de retorno/erro da SEFAZ Continue…

NFe Outbound / NFe 10.0 / NFe GRC – Part 2 9) Maintain Control Parameters for Process Flow Here you can make the settings for the process steps processing the NF-e, CT-e, events. The process steps are derived from the business process that is assigned to the document. In this customizing (/XNFE/PROCSTEP) you define what step in the process (process flow for business – table /XNFE/PROCFLOW) can be automatic (FLAG_AUTO = x) and the ones that are mandatory (FLAG_MAND = x). You can for example, deactivate the B2B Output to an specific scenario (NFe issued w/o batch) or do that to an specific receiver CNPJ/Sender CNPJ.

See below an example suggested by Jose Nunes in this SCN Post: To deactivate the B2B Events (Correction Letter and Cancellation) only to the Partner Carrier Step 1: SM30 Via SM30, select table /XNFE/PROCSTEP and click Maintain. Go to Menu -> Selection -> By contents…, select Process Step ID = B2BOUTCA Uncheck the field Nec. Step. That will make possible to deactivate this step via SPRO. Step 2: SPRO SPRO > Nota Fiscal Eletronica -> Outbound -> Maintain Control Parameters for Process Flow To the processes EVB2BNFE and EVB2BNFC do the changes below:

The possibilities are according to your business needs.

See a list of process that you can manipulate:

10) Activate B2B Scenarios for Business Partners Here is where you will determine the business partners with whom you want to exchange electronic documents. You will maintain here for example the Customers that will receive B2B communication when you are issuing a NFe (Like the XML via email for

example). To do that, add customer’s CNPJ and Select “X Communication via PI”. To process stock transfer orders (STO) – Plant to Plant into same Company Code – you must enter the B2B communication to DB for every branch’s CNPJ. You don’t have to go through PI for that, since your branches share the same Database. SPRO > Nota Fiscal Eletronica -> Outbound -> Activate B2B Scenarios for Business Partners

11) Activate B2B Scenarios for Natural Persons Same as above, however you maintain here F (Natural Person IDs) SPRO > Nota Fiscal Eletronica -> Outbound -> Activate B2B Scenarios for Natural Persons

12) NF-e: Maintain Connected Government Systems This is a new customizing that came with the 3.10 Layout changes on SAP. It can’t be simpler than that: you configure the settings that the system needs for deciding to which government system your messages are to be sent. SPRO > Nota Fiscal Eletronica -> Outbound -> NF-e -> NF-e: Maintain Connected Government Systems

On Logical Destination you enter the RFC Logical Destination (Steps 5 and 6 on previous post in this blog). Company’s Own CNPJ, that’s easy… your business place CNPJ’s; CUF is the Region where the Business Place is located and Environment you will use Homologation and Productive system accordingly.

NFe Outbound / NFe 10.0 / NFe GRC – Part 3 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 U 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)

If you are using the settings below:

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 U 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): NFe Outbound Processing 17) Activate Services for Interface Display The monitoring options in SAP NFE gives you the ability to tracking the status of NF-es, batches, Service Status and etc, via communication process between NFE application and SEFAZ system. You can also use the monitors to, in case of errors, troubleshooting, resending and rechecking of NF-es, batches, events and etc. To activate the monitors (and that has to be done at the client level), go to SICF, Select Service Name XNFE and hit enter. Use the navigation tree for the Virtual Hosts/Services : default_host > sap > bc > webdynpro > xnfe You will have to activate (by right clicking and selecting Activate) the following monitors to NFe Outbound: NF-e 

/nfe_monitor_new



/nfe_outb_monitor



/event_monitor



/batch_monitor_new



/nfe_batch_monitor



/event_batch_monitor



/STATUS_MONITOR_NEW



/nfe_servsta_monitor



/NFE_LISTSTA_MONITOR



/nfe_analytics_out

istration 

/_mass_xml



/ssf_maintenance



/nfe_monitor_arch



/NFE_OUTB_MONITOR_arch



/nfe_fisc_workplace_arch

18) NFe Outbound Roles and Authorization SAP NFE contains the following roles with their relevant authorization objects. 

/XNFE/WP_NFE_OUT_MONITOR This role does not contain authorizations and is therefore only meant to create and set up the menu for the NFE Outbound Monitors. You can copy this role to adjust the menu according to your requirements. This role can be combined with other roles in a composite role.



/XNFE/WP_NFE_ This role is intended for the NFE . It does not contain authorizations and is therefore only meant to create and set up the menu. You can copy this role to adjust the menu according to your requirements. This role can be combined with other roles in a composite role.

19) NFe Jobs You will have to schedule the jobs below. You can do that using SM37: 

/XNFE/NFE_BATCH_PROCESS for sending batches and batch requests



/XNFE/NFE_B2B_SEND for sending authorized NF-es to the Business Partners



/XNFE/NFE_SKIP_SEND for sending skip requests



/XNFE/NFE_CONTINUE_PROCESS for repeating the status update to ERP in case of technical problems



/XNFE/NFE_CHECK_SRV_STATUS for checking the Web Service availability of SEFAZ, SCAN and SVC



/XNFE/EVENT_BATCH_SEND for sending Events (cancellation and correction letter)



/XNFE/GET_ACKNOWLEDGMENT for processing negative acknowledgements from PI

I am ending here the overview on NFe Outbound configuration. As I mentioned in the 1st part of this posts, the intention is to give you a general idea and to show the steps that you have to follow to have you SAP NFe (SAP GRC) communicating with SEFAZ Authority systems. Neither PI/XI or ERP Settings are described in those posts.

Don’t forget to check all the OSS Notes and reference documents that I mentioned here: Outbound / NFe 10.0 / NFe GRC – Part 1 And yes, be prepared to many issues. NFe is not like vanilla ice cream… you will have to work also on BAdI enhancements to the XML and DANFE Printing, but that’s is whole another subject…

Brazil legal and taxes reports and others legal requirements Date: October 1, 2013Author: leandropia

This posting is a summary of subjects that you will see on the next posts here in this blog. Maybe not on this sequence, since I am planning mix concepts with technical details and examples. MONTHLY LEGAL REPORTS Most of Companies in Brazil are subjected to many taxes and legal reports that must be submitted monthly, bi-monthly, yearly and etc; These reports are submitted to Municipal (City), State and/or Federal Tax Authorities. As interpretation of the law changes from company to company according to the business, size, special requirements and several other combination of possibilities, this always will make it more difficult to SAP develop a solution that will work 100% for your company. For that reason you must keep in mind that: you will need to have the right resources (like FI, CO, MM, SD, ABAP) to configure and make the standard reports work and to the ones that are

not delivered by SAP you will need to develop it on SAP (or use a 3rd partner software doing interface on SAP for these reports). Before start talking about what is delivered by SAP and what it is not, I want to bring to your attention that, using a 3rd partner software as tax solution for the reports that are not delivered by SAP should be the LAST option. In a future post I will explain why you should not start considerign to use a bolt-on or interface for that instead using SAP as much as possible. It is very difficult to list ALL legal / tax reports and files mandatory for all companies in Brazil, but I will list the most common in use: 

Tax Registration PIS/COFINS (Apuração da PIS/COFINS)



Tax Registration ICMS (Model 9) (Apuração do ICMS (Modelo 9))



Tax Registration ICMS-ST (Apuração do ICMS-ST)



Tax Registration INSS Fonte (Apuração do INSS Fonte)



Tax Registration IPI (Model 8) (Apuração do IPI (Modelo 8))



Tax Registration IRRF (Apuração do IRRF)



Tax Registration ISS Fonte (Apuração do ISS Fonte)



Tax Registration PIS/COFINS/CSLL Withholding (Apuração do PIS /COFINS/CSLL Retido)



CIAP – Fixed Asset Tax Credit Control (CIAP – Controle de Crédito do Ativo Permanente)



Goods on 3rd hands control (Controle de Terceiros)



LALUR/CSLL



DACON – Social Contribution Tax Registration Control (DACON – Demonstrativo de Apuração de Contribuições Sociais)



DARF (DARF)



DCTF – Federal Tax Debit/Credit declaration (DCTF – Declaração de Débitos e Créditos Tributários Federais)



DIPJ (DIPJ)



DIRF – Income Tax Wht (DIRF – Declaração do Imposto de Renda Retido na Fonte)



DNF – Nota Fiscal Report (DNF – Demonstrativo de Notas Fiscais)



Production and Inventory Report (Model 3) (Estoque e Produçao (Modelo 3))



Phisical Stock (Model 7) (Estoque Fisico (Modelo 7))



FCONT



Electronic Service Nota Fiscal (NFSe) (Geração de Nf de Serviços Tomados (arquivo eletronico))



GIA – ICMS Information File Monthly and Yearly (GIA – Guia de Informação do ICMS (Mensal e Anual))



GIA-ST – ICMS-ST Information File Monthly and Yearly (GIA/ST – Guia de Informação do ICMS Substituição Tributária)



GNRE – State Taxes Collection File (GNRE – Guia Nacional de Recolhimento de Tributos Estaduais)



Electronic GPS (GPS Eletrônica)



ICMS Collection files (Guias de Recolhimentos do ICMS)



IRPJ / LALUR



ISS book (51, 53, 56) (Livros de ISS (51, 53 ou 56))



Incoming Nota Fiscal Report (Model 1) (Livros Fiscais (Modelos: 1, 1A))



Outgoing Nota Fiscal Report (Model 2) (Livros Fiscais (Modelos: 2, 2A))



Inter-state Operation Report (Model 12) (Operações Inter-Estatudais (Modelo 12))



PER/DCOMP (IPI Credit File) (PER/DCOMP (Arquivos de Notas de crédito de IPI))



SEFIP – Natural Person INSS (SEFIP (INSS de autônomos))



SPED ing ECD (SPED ECD Contábil)



SPED Contributions EFD (PIS/COFINS) (SPED Contribuições EFD)



SPED EFD-IRPJ (E-LALUR)



SPED Fiscal EFD (ICMS/IPI) (SPED Fiscal EFD)



Free Trade Zone Control (Zona Franca de Manaus)

You probably will say: Wow, this is a lot! Yes, but I have to say that it is missing many others. Some of them are very specific for some industries, for example, Gas & Oil, Pharmaceuticals, Chemicals, Transportation, Services providers, and etc., they all have very specific reports to their kind of businesses. Only 30% of the reports above are covered in Standard by SAP, nevertheless it will be necessary to configure and adjust to your business model; The others 70% if your company is required to report, you must consider develop it on SAP using ABAP development. On the next posts I will talk about the reports that are delivered by SAP and the most important ones, such as: SPED ing ECD, SPED Contributions EFD (PIS/COFINS), SPED Fiscal EFD (ICMS/IPI). OTHER LEGAL OBLIGATIONS These are others legal requirements for most of the companies in Brazil, they are not a legal report, but legal documents, webservice based communication and

real time process required to keep your business running, invoicing your customers and receiving goods in your company: o Outgoing Electronic Nota Fiscal (NFe, NF-e) o Incoming Electronic Nota Fiscal (NFe Inbound) o CT-e (Freight Electronic Nota Fiscal, aka, Electronic CTRC) o Electronic Services Nota Fiscal (NFSe, NFS-e) o Receipt Acknowledge (Manifesto do Destinatário) o FCI (Importation Content File, or, Ficha de Conteúdo de Importação) o Others SINIEF ADJUSTMENT (the newest ones) • I will talk about these Legal Obligations above in separated posts, otherwise, this post will never finish