We have created XX_Data_V on Query which uses XX_PACKAGE1 to calculate amount.. XX_PACKAGE1 internally refers to XX_PACKAGE_INT … Below are steps we face issues,
XX_Data_V Editioning View created in apps schema and Grant/Synonym to Custom Schema
XX_PACKAGE1 created in APPS schema with Synonym in Custom Schema
Custom Schema:
Step1: INVALIDATE XX_PACKAGE_INT package..
Step2: Query XX_Data_V which results in wrong value say 100 because we handled exception in XX_PACKAGE1 and returned 100
Step3: Now make XX_PACKAGE_INT package VALID.
Step4: Query XX_Data_V which results in same 100 Value
APPS Schema:
Above behavior do not exist in APPS schema..