r12.2

[satish]

Hi Erman,

Triggers will be created in patch edition during the patching cycle.if i want to look at these triggers we have to connect to patch edition.But in my case i am able to view them from run edition.can you please let us know the reason behind this.your explanation is always welcome

select * from ad_objects where OBJECT_type='TRIGGER' and object_name like 'FND%'

APPS                           FND_PROFILE_OPTION_VALUES+     TRIGGER
Y VALID   21-SEP-17          21-SEP-17          21-SEP-17

[ErmanArslansOracleBlog]

What is the type of that edition trigger? Forward or Reverse?

[satish]

This is what i can see from dba_source

trigger "APPS"."FND_PROFILE_OPTION_VALUES+" before insert or update or delete on "APPLSYS"."FND_PROFILE_OPTION_VALUES#" for each row  declare   l_current varchar2(30) := sys_context('userenv', 'current_edition_name');   l_default varchar2(30); begin    select property_value into l_default   from   database_properties where  property_name = 'DEFAULT_EDITION';   if l_current > l_default and l_current != 'V_20170921_1532' then     raise_application_error(-20002,'Seed Data Table FND_PROFILE_OPTION_VALUES has not been prepared for patching');   end if;   if INSERTING then      :new.zd_edition_name := 'V_20170921_1532';   end if; end;

[ErmanArslansOracleBlog]

This is not a cross edition trigger.
It should have "CROSSEDITION" clause in its code.
This one hasn't.

This seems to be a guard trigger, created with ad.plsql.ad_zd_seed.create_guard.
This seems to be a trigger for controlling whether the underlying table is ready for patching (prepared for patching)

[satish]

thank you