Common Condition Expressions No Longer Allowed In PDC
(Doc ID 1671845.1)
Last updated on MARCH 18, 2019
Oracle Communications Pricing Design Center - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11.1.0] Information in this document applies to any platform.
On : PDC 18.104.22.168.0 version ;
Problem : Common condition expressions no longer allowed in PDC
* While running PDC migration tool, the analysis report for pricing objects has identified critical problems when using functions like ROUND(), TRUNC(), TOTALQ(), etc. and suggests the use of EVAL() function. * We were unable to find further documentation on the use of EVAL() function and it doesn’t seem to be an easy way to resolve these conflicts, since the base expression (the call to the function) only allows the name of the function and no input parameters, for example: EVAL("getROUND"). For cases where the resource ID is involved (see below) we would need to loop through the edr to match the corresponding resource id which might lead to performance impacts.
Base expressions examples: • round(Bal(1002514)/150,0,ROUND_DOWN)*150 • round(Bal(1002512)/250,0,ROUND_DOWN)*250 • TotalQ-EBal(2)
Note: For the above round examples, two Eval() functions would be required if resource ID cannot be passed as an input parameter.
In this context, below queries are answered in this document.
Questions and Answers
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!