R12 Upgrade - Strategy to upgrade custom triggers
Hi,We are upgrading from 11.5.10.2 to 12.1.3.
We are having an issue with upgrading the custom triggers on tables which have become views in R12, and replaced with _B and _TL tables.
e.g.
Trigger (Insert/Update/Delete) on MTL_CROSS_REFERENCES in 11i which is a table.
In R12, MTL_CROSS_REFERENCES has become a view/synonym, though generally MTL_CROSS_REFERENCES_VL is used. The base tables are MTL_CROSS_REFERENCES_B and MTL_CROSS_REFERENCES_TL, and the column list of MTL_CROSS_REFERENCES of 11i are shared between the _B and _TL tables in R12.
Is there any established and acknowledged strategy to move the triggers from 11i to R12. I understand It can be done the hard way e.g. creating separate triggers on MTL_CROSS_REFERENCES_B and MTL_CROSS_REFERENCES_TL, or possibly by creating an INSTEAD OF trigger on the view MTL_CROSS_REFERENCES_VL, which I have not explored - but I would like to know if anyone has experienced a similar issue and how it was resolved.
We are having an issue with upgrading the custom triggers on tables which have become views in R12, and replaced with _B and _TL tables.
e.g.
Trigger (Insert/Update/Delete) on MTL_CROSS_REFERENCES in 11i which is a table.
In R12, MTL_CROSS_REFERENCES has become a view/synonym, though generally MTL_CROSS_REFERENCES_VL is used. The base tables are MTL_CROSS_REFERENCES_B and MTL_CROSS_REFERENCES_TL, and the column list of MTL_CROSS_REFERENCES of 11i are shared between the _B and _TL tables in R12.
Is there any established and acknowledged strategy to move the triggers from 11i to R12. I understand It can be done the hard way e.g. creating separate triggers on MTL_CROSS_REFERENCES_B and MTL_CROSS_REFERENCES_TL, or possibly by creating an INSTEAD OF trigger on the view MTL_CROSS_REFERENCES_VL, which I have not explored - but I would like to know if anyone has experienced a similar issue and how it was resolved.
0