RFM Does Not Send Local Timestamp At Location Level For NFe Approval (Doc ID 2219094.1)

Last updated on JANUARY 03, 2017

Applies to:

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

Symptoms

When RFM integrates with DF-e partner, Nota Fiscal document data model supports the publication of the issue_date with timezone as part of the NF Header at FM_FISCAL_DOC_HEADER.ISSUE_DATE_TZ table/column.


There is an issue in the logic of how RFM sends the timestamp due to which SEFAZ can reject fiscal document with the following messages:
1. 703 - Data-Hora de Emissão posterior ao horário de recebimento
2. 578 – Data do evento não pode ser maior que a data de processamento
3. 558: Data de entrada em contingência posterior a data de recebimento

In order to be compliant with Fiscal authority when requesting NF approvals/events, RFM should use the timezone that is associated with the location (store/WH) and publish the fiscal documents with consistent data, i.e., to send out the correct timestamp/timezone of the location that is issuing that NF.

Changes

 

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