Step 1: Create A Custom Application Using AD Splice
- Download Patch 3636980 "Support Diagnostics (IZU) patch for AD Splice" from My Oracle Support.
- Manually copy the three .txt files from the 3636980\izu\admin directory to your own temporary directory.
- Rename izuprod.txt to <CUSTOM MODULE>prod.txt. In this example, we will be using "xxmzprod.txt".
- Rename izterr.txt to <CUSTOM MODULE>terr.txt. In this example, we will be using "xxmzterr.txt".
Ex:
Rename izuterr.txt to xxerpterr.txt
and izuprod.txt to xxerpprod.txt
5. Change the details in the newprods.txt so that all references of "izu" to and all references of "IZU" to (i.e. keep the case sensitivity).
Ex:
In this example case, the modified version of this file will look like the following:
product=xxerp
base_product_top= *APPL_TOP*
oracle_schema=xxerp
sizing_factor=100
main_tspace= USER_DATA
index_tspace=USER_IDX
temp_tspace=TEMP
default_tspace= USER_DATA
base_product_top= *APPL_TOP*
oracle_schema=xxerp
sizing_factor=100
main_tspace= USER_DATA
index_tspace=USER_IDX
temp_tspace=TEMP
default_tspace= USER_DATA
6. We then create a tablespace. In our example our tablespace name will be TSXXST
Note: Custom data and index tablespaces are defaulted to APPS_TX_TX_DATA and APPS_TS_TX_IDX.
7.After we create the tablespace, we continue with the user creation. We add the required privileges so that this use can work
Ex:
CREATE USER XXERP
IDENTIFIED BY xxerp
DEFAULT TABLESPACE XXERP
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 1 Role for XXERP
GRANT CONNECT TO XXERP;
ALTER USER XXERP DEFAULT ROLE ALL;
-- 13 System Privileges for XXERP
GRANT ALTER ANY OUTLINE TO XXERP;
GRANT ALTER SESSION TO XXERP;
GRANT ANALYZE ANY TO XXERP;
GRANT CREATE ANY OUTLINE TO XXERP;
GRANT CREATE CLUSTER TO XXERP;
GRANT CREATE MATERIALIZED VIEW TO XXERP;
GRANT CREATE SEQUENCE TO XXERP;
GRANT CREATE SESSION TO XXERP;
GRANT CREATE TABLE TO XXERP;
GRANT CREATE TRIGGER TO XXERP;
GRANT CREATE TYPE TO XXERP;
GRANT DROP ANY OUTLINE TO XXERP;
GRANT QUERY REWRITE TO XXERP;
ALTER USER XXERP QUOTA UNLIMITED ON XXERP;
Change all references to prodid 278 to your own application ID.
If you are upgrading, and the custom application already exists in the database, you should specify the same application ID. If you are performing a new installation, choose a number above 50,000 that is not already in use.
You can run the following SQL to find out if your selected custom application ID number is available:
If you are upgrading, and the custom application already exists in the database, you should specify the same application ID. If you are performing a new installation, choose a number above 50,000 that is not already in use.
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
)
);
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: This example will use a prodid of 50001.
8.Open xxmzterr.txt in a text editor.
- Change all references of "izu" to <custom module> and all references of "IZU" to <CUSTOM MODULE> (keeping the case sensitivity).
- Note: In this example, references to "izu" will to changed to "xxerp", and references to "IZU" will be changed to "XXERP".
- Copy the following text files to the $APPL_TOP/admin directory:
- xxmzprod.txt
- xxmzterr.txt
- newprods.txt
9.Change directory to the admin directory under $APPL_TOP
10.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] :
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.
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 = 'XXERP';
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 = 50001;
This statement should return one row only.
Run the following SQL to check the database user:
SQL>select * from dba_users where username = 'XXERP';
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 $XXERP_TOP variable is correctly set:
$ env | grep XXERP
Run the following command to check the file system has been created correctly. You should see a directory listing returned as shown:
$ ls $XXERP_TOP
admin log mesg out sql
admin log mesg out sql