My Oracle Support Banner

Common Condition Expressions No Longer Allowed In PDC (Doc ID 1671845.1)

Last updated on MARCH 18, 2019

Applies to:

Oracle Communications Pricing Design Center - Version to [Release 11.1.0]
Information in this document applies to any platform.


 On : PDC version ;

Problem :
  Common condition expressions no longer allowed in PDC

Details :
* 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!

In this Document
Questions and Answers
 1. Why these basic functions are no longer supported?
 2. Prior to BRM 7.5 the recommendation was not to use EVAL() unless there was no other way, this due to performance issues of the function. Has this function been improved in BRM 7.5?
 3. Is there a way to pass input parameters to EVAL() function ?

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