Data Conversion - Cost Changes Not Keeping The Original APPROVAL_DATE And APPROVAL_ID (Doc ID 3039495.1)

Last updated on AUGUST 09, 2024

Applies to:

Symptoms

On : 24 version, Data Conversion

ACTUAL BEHAVIOR
---------------
When loading Cost Changes to MFCS using the Data Conversion application, we noticed that the “original” APPROVAL_DATE and APPROVAL_ID from the source system, which is on the data conversion file, is being ignored and Data Conversion is populating instead:
  - APPROVAL_ID with the user that is running the Data Conversion process;
  - APPROVAL_DATE with the current system date.

1) On the data conversion .dat file the Cost Change shows the following “original” data:
  - APPROVAL_DATE = 01-MAR-2023
  - APPROVAL_ID = J83537953

2) Then on the data uploaded to the SVC_COST_SUSP_SUP_HEAD staging table, it still shows:
  - APPROVAL_DATE = 01-MAR-2023
  - APPROVAL_ID = J83537953

3) However, in the MFCS final table (COST_SUSP_SUP_HEAD), this information seems to have changed:
  - APPROVAL_DATE = 06-May-2024 09:25:02 (which is the timestamp the data was loaded)
  - APPROVAL_ID = helio.teixeira@oracle.com (which is the user that run the data conversion process)



This behavior is confusing the user as it deviates from the expected functionality of the data conversion tool, which should accurately reflect the values uploaded from the original source data.

Cause

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