Last updated on MARCH 02, 2017
Applies to:Siebel Tools - Version 188.8.131.52 and later
Information in this document applies to any platform.
""Checked for Relevance on 21-10-2015""
If you use a calculated field (may be for database fields similar) in a parent field read only user property the field is very often evaluated. Because of complex calculation expression (include BCHasRows etc) the performance is not optimal. To reproduce the behavior in vanilla:
1. Create a business service which logs the calling itself.
2. Then create a calculated field “Test” which calls the service using InvokeServiceMethod("SC Log", "Log", "Test=Test", ""). I use BC “HLS Case” for testing.
Now add a user property “Parent Read Only Field: HLS Case” “Test” on a child BC. I use “PUB Case Benefit Plan” here.
3. Compile and start the application.
4. Now you can see even there is only one evaluation is needed per record but you will find over 10 time.
Can we get a fix where the siebel code is may optimized here. If we change Parent Read Only Field to BC Read Only the behavior correct?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms