Oracle E-Business Suite (EBS)/ Apps

MY E-BUSINESS SUITE BOOK :

(covering EBS 11i, R12 and 12.2, but focusing mainly on EBS 12.2) 
--------------------------------------------------------------------------------------------------------

Some might say: "the blog turned into a book", but it was not actually the case for me.
Our story has begun in the spring of 2015. Syeed Zaheer(my coauthor and friend) and I have written and reviewed approximately 800 pages since that time.

After all the efforts, hard work,  dedication and patience,  I 'm pleased the announce that my book, "Practical Oracle E-Business Suite" has released and it is now available on amazon.com.

Amazon Link: www.amazon.com/Practical-Oracle-Business-Suite-Implementation/dp/1484214234

Official website of Practical Oracle E-Business Suite : http://www.apress.com/9781484214237

This book is a complete Implementation and Management Guide for Oracle E-Business Suite.
Although we have focused on the latest EBS 12.2 release in this book, key areas in R12.1 are also covered wherever necessary.

This book is the one and only book written for EBS 12.2.

--------------------------------------------------------------------------------------------------------

EBS  3 TIER ARCHITECTURE:

---------------------------------------------------------------------------------------------------------------------

EBS 12.2 , R12 AND 11i FILESYSTEMS

11i:

R12: (12.1 & 12.0):

12.2 dual fs:  (latest release  -- as of 26.04.2018)

--------------------------------------------------------------------------------------------------------

ERROR:  

Internal server error oracle.apps.fnd.framework.OAException:FND_NO_DATABASE_CONNECTION.

noDatabaseConnection(OANullDBTransactionImpl.java:653)

--This error is prouced on EBS Version 12.1.3 (note that it can be encountered in lower versions too).

Not that , This error is hard to be found on the logfiles sometimes.. For example if there are multiple oacore services in the environment, then only the web sessions, which are assigned to this problematic oacore process will face this error.. So this can make us think that it s a client problem rather than a system problem... 

SOLUTION: 

Reference Oracle Support Doc id: 1298103.1

For 12.1.3 patch : 1406950 will fix the issue.


------------------------------------------------------------------------------------------------------------

ORACLE APPLICATIONS CONCURRENT REQUEST PHASE AND STATUS CODES

 Table Name: FND_CONCURRENT_REQUESTS
Column Name: PHASE_CODE

 Value  Meaning 
 C  Completed 
 I  Inactive 
 P  Pending 
 R  Running 

Table Name: FND_CONCURRENT_REQUESTS
Column Name: STATUS_CODE
 Value  Meaning 
 D  Cancelled 
 U  Disabled 
 E  Error 
 M  No Manager 
 R  Normal 
 I  Normal 
 C  Normal 
 H  On Hold 
 W  Paused 
 B  Resuming 
 P  Scheduled 
 Q  Standby 
 S  Suspended 
 X  Terminated 
 T  Terminating 
 A  Waiting 
 Z  Waiting 
 G  Warning

------------------------------------------------------------------------------------------------------------


AUTOPATCH ARGUMENTS


apply Purpose: Tells AutoPatch whether to run in test mode.Default: y
driver Purpose: Tells AutoPatch the name of the patch driver file. This is usually used during non-interactive processing.
patchtop Purpose: Tells AutoPatch the top-level directory for the current patch. This is normally used during non-interactive processing. Values: A fully qualified directory name.
preinstall Purpose: Tells AutoPatch whether to run in pre-install mode. Pre-install mode is used to update AD utilities before an upgrade and to apply pre-upgrade patches.
uploadph Purpose: Tells AutoPatch to upload patch history information from the patch information files

AutoPatch Options

The options= argument is used to pass generic options to AutoPatch. It takes the form of a comma-separated list. Enter one option or a comma-separated list of options. For example, options=nocopyportion,nogenerateportion. As with AutoPatch arguments, there must be no space after the comma.

autoconfig Purpose: Tells AutoPatch to run AutoConfig automatically.Default: autoconfig
Use options=noautoconfig if you are applying a number of patches in sequence and want to run AutoConfig once, after applying the last patch of the sequence. The more common method is to merge the patches first with AD Merge Patch.
checkfile Purpose: Tells AutoPatch to either skip running EXEC, SQL, and EXECTIER commands if they are recorded as already run, or to record them as having run after running them. checkfile provides significant performance benefits.
compiledb Purpose: Tells AutoPatch to automatically compile invalid objects in the database after running actions normally found in the database portion of the driver. Use nocompiledb for standard patch translations, documentation patches, and documentation patch translations. Use options=nocompiledb to save time when multiple non-merged patches are applied in a maintenance window.
compilejsp Purpose: Tells AutoPatch whether to automatically compile out-of-date JSP files. JSP files are only compiled if the patch contains copy actions for at least one JSP file.compilejsp for standard patches. nocompilejsp for standard patch translations, documentation patches, and documentation patch translations.
Use options=nocompilejsp to save time when multiple non-merged patches are applied in a maintenance window.
copyportion Purpose: Tells AutoPatch whether to run commands normally found in the copy portion of the driver.
databaseportion Purpose: Tells AutoPatch whether to run commands normally found in the database portion of the driver.
generateportion Purpose: Tells AutoPatch whether to run commands normally found in the generate portion of the driver. Use options=nogenerateportion to tell AutoPatch not to perform generate actions of the driver.
hotpatch Purpose: Tells AutoPatch to apply a patch regardless of whether the Oracle E-Business Suite system is in Maintenance mode.Default: nohotpatch
integrity Purpose: Tells AutoPatch whether to verify that the version of each file referenced in a copy action matches the version present in the patch.Default: nointegrity, nointegrity is safe and avoids some AutoPatch overhead.
maintenancemode Purpose: Tells AutoPatch to enable Maintenance mode at the beginning of a patch session and disable it at the end (if patch application was successful). Default: nomaintenancemode
parallel Purpose: Tells AutoPatch whether to run actions that update the database in parallel (such as SQL) and actions that generate files in parallel (such as genform).
Default: parallel Comments: Oracle does not recommend changing the default, as Oracle E-Business Suite patches are tested on systems using parallel processing.
phtofile Purpose: Tells AutoPatch where to place patch history information after applying the patch.
Default: nophtofile. Use options=phtofile to tell AutoPatch to write patch history information to the patch information files in the file system ($APPL_TOP/admin/$TWO_TASK) instead of uploading it to the database. Comments: Using phtofile allows you to defer the uploading of patch history information to the database until after the system downtime. Use the adpatch uploadph=y command to upload patch history information from the patch information files (in $APPL_TOP/admin/$TWO_TASK) to the database during uptime.
validate Purpose: Tells AutoPatch whether to connect to all registered Oracle E-Business Suite schemas at the start of the patch. Use options=validate to validate password information for all Oracle E-Business Suite schemas. Comments: Useful for finding problems with incorrectly registered Oracle E-Business Suite schemas or schemas with invalid passwords.

------------------------------------------------------------------------------------------------------------

ORACLE XML PUBLISHER

XML publisher/BI Publisher is a template based reporting tool. Multiple templates can be deployed for the same report and generate different layouts for the same report.
XML publisher is integrated to EBS. In EBS templates are deployed through Templates Manager.
EBS reports can be generated in different formats like PDF,RTF,HTML by using XML Publisher . XML publisher takes xml and layout templates as inputs and produces outputs based on these inputs.

Following diagram clearly describes these process;

------------------------------------------------------------------------------------------------------------

EBS R12 LOG FILES LOCATIONS ( They are located in $LOG_HOME which is $INST_TOP/logs)

Concurrent Reqeust related logs:

$LOG_HOME/appl/conc -> Concurrent requests log and out files
$LOG_HOME/appl/admin -> lApps tier startup scripts log files

Apache Logs (10.1.3 Home = iAS Oracle Home) :

$LOG_HOME/ora/10.1.3/Apache -> Location for Apache Error and Access log files
$LOG_HOME/ora/10.1.3/j2ee -> location for j2ee related log files
$LOG_HOME/ora/10.1.3/opmn -> location for opmn related log files

Forms & Reports related logs (10.1.2 = 806 Oracle Home(in R11))

$LOG_HOME/ora/10.1.2/forms
$LOG_HOME/ora/10.1.2/reports

------------------------------------------------------------------------------------------------------------

ORACLE EBS 11i ADD CUSTOM TOP SCRIPT

Usage Example:

 sh add_custom_top.sh xxefa TEST oracle1 XXEFA XXEFA XXEFA_TBS TEMPPROD /u2/oradata/u2/xxefa_01.dbf 1000M

###ADD CUSTOM TOP SCRIPT BY ERMAN ARSLAN ### Created 6/18/2013

### This script should be executed by the application owner

### Before, executing this script, apps environment should be sourced. APPS{SID}_{hostname}.env

### 1. parameter ->  name of the custom top  (lowercase) example: xxefa

### 2. parameter- >  Ebs database SID 

### 3. parameter ->  System user password

### 4. parameter ->  Db user name that is going to be created for the new application 

### 5. parameter ->  Password of the db user  that is going to be created for the new application 

### 6. parameter ->  Tablespace name that will be created for the new  user.

### 7. parameter ->  Existing Temp tablespace that will be used by the new user

### 8. parameter ->  Datafile full path with datafile name . This datafile will be created while creating the new tablespace

### 9. parameter -> datafile size 1000M

### Checking Command line argument count ###

if test $# -lt 9;

then

echo Lacking argument.. Please provide 9 arguments

echo " Usage :

#######################################################################################################

Script calistirilmadan once application environment source edilmis olmalidir. APPS{SID}_{hostname}.env

ADD CUSTOM TOP SCRIPT BY ERMAN ARSLAN ### Created 6/18/2013

This script should be executed by the application owner

Before, executing this script, apps environment should be sourced. APPS{SID}_{hostname}.env

1. parameter ->  name of the custom top  (lowercase) example: xxefa

2. parameter- >  Ebs database SID 

3. parameter ->  System user password

4. parameter ->  Db user name that is going to be created for the new application 

5. parameter ->  Password of the db user  that is going to be created for the new application 

6. parameter ->  Tablespace name that will be created for the new  user.

7. parameter ->  Existing Temp tablespace that will be used by the new user

8. parameter ->  Datafile full path with datafile name . This datafile will be created while creating the new tablespace

9. parameter -> datafile size 1000M

########################################################################################################

"

exit

fi

echo Script is executed by user =  `whoami`

echo "Continue?  (Y or N)  Y for continue , N for abort"

read Cevap1

if [ $Cevap1 == "N" ]

then

echo Program closed.

exit

fi

echo " Is apps environment set? ( Y or N)   Y for continue , N for abort"

read Cevap2

if [ $Cevap2 == "N" ]

then

echo Program closed

exit

fi

### Creating Directory structure. ####

mkdir $APPL_TOP/$1

mkdir $APPL_TOP/$1/11.5.0

mkdir $APPL_TOP/$1/11.5.0/admin

mkdir $APPL_TOP/$1/11.5.0/admin/sql

mkdir $APPL_TOP/$1/11.5.0/admin/odf

mkdir $APPL_TOP/$1/11.5.0/sql

mkdir $APPL_TOP/$1/11.5.0/bin

mkdir $APPL_TOP/$1/11.5.0/reports

mkdir $APPL_TOP/$1/11.5.0/reports/US

mkdir $APPL_TOP/$1/11.5.0/forms

mkdir $APPL_TOP/$1/11.5.0/forms/US 

mkdir $APPL_TOP/$1/11.5.0/$APPLLIB

mkdir -p $APPL_TOP/$1/11.5.0/$APPLOUT

mkdir -p $APPL_TOP/$1/11.5.0/$APPLLOG

### Adding custom product top to topfile.txt..

cd $APPL_TOP

cd admin

echo $1  $APPL_TOP >> topfile.txt

### Adding new Custom top to the default custom environment file

function toUpper { echo $1 | tr [a-z] [A-Z]; } ## uppercase e cevirme fonksiyonunu tanimladik

echo export `toUpper $1`_TOP=$APPL_TOP/$1/11.5.0 >> $APPL_TOP/custom`echo $2`_`hostname -a`.env

###  Connecting to db and creating tablespace and user 

sqlplus system/$3 << EOF

create tablespace $6 datafile '$8' size $9 default storage(initial 10k next 10k);

create user $4 identified by "$5" default tablespace $6 temporary tablespace $7 quota unlimited on $6 ;

grant connect, resource to $4;

exit;

EOF

### Environment is sourced again

. $APPL_TOP/APPS`echo $2`_`hostname -a`.env

echo"

### Script completed . Check above for the error.. If there are errors produced, run the script after correcting them. Error handling is not done in this script, because this script will not be used by the end users.

"

################

###################################

------------------------------------------------------------------------------------------------------------

Oracle E-Business Suite R12 changing IP addres

1)perl $AD_TOP/bin/adgentns.pl appspass=apps contextfile=$APPL_TOP/admin/<SID>_hostname.xml -removeserver
2)connect with sqlplus apps/apps and run the following
begin
FND_NET_SERVICES.remove_server('<SID>', '<hostname>');
end;
/
commit;
/
3) Run autoconfig on application tier
4) Check fnd_nodes to see ip 's are reflected...
select node_id, platform_code, support_db D, support_cp C, support_admin A, support_forms F,
support_web W, node_name, server_id, server_address, domain, webhost, virtual_ip
from fnd_nodes
order by node_id;


Look for the hardcoded old IP Address in the following files on the DB tier
a) listener.ora
b) tnsnames.ora (Local Naming) or check if any other naming method is used to resolve address.
Check if any of the parameter using the old IP Address

------------------------------------------------------------------------------------------------------------

Oracle E-Business Suite Starting/Stopping Notification Mailer with PLSQL

*LOGIN as APPS user


TO STOP NOTIFICATION MAILER
---------------------------------------------------------------------
declare
n_component_id number;
l_errcode number;
l_errstr varchar2(4000);
begin
select component_id into n_component_id from fnd_svc_components
where component_name='Workflow Notification Mailer';
FND_SVC_COMPONENT.stop_Component(n_Component_Id, l_errcode, l_errstr);
commit;
end;
/

TO START NOTIFICATION MAILER
-------------------------------------------------------------------------
declare
n_component_id number;
l_errcode number;
l_errstr varchar2(4000);
begin
select component_id into n_component_id from fnd_svc_components
where component_name='Workflow Notification Mailer';
FND_SVC_COMPONENT.start_Component(n_Component_Id, l_errcode, l_errstr);
commit;
end;
/

TO CHECK THE CURRENT STATUS OF NOTIFICATION MAILER
-------------------------------------------------------------------------
select component_status from fnd_svc_components
where component_name='Workflow Notification Mailer';

------------------------------------------------------------------------------------------------------------


EBS PRESENTATION -- Oracle Applications Concepts

This presentation was prepared to create an general understanding on Oracle EBS technologies, as well as to give information about the tools that a developer may need to use within the EBS system. It was presented to EBS developers and functional users ... It covers general information about topics such as general architecture, file locations, cloning, gathering diagnostics, tracing , monitoring and etc.

------------------------------------------------------------------------------------------------------------

Oracle E-Business Suite R12 on Exadata V2 Sun Oracle Database Machine

------------------------------------------------------------------------------------------------------------

Oracle E-Business Suite 12.2 System Administration & Apps DBA presentation