Create a custom top in Oracle Apps

POSTED BY ABHIJIT RAY MAY 5, 2012 LEAVE A COMMENT FILED UNDER ADCMCTL.SH, BASEPATH, DATAGROUP, FND_APPLICATION, ICM

All Oracle Apps instances have at least 1 custom top for all the custom objects. The custom top corresponds to a custom schema. As per development standards (Oracle EBSO guidelines), custom objects should be registered only in the custom top and the custom schema. This ensures that patch application or upgrade activities on standard objects do not affect the custom objects in any way. The custom top(s) is(are) generally created and maintained by the DBA. I have created a custom top, XXDOM_TOP along with a custom schema XXDOM for illustration. The steps are given below.

Step 1: Create the custom schema Connect to database as SYSTEM Create the schema and grant privileges to it

1 Create user xxdom identified by xxdom; 2 3 Grant connect, resource to xxdom;

Step 2: Register the database schema Responsibility: System Administrator Navigation: Security > ORACLE > Register Create a new record Database user Name: xxdom Password: xxdom (this value has to be entered twice)

Privilege: Enabled Install Group: 0 Description: Custom schema

Step 3: Register Application Navigation: Application > Register Create a new record for this application to which the schema will be attached. Application: DOM application Short Name: XXDOM Basepath: XXDOM_TOP

Step 4: Register Schema in Datagroup Navigation: Security > Oracle > DataGroup Query for DataGroup = Standard Create a record in the detail section Application: DOM Application Oracle ID: APPS

Note: All custom applications will connect to Oracle ID, APPS, as all code, Standard or Custom, is executed from APPS schema. We need to grant all privileges on the custom objects in the custom schema to APPS schema.

Now the new application will be available to Apps. For instance on the Concurrent Executable form you can select the newly created application

Now the application is visible and is ready for usage from the front end but the corresponding file structure is not yet ready. Step 5: Restart Internal Concurrent Manager Restart Internal Manager so that the changes take place across the concurrent managers as well.

Navigation:

You need to click on Terminate to stop the manager and then click on Restart to start the manager. Note: All concurrent processing will be affected. You can also restart the Internal Manager from Unix. Login to Unix and go to the following directory, $COMMON_TOP/admin/scripts/$CONTEXT_NAME Then run the script,

1 $ adcmctl.sh stop apps/<password>

After the script ends,

1 $ adcmctl.sh start apps/<password>

To start the manager

Step 6: Create the file structure Log in to Unix Create a directory structure with a top directory named xxdom. This directory structure should be created under $APPL_TOP directory. The structure will be similar to any standard top directory structure, e.g. GL_TOP, AP_TOP etc.

Modify the environment file Identify the environment file. We need to add an Apps environment variable to point to the xxdom directory. We shall use XXDOM_TOP as the variable. The environment file will be

under $APPL_TOP directory and normally will be named like, <<instance name>>.env

Add the following lines in the .env file,

1 # Adding XXDOM_TOP environment variable</pre> 2 3 4 XXDOM_TOP=/d03/appltest/testappl/xxdom/11.5.0 5 6 export XXDOM_TOP

Step 7: Bounce Apache server. The steps for bouncing Apache is given here Verification steps

Unix: Check for the environment variable in unix

1 $ env | grep XXDOM

Database: On the database run the following query,

1 SELECT basepath, product_code, application_short_name 2 3 4 5 WHERE application_short_name = 'XXDOM' FROM fnd_application

The environment is now set for the new custom top created in Unix.