Creating a Custom Application in Apps11i

Custom Applications are required if you are creating new forms, reports, etc. This allows you to segregate your custom written files from the standard seeded functionality that Oracle Applications provide. Customizations can therefore be preserved when applying patches or upgrades to your environment.
1) Make the directory structure for your custom application files.
cd $APPL_TOP
mkdir cust
mkdir cust/11.5.0
mkdir cust/11.5.0/admin
mkdir cust/11.5.0/admin/sql
mkdir cust/11.5.0/admin/odf
mkdir cust/11.5.0/sql
mkdir cust/11.5.0/bin
mkdir cust/11.5.0/reports
mkdir cust/11.5.0/reports/US
mkdir cust/11.5.0/forms
mkdir cust/11.5.0/forms/US
mkdir cust/11.5.0/$APPLLIB
mkdir cust/11.5.0/$APPLOUT
mkdir cust/11.5.0/$APPLLOG
2) Add the custom module into the environment
Apply ADX.E.1 and add the entry to topfile.txt as a standard product top entry (follow the existing model in the file) Customised environment variables can be added to AutoConfig by using the filename specificed by s_custom_file, which is then called from the APPSORA.env file.
If using Forms Listener Servlet, you may also need to add $CUSTOM_TOP to formsservlet.ini in $APACHE_TOP/Jserv/etc
3) Create new tablespace for database objects

[oracle@r0469 ~]$ cd /oracle/VIS/db/tech_st/11.1.0/
[oracle@r0469 11.1.0]$ . VIS_r0469.env
[oracle@r0469 11.1.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Fri Aug 31 16:23:12 2012

Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> create tablespace cust datafile '/oracle/VIS/db/apps_st/data/cust.dbf' size 20M;

Tablespace created.


4) Create schema
create user cust identified by cust
default tablespace cust
temporary tablespace temp
quota unlimited on cust
quota unlimited on temp;
grant connect, resource to cust;


SQL> create user cust identified by cust default tablespace cust;
SQL> grant connect, resource to cust;


5) Register your Oracle Schema.
Login to Applications with System Administrator responsibility
Navigate to Application-->Register
Application = cust Custom
Short Name = cust
Basepath = cust_TOP
Description = cust Custom Application
6) Register Oracle User
Naviate to Security-->Oracle-->Register
Database User Name = cust
Password = cust
Privilege = Enabled
Install Group = 0
Description = cust Custom Application User
7) Add Application to a Data Group
Navigate to Security-->Oracle-->DataGroup
Data Group = custGroup
Description =custCustom Data Group
Click on "Copy Applications from" and pick Standard data Group, then add the following entry.
Application = custCustom
Oracle ID = APPS
Description = custCustom Application

8) 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 = custRequest Group
Application = custCustom
Code =cust
Description = cust Custom Requests
We will not define any requests to add to the group at this stage, but you can add some now if required.

9) 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 = cust_CUSTOM_MENU
User Menu Name =cust Custom Application
Menu Type =
Description =custCustom 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
Menu =cust_CUSTOM_MENU_SSWA
User Menu Name = custCustom Application SSWA
Menu Type =
Description =cust Custom Application Menu for SSWA
10) Create new responsibility. One for Core Applications and One for Self Service (SSWA)
Navigate to Security-->Responsibility-->Define
Responsibility Name = cust Custom
Application = cust Custom
Responsibility Key = custCUSTOM
Description = custCustom Responsibility
Available From = Oracle Applications
Data Group Name = custGroup
Data Group Application = cust Custom
Menu = cust Custom Application
Request Group Name = cust Request Group
Responsibility Name = cust Custom SSWA
Application = cust Custom
Responsibility Key = custCUSTOMSSWA
Description = cust Custom Responsibility SSWA
Available From = Oracle Self Service Web Applications
Data Group Name = custGroup
Data Group Application = cust Custom
Menu = cust Custom Application SSWA
Request Group Name = cust Request Group
11) Add responsibility to user
Navigate to Security-->User-->Define
AddcustCustom responsibility to users as required.
12) Other considerations
You are now ready to create your database Objects, custom Reports, Forms, Packages, etc
Create the source code files in the cust_TOP directory appropriate for the type of object. For example forms would be located in
$cust_TOP/forms/US or package source code in $cust_TOP/admin/sql for example.

Database Objects, such as tables, indexes and sequences should be created in the cust schema, then you need to
a) Grant all privilege from each custom data object to the APPS schema.
For example : logged in as cust user
grant all privileges on my Table to apps;
b) Create a synonym in APPS for each custom data object
For example : logged in as APPS user
create synonym myTable for cust.myTable;
Other database objects, such as views and packages should be created directly in the APPS schema.

******************************END****************************************

No comments:

ORA-01552: cannot use system rollback segment for non-system tablespace 'TEMP'

 ORA-01552: cannot use system rollback segment for non-system tablespace "string" Cause: Used the system rollback segment for non...