My Oracle Support Banner

RFI Autopurging Data Before Issues Can Be Looked At (Doc ID 2733667.1)

Last updated on DECEMBER 04, 2020

Applies to:

Oracle Retail Integration Cloud Service - Version NA and later
Information in this document applies to any platform.

Symptoms

The auto purging needs to be fixed as currently it is deleting both processed and non processed status rows. This makes finding issues and getting them resolved difficult.

The process of getting data into and out of RFI has been made over complicated with to many points of failure and very poor or no alerting or monitoring. It is very easily for financial information to completely go missing using the current process. Understand to fix it will need a big redesign which we don;t have the time for so this is just a request to not purge failed status rows.

Request is that only status rows for data that has been processed should be considered for purging using the autoPurgeDelay in rfi-deployment-env-info.json.
Leave all failed status rows for operations or customer auditors when they realize financial data is missing.


Steps to reproduce:
1. In rfi-deployment-env-info.json set "autoPurgeDelay":"1d"
2. Try and send data from invoice matching to financials via rfi
3. If a day later data is missing the cloud team (as customers cannot access the error tables) will notice that there are no failed status rows in tables like RFI_CFIN_REIM_ACNT_ENT_STATUS & RFI_CFIN_AP_INV_INT_STATUS

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.