Implement SAP GRC NFE for Brazilian e-Invoicing

SAP GRC NFE 1.0 - New Solution Introduction &
Implemention Best Practices
Henrique Pinto
Business Card
Company: SAP
Posted on Jun. 12, 2008 01:40 AM in Governance, Risk and Compliance, SAP
Process Integration (PI), SAP NetWeaver Platform, SAP xApps, Business
Solutions

1. Introduction
SAP GRC NFE is a product recently released by SAP that implements the requirements for Brazilian specific
electronic invoicing scenario. It handles several communication interfaces between the company's ERP(s)
system(s) and the relevant government systems; xml document handling; digital signatures for the xml
documents with specific requirements from the government; B2B communication between business partners
(suppliers and customers), among other functionalities.
However, in order to explain about the SAP GRC NFE solution, it's necessary to have some background on the
Brazilian NF-e project (NF-e stands for "Nota Fiscal eletrônica", which is Portuguese for Electronic
Invoice).

1.1. NF-e Project
http://www.nfe.fazenda.gov.br/
In Brazil, the NF-e project is part of a bigger government program called SPED (Sistema

Público de
Escrituração Digital, or Electronic Bookkeeping Public System), which is a nationwide project that intends
to eliminate all (or most of) the current paper-based legal reporting activities, replacing them for electronicbased operations.
Among these, collecting all the issued invoices, sending them to the relevant parties (transporters, customers
etc.) and storing them for auditioning purposes is one of the most expensive activities. The NF-e project, in
particular, brought some new concepts on how the invoice issuing process shall work in Brazil from now on:
for any company to be able to issue an electronic invoice (or an NFe, from now on), it has to be sent to
a validating government system, which will either approve, reject or deny that NFe (rejection is due to technical
issues, such as missing mandatory fields, invalid data etc.; denial is due to business issues, such as the issuing
company being in the government black list of tax evasion or something of that sort). So, from now on, the
government has actual control over the billing processes of the companies, and that's the big change in the
picture;
instead of storing the paper invoices for several years, now the companies have to digitally store the
electronic files which hold the NFe data and the approval data from the government;
instead of sending/receiving paper invoices, now the companies send electronic files to their customers
and receive such files from their suppliers, making it much easier to implement business to business (B2B)
integrations;
instead of the invoice following the goods transportation, now there is a paper auxiliary document,
called DANFe (short for NFe auxiliary document), that describes the NFe and follows the goods (the electronic
file is the document with actual legal value; the DANFe has actual no legal value, it's just a paper representation
of the NFe, with a pre-defined format, for facilitation purposes).

1.2. SAP NF-e solution portfolio
In order to cover the whole NF-e project requirements, SAP offers two products in its portfolio:
SAP ERP NFE: included in all SAP R/3 / ECC / ERP versions from 4.6C*: this solution, included in
SAP_APPL software component, gives all the necessary tools in order for the relevant sales (SD) and purchase
(MM) scenarios to be adjusted to work with electronic invoices; in order to generate the relevant messages and
to communicate with the government systems, a NF-e messaging solution is also necessary;
SAP GRC NFE: this product is the SAP NF-e messaging solution and its implementation will be
commented in details below;
* In 4.6C, for customers with extended maintenance contract only.

2. Installation
The SAP GRC NFE product is developed over the SAP NetWeaver platform by SAP GRC (Governance, Risk &
Compliance) team.
It consists of basically three logical components:
NFE core component (ABAP Add-on): delivered within SLL-NFE Software Component;
Digital Signature application (Java EJB): delivered within SLL-NFE-JWS Software Component;
XI Content for the SLL-NFE Software Component, with the relevant interface objects for NFE.
The logical landscape for GRC NFE is shown below:

The relation between logical and physical landscape is as shown below:
the NFE Core component is installed on a SAP WAS ABAP 7.00;
the NFE Java component is deployed on a SAP WAS Java 7.00;
the NFE XI Content is imported on Integration Repository of SAP PI 7.0;

Technically speaking, SAP Portal is not a requirement for GRC NFE to properly work, since the user interfaces
for GRC NFE are available through Web Dynpro for ABAP screens and properly delivered within the Core ABAP
component, together with the relevant user roles. But since the UI is web-based, it is also a good practice to
maintain it in the company's corporate portal, following SAP recommendation, for enhancing the user
experience, for security purposes, etc. Whether or not to maintain GRC NFE UI in SAP Portal, that must be
evaluated at project blueprint and sorted out with the customer.
For the installation of ABAP & Java NFE components, there are some pre-requisite software components, which
are described in the documentation referred below:
for the installation of the core component of SAP GRC NFE (SLL-NFE), please check SAP Note 1139220;
for the deploy of the Java component of SAP GRC NFE (SLL-NFE-JWS), please check the SAP GRC NFE
1.0 Master Guide (http://service.sap.com/instguides ->

G -> SAP GRC Nota Fiscal Electronica ->

Using SAP NFE 1.0);
for the import of the XI Content for SAP SLL-NFE SWCV, please check SAP Note 836200.
Regarding the logistics for the installation of these Application servers, it may be evaluated the possibility of
installing everything on a single instance, usually the PI instance, since it already contains both ABAP and Java

Web Application Servers.
However, the formal recommendation by SAP is to not install more than one application by instance, especially in
the case of SAP PI (for this recommendation, please check SAP NetWeaver 7.0 Master Guide:
http://service.sap.com/instguidesNW70 -> Installation) due to the possibility of causing performance
bottlenecks (because PI is a very resource-consuming application).
Nevertheless, at project time, it may be evaluated to go further with the single-instance landscape, at least for
DEV and QAS systems (for which performance does not play a much relevant role), thus reducing hardware
costs. But this has to be evaluated case by case (and aligned with the customer, who must be aware of the
risks).

If the customer does decide for the single-instance installation, please notice that GRC NFE, as any other SAP
application, needs a Business System in SLD with the Application Server role, to properly communicate with the
Integration Server. Hence, it is necessary a second Business System for GRC NFE in the WAS ABAP Technical
System of PI instance (meaning, a new client on WAS ABAP needs to be created, on which GRC NFE will run; the
Integration Server client should remain the same).

3. Implementation
3.1. Pre-requisites
In order for SAP GRC NFE to be able to receive the necessary data from the backend system, it is necessary that
the backend system is prepared to generate this data in the format that the government expects and to receive
the response messages, evaluate the results and continue the sales/purchase processes accordingly. It is also
necessary to create an interface between the backend system and SAP GRC NFE product so that the information
can be exchanged.
In case the backend is SAP ERP (which will probably be the case for most of the implementations), the
integration between SAP ERP and SAP GRC NFE is seamless, meaning that no development is necessary. The
only steps which are necessary is to set the "xNFe active" flag on the NF-e specific customizing view on ERP and
to create the relevant RFC destinations (from ERP to GRC NFE and vice-versa). These steps are described in
details in the GRC NFE documentation (discussed below).
For SAP ERP, the necessary tools in ERP side communicate with GRC NFE are released in Support Packages (it is
also possible to implement these view direct implementation of relevant SAP Notes). An overview on these
requirements can be found in SAP Note 989115. If you intend to search for the relevant notes, search for notes
in the XX-CSC-BR-NFE application area (for SAP_APPL Software Component).

In case the backend is not SAP ERP, communication interfaces with SAP GRC NFE can be easily designed
through SAP Process Integration to communicate with the standard GRC NFE inbound and outbound interfaces.
These interfaces are RFCs on the Core ABAP component, listed below:
/XNFE/NFE_CREATE: for incoming NF-e authorization requests;
/XNFE/NFE_CANCEL: for incoming NF-e cancellation requests;
/XNFE/NFE_SKIP: for incoming NF-e number skipping requests.

3.2. Documentation
In order to assist the technical consultants with implementing and configuring GRC NFE, SAP has developed an

Online Knowledge Product (e-learning) delivered as a RKT (Ramp-up Knowledge Transfer) for SAP GRC NFE 1.0.
It is available for free for Ramp-up customers and can be acquired by any other customers and consulting
partners (for price and purchase information, please access http://service.sap.com/okp -> Preview Content

Details & Buy and browse for GRC -> ONFE10 SAP GRC Nota Fiscal Electronica 1.0).

Once you've purchased it, the RKT can be directly accessed through the OKP home page, through the menu
to the right (just click on SAP GRC Nota Fiscal Electronica 1.0 on the list of available OKPs).

There is also an online help for the product, available through SAP Help Portal.

3.3. Configuration
As described above, the configuration steps for GRC NFE are covered by the RKT. However, due to the product
evolution, some enhancements have already been included in the Product, which were not yet reproduced in the
RKT material (it will be updated in time). Meanwhile, these points which are now missing in the RKT are
described below.

3.3.1. System Landscape Directory
Before the configuration of the NFE XI Content can be executed in the Integration Directory (as indicated in the
RKT), some tasks need to be performed in the SLD.
As indicated above, there are two application components for the GRC NFE internal components: 1 for the Java
component, 1 for the Core component (ABAP Add-on). Hence, two Business Systems (1 of type WAS Java and 1
of type WAS ABAP) are necessary in SLD, to represent these components.
Also, in order to properly configure all the scenarios (with the relevant routing conditions), it is necessary to add
the NFE Product & Software Components versions to the Technical/Business Systems. You find these in the
Software Catalog of SLD. The association should be as shown below.

The SAP Nota Fiscal Electronica 1.0 Product Version and the nested Software Component Versions are
included in SAP Component Repository Content (SAP CR Content) starting on version 3.10. To check the current
SLD CR Content version, in SLD home page, go to: Administration -> Details -> Data tab, and check
the

SAP CR Content Version value.

In order to update the SAP Component Repository in SLD, please check SAP Note 669669.

3.3.2. New Scheduling Rule for the Batch Processing Job
As of SLL-NFE SP02, a new behavior for the /XNFE/PROCESS_REPORTS report has been introduced.
Differently from what is commented on the RKT material, now this report can be scheduled as a Periodic Job, in
the same way of the Service Status check Job. The Job is still executed permanently but, in case of any failures,
it will be automatically restarted, thus guaranteeing a 24/7 processing without necessary human intervention.
The new functionalities also include a parallel execution control in order to avoid multiple instances of the report
of being executed.

3.3.3. Schema Validation
As of SLL-NFE SP02, the NFe Schema Validation was released. This validation makes sure that no wrongly
formatted data is included in the NFe XML messages. In order to activate the validation for a configured branch,
just mark the "Validation" flag in the Configure System Response for Each Tax Number (CNPJ)
customizing view for NFE, in SAP IMG (transaction code SPRO), as shown below.

If an NFe sent from backend is invalidated, an automatic message is sent back to the ERP with a rejection
status, so that the necessary corrective measures are taken, and the further processing steps (digital signature,
batch association etc.) are not executed. In order to check the validation log (with the invalidated fields), click
on the "Log Display" button of the NF-e Details screen, as shown below. A popup with the validation log will be
open.

3.3.4. BAdI for enhanced NF-e fields mapping
As of SLL-NFE SP02, it was also released a new BAdI for enhancing the mapping of the NF-e fields. The
standard mapping should be enough for most customers but, for those who have custom specific rules for some
fields (for example, special cases for some taxes, specific industry sector fields etc.), these can be evaluated
within this BAdI.
To implement the BAdI for NF-e fields mapping, just execute the

BAdI to Extend the NF-e with Feeder

System Data customizing entry for GRC NFE (also accessible through SPRO), as shown below.

3.3.5. Communication User Details
As of SLL-NFE SP03, two new user roles were released in order to make it easier to configure the
communication between the several components of the NF-e data exchange process.

These user roles can also be created through manual steps, following the recomendations of SAP Note
1223469.
On a simplified view, the communication process is as follows:

Each communication step is described below.

I - RFC Communication between ERP & GRC NFE
a) Communication from ERP to GRC NFE
In ERP, it is necessary to create a RFC Destination of type 3 (R/3), in order to send the NF-es to GRC NFE. In
this RFC Destination, define a service user from the GRC NFE system which contains the /XNFE/RFCSERV role.

A dialog user can be used temporarily for debugging & testing purposes, but should be avoided for productive
scenarios.

b) Communication from GRC NFE to ERP
In GRC NFE, it is also necessary to create a RFC Destination of type 3. This RFC Destination must be defined
with a service user from the ERP system with the necessary authorizations for the ERP processes (at least, the
S_RFC & F_NFBA authorization objects are necessary).

A dialog user can be used temporarily for debugging & testing purposes, but should be avoided for productive
scenarios.
There is also the necessity to associate this RFC Destination with the ERP Logical System Name (as described in
the RKT), in BD97 transaction (if necessary, create the ERP Logical System Name in the GRC NFE system
through BD54 transaction).

II - Proxy Communication between ERP & GRC NFE
a) Communication from GRC NFE to XI
In order for GRC NFE to communicate with XI, it is necessary to maintain a HTTP Destination (RFC Destination
of type H) in the GRC NFE system, pointing to the XI system. It needs to have the path prefix as
/sap/xi/engine?type=entry.

This HTTP Destination should use the PIAPPLUSER in order to log on PI.
Then, define this HTTP Destination in SXMB_ADM -> Integration Engine Configuration, in the
Corresponding Integration Server field, in the format "dest://<HTTP_Destination>", as shown below:

b) Communication from XI to GRC NFE
In order for XI to return the response messages to the GRC NFE system, it is necessary to create a HTTP
Destination in the XI system pointing to the GRC NFE system, with the same path prefix as above. As for the
user, create a service user with the /XNFE/PRXYSERV role.
In the Integration Directory, in the Receiver XI Communication Channel pointing to the GRC NFE system, use
this HTTP Destination, as shown below:

III - SOAP Communication between XI & Digital Signer
In order for XI to communicate with the Digital Signer, a user with at least the SAP_J2EE_GUEST role needs to
be used.
The Digital Signer Web Service address is always in the following format:

http://<server>:<port>/DigitalSignature/ws?style=document
where <server> and <port> are relative to the J2EE Engine where the Digital Signer was deployed.

IV - SOAP Communication between XI & Government Systems
The authentication for the communication from XI to the Government Systems is done through the use of digital
certificates, as described in the RKT, so no user details are needed.

4. Further Information
In order to further discusss about NF-e (government requirements) or the SAP NFE solution, the GRC forum on
BPX community can be used. Furthermore, on the short term, a portuguese language forum will be set up and
will have a NF-e subforum. I'll update the blog as soon as this forum has been released.
As any SAP product, GRC NFE is under SAP standard maintenance program. Thus, correction notes and new
functionalities within Support Packages are being released on a regular basis. So, it is a good practice to
regularly monitor SAP Support Portal for new Notes and SAP Software Distribution Center for new Support
Packages for GRC NFE. To do so, search for objects in the SLL-NFE and SLL-NFE-JWS Software Components. For
Notes, also restrict the search for the SLL-NFE Application Area.
In order to create new customer messages for GRC NFE, use the SLL-NFE component.

This blog will be regularly updated in order to include the latest changes/enhancements
on the GRC NFE product. Make sure to check it regularly for the newest available
information.
Henrique Pinto works at SAP Brazil, focusing on integration related solutions and development link for brazilian

specific products.
Please give me your feedbacks to improve this blog.
Comment on this weblog
Showing messages 1 through 75 of 75.
Titles Only
Main Topics
RKT profile
2010-06-14 12:01:13 Rafael Vieira da Silva Business Card [Reply]

Oldest First

Hi Henrique,
great content for those who needs help in NFe.
However, a very important detail of how to configure the NFe scenario is in the RKT content that is restrict for
SAP Partners.
I'm a PI consultant who needs to implement the NFe and who doesn't has the right access.
What would you suggest, in order to gain access to this valuable content?
Thanks and congratulations for the great blog.
Rafael V. Silva.

o

RKT profile
2010-06-14 12:08:22 Henrique Pinto

Business Card [Reply]

Hi Rafael,
actually, the OKP (Online Knowledge Provider, former RKT) for NFE 1.0 (course code: ONFE10) is available to
anyone who purchases it through SAP Education, be it SAP customers, SAP partners or just SAP users.
The OKP is not necessary for the configuration, but does teach you most of what you need to have a running
system, so it is basically a training content, and as such is available through purchase.
Generic information on how to configure SAP NFE 1.0 is still available through the Online Help
(http://help.sap.com/saphelp_grcnfe10/helpdata/en/93/cc40a6f0434083a64e23823175a8ff/frameset.htm), but it
does require that the consultant have some expertise in SAP XI & other basis knowledges (using Visual Admin,
scheduling jobs etc.).
Best regards,
Henrique.
Usage of SCAN-Server
2010-06-09 14:39:49 Thomas Mader Business Card [Reply]
Hello at all,
I found some sap notes regarding the usage of the SCAN Server instead of the "old" contingency process.
How can i use the scan server in GRC NFe? Do i have to reconfigure the integration szenarios with TPEMIS = 3
for the scan system? Are there any additional topics on the PI System?
Regards
Thomas

Archiving the NFe
Hello Henrique,
I have a question regarding the Archiving-Concept for NFe-Data:
With GRC NFe 1.0 Patch 10 it's possible to write the NFe Data to an archive (Object /XNFE/NFE) that's fine.
My Question:
How can i view the archived XML-Files after the reorganisation? Is there a special report available because the
GRC Webmonitor will be emty?!
Regards
Thomas

o

Archiving the NFe
2010-03-10 13:36:13 Henrique Pinto


Hi Thomas,
could you open a message in the SLL-NFE component with your question?
Thanks,
Henrique.



Archiving the NFe
Ok, thank's for the information - we will do the.
One more question: Is it possible to change the name of the content-repository NFE_COR_DOC_REP? We tried it
but it didn't work?!
Regards
Thomas


2010-03-11 13:46:05 Henrique Pinto

Archiving the NFe

Hi Thomas,
in tx KPRO, option Storage Categories, you'll see that the NFE_CAT category is related to the
NFE_COR_DOC_REP content repository.
And at code level (you can see the gc_storage_category constant in /XNFE/CORE_KPRO_XML_SAVE function
module, for example). So, relation with NFE_COR_DOC_REP content repository is at code level.
IMHO, it would not be recommended to change these names. What you could do was to change the original
configuration of NFE_COR_DOC_REP repository to reflect your own content repository (e.g. HTTP Server instead
of Database table).
Best regards,
Henrique.



Archiving the NFe

Hi,
Thank your for the information, we have changed the destination to http-content-server, it works.
We have another problem here in Paranà - we need the „FICHA DE CREDENCIAMENTO DE FORNECEDOR E
TERMO DE RESPONSABILIDADE DO SISTEMA“ for SAP GRC NFe - can you help me where we can get this?
Regards
Thomas


2010-03-15 14:21:52 Henrique Pinto

Archiving the NFe

Hi Thomas,
regarding registration at Parana, please open an OSS message on SLL-NFE component requesting the
information to contact the legal office responsible for that.
Best regards,
Henrique.
Versions, SP's and other
2010-03-01 10:40:15 Rodrigo Salomao Business Card [Reply]
Hi,
We're finishing the installation process of GRC and I would like to know what are the latests patches, SP's, EhP
and versions of each SW component involved on the landscape (ERP, XI, GRC, etc.)
Thanks,
Rodrigo Salomao
rodrigo_salomao@yahoo.com.br

o

Versions, SP's and other
2010-03-01 11:53:59 Henrique Pinto
Hi,
you can check that directly in the SAP Software Distribution Center: http://service.sap.com/swdc
Best regards,
Henrique.
GRC NFe download and Licensing for GRC NFe
2010-02-24 13:23:04 vaanvaram Aanvaram Business Card [Reply]
Hi,
Could you please let me know how can we get the GRC NFE software, i'am not able to download the Installation
package from service market place.
Also could you please let me know if we have to take license for using GRC NFe 1.0.

Thanks
Vivek

o

GRC NFe download and Licensing for GRC NFe
2010-06-02 12:34:29 Henrique Pinto
Yes, you do need a separate license for SAP NFE. It's a licensable product under the GRC suite.
Best regards,
Henrique.
BI and P install needed only for printing?
2010-02-01 15:06:28 Droney Will Business Card [Reply]
Hi Henrique,
Great blog, very helpful.. The NFE guide talks about a technical install of EP or BI, is this used only for printing?
We have ADS, Portal, BI already installed. Any reason we can't install just a NFE Abap instance and point at our
Portal for printing and use the PI system we're curently building for the Java component?

o

2010-02-01 19:52:06 Henrique Pinto
Hi Droney,
as stated, all you need is an ABAP 7.00 instance (for SLL-NFE component), a 7.00 Java instance (for SLL-NFEJWS component) and PI (for SLL-NFE XI Content). You don't need to activate the ADS printing for the NFE
WebDynpros (I'm not even sure they're activated at code level), so just forget about that.
As for the Java component, you can deploy it in the PI 7.0 Java stack of even in any other Java 7.00 instance
you already have in place (e.g. Portal or BI Java). But if PI is specific for NFE, it makes sense to deploy there.
Best,
Henrique.



2010-02-02 03:04:45 Marco Cerda Business Card [Reply]
Hello Enrique,
I'm working with Will Droney in this project. We will be installing our first PI server for this purpose and perhaps
use it as well in other projects. We choose to install PI 7.1 EhP1 which should be compatible with the SLL-NFE XI
Content component. From your reply to WIll I understand that the SSL-NFE-JWS does need a NW 7.0 java stack,
would it be supported by the NW 7.1 in the PI system ?


2010-02-02 04:28:58 Henrique Pinto


Hi Marco,
even though the SLL-NFE-JWS component is formally released just for AS Java 7.00, it runs without any issues
over AS Java 7.10 (if you deploy the pre-req components SP-XIAF and SAP-XIAFC). In a PI 7.1 system, these
pre-req components are already in place, and hence you shouldn't have any issues.
Just notice that during high loads, the Java Digital Signature Web Service may consume a lot of resources, so
size well your PI system (specially if you intend to use it for other purposes).
Best,

Henrique.



PI 7.1 and SLL-NFE-JWS
2010-05-15 20:03:08 Deidre Logan Business Card [Reply]
hello there,
we are being told that the digital signature will not work with PI 7.1... how do you do the PI 7.1 configuration for
the digital signature... the documentation in help.sap.com refers to have the XiRuntimeSecurity property set in
the Security Provider but in PI 7.1 we do not have the Visual admin and I can not find how to do this
configuration. Can anyone help with details on the PI 7.1 configuration for the digital signature web service...
thanks. Deidre Logan


2010-05-17 06:00:26 Henrique Pinto

PI 7.1 and SLL-NFE-JWS

Hi Deidre,
the XiSecurityRuntimePermission is not required for PI 7.1. For 7.1, you just install the certificate through NWA
and that's it. Please check help.sap.com for PI 7.1 in order to check how to maintain certificates in NWA.
Best regards,
Henrique.



Hello Enrique,
Thanks a lot for the information. This Blog is really a great source of information.
Just one more question, given our lack of experience with PI, can we use the same PI 7.1 EhP 1 for both
systems Dev and QA ?. I do not know if the PI content and SSL NFE JWS can be configured to allow the PI to
service the Dev and QA instances at the same time. We are not concern with high loads at this point.
Best Regards. Marco


2010-02-02 07:11:18 Henrique Pinto


Hi Marco,
do you mean one single PI 7.1 system to handle communications for DEV ERP + DEV GRC and also QAS ERP +
QAS GRC? Or did you also mean a single GRC instance + single PI instance for both DEV and QAS ERP?
As always, SAP strongly recommends that you have separate instances for Development and Quality Assurance
landscapes, in order to not impact tests with development changes and also to not close the development
system due to tests being ran. Nevertheless, it is technically possible to use a single PI instance to handle
communications for both DEV and QAS landscapes.
I wouldn't recommend using the same GRC system for both DEV and QAS though, because then PI 7.1 would
not be able to recognize which messages would have come from ERP DEV or ERP QAS. In the worst case
scenario, if you can't have separate GRC NFE instances for DEV and QAS, use two different clients (mandants) to
connect with ERP DEV and ERP QAS, then in PI you'll have two separate business systems (since each client of
an ABAP instance relates uniquely to a business system in the SLD).
Best regards,
Henrique.




Hello Enrique.
I meant a single PI to handle communications for both (DEV ERP + DEV GRC) and also (QAS ERP + QAS GRC).
We will have separate NW WAS ABAP 7.0 instances for DEV GRC and QAS GRC.
Thanks - Marco.



BI and P install needed only for
printing?
2010-02-02 09:10:17 Henrique Pinto


Hi Marco,
I'm sorry, I misunderstood the point and gave you a wrong information.
If you have two separate GRC systems communicating to the same PI, PI won't be able to know to which system
it should return the messages after they're processed by the government. This is due to the fact that all GRC <> PI integrations are asynchronous, and that within the messages there are no system-specific informatio (so
there is no possibility to have a correlation between the request and response messages within PI).
On the other hand, on the GRC component level, it is possible to identify the originating system (the LOGICAL
SYSTEM information is in the NFE header table). Furthermore, you can configure several ERP systems (several
logical systems) within a single GRC system.
Hence, the possible scenarios are:
1. one GRC + one PI for both DEV and QAS ERP;
2. one GRC + one PI for each DEV and QAS ERP.
In summary, for each GRC, you need a PI (GRC <-> PI relation is biunique).
Best,
Henrique.



BI and P install needed
only for printing?
Hello Henrique,
Following up with our installation, I have deployed the SLL NFE JWS Digital Signature web service in the PI 7.1
EhP1 SPS 04 system. The web service can be tested Ok using the Web Services Navigator but I'm having a
problem with it's publishing. If I try to access the WS via the URL
http://<Myserver>:<Myport>/DigitalSignature/ws
I get a 404 Not Found error.
Error: Web Service Endpount URI expected. Not found endpoint with URI /DIgitalSignature.
It is clear that the webservice is not being published. Can you provide some advice on how to correct this, again
this is on the PI 7.1 system.
Thanks a lot.
Regards - Marco.

2010-02-22 11:49:34 Henrique Pinto


One more thing. In the error message you've pasted, there's a typo: "DIgitalSignature" has capital "D", "I" and
"S", but it should be just the "D" and "S" (DigitalSignature); since it's case sensitive, it doesn't match the actual
existing service.
Again, the more safe approach is to copy the URL from the location attribute in the WSDL. It avoids such issues.
Best,
Henrique.

o

Hello Henrique,
Thanks for your replies.
The error message was a typo. But it still does not work even with the correct syntax.
http://<myserver>:<myport>/DigitalSignature/ws?style=document
Error: Web Service Endpoint URI expected. Not found endpoint with URI /DigitalSignature.
I'll follow up your previous recommendations, I'll open an OSS message if the problem continues.
Thanks.
2010-02-22 11:45:50 Henrique Pinto
Hi Marco,
please use the common discussion tools (e.g. Forums) or report an OSS message (SLL-NFE) component, since
this area is intended just for short comments and not extended discussions.
Anyway, have you double checked you're using the Java HTTP port and not the ABAP HTTP port? What the WS
Navigator does is just access the WS through the location URL defined in the WSDL. One alternative would be to
open the actual WSDL from the navigation context in WS Navigator and check the URL within the "location"
attribute (near the end of the WSDL). That is the URL you need to use in your Communication Channel.
Best,
Henrique.
NFE with XI 3.0
2010-01-26 01:00:36 Christian Pichler Business Card [Reply]
Hello Henrique,
thanks a lot for all the information in your blog. There is just one question left for me: is it possible to install NFE
if we have SAP XI 3.0 SP 15?
Kind regards
Christian

o

NFE with XI 3.0
2010-01-27 07:03:34 Henrique Pinto


Hi Christian,
we do have some customers running the NFE XI Content on XI 3.0 on an exception basis, but you'll still need a
AS ABAP 7.00 for the SLL-NFE component and a AS Java 7.00 for the SLL-NFE-JWS component, since they are
not compatible with WAS 6.40.
Also, it'd be a good idea to apply the latest SP levels to your XI system in order to avoid any incompatibility
issues, since the NFE XI Content is always developed and homologated in the latest SPs of PI 7.0.
Best,
Henrique.



NFE with XI 3.0
Hello Henrique,
We have a customer they will install a new PI System for the NFe.
Which version would be the beste choice - PI 7.0 or is the actual version of NFe compatible with PI 7.1 ?
Best regards,
Thomas


2010-01-29 04:48:12 Henrique Pinto

NFE with XI 3.0

Hi Thomas,
is this new system exclusive for the NFe scenario (separated from the corporate PI)? If yes, I imagine he'd want
to go for a "all-in-a-box" approach for it, right?
If that's the case, the only possibility is to use PI 7.0. If you go for 7.1, you'd still need a separate AS ABAP 7.00
instance in order to run the NFE Core (SLL-NFE) component.
Best regards,
Henrique.



NFE with XI 3.0
2010-01-27 07:55:09 Christian Pichler Business Card [Reply]
Hi Henrique,
thanks for your comment! I will wait until the upgrade to PI 7.1 is done.
Greetings from Austria
Christian
XML to Brazilian government
2009-10-08 08:40:00 Shaikh Basit Business Card [Reply]
Hello Henrique,
I am very new to NFe and trying to configure it. I read your blog and took the RKT session from SAP regarding
NFe. I havev couple of questions.

I have gone over the session and created 6 communication channels as e=mentioned in the RKT.
1.I am unable to find the SOAP adapter there since the field is grayed out even in the change mode
2. Are we generating the datatypes and structures and do the mappings in PI ? if yes how can i get the source
BAPI and target (XSD / WSDL ) file to import into PI 7.0 for mapping
or If SAP has provided us with all the structures and no mapping is needed.
Really need some input
thanks and regards
Basit Shaikh

o

2009-10-22 09:04:26 Henrique Pinto
Basit,
you need 6 channels for each SEFAZ site you're going to access, for each environment type
(homologation/environment). The structure should be like: 1 party for each SEFAZ site, each including 2
Business Services (1 for homolog/1 for prod), and each service including 6 channels (1 for each service).
You're not able to create a SOAP channel? Maybe there is an issue with your installation. Ask in the PI forums or
open a OSS message for this issue.
As for the XI Content, it is already delivered by SAP, you don't have create any objects in Repository, just
configure the Integration Scenarios in Directory.
Best regards,
Henrique.

o

2009-10-22 05:25:59 Henrique Pinto
Basit,
Best regards,
Henrique.



2009-10-22 06:51:46 Shaikh Basit Business Card [Reply]
Dear Henrique,
Thanks for the response.
The SOAP adapter problem that I was having is resolved by importing the XI Basis component.

I have created six communication channels for each region as you and SAP OKT have mentioned
Some new issues which I am facing are
Issue 1. when we send or resend the NFe it gives us the status as below
" Waiting for Response 0 Sent to Messaging System (XI,...) G "
Issue 2. When I go to the main NFe browser, it says
" Key storage data not maintained in table /XNFE/TCNPJ "
Even though I have defined the key view and element information and can see them in the mentioned table.
Issue 3. The HTTP RFC to and from XI both gives the status 500 with the beloe information
"HTTP/1.0 500 Empty HTTP request received"

Thanks and regards
Basit Shaikh


2009-10-22 09:05:55 Henrique Pinto


Hi Basit,
please ask these quests in the forums or open OSS messages. This is not the best interface for error evaluation.
Best,
Henrique.

o

2009-10-22 05:17:03 Henrique Pinto
Basit,
Best regards,
Henrique.
Information on server location and installation for SAP GRC NFE
2009-09-02 05:47:33 Pier Luigi Montani Business Card [Reply]
Dear Henrique,
we are planning the installation of the SAP NFE because our group has a company in Brasil.
Currently we have a landscape with ecc 600 (and CRM 4.0 and BI 70) that is located in Italy

and hosts various other companies.
The questions that follows may be silly but unfortunately I have not experience with double stack, XI, PI and so
on.
I have read that to install SAP NFE 1.0 three components are necessary:
1) SAP SLL-NFE 1.0 core component
2) Sap SLL-NFE 1.0 XI 7.0 content
3) SAP SLL NFE JWS 1.0
To make thing simpler we are thinking to install these components on a single WINDOWS (or aix) server
separated from the ecc 600 (AIX) servers but we are wondering:
1) should this server be located in Italy or in Brasil(we strongly prefer the Brasil location)? Pro and cons? I have
not found any discussion regarding this issue.
2) is possible and correct to have only one server for the three components?
Please consider that the communication between Italy and Brasil works on a static VPN (on a 4Mb internet
connection) and that the max number of nota fiscal per hour is very very low (we reached a maximum of about
30 NF for a total of 100 lines) so the load is minimum.
Regarding the installation (assuming a single server can be used) I have some doubts on components and
sequence:
1) Installation of Netweaver 7.0 ABAP + JAVA stacks. Which usage type should I use?
2) Installation of the SAP SLL-NFE 1.0 core component on the abap stack of 1)
3) Installation of XI content SLL-NFE on SAP NW XI 7.0. Can the XI 7.0 be installed on the same instance of step
1 or do I need a separate instance and/or server? In the Blog you say that the NFE XI Content is imported on
Integration Repository of SAP PI 7.0, can you clarify?
4) Installation/deployment of SLL NFE JWS 1.0 on the java stack (j2ee part) of 1)
5) I have also read that if I want to print the monitoring lists I must use BI or EP so can these components be
installed on the same instance of 1) or do I need a separate instance and/or server?
6) In the blog you suggest the use of the PI instances (we have not it yet) to install everything so first of all
should I install a SAP NW 7.0 usage type PI instead of point 1 and then follow the other steps? In this case the
client of PI can be only one because we use it only for NFE: is this correct?
Please can you give me some suggestion and/or tell me where can I find some documentation on these matters?
Thank you very much, compliments for the blog and sorry for all the questions.
Pier Luigi Montani

o

Information on server location and installation for SAP GRC NFE
2009-09-03 13:16:24 Henrique Pinto
Dear Pier Luigi,

regarding the technical installation, I do comment that it is possible to install everything in a single Box. Notice it
is not a sugestion, but just a possible choice. The landscape that best suits your company's needs must be
defined during the blueprint phase of your project.
Regarding the single Box installation, the only possibility is to use PI 7.0 as a central instance and install the NFE
components (ABAP and Java) over that PI installation. Notice that you'll need a separate client, in the ABAP part,
for the NFE client (e.g. PI client, by default, is 001; create a new client, for example 100, for NFE, as copy from
000). Functionally speaking, you will still have the 3 independent-but-integrated components (NFE Core ABAP,
NFE Java Digital Signature, PI Content for NFE Interfaces), each one as an specific Business System, but they
will be installed in a single Technical System.
As for the location, it depends on your conditions. The connection to Brazilian Government is done through the
Internet, so there is no requirement to have the NFE server located in Brazil whatsoever. Moreover, having the
system onsite, the connection between ERP and NFE, which is usually done through an Intranet infrastructure,
would be done over your VPN 4MB link, which may rise a risk. On the other hand, having the system onsite
would make the maintenance closer to the daily operation, which would reduce down times and the overall
impact on the billing process. So, it is up to your company to weight the pros and cons and take the decision. In
technical terms, the Netweaver platform is prepared to allow your company to use any landscape (centralized or
descentralized).
Best,
Henrique.
Outbound B2B Interface
2009-07-20 08:09:08 AES Generic-Read-Only Business Card [Reply]
Hi Henrique.
First I would to congratulate the NF-e solution and product of SAP GRC.
I need to clarify a doubt; this Outbound B2B Interface is available from version 4.7 or only from the 6.0?
Here is implemented the GRC solution, version 1.0 and support package 5.
Tks and regards.

o

Outbound B2B Interface
2009-07-20 14:44:33 Henrique Pinto
Hello,
the B2B interface is started by SAP NFE, so its independent of the backend version; it works even for NFes
generated in non-SAP backends.
Best regards,
Henrique.
SAP PI7.1 EHP1
2009-06-01 23:36:52 Abhishek Goel Business Card [Reply]
Hi Henrique
Thanks for such a nice blog.
Would like to check if NF-e XI Content is supported for SAP PI7.1 including EHP1.
Thanks
Abhishek

o

SAP PI7.1 EHP1
2009-06-02 09:46:55 Henrique Pinto


Hi Harpreet,
since PI 7.1 EHP1 is backward compatible, than it should be ok.
The recommendation is always to be on the latest available SP/patch.
Best regards,
Henrique.
New Client for NFE ?
2009-05-26 09:27:57 Thanukrishnan Kumaraswamy Business Card [Reply]
Hi,
In our PI landscape we have installed NFE in DEV system which has only one client(100) ,which is configured as
Integration server.
I understand from the point II - a)Communication from GRC NFE to XI , that we need to have one more new
client(200) and be configured as Application system which will point to XI Integration system(Client 100).
Please correct if I am wrong and revert.
regards
Thanu

o

New Client for NFE ?
2009-05-26 09:31:21 Henrique Pinto


Hi Thanu,
the actual installation of the Add-On is taken over the client 000 and is valid for all clients, since the objects are
client-independent. However, in order to execute the processes, it is necessary to have a separate client,
configured as Application Server, in order to be able to execute the server proxies (it is not possible to execute
ABAP proxies in the Integration Server).
Best regards,
Henrique.
Great Blog! Just one questoin about getting SAP Support
2009-04-21 13:25:41 Chad Niswander Business Card [Reply]
Throughout this Blog and in the comments section there is mention about putting these three components of
NFe on different Systems (Instances).
One of the comments you mention: NFE ABAP Add-on, whose objects are included in a specific namespace
(/XNFE/), hence letting it be installed on any SAP WAS ABAP that you have on your landscape (inclusing SAP
ERP); our suggestion is to handle it separately of ERP (or any other installations, for that matter) in order to not
incur into governance issues.
What type of governance issues are you referring to? Likewise, if we installed this Add-on with our ERP 6.0
system is this supported by SAP? Another option in our landscape is to install SLL-NFE on the system currently
hosting our Global Trade Services functionality (SLL-LEG)? Which is a better home?

Likewise, I can think of two homes for the NFE Java Component within my landscape. This could be installed
within our Portal or PI. Any recommendations or support concerns with either of these options?
Any comments or suggestions would be greatly appreciated.
Thanks much,
Chad

o

Great Blog! Just one questoin about getting SAP Support
2009-04-27 08:35:35 Henrique Pinto
Hi Chad,
technically, you can install the ABAP Add-On in any ABAP 7.0 instance with SAP_BASIS SP13+ (there are prereqs
for other components as well, check the Installation Note linked above). Nevertheless, when you install two or
more applications in the same instance, you incur into governance problems, such as:
- when you have to upgrade one application SP level, you necessarily upgrade the other (implying into
necessarily synchronized down times + post-SP application testing efforts)
- problems on changes of one application (bugs or crashes) may impact in the other application;
- etc
Since ERP is a highly critical application, it's generally not recomended to install any other application together
with it. If you have another ABAP 7.0 system, it's recommended to use that instead. Your GTS system should be
ok for it.
For the Java component, you can use it in PI or in Portal, given they are both Java 7.0. But notice that the SLLNFE-JWS component requires two pre-reqs components (related to Adapter Framework), which are already in
PI. So it'd be easier to install the NFE Java component in PI.
Best regards,
Henrique.
Implementation time
2009-03-10 06:22:36 Adriano Cardoso Business Card [Reply]
Hello,
How long does it take to implement the NFe solution counting with the GRC NFE(an average time)? I´d like to
have an idea in order to measure the resources needed for such.
Thanks in advance,
Adriano Cardoso

o

Implementation time
2009-03-10 06:27:01 Henrique Pinto
Hi Adriano,
typical implementation takes around 2-3 months.
Best regards,
Henrique.



Implementation time
Hello Adriano,
Great blog and a great overview of NFe.
Regarding the implementation time: Do you have an estimation of the timebudget for an implementation projekt
of NFe 1.0 (technically and process MM/SD)?!
Thanks
Thomas


2009-05-15 05:48:49 Henrique Pinto

Implementation time

Thomas,
usual recomendation is:
SD - full time (for configuration and test phase, 2-3 months)
MM - part time (just configuration 2-4 weeks)
PI - full time (for configuration and test phase)
ABAP - on demand
Basis - part time (for installation, 1-2 weeks), after that on demand
Best regards,
Henrique.
SLD outside
2009-01-28 15:27:50 Alexandre Rezende Business Card [Reply]
Hello Henrique,
In my company the global SLD is located in another country, our Internet link may fall and SLD is unavailable.
What happens if that occurs?
There will be no communication of ERP?
Ps. Sorry for my bad English.

o

SLD outside
2009-02-02 04:40:23 Henrique Pinto


Hi Alexandre,
theoretically, SLD is not directly used in the runtime XI calls. So it should not be a problem. However, if the
connection is not stablished after a little while (e.g. 5~10 minutes), the SLD cache in XI may fail and then all
subsequent calls will fail.
Nevertheless, the connection between R/3 and GRC NFE is not over XI (it's a direct RFC call), and hence even if
SLD is down, you'll be able to see all NF-es in the GRC NFE Monitor: if the subsequent call through XI fails, then
you can restart it directly through the NFE Monitor.
Best regards,

Henrique.
New to NFE !!!
2009-01-19 11:02:20 Enrique Cordeiro Business Card [Reply]
Hello Henrique.
I’m being asked to implement NFE in my company, but I have no idea of what this is.
I checked on SAP training and found an online course that last only 3,5 hours.
Do you think that If I take this course, I will be able to implement NFE, (I’m a junior SD consultant), or I need
some other skills?
Besides the knowledge of NFE and a Basis to implement and install the package, I will need any specific
consultant in order to implement NFE?
Thanks for your help
Regards
Henrique,

o

New to NFE !!!
2009-01-20 11:46:06 Henrique Pinto


Hi Henrique,
implementing end-to-end NFE require two sets of skills:
- ERP (SD/MM) Brazilian localization: SAP ERP
- Netweaver (XI/ABAP): SAP GRC NFE
A SD consultant would do well in the ERP configuration part for NF-e, but in order to be able to configure the
SAP GRC NFE solution, it is necessary to have SAP XI/PI skills. You'd also probably require some ABAP help
through the whole implementation project.
For NF-e configuration in ERP, search for the following courses: LAPNFE & WBRNFE. For the SAP GRC NFE
configuration, search for ONFE10 and LAPGRC courses.
Best regards,
Henrique.
Government status codes
2009-01-14 13:27:20 Karsten KÃ¶tter Business Card [Reply]
Hello Henrique,
thanks for this excellent blog!
I have a question regarding the configuration of the government status codes:
SAP documentation says, that I can upload the meaning of government status codes to SAP system with a
report. Furthermore the user is adviced, that the meaning of the government status codes can be received from
government.
I checked http://www.nfe.fazenda.gov.br/, but unfortunately my (really basic) portugese seems not to be
sufficient to find the file.
Maybe you can point me directly to the location, where I can get the file?
Thanks & best regards,
Karsten

o

Government status codes
2009-01-15 10:35:58 Henrique Pinto

Hi Karsten,
the government status codes are found in the NFe Government Implementation Guide ("manual de integracao
do contribuinte"), in the 5.1.1 section.
Best regards,
Henrique.
Excellent
2008-12-12 06:00:57 Midervilson Andrade Business Card [Reply]
Very good job, Henrique.
Thanks for your complete and clear explanation.
Mider.
Using SAP GRC/NFE solution for B2B integration with vendors
2008-12-09 09:13:49 Kristofer Hansson Business Card [Reply]
Dear Henrique,
I am involved in a project for implementing the SAP GRC/NF-e solution for communication/validation against
government systems. The information you have provided here is very valuable in that perspective.
However we are also currently investigating if/how to use the SAP GRC/NF-e solution for receiving electronic
vendor invoices from suppliers in Brazil and I am missing information on this functionality.
In general - what kind of support and benefits does the GRC/NF-e solution provide for receiving NF-e from
vendors?
As far as I understand the invoices are received in GRC/NF-e then posted in ERP via SAP delivered RFCs. Is that
a correct understanding?
Does GRC/NF-e have an out-of-the-box solution for handling of Brazilian specific taxes?
Thanks for a great blog!
/Kristofer

o

Using SAP GRC/NFE solution for B2B integration with vendors
2008-12-15 06:21:27 Henrique Pinto
Hello Kristofer,
as per version 1.0, SAP NFE includes just the compliance part regarding of incoming NF-es: it stores the XML
messages and show them to the user in a monitor-like screen, with possibility to download the XML file etc.
ERP automation of incoming NF-es (complete MM integration, including brazilian specific requirements) is been
currently evaluated and, if released, will be included in the next NFE release. However, we don't have any dates
confirmation yet. Sorry for that.
Best regards,
Henrique.
good detail
2008-10-30 06:50:42 Siva P Kumar Business Card [Reply]

This blog is very detailed and helpful to understand. However, as with any new system, it seems that we
complicate the solution just to use the new components. Managing an instance of SAP, and especially Java
systems is not a trivial task. The TCO goes very high when we increase the number of systems.
It is not clear why we need to manage 2 instances for this in addition the ERP. And if you add the HA
requirements and DEv/integ/Test, it just explodes.
It would have been nice to have the NFE work inside of ERP and also give an option to use other middlewares.
IDOCs and RFCs have been very successful and are still used today for large volumes. Why not use RFC from
ERP to XI, and webservices from XI to outside.
Just my 2 cents.
Thanks
siva

o

It's not that simple
2008-10-30 09:42:48 Henrique Pinto


Hello Siva,
indeed, managing HW/instances is really tricky to handle.
That's why, in a good software development approach, the application level must be the most decoupled from
the HW/instance as possible, so that the HW requirements can be handled specifically by each customer,
implementing the landscape that best fits their needs.
SAP NFE 1.0, as all of the latest SAP products, is implemented on the NetWeaver platform, which guarantees the
HW decoupling, since the HW compatibility is handled by the Application Server, and not at the application layer.
More than that, as outlined above, SAP NFE has 3 components:
- NFE ABAP Add-on, whose objects are included in a specific namespace (/XNFE/), hence letting it be installed on
any SAP WAS ABAP that you have on your landscape (inclusing SAP ERP); our sugestion is to handle it
separately of ERP (or any other installations, for that matter) in order to not incur into governance issues (the
rule of thumb that less systems implies in lower TCO is not always true);
- Digital Signature Java application: since the Brazilian government defined several specific rules, the standard
Digital Signature components in SAP PI didn't suffice the requirements; thus a development was necessary to
enhance the digital signature with the specific rules defined by the government. As the ABAP component, it can
be deployed in any WAS Java in your landscape;
- XI Content: you mentioned the possibility of using other middlewares, by replacing the proxies for RFCs or
IDOCs. I think that you missed the point here. The purpose of the SAP NFE solution is to be an out-of-the box
solution to meet all the requirements from the Brazilian Government for electronic invoicing (NF-e). Of course, all
SAP ERP customers can use 3rd party middlewares or even develop their own NF-e messaging system solution,
since from SAP ERP there are RFCs which send the NF-e data for external systems.
Regarding software logistics, the requirements by Brazilian government (digital signature, creation of batches of
NF-es, stateful processes etc.) were too specific to be included in ERP, since they'd impact a lot in the standard
SD & MM processes. That's why the decision was to make a standalone solution (even because customers with
several ERP instances and even non-SAP ERPs can issue their electronic invoices through a single instance of
SAP NFE).

Last but not least, you may wonder why a new solution was required at all. You may think that a few RFC
interfaces + Java EJB + BPM in XI would meet the requirements. Believe me, pilot projects for NF-e are being
implemented in Brazil since 2005. The first project-based solutions were exactly based on XI ccBPMs. When the
1st companies started to roll-out the solution to their business places, the performance was just not enough to
meet 100% of the companies' volume of issued invoices (imagine a huge BPM in XI being executed once for
each invoice, the're companies in Brazil with as much as 100k invoices per day, issued within a 8-hour
timeframe). The current solution architecture is the natural evolution of all project implementations that SAP and
SAP partners have experienced in Brazil during these couple of years. And it has been validated in several
customers, as of now.
I hope these information clear things up a bit.
Best regards,
Henrique.



It's not that simple
2008-10-31 05:32:47 Siva P Kumar Business Card [Reply]
Henrique, Thank your for your detailed response. Now, I understand the reasons behind the architecture.
siva
The best overview I've seen so far! Still one stupid question...
2008-10-29 03:13:13 Reinhard Wiggers Business Card [Reply]
Dear Henrique,
thanks a lot for this great blog. It is the first one that gives me a comprehensive overview of the applications
involved in this process. Due to the fact that I'm not a technical expert but one of these guys that has to keep
an eye on proper functions and the costs in our company, I still have a question regarding instances and
hardware.
For our company and our subsidiaries in Brazil we have to meet the new requirements coming with SPED and
NF-e. We are running a R/3 4.7 instance for our business processes and already a PI 7.0 for communicating with
3. party applications and with external partners. PI is installed on separate HW/instance already.
Youe are saying:
Regarding the logistics for the installation of these Application servers, it may be evaluated the possibility of
installing everything on a single instance, usually the PI instance, since it already contains both ABAP and Java
Web Application Servers.
However, the formal recommendation by SAP is to not install more than one application by instance, especially in
the case of SAP PI due to the possibility of causing performance bottlenecks (because PI is a very resourceconsuming application).
To install GRC NFE is it necessary to have a second PI instance and even separate HW or can it be installed on
our current PI instance?
With best regards from Germany
Reinhard Wiggers

o

The best overview I've seen so far! Still one stupid question...
2008-10-29 03:24:04 Henrique Pinto
Hi Reinhard,

a second PI instance is definitely not necessary.
What you would need, if you choose to go for the separate landscape, is a Web AS installation (pure NetWeaver
instalation), with Web AS ABAP & Web AS Java usage types, not PI.
Over these Application Servers (AS), you install the GRC NFE application (both ABAP & Java components), but
for the communication you could use the already existing PI. It would be like if you were installing a new CRM or
BW instance, for example.
Some alternatives are also possible, e.g. install a new instance with just ABAP stack, and deploy the NFE Java
component (which includes only a small application for digital signature) on the same Java stack of PI or any
other Java Stack that you may already have in your landscape for running Java applications (e.g. Portal).
Of course, each of these landscapes must be evaluated within your company's needs and current
landscape/sizing capabilities. And again, SAP's recommendation is always to use a separate instance for the
solutions.
Notice that I have not talked about separate HW, but just separate instances (logical components), since it's
possible to have several instances on the same HW (virtual machines etc.). How to distribute the instances
among the HWs is also a decision to be made by your basis team, based on your company's policies.
Great content!
2008-09-10 17:06:39 Paul Pessutti


Excellent work Henrique
Very helpful
2008-07-10 18:36:58 Leonardo Machado


Hi Henrique,
your Blog is very helpful and clear, congratulations!
Best regards
Leo
Very Insightful
2008-06-15 07:22:28 S Sundaram Business Card [Reply]
Hi,
This is a nice blog.Does this implementation supports GRC Access Control 5.2 version?
Thanks
Sundaram

o

Very Insightful
2008-06-15 14:17:47 Henrique Pinto


Hi Sundaram,
as of now, no.
And since GRC NFE is a product specific to Brazil, I'm not sure it will ever support Access Control (but I might be
wrong).
Best regards,
Henrique.



Very Insightful
2009-04-27 08:21:54 Shobhit Swarup Mathur Business Card [Reply]

Hi Henrique,
Excellent blog. Can NFe be setup with PI7.1 instead of PI7.0?
Regards,
Shobhit


2009-04-27 08:25:59 Henrique Pinto

Very Insightful

Hi Shobhit,
yes. Starting from SP06, the SLL-NFE XI Content is also supported for PI 7.1.
Nevertheless, the ABAP and Java components still require AS 7.00 (so, at least, you'd need PI 7.1 + additional
7.0 instance).
Best regards,
Henrique.



Very Insightful
Is there a release date for the ABAP and JAVA components to be working on AS 7.1?
We are like many companies fighting with 13 landscapes running different versions of SAP and types of
software.
So we are willing to take the risk of loading these components in existing systems to prevent installing another
landscape to support GRC-NFe. We have an ECC 6.0 system and a XI 3.0 system that we are upgrading to PI
7.1. We do not want to install PI 7.0 to have all the GRC-NFE pieces.
We can look at putting the AS 7.0 components in our ECC 6.0 system that is already a dual stack.
Thanks for all the information in the blog. It was very helpful


2010-03-22 14:28:15 Henrique Pinto

Very Insightful

Hi Deidre,
as commented, even though not formally released, the Java component already works for AS Java 7.10, so you
could evenn use it together with your PI 7.1 system.
As for the ABAP component, unfortunatelly there are currently no plans to support AS ABAP 7.10 (all functional
solutions are still being developed on AS ABAP 7.0x, e.g. ERP and CRM). So you'd need to use an existing AS
ABAP 7.00 instance on your landscape.
Best regards,
Henrique.



Very Insightful

Thanks... I saw that the XI content for 7.0 would work on PI 7.1 but did not understand that the java bean web
service should work on AS 7.1 too. thanks for the quick response.

Implement SAP GRC NFE for Brazilian e-Invoicing

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (20)

Semelhante a Implement SAP GRC NFE for Brazilian e-Invoicing

Semelhante a Implement SAP GRC NFE for Brazilian e-Invoicing (20)

Último

Último (20)

Implement SAP GRC NFE for Brazilian e-Invoicing