Limitations In Package Credit Limits Value Ranges In PDC
(Doc ID 2036164.1)
Last updated on SEPTEMBER 27, 2018
Applies to:Oracle Communications Pricing Design Center - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11.1.0]
Information in this document applies to any platform.
On : 22.214.171.124.0 version, User Interface
Limitations in package credit limits value ranges.
There is a 10-character input limitation in the credit limit, credit floor and fixed thresholds fields of PDC GUI and a 32-bit integer limitation in the transformation. These limitations seem to some extent unwarranted. When loading a credit floor of -2,147,483,647 via the ImportExportPricing tool, the value is loaded correctly into PDC and then into BRM. Yet, this same value cannot be entered via the GUI.
Also, higher values of credit limits and credit floors, i.e. -214,748,364,800, are supported by BRM but not by PDC. Even when loaded via the ImportExportPricing, they are removed in transformation.
Allow configuring values that match the underlying BRM data types:
- DECIMAL for credit limit and credit floor (for example -214,748,364,800, i.e. -200GB)
- INT for fixed thresholds (for example -2,147,483,648, i.e. -2GB)
Note also that when clicking away from the text box, the GUI will automatically format the number entered there by adding commas - i.e. from "2147483648" to "2,147,483,648". This causes cutting off the 3 last digits when the user returns to the text box to make a correction. The remaining text is shortened to "2,147,483," and the commas have to be removed to add the missing digits back.
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