Step By Step Guide to Creating a Custom Application in Applications 11i

Modified 05-MAY-2011 Type WHITE PAPER Status PUBLISHED

Applies to: Oracle Application Object Library - Version: 11.5.10.0 to 11.5.10.2 [Release: 11.5.10 to 11.5.10]Information in this document applies to any platform.*************************************************************This article is being delivered in Draft form and may containerrors. Please use the MetaLink "Feedback" button to adviseOracle of any issues related to this article.*************************************************************
AbstractPURPOSE-------This note describes the basic steps needed to setup a Custom Application within Oracle Applications 11i.
Step By Step Guide to Creating a Custom Application in Applications 11i**************************************************************************************************************************************************************IMPORTANT NOTE - This note is retained for reference only. You should now follow note 270519.1 "Customizing an AutoConfig Environment" to make changes to your system configuration**************************************************************************************************************************************************************
Creating a Custom Application in Applications 11i-------------------------------------------------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_TOPmkdir xxmzmkdir xxmz/11.5.0mkdir xxmz/11.5.0/adminmkdir xxmz/11.5.0/admin/sqlmkdir xxmz/11.5.0/admin/odfmkdir xxmz/11.5.0/sqlmkdir xxmz/11.5.0/binmkdir xxmz/11.5.0/reportsmkdir xxmz/11.5.0/reports/USmkdir xxmz/11.5.0/formsmkdir xxmz/11.5.0/forms/USmkdir xxmz/11.5.0/$APPLLIBmkdir xxmz/11.5.0/$APPLOUTmkdir xxmz/11.5.0/$APPLLOG

2) Add the custom module into the environmentApply 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 objectscreate tablespace xxmz datafile '/emea/oracle/visuk09/visuk09data/xxmz.dbf' size 10M default storage(initial 10k next 10k)

4) Create schemacreate user xxmz identified by xxmzdefault tablespace xxmztemporary tablespace tempquota unlimited on xxmzquota unlimited on temp;grant connect, resource to xxmz;

5) Register your Oracle Schema.Login to Applications with System Administrator responsibilityNavigate to Application-->RegisterApplication = xxmz CustomShort Name = xxmzBasepath = xxmz_TOPDescription = xxmz Custom Application
6) Register Oracle UserNaviate to Security-->Oracle-->RegisterDatabase User Name = xxmzPassword = xxmzPrivilege = EnabledInstall Group = 0Description = xxmz Custom Application User
7) Add Application to a Data GroupNavigate to Security-->Oracle-->DataGroupData Group = xxmzGroupDescription = xxmz Custom Data GroupClick on "Copy Applications from" and pick Standard data Group, then add the following entry.Application = xxmz CustomOracle ID = APPSDescription = xxmz Custom Application
8) Create custom request groupThis 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-->RequestGroup = xxmz Request GroupApplication = xxmz CustomCode = xxmzDescription = xxmz Custom RequestsWe will not define any requests to add to the group at this stage, but you can add some now if required.
9) Create custom menuThis 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-->MenuMenu = xxmz_CUSTOM_MENUUser Menu Name = xxmz Custom ApplicationMenu Type =Description = xxmz Custom Application MenuSeq = 100Prompt = View RequestsSubmenu =Function = View All Concurrent RequestsDescription = View RequestsSeq = 110Prompt = Run RequestsSubmenu =Function = Requests: SubmitDescription = Submit RequestsMenu = xxmz_CUSTOM_MENU_SSWAUser Menu Name = xxmz Custom Application SSWAMenu Type =Description = xxmz Custom Application Menu for SSWA
10) Create new responsibility. One for Core Applications and One for Self Service (SSWA)Navigate to Security-->Responsibility-->DefineResponsibility Name = xxmz CustomApplication = xxmz CustomResponsibility Key = xxmzCUSTOMDescription = xxmz Custom ResponsibilityAvailable From = Oracle ApplicationsData Group Name = xxmzGroupData Group Application = xxmz CustomMenu = xxmz Custom ApplicationRequest Group Name = xxmz Request GroupResponsibility Name = xxmz Custom SSWAApplication = xxmz CustomResponsibility Key = xxmzCUSTOMSSWADescription = xxmz Custom Responsibility SSWAAvailable From = Oracle Self Service Web ApplicationsData Group Name = xxmzGroupData Group Application = xxmz CustomMenu = xxmz Custom Application SSWARequest Group Name = xxmz Request Group
11) Add responsibility to userNavigate to Security-->User-->DefineAdd xxmz Custom responsibility to users as required.
12) Other considerationsYou are now ready to create your database Objects, custom Reports, Forms, Packages, etcCreate the source code files in the xxmz_TOP directory appropriate for the type of object. For example forms would be located in $xxmz_TOP/forms/US or package source code in $xxmz_TOP/admin/sql for example.Database Objects, such as tables, indexes and sequences should be created in the xxmz schema, then you need to
a) Grant all privilege from each custom data object to the APPS schema.For example : logged in as xxmz usergrant all privileges on myTable to apps;
b) Create a synonym in APPS for each custom data objectFor example : logged in as APPS usercreate synonym myTable for xxmz.myTable;Other database objects, such as views and packages should be created directly in the APPS schema.RELATED DOCUMENTS-----------------Oracle Applications Release 11i Developers Guide.Oracle Applications Release 11i System Administrators Guide.Additional Search Words-----------------------11i custom customization core apps