nfe consult guide inbound

7/25/2019 Nfe Consult Guide Inbound

http://slidepdf.com/reader/full/nfe-consult-guide-inbound 1/37

Implementation Help for NFE Consultants: Inbound

Document version: 1.0 – 2015-10-13

Implementation Help for SAP NFE Consultants:Inbound

CUSTOMER



Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. You can find the

latest version at the following location: help.sap.com/nfe .

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.0 2015-10-13 Implementation Help for SAP NFE Consultants: Inbound

2

CUSTOMER

© Copyright 2015 SAP SE or an SAP affiliate company.

All rights reserved.

Implementation Help for SAP NFE Consultants: Inbound

Document History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnfe



Content

1 Implementation Help for SAP NFE Consultants: Inbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5


Content

CUSTOMER


All rights reserved. 3



4

CUSTOMER


All rights reserved. Implementation Help for SAP NFE Consultants: Inbound



1 Implementation Help for SAP NFEConsultants: Inbound

SAP Nota Fiscal Eletrônica (SAP NFE) provides the integration between a company and the Brazilian government

system as a main scenario. Another main scenario represents the integration between a company and its

business partners (BP).

This document describes the configuration of the NF-e inbound procedures.

Figure 1

Inbound Scenario – Basic Process

To comply with the legal requirements of Brazil the inbound scenario has the scope to receive, save and archive

NF-e documents and to check the authorization against government systems.

Figure 2

Inbound Scenario – Inbound Automation

SAP NFE provides the inbound automation to receive, save, and archive NF-e documents and to check the

authorization against government systems. In addition, NFE can automatically post the corresponding documents

in ERP, such as goods movement and invoice.



CUSTOMER





Figure 3

Content

1. Maintain Own Tax Numbers

2. Digital Signature

○ Prerequisites

○ Inbound Configuration

3. Web Services

○ Activate the Service for Displaying the User Interfaces

○ Activate the Basis Services for the Virtual Hosts/Services

4. Number Ranges for Batches

5. System Communication

6. User Roles and Authorization

7. Batch Job Planning

8. Maintain Logical System for Own Tax Numbers

9. Maintain Control Parameters for Process Flow

10. Define Control Parameters for Process Steps

11. Control Parameters for Process-Independent Actions

12. Maintenance of Messages for Temporary Error

13. Communication to Business Partner

○ Maintain Mail Sender Parameters for Own Tax Numbers

○ Maintain Communication Parameters for Partner Tax Numbers

14. NF-e: Define Reasons for Rejection; Assign to Events

15. NF-e: Maintain Business Process Determination for Inbound NF-es

16. NF-e: Maintain Assignment of Item Category to CFOP Code

17. NF-e: Maintain Receiver Acknowledgment Deadlines

Maintain Own Tax Numbers

As a first setting, the tax number(s) of your company need(s) to be defined to control further customizing settings

based on this/these CNJP(s).

6

CUSTOMER







Use transaction SPRO and navigate to the SAP Customizing Implementation Guide (IMG): Nota Fiscal

Eletrônica General Settings Maintain Own Tax Numbers

Figure 4

You enter your company's tax numbers, as well as an appropriate region and descriptions:

Figure 5

Digital Signature

Prerequisites

● User Role

Prerequisite to capture the digital signature is the user role SAP_QAP_RZL_ADM to execute transaction

STRUST.

● Download of Certificate

In order to issue electronic invoices, the xml must be signed with a digital certificate. This certificate must

comply with the ICP-Brazilian standards that secure the communication and access between the NFE

system and the government servers. To receive XMLs, the buyer has to validate the signature of the

incoming xml documents from the B2B Partner to ensure the authentication and integrity. For the

verification of the digital signature of incoming NF-es, the CA (certification authority) has to be imported into

the system.

You can download the CA certificates as described here:



CUSTOMER





www.iti.gov.br/icp-brasil/certificados .

You have to import all CA certificates of the signers of the NF-e you receive in your inbound scenario. Only

the lowest intermediate certificate from each CA is required, not the entire certificate chain.

● 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.

Inbound Configuration

● Create PSE for Signature Check

From the Administration workplace, use transaction STRUST: Maintain System Security Information

Figure 6

Create a self-signed PSE for SSF NFE signature validation

8

CUSTOMER





http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.iti.gov.br%2Ficp-brasil%2Fcertificados



Figure 7

Confirm the suggestion of PSE

Figure 8

● Import CA Certificates

After the data from the previous step was saved successfully, you need to import the CA certificate of the

issuer of the signing certificate.



CUSTOMER





You can download the CA certificates as described here: www.iti.gov.br

You have to import all CA certificates of the signers of the NF-e you receive in your Inbound scenario, and

that might be a double digit number. Still, you don’t need the entire certificate chain, only the lowest

intermediate certificate from each CA.

Note

To find out which CA’s are needed, you either ask the Business partner for the certification provider he

used or you might check the CA in the XML of the Inbound-NF-e. Therefor you have to open the XML,

search for the tags X509Certificate and /X509Certificate and copy the content of the

X509Certificate tag to a notepad file and save it as .cer file.

Figure 9

With a double click on the cer file, Windows displays the certificate information such as Issued by:

10

CUSTOMER





http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.iti.gov.br



Figure 10

Import the CA certificate of the certification authority in STRUST

Figure 11

Select the correct certificate for the import



CUSTOMER





Figure 12

The certificate is displayed in the certificate list:

Figure 13

Click on Add to Certificate List

12

CUSTOMER







Figure 14

Repeat the same step for other CA certificates. The CA certificates for all certification authorities of your

business partners have to be imported one by one. After importing and adding all certificates to the list, you

must save to persist the changes.

Figure 15

● Troubleshooting

If you receive errors, such as SSF kernel error: invalid parameter, change the file format:

Figure 16

Web Services

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 transaction code SICF and choose Execute.

In the navigation tree for the Virtual Hosts/Services under default_host sap bc webdynpro xnfe :



CUSTOMER





Figure 17

Activate the service for displaying the user interfaces for each of the following entries by using the context menu

and selecting Activate Service:

● ssf maintenance

● download_mass_xml

● gatekeeper_workplace

● nfe_fiscal_workplace for

● nfe_fisc_workplace_arch

● nfe_log_workplace

● nfe_receiver_ack_wp

● nfe_list_monitor

● nfe_liststa_monitor

● nfe_analytics

● innfe_dab

Figure 18

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 :

Figure 19

14

CUSTOMER







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

Figure 20

Number Ranges for Batches

Depending on your industry and/or if you are downloading XML documents from the National Environment, the

sending of events is legally required.

Batches that package NF-es require a number range both to identify and to monitor the batches in process. In the

Event Batch Monitor, you can use this number range to access all events that the system has combined into one

batch. Use transaction code SNUM to create the number range for the object/XNFE/EVBT.

Note

CT-e and MDF-e events are not authorized in packages. Every event is send individually and synchronously.



CUSTOMER





Figure 21

Create an interval by selecting Change Intervals.

Figure 22

Insert the interval 01 with a length of 15 digits.

Figure 23

The download of XML documents from the National Environment is executed in batches of up to 10 NF-e access

keys.

Use transaction code SNUM to create the number range for the object /XNFE/NFDL

16

CUSTOMER







Figure 24

Create an interval by selecting Change Intervals.

Figure 25

Insert the interval 01 with a length of 15 digits.

Figure 26

System Communication

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 the system data of the feeder system.



CUSTOMER





● On the tab page Logon & Security, enter the RFC user created in the SAP ERP system.

● Save your settings.

Figure 27

Figure 28

You must maintain the relationship between the RFC destination and the logical system.

● Call transaction BD97.

● Enter the Standard RFC destination for BAPI calls.

● Save your settings.

18

CUSTOMER







Figure 29

System Communication – NFE to SAP NetWeaver PI

NFE and SAP NetWeaver PI have to be connected. Therefore, use transaction sxmb_admin Integration Engine

Configuration .

Figure 30

In the Integration Engine Configuration Data, fill out the role 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.



CUSTOMER





Figure 31

User Roles and Authorization

To adjust the user menu for SAP NFE Outbound, the following roles are needed:

● /XNFE/WP_NFE_ADMIN

● /XNFE/WP_NFE_IN_FISCAL

● /XNFE/WP_NFE_IN_LOGISTIC

● /XNFE/WP_NFE_IN_REPORTS

1. /XNFE/WP_NFE_ADMIN

TransactionPFCG 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.

Figure 32

2. /XNFE/WP_NFE_IN_FISCAL

TransactionPFCG shows that this role is intended for the user of inbound monitors and workplaces for NF-e,

for example, Fiscal Workplace for NF-e. 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

20

CUSTOMER







Figure 33

3. /XNFE/WP_NFE_IN_LOGISTIC

TransactionPFCG shows that this role is intended for the user of the NF-e Logistics Workplace. 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.

Figure 34

4. /XNFE/WP_NFE_IN_REPORTS

TransactionPFCG shows that this role is intended for the user who wants to run an analysis of various NF-e

processing situations. It does not contain authorizations and is therefore only meant to create and set up the



CUSTOMER





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.

Figure 35

Batch Job Planning

For processing inbound NF-es, batch jobs are required.

Figure 36

22

CUSTOMER







For more detailed information, see the application help of SAP Electronic Invoicing for Brazil (SAP Nota Fiscal

Eletrônica) under Configuration for Electronic Invoicing for Brazil (SAP NFE) Configuration of Inbound Batch

Job Planning for NF-e/CT-e Inbound .

For creating a batch job, use transaction code SM36. Enter a job name and go to Start condition.

Figure 37

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

Figure 38



CUSTOMER





Figure 39

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

Figure 40

Maintain Logical System for Own Tax Numbers

When inbound NF-es are processed, process steps can be carried out that require communication with an ERP

system. The corresponding ERP system is determined using the recipient's CNPJ number from the incoming NF-

e. In this customizing activity, you assign the ERP system to a recipient’s CNPJ number.

Figure 41

Select your CNPJ and define the system environment.

24

CUSTOMER







Example

If an NF-e is received for CNPJ number 07.358.761/0001-85, system ERPCLNT001 is determined

Figure 42

Maintain Control Parameters for Process Flow

In this customizing activity, you can specify the settings for the process steps of an incoming NF-e document.

Figure 43

These process steps are determined from the business process to which the NF-e was assigned based on the

CFOP codes of its items (the process flow for this business process is contained in table /XNFE/PROCFLOW).

Figure 44

In the following table, you can see how the process flow is handled depending on the sender's and/or recipient's

CNPJ number in the incoming document. Alternatively, you can have a look at system table /XNFE/PROCSTEP.

The control options let you control whether the processing of a process step must be done manually by the user,

or automatically by the system. For three process steps you can choose between option manual and automatic.

The Deactive flag can be set for the following specific process steps with the check box icon to run over this step.



CUSTOMER





Figure 45

Define Control Parameters for Process Steps

Specific process types and process steps can be further influenced by this customizing setting in the IMG of

Nota Fiscal Eletronica Inbound Define Control Parameters for Process Steps .

The following table displays an example of a parameter and its possible value to influence the outcome of the

process flow.

Figure 46

The available parameters are BLDCOUNT (Entry of Goods Quantity), LSTLOGWP (Step relevant for Logistics

Workplace),TRANSTDF (Control of XML Data Transfer), DANFEPRE (PDF Preview), and SIGVALID (Signature

Validation).

To see all available parameters and list possible values, refer to the IMG activity documentation of Define Control

Parameters for Process Steps.

Control Parameters for Process-Independent Actions

In the customizing activity IMG Nota Fiscal Eletronica Inbound Control Parameters for Process-Independent

Actions , you can set further control parameters for NF-e documents.

26

CUSTOMER







Figure 47

The following parameters are available:

● UNKNCNPJ: This parameter influences the system reaction if the CNPJ Number differs from your own CNPJ

defined in Customizing.

● TRANSFER: This parameter determines which types of transfers are available for the XML document in the

List and Download Monitor once the XML is downloaded.

●

RCVDUPLI (see example): This parameter can be set to handle the documents in case it is received morethan once.

For all available parameters and their values, refer to the application help of NFE 10.0 in chapter Process Settings

and Customizing (Inbound) of the section Configuration of SAP NFE and the IMG activity documentation of Control

Parameters for Process-Independent Actions.

Example

Reaction When Duplicate Received (RCVDUPLI):

If an NF-e is received more than once, you have two options for dealing with such a duplicate:

● Blank -> The exception is visible as application error in PI: This is the default setting -> The PI message

monitor displays the attached XML document with an application error.

● 1 -> Ignore; Entry in History Table: The PI message monitor displays the XML message as successfully

processed. An entry in the document history is the only indicator that the document was received more

than once.

Maintenance of Messages for Temporary Error

In the Customizing activity IMG Nota Fiscal Eletronica Inbound Maintenance of Messages for Temporary

Error , you can maintain message classes and numbers for a combination of process type and process step. In

the process step, this means that a step for which the corresponding message is issued, is set to being a

temporary error. The messages for the BAPI Return Information are evaluated once the back-end system has

been called.

In Customizing, you define the corresponding message class and message number for a combination of processtype and process step. There is a predefined selection of process steps available to you. Suitable process steps

are not available for every process type.



CUSTOMER





Figure 48

Example

Posting a goods receipt in the ERP system leads to an error there, for example, the material master is blocked.

This error previously meant the step Post Goods Receipt was set to error. If you enter (in the table) the

message class and message number that correspond to the goods receipt being blocked, the step is set toTemporary Error. When you run report /XNFE/NFE_CONTINUE_PROCESS (required to schedule in the

background), the system collects the documents that have a temporary error and attempts to continue the

process. In this example, the step Post Goods Receipt is executed again.

Communication to Business Partner

Maintain Mail Sender Parameters for Own Tax Numbers

In this Customizing activity, you assign an e-mail address to incoming NF-es for your own tax number (CNPJ).

Figure 49

This e-mail address is used as the sender address for e-mail communication. If you do not define this entry, the

system tries to use the e-mail address of the current active user. You can enter the e-mail text with the rejection in

the field Rejection Text Name and the e-mail text with the acceptance in the field Acceptance Text Name.

Figure 50

Maintain Communication Parameters for Partner Tax Numbers

In this Customizing activity, you define the communication parameters for a business partner.

28

CUSTOMER







Figure 51

Figure 52

The business partner tax number must be entered. You can also enter your own tax number and link it with the

business partner tax number.

You can specify which language should be used when sending texts to the business partner. (The text must exist

in the respective language.) If no language is entered, the language in which you are logged on during the process

is used by default.

The recipient e-mail address determines where notifications are send during e-mail communication. If no recipient

e-mail address is entered for a business partner tax number, then e-mail notification is not possible for this

business partner.

NF-e: Define Reasons for Rejection and Assign to Events

In this Customizing activity, you specify the reasons for rejecting the processing of inbound NF-es.



CUSTOMER





Figure 53

In the keyfield Rejection, you can enter a sequence number, or a word that describes the rejection reason.

However, it is not displayed in the pop up screen of the Fiscal Workplace.

In the field Send Type of Event, you can either select Do not send Event, or one of the following events: Operation

Denied or Operation Terminated. In this case, an event is send automatically to the authority after rejecting the

NF-e.

The Rejection Text defined in this activity describes the reasons for rejection. This text is displayed in the pop up

screen of the Fiscal Workplace as a selection help and is also send to the authorities together with a specific status

code. If vendor notification is active (in the rejection case), the selected rejection text can be send to the businesspartner as part of an e-mail.

Figure 54

In the field Text Name NF-e/CT-e Rejection, you can select the text of an e-mail depending on a specific reason.

This text is maintained in transaction code SO10 and the text ID must be NFE.

30

CUSTOMER







Figure 55

You can use the following fields from structure /XNFE/NFE_COM_TEXT to create the texts:

● NFEID - Access key

● TYPE - NF-e type

● FINNFE - Issue function

● CNPJ_EMIT - CNPJ number of the NF-e issuer

● C_XNOME - Company name of the NF-e issuer

● CNPJ_DEST - CNPJ/CPF number of the NF-e recipient

● E_XNOME - Company name of the NF-e recipient

● SERIE - Series

● NNF - NF-e number

● NOTIFICATION - Rejection text

In the Fiscal Workplace, the rejection texts are shown in a popup for selection:

Figure 56

In this example, an NFE was denied due to wrong pricing and the event Operation Denied was send to authorities.

This is also displayed in the Fiscal Workplace. The status of the NF-e was set to Document rejected.



CUSTOMER





Figure 57

It is also displayed as rejected in the History and the Status Overview.

Figure 58

NF-e: Maintain Business Process Determination for Inbound NF-es

In this Customizing activity in IMG Nota Fiscal Eletronica Inbound NF-e NF-e: Maintain Business ProcessDetermination for Inbound NF-es , you assign specific business processes to incoming NF-es for further

processing. The business processes are determined based on the CFOP codes that are assigned to the NF-e

items. If the CFOP code does not enable identification of a unique business process, the NF-e is not assigned

Example

If an NF-e in which all items have CFOP 5101, is processed, the NF-e for Normal Purchasing process is executed.

If an NF-e whose CFOPs do not lead to a unique process type (such as 5101), is processed, an error occurs.

Figure 59

You have to correct this inconsistency in Customizing - after which you can determine the business process again

- using menu path Administration Incoming NF-es Redetermine Business Process .

If an NF-e that contains only CFOPs that are not defined here in its items is processed, a predefined process is

executed that consists of the steps Check Business Partner's Signature and Check Authorization after NF-e

Receipt. If you do not want this to happen, the administrator can also start redetermination through the report

after adjusting the Customizing settings.

NF-e: Maintain Assignment of Item Category to CFOP Code

In the Customizing activity IMG Nota Fiscal Eletronica Inbound NF-e NF-e: Maintain Assignment of Item

Category to CFOP Code , you can maintain the assignment of item categories to CFOP codes. This assignment is

relevant for determining the correct business process.

The item categories represent the meanings of the CFOP codes. They have different priorities in the

determination of the business processes. If an NF-e contains both main items and other item categories, only the

main items are used to determine the business process.

In subcontracting cases, the NF-e can contain a final product (= main item) and the subcontracting components

(= symbolic return). To determine the correct business process, the entries must be maintained for the final

product and the subcontracting components, to enable assignment of the corresponding item categories:

32

CUSTOMER







Figure 60

Figure 61

NF-e: Maintain Receiver Acknowledgment Deadlines

You use the Customizing activity IMG Nota Fiscal Eletronica Inbound NF-e NF-e: Maintain Receiver

Acknowledgment Deadlines , to specify the deadlines for final receiver acknowledgment events by which the

transaction concerned needs to be reported to SEFAZ by means of a suitable end event. Specify the deadlines for

your own tax number CNPJ and the related region CUF. You can also make generic entries (blank for the CNPJ

and the CUF) for all CNPJs and regions.



CUSTOMER





Figure 62

There are two types of final events in this group:

1. Denial Event (event type 210220 - operation denial)

2. Confirmation Events (event type 210200 - operation confirmation and event type 210240 - operation

termination)

The duration of the confirmation of the transaction considers the required transport route. Three tiers are

available:

● Intrastate: The goods transport takes place within the boundaries of a state.

● The goods transport crosses the state boundary into other states.

● SUFRAMA: The goods transport involves the Manaus free trade zone.

34

CUSTOMER







Typographic Conventions

Table 2

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries

to make entries in the system, for example, “Enter your <User Name> ”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the

documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific

content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles,

pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, database table names, and key concepts of a programming language

when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard


Typographic Conventions

CUSTOMER



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D123456%26_NLANG%3Den%26_NVERS%3D0

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D123456%26_NLANG%3Den%26_NVERS%3D0

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



www.sap.com

© Copyright 2015 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.

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 c ompany) in Germany and other

http://www.sap.com/

nfe consult guide inbound

Documents