E1: 41: As Of (F41112) TC Program Corrupts Cummulative Amounts (CUMA) (Doc ID 2499244.1)

Last updated on JUNE 12, 2023

Applies to:

Symptoms

F41112 TC Program

Loss of functionality
After the conversion of the As Of Table (F41112) from 9.0 to 9.2, the Amount - Net Posting (AN01-AN12) fields are correct, but the Cumulative Amount (CUMA) field has two extra zeros on all the Japanese company records in the file. Japanese Yen Currency is managed with 0 decimals and only the Japanese company records are affected.

Significance of the loss
This makes integrity reporting impossible because the Cumulative Amount (CUMA) field is used to calculate the amount in the integrity report. Without accurate integrity reports the company loses control of inventory accuracy and financial reporting to government agencies which could subject them to fines or other sanctions.

Sequence of events

1. Sign into the 9.0 system.
2. Using the databrowser, go into the 9.0 As Of Table (F41112)
3. In the Company Field, populate the Japanese Company Number and populate a valid item number and click Find.
4. Export the records for the Japanese company and Item to an Excel Spreadsheet.
5. Run the JD Edwards Standard Table Conversion program to convert the records in the As Of Table (F41112) from the 9.0 to the 9.2 system.
6. Sign into the 9.2 system to review the converted records.
7. Using the databrowser, go into the 9.2 As Of Table (F41112)
8. In the Company Field, populate the Japanese Company Number and populate the item number used in the 9.0 query and click Find.
9. Export the records for the Japanese company and Item to an Excel Spreadsheet.
10. Compare the value in the Cumulative Amount (CUMA) field in the 9.0 records to the 9.2 records.
11. All the 9.2 CUMA values have two extra zeros.

Where the issue happens
This issue occurs in all environments where the JD Edwards Conversion Programs are used to convert the 9.0 As Of Table (F41112) records to 9.2 records.

Expected or acceptable result
The Table Conversion Program that converts the As Of (F41112) records needs to be updated to prevent the addition of two zeros to the F41112.CUMA field so that other customers upgrading to 9.2 from earlier releases do not have the problem.

Changes

Cause

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