Creating a Custom Application in Oracle E-Business Suite Release 12.1.3 and 12.2

Custom applications are required if you are creating new forms, reports, and so on.

Requirements and Defaults:

The procedure described in this document should be performed on the run file system when there is no active patching cycle.
Custom data and index tablespaces default to APPS_TS_TX_DATA and APPS_TS_TX_IDX respectively.

First down the Application services, then after starting the Process

Create Custom Application Using AD Splice:

1.Create tablespace with the below command

sqlplus “/as sysdba”
select NAME, FILE# from V$DATAFILE;

TEMP tablespace :
select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;

create tablespace XXEXAM datafile ‘/devdb/oracle/data/xxexam01.dbf’ size 1024M AUTOEXTEND ON NEXT 100M

2. New User creation:

create user xxexam identified by xxexam default tablespace XXEXAM temporary tablespace TEMP1 profile default account unlock;

product=xxexam
main _tablespace : APPS_TS_TX_DATA
Index tablespace : APPS_TS_TX_IDX

temp tablepace : TEMP1
default tablespace: APPS_TS_TX_DATA

GRANT CONNECT TO XXEXAM;

ALTER USER XXEXAM DEFAULT ROLE ALL;

GRANT ALTER ANY OUTLINE TO XXEXAM;

GRANT ALTER SESSION TO XXEXAM;

GRANT ANALYZE ANY TO XXEXAM;
GRANT CREATE ANY OUTLINE TO XXEXAM;
GRANT CREATE MATERIALIZED VIEW TO XXEXAM;

GRANT CREATE SEQUENCE TO XXEXAM;

GRANT CREATE SESSION TO XXEXAM;
GRANT CREATE TABLE TO XXEXAM;
GRANT CREATE TRIGGER TO XXEXAM;
GRANT CREATE TYPE TO XXEXAM;
GRANT DROP ANY OUTLINE TO XXEXAM;
GRANT QUERY REWRITE TO XXEXAM;
ALTER USER XXEXAM QUOTA UNLIMITED ON APPS_TS_TX_DATA;

ALTER USER XXEXAM QUOTA UNLIMITED ON XXEXAM;

COMMIT;

GRANT CREATE SESSION,RESOURCE TO XXEXAM;

  1. Download Patch 3636980 from My Oracle Support. (This Support Diagnostics patch for AD Splice can be used with any 12.x release, not just 12.2.)
  2. Manually copy the three .txt files from the 3636980\izu\admin directory to your own tmp directory.
  3. Copy the below three files from /tmp to $APPL_TOP/admin to run file system
    a) izuprod.txt
    b) izuterr.txt
    c) newsprod.txt
  4. Rename izterr.txt to terr.txt.
    In this example, Rename the above files to your CUSTOM product name like xxexam as per our assumption
    a) xxexamprod.txt
    b) xxexamterr.txt
    c) newsprod.txt

7. Open the newprods.txt file and change as below
Replace izu with xxexam

  1. Edit the below values in xxexamprod.txt file a)
    Replace izu with xxexam and IZU with XXEXAM b)
  1. Edit the below values in xxexamterr.txt file
    a) Replace izu with xxebs and IZU with XXEXAM
    b) Oracle_Support_Diagnostic_Tools : xxexam_custom_app

10.Change the directory to $APPL_TOP/admin and then run adsplice

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 ‘/devapps/applmgr/fs2/EBSapps/appl’.
Is this the correct APPL_TOP [Yes] ?

AD Splicer records your AD Splicer session in a text file
you specify. Enter your AD Splicer log file name or press [Return]
to accept the default file name shown in brackets.

Filename [adsplice.log] :

* Start of AD Splicer session *
AD Splicer version: 12.2.0
AD Splicer started at: Thu Apr 08 2021 18:06:13

APPL_TOP is set to /devapps/applmgr/fs2/EBSapps/appl

Change DB = YES.

Backing up restart files, if any……Done.

Your previous AD Splicer session did not run to completion.
Do you wish to continue with your previous AD Splicer session [Yes] ? No

You chose to disregard your previous AD Splicer session
and to restart AD Splicer from the beginning.

Enter Yes to confirm that you wish to overwrite your previous
AD Splicer session and begin a new AD Splicer session.

Enter No to continue with your previous AD Splicer session. [No] : Yes

Please enter the name of the Oracle E-Business Suite System that this
APPL_TOP belongs to.

The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.

Sample Applications System names are: “prod”, “test”, “demo” and
“Development_2”.

Applications System Name [DEV] : DEV *

NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.

Example 1: If you don’t have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.

Example 2: If you don’t have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.

Example 3: If you don’t have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.

Do you currently have or want to install files used for installing or upgrading
the database in this APPL_TOP [YES] ? YES *

Do you currently have or want to install Java and HTML files for HTML-based
functionality in this APPL_TOP [YES] ? YES *

Do you currently have or want to install Oracle E-Business Suite forms files
in this APPL_TOP [YES] ? YES *

Do you currently have or want to install concurrent program files
in this APPL_TOP [YES] ? YES *

Please enter the name Oracle E-Business Suite will use to identify this APPL_TOP.

The APPL_TOP name you select must be unique within an Oracle E-Business Suite
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.

Sample APPL_TOP Names are: “prod_all”, “demo3_forms2”, and “forms1”.

APPL_TOP Name [AT_devebsapp] : AT_devebsapp *

You are about to install or upgrade Oracle E-Business Suite product tables
in your ORACLE database ‘DEV’
using ORACLE executables in ‘/devapps/applmgr/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] :

AD Splicer is verifying your username/password.

The status of various features in this run of AD Splicer is:

                                       <-Feature version in->

Feature Active? APPLTOP Data model Flags
—————————— ——- ——– ———– ———–
CHECKFILE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N
PATCH_TIMING Yes 2 2 Y N N Y N Y
PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y
JAVA_WORKER Yes 1 1 Y N N Y N Y
CODELEVEL Yes 1 1 Y N N Y N Y

Reading product information from file…

Reading language and territory information from file…

Reading language information from applUS.txt …

Reading database to see what industry is currently installed.

Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:

Code Language Status
—- ————————————— ———
US American English Base

Your base language will be AMERICAN.

Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt …

Saving product information.
*** Edition Enabled User ***

The log file is located at:
/devapps/applmgr/fs2/EBSapps/appl/admin/DEV/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
/devapps/applmgr/fs2/EBSapps/appl/admin/DEV/log/adsplice.log

and in other log files in the same directory.

11.Autoconfig will run automatically as part of this procedure
12.Review the AD Splice log file to ensure the procedure completed successfully.
13.Review the AutoConfig log file to ensure the procedure completed successfully.

Verify Creation of Custom_top

  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 = ‘XXEXAM’;

This statement should return one row only.

  1. 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 = 50301;

This statement should return one row only.

3.Run the following SQL to check the database user:

SQL> select * from dba_users where username =’XXEXAM;

This statement should return one row only.

  1. To ensure the new environment file is picked up, log out and back in again as
    application user applmgr, at OS level and then source the env file then run
    the following command to confirm the $XXEXAM_TOP variable is correctly set:

Start the Application services:

  1. Source the Application file
    2.Startup the applicatio services cd $ADMIN_SCRIPTS_HOME
    ./adstrtal.sh apps/apps

[applmgr@test ~]$ env | grep XXEXAM
XXEXAM_TOP=/devapps/applmgr/fs2/EBSapp/appl/xxexam/12.0.0

Leave a Comment

Your email address will not be published.