Creating a Custom Application in Oracle E-Business Suite Release 12.2
Reference (Doc ID 1577707.1)
- 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.
Copied to /home/applmgr/patch_custom
Rename izuprod.txt to <CUSTOM MODULE>prod.txt. In this example, we will use "xxmobileprod.txt".
Rename izterr.txt to <CUSTOM MODULE>terr.txt. In this example, we will use "xxmobileterr.txt".
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 "xxmobile"
and "IZU" to be "XXMOBILE".
a.
In this example case, the modified
version of this file will look like the following:
product=xxmobile
base_product_top= *APPL_TOP*
oracle_schema=xxmobile
sizing_factor=100
main_tspace= USER_DATA
index_tspace=USER_IDX
temp_tspace=TEMP
default_tspace= USER_DATA
Grant
connect, resource to xxmobile;
GRANT CONNECT TO XXMOBILE;
GRANT RESOURCE TO XXMOBILE;
ALTER USER XXMOBILE DEFAULT ROLE NONE;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_INTERFACE;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_INTERFACE;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_TX_DATA ;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_NOLOGGING;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_MEDIA;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_TX_DATA;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_SUMMARY;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_TX_IDX;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_SEED;
ALTER USER XXMOBILE QUOTA UNLIMITED ON APPS_TS_ARCHIVE;
7. In Release 12.2, any new custom application objects will be stored in APPS_TS_TX_DATA and APPS_TS_TX_IX, regardless of the settings for "main_tspace=" and "index_tspace=" in the newprods.txt file.
AD Splice will ignore any information for these two settings, and will use only the default OATM tablespaces for your new custom objects. For this reason, any new custom schema should use default_tspace as APPS_TS_TX_DATA.
Only for old custom applications created in
Release 11i should you update these two values to point to your old custom OFA
tablespaces. This should only be done if you did not convert to OATM before
upgrading to Release 12.2.
product=xxmobile
base_product_top= *APPL_TOP*
oracle_schema=xxmoblie
sizing_factor=100
main_tspace= USER_DATA // This will be ignored by adsplice.
index_tspace=USER_IDX // This will be ignored by adsplice.
temp_tspace=TEMP
default_tspace= APPS_TS_TX_DATA // This should be set to APPS_TS_TX_DATA, the
default tablespace for your new custom schema user.
1. 8. Select the reference number for you custom
application
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
));
Cant use 278, lets try another number
888 is available, so we will be
using 888 as our Custom Application ID
9. Open xxmobileprod.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 be changed to "xxmobile", and
references to "IZU" will be changed to "XXMOBILE".
Change all
references of 278 to 888
Update following references in file xxmobileprod.txt
<<Displaying
only the updated entries>>
# Product specific
Product ID's
xxmobile 888
# application id,
abbreviation, shortname, prefix
888 xxmobile XXMOBILE APP
Yes Yes
# install oracle id,
default ORACLE username, default ORACLE password
888 XXMOBILE XXMOBILE
# list of products
and versions
XXMOBILE 12.0.0
10.
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 "xxmobile", and
references to "IZU" will be changed to "XXMOBILE
Change the text "Oracle_Support_Diagnostic_Tools"
to be "xxmz_custom_app"
Updated entry looks like below :-
# product names in this language
c xxmobile xxmobile_custom_app
11.
Copy the following text files to the
$APPL_TOP/admin directory:
- xxmobileprod.txt
- xxmobileterr.txt
- newprods.txt
12. Change directory to the admin
directory under $APPL_TOP & run adsplice
[applmgr@oraerpvision admin]$ pwd
/u01/appstier/oracle/VIS/fs2/EBSapps/appl/admin
[applmgr@oraerpvision admin]$ cp /home/applmgr/patch_custom/*.txt .
[applmgr@oraerpvision admin]$ ls –ltr xxmobile* newprod*
-rwxr-xr-x 1 applmgr dba 2882
Sep 2 12:11 xxmobileterr.txt
-rwxr-xr-x 1 applmgr dba 4996
Sep 2 12:11 xxmobileprod.txt
-rwxr-xr-x 1 applmgr dba 381
Sep 2 12:11 newprods.txt
[applmgr@oraerpvision admin]$ adsplice
[applmgr@oraerpvision
admin]$ adsplice
Copyright (c) 2002, 2012 Oracle Corporation
Redwood Shores,
California, USA
AD Splicer Version 12.2.0
NOTE: You may not use this
utility for custom development
unless you have written permission from
Oracle Corporation.
Your default directory is
'/u01/appstier/oracle/VIS/fs2/EBSapps/appl'.
Is this the correct
APPL_TOP [Yes] ?
Filename
[adsplice.log] : adsplice-2Sep2020.log
You are about to install or
upgrade Oracle E-Business Suite product tables
in your ORACLE database 'VIS'
using ORACLE executables in
'/u01/appstier/oracle/VIS/fs2/EBSapps/10.1.2'.
Is this the correct
database [Yes] ?
AD Splicer needs the password for
your 'SYSTEM' ORACLE schema
in order to determine your
installation configuration.
Enter the password
for your 'SYSTEM' ORACLE schema:
The ORACLE username specified
below for Application Object Library
uniquely identifies your existing
product group: APPLSYS
Enter the ORACLE
password of Application Object Library [APPS] :
…………………….
……………………
…………………….
………………………
Please enter the directory where
your AD Splicer control file is located.
The default
directory is [/u01/appstier/oracle/VIS/fs2/EBSapps/appl/admin] :
Please enter the
name of your AD Splicer control file [newprods.txt] :
AD Splicer is creating or
updating the ORACLE username XXMOBILE
with password ***** for xxmobile
custom app tables.
New product XXMOBILE spliced. Use
FNDCPASS to change the password.
Granting privileges for
tablespaces...
Granting required system
privileges and creating APPS*DDL packages...
sqlplus -s XXMOBILE/*****
@/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql
'/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls
***** XXMOBILE *****'
Done running adaddls.pls for
XXMOBILE
sqlplus -s XXMOBILE/*****
@/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql
'/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaaddls.pls
***** XXMOBILE *****'
Done running adaaddls.pls for
XXMOBILE
sqlplus -s XXMOBILE/*****
@/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql
'/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddlb.pls
***** XXMOBILE *****'
Done running adaddlb.pls for
XXMOBILE
sqlplus -s XXMOBILE/*****
@/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql
'/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaaddlb.pls
***** XXMOBILE *****'
Done running adaaddlb.pls for
XXMOBILE
Registering ORACLE usernames/passwords.
**
**Inserting application
information for new products...
**
**** Running Seed Table Prepare
for FND_APPLICATION ****
**** Running Seed Table Prepare
for FND_APPLICATION_TL ****
INSERT INTO FND_OAM_CONTEXT_CUSTOM
(OA_VAR,CTX_TYPE,OA_TYPE,NAME,DEFAULT_VALUE,TITLE,DESCRIPTION) VALUES
('c_xxmobile','A','PROD_TOP','c_xxmobile','/u01/appstier/oracle/VIS/fs2/EBSapps/appl/xxmobile/12.0.0','custom
prod top xxmobile','this is spliced custom prod top') Temporarily resetting CLASSPATH to:
"/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/java/adjava.zip:/u01/appstier/oracle/VIS/fs2/EBSapps/comn/util/jdk32/lib/dt.jar:/u01/appstier/oracle/VIS/fs2/EBSapps/comn/util/jdk32/lib/tools.jar:/u01/appstier/oracle/VIS/fs2/EBSapps/comn/util/jdk32/jre/lib/rt.jar:/u01/appstier/oracle/VIS/fs2/EBSapps/comn/shared-libs/ebs-3rdparty/WEB-INF/lib/ebs3rdpartyManifest.jar:/u01/appstier/oracle/VIS/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-fmw/WEB-INF/lib/ebsFMWManifest.jar:/u01/appstier/oracle/VIS/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u01/appstier/oracle/VIS/fs2/FMW_Home/oracle_common/modules/oracle.uix_11.1.1/uix2.jar:/u01/appstier/oracle/VIS/fs2/EBSapps/comn/java/classes:/u01/appstier/oracle/VIS/fs2/EBSapps/10.1.2/forms/java:/u01/appstier/oracle/VIS/fs2/EBSapps/10.1.2/forms/java/frmall.jar:/u01/appstier/oracle/VIS/fs2/EBSapps/10.1.2/jlib/ewt3.jar:/u01/appstier/oracle/VIS/fs2/EBSapps/10.1.2/j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/WEB-INF/lib/frmsrv.jar"
Calling
/u01/appstier/oracle/VIS/fs2/EBSapps/comn/util/jdk32/jre/bin/java ...
Running
fnd_application_pkg.add_language ...
**
**Updating product information
for new products...
**
Populating INSTALL_GROUP_NUM
column to FND_ORACLE_USERID table.
**
**Updating product dependency
information...
**
Recording modules in the
database...done.
**
**Updating Data Groups...
**
Reading existing data groups from
database.
Registering any new data groups.
Registering any new data group
units.
Updating Data Group
"Standard" to point to
APPS #1 Account (ORACLE ID = 900)
Updating Patch Advisor tables to
include new product information ..
sqlplus -s APPS/*****
@/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql
'/u01/appstier/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/sql/adpaseed.sql *****'
Done.
Saving module actions...done.
Saving product actions...done.
Making product top directory for
product "xxmobile"...
Directory will be
/u01/appstier/oracle/VIS/fs2/EBSapps/appl/xxmobile/12.0.0
Making directory "log" for product "xxmobile"...
Making directory "out" for product "xxmobile"...
Making directory "mesg" for product "xxmobile"...
Making directory "sql" for product "xxmobile"...
Creating stub file
"sql/XXMOBILENLINS.sql" for product "xxmobile"...
Making directory "admin/sql" for product
"xxmobile"...
Creating stub file
"admin/sql/XXMOBILENLADD.sql" for product "xxmobile"...
Making directory "admin/driver" for product
"xxmobile"...
Recording ADSPLICE action for product:
xxmobile
Do you wish to
regenerate your environment file [Yes] ? yes
Checking if
AutoConfig is enabled....
Running AutoConfig
on : All products ...
The log file is located at:
/u01/appstier/oracle/VIS/fs2/EBSapps/appl/admin/VIS/log/autoconfig_1.log
Please check the log file for
more details about the run of AutoConfig.
If you added new products, use
FNDCPASS to change their default passwords.
AD Splicer is
complete.
Errors and warnings are listed in
the log file
/u01/appstier/oracle/VIS/fs2/EBSapps/appl/admin/VIS/log/adsplice-2Sep2020.log
and in other log files in the
same directory.
CUSTOM TOP IS REGISTERED, RESOURCE THE
ENVIRONMENT VARIABLE TO SEE THE EFFECT
Verify Creation of Custom Product in the Database
1. 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 = 'XXMOBILE';
This statement should return one row
only.
2. 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 = 888;
This statement should return a single
row.
3. Run the following SQL to check the database user:
SQL> select * from dba_users where username = 'XXMOBILE';
This statement should return one row
only.
4. 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 $XXMOBILE_TOP environment variable is correctly set:
$ env | grep XXMOBILE
5. Run the following command to check the file system has been created correctly. You should see a directory listing returned as shown:
$ ls $XXMOBILE_TOP
admin log mesg out sql
No comments:
Post a Comment