AfterDelete Trigger Not Working For M:M Relationship
(Doc ID 2234564.1)
Last updated on FEBRUARY 16, 2017
Applies to:Oracle Fusion Sales Cloud Service - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Technology Management - Application Customization
Cascade Delete not working for M:M relationship
Use Case :
Custom Objects: Promotion object, with two child objects:
- Tactics object - a 1:M relationship
- Promoted Products object - an intersection object of an M:M relationship between Promotion and Products (standard object)
AfterDelete trigger defined on both these objects - Tactics and Promoted Products
When deleting a Promotion record, the trigger works as expected, along with one record for every Tactic record existing under the Promotion. However the trigger for the "Promoted Products" is not called as expected.
Deleting the "Promoted Products" record directly (i.e. removing the association between a Promotion and a Product) is also not working, and the After Delete trigger is not called.
Why the trigger on the M:M intersection object is not working?
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