Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 8.0 SIA  and later
Information in this document applies to any platform.
Checked for Relevance on 28-Aug-2013
On : 220.127.116.11 SIA  version, Configuration - General
The custom Siebel Financial configuration is using the "Deep Delete" business component (BC) user property. In this case, the custom Claims BC and its related child custom Asset BC were configured to use the Business Component user property "Deep Delete".
This is used so that the child Asset records are deleted when the parent Claim record is deleted.
The Deep Delete user property was not working as expected. The child Asset BC records were not deleted when the parent Claim record was deleted.
The "Deep Delete" user property was being used successfully for other Claims child BCs.
Why did it not work for the child Asset BC?
The expected behavior is that if the "Deep Delete" business component field is configured correctly then it should work to delete the child records when the parent record is deleted.
Requirements for the Deep Delete BC user property
1. The parent bc has the Deep Delete BC user property set to the name of the mvlink's destination business component
2. The parent bc has a mvlink defined for that destination business component.
3. The mvlink has the NoDelete property set to FALSE
4. The parent BC is not Quote or Order where the user of the Deep Delete user property is not supported due to the specialized functionality for those business components.
If these requirements are met, then the child BC records should be deleted when the parent record is deleted.
Siebel Bookshelf has this information on configuring the Deep Delete business component user property.
The issue is reproduced in the custom application every time when deleting a parent Claim record.
The child Asset records are not deleted.
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