If you’re facing discrepancies between your Item and General Ledger, it could be because of problems with your decimal precision. Limited decimal places can create discrepancies in the math between the two ledgers.

Oracle team members David Greiner, Principal Product Manager, and Kevin Barker, Senior Principal Applications Engineer, presented how to approach this problem and what solution is available to help reconcile your General Ledger with greater decimal precision.

The Problem

The current problem is that when inventory issues and labor hours are recorded for a Work Order, those quantities are currently stored with a maximum of two decimals in the unaccounted units field. This field is used by manufacturing accounting to write journal entries. For users that have transaction decimals set up with more than two decimals, the potential exists for discrepancies between the Item and General Ledgers to arise. For most use cases, it’s just a matter of small, yet annoying variances. However, for some, the differences can become significant when working on a larger scale.

The Solution

Oracle has released a data conversion program and supported procedure to update the display decimals of unaccounted units values to match transaction display decimals. This will allow for unaccounted units fields used by manufacturing accounting to store a greater decimal precision value. Increasing the decimal precision value will eliminate erroneous production costs and rounding variances and discrepancies between Item and General Ledgers. This solution is available now for users looking to reconcile these discrepancies.

When to Run the UBE (R8931CTSX)

Oracle recommends that you run the program if you have an existing installation of JD Edwards EnterpriseOne or you are upgrading to the latest release. Keep in mind, you do not have to run this UBE unless you are facing a problem with discrepancies between your Item and General Ledger. If you do wish to run the program, the timings will vary based on the following conditions:

• New installation: If you are installing JD Edwards EnterpriseOne for the first time, you do not need to run the R8931CTSX program because there is no data to convert. However, you must change the display decimals for the CTSx data items to match the display decimals of TRQT (four decimals) to avoid rounding issues.
• Upgrading to the latest release: Oracle strongly suggests that you run R8931CTSX when upgrading to the latest EnterpriseOne release as part of the Manual Table Conversions process.
• Existing installation: If you have an existing installation of JD Edwards EnterpriseOne, you must run R8931CTSX and change the display decimals for the CTSx data items to allow future CTSx values to be written with the necessary decimal precision. However, note that existing data in the CTSx fields cannot be corrected.

For more information about the process around running the UBE, check out Document ID 2438553.1 on My Oracle Support or view the full presentation, attached below, which includes a walkthrough of the problem, solution and Oracle Doc.