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.

Untitled.jpg

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 signing the messages need to be deployed at a Net Weaver java server. This service can then be reached by SAP PI for signing the documents.

Process Explained(Sending NFE):

Untitled.jpg

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.sap-ag.de/~sapidb/011000358700000299122008E/NFE10_MASTER_GUIDE.pdf

Thanks

Gaurav Ranjan

To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Ricardo Viana

    Nice blog about NF-e solution.

    I´m specialist on it, almost 12 projects. If you need some help, let me know.

    Ready for new XML version 3.10, will be released soon.

    Kind regards,

    Ricardo Viana.

    (0) 
    1. chandra prasath sarathy

      Hi Ricardo Viana,

      Currently i am having one development in ERP to add two xml tags for vICMS and motdesICMS tags through CL_NFE_PRINT~FILL_ITEM method.

      so could you please guide me to proceed the development with some technical information ?

      Thanks in Advance.

      (0) 
    2. Sayi Pattapagala

      Hi Ricardo and team,

      Could you please help me on this

      01) I need to install SAP nfe 10.0 .My question is as per SAP documentation



      Basically you need ABAP stack to install core NFE and PI system dual stack to install PI content.


      -ABAP stack to install core SAP nfe (SAPBO SLL-NFE 10.0)


      – PI dual stack to install PI content (SLL-NFE 10.0)



      SAP ECC is connected to SAP ABAP stack where nfe is installed.

      SAP NFE ABAP server is connected to SAP PI where nfe content is installed

      SAP PI is connected to external Brazil gov software system.


      Option1:


      SAP ECC …>SAP PI dual stack ……..>Brazil gov external system


      In this option, you install core NFE and PI content in the same system


      Option 2:


      SAP ECC…….>SAP Nfe ABAP stack …..>SAP PI …>Brazil gov external system



      In this option you will have separate ABAP stack for core SAP nfe and PI system will be separate.


      Option3:


      Latest, I’m reading you do not need ABAP stack for SAP nfe 10.0, you can install directly on PI 7.31 java stack ( not dual stack) core nfe, PI content etc.


      when I’m  designing SAP landscape for SAP nfe which option is best. If you could through some light and documentation will be really appreciated.


      Thank you every one.











      (0) 
    3. Genildo Sena

      Hi Ricardo,

      We have a project to migrate the current vendor of NFe to SAP GRC NFe.

      Is there any restriction to install the SAP GRC NFe at the server on the ECC 6 is installed?

      Best Regards,

      Sena

      (0) 

Leave a Reply