Implementation Help For SAP NFE Consultants: Outbound

IMPLEMENTATION GUIDE | PUBLIC
2019-10-29
Implementation Help for SAP NFE Consultants:

Outbound
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Implementation Help for SAP NFE Consultants: Outbound. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Implementation Help for SAP NFE Consultants: Outbound

2 PUBLIC Content
1 Implementation Help for SAP NFE
Consultants: Outbound
Configuration for NFE Outbound
SAP Nota Fiscal Eletrônica (SAP NFE, SAP Electronic Invoicing for Brazil) helps companies comply with the
Brazilian requirements for electronic invoicing. SAP NFE is a centralized data store and workplace for all
messages communicated between your company and the government system, as well as for messages
between your company and other companies' systems in B2B scenarios. It also is the central platform for
storing the exchanged files as required by law and provides interfaces for easy access to these documents. This
document describes the configuration of the NF-e outbound and NF-e event procedures.
1. Maintain Own Tax Numbers (CNPJ)

2. Digital Signature
3. Web Services
4. Number Ranges for Batches
5. System Communication
6. User Roles and Authorization
7. Batch Job Planning
8. Event Version Customizing
9. Maintain System Response for Own Tax Numbers
10. Define Authority's Status Code
11. Maintain Control Parameters for Process Flow
12. Activate B2B Scenarios for Business Partners
13. Activate B2B Scenarios for Natural Persons
14. NF-e: Maintain Connected Government Systems
15. NF-e: Maintain Version of Message Types
16. NF-e: Define Query for Service Status for Authority (SEFAZ)
17. NF-e: Maintain Batch Parameters
18. NF-e: Maintain Process Determination for Outbound NF-es
19. Configuration Check
1. Maintain Own Tax Numbers (CNPJ)
As a first setting, the tax number(s) of your company need(s) to be defined to control further customizing
settings based on the CNJP(s).
Use transaction SPRO and navigate to the SAP Customizing Implementation Guide (IMG): Nota Fiscal
Eletrônica General Settings Maintain Own Tax Numbers

Implementation Help for SAP NFE Consultants: Outbound PUBLIC 3
4 PUBLIC Implementation Help for SAP NFE Consultants: Outbound
You enter your company's tax numbers, as well as an appropriate region, and description:
2. Digital Signature
2.1. Prerequisites
● Prerequisites
○ User Role
Prerequisite to capture the digital signature is the user role SAP_QAP_RZL_ADM to execute transaction
Strust.
○ Request of Certificate
In order to issue electronic invoices the xml must be signed using a digital certificate compliant with
ICP-Brasil standards securing the access between the NFE system and the government's servers.
To obtain the digital certificate you must interact with a certification authority. You can find a
completed and updated list of certificating authorities on the website of the National Information
Technology Institute (ITI Brazil) http://www.iti.gov.br. The main certification authorities are:
Caixa, Serasa, Certisign, Valid, Digitalsign, and Boa Vista.
The certificating authorities can issue both certificates, as well as certificates in the form of a physical
token. Therefore, make sure you request the digital certificate that can be used for e-commerce
transactions in PKCS#12 format with the ending .pfx. The certificate can also be used for the client

authentication using https in PI. For signing, you can also use the physical token and connect it via PI
using enhancement spot /XNFE/CORE_SIGNATURE_CREATE_EN.
○ XML Signature Test Program
The program SECXML_DSIGNATURE provides an UI to test the signing and verifying of an XML source
and takes the configured Personal Security Environment (PSE) application* and a local XML file name
as input.
2.2 Outbound Configuration
● Outbound Configuration
○ Create PSE
Use the tool SAPGENPSE to create a PSE from the existing private certificate as described in Importing
a PKCS#12 File:
 Note
A certificate file name with extension .pfx is also valid
○ Create SSF application

From the Administration workplace, use applicationDefine SSF Applications. With this administration
UI, SSF applications are created and all attributes are set correctly in table SSFAPPLIC. You need a
separate SSF application for every private certificate that you use for signing the NF-e (for example, for
each own tax number). This step has to be done in all NFE systems separately and will not be
transported.

○ Assign SSF application to CNPJ
The SSF applications have also to be customized in IMG activity Outbound Maintain System
Response for Own Tax Numbers .

○ Set Application Parameter
From the Administration workplace, use transaction SSFA Maintain Application-Dependent SSF
Information, to add application-specific SSF parameters.

Choose New Entries and fill in the appropriate data:
○ Load the PSE

From the Administration workplace, use transaction STRUST – SSF: Trust Manager and load the PSE:
Double click on file:

Inform about the .pse that is copied from the server to the local machine and also inform about the
password of the PSE.

Choose the PSE and select Save as…

Select the SSF application in the Save PSE as box and select and confirm the proper SSF for signature:

3. Web Services
3.1. Activate the Service for Displaying the User Interfaces
The user interface for master data maintenance and the central messaging monitoring uses Web technology,
for which you must activate the relevant services.
In SAP NFE, enter the transaction code SICF and choose Execute. Select the following entries:
● nfe_outb_monitor for NF-e Monitor

● nfe_batch_monitor for NF-e Batch Monitor
● nfe_servsta_monitor for Service Status Monitor
● nfe_outb_monitor_arch for NF-e Monitor for Archived NF-es
● nfe_analytics_out for Evaluations of Outbound NF-es
● ssf maintenance for SSF maintenance
● event_batch_monitor
● event_monitor
● event_monitor_IB
In the navigation tree for the virtual hosts/services, navigate to default_host sap bc webdynpro
xnfe :

Activate the service for displaying the user interfaces for each of the following entries by using the context
menu and selecting Activate Service:
3.2. Activate the Basis Services for the Virtual Hosts/Services

You must activate the following basis services in the navigation tree for the virtual hosts/services. Select the
following entries in the navigation tree for the virtual hosts/services under default_host sap public
bc :
Activate the basis services for the virtual hosts/services for each of the following entries by using the context
menu and selecting Activate Service:
● ur for Unified Rendering

● icons for SAP Icons
● icons_rtl for Icons RTL
● pictograms for Pictograms
● webdynpro for Web Dynpro MIME Handling

4. Number Ranges for Batches
Batches that package NF-es/events require a number range to identify and to monitor the batches in process.
In the batch monitors of SAP NFE, you can use this number range to access all NF-es/events that the system
has combined into one batch.
 Note
CT-e and MDF-e events are not authorized in batches. Every event for CT-e/MDF-e is send individually and
synchronously.
Use transaction code SNUM to create the number range for the object /XNFE/BAID, as well as /XNFE/EVBT
and create interval 01 with a length of 15 digits.

5. System Communication
5.1. System Communication – ERP to NFE
Use transaction code SM59 in the logistics feeder system SAP ERP to define the RFC destination for the core
application of SAP NFE:
● Create a connection with connection type Logical connection.

● In the Logon & Security section, enter the RFC user created in the SAP NFE system.
● Save your settings.

5.2. System Communication – NFE to ERP
Use transaction code SM59 in SAP NFE to define the RFC destination for the SAP ERP system:
● Create a connection with connection type ABAP Connection.

● On the tab page Technical Settings, enter system data of the feeder system.
● On the tab page Logon & Security, enter the RFC user created in the SAP ERP system.

You must maintain the relationship between the RFC destination and the logical system.
● Call transaction BD97.

● Enter the Standard RFC destination for BAPI calls.

5.3. System Communication – NFE to SAP NetWeaver PI
NFE and SAP NetWeaver PI must be connected. To do that, use transaction sxmb_admin Integration
Engine Configuration .

In the Integration Engine Configuration Data, fill out the role of the Business Application Server and the
corresponding Integration Server. To verify whether the connection setup to the central integration server was
successful, use the check function.
6. User Roles and Authorization
To adjust the user menu for SAP NFE Outbound, the following roles are needed:
1. /XNFE/WP_NFE_ADMIN
Transaction PFCG shows that this role is intended for the NFE Administrator. It does not contain
authorizations and is therefore only meant to create and set up the user menu. You should copy this role to
adjust the user menu according to your requirements. This role can be combined with other roles in a
composite role.

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

3. /XNFE/TAXNUMBER
Use transaction PFCG and change the role /xnfe/taxnumber. In the lower part of the Authorizations tab,
you can select Change Authorization Data. You should copy this role to adjust the user menu according to
your requirements regarding the tax numbers and the allowed user activities.

7. Batch Job Planning
For communication processes, you must define batch jobs that require regular processing.
There are different options to send batches: Use /XNFE/NFE_BATCH_PROCESS OR XNFE/NFE_BATCH_CREATE

AND /XNFE/NFE_BATCH_REQUEST.

In addition, the following reports have to be scheduled for NF-es:

The following programs are valid for events:
For creating a batch job, use transaction code SM36. Enter a job name and go to Start condition.

On the selection screen Start Time, choose Immediate to select the period values.

Go to Step, enter the name of the report and Save your settings.

8. Event Version Customizing
Determine which XML version is used for individual message types when communicating with authorities.

9. Maintain System Response for Own Tax Numbers
Configure the system behavior and storage location of the certificate that you use for digital signatures. Also
configure whether or not you use the productive or test system environment for your communication. You have
to do this for every tax number that you are using in your company:
1. Select your CNPJ and define the system environment.

2. Enter the name of the SSF application* as described in Digital Signature Outbound Configuration .

10. Define Authority's Status Code
Define the codes (and their descriptions) that the authorities use as electronic answer message. You receive
this list from your responsible tax authority. Use transaction /XNFE/STATUS_UPLOAD to upload the electronic
list version to the system. An individual line of the file can only contain one code and its description, split by a
separator.

You can also enter the codes manually by selecting New Entries:

11. Maintain Control Parameters for Process Flow
The process Issue of NF-e with Batch consists of the following steps (also described in the application help
under http://help.sap.com/nfe Application Help English ):
You can influence the handling of the process flow depending on the sender's and/or recipient's CNPJ number
in the document.

* The Trigger B2B Process can be disabled. Therefore, you have to set the flag in the Deactivation check box.
12. Activate B2B Scenarios for Business Partners
Determine the business partners you want to exchange electronic documents with.
● Option 1: Create a new entry with a blank CNPJ field and select indicator* for electronic communication.
This activates sending electronic documents for all business partners.
● Option 2: Create an entry for each business partner with whom you want to exchange documents
electronically in a manner that is different from the standard setting. To do so, enter the tax number
(CNPJ).

 Note
*In the B2B Active field, you decide between the following parameters:
● Communication to business partner via PI (for example, mail)

● Communication via DB (for example, the business partner is a second plant in the same client of the
NFE system, for example, for a stock transfer).
13. Activate B2B Scenarios for Natural Persons
Determine with which natural persons you want to exchange electronic documents.
1. Option 1: Create a new entry with a blank CPF (tax number for a natural person) field and select the
indicator B2B Active (B2B Scenario CPFs). This activates general sending for all natural persons.
2. Option 2: Create an entry for each business partner with whom you want to exchange documents
electronically in a manner that is different from the standard setting. To do so, enter the CPF number.

14. NF-e: Maintain Connected Government Systems
Configure to which authority system you want to send your NF-e messages.
1. Select the desired logical system and enter your tax number (CNPJ).
2. Then select the region (CUF) of the authority system you want to communicate with, and determine
whether you want to use the system environment (Test or Production) at SEFAZ/SCAN Authority.

15. NF-e: Maintain Version of Message Types
Determine which XML version you want to use for individual message types.
1. Enter the logical system and tax number. A blank tax number is also permitted.
2. The document types must be defined for each tax number
3. The XML versions for the message types NFE (Issue NF-e) and INUTNFE (Skip NF-e) have to be
maintained.

To determine the XML version, the system first searches an entry for the respective tax number. If no such
entry is found, the system uses the entry with a blank tax number.
16. NF-e: Define Query for Service Status for Authority (SEFAZ)
The availability of the SEFAZ system as well as the responsible contingency system has to be checked
periodically. To do so, use following parameters for each combination of Brazilian region and system
environment:
1. Frequency of status request in seconds.

2. Time zone.
3. Assignment of the responsible contingency systems*.
4. For the check of the contingency system, the following options are available.

 Note
● *43 SVC Rio Grande do Sul (RS, tpemis = 7)

● *91 SVC National (AN, tpemis = 6)

17. Maintain Batch Parameters
The process NFEISSU1 bundles NF-es into batches. The following parameters must be defined:

1. Specify the region for which you want to define the parameters. You have the option of defining a default
setting. To do this, create an entry with a blank CUF field and fill in the remaining values as needed. This
entry applies the parameters for all regions that do not have their own specific entry.
2. Max. Coll. Time (sec.): The maximum time in seconds during which NF-es are collected for a region before
the resulting batch is sent.
3. Max. Batch Size (bytes): The size of the batch is based on the signed NF-es. A maximum of 500,000 bytes
is permitted.
4. Max. Number of NF-es: A maximum of 50 NF-es per batch is permitted.
5. Wait Time (sec.): The number of seconds the system waits after sending the batch before the system
sends the batch request to the authority.
6. Max. No. of Retries: Maximum number of automatic attempts at sending the batch request.
7. Compressed (.zip file): Indicates whether the batch is compressed (as a .zip file).

The standard system settings are as follows:
 Note
These parameters have a high influence on the CPU usage, disk usage, and overall performance of SAP
NFE. Therefore, change the parameters according to business needs and try to create the batches with the
highest NF-e number in an acceptable time duration. Be aware that using small values for Max.Collecting
Time, Max. Batch Size, or Max. Number of NF-es increases the amount of batches. This can provoke
performance problems in the processing. The creation of NF-e batches is also influenced by the way you
schedule the job for the batch report. For more information about batch jobs, refer to the section NF-e
Batch Job Planning (Outbound) in the application help of SAP NFE (see http://help.sap.com/nfe ).
18. NF-e: Maintain Process Determination for Outbound NF-es
Assign the desired process type to the CNPJ number. You can also make a blank entry for the CNPJ number. In
this case, the system first searches for an entry that matches the relevant CNPJ number when determining the
process type. If no matching entry is found, the system uses the blank entry.

 Note
The process determination is carried out when the NF-e is received from the feeder system (ERP). There is
no option to switch between the two processes during processing. If you want to send a rejected NF-e with
a different process, you have to forward the rejection to your feeder system (Change the Customizing!) and
send the NF-e again.
19. Configuration Check
To double check that the necessary customizing and the batch jobs are correct, execute program /XNFE/
CONF_CHECK.

1. Enter your CNPJ Number and execute the program:
2. A table with the information about the following customizing/jobs for this CNPJ is displayed:
○ Signature
○ XML Version for NF-e
○ XML Version for Skip
○ XML Version for NF-e Events
○ Job for NF-e Sending
○ Job for Acknowledgements
○ Job for Skip NF-e Sending
○ Job for NF-e Event Sending
○ Job for Status Check
○ Job for B2B Sending
○ Job for Continue Process
3. The red marked statuses show missing entries. By selecting the line and clicking on the button Adapt
Configuration, you navigate to the linked IMG activity.

4. In the table, you can add, change, and delete entries.

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information PUBLIC 61
www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Implementation Help For SAP NFE Consultants: Outbound

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Implementation Help For SAP NFE Consultants: Outbound

Încărcat de

Drepturi de autor:

Formate disponibile

IMPLEMENTATION GUIDE | PUBLIC

Implementation Help for SAP NFE Consultants:

THE BEST RUN

1 Implementation Help for SAP NFE Consultants: Outbound. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Implementation Help for SAP NFE Consultants: Outbound

Configuration for NFE Outbound

1. Maintain Own Tax Numbers (CNPJ)

1. Maintain Own Tax Numbers (CNPJ)

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

2.2 Outbound Configuration

A certificate file name with extension .pfx is also valid

○ Create SSF application

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

○ Load the PSE

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

3.1. Activate the Service for Displaying the User Interfaces

● nfe_outb_monitor for NF-e Monitor

Implementation Help for SAP NFE Consultants: Outbound

3.2. Activate the Basis Services for the Virtual Hosts/Services

Implementation Help for SAP NFE Consultants: Outbound

● ur for Unified Rendering

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

5.1. System Communication – ERP to NFE

● Create a connection with connection type Logical connection.

Implementation Help for SAP NFE Consultants: Outbound

● Create a connection with connection type ABAP Connection.

Implementation Help for SAP NFE Consultants: Outbound

● Call transaction BD97.

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

6. User Roles and Authorization

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

There are different options to send batches: Use /XNFE/NFE_BATCH_PROCESS OR XNFE/NFE_BATCH_CREATE

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

1. Select your CNPJ and define the system environment.

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

12. Activate B2B Scenarios for Business Partners

Implementation Help for SAP NFE Consultants: Outbound

● Communication to business partner via PI (for example, mail)

13. Activate B2B Scenarios for Natural Persons

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

Implementation Help for SAP NFE Consultants: Outbound

1. Frequency of status request in seconds.

Implementation Help for SAP NFE Consultants: Outbound