My Oracle Support Banner

Large Decimal Numbers for GL Currency Inverse Precision Cause Requisitions Error: FRM-40831: Truncation occurred: value too long for field quantity_committed (Doc ID 2416880.1)

Last updated on JULY 04, 2018

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Oracle Purchasing - Version 12.0.0 and later
Information in this document applies to any platform.
Purchase Order (PO), Requisitions
GL Currency Inverse Rates

Symptoms

GL inverse rates are getting calculated by the system with a great number of decimals.
Requisition is created in i-Procurement page. Quantity_committed column gets the value from the Purchase Requisition and it has a great number of decimals while the standard PO form can accept quantity_committed field with length maximum 30.

This causes error as following:

ERROR:
FRM-40831: Truncation occurred: value too long for field quantity_committed


STEPS TO REPRODUCE:
The issue can be reproduced at will with the following steps:
1. GL Responsibility > Enter rates, allow the system to calculate inverse rate
2. Observe the number of decimals for inverse rates
3. I-procurement page > Create Requisition
4. PO standard form, try to open the PO created from the mentioned Requisition
5. Observe the error

Changes

 

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
Changes
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.