Showing posts with label R12. Show all posts
Showing posts with label R12. Show all posts

STEP by STEP Installation of Oracle Applications Release 12


This is the install process for R12 Oracle applications on LINUX. Assuming that the LINUX is ready with all the rpms and OS settings.

I am doing a multiuser installation on LINUX.

In order to prepare for a multi-user installation, you must first create an oracle user account and an applmgr user account. Both should be created with a default shell that is compatible with the Bourne shell. Log in as root to run Rapid Install. Then specify the oracle user as the Oracle OS user, and the applmgr user as the Apps OS user.

Please complete all standard pre-reqs for LINUX install ( Like "/etc/sysctl.conf" for Shared memory and semaphors)

Create Oracle user
#useradd -u 1100 -g dba oraalpha
#passwd oraalpha
Changing password for user oraalpha.
New UNIX password:
BAD PASSWORD: it is based on a dictionary word
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
#

#useradd -u 1101 -g dba appalpha
#passwd appalpha
Changing password for user appalpha.
New UNIX password:
BAD PASSWORD: it is based on a dictionary word
Retype new UNIX password:
passwd: all authentication tokens updated successfully.

Create the STAGE area (Stage area is the software location for R12 software)


The script prompts you to choose the components that you want to stage:
1. Oracle Applications
2. Oracle Database technology stack (RDBMS)
3. Oracle Applications database (Databases)
4. Oracle Applications technology stack (Tools)
5. APPL_TOP

You should be able to see the following directories. (After your stage location is ready)
Software/Disk1/rapidwiz/adautostg.pl : This helps in creating the stage area for your installation.
startCD
oraDB
oraAppDB
oraAS
oraApps


After your stage area is ready, You can start the installation.
Please note that starting with R12 you need not to install the JDK seprately.

1. Login as root (on GUI , May be a VNC session)

cd /StageR12/startCD/Disk1/rapidwiz

Please note : If you want to use an alias (not the actual name of the host machine), use the
-servername parameter when you start Rapid Install.

rapidwiz -servername alias
rapidwiz -techstack (Can be used to install techstack only)

If install fails in between and you may need to restart it , You can use rapidwiz -restart


========
Installation Begins...

cd /StageR12/startCD/Disk1/rapidwiz
./rapidwiz


Oracle applications release 12 installation screen 1.


Oracle applications release 12 installation screen : This is welcome screen


You may choose if you want to do a fresh install of Release 12 oracle applications or You want to upgrade the existing oracle applications to R12. In this post we are doing the Fresh install of a Vision database with R12 Oracle applications.



Oracle connection tool information (If required and this is optional)


If you have Oracle support login you can provide the information in the above screen.
You may choose to create a new config file OR if you already have config file you can used the existing one.

Port pool: One of the very important task in installation. You should be careful here, Please make sure that no other applications is using the same port.
The net result of this is that there are 100 different port pools (sets), which are guaranteed to contain non-overlapping values
Vision Demo database is the Database which comes with the sample oracle applications data. This is used to the training purposes.

provide the base directory oracle and applmgr user details.

Another important discion to make here. If you want to keep all services on a single node you should do a Single node installation. If you want to spread the services on different boxes you can add another node. In General, The recommonded way is that we should keep the admin and Db server on one node and web/form on another node. This is to get the best perofmance.

This is the pre-req cheque



Once all pre-req checks are complete , You are ready to install the Oracle applications R12

Final screen before install.


Installation in progress....



Post innstall checks.

This is a known error  and generally occurs if you donot have enough memory at the time of post check. If you retry you may get success, Otherwise free some memory and then retry.

You must have all greens here in order to have your oracle applications work.

You are now ready to use the Oracle Applocations Release 12

Enter with Default username and password
:You must change all password to secure your oracle applications here.



Error Details:

checking URL = http://:/OA_HTML/AppsLogin




RW-50016: Error: - {0} was not created:

File = {1}

Fix:
This is a known error and generally occurs if you donot have enough memory at the time of post check. If you retry you may get success, Otherwise free some memory and then retry.



you may check this from DBA also, That this is related to Memory.

ORA-00060: Deadlock detected. More info in file /u05/oracle/ALPHA/db/tech_st/10.2.0/admin/ALPHA_serv0611/udump/alpha_ora_10277.trc.

Wed Apr 14 01:47:32 2010

Process J000 died, see its trace file

Wed Apr 14 01:47:32 2010

kkjcre1p: unable to spawn jobq slave process

Wed Apr 14 01:47:32 2010

Errors in file /u05/oracle/ALPHA/db/tech_st/10.2.0/admin/ALPHA_serv0611/bdump/alpha_cjq0_16160.trc:





Waited for process J000 to initialize for 60 seconds

*** 2010-04-14 00:31:20.440

Dumping diagnostic information for J000:

OS pid = 27634

loadavg : 11.75 5.49 5.12

memory info: free memory = 0.00M

swap info: free = 0.00M alloc = 0.00M total = 0.00M

F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD

000 D oraalpha 27634 1 0 78 0 - 23427 lock_p Mar22 ? 00:00:00 ora_j000_ALPHA

(no debugging symbols found)

Using host libthread_db library "/lib/tls/libthread_db.so.1".

(no debugging symbols found)

[Thread debugging using libthread_db enabled]


Please feel free to write if you need additional information on R12 install.
This blog is for STUDY purpose only, Please read Oracle Official documentations for the Refrences.



.

adadmin - R12 options

Adadmin is a Application maintainance utility.
Following options are available with this utility and This is how it is used.

adadmin
[printdebug=y|n][localworkers=]
[flags=hidepw|trace]

adadmin Non-Interactive mode
[defaultsfile=<$APPL_TOP/admin/SID/defaultsfile>]
[logfile=][interactive=y|n]
[workers=][menu_option=][restart=y|n]

where
localworkers = Used in Distributed AD. The number of workers to
run on the local machine.
flags = Generic flags passed to AD utilities. The available
values for Adadmin are hidepw and trace.
defaultsfile = The defaults file name that is located under
$APPL_TOP/admin/SID/ directory.
menu_option = Skips the menu in Adadmin and executes the task
provided on the command line.


Valid values for the menu options are listed below. Following Tasks can be achieved with adadmin.

RELINK Relink Applications programs
GEN_MESSAGES Generate message files
GEN_FORMS Generate form files
GEN_REPORTS Generate reports files
GEN_JARS Generate product JAR files
VALIDATE_APPS Validate APPS schema
CMP_INVALID Compile APPS schema
CMP_MENU Compile menu information
CREATE_GRANTS Recreate grants and synonyms for APPS schema
CMP_FLEXFIELDS Compile flexfield data in AOL tables
MAINTAIN_MLS Maintain multi-lingual tables
CHECK_DUAL Check DUAL table
RELOAD_JARS Reload JAR files to database
COPY_FILES Copy files to destinations
CHECK_FILES Check for missing files
LIST_SNAPSHOTS List snapshots
UPDATE_CURRENT_VIEW Update current view snapshot
CREATE_SNAPSHOT Create named snapshot
EXPORT_SNAPSHOT Export snapshot to file
IMPORT_SNAPSHOT Import snapshot from file
DELETE_SNAPSHOT Delete named snapshot(s)
CONVERT_CHARSET Convert character set
SCAN_APPLTOP Scan the APPLTOP for exceptions
SCAN_CUSTOM_DIR Scan a CUSTOM directory for exceptions
ENABLE_MAINT_MODE Enable Maintenance Mode
DISABLE_MAINT_MODE Disable Maintenance Mode

R12 startup/shutdown scripts

In this Blog , I am explaining the shutdown/startup scripts under $INST_TOP/admin/scripts/ (Application Tier) and $ORACLE_HOME/appsutil/scripts/context_name/

These scripts are used to start and shutdown oracle applications. (All together OR individual component)


adapcctl.sh:# | Start/stop/status Apache only

adformsctl.sh:# | This script is used to start, stop and check the status of the forms oc4j instance.

adformsctl.sh:# | This script is provided as a wrapper on top of the opmnctl script shipped

adformsrvctl.sh: printf "Forms Connect Mode is set to Servlet. Please Change Forms Mode to socket and then run this script.

adoacorectl.sh:# | This script is used to start, stop and check the status of the oacore oc4j instance.

adoacorectl.sh:# | This script is provided as a wrapper on top of the opmnctl script shipped

adoafmctl.sh:# | This script is used to start, stop and check the status of the oafm oc4j instance.

adopmnctl.sh:# | This script is used to start, stop and check the status of OPMN.

adstpall.sh:# | This script is used to stop Oracle E-Business Suite Services on machine machine-name
adstrtal.sh:# | This script is used to start Oracle E-Business Suite Services enabled on machine machine-name.


java.sh:# | This script is used by opmn and java concurrent programs to call java

adcmctl.sh : Start / Stop Concurrent Manager

adautocfg.sh: Runs autoconfig

gsmstart.sh: Start/Stop FNDSM

adalnctl.sh : Start/stop RPC listeners

adpreclone.pl : Cloning Prepration script.



DB Node:


adautocfg.sh:Runs Autoconfig

adchknls.pl
This scripts checks for the existance of the following:
RDBMS ORACLE_HOME/nls/data/XXdata directory


addlnctl.sh:#
Start / Stop Net8 Listener process
addlnctl.sh {start|stop} {listener}

adexecsql.pl: Execute all sql scripts that update the profiles in an AutoConfig run
adexecsql.pl sqlfile=

adlsnodes.sh: This script is used for 9i database only. For 10g database run /bin/olsnodes for checking the cluster status.
adlsnodes.sh: This script is used for 9i database only. For 11g database run /bin/olsnodes for checking the cluster status.

adpreclone.pl: Clone prepration scipt.



adstrtdb.sql:
to start DB : sqlplus /nolog @adstrtdb.sql

adstopdb.sql:
Script to shutdown database
sqlplus /nolog adstopdb.sql SHUTDOWN MODE



Process for startup

1. Start database (Manually OR @adstrtdb.sql)
2. Start Database listner (addlnctl.sh {start|stop} {listener}OR lsnrctl start listener-name
3. Start oracle applications services. (adstrtal.sh-Will start everything)

Process for shutdown

1. Shutdown Oracle Application services (adstpall.sh -Will shutdown everything (Other then DB and DB listener)
...........After running this script, Please wait till all processes are gone.
For Example if you are using applmgr (OS user) , Please check ps -ef | grep applmgr (No application process must be running)

Sometime you may need to kill some processes (Do it on your own risk -But believe me its commonly used)

2. Shutdown Datbase (Manually OR
adstopdb.sql:
Script to shutdown database
sqlplus /nolog adstopdb.sql SHUTDOWN MODE (Mostly shutdown immediate used)
3. Shutdown DB listener.
addlnctl.sh {start|stop} {listener} OR lsnrctl stop lisneter-name




Hope this help. Feel Free to update this if additional information is required.

Oracle EBS R12 Architecture

The Oracle Applications Architecture is a framework for multi-tiered, distributed computing that supports Oracle Applications products. In this model, various servers or services are distributed among three levels, or tiers.

Technology advances for EBS R12–
Certified on Oracle Fusion Middleware–Adapted the latest technology:
Oracle 10gR2 Database
Oracle Application Server 10g (10.1.2 for Forms & Reports, 10.1.3 for HTML & Java)
OA Framework and the new user interface
Oracle Containers for Java (OC4J)
Oracle Personalization
Extending R12 with JDeveloper10.1.3
Integration Repository
XML Publisher

Fully Certified on 64 bit platforms for App and DB tiers compared to 11.5.10 that requires 32 bit for App tier





R12 Oracle homes :




:

• The 10g Release 2 (10.2) Database Server ORACLE_HOME replaces the Oracle9i
ORACLE_HOME used in Release 11i.

• The Application Server 10.1.2 ORACLE_HOME (sometimes referred to as the Tools,
C, or Developer ORACLE_HOME) replaces the 8.0.6 ORACLE_HOME provided by
Oracle9i Application Server 1.0.2.2.2 in Release 11i.

• The Application Server 10.1.3 ORACLE_HOME (sometimes referred to as the Web
 Java ORACLE_HOME) replaces the 8.1.7-based ORACLE_HOME provided by
Oracle9i Application Server 1.0.2.2.2 in Release 11i.

R12 File System:




The db/apps_st/data (DATA_TOP) directory is located on the database node

machine, and contains the system tablespaces, redo log files, data tablespaces, index
tablespaces, and database files

 The db/tech_st/10.2.0 directory is located on the database node machine, and
contains the ORACLE_HOME for the Oracle10g database

The apps/apps_st/appl (APPL_TOP) directory contains the product directories and
files for Oracle Applications

The apps/apps_st/comn or (COMMON_TOP or COMN_TOP) directory contains
directories and files used across products

The apps/tech_st/10.1.2 directory contains the ORACLE_HOME used for the
Applications technology stack tools components

The apps/tech_st/10.1.3directory contains the ORACLE_HOME used for the
Applications technology stack Java components


Instance Home: Instance top : INST_TOP

Oracle Applications Release 12 introduces the concept of a top-level directory for an

Applications instance. This directory is referred to as the Instance Home, and denoted by
the environment variable $INST_TOP.


The basic structure of the instance home is:

/inst/apps//, where APPS_BASE (which does not
have or need a corresponding environment variable) is the top level of the Applications
installation, and is the highest level at which the Applications context exists.





Instance Home Directory Structure






$INST_TOP/admin/scripts ($ADMIN_SCRIPTS_HOME): All AD scripts are located here
$INST_TOP/appl ($APPL_CONFIG_HOME) : For standalone envs, this is set to $APPL_TOP
$INST_TOP/appl/fnd/12.0.0/secure FND_SECURE: The dbc file is located here
$INST_TOP/appl/admin All the env config files are located here
$INST_TOP/certs SSL Certificates go here
$INST_TOP/logs LOG_HOME: Central log file location. All log files are placed here (except adconfig)
$INST_TOP/logs/ora ($ORA_CONFIG_HOME)
$INST_TOP/logs/ora/10.1.2 Contains tnsnames and forms listener servlet config files
$INST_TOP/logs/ora/10.1.3 Apache & OC4J config home, Apache, OC4J and opmn. ‘Java’ oracle home configuration for OPMN, Apache and OC4J
$INST_TOP/pids Apache/Forms server PID files are located here
$INST_TOP/portal Apache’s DocumentRoot folder




New login screen for R12 oracle applications:





Startup and Shutdown r12

Application tier scripts (adstrtal.sh, adstpall.sh) can be found under $INST_TOP/admin/scripts directory, stop the services as applmgr user.


Database tier scripts (addbctl.sh, addlnctl.sh) can be found under $RDBMS_ORACLE_HOME/appsutil/scripts/ directory, stop the services as oracle user.


R12 instance:   Release 12 Vision for public access.by Solution Beacon
http://www.solutionbeacon.com/tools_r12vision.htm


Please feel free to ask any questions related to R12 new features.

adpatch options in R12

adpatch help=y

usage: adpatch [help=y]

adpatch Pre-Install Mode
[preinstall=y|n]

adpatch Test Mode
[apply=y|n]

adpatch Non-Interactive mode
[defaultsfile=<$APPL_TOP/admin/SID/defaultsfile>]
[logfile=][interactive=y|n][workers=]
[patchtop=][driver=][restart=y|n]
[abandon=y|n][wait_on_failed_job=y|n]

adpatch
[localworkers=][workers=]
[printdebug=y|n][parallel_index_threshold=]
[order=] [flags=][options=]

adpatch Upload Patch History From Filesystem
[uploadph=y|n]
where

* help=y - Prints help information about adpatch options.

* preinstall - To run adpatch in Pre-Install Mode.
Default - No.

* apply - To run adpatch in Test Mode.
Default - Yes.

* uploadph - To upload the patch history from the filesystem to the
database and exit. This feature can be used when the system
is not in maintenance mode.
Default - No.

* interactive - Invokes adpatch in Non-Interactive mode when
"interactive=no" is specified.
Default - Yes.

Following are usually specified in Non-Interactive Mode, however not all
are compulsory. Some are also valid for interactive mode.

* defaultsfile - Defaults file name.
Default - none. No default file read or written.
* logfile - Adpatch log file name.
Default - none. Adpatch prompts for this value.
* workers - Specifies the number of workers to run.
Default - none. Adpatch prompts for this value.
* patchtop - Top-level directory for the current patch.
Default - none. Adpatch prompts for this value.
* driver - Name of the patch driver file.
Default - none. Adpatch prompts for this value.
* backup - Absolute Path for backup.
Default - patchtop.
* restart - To restart an existing session.
Default - none. Adpatch prompts for this value.
* abandon - To abandon the previous failed session.
Default - No.
* wait_on_failed_job - To prevent adpatch from exiting, when all
workers have failed in Non-Interactive Mode.
Default - No.

* localworkers - Used in Distributed AD to specify the number of
workers to be run on the current machine.
Default - Value specified for workers.
* printdebug - To display extra debugging information.
Default - No.
* parallel_index_threshold - Threshold block count in each table, which when
exceeded for a table causes its indexes to be
created using parallel slaves.
Default - none. Adpatch does not create indexes
in parallel.

* order = To organize list of jobs to run in a phase. Default - forward.
* forward - The order in which jobs are listed in the
patch driver file.
* backward - Opposite to how the jobs are listed in the
patch driver file.

* flags = Generic flags passed to adpatch
* hidepw - To omit the "HIDEPW:" comments in the log file.
Default - hidepw.
* trace - To log all database operations to a trace file.
Default - notrace.
* logging - To create indexes in LOGGING or NOLOGGING mode.
Default - nologging.

* options = Generic options passed to adpatch.
* checkfile - To skip running exec, SQL, and exectier
commands if they are recorded as already run.
Default - checkfile.
* compiledb - To compile invalid objects in the database
after running actions in the database driver.
Default - compiledb.
* compilejsp - To compile out-of-date JSP files, if the patch
has copy actions for at least one JSP file.
Default - compilejsp.
* copyportion - To run commands found in a copy driver.
Default - copyportion.
* databaseportion - To run commands found in a database driver.
Default - databaseportion.
* generateportion - To run commands found in a generate driver.
Default - generateportion.
* integrity - To perform patch integrity checking.
Default - nointegrity.
* autoconfig - To run AutoConfig.
Default - autoconfig.
* actiondetails - To get the details of actions turned off.
Default - actiondetails.
* parallel - To run actions that update the database or
actions that generate files in parallel.
Default - parallel.
* prereq - To perform prerequisite patch checking prior
to running patch driver files.
Default - noprereq.
* revcache - To load the package revision cache (if adpatch
determines it is needed).
Default - revcache.
* validate - To connect to all registered Oracle
Applications schemas at the start of the patch.
Default - novalidate.
* hotpatch - A patch which can be applied in Normal mode.
Default - hotpatch.
* phtofile - The patch history will be saved to files.
Default - nophtofile.

Logout R12 Oracle applications:

Logout R12 Oracle applications:
• Ensure the users are trained to use the Logout or Home global buttons when completing their transactions.
• Do not train them to use the browser close (“x”) link.
• Logging out gracefully releases the memory and corresponding resources (i.e. connections, etc..)
• Releases process resources sooner

config.txt - rapid install

Previous releases of Oracle Applications only used a text file, config.txt, to store the supplied configuration values.


In Release 12, the name of this configuration file has changed, and it now includes the database SID, to give a file name of conf_.txt (for example, conf_PROD.txt). This file stores the information collected by Rapid Install for all database and Applications nodes.

Rapid Install stores copies of the conf_.txt file in three separate locations:

• Database 10g R2 /appsutil: This copy is used on database nodes, on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted.

• $INST_TOP: This copy is used on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted.

• /tmp/

adpatch - Oracle Applications r12

Part 1: Basics: This post will guide you about the patching  for oracle Applications.



1. Patch File Structure

Patches generally consist of a top-level directory that may contain several files, and one or more subdirectories. The top-level directory is named , where is the number of the patch. The most important files in the top-level directory are: README.txt, README.html and the unified driver file (named u.drv).

2.  Patch Formats


3. Adpatch will do the following


Use AutoPatch to apply patches to the Oracle Applications file system or database. It
gathers necessary information about your system through a series of prompts. When
you have completed the prompts, AutoPatch performs all the tasks required to apply
the patch, including the following:

■ Reads patch metadata to determine patch dependencies and requirements.
■ Uploads patch information from a prior patch session to the database (if needed).
■ Reads and validates the patch driver file and reads the product driver files.
■ Compares version numbers of object modules from the product libraries and
version numbers of the existing files against the patch files.
■ Backs up all existing files that will be changed by the patch.
■ Copies files.
■ Archives files in libraries.
■ Relinks executables.
■ Generates forms, reports, message, graphics, and Java archive (JAR) files.
■ Compiles JSP files and invalid database objects.
■ Updates database objects.
■ Runs AutoConfig to update configuration files, if any template files are introduced
or updated by the patch.
■ Saves patch information to the database.

AutoPatch takes no action if a patch contains no new updates to files or database
objects in your system. If AutoPatch detects that there is a previously failed AutoPatch
session, it will attempt to recover that session


4. Enable Maintenance Mode


Before you initiate an AutoPatch session, you must
a)Enable maintainance mode (Use adpatch options=hotpatch if you want to avoid turning on the maintainance mode)

 The Oracle Applications Manager (OAM) Maintenance Mode page allows
you to schedule system downtime and send alert messages to notify users of the
downtime schedule

5. Use adpatch utility to apply the patch.

6. Log Files


In addition to the main log file (adpatch.log), AutoPatch also creates several other log
files for specific purposes, for example, to record all the actions associated with
parallel workers. The log files are written to $APPL_TOP/admin//log (UNIX),
where is the value of your ORACLE_SID or TWO_TASK variable, or
in %APPL_TOP%\admin \\log (Windows), where is the value of
ORACLE_SID or LOCAL. Review these files when the AutoPatch session is complete




Autoconfig r12 , 2 new great features...

1)Running Autoconfig in parallel on multiple application nodes in Release 12 is supported right now.
 2)You can run restore.sh (UNIX) or restore.cmd (Windows) to roll back an AutoConfig session.

Removing Credentials from a Cloned EBS Production Database

Metalink note [ID 419475.1] descibes the process of Removing Credentials from Cloned EBS Production Database ..A very decent process

R12 Topic 2: Oracle Applications Product Prefixes / Oracle applications Products short name list in R12

Applications Product Prefixes
ABM - Activity Based Management (Obsolete)
AD - Applications DBA
AHL - Complex Maintenance Repair and Overhaul
AHM - Hosting Manager(Obsolete)
AK - Common Modules-AK
ALR - Alert
AME - Approvals Management
AMF - Fulfillment Services (Obsolete)
AMS - Marketing
AMV - Marketing Encyclopedia System
AMW - Internal Controls Manager
AN - Sales Analysis
AP - Payables
AR - Receivables
AS - Sales Foundation
ASF - Sales Online
ASG - CRM Gateway for Mobile Devices
ASL - Sales Offline
ASN - Sales
ASO - Order Capture
ASP - Oracle Sales for Handhelds
AST - TeleSales
AU - Application Utilities
AX - Global Accounting Engine
AZ - Application Implementation
BEN - Advanced Benefits
BIC - Customer Intelligence (obsolete)
BIE - eCommerce Intelligence
BIL - Sales Intelligence
BIM - Marketing Intelligence
BIN - Communications Intelligence
BIS - Applications BIS
BIV - Service Intelligence
BIX - Interaction Center Intelligence
BIY - Systems Intelligence
BLC - Utility Billing
BNE - Web Applications Desktop Integrator
BOM - Bills of Material
BSC - Balanced Scorecard
CCT - Telephony Manager
CDR - Oracle Clinical Data Repository
CE - Cash Management
CHV - Supplier Scheduling
CLA - APAC Consulting Localizations
CLE - EMEA Consulting Localizations
CLJ - Japan Consulting Localizations
CLL - LAD Consulting Localizations
CLN - Supply Chain Trading Connector for RosettaNet
CN - Incentive Compensation
CPGC - CPG - CDOA
CRP - Capacity
CS - Service
CSC - Customer Care
CSD - Depot Repair
CSE - Asset Tracking
CSF - Field Service
CSI - Install Base
CSL - Field Service/Laptop
CSM - Field Service/Palm
CSN - Call Center
CSP - Spares Management
CSR - Scheduler
CSS - Support (obsolete)
CST - Cost Management
CTB - Clinical Transaction Base
CUA - Capital Resource Logistics - Assets
CUC - Revenue Accounting
CUE - Billing Connect (obsolete)
CUF - Capital Resource Logistics - Financials
CUG - Citizen Interaction Center
CUI - Network Logistics - Inventory
CUN - Network Logistics - NATS (obsolete)
CUP - Network Logistics - Purchasing
CUR - Mass Market Receivables for Comms
CUS - Network Logistics
CZ - Configurator
DDD - CADView-3D
DDR - Demand Signal Repository
DEM01 - Team 01 Order Entry Demo
DNA - Development
DOM - Document Managment and Collaboration
DPP - Oracle Price Protection
DT - DateTrack
DUMMY_GMO - Obsolete Process Operations
EAA - SEM Exchange (obsolete)
EAM - Enterprise Asset Management
EC - e-Commerce Gateway
ECX - XML Gateway
EDR - E-Records
EGO - Advanced Product Catalog
EMS - Environment Management System
ENG - Engineering
ENI - Product Intelligence
EVM - Value Based Management
FEM - Enterprise Performance Foundation
FF - FastFormula
FII - Financial Intelligence
FLM - Flow Manufacturing
FND - Application Object Library
FPA - Project Portfolio Analysis
FPT - Banking Center (obsolete)
FRM - Report Manager
FTE - Transportation Execution
FTP - Transfer Pricing
FUN - Financials Common Modules
FV - Federal Financials
GCS - Financial Consolidation Hub
GHR - US Federal Human Resources
GL - General Ledger
GMA - Process Manufacturing Systems
GMD - Process Manufacturing Product Development
GME - Process Manufacturing Process Execution
GMF - Process Manufacturing Financials
GMI - Process Manufacturing Inventory
GML - Process Manufacturing Logistics
GMO - Manufacturing Execution System for Process Manufacturing
GMP - Process Manufacturing Process Planning
GMS - Grants Accounting
GMW - Process Manufacturing Portal
GNI - Genealogy Intelligence
GR - Process Manufacturing Regulatory Management
HCA - Healthcare
HCC - iHCConnect
HCN - iHCIntegrate
HCP - Healthcare Intelligence
HCT - Healthcare Terminology Server
HRI - Human Resources Intelligence
HXC - Time and Labor Engine
HXT - Time and Labor
IA - iAssets
IAM - Digital Asset Management
IBA - iMarketing (Obsolete)
IBC - Content Manager
IBE - iStore
IBP - Bill Presentment & Payment
IBT - iAuction
IBU - iSupport
IBW - Oracle Web Analytics
IBY - Payments
ICX - Oracle iProcurement
IEB - Interaction Blending
IEC - Advanced Outbound Telephony
IEM - Email Center
IEO - Interaction Center Technology
IEP - Predictive
IES - Scripting
IET - Call Center Connectors
IEU - Universal Work Queue
IEV - IVR Integrator
IEX - Collections
IGC - Contract Commitment
IGF - Financial Aid
IGI - Public Sector Financials International
IGS - Student System
IGW - Grants Proposal
IMC - Customers Online
IMT - iMeeting (obsolete)
INL - Oracle Landed Cost Management
INV - Inventory
IPA - Capital Resource Logistics - Projects
IPD - Product Development (obsolete)
IPM - Oracle Imaging Process Management
IRC - iRecruitment
ISC - Supply Chain Intelligence
ISX - iSettlement
ITA - Information Technology Audit
ITG - Internet Procurement Enterprise Connector
IZU - Oracle E-Business Suite Diagnostics
JA - Asia/Pacific Localizations
JE - European Localizations
JG - Regional Localizations
JL - Latin America Localizations
JMF - Supply Chain Localizations
JTF - CRM Foundation
JTM - Mobile Application Foundation
JTS - CRM Self Service Administration
LNS - Loans
ME - Controlled Availability Product(Obsolete)
MFG - Manufacturing
MIA - Mobile Applications for Inventory Management
MIV - Media Interactive
MQA - Mobile Quality Applications
MRP - Master Scheduling/MRP
MSC - Advanced Supply Chain Planning
MSD - Demand Planning
MSO - Constraint Based Optimization
MSR - Inventory Optimization
MST - Transportation Planning
MTH - Oracle Manufacturing Operations Center
MWA - Mobile Applications
OAM - Oracle Applications Manager
ODQ - Data Query
OE - Order Entry
OFA - Assets
OKB - Contracts for Subscriptions (Obsolete)
OKC - Contracts Core
OKC_REP_TXT_INDEX_OPTIMIZE - Optimize Contracts Repository Text index
OKC_REP_TXT_INDEX_SYNC - Build/syncronize Contracts Repository Text index
OKE - Project Contracts
OKI - Contracts Intelligence
OKL - Leasing and Finance Management
OKO - Contracts for Sales (Obsolete)
OKP - Contracts for Procurement (Obsolete)
OKR - Contracts for Rights (Obsolete)
OKS - Service Contracts
OKT - Royalty Management
OKX - Contracts Integration
ONT - Order Management
OPI - Operations Intelligence
OTA - Learning Management
OUC - University Curriculum
OZF - Trade Management
OZP - Trade Planning (Obsolete)
OZS - iClaims (Obsolete)
PA - Projects
PAY - Payroll
PBR - Budgeting and Planning
PER - Human Resources
PFT - Oracle Profitability Manager
PJI - Project Intelligence
PJM - Project Manufacturing
PMI - Process Manufacturing Intelligence
PN - Property Manager
PO - Purchasing
POA - Purchasing Intelligence
POM - Exchange
PON - Sourcing
POS - iSupplier Portal
PQH - Public Sector HR
PQP - Public Sector Payroll
PRP - Proposals
PSA - Public Sector Financials
PSB - Public Sector Budgeting
PSP - Labor Distribution
PSR - Public Sector Receivables
PTX - Patch Tracking System
PV - Partner Management
QA - Quality
QOT - Quoting
QP - Advanced Pricing
QPR - Oracle Deal Management
QRM - Risk Management
RCM - Regulatory Capital Manager (obsolete)
RG - Application Report Generator
RHX - Advanced Planning Foundation(obsolete)
RLA - Release Management Integration Kit (Obsolete)
RLM - Release Management
RMG - Risk Manager
RRC - Retail Core
RRS - Site Management
SHT - Applications Shared Technology
SSP - SSP
SYSADMIN - System Administration
TEST - test
VEA - Automotive
VEH - Automotive Integration Kit (Obsolete)
WIP - Work in Process
WMA - Manufacturing Mobile Applications
WMS - Warehouse Management
WPS - Manufacturing Scheduling
WSH - Shipping Execution
WSM - Shop Floor Management
XDO - XML Publisher
XDP - Provisioning
XLA - Subledger Accounting
XLE - Legal Entity Configurator
XNA - Service Assurance for Communications
XNB - Oracle Telecommunications Billing Integrator
XNC - Sales for Communications (Obsolete)
XNI - Install Base Intelligence (Obsolete)
XNM - Marketing for Communications (Obsolete)
XNP - Number Portability
XNS - Service for Communications (obsolete)
XNT - TeleBusiness for Telecom/Utilities
XTR - Treasury
ZFA - Financial Analyzer
ZPB - Enterprise Planning and Budgeting
ZSA - Sales Analyzer
ZX - E-Business Tax

R12 new features : Topic 1

New features R12 Topic 1

Case Sensitivity in Oracle Applications User Passwords

In previous releases of Oracle Applications, user passwords were treated as case
insensitive. Now, Oracle Applications user passwords can optionally be treated as case sensitive, depending on the mode you choose.

Case-sensitivity in passwords is controlled by the site-level profile option Signon
Password Case. This profile has two possible settings:

• Sensitive - Passwords are stored and compared as they are, with the password case

• Insensitive (or unset) - Passwords are treated as case insensitive. In Insensitive
mode, passwords are stored and compared in uppercase, similar to that in earlier
releases. The entered password and the decrypted password are converted to
uppercase prior to comparison.

r12 upgrade path

Prepare the DB home for R12 upgrade:
Oracle 10gR2 Database Preparation Guidelines for Oracle E-Business Suite Release 12 Upgrade (Doc ID: 403339.1).

Upgrade Path for Systems with 11.5.9 CU2 or 11.5.10.2 with a 10.2.0.3 Database

Path E is applicable for E-Business Suite systems already on either 11.5.9 CU2 or 11.5.10.2 and currently running 10.2.0.3 of the database. Systems in this category have databases not yet upgraded to 10.2.0.4, and whose administrators plan to continue using version 10.2.0.3 after upgrading to Release 12.0.4. While this is supported, Oracle recommends that users upgrade the database to the latest patch set of Oracle Database 10g Release 2 available (currently 10.2.0.4).
Path E follows the R12 upgrade path as documented in the Oracle Applications Upgrade Guide: Release 11i to Release 12.0.4. During the Migrate database to Oracle10g Release 2 step in Chapter 3, apply database patches to the existing 10.2.0.3 Oracle home and perform all tasks documented in the patch readmes, before continuing with the standard R12 upgrade process.

R12 GSS hangs

GSS for ALL got struck. ( Reason: Gather Schema Statistics concurrent program hung on an external tables. GSS can't collect stats on external tables)

SOL: This problem is a known bug and Oracle has given patch 5876047( This patch modifies FND_STATS package to exclude gathering statistics on external tables) for it.


Gather Schema Stats Failed With Ora-1 Errors After Applying Patch 5876047

Note:470556.1:

Take a backup of the FND_STATS_HIST table
Truncate table FND_STATS_HIST
Re-submit Gather Schema Statistics program.

You do NOT need to truncate this table after each run of Gather Schema Statistics. Doing it once
will be enough, because each run of GSS will use a new request_id