Skip to main content

Create Custom Top/Application in Oracle R12

Agenda:

Create custom top/application in E-Business Suite R12.

Steps to be followed:

SCHEMA NAME : XXNEW
TOP NAME : XXNEW_TOP
Application : XXNEW Custom Application
Data Group : Standard
Request Group : XXNEW Request Group
Menu : XXNEW_CUSTOM_MENU
Responsibility : XXNEW Custom



Step-1
Create a Tablespace XXNEW in the Database for custom schema.
create tablespace XXNEW datafile '/u01/oradata/XXNEW01.dbf'
size 50M;
Step-2
Create Schema XXNEW in the database.
create user XXNEW identified by XXNEW default tablespace XXNEW temporary tablespace temp quota unlimited on XXNEW;
Step-3
Grants Connect and Resource to schema XXNEW.
grant connect, resource to XXNEW;

Step-4

Make the directory structure for your custom application files.

cd $APPL_TOP
mkdir XXNEW
mkdir -p XXNEW/12.0.0
mkdir -p XXNEW/12.0.0/admin
mkdir -p XXNEW/12.0.0/admin/sql
mkdir -p XXNEW/12.0.0/admin/odf
mkdir -p XXNEW/12.0.0/sql
mkdir -p XXNEW/12.0.0/bin
mkdir -p XXNEW/12.0.0/reports
mkdir -p XXNEW/12.0.0/reports/US
mkdir -p XXNEW/12.0.0/forms
mkdir -p XXNEW/12.0.0/forms/US
mkdir -p XXNEW/12.0.0/lib
mkdir -p XXNEW/12.0.0/out
mkdir -p XXNEW/12.0.0/log
Step-5
Create custom environment file in APPL_TOP location.

Step-6
Edit custom environment file and insert new custom top information in it.

export XXNEW_TOP=/u01/appluat/UAT/apps/apps_st/appl/XXNEW/12.0.0

Step-7

Edit the default environment file (default.env) located at cd $ORACLE_CONFIG_HOME/forms/server

Open default.env and add the new custom top information at the last line.

XXNEW_TOP=/u01/appluat/UAT/apps/apps_st/appl/XXNEW/12.0.0

Step-8

Register your Oracle Schema.
Login to Applications with System Administrator responsibility
Navigate to Application–>Register
Application = XXNEW Custom Application
Short Name = XXNEW
Basepath = XXNEW_TOP
Description = XXNEW Custom Application






















Step-9

Register Oracle User
Naviate to Security–>Oracle–>Register
Database User Name = XXNEW
Password = XXNEW
Privilege = Enabled
Install Group = 0
Description = XXNEW Custom Application User





















Step-10

Add Application to a Data Group
Navigate to Security–>Oracle–>DataGroup

Application -> XXNEW Application
In Oracle ID -> APPS





















Step-11

Create custom request group
This will act as a placeholder for any custom reports we wish to make available for the Custom Responsibility (which is defined at a later stage)


Navigate to Security–>responsibility–>Request
Group = XXNEW Request Group
Application = XXNEW Custom
Code = XXNEW
Description = XXNEW Custom Requests


We will not define any requests to add to the group at this stage, but you can add some now if required.



















Step-12


Create custom menu
This will act as a placeholder for any menu items we wish to make available for the
Custom Responsibility (which is defined at a later stage). We will create two menus, one for Core Applications and one for Self Service.


Navigate to Application–>Menu
Menu = XXNEW_CUSTOM_MENU
User Menu Name = XXNEW Custom Application
Menu Type =
Description = XXNEW Custom Application Menu
Seq = 100
Prompt = View Requests
Submenu =
Function = View All Concurrent Requests
Description = View Requests
Seq = 110
Prompt = Run Requests
Submenu =
Function = Requests: Submit
Description = Submit Requests

















Step-13

As we have edited default.env we need to bounce the opmn.
cd $ADMIN_SCRIPTS_HOME
sh adopmnctl.sh stopall
Rest the Application ENvironment and start OPMN
sh adopmnctl.sh startall

Comments

Popular posts from this blog

Node id does not exist for the current application server id

Issue: After completing cloning procedure, you generally may across the following issue. "Node id does not exist for the current application server id". Solution: First stop the application. Run adgendbc.sh script to configure apps tier dbc file with the correct id from the database instance. Start the application and test your issue. Location of script: 11i: $COMMON_TOP/admin/install/$CONTEXT_NAME R12: $INST_TOP/admin/install [appldev@erptest install]$ sh adgendbc.sh (Note: It will prompt you to give apps username and apps password.)

How to change EBS R12 database and application port number

On Database Tier 1. Logon as oracle database user and source environment for R12 RDBMS ORACLE_HOME 2. Start database instance for which you want to change R12 port 3. Backup contextfile 4. Change as below in contextfile         dbport  : Change database port from 1521 to 1541         db_ons_localport : 6300 to 6320         db_ons_remoteport : 6400 to 6420         cmanport : 1521 to 1541 5. Run adautocfg.sh On Apps Tier Change Application port from 8000 to 8020 1. Logon as application manager user and source environment for R12 2. Backup contextfile 3. Run adpreclone    $ perl ./adpreclone.pl appsTier 4. Run adcfgclone and choose new port pool    $ cd $COMMON_TOP/clone/bin    $ perl ./adcfgclone.pl appsTier 5. Check new application URL SQL> select home_url from icx_parameters; HOME_URL ----------...

Oracle R12 : You are trying to access a page that is no longer active

Login fails “You are trying to access a page that is no longer active.” The issue can be reproduced at will with the following steps: Issue : After cloning process the login page of Oracle E-Business Suite R12 show the above error. Solution :  For this you need to update the new hostname in the  icx_parameteres table 1.   SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- erp.local.com (This is hostname of Source Application Tier) 2. SQL>update icx_parameters set SESSION_COOKIE_DOMAIN = ‘target.local.com’; 1 row updated. SQL> commit; Commit complete. (This has changed the SESSION_COOKIE_DOMAIN of target application to target hostname.domain_name) 3. SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- target.local.com