My Oracle Support Banner

NF Approved In Contigency Controlled By DFe Partner Cannot Be Set To Error If Final Approval Fails (Doc ID 2644482.1)

Last updated on MARCH 05, 2020

Applies to:

Oracle Retail Fiscal Management - Version 14.1.3.2 and later
Information in this document applies to any platform.

Symptoms

RFM should not allow NF to be set to "E"rror status after it was previously approved in Contingency (EPEC)

Steps to reproduce:
1) Issue a NF ( Transfer , STOCK, etc)
2) NF status will be set to NFE_P
3) Staging status (FM_STG_NFE) will be set as follows
- status: NFE_P
- prev_status: NFE_X
4) NDD picks the record for processing, staging status as follows:
- status: NFE_I
- prev_status: NFE_P
5) State Sefaz (regular) is OFF
6) NDD switches to Contingency mode
7) NDD authorizes (approves) NF in Contingency mode in National SEFAZ
8) NDD sends "A_C" (Approved in Contingency) status to RFM by calling FM_MS_NFE_SQL.CONSUME and passing status "A_C"
9) RFM recognizes and posts out final approval request to NDD, staging status as follows:
- status: NFE_F
- prev_status: NFE_X
10) Once State SEFAZ( Regular) is ON, NDD picks the record for processing, staging status as follows:
- status: NFE_I
- prev_status: NFE_F
11) State SEFAZ (Regular) returns an rejection (error code 468 as attached) to NDD
12) NDD sends status "E" to RFM by calling FM_MS_NFE_SQL.CONSUME and passing status "E"
12.1 fm_fiscal_doc_header.status is updated to "E"rror
12.2 FM_STG_NFE.STATUS is updated to "E"rror

Step 12.1 is incorrect. NF is authorized and cant be updated to error as this allows users to put it back to worksheet and try to approve again. Also, an authorized NF cannot be set to Error.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.