Nota Fiscal TRAN_DATE Field Is Filled With SYSDATE Instead of Actual Transaction Date (Doc ID 1597608.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Fiscal Management - Version 13.2.5 to 13.2.7 [Release 13.2]
Information in this document applies to any platform.

Symptoms

The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.

 

In Oracle Retail Fiscal Management (RFM) 13.2.5, we find that NF (Nota Fiscal) are posted such that FM_TRAN_DATA.TRAN_DATE is populated with SYSDATE and not VDATE.

In FM_TRAN_DATA table, the column TRAN_DATE is filled with SYSDATE instead of the actual transaction date. This value is provided within FM_TRANDATA_POSTING_SQL.INSERT_TRAN_DATA. This results in FM_TRAN_DATA.TRAN_DATE being different from TRAN_DATA.TRAN_DATE.


Steps to Reproduce:

  1. Create a PO (Purchase Order).
  2. Register schedule and a Nota Fiscal.
  3. Receive in SIM.  You can run the FM_TRAN_DATA batch on the next day.
  4. Note that TRAN_DATE field in FM_TRAN_DATA table is filled with SYSDATE and not VDATE.

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms