We mostly have forward cross edition triggers in EBS online patching mechanism. These triggers are defined to transmit the data from the run edition to the patch edition and to synchronize the data between the editions. We may also see reverse cross edition in EBS.
You may see the reverse cross-edition triggers in some exceptional cases, but you see the forward cross-edition triggers almost in every case where a table structure is changed via online patching.
Those are standard cross edition triggers like the following;
CREATE OR REPLACE STUDENTS_FTRG
BEFORE INSERT OR UPDATE
ON FULL_NAME
FOR EACH ROW
FORWARD CROSSEDITION
DISABLE
BEGIN
:NEW.FIRSTNAME := TRIM(SUBSTR(:NEW.FULLNAME, 1, INSTR(:NEW.FULLNAME, ' ', -1)));
:NEW.SURNAME := TRIM(SUBSTR(:NEW.FULLNAME, INSTR(:NEW.FULLNAME, ' ', -1)));
END STUDENTS_ FTRG;
So every principle that applies for the Cross Edition Triggers in general, also applies for EBS 's Cross Edition Triggers.
A forward cross edition trigger is fired when the data is changed in the older Editions. (run)
The reverse Cross Edition Trigger is fired when data is changed in the new edition. (patch)
In EBS, in the case of the tables that store the seed data, the method is different. The table data is actually copied during a patch application.. Cross Edition triggers then come into play, to synchronize the copy of the data that is used by the patch edition and the data used by the run edition, as there may be updates to the actual seed data during a patching cycle, exactly between the apply and cutover phases.
Read my book for more ->
https://www.amazon.com/Practical-Oracle-Business-Suite-Implementation/dp/1484214234
Locked
