Electronic Nota Fiscal – NF-e
SAP Best Practices
Purpose and Benefits
Objective
 This scenario describes the processes of Nota Fiscal Electronic (NF –e) for:
1.
2.
3.
4.
Nota Fiscal Electronic Cancel
Switched or Posted under Contingency
2.1 NF-e Switched to Contingency – NF-e Writer
2.2 NF-e Switched to Contingency (Only Cancel) – MM
2.3 NF-e Switched to Contingency – SD
2.4 NF-e Posted Under Contingency
Nota Fiscal Electronic Skipping
Nota Fiscal Electronic Gaps Skipping
Benefits
 Monitoring process / action of users for the communication failure with SEFAZ or Gaps
occurring during the execution of procedures involving Nf-e
© 2012 SAP AG. All rights reserved.
2
Required SAP Applications and Company Roles
Required SAP Applications
 Enhancement package 6 for SAP ERP 6.0
Company Roles
 Employee (Brazil Localization)
 Warehouse Clerk
 IT Administrator
© 2012 SAP AG. All rights reserved.
3
Detailed Process Description
Electronic Nota Fiscal
This scenario describes the possible processes that are required for the output Nota
Fiscal in Contingency (when there are communication problems with the SEFAZ) and
possible Gaps that may occur during procedures to output NF-e.
The procedures are differentiated as follows:
 Nota Fiscal Electronic Cancel: The cancelation of Electronic Nota Fiscal occurs when you have
the authorization from SEFAZ, but for any reason, you must cancel the Electronic Nota Fiscal. At
this time, the company must create a Request for Cancel NF-e (XML) to send to SEFAZ.
 NF-e Switched to Contingency – NF-e Writer: The Nota Fiscal Electronic Switched to
Contingency occurs when there is an urgency to issue the electronic Nota Fiscal but there is no
quick answer from SEFAZ (for example, a communication error or a slow response time from
SEFAZ). The user switches the NF-e to contingency and creates a new NF-e that must be
printed with the security form.
 NF-e Switched to Contingency (Only Cancel) – MM: The Nota Fiscal Electronic Switched to
Contingency occurs when there is an urgency to issue the electronic Nota Fiscal but there is no
quick answer from SEFAZ (for example, a communication error or a slow response time from
SEFAZ) The user switches the NF-e to contingency and prints it with the security form.
© 2012 SAP AG. All rights reserved.
4
Detailed Process Description
 NF-e Switched to Contingency – SD: The Nota Fiscal Electronic Switched to Contingency occurs
when there is an urgency to issue the electronic Nota Fiscal but there is no quick answer from
SEFAZ (for example, a communication error or a slow response time from SEFAZ). The user
switches the NF-e to contingency and creates a new NF-e that must be printed with the security
form.
 NF-e Posted Under Contingency: This step is necessary when the Business Place must be under
contingency (for example, without communication, communication failed, or a slow response time
from SEFAZ) .The user sets the Business Place under contingency to create an NF-e. Therefore,
these NF-es are printed on the security form.
 Nota Fiscal Electronic Skipping: The Electronic Nota Fiscal Skipping occurs when an NF-e was
rejected by SEFAZ, rejected by the messaging system, or was rejected due existing GAP
numbering. For these situations, the company must create a Request for NF-e (XML) Skipping to
SEFAZ.
 Nota Fiscal Electronic Gaps Skipping: The Nota Fiscal Electronic Gaps Skipping occurs when
you have a gap in the NF-e number range. You know gaps exist when you see a number that is
incompatible with NF-e numbers.
© 2012 SAP AG. All rights reserved.
5
Process Flow Diagram
Event
Nota Fiscal Electronic Cancel
NF-e Cancel
Employee (Brazil Localization)
Identifies the
need to cancel
an NFE
© 2012 SAP AG. All rights reserved.
Send the request
to cancel for
SEFAZ
Cancel
Approved?
No
Send the new
request to cancel
for SEFAZ
Yes
NFe Cancel
6
Process Flow Diagram
Employee (Brazil Localization) /
Warehouse Clerk
Event
Switched or Posted under Contingency
NF-e Switched
to Contingency –
NF-e Writer
NF-e Switched
to Contingency
(Only Cancel) –
MM
NF-e Switched
to Contingency –
SD
Choose the NFe
in the J1BNFE
monitor and put
in contingency
Choose the NFe
in the J1BNFE
monitor and put
in contingency
Choose the NFe
in the J1BNFE
monitor and put
in contingency
Cancel the
Original
Document
(transaction
MBST)
Cancel the
Original
Document
(transaction
VF11)
Switch the
Business Place
to Contingency
Wait for answer
SEFAZ
In Transaction
J1B3N enter the
number of doc.
Converted for
contingency
The system will
cancel the Nota
Fiscal selected
and will generate
a new NF
Contingency
Create a new
NF-e
NF-e Posted
Under
Contingency
Choose the NFe
in the J1BNFE
monitor and put
in contingency
Create Electronic
Nota Fiscal in
Contingency
End
In the transaction
VF01 and with
Delivered number
make a new NF-e
Posted under
Contingency.
End
© 2012 SAP AG. All rights reserved.
End
End
7
Process Flow Diagram
Electronic Nota
Fiscal Skipping
IT
Administrator
Event
Nota Fiscal Electronic Skipping
Electronic Nota
Fiscal Gaps
Skipping
In transaction SE38, execute the
program
J_1BNFECHECKNUMBERRANGE
S
Employee (Brazil Localization)
In the transaction
ZNFENUMGAPS
check the status for
request
In transaction
J1BNFE choose
the NFe rejected
by SEFAZ
Status 1 or
2?
Entry with the
Reason of Cancel
and request the
cancel for SEFAZ
Receive
confirmation of
SEFAZ
End
© 2012 SAP AG. All rights reserved.
2
Use the transaction
ZNFENUMCHECK to
adjust the numbers
and new send
skipping request for
SEFAZ
1
Numbering of
Eletronic Nota
Fiscal Skipping
End
8
Legend
<Function>
Symbol
Description
Usage Comments
Band: Identifies a user role, such as Accounts
Payable Clerk or Sales Representative. This band
can also identify an organization unit or group,
rather than a specific role.
Role band contains
tasks common to that
role.
Symbol
Diagram
Connection
The other process flow symbols in this table go
into these rows. You have as many rows as
required to cover all of the roles in the scenario.
External
to SAP
External Events: Contains events that start or end
the scenario, or influence the course of events in
the scenario.
Business
Activity / Event
SubProcess
Reference
Process
Decision
Flow line (solid): Line indicates the normal sequence
of steps and direction of flow in the scenario.
Flow line (dashed): Line indicates flow to
infrequently-used or conditional tasks in a
scenario. Line can also lead to documents involved
in the process flow.
Connects two tasks in
a scenario process or
a non-step event
Business Activity / Event: Identifies an action that
either leads into or out of the scenario, or an
outside Process that happens during the scenario
Does not correspond
to a task step in the
document
Unit Process: Identifies a task that is covered in a
step-by-step manner in the scenario
Corresponds to a task
step in the document
To next / From last Diagram: Leads
to the next / previous page of the
Diagram
Flow chart continues on the next /
previous page
Hardcopy / Document: Identifies a
printed document, report, or form
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Financial Actuals: Indicates a
financial posting document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Budget Planning: Indicates a
budget planning document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Manual Process: Covers a task
that is manually done
Does not generally correspond to
a task step in a document;
instead, it is used to reflect a task
that is manually performed, such
as unloading a truck in the
warehouse, which affects the
process flow.
Existing Version / Data: This block
covers data that feeds in from an
external process
Does not generally correspond to
a task step in a document;
instead, this shape reflects data
coming from an external source;
this step does not have any
incoming flow lines
System Pass / Fail Decision: This
block covers an automatic
decision made by the software
Does not generally correspond to
a task step in the document;
instead it is used to reflect an
automatic decision by the system
that is made after a step has been
executed.
Financial
Actuals
Process Reference: If the scenario references
another scenario in total, put the scenario number
and name here.
Corresponds to a task
step in the document
Sub-Process Reference: If the scenario references
another scenario in part, put the scenario number,
name, and the step numbers from that scenario
here
Corresponds to a task
step in the document
Process Decision: Identifies a decision / branching
point, signifying a choice to be made by the end
user. Lines represent different choices emerging
from different parts of the diamond.
Does not usually
correspond to a task
step in the document;
Reflects a choice to
be made after step
execution
© 2012 SAP AG. All rights reserved.
Usage Comments
Hardcopy /
Document
Budget
Planning
Unit Process
Process
Reference
Description
Manual
Process
Existing
Version /
Data
System
Pass/Fail
Decision
9
© 2012 SAP AG. 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 AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power
Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,
Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks
of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App
World are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.
© 2012 SAP AG. All rights reserved.
10