PURPOSE ASSUMING the CUSTOM TOP NAME as XBOL ------This note describes the basic steps needed to setup

a Custom Application within Oracle Applications 11i. 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 y our environment. 1) Make the directory structure for your custom application files. cd $APPL_TOP mkdir XBOL mkdir XBOL/11.5.0 mkdir XBOL/11.5.0/admin mkdir XBOL/11.5.0/admin/sql mkdir XBOL/11.5.0/admin/odf mkdir XBOL/11.5.0/sql mkdir XBOL/11.5.0/bin mkdir XBOL/11.5.0/reports mkdir XBOL/11.5.0/reports/US mkdir XBOL/11.5.0/forms mkdir XBOL/11.5.0/forms/US mkdir XBOL/11.5.0/$APPLLIB mkdir XBOL/11.5.0/$APPLOUT mkdir XBOL/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 filenam e 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 formsse rvlet.ini in $APACHE_TOP/Jserv/etc 3) Create new tablespace for database objects create tablespace XBOL datafile '/u04/AIRXPdata/xbol/xboldata/XBOL.dbf' size 10M default storage(initial 10k next 10k) 4) Create schema create user XBOL identified by XBOL default tablespace XBOL temporary tablespace temp quota unlimited on XBOL quota unlimited on temp; grant connect, resource to XBOL; grant create session to XBOL; 5) Register your Oracle Schema.

Login to Applications with System Administrator responsibility Navigate to Application-->Register Application = XBOL Custom Short Name = XBOL Basepath = XBOL_TOP Description = XBOL Custom Application 6) Register Oracle User Naviate to Security-->Oracle-->Register Database User Name = XBOL Password = XBOL Privilege = Enabled Install Group = 0 Description = XBOL Custom Application User 7) Add Application to a Data Group Navigate to Security-->Oracle-->DataGroup Data Group = XBOLGroup Description = XBOL Custom Data Group Click on "Copy Applications from" and pick Standard data Group, then add the fol lowing entry. Application = XBOL Custom Oracle ID = APPS Description = XBOL Custom 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-->responsbility-->Request Group = XBOL Request Group Application = XBOL Custom Code = XBOL Description = XBOL Custom Requests We will not define any requests to add to the group at this stage, but you can a dd 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 t wo menus, one for Core Applications and one for Self Service. Navigate to Application-->Menu Menu = XBOL_CUSTOM_MENU User Menu Name = XBOL Custom Application Menu Type = <leave blank> Description = XBOL Custom Application Menu Seq = 100 Prompt = View Requests Submenu = <leave blank> Function = View All Concurrent Requests Description = View Requests Seq Prompt Submenu Function Description = = = = = 110 Run Requests <leave blank> Requests: Submit Submit Requests

Menu = XBOL_CUSTOM_MENU_SSWA User Menu Name = XBOL Custom Application SSWA Menu Type = <leave blank>

Description

= XBOL Custom Application Menu for SSWA

10) Create new responsibility. One for Core Applications and One for Self Ser vice (SSWA) Navigate to Security-->Responsibility-->Define Responsibility Name = XBOL Custom Application = XBOL Custom Responsibility Key = XBOLCUSTOM Description = XBOL Custom Responsibility Available From = Oracle Applications Data Group Name = XBOLGroup Data Group Application = XBOL Custom Menu = XBOL Custom Application Request Group Name = XBOL Request Group Responsibility Name Application Responsibility Key Description Available From Data Group Name Data Group Application Menu Request Group Name = = = = = = = = = XBOL Custom SSWA XBOL Custom XBOLCUSTOMSSWA XBOL Custom Responsibility SSWA Oracle Self Service Web Applications XBOLGroup XBOL Custom XBOL Custom Application SSWA XBOL Request Group

11) Add responsibility to user Navigate to Security-->User-->Define Add XBOL Custom responsibility to users as required. 12) Other considerations You are now ready to create your database Objects, custom Reports, Forms, Packag es, etc Create the source code files in the XBOL_TOP directory appropriate for the type of object. For example forms would be located in $XBOL_TOP/forms/US or package source code in $XBOL_TOP/admin /sql for example. Database Objects, such as tables, indexes and sequences should be created in the XBOL schema, then you need to a) Grant all privilege from each custom data object to the APPS schema. For example : logged in as XBOL user grant all privileges on myTable to apps; b) Create a synonym in APPS for each custom data object For example : logged in as APPS user create synonym myTable for xbol.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 customisation core apps