Oracle Apps Essentials

There are two steps to create Materialized Views in 12.2 Create Logical View Upgrade to Materialized View Create Logical View CREATE OR REPLACE <Custom Schema>.XXBLOG_CREATE_LOGICAL_MV# AS <SELECT Statement>; Upgrade Logical View to Materialized View exec ad_zd_mview. upgrade('<custom schema>', 'XXBLOG_CREATE_LOGICAL_MV'); How to check if the Materialized Views got created properly in 12.2 SELECT object_type, object_name FROM dba_objects WHERE object_name like 'XXBLOG_CREATE_LOGICAL_MV%'; -- 4 rows Selected These 4 Rows get created in the process for Logical View (Ending with '#') in Custom Schema Materialized View in Custom Schema Table in Custom Schema Synonym in APPS Possible Issue: Create mview gives the following error when the mview definition query refers to editioned function: ORA-38818: illegal reference to editioned object %.% Possible Solution: Re-create the referenced pl/sql objects in a sche

AME Debug Scripts Purpose: This AME setup output allows support and development to analyze your approval setup. Requirement: Internal ID (application_id) Purpose of Utility Script This reporting utility script will allow a snapshot to be taken of the AME set-up for a specified transaction type (ie Setup Report for the transaction Type). It will report on the following AME Setup Data for a Transaction Type Invalid Approvers in the setup Invalid AME Objects AME Patch Level AME Key Files Versions The output of this utility script is an HTML document. Steps to generate the Setup Report There are 2 steps involved in generating the setup report. The first step we need to identify the AME’s internal application id for the transaction type in question. The second step is the actually running the script which generates the setup report. Step 1 : Identify the AME Internal ID for the Transaction Type. AME assigns a internal ID (also known as AME app