This Document describes the basic steps needed to create a custom application in Oracle E-Business Suite Release 12.2.
Step 1: Create A Custom Application Using adsplice
Step 2: Verify Creation of Custom Product in the Database
Step 3: Create Custom Objects
Step 4: Propagate Changes to Other File System
Step 1: Create A Custom Application Using adsplice
1.Download Patch 3636980 "Support Diagnostics (IZU) patch for AD Splice" from My Oracle Support.
2.Manually copy the three .txt files from the 3636980\izu\admin directory to your own temporary directory.
3.Rename izuprod.txt to <CUSTOM MODULE>prod.txt. In this example, we will be using "xxqbprod.txt".
4.Rename izterr.txt to <CUSTOM MODULE>terr.txt. In this example, we will be using "xxqbterr.txt".
4.a )Open newprods.txt in a text editor.
Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOM MODULE> (i.e. keep the case sensitivity).
Note: In this example, we will be changing references of "izu" to be "xxqb" and "IZU" to be "XXQB".
4.b) Modify any other values as appropriate.
In this example case, the modified version of this file will look like the following:
product=xxqb
base_product_top= *APPL_TOP*
oracle_schema=xxqb
sizing_factor=100
main_tspace= USER_DATA
index_tspace=USER_IDX
temp_tspace=TEMP
default_tspace= USER_DATA
5.Open xxqbprod.txt in a text editor.
5.a) Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOM MODULE> (keeping the case sensitivity).
Note: In this example, we will be changing references of "izu" to be "xxqb" and "IZU" to be "XXQB".
5.b) Change all references to prodid 278 to your own application ID.
You can run the following SQL to find out if your selected custom application ID number is available:
SQL>select decode(count ,0, 'Selected number is available', 'Selected number is already in use') Status, &&enter_custom_applID selected_number
from
(
select count(*) as count from
(
select 'x' from fnd_oracle_userid
where oracle_id= &&enter_custom_applID
union
select 'x' from fnd_application
where application_id= &&enter_custom_applID
)
);
Note: In this example, we will use a production_id of 277.
6. Open xxqbterr.txt in a text editor.
6.a) Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOMMODULE> (keeping the case sensitivity).
Note: In this example, we will be changing references of "izu" to be "xxqb" and "IZU" to be "XXQB".
6.b) Change the text "Oracle_Support_Diagnostic_Tools" to be "xxqb_custom_app".
7.Copy the following text files to the $APPL_TOP/admin directory:
xxqbprod.txt
xxqbterr.txt
newprods.txt
8.Change directory to the admin directory under $APPL_TOP
Run AD Splice
Note: In Oracle E-Business Suite Release 12.2, AD Splice first makes the new user edition-enabled,and then enables Edition-Based Redefinition (EBR) for the custom objects.AD Splice must be run from the admin directory under APPL_TOP, and is invoked by running the command :
$ adsplice
When prompted for the following, you can press Enter to accept the default location :
Enter the directory where your AD Splicer control file is located.The default directory is [/oracle/VIS/apps/apps_st/appl/admin] :
When prompted for the following, you can press Enter to accept the default filename:
Please enter the name of your AD Splicer control file [newprods.txt] :
When prompted for the following, you can press Enter to accept the default value and regenerate the environment file :
Do you wish to regenerate your environment file [Yes] ?
AutoConfig will be run automatically as part of this procedure.
Review the AD Splice log file to ensure the procedure completed successfully.
Review the AutoConfig log file to ensure the procedure completed successfully.
Step 2: Verify Creation of Custom Product in the Database
Log in to SQL*Plus as APPS, and run the following SQL to confirm that the fnd_application table has one row :
SQL>select * from fnd_application where application_short_name = 'XXQB';
This statement should return one row only.
Run the following SQL to check the product installations table has one row for your custom product :
SQL>select * from fnd_product_installations where APPLICATION_ID = 50201;
This statement should return one row only.
Run the following SQL to check the database user :
SQL>select * from dba_users where username = 'XXQB';
This statement should return one row only.
To ensure the new environment file is picked up, log out and back in again as applmgr, then run the following command to confirm the $XXQB_TOP variable is correctly set :
$ env | grep XXQB
Run the following command to check the file system has been created correctly. You should see a directory listing returned as shown :
$ ls $XXQB_TOP
admin log mesg out sql
Note: If you have registered any schemas using the fnd_oracle_user_pkg.lod_row API, their passwords will not be encrypted. As a result,adpatch and adsplice will fail. To correct this, you need to run the FNDCPASS utility to set the password for the schemas.
Step 3: Create Custom Objects
You can now create any custom objects required.
In the $XXQB_TOP directory, create source code files appropriate to the type of object. For example, forms would be located in $XXQB_TOP/forms/US,and package source code in $XXQB_TOP/admin/sql.
You may also want to create custom request group, responsibilities, menus, etc. that your users require to access your custom objects.
Database objects such as tables, indexes, and sequences should be created in the XXQB schema.
Grant all privilege from each custom data object to the APPS schema.
For example, logged in as the XXQB user:
SQL>grant all privileges on myTable to apps;
Create a synonym in APPS for each custom data object.
For example, logged in as the APPS user:
SQL>create synonym myTable for XXQB.myTable;
Step 4: Propagate Changes to Other File System
When you start the next online patching cycle, the prepare phase will run AD Splice sync-up actions to synchronize the two file systems.
If the AD Splice sync-up fails when the prepare phase is run, check the $APPL_TOP/admin/$TWO_TASK/log/adsplicelog log file for the following :
UPDATE FND_ORACLE_USERID SET READ_ONLY_FLAG = 'A' WHERE ORACLE_ID
If you see this, apply Patch 18283295:R12.AD.C.Delta.5 and restart the prepare phase.
Note: Instructions for applying this patch can be found in My Oracle Support Knowledge Document 1617461.1,Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2.
