Purpose
The purpose of this page is present the NF-e Gap report J_1BNFECHECKNUMBERRANGES. How to run, use and configurations.
Overview
Working with Nota Fiscal Eletrônica (Brazilian Electronic Invoice), sometimes gaps in the official number range may happen due several reasons, like update termination, network problems, etc. In order to help customers to report those gaps to SEFAZ (Brazil's tax authority), SAP has released this report that should be run once in a month, that will read all the customization regarding the number range objects, and perform a sequential read in all notas fiscais tables in order to identify gaps. If any gap exists, the report will also send automatically to GRC, triggering the skip process and get the SEFAZ acknowledge.
The NF-e Gap Report
Basically the report requires only a couple of the parameters to run:
This report allows you to make execution as much as you can without actually trigger the skipping to GRC. You just have to use the 'Test Run' flag. When you validates the information, you can run 'for real'. You can also decide if you want to use Asynchronous or Synchronous execution. The difference is, report will run until all the notas fiscais numbers found as gaps be sent to GRC. If you decide to use 'Asynchronous' method, report will run in few seconds and the control will pass to the SAP engine control the execution.
The Main Customizing View
It is very important to make the correct customization before run the report for the first time in the view J_1BNFENUMCHECKV. The customization should be done via Company Code. Check how the customization looks like:
Here you insert the business place, the object of the number range related in the process, the number and finally in the field 'To Number', you insert the last number verified.
- Why this last field is so important?
This field is important if you already reported any time a gap to SEFAZ in old numbers. Lets took our example:
Bus. Place
|
Subobj.val
|
No
|
To number
|
|---|---|---|---|
| 0001 | BR9901 | 01 | 6963 |
The number 6963 was the last number checked by the report. This means, in the next execution of the report, it will not read from the number zero to check gaps, but will start from number 6963. So, this means if it is the first time you are executing the report and you never report a gap to SEFAZ before for this combination, is natural to have the number '0' in this field. However, let's say in your internal control, it is the first time you are executing the report, but you already report to SEFAZ gaps until number 17038. Hence, you should insert the value 17038 in the field 'To Number'. With that, the report will start from this number to.
After execution
After the execution, you will see this:
Those are the notas fiscais number that the system identify as gaps, and it will report to SEFAZ. At this point, the skipping process was trigger at GRC/PI and in a few seconds we will get the SEFAZ approve for it.
Following up
You can follow up the results inside table J_1BNFENUMGAP. This table keeps the register of the access key create for this gap, the version, all the information about form, brunch, company code and the most important one, if the skip request was authorized by SEFAZ. See field 'Status'.
You can also access the information of this table inside J1BNFE, menu Goto > Gap Monitor.
Related Content
Related Documents
Related SAP Notes/KBAs
Here is the list of main SAP notes and KBAs related with the report:
Fonte: https://wiki.scn.sap.com/wiki/display/LOCLA/NF-e+Gaps+Report
Nenhum comentário:
Postar um comentário