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".
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 "xxmz" and "IZU" to be "XXMZ".
Modify any other values as appropriate.
In this example case, the modified version of this file will look like the following:
product=xxmz
base_product_top= *APPL_TOP*
oracle_schema=xxmz
sizing_factor=100
main_tspace= USER_DATA
index_tspace=USER_IDX
temp_tspace=TEMP
default_tspace= USER_DATA
Open xxmzprod.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, we will be changing references of "izu" to be "xxmz" and "IZU" to be "XXMZ".
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:
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 prodid of 50201.
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, we will be changing references of "izu" to be "xxmz" and "IZU" to be "XXMZ".
Change the text "Oracle_Support_Diagnostic_Tools" to be "xxmz_custom_app".
Copy the following text files to the $APPL_TOP/admin directory:
xxmzprod.txt
xxmzterr.txt
newprods.txt
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.
Section 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 = 'XXMZ';
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 = 'XXMZ';
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 $XXMZ_TOP variable is correctly set:
$ env | grep XXMZ
Run the following command to check the file system has been created correctly. You should see a directory listing returned as shown:
$ ls $XXMZ_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.
Section 3: Perform Required Steps on Application Tier Nodes
Follow the relevant steps for the Oracle E-Business Suite application tier nodes in your environment.
For shared APPL_TOP installations, simply run AutoConfig for the remaining nodes (there is no need to rerun AD Splice). Or, if the APPL_TOP is not shared, repeat Steps 8 to 12 in Section 1 on all the other nodes.
Restart the application tier services.
Test operation thoroughly to confirm the effect of your changes.
Reference:Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)
