Incorrect SUM(MVF) Results in Calculated fields in Siebel

(Doc ID 2213515.1)

Last updated on DECEMBER 15, 2016

Applies to:

Siebel CRM - Version [IP2013] and later
Information in this document applies to any platform.


On : [IP2013] version, Configuration - General

Calculated field value with expression Sum([MVF]) is not correct when child records exceeds value defined in "Maximum Cursor Size" or default cursor size (in case BC level cursor size is null).

Calculated field Sum([MVF]) should return correct value irrespective number of child records.

The issue can be reproduced with the following steps:

1.Create a calculated field based on MVF (using number Type field at child buscomp) in Parent Buscomp and expose it at UI.

2. Add records in child BC exceeding "Maximum Cursor Size"/Application level default cursor size specified number of records.

3. Compile and Observe the Sum of MVF at Parent level.

The issue has the following business impact:
Due to this issue, user is finding incorrect data at header level.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms