All about Oracle applications

Fixing a corrupt or a cloned database 11g Oracle Inventory

2011-04-08T12:33:00.002+01:00

DBA’s working with Oracle especially ERP applications are familiar with cloning environment on demand. The issue becomes tricky when you need to apply a database patch using Opatch for testing before moving it to production.
The Oracle Inventory is a critical part of oracle installation and created using OUI. This is useful when you what to find out what patches have been applied to the database, mostly during upgrades and patch applications.

When you run the command opatch lsinventory from the Opatch directory in the $ORACLE_HOME in a cloned environment you might see the output like below

applprod@gvaebsdb3:/u01/DEV3/apps/proddb/11.2.0/OPatch $ opatch lsinventory
Invoking OPatch 11.1.0.6.6
Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation. All rights reserved
Oracle Home : /u01/DEV4/apps/proddb/11.2.0
Central Inventory : n/a
from :
OPatch version : 11.1.0.6.6
OUI version : 11.2.0.1.0
OUI location : /u01/DEV3/apps/proddb/11.2.0/oui
Log file location : n/a
Patch history file: /u01/DEV3/apps/proddb/11.2.0/cfgtoollogs/opatch/opatch_history.txt
OPatch cannot find a valid oraInst.loc file to locate Central Inventory.
OPatch failed with error code 104
applprod@gvaebsdb3:/u01/DEV3/apps/proddb/11.2.0/OPatch

or
Now check the status of the inventory
applprod@gvaebsdb3:/u01/DEV3/apps/proddb/11.2.0/OPatch $ opatch lsinventory
Invoking OPatch 11.1.0.6.6
Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation. All rights reserved
Oracle Home : /u01/DEV4/apps/proddb/11.2.0
Central Inventory : n/a
Central Inventory : /home/applprod/oraInventory
from : /etc/oraInst.loc
OPatch version : 11.1.0.6.6
OUI version : 11.2.0.1.0
OUI location : /u01/DEV3/apps/proddb/11.2.0/oui
Log file location : /u01/DEV3/apps/proddb/11.2.0//cfgtoollogs/opatch/opatch-2011_Apr_09_40-20-30-CET_Tue.log

LsInventory Session failed: OPatch failed to locate Central Inventory.
Possible causes are:
The Central Inventory is corrupted
The oraInst.loc file specified is not valid.

OPatch failed with error code 72

At times the Inventory location can become corrupt or might have changed due to architecture due to different file systems etc. this will cause Opatch to error out with error code 104 and can hamper the database patch application.

To fix a corrupted oracle inventory implicates at times moving it to a different location or editing ContentsXML and changing the ORACLE_HOME_NAME

applprod@gvaebsdb3:~ /home/applprod/oraInventory/ContentsXML

Then go the $ORACLE_HOME/oui/bin

Launch the repair as shown below .Note you should attached the correct ORACLE_HOME and ORACLE_HOME_NAME can be anything

applprod@gvaebsdb3:/u01/DEV3/apps/proddb/11.2.0/oui/bin $ ./runInstaller -silent -invPtrLoc "/etc/oraInst.loc" -attachHome ORACLE_HOME="/u01/DEV3/apps/proddb/11.2.0" ORACLE_HOME_NAME="Ora11g_home1"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB. Actual 7954 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-04-08_11-32-32AM. Please wait ...applprod@gvaebsdb3:/u01/DEV3/apps/proddb/11.2.0/oui/bin $ The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /home/applprod/oraInventory
'AttachHome' was successful.
applprod@gvaebsdb3:/u01/DEV3/apps/proddb/11.2.0/oui/bin

Procedure to reconfigure EM on 11gR2 running Oracle Application 11.5.10.2

2010-08-25T15:16:00.003+01:00

This is a complete procedure I used to reconfigure the dbconsole on 11gR2. I migrated my source Oracle application database version 9.2.0.8 running on a 32 bit architecture listener to port 1523 single node to a dual node 64bit architecture for the 11gR2 database and the appsTier running on a HS22blade with 32 GB.

For clarity I used used the export import as its a cross platform migration. The destination 11gR2 I installed with the complete options Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options Release 11.2.0.1.0 - 64bit Production the source had Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production 32 bit. Follow the
Metalink Doc: 946413.1 Using Oracle E-Business Suite with a Split Configuration Database Tier on Oracle 11gR2
Metalink Doc: 881505.1 Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0)
Metalink Doc: 230627.1 Export/Import Process for Oracle Applications Release 11i Database Instances Using Oracle9i Enterprise Edition

The detail of the patching and spliting is not included here see my next posting. The initial 11gR2 db Console was functional.

Shutdown the EM dbconsole from $ORACLE_HOME/bin using $emctl stop dbconsole
Shutdown the listener from $ORACLE_HOME/bin using $lsnrctl stop LISTENER (note my Oracle Applications listener name is PROD)
Shutdown the Oracle configuration manager from $ORACLE_HOME/ccr using $ emCCR stop

Drop the following user ,role and sysnonym

applprod@gva2ebsdbprod:/u01/PROD/apps/proddb/cfgtoollogs/emca/PROD $ sqlplus '/as sysdba';
SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 25 14:13:00 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options

SQL> drop user sysman cascade;
User dropped.

SQL> drop role MGMT_USER;
Role dropped.

SQL> commit;
Commit complete.

SQL> drop user sysman cascade;
User dropped.

SQL> drop public synonym SETEMVIEWUSERCONTEXT;
Synonym dropped.

SQL> drop role MGMT_USER;
Role dropped.

SQL> drop PUBLIC SYNONYM MGMT_TARGET_BLACKOUTS;
Synonym dropped.

SQL> drop user MGMT_VIEW;
User dropped.

I had to register the new Listener PROD which is listening on port 1523 whereas the default IIg install listener was listener on port 1521

SQL> ALTER SYSTEM SET LOCAL_LISTENER="PROD" scope=spfile;
System altered.

First deconfigured the original EM dbconsole

applprod@gva2ebsdbprod:/u01/PROD/apps/proddb/11.2.0/bin $ emca -deconfig dbcontrol db

STARTED EMCA at Aug 25, 2010 12:07:32 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: PROD
Do you wish to continue? [yes(Y)/no(N)]: y
Aug 25, 2010 12:07:38 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/PROD/apps/proddb/cfgtoollogs/emca/PROD/emca_2010_08_25_12_07_32.log.
Aug 25, 2010 12:07:39 PM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration
WARNING: EM is not configured for this database. No EM-specific actions can be performed.
Enterprise Manager configuration completed successfully

Now use the recreate option

applprod@gva2ebsdbprod:/u01/PROD/apps/proddb/11.2.0/bin $ emca -config dbcontrol db -repos recreate

STARTED EMCA at Aug 25, 2010 12:55:25 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database SID: PROD
Listener port number: 1523
Listener ORACLE_HOME [ /u01/PROD/apps/proddb/11.2.0 ]:
Password for SYS user:
Password for DBSNMP user:
Password for SYSMAN user:
Email address for notifications (optional): gshelton@pajago.com
Outgoing Mail (SMTP) server for notifications (optional): vezfe1.europe.pajagogroup.com
-----------------------------------------------------------------

You have specified the following settings

Database ORACLE_HOME ................ /u01/PROD/apps/proddb/11.2.0

Local hostname ................ gva2ebsdbprod.pajagogroup.com
Listener ORACLE_HOME ................ /u01/PROD/apps/proddb/11.2.0
Listener port number ................ 1523
Database SID ................ PROD
Email address for notifications ............... gshelton@pajago.com
Outgoing Mail (SMTP) server for notifications ............... vezfe1.europe.pajagogroup.com

-----------------------------------------------------------------
Do you wish to continue? [yes(Y)/no(N)]: Y
Aug 25, 2010 12:55:53 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/PROD/apps/proddb/cfgtoollogs/emca/PROD/emca_2010_08_25_12_55_25.log.
Aug 25, 2010 12:55:54 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) ...
Aug 25, 2010 12:56:47 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Aug 25, 2010 12:56:47 PM oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) ...
Aug 25, 2010 1:01:26 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
Aug 25, 2010 1:01:29 PM oracle.sysman.emcp.EMReposConfig uploadConfigDataToRepository
INFO: Uploading configuration data to EM repository (this may take a while) ...
Aug 25, 2010 1:02:06 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Uploaded configuration data successfully
Aug 25, 2010 1:02:08 PM oracle.sysman.emcp.util.DBControlUtil configureSoftwareLib
INFO: Software library configured successfully.
Aug 25, 2010 1:02:08 PM oracle.sysman.emcp.EMDBPostConfig configureSoftwareLibrary
INFO: Deploying Provisioning archives ...
Aug 25, 2010 1:02:28 PM oracle.sysman.emcp.EMDBPostConfig configureSoftwareLibrary
INFO: Provisioning archives deployed successfully.
Aug 25, 2010 1:02:28 PM oracle.sysman.emcp.util.DBControlUtil secureDBConsole
INFO: Securing Database Control (this may take a while) ...
Aug 25, 2010 1:03:08 PM oracle.sysman.emcp.util.DBControlUtil secureDBConsole
INFO: Database Control secured successfully.
Aug 25, 2010 1:03:08 PM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
Aug 25, 2010 1:03:29 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: Database Control started successfully
Aug 25, 2010 1:03:29 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: >>>>>>>>>>> The Database Control URL is https://gva2ebsdbprod.pajagogroup.com:1158/em <<<<<<<<<<<
Aug 25, 2010 1:03:31 PM oracle.sysman.emcp.EMDBPostConfig invoke
WARNING:
************************ WARNING ************************

Management Repository has been placed in secure mode wherein Enterprise Manager data will be encrypted. The encryption key has been placed in the file: /u01/PROD/apps/proddb/11.2.0/gva2ebsdbprod.pajagogroup.com_PROD/sysman/config/emkey.ora. Please ensure this file is backed up as the encrypted data will become unusable if this file is lost.

***********************************************************
Enterprise Manager configuration completed successfully
FINISHED EMCA at Aug 25, 2010 1:03:31 PM
applprod@gva2ebsdbprod:/u01/PROD/apps/proddb/11.2.0/bin $

Cmments are welcome
sheltong@gmail.com
Senior Oracle Applications and OBIA DBA

Configuring EM console and repository on Oracle 11gR2

2010-07-15T11:22:00.002+01:00

There are 3 database users that must MUST be configured to successfully deploy EM dbconsole on 11gR2

if by accident you dropped DBSNMP user please use the script below to recreate the user and SNMPAgent role to access the v$ tables
cd $catsnmp.sql

You must drop these 2 users using the cascade option as they are recreated by the emca if you don't rop them the EM dbconsole creation will fail

SQL> drop user sysman cascade;
SQL> drop user MGMT_VIEW cascade;

You can now proceed with the EM configuration all the file are found under $ORACLE_HOME/bin

Create Database Console

To create the configuration files and repository for Database Console, run:
$ emca -config dbcontrol db -repos create

STARTED EMCA at Jul 14, 2010 11:28:03 AM
EM Configuration Assistant, Version 11.1.0.7.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database SID: BIDEV
Listener port number: 1521
Password for SYS user: bimaster
Password for DBSNMP user: bimanager
Password for SYSMAN user: bimanager
Email address for notifications ...............gshelton@amuru.com
Email address Outgoing Mail (SMTP) server for notifications ...............vezfe1.uganda.amurugroup.com

You have specified the following settings

Database ORACLE_HOME ................ /u01/BIDEV/apps/oracle/product/11.1.0.7

Database hostname ................ gva2bidevdb.amurugroup.com
Listener port number ................ 1521
Database SID ................ BIDEV
Email address for notifications ...............gshelton@amuru.com
Email address Outgoing Mail (SMTP) server for notifications ...............vezfe1.uganda.amurugroup.com

Do you wish to continue? [yes(Y)/no(N)]: Y
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/BIDEV/apps/oracle/product/11.1.0.7/cfgtoollogs/emca/BIDEV/emca_2010-07-15_09-59-39-PM.log.
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: Database Control started successfully
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: >>>>>>>>>>> The Database Control URL is http://gva2bidevdb.amurugroup.com:1158/em <<<<<<<<<<<
Enterprise Manager configuration completed successfully
FINISHED EMCA at Jul 14, 2010 11:28:03 AM

Drop Database Console

To drop (remove) the configuration files and repository for Database Console, run:
$ emca -deconfig dbcontrol db -repos drop

STARTED EMCA at Jul 14, 2010 11:28:03 AM
EM Configuration Assistant, Version 11.1.0.7.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database SID: BIDEV
Listener port number: 1521
Password for SYS user: bimaster
Password for SYSMAN user: bimanager

Do you wish to continue? [yes(Y)/no(N)]: Y
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/BIDEV/apps/oracle/product/11.1.0.7/cfgtoollogs/emca/BIDEV/emca_2010-07-15_09-53-55-PM.log.
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig dropRepository
INFO: Dropping the EM repository (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Jul 14, 2010 11:28:03 AM

Recreate Database Console

To recreate the configuration files and repository for Database Console, run:
$ emca -config dbcontrol db -repos recreate

STARTED EMCA at Jul 14, 2010 11:28:03 AM
EM Configuration Assistant, Version 11.1.0.7.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database SID: BIDEV
Database Control is already configured for the database BIDEV
You have chosen to configure Database Control for managing the database BIDEV
This will remove the existing configuration and the default settings and perform a fresh configuration
Do you wish to continue? [yes(Y)/no(N)]: Y
Listener port number: 1521
Password for SYS user: bimaster
Password for DBSNMP user: bimanager
Password for SYSMAN user: bimanager
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):

You have specified the following settings

Database ORACLE_HOME ................ /u01/BIDEV/apps/oracle/product/11.1.0.7

Database hostname ................ gva2bidevdb.amurugroup.com
Listener port number ................ 1521
Database SID ................ BIDEV
Email address for notifications ...............gshelton@amuru.com
Email address Outgoing Mail (SMTP) server for notifications ...............vezfe1.uganda.amurugroup.com

Do you wish to continue? [yes(Y)/no(N)]: Y
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/BIDEV/apps/oracle/product/11.1.0.7/cfgtoollogs/emca/BIDEV/emca_2010-07-15_10-08-20-PM.log.
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig dropRepository
INFO: Dropping the EM repository (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: Database Control started successfully
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: >>>>>>>>>>> The Database Control URL is http://gva2bidevdb.amurugroup.com:1158/em <<<<<<<<<<<
Enterprise Manager configuration completed successfully
FINISHED EMCA at Jul 14, 2010 11:28:03 AM

Using EMCA with Real Application Clusters

In this section, I will be using two Database Control consoles running; one on gva2bidevdb1 and the other on linux2. From either of these consoles, you can manage and monitor all targets in the cluster.

For information on the current cluster configuration, you can run:
$ emca -displayConfig dbcontrol -cluster

STARTED EMCA at Jul 14, 2010 11:28:03 AM
EM Configuration Assistant, Version 11.1.0.7.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database unique name: biprod

Do you wish to continue? [yes(Y)/no(N)]: Y
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/BIDEV/apps/oracle/product/11.1.0.7/cfgtoollogs/emca/orcl/emca_2010-07-15_10-30-51-PM.log.
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig showClusterDBCAgentMessage
INFO:
**************** Current Configuration ****************
INSTANCE NODE DBCONTROL_UPLOAD_HOST
---------- ---------- ---------------------

biprod1 gva2bidevdb1 gva2bidevdb1
biprod2 gva2bidevdb2 gva2bidevdb1

Enterprise Manager configuration completed successfully
FINISHED EMCA at Jul 14, 2010 11:28:03 AM
The above command prompts for the database unique name for the cluster database. This will print the current configuration onto the screen, indicating the nodes that have consoles running on them and the consoles where each agent is uploading.

Create Database Console

$ emca -config dbcontrol db -repos create -cluster

STARTED EMCA at Jul 14, 2010 11:28:03 AM
EM Configuration Assistant, Version 11.1.0.7.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database unique name: orcl
Listener port number: 1521
Cluster name: crs
Password for SYS user: bimaster
Password for DBSNMP user: bimanager
Password for SYSMAN user: bimanager
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
ASM ORACLE_HOME [ /u01/BIDEV/apps/oracle/product/11.1.0.7 ]: /u01/BIDEV/apps/oracle/product/11.1.0.7
ASM port [ 1521 ]: 1521
ASM user role [ SYSDBA ]: SYSDBA
ASM username [ SYS ]: SYS
ASM user password:

You have specified the following settings

Database ORACLE_HOME ................ /u01/BIDEV/apps/oracle/product/11.1.0.7

Database instance hostname ................ gva2bidevdb1
Listener port number ................ 1521
Cluster name ................ crs
Database unique name ................ orcl
Email address for notifications ...............gshelton@amuru.com
Email address Outgoing Mail (SMTP) server for notifications ...............vezfe1.uganda.amurugroup.com
ASM ORACLE_HOME ................ /u01/BIDEV/apps/oracle/product/11.1.0.7
ASM port ................ 1521
ASM user role ................ SYSDBA
ASM username ................ SYS

Do you wish to continue? [yes(Y)/no(N)]: y
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/BIDEV/apps/oracle/product/11.1.0.7/cfgtoollogs/emca/orcl/emca_2007-06-12_11-07-56-AM.log.
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig createRepository
INFO: Creating the EM repository (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully created
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBCConfig instantiateOC4JConfigFiles
INFO: Propagating /u01/BIDEV/apps/oracle/product/11.1.0.7/oc4j/j2ee/OC4J_DBConsole_gva2bidevdb1_biprod1 to remote nodes ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBCConfig instantiateOC4JConfigFiles
INFO: Propagating /u01/BIDEV/apps/oracle/product/11.1.0.7/oc4j/j2ee/OC4J_DBConsole_linux2_biprod2 to remote nodes ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMAgentConfig deployStateDirs
INFO: Propagating /u01/BIDEV/apps/oracle/product/11.1.0.7/gva2bidevdb1_biprod1 to remote nodes ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMAgentConfig deployStateDirs
INFO: Propagating /u01/BIDEV/apps/oracle/product/11.1.0.7/linux2_biprod2 to remote nodes ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: Database Control started successfully
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig performConfiguration
INFO: >>>>>>>>>>> The Database Control URL is http://gva2bidevdb1:1158/em <<<<<<<<<<<
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMDBPostConfig showClusterDBCAgentMessage
INFO:
**************** Current Configuration ****************
INSTANCE NODE DBCONTROL_UPLOAD_HOST
---------- ---------- ---------------------

biprod1 gva2bidevdb1 gva2bidevdb1
biprod2 linux2 gva2bidevdb1

Enterprise Manager configuration completed successfully

FINISHED EMCA at Jul 14, 2010 11:28:03 AM

Drop Database Console

$ emca -deconfig dbcontrol db -repos drop -cluster

STARTED EMCA at Jul 14, 2010 11:28:03 AM
EM Configuration Assistant, Version 11.1.0.7.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database unique name: orcl
Listener port number: 1521
Password for SYS user: bimaster
Password for SYSMAN user: bimanager
Do you wish to continue? [yes(Y)/no(N)]: y
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/BIDEV/apps/oracle/product/11.1.0.7/cfgtoollogs/emca/orcl/emca_2007-06-12_10-53-57-AM.log.
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig dropRepository
INFO: Dropping the EM repository (this may take a while) ...
Jul 14, 2010 11:28:03 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Jul 14, 2010 11:28:03 AM

Resolving install EM issues

It’s paramount to have create the password file created in $ORACLE_HOME/dbs using orapwd otherwise you will have some errors like
Jul 14, 2010 6:13:39 PM oracle.sysman.emcp.EMReposConfig unlockMGMTAccount
CONFIG: Unlocked mgmt_view account
Jul 14, 2010 6:13:39 PM oracle.sysman.emcp.EMReposConfig invoke
CONFIG: Successfully unlocked mgmt_view account
Jul 14, 2010 6:13:39 PM oracle.sysman.emcp.ParamsManager getParam
CONFIG: No value was set for the parameter ORACLE_HOSTNAME.
Jul 14, 2010 6:13:39 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine connecting with SID: BIDEV, oracleHome: /u01/BIDEV/apps/oracle/product/11.1.0.7, and user: SYS
Jul 14, 2010 6:13:39 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine created successfully and connected
Jul 14, 2010 6:13:40 PM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl
CONFIG: ORA-01031: insufficient privileges

oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-01031: insufficient privileges
at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1530)
at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeSql(SQLEngine.java:1771)
at oracle.sysman.emcp.ParamsManager.checkListenerStatusForDBControl(ParamsManager.java:2682)
at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:368)
at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:147)
at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:222)
at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:535)
at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1215)
at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:519)
at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:468)
Jul 14, 2010 6:13:40 PM oracle.sysman.emcp.EMConfig perform
SEVERE: Listener is not up. Start the Listener and run EM Configuration Assistant again .
Refer to the log file at /u01/BIDEV/apps/oracle/product/cfgtoollogs/emca/BIDEV/emca_2010_07_14_18_08_29.log for more details.
Jul 14, 2010 6:13:40 PM oracle.sysman.emcp.EMConfig perform
CONFIG: Stack Trace:
oracle.sysman.emcp.exception.EMConfigException: Listener is not up. Start the Listener and run EM Configuration Assistant again .at oracle.sysman.emcp.ParamsManager.checkListenerStatusForDBControl(ParamsManager.java:2689)
at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:368)
at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:147)
at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:222)
at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:535)at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1215)
at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:519)
at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:468)

If you have any problems when running emca, check the log file under:
$ORACLE_HOME/cfgtoollogs/emca//

Autoconfig errors with icxwebprf.sh INSTE8_PRF 1

2010-06-08T13:09:00.002+01:00

Running a post clone process on a test server results in a failure to successfully run all components and the log shows the below error

[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:

[PROFILE PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: /u01/UAT/apps/prodcomn/admin/install/UAT_gva2ebs
icxwebprf.sh INSTE8_PRF 1

AutoConfig is exiting with status 1

select constraint_name from user_cons_columns where table_name = 'FND_OAM_CONTEXT_FILES' and column_name = 'CTX_TYPE';

/u01/UAT/apps/prodcomn/admin/log/UAT_gva2ebs

applprod@gva2ebs:/u01/UAT/apps/prodcomn/admin/log/UAT_gva2ebs $ more icxwebprf.txt
Enter value for 4: http
Enter value for 5: 8002
Updated profile option value - 1 row(s) updated
Application Id : 178
Profile Name : POR_CACERT_FILE_NAME
Level Id : 10001
New Value : /u01/UAT/apps/prodora/iAS/Apache/Apache/conf/ssl.crt/ca-bundle.crt
Old Value : /u01/PROD/apps/prodora/iAS/Apache/Apache/conf/ssl.crt/ca-bundle.crt
declare
*
ERROR at line 1:
ORA-04091: table APPLSYS.FND_PROFILE_OPTION_VALUES is mutating,
trigger/function may not see it
ORA-06512: at "APPS.FND_CORE_LOG", line 25
ORA-06512: at "APPS.FND_CORE_LOG", line 432
ORA-06512: at "APPS.FND_PROFILE", line 110
ORA-06512: at "APPS.FND_GLOBAL", line 539
ORA-06512: at "APPS.FND_PROFILE_OPTION_VALUES_AI", line 1
ORA-04088: error during execution of trigger
'APPS.FND_PROFILE_OPTION_VALUES_AI'
ORA-06512: at line 61
ORA-06512: at line 120

Solution

Disable the following 3 triggers and run autoconfig all should be okay

ALTER TRIGGER FND_PROFILE_OPTION_VALUES_AD DISABLE;
ALTER TRIGGER FND_PROFILE_OPTION_VALUES_AI DISABLE;
ALTER TRIGGER FND_PROFILE_OPTION_VALUES_AU DISABLE;

VMWARE ESX Server 3.5 update 2 Installation

2010-02-28T16:26:00.050Z

Products such as VMware Server and VMware Workstation are hypervisors that sit on top of a guest operating system, so some of the server resources are taken up by the host operating system. ESX Server is the enterprise level hypervisor from VMware, which installs on the "bare-metal", making it significantly more efficient.
Once installed, you are able to create virtual machines, each running as a complete system, with processors, memory, networking, storage and BIOS.

Download the following software.

VMware ESX Server

VMware ESX Server Installation
Start the VMware ESX Server installation by booting from the VMware ESX Server CD.

Tab to the "Skip" button and press the "Enter" key to skip the media test.

Select the "Install" installation type option, then click the "Next" button.

Accept the license agreement, then click the "Next" button.

Accept the default partitioning option by clicking the "Next" button

Click the "Next" button on the "Advanced Options" screen.

Enter the appropriate network information for your site, then click the "Next" button.

Select your time zone by clicking on the map or selecting the location on the "Location" tab, then click the "Next" button.

Enter the "root" password, and create any additional users required. Additional users can also be created from the client tool at a later time. Click the "Next" button.

Check the summary information for the installation, then click the "Next" button.

Wait while the installation takes place

Once the installation is complete, click the "Finish" button.

Once the server has rebooted, you are presented with the console window, which lists the URL for the VMware ESX Server 3 welcome page.

Open a browser on a client PC and got to the link specified on console screen.

The resulting page includes a link to the VMware Infrastructure Client installation, which we will install next.

VMWARE INFRASTRUCTURE CLIENT INSTALLATION

Navigate to the VMware ESX Server 3 welcome page using the URL listed on the console and click the "Download VMware Infrastructure Client" link. Start the installation once the download is complete.
Select the appropriate setup language and click the "OK" button.

Click the "Next" button on the welcome page

Accept the license agreement and click the "Next" button

Enter the customer information and click the "Next" button.

Click the "Next" button on the "Custom Setup" screen.

Accept the default destination folder by clicking the "Next" button.

Wait while the installation takes place.

Start the client application and log in to the ESX server with the credentials specified during the installation.

You are then presented with the console.

You are now ready to start creating virtual machines.

VIRTUAL MACHINE SETUP
The virtual machine creation process will vary a little depending on your requirement. To give you a feel for the process I will set up a small Red Hat Enterprise Linux (RHEL) 5 virtual machine.
Right-click on the ESX server in the left-hand pane and select the "New Virtual Machine..." menu option.

Select the custom option and click the "Next" button.

Enter the virtual machine name as you would like it to appear in the right-hand pane of the client, then click the "Next" button.

Select the appropriate operating system and version, then click the "Next" button.

Enter the required amount of memory for the virtual machines, then click the "Next" button.

Accept the default storage adapter by clicking the "Next" button.

Enter the appropriate disk capacity, then click the "Next" button.

If you are happy with the summary information, click the "Finish" button.

To start the virtual machine, click the play button on the toolbar. The virtual machine will start and attempt to boot from any installable media, or the network.

GUEST OPERATING SYSTEM INSTALLATION

Place the operating system disk in the client PC's CD drive and start the virtual machine by clicking the play button on the toolbar. The right pane of the client should display a boot loader, then the operating system installation screen

Continue through the operating system installation as you would for a normal server.
VMware Tools Installation
Once the operating system installation is complete, you should install the VMware tools. The process my vary a little depending on the operating system. This example shows the installation on Red Hat Enterprise Linux (RHEL) 5.
From the "VM" menu, select the "Install/Upgrade VMware Tools" menu option.

Click the "OK" button in the information dialog.

A folder group will appear containing an "RPM" file. Right-click on the file and select the "Open with "Software Installer"" menu option.

Once the software has installed, click the "OK" button and the CD should unmount automatically

You must then run the "vmware-config-tools.pl" script as the root user.
# vmware-config-tools.pl
Accept all the default settings and pick the screen resolution of your choice. The VMware tools are now installed.

Start the VMware Toolbox using the "vmware-toolbox" command.
# /usr/bin/vmware-toolbox
Select the time synchronization options, then close the dialog.

Reboot the server and the virtual machine installation is complete. You can now start using your virtual machine just like any other server.

Enjoy

VNC setup on Oracle servers running Linux Redhat operating system

2010-02-28T16:24:00.001Z

VNC setup on Oracle servers running Linux Redhat operating system.
VNC is a headless display server which proves the same options than system display servers. They do not require video adapter hardware nor a monitor.
Here are the steps to set it up on Oracle servers.

1. Setting up runlevel 3
First the server runlevel must be set to 3.
This is done in the /etc/inittab file:
We replace
id:5:initdefault:
with
id:3:initdefault:

2. Running the VNC server at system startup

We configure VNC to start with runlevel 3. We can use the serviceconf system tool to do so:

root@hostname:~ # export LANG=C
root@hostname:~ # export DISPLAY=10.42.10.9:0
root@hostname:~ # serviceconf &

3. VNC server configuration

The VNC server must be started on display :0.

To do this we add/uncomment the following line in the /etc/sysconfig/vncservers file:

VNCSERVERS="0:root"

To authorize the localhost – here vernier - to access the DISPLAY, we add the red line to /root/.vnc/xstartup

#!/bin/sh

xhost +hostname
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

4. VNC server status

To check if the VNC server is running, we type the following command:

root@hostname:~ # ps -ef | grep vnc
root 7019 1 0 Apr19 ? 00:00:00 Xvnc :0 -desktop X -httpd /usr/s
root 2754 2673 0 19:53 pts/0 00:00:00 grep vnc

5. VNC server manual start/stop

To start the VNC server manually, we type the following command:
/usr/bin/vncserver :0

Example with DISPLAY :1:
root@hostname:~ # vncserver :1
New 'X' desktop is hostname:1

Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/hostname:1.log

To stop it we type:
/usr/bin/vncserver –kill :0

Example with DISPLAY :1:
root@hostname:~ # vncserver -kill :1
Killing Xvnc process ID 17005

OATM Migration on 11.5.10 CU2

2010-02-03T13:29:00.002Z

How to run OATM migration utility Note: 404954.1

Applies to: Oracle Application Object Library - Versio 11.5.10.2
Information in this document applies to any platform.

Goal

1- Review OATM Model for Oracle Applications 11i
2- Install OATM migration utility
3- Run OATM migration utility
4- Parameters needed while starting OATM utility
5- OATM Menu Structure

Solution

1- Review OATM Model for Oracle Applications 11i

The Oracle Applications Tablespace Model (OATM) introduces a new, consolidated tablespace model in Oracle Applications uses 12 locally managed tablespaces for all products including the temporary tablespace, system tablespace, and undo segments. In this revised Oracle Applications Tablespace Model, each Oracle Applications database object is mapped to a tablespace based on its Input/Output characteristics. This new model allows for easier maintenance, reduces space usage, and allows for potential run-time performance gains.
The Oracle Applications Tablespace Migration Utility is an interactive menu-based PERL program including a set of sizing estimate reports. It enables customers to convert their Oracle Applications databases to the new tablespace model (OATM) for either all schemas at once or partially for select schema(s) at a time, depending on acceptable down time and available disk space.

You can find more information about OATM migration utility in the following note:
Note 248857.1 - OATM Release 11i - Tablespace Migration Utility

Also please refer to Oracle Documentation:
http://download-uk.oracle.com/docs/cd/B25516_14/current/acrobat/115sacg.zip

2- Install OATM migration utility
You can install the OATM migration utility by downloading & applying the following patch through Metalink:Patch 3942506 - AOL/FND: OATM MIGRATION UTILITY ROLLUP C
(Note: Above patch is already included in 11.5.10 and higher, so if you have Oracle Applications 11.5.10 or higher you do not need to install it)

/u01/MIG/apps/prodappl/admin/mig/log

3- Run OATM migration utility
After installing the utility through above patch, please use the following command in order to start running the utility:
perl $FND_TOP/bin/fndtsmig.pl
4- Parameters needed while starting OATM utility

After running the PERL script in order to start the OATM utility, the following parameters screen will appear:
+=======================================================================+
Copyright (c) 2003 Oracle Corporation Redwood Shores, California, USA
All rights reserved.
+=======================================================================+

Welcome to the Oracle Applications Tablespace Migration Utility

+=======================================================================+

Warning: If DB was upgraded from 8.1.7 to a version prior to 9.2.0.6
please run $FND_TOP/patch/115/sql/fndupglb.sql before the migration.

+=======================================================================+
Enter OATM configuration file or press enter to continue:
Enter APPL_TOP [/u01/MIG/apps/prodappl]:
Enter FND_TOP [/u01/MIG/apps/prodappl/fnd/11.5.0]:
Enter the Database Connect String [MIG]:
Enter the password for your 'SYSTEM' ORACLE schema:
Successfully connected to database MIG using SYSTEM user.
Enter the ORACLE APPS Schema name[APPS]: apps
Enter the password for APPS:
Successfully connected to database MIG using APPS user.
Enter the ORACLE Application Object Library Schema name[APPLSYS]: applsys
================================================================
CONNECT_STRING =MIG
FND_TOP =/u01/MIG/apps/prodappl/fnd/11.5.0
APPLSYS_SCHEMA =APPLSYS
APPS_SCHEMA =APPS
APPL_TOP =/u01/MIG/apps/prodappl
================================================================

Please review and press 'Y' to accept or 'N' to re-enter[Y]: y
Performing database check...
Database check completed.
Checking required components...
Required components check completed.

5- OATM Menu Structure
After providing all parameters as in the previous step, you will get the Main Menu for Oracle Applications Tablespace Migration Utility which consists of 8 options as following:
Important Note: Some Menu Options are available only on 11.5.10.2 and later such as: Migrate CTXSYS Schema, Generate script to drop empty tablespaces.

Oracle Applications Tablespace Migration Utility
Main Menu

1. Migration Sizing Reports
2. Create New Tablespaces
3. Generate Migration Commands
4. Execute Migration Commands
5. Run Migration Status Reports
6. Run Post Migration Steps
7. Run Customization Steps
8. Run Migration in Batch Mode
[Q]uit [N]ext
Please enter your option -
Here are the details for each menu option:

5.1. Migration Sizing Reports
Migration Sizing Reports

These reports are provided to help you gauge the space requirements for the new Tablespaces. Additionally, they will also help you determine the type of migration approach that best suits your needs

1. Generate a Report with the list of all the Oracle Application product schemas that can be migrated
2. Calculate total space required by each new tablespace to migrate all Oracle Application product schemas (relevant for a complete migration)
3. Calculate total space required by each new tablespace to migrate each Oracle Application product schema (relevant for a schema-by-schema migration)
4. Calculate total space required by each Oracle Applications schema, with details for each object
5. Display Sizing Exception report

[Q]uit [B]ack [N]ext

Please enter your option -
5.2. Create New Tablespaces
Create New Tablespaces

1. Generate new tablespace creation script
2. Create new tablespaces

[Q]uit [B]ack [N]ext

Please enter your option -

5.3. Generate Migration Commands

Generate Migration Commands
Generation of Migration commands including disable/enable
commands for triggers, constraints, policies, stop/start for queues.

1. Invalid Indexes Report. Please correct/drop these before generating migration commands
2. Generate migration commands for all schemas
3. Generate migration commands for a list of schemas

[Q]uit [B]ack [N]ext

Please enter your option -
5.4. Execute Migration Commands

Execute Migration Commands
Execution of Migration commands including disable commands for triggers constraints, stop/start for queues.

PLEASE TAKE A COMPLETE BACKUP OF THE DATABASE BEFORE MIGRATION

1. Migrate all Schemas
2. Migrate a list of Schemas
3. Migrate CTXSYS Schema

Note: Migrate CTXSYS schema when no other migration process is in progress.

[Q]uit [B]ack [N]ext

Please enter your option -
5.5. Run Migration Status Reports
Run Migration Status Reports

1. Run migration progress report
2. Run migration error report

[Q]uit [B]ack [N]ext

Please enter your option -
5.6. Run Post Migration Steps
Run Post Migration Steps

1. Run audit report
2. Enable constraints/triggers/policies & start queues
3. Resize old tablespaces
4. Generate script to drop empty tablespaces

Note: Please complete refresh all the Materialized Views
in Oracle Applications before using the system.

[Q]uit [B]ack

Please enter your option -
5.7. Customization
Customization

1. Register new tablespace - tablespace type
2. Change name of the existing tablespace
3. Register object classification
4. Change object classification

[Q]uit [B]ack
Please enter your option -
5.8. Batch Mode Migration
Batch Mode Migration

1. Run Migration in Batch Mode
2. Run Migration Monitor

[Q]uit [B]ack

Please enter your option -

OATM migration

applprod@vezora1:~ $ cd /u01/MIG/apps/prodappl/fnd/11.5.0/bin
applprod@vezora1:/u01/MIG/apps/prodappl/fnd/11.5.0/bin $ perl fndtsmig.pl
+=======================================================================+
Copyright (c) 2003 Oracle Corporation Redwood Shores, California, USA
All rights reserved.
+=======================================================================+

Welcome to the Oracle Applications Tablespace Migration Utility

+=======================================================================+

Warning: If DB was upgraded from 8.1.7 to a version prior to 9.2.0.6
please run $FND_TOP/patch/115/sql/fndupglb.sql before the migration.

+=======================================================================+

Enter OATM configuration file or press enter to continue:

Enter APPL_TOP[/u01/MIG/apps/prodappl]:

Enter FND_TOP[/u01/MIG/apps/prodappl/fnd/11.5.0]:

Enter the Database Connect String[MIG]:

Enter the password for your 'SYSTEM' ORACLE schema:

Successfully connected to database MIG using SYSTEM user.

Please create log directory /u01/MIG/apps/prodappl/admin/mig/log to continue:
Enter the ORACLE APPS Schema name[APPS]: ma6utoza

Enter the ORACLE APPS Schema name[APPS]:

Enter the password for APPS:

Successfully connected to database MIG using APPS user.

Enter the ORACLE Application Object Library Schema name[APPLSYS]:
================================================================
CONNECT_STRING =MIG
FND_TOP =/u01/MIG/apps/prodappl/fnd/11.5.0
APPLSYS_SCHEMA =APPLSYS
APPS_SCHEMA =APPS
APPL_TOP =/u01/MIG/apps/prodappl
================================================================

Please review and press 'Y' to accept or 'N' to re-enter[Y]: Y

Performing database check...

Database check completed.

Checking required components...

Required components check completed.

Oracle Applications Tablespace Migration Utility
Main Menu

1. Migration Sizing Reports
2. Create New Tablespaces
3. Generate Migration Commands
4. Execute Migration Commands
5. Run Migration Status Reports
6. Run Post Migration Steps
7. Run Customization Steps
8. Run Migration in Batch Mode

[Q]uit [N]ext

Please enter your option - 1

Migration Sizing Reports

These reports are provided to help you gauge the space requirements for the new Tablespaces. Additionally, they will also help you determine the type of migration approach that best suits your needs

1. Generate a Report with the list of all the Oracle Application product schemas that can be migrated
2. Calculate total space required by each new tablespace to migrate all Oracle Application product schemas (relevant for a complete migration)
3. Calculate total space required by each new tablespace to migrate each Oracle Application product schema (relevant for a schema-by-schema migration)
4. Calculate total space required by each Oracle Applications schema, with details for each object
5. Display Sizing Exception report

[Q]uit [B]ack [N]ext

Please enter your option - 1

Migration Progress Report
Report Date : February 14, 2008 PAGE: 1
Total generated % commands
Schema commands successfully executed
--------------- --------------- -----------------------------------------
ABM 0 0%
AHL 0 0%
AHM 0 0%
AK 0 0%
ALR 0 0%
AMF 0 0%
………………………
…………………………
………………….
XNB 0 0%
XNC 0 0%
XNI 0 0%
XNM 0 0%
XNP 0 0%
XNS 0 0%
XTR 0 0%
ZFA 0 0%
ZPB 0 0%
ZSA 0 0%
ZX 0 0%

Report created /u01/MIG/apps/prodappl/admin/mig/log/fndtrep0.txt

Press Return key to continue...

Migration Sizing Reports

These reports are provided to help you gauge the space requirements for the new Tablespaces. Additionally, they will also help you determine the type of migration approach that best suits your needs

1. Generate a Report with the list of all the Oracle Application product schemas that can be migrated
2. Calculate total space required by each new tablespace to migrate all Oracle Application product schemas (relevant for a complete migration)
3. Calculate total space required by each new tablespace to migrate each Oracle Application product schema (relevant for a schema-by-schema migration)
4. Calculate total space required by each Oracle Applications schema, with details for each object
5. Display Sizing Exception report

[Q]uit [B]ack [N]ext

Please enter your option - 2
Sizing Program has never been run.

Enter Uniform Extent Size for the Tablespaces in KBytes[1024]:
Executing the Sizing program for all schemas. This may take upto 20min. Please wait...
Sizing program executed successfully.
PAGE: 1
Summary Report-Amount of space by tablespace
Report Date : February 14, 2008
Last Sizing Run Date : February 14, 2008
Tablespace Extent Management - Local
Allocation type -Uniform Extents<1024kb>

Current space
Recommended taken up by
Estimated space space in KB existing
Tablespace Name required in KB (20% Buffer) objects in KB
------------------------------ ---------------- --------------- ---------------------------------------
APPS_TS_ARCHIVE 6,228,992 7,474,791 2,061,240
APPS_TS_INTERFACE 15,163,392 18,196,071 11,089,784
APPS_TS_MEDIA 3,638,272 4,365,927 3,570,144
APPS_TS_NOLOGGING 662,528 795,034 342,200
APPS_TS_QUEUES 3,369,984 4,043,981 2,825,328
APPS_TS_SEED 7,327,744 8,793,293 2,129,744
APPS_TS_SUMMARY 6,267,904 7,521,485 1,135,208
APPS_TS_TX_DATA 61,418,496 73,702,196 50,858,192
APPS_TS_TX_IDX 66,878,464 80,254,157 45,371,752
------------------------------------- --------------- ------------------------------------------------
Total (in KB): 170,955,776 205,146,935 119,383,592

Report created /u01/MIG/apps/prodappl/admin/mig/log/fndtrep1.txt

Report created /u01/MIG/apps/prodappl/admin/mig/log/fndtrep1.txt

Press Return key to continue...

Migration Sizing Reports

These reports are provided to help you gauge the space requirements for the new Tablespaces. Additionally, they will also help you determine the type of migration approach that best suits your needs

1. Generate a Report with the list of all the Oracle
Application product schemas that can be migrated
2. Calculate total space required by each new tablespace to migrate all Oracle Application product schemas (relevant) for a complete migration)
3. Calculate total space required by each new tablespace to migrate each Oracle Application product schema (relevant for a schema-by-schema migration)
4. Calculate total space required by each Oracle Applications schema, with details for each object
5. Display Sizing Exception report

[Q]uit [B]ack [N]ext

Please enter your option - 2

Sizing Program was last run on 14-FEB-08
Do you want to run the Sizing program again before running the report[N]: Y

PAGE: 1
Summary Report-Amount of Space by Schema by Object
Report Date : February 15, 2008
Last Sizing Run Date : February 15, 2008
Tablespace Extent Management - Local
Allocation type -Uniform Extents<1024kb>

Object Estimated Space Sizing
Schema Name Required (in KB) Errors
-------------------- ------------------------------ ---------------- ------------
ABM ABM_VIEW_SEC_OBJS_U2 1,024 No Error
ABM_CALC_TMPLTS_TL_PK 1,024 No Error
ABM_CALC_TMPLT_VARS_TL_PK 1,024 No Error
ABM_CURRS_TL_PK 1,024 No Error
ABM_IMP_ENT_TYPES_TL_PK 1,024 No Error
ABM_IMP_TAGS_TL_PK 1,024 No Error
ABM_IMP_TAG_SETS_TL_PK 1,024 No Error
ABM_REP_TMPLTS_TL_PK 1,024 No Error
ABM_BOR_WIZ_CHILD_RES_TREE_PK 1,024 No Error
ABM_API_TEMPLATES_PK 1,024 No Error
ABM_API_TEMPLATE_ATTRIBUTES_PK 1,024 No Error
ABM_NAV_STEPS_PK 1,024 No Error
ABM_NAV_STEPS_U1 1,024 No Error
ABM_IMP_TAGS 1,024 No Error
ABM_IMP_TAG_ENTS 1,024 No Error
ABM_IMP_TAG_SETS 1,024 No Error
ABM_IMP_UOM_CV_RULES 1,024 No Error
ABM_LAUNCHPAD_METADATA 1,024 No Error
ABM_MAP_BASES 1,024 No Error
ABM_MAP_EXPTN_REP 1,024 No Error
ABM_MAP_FORM_LOG 1,024 No Error
ABM_MAP_FORM_MASTERS 1,024 No Error
ABM_MAP_RULE_SETS 1,024 No Error
ABM_MAT_UNIT_COST 1,024 No Error
******************** ----------------
Total (in KB) : 424,960

PAGE: 2
Summary Report-Amount of Space by Schema by Object
Report Date: February 15, 2008
Last Sizing Run Date: February 15, 2008
Tablespace Extent Management - Local
Allocation type -Uniform Extents<1024kb>

Migration Sizing Reports

These reports are provided to help you gauge the space requirements for the new Tablespaces. Additionally, they will also help you determine the type of migration approach that best suits your needs

1. Generate a Report with the list of all the Oracle Application product schemas that can be migrated
2. Calculate total space required by each new tablespace to migrate all Oracle Application product schemas (relevant for a complete migration)
3. Calculate total space required by each new tablespace to migrate each Oracle Application product schema (relevant for a schema-by-schema migration)
4. Calculate total space required by each Oracle Applications schema, with details for each object
5. Display Sizing Exception report

[Q]uit [B]ack [N]ext

Please enter your option - 5

Enter the Schema name[%]:
Running Exception Report ..............

There are no objects in errors

Report created /u01/MIG/apps/prodappl/admin/mig/log/fndtrep5.txt
Press Return key to continue...

Oracle Applications Tablespace Migration Utility
Main Menu

1. Migration Sizing Reports
2. Create New Tablespaces
3. Generate Migration Commands
4. Execute Migration Commands
5. Run Migration Status Reports
6. Run Post Migration Steps
7. Run Customization Steps
8. Run Migration in Batch Mode

[Q]uit [N]ext

Please enter your option - 2
Create New Tablespaces

1. Generate new tablespace creation script
2. Create new tablespaces
[Q]uit [B]ack [N]ext

Please enter your option - 1
*****************************************************************
The utility will append a sequence number to the tablespace name
and a .dbf extension to generate the datafile names.
Datafile size should not be greater than OS file size limit.
Please edit the generated script to change the file name/size
*****************************************************************
Enter the Extent Allocation type A(utoallocate) or U(niform Extent Size)[U]: U

Enter Uniform Extent Size for the Tablespaces in KBytes[1024]:

Enter the absolute path for the datafiles directory: /u02/MIG/dbf
Enter the Number of Datafiles for APPS_TS_TX_DATA tablespace[1]: 10
Enter the Datafile Size for APPS_TS_TX_DATA tablespace (MB): 2000
Enter the Number of Datafiles for APPS_TS_TX_IDX tablespace[1]: 10
Enter the Datafile Size for APPS_TS_TX_IDX tablespace (MB): 2000
Enter the Number of Datafiles for APPS_TS_SEED tablespace[1]: 2
Enter the Datafile Size for APPS_TS_SEED tablespace (MB): 2000
Enter the Number of Datafiles for APPS_TS_INTERFACE tablespace[1]: 5
Enter the Datafile Size for APPS_TS_INTERFACE tablespace (MB): 2000
Enter the Number of Datafiles for APPS_TS_SUMMARY tablespace[1]: 5
Enter the Datafile Size for APPS_TS_SUMMARY tablespace (MB): 2000
Enter the Number of Datafiles for APPS_TS_NOLOGGING tablespace[1]: 2
Enter the Datafile Size for APPS_TS_NOLOGGING tablespace (MB): 1000
Enter the Number of Datafiles for APPS_TS_ARCHIVE tablespace[1]: 7
Enter the Datafile Size for APPS_TS_ARCHIVE tablespace (MB): 1000
Enter the Number of Datafiles for APPS_TS_QUEUES tablespace[1]: 5
Enter the Datafile Size for APPS_TS_QUEUES tablespace (MB): 1000
Enter the Number of Datafiles for APPS_TS_MEDIA tablespace[1]: 5
Enter the Datafile Size for APPS_TS_MEDIA tablespace (MB): 1000

Tablespace creation script /u01/MIG/apps/prodappl/admin/mig/log/crtts.sql created

/u01/MIG/apps/prodappl/admin/mig/log ***scripts is in this directory **

Press Return key to continue...

Create New Tablespaces

1. Generate new tablespace creation script
2. Create new tablespaces

[Q]uit [B]ack [N]ext
Please enter your option - 2
Creating Tablespaces. Please wait...
Connected.

PL/SQL procedure successfully completed.

Tablespace created.

Tablespace created.

Tablespace created.

Tablespace altered.

Tablespace altered.

Tablespace altered.

Tablespace altered.

Tablespace altered.

Tablespace altered.

Tablespace altered.
Tablespace altered.

Tablespaces creation script executed. Please check the log /u01/MIG/apps/prodappl/admin/mig/log/crtts20080216215009.log for errors.
Press Return key to continue...

Create New Tablespaces

1. Generate new tablespace creation script
2. Create new tablespaces

[Q]uit [B]ack [N]ext

Please enter your option - B

Oracle Applications Tablespace Migration Utility
Main Menu

1. Migration Sizing Reports
2. Create New Tablespaces
3. Generate Migration Commands
4. Execute Migration Commands
5. Run Migration Status Reports
6. Run Post Migration Steps
7. Run Customization Steps
8. Run Migration in Batch Mode

[Q]uit [N]ext

Please enter your option - 3

Generate Migration Commands
Generation of Migration commands including disable/enable
commands for triggers, constraints, policies, stop/start for queues.

1. Invalid Indexes Report. Please correct/drop these before
generating migration commands
2. Generate migration commands for all schemas
3. Generate migration commands for a list of schemas

[Q]uit [B]ack [N]ext

Please enter your option - 1

Report created /u01/MIG/apps/prodappl/admin/mig/log/fndinvld.txt

Press Return key to continue...
Press Return key to continue...

Generate Migration Commands
Generation of Migration commands including disable/enable
commands for triggers, constraints, policies, stop/start for queues.

1. Invalid Indexes Report. Please correct/drop these before generating migration commands
2. Generate migration commands for all schemas
3. Generate migration commands for a list of schemas

[Q]uit [B]ack [N]ext

Please enter your option - 2

Generating Migration commands for all schemas. This may take upto 30min. Please wait...

Command generation successful. Please check the log /u01/MIG/apps/prodappl/admin/mig/log/fndgmcmd20080216224419.log

Press Return key to continue...

Generate Migration Commands
Generation of Migration commands including disable/enable
commands for triggers, constraints, policies, stop/start for queues.

1. Invalid Indexes Report. Please correct/drop these before generating migration commands
2. Generate migration commands for all schemas
3. Generate migration commands for a list of schemas

[Q]uit [B]ack [N]ext

Please enter your option - 2

Generating Migration commands for all schemas. This may take upto 30min. Please wait...

Command generation successful. Please check the log /u01/MIG/apps/prodappl/admin/mig/log/fndgmcmd20080216224419.log

Press Return key to continue...

Generate Migration Commands
Generation of Migration commands including disable/enable
commands for triggers, constraints, policies, stop/start for queues.

1. Invalid Indexes Report. Please correct/drop these before
generating migration commands
2. Generate migration commands for all schemas
3. Generate migration commands for a list of schemas

[Q]uit [B]ack [N]ext

Please enter your option - B

Oracle Applications Tablespace Migration Utility
Main Menu

1. Migration Sizing Reports
2. Create New Tablespaces
3. Generate Migration Commands
4. Execute Migration Commands
5. Run Migration Status Reports
6. Run Post Migration Steps
7. Run Customization Steps
8. Run Migration in Batch Mode

[Q]uit [N]ext

Please enter your option - 4

Execute Migration Commands
Execution of Migration commands including disable
commands for triggers constraints, stop/start for queues.

PLEASE TAKE A COMPLETE BACKUP OF THE DATABASE BEFORE MIGRATION

1. Migrate all Schemas
2. Migrate a list of Schemas
3. Migrate CTXSYS Schema

Note: Migrate CTXSYS schema when no other migration process is in progress.

[Q]uit [B]ack [N]ext

Please enter your option - 1

Are you sure you want to migrate all schemas[N]: Y
Enter the maximum number of parallel processes for MIG[8]:

Starting the Migration process for all schemas. Please wait...

Migration processes for tables with LONG and LONG RAW columns started in the background. Please monitor the log file /u01/MIG/apps/prodappl/admin/mig/log/fndmlong20080216230605.log for errors and completion of this migration process.

Sequential migration process started in the background for MIG. Please monitor the log file /u01/MIG/apps/prodappl/admin/mig/log/fndemseq20080216230606.log for errors and completion of this migration process.

Parallel migration processes started in the background for MIG. Please monitor the log file /u01/MIG/apps/prodappl/admin/mig/log/fndemcmd20080216230622.log for errors and completion of this migration process.

OATM Utility processes are running in the background. sql*plus sessions and one JRE session are spawned in the background. You can monitor those sessions from the OS. Please do not kill any of those sessions as it will adversely affect migration process and result in errors. Monitor migration by running migration progress report.

Press Return key to return to the menu...

Press Return key to continue...

Run Post Migration Steps

1. Run audit report
2. Enable constraints/triggers/policies & start queues
3. Resize old tablespaces
4. Generate script to drop empty tablespaces

Note: Please complete refresh all the Materialized Views
in Oracle Applications before using the system.

[Q]uit [B]ack

Please enter your option - 2

Enter a comma separated list of Schema names[%]:

Enabling Constraints/triggers/policies and starting queues. Please wait...

All constraints/trigger/policies are enabled and queues started

Press Return key to continue...

Run Post Migration Steps

1. Run audit report
2. Enable constraints/triggers/policies & start queues
3. Resize old tablespaces
4. Generate script to drop empty tablespaces

Note: Please complete refresh all the Materialized Views
in Oracle Applications before using the system.

[Q]uit [B]ack

Please enter your option - 4
+=======================================================================+
Warning: Please ensure you do not have any residual data segments
in the tablespaces attempted to be dropped to avoid irrevocable
loss of data.
+=======================================================================+

Drop empty tablespace script /u01/MIG/apps/prodappl/admin/mig/log/fndtsdrp.sql has been created.

Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @fndtsdrp.sql;

Tablespace dropped.

Tablespace dropped.
Tablespace dropped.

Tablespace dropped.

Tablespace dropped.

SQL> commit;

Commit complete.

OATM How to move objects left in the old tablespace after oatm migration?

Solution
1) Run the 'Migration Error Report' and correct the errors that cause the migration to fail.

2) Make sure that queue 'TBLMIG_MESSAGEQUE' is started

select NAME, ENQUEUE_ENABLED, DEQUEUE_ENABLED from dba_queues where owner ='SYSTEM' and name = 'TBLMIG_MESSAGEQUE' ;

In case the queue is not started, run from sqlplus as the system user:

exec dbms_aqadm.start_queue('SYSTEM.TBLMIG_MESSAGEQUE');

3) Run the migration command again and the migration utility will try to move the objects which are still in the old tablespaces

Drop SWALLACE and SPOTLIGHT USERS

drop user spotlight cascade;
drop user swallace cascade;

Note:430604.1
CREATE TEXT INDEX DRG-11446 DROLDUS.DAT NOT INSTALLED

PATCH 4575748 OATM RE-SIZE OLD TABLESPACES DOES NOT RESIZE DATAFILES

IMPORTANT NOTE :

One-off patches are not fully certified by all Oracle products, and so there is some risk of unexpected side effects. If the fix in this patch is included in the latest released ATG Family Packs and/or ATG PF Consolidated Updates (CU), then it is highly recommended to upgrade to latest released ATG Family Pack or ATG PF Consolidated Update (CU) that is available in Recommended Patch List (Metalink Note 123456.1). It is also recommended to upgrade to latest released ATG Family Pack or ATG PF Consolidated Update (CU) before applying this patch.

This patch provides implementation that will correctly resize database file after migration is done

ERROR resolution

SQL> @irctxido1.sql HR APPLSYS APPS CTXSYS

PL/SQL procedure successfully completed.

Commit complete.

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
applprod@vezora1:/u01/MIG/apps/prodappl/per/11.5.0/patch/115/sql

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @irctxipt HR APPLSYS APPS CTXSYS

PL/SQL procedure successfully completed.

Commit complete.

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

applprod@vezora1:/u01/MIG/apps/prodappl/per/11.5.0/patch/115/sql

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @peredind.sql HR APPLSYS APPS CTXSYS

PL/SQL procedure successfully completed.

Commit complete.

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
applprod@vezora1:/u01/MIG/apps/prodappl/per/11.5.0/patch/115/sql

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @ibcinctx.sql

PL/SQL procedure successfully completed.

Commit complete.
SQL*Plus: Release 8.0.6.0.0 - Production on Mon Feb 18 19:26:35 2008

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @icxintm2.sql icx icx CTXSYS
DECLARE
*
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-10502: index ICX_QUES_CTX does not exist
DRG-13201: KOREAN_LEXER is desupported
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 364
ORA-06512: at "SYS.DBMS_SYS_SQL", line 909
ORA-06512: at "SYS.DBMS_SQL", line 39
ORA-06512: at line 31

HACK THE USER SEE SCRIPTS

applprod@vezora1:/u01/MIG/apps/prodappl/icx/11.5.0/patch/115/sql

SQL*Plus: Release 8.0.6.0.0 - Production on Mon Feb 18 19:29:25 2008

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @jtfiimt.sql jtf jtf
ERROR:
ORA-01017: invalid username/password; logon denied

HACK THE USER SEE SCRIPTS

applprod@vezora1:/u01/MIG/apps/prodappl/jtf/11.5.0/patch/115/sql

Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @amviimt.sql amv amv

PL/SQL procedure successfully completed.
Grant succeeded.
Grant succeeded.
Grant succeeded.
DECLARE
*
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-10701: preference AMV.KOREAN_LEXER already exists
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_DDL", line 26
ORA-06512: at line 76

CHECK ISSUE

applprod@vezora1:/u01/MIG/apps/prodappl/amv/11.5.0/patch/115/sql

POST MIGRATION

1) APPLSPE

OWNER SEGMENT_NAME SEGMENT_TYPE
SYS 17.22 SPACE HEADER

SQL> alter tablespace APPLSPE offline;

Tablespace altered.

SQL> drop tablespace APPLSPE including contents and datafiles cascade constraints;

Tablespace dropped.

2) AMVD

select table_name, column_name, tablespace_name, segment_name from dba_lobs
where tablespace_name = 'CSD';

alter table cs.DR$CS_INCIDENTS_ALL_TL_N1$I move lob(token_info) store as (tablespace APPS_TS_TX_DATA);

alter table cs.DR$CS_INCIDENTS_ALL_TL_N1$R move lob(data) store as (tablespace APPS_TS_TX_DATA);

alter table cs.DR$SUMMARY_CTX_INDEX$I move lob(token_info) store as (tablespace APPS_TS_TX_DATA);

alter table cs.DR$SUMMARY_CTX_INDEX$R move lob(data) store as (tablespace APPS_TS_TX_DATA);

select OWNER, INDEX_NAME, INDEX_TYPE, TABLE_NAME,TABLESPACE_NAME
from DBA_INDEXES
where INDEX_TYPE LIKE 'IOT%'
and TABLESPACE_NAME = 'CSD';

OWNER INDEX_NAME INDEX_TYPE TABLE_NAME TABLESPACE_NAME
CS SYS_IOT_TOP_2516234 IOT - TOP DR$CS_INCIDENTS_ALL_TL_N1$K CSD
CS SYS_IOT_TOP_2516196 IOT - TOP DR$SUMMARY_CTX_INDEX$K CSD
CS SYS_IOT_TOP_2516249 IOT - TOP DR$CS_INCIDENTS_ALL_TL_N1$N CSD
CS SYS_IOT_TOP_2516231 IOT - TOP DR$SUMMARY_CTX_INDEX$N CSD

3) CTXD

select table_name, column_name, tablespace_name, segment_name from dba_lobs
where tablespace_name = 'CTXD';

alter table ctxsys.DR$PART_STATS_PRE10I move lob(statistics) store as (tablespace APPS_TS_TX_DATA);

alter table ctxsys.DR$STATS_PRE10I move lob(statistics) store as (tablespace APPS_TS_TX_DATA);

alter table ctxsys.DR$NVTAB move lob(val) store as (tablespace APPS_TS_TX_DATA); ISSUE !!

4) APPLSYSX

select table_name, column_name, tablespace_name, segment_name from dba_lobs
where tablespace_name = 'APPLSYSX';

no rows selected

select OWNER, INDEX_NAME, INDEX_TYPE, TABLE_NAME,TABLESPACE_NAME
from DBA_INDEXES
where INDEX_TYPE LIKE 'IOT%'
and TABLESPACE_NAME = ' APPLSYSX';

no rows selected

---------------------------------------------
alter table AQ$_WF_CONTROL_D move lob(data) store as (tablespace APPS_TS_TX_DATA)
*
ERROR at line 1:
ORA-08108: may not build or rebuild this type of index online

Procedures to Remove Orphan AQ Objects which Fail to Drop via DBMS_AQADM Note:236898.1

DBMS_AQADM.DROP_QUEUE_TABLE(queue_table => 'APPLSYS.AQ$_WF_CONTROL_D');

OATM migration leaves WF_CONTROL objects in the old tablespace Note:418238.1

Solution
1.First stop WF related services like WF Mailer Agent, WF listener, etc.

2.Then run following SQL :
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfctqrec.sql apps/apps

(This script should recreate the WF_CONTROL queue) PROBLEM

Migration of 02-March 2008

1) APPLSYSX

select OWNER, INDEX_NAME, INDEX_TYPE, TABLE_NAME,TABLESPACE_NAME from DBA_INDEXES where INDEX_TYPE LIKE 'IOT%' and TABLESPACE_NAME = 'APPLSYSX';

OWNER INDEX_NAME INDEX_TYPE TABLE_NAME TABLESPACE_NAME

APPLSYS SYS_IOT_TOP_2516161 IOT - TOP DR$FND_LOBS_CTX$N APPLSYSX
APPLSYS SYS_IOT_TOP_2516156 IOT - TOP DR$FND_LOBS_CTX$K APPLSYSX

Alter table APPLSYS.DR$FND_LOBS_CTX$N move tablespace APPS_TS_QUEUES;
Alter table APPLSYS. DR$FND_LOBS_CTX$K move tablespace APPS_TS_QUEUES;

2) APPLSYSD

SQL> select segment_name, segment_type from dba_segments where tablespace_name ='APPLSYSD';

SEGMENT_NAME SEGMENT_TYPE

AD_FRAGMENT_REPORT TABLE
FND_LOBS TABLE
SYS_IL0000076155C00004$$ LOBINDEX
SYS_LOB0000076155C00004$$ LOBSEGMENT
18.51829 SPACE HEADER

select OWNER, TABLE_NAME, SEGMENT_NAME from dba_lobs where SEGMENT_NAME like 'AD_FRAGMENT_REPORT';

select OWNER, TABLE_NAME, SEGMENT_NAME from dba_lobs where SEGMENT_NAME like 'SYS_IL0000076155C00004$$';

select OWNER, TABLE_NAME, SEGMENT_NAME from dba_lobs where SEGMENT_NAME like 'SYS_LOB0000076155C00004$$';

OWNER TABLE_NAME SEGMENT_NAME
APPLSYS FND_LOBS SYS_LOB0000076155C00004$$

select OWNER, TABLESPACE_NAME from dba_tables where TABLE_NAME like 'FND_LOBS';

OWNER TABLESPACE_NAME
----------------------------------------------------------- ------------------------------
APPLSYS APPS_TS_TX_DATA

select OWNER, TABLESPACE_NAME from dba_tables where TABLE_NAME like 'AD_FRAGMENT_REPORT';

OWNER TABLESPACE_NAME
--------------------------------------------------------------------- ------------------------------
SYSTEM APPLSYSD
APPS APPS_TS_TX_DATA

alter table system.AD_FRAGMENT_REPORT move tablespace APPS_TS_TX_DATA;

Table altered.

3) APPLSYSX

select segment_name, segment_type from dba_segments where tablespace_name ='APPLSYSX';

SEGMENT_NAME SEGMENT_TYPE

FND_LOBS_U1 INDEX
19.38358 SPACE HEADER

alter index APPLSYS.FND_LOBS_U1 rebuild tablespace APPS_TS_TX_IDX;
alter tablespace APPLSYSX offline;
drop tablespace APPLSYSX including contents and datafiles cascade constraints;

4) SCSX

select segment_name, segment_type from dba_segments where tablespace_name ='SCSX';

SEGMENT_NAME SEGMENT_TYPE
384.14 SPACE HEADER

alter tablespace SCSX offline;
drop tablespace SCSX including contents and datafiles cascade constraints;

5) APPLSCS

select segment_name, segment_type from dba_segments where tablespace_name ='APPLSCS';

SEGMENT_NAME SEGMENT_TYPE
16.72 SPACE HEADER

alter tablespace APPLSCS offline;
drop tablespace APPLSCS including contents and datafiles cascade constraints;

6) CTXD

select segment_name, segment_type from dba_segments where tablespace_name ='CTXD';

SEGMENT_NAME SEGMENT_TYPE
37.1161 SPACE HEADER

SQL> alter tablespace CTXD offline;
Tablespace altered.
SQL> drop tablespace CTXD including contents and datafiles cascade constraints;

MIGRATION 09/03/2008

APPLSYSD

select segment_name, segment_type from dba_segments where tablespace_name ='APPLSYSD';

SEGMENT_NAME SEGMENT_TYPE

AD_FRAGMENT_REPORT TABLE
FND_LOB TABLE

DR$FND_LOBS_CTX$ TABLE
DR$FND_LOBS_CTX$R TABLE
SYS_IL0000076155C00004$$ LOBINDEX
SYS_IL0002516153C00006$$ LOBINDEX
SYS_IL0002516158C00002$$ LOBINDEX
SYS_LOB0000076155C00004$$ LOBSEGMENT
SYS_LOB0002516158C00002$$ LOBSEGMENT
SYS_LOB0002516153C00006$$ LOBSEGMENT

18.51829 SPACE HEADER

11 rows selected.

select OWNER, TABLE_NAME, SEGMENT_NAME from dba_lobs where SEGMENT_NAME like 'SYS_LOB0000076155C00004$$';

OWNER TABLE_NAME SEGMENT_NAME
APPLSYS FND_LOBS SYS_LOB0000076155C00004$$

select OWNER, TABLESPACE_NAME from dba_tables where TABLE_NAME like 'FND_LOBS';

OWNER TABLESPACE_NAME
APPLSYS APPLSYSD

SQL> select OWNER, TABLESPACE_NAME from dba_tables where TABLE_NAME like 'AD_FRAGMENT_REPORT';

OWNER TABLESPACE_NAME
SYSTEM APPLSYSD
APPS APPS_TS_TX_DATA

Alter table AD_FRAGMENT_REPORT move tablespace apps_ts_tx_data;

Table altered.

Alter table applsys.FND_LOBS move tablespace apps_ts_tx_data;

Table altered.

Alter table applsys.DR$FND_LOBS_CTX$R move tablespace apps_ts_tx_data;

Table altered.

Alter table applsys.DR$FND_LOBS_CTX$I move tablespace apps_ts_tx_data;

Table altered.

Alter table sys.AD_FRAGMENT_REPORT move tablespace apps_ts_tx_data;
APPLSYSX

select segment_name, segment_type from dba_segments where tablespace_name ='APPLSYSX';

SEGMENT_NAME SEGMENT_TYPE

FND_LOBS_U1 INDEX

SYS_IOT_TOP_2516161 INDEX

SYS_IOT_TOP_2516156 INDEX

DR$FND_LOBS_CTX$X INDEX

19.38358 SPACE HEADER

alter index APPLSYS.FND_LOBS_U1 rebuild tablespace APPS_TS_TX_IDX;
Index altered.

alter index applsys.DR$FND_LOBS_CTX$X rebuild tablespace APPS_TS_TX_IDX;

Index altered.

select OWNER, INDEX_NAME, INDEX_TYPE, TABLE_NAME,TABLESPACE_NAME from DBA_INDEXES where INDEX_TYPE LIKE 'IOT%' and TABLESPACE_NAME = 'APPLSYSX';

OWNER INDEX_NAME INDEX_TYPE TABLE_NAME TABLESPACE_NAME

APPLSYS SYS_IOT_TOP_2516161 IOT - TOP DR$FND_LOBS_CTX$N APPLSYSX
APPLSYS SYS_IOT_TOP_2516156 IOT - TOP DR$FND_LOBS_CTX$K APPLSYSX

Alter table APPLSYS.DR$FND_LOBS_CTX$N move tablespace APPS_TS_TX_IDX;

Alter table APPLSYS. DR$FND_LOBS_CTX$K move tablespace APPS_TS_TX_IDX;

select segment_name, segment_type from dba_segments where tablespace_name ='APPLSYSX';

SEGMENT_NAME SEGMENT_TYPE
19.38358 SPACE HEADER

SQL> alter tablespace APPLSYSX offline;

Tablespace altered.

SQL> drop tablespace APPLSYSX including contents and datafiles cascade constraints;

Tablespace dropped.

2010-02-03T13:26:00.001Z

Installing Informatica Power Center 8.6.0 on Linux Redhat 4

2009-08-12T21:54:00.003+01:00

Basic install of OBIEE on Linux Redhat AS4 update 5

2009-08-12T21:49:00.003+01:00

Indian Payroll Localization Patchset Implementation

2009-08-09T01:42:00.001+01:00

OVERVIEW
This paper presents a step-by-step approach for completely application of the patches for the Indian payroll

Patch_dir=/stage/patches
Indian Payroll dir = /stage/IN_Localization
Target_server= Linux Redhat AS 4.5
Target_datbase= Oracle 9.2.0.8

INSTALL THE INDIAN PATCH TOOL
Steps to apply Patch 5498551 :
1. Copy 5498551.zip to $JA_TOP
2. Unzip the patch 5498551 using : unzip 5498551.zip
3. Download the Patch Application Tool ( Patch 5458248 ). (This replaces the earlier tool with Patch 5393004)
4. Copy the 5393004.zip to $JA_TOP.
5. Unzip the patch 5393004 ( using command : unzip 5393004.zip ) which creates a directory inpatch in $JA_TOP.
6. Change directory to $JA_TOP/inpatch
7. Install the patch using : perl install.pl appspwd= japwd=
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/inpatch $ perl install.pl appspwd=xxk3ia japwd=ja
Applied jai_create_table.sql successfully.
Applied jai_create_synonym.sql successfully.
Applied jai_get_obj_ver_f.sql successfully.
Patch Application Tool installed successfully.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/inpatch

Now apply the below patch

8. In step 7 once the patch application tool is successfully installed then change directory to $JA_TOP/5498551
9. Refer readme of Patch 5498551. Issue the patch application command relevant to your Oracle Applciations Installation ( to know more refer two documents - a. "User_Manual.txt" in $JA_TOP/inpatch directory b. Metalink )
The command would be something similar to what is given below :
perl $JA_TOP/inpatch/indpatch.pl drvr_file=5498551.drv fnd_patchset= appspwd= japwd= mode=
where and are passwords for APPS and JA user
if your FND patchset is 11i.FND.H then is H.
is required if your have different tiers F- Forms tier, C-Concurrent , D-Database
10. On patch application you will get logs generated at $JA_TOP/$APPLLOG/5498551. In case of patch failures please refer Metalink for log details.

See the log file in /stage/IN_Localization5498551_output.log

PATCH 5498551 - INDIA LOCALIZATION CUMULATIVE PATCHSET IN60107
This Patch should be applied on the TEST instance first, perform rigorous test cycles,
after you are satisfied with the result of the cycles, apply this patch on the PRODUCTION
Instance.

Never apply it directly on the Production instance without applying on the test.

Go through the following sections and understand them thoroughly before
proceeding to apply the patch.
- Pre-requisites
- Automated Patch Application Steps and
- Post-Patch Application Steps

PRE-REQUISITES
1. This patchset is for Oracle Applications Releases from 11.5.3 to 11.5.10CU2, but only with FND patchset C or above.
Customers at any level of India Localization ( say , for example , IN60102 or IN60105D2 or IN60106 ) can DIRECTLY APPLY this patch.
2. Take a cold backup of the database before applying the patch.
3. The patch is 'India Localization Patch Tool' compliant. Please download the tool ( Patch # 5458248 ) and apply this patch .
This patch is NOT ADPATCH compliant and requires India Localization Patch Tool for application of this patch.

This patch should NOT BE applied MANUALLY.

Please refer to Metalink Note # 376756.1 for details about India Localization Patch Application Tool.

You would find many patches of India Localization which are not patch tool compliant.
These patches need to be applied as per instructions in the readme only if you have not applied Cumulative Patchset IN60107.

4. UNIX Server disk space required for this localization patchset files: 70 MB.

5. Ensure that enough free space exists in data files to create various database objects like tables, indexes etc. The data file should have at least 100MB free space and the index file should have at least 50MB free space.
Additional space should be allocated for data growth in all these files. The schema in which the tables/indexes are created is "JA". So check for related data files.

6. Ensure to have a rollback segment of at least 30MB and it is online.

7. Check if DBMS_SUPPORT package is present in your APPS schema by using the below query in APPS schema :
select object_name, object_type from all_objects where object_name = 'DBMS_SUPPORT' and object_type like 'PACKAGE%' ;

Okay package exists

If the above query does not return both DBMS_SUPPORT package and package body, create them using :
sqlplus apps/apps @$ORACLE_HOME/rdbms/admin/dbmssupp.sql
applprod@vezora3:/stage/IN_Localization/5498551 $ sqlplus apps/k3ob3ia
SQL*Plus: Release 8.0.6.0.0 - Production on Thu Jul 17 15:22:46 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> @ja_chk_stat.sql;
***************************************************************************************************
This log contains various checks to see if all the pre-requisites for India Localization patchset application are
satisfied. If any errors are found, please DO NOT PROCEED with India Localization patchset and contact India
Localziation Support with this log file.
***************************************************************************************************
This log contains various checks to see if all the pre-requisites for India Localization patchset application are
satisfied. If any errors are found, please DO NOT PROCEED and contact India Localziation Support with this log file.
***************************************************************************************************
==============================================================
Checking whether JA is installed or not and the Apps Release..
==============================================================

APPLICATION_ID
--------------
7000

1 row selected.

If the above query returned 0 rows, please DO NOT PROCEED and contact India Localization support.

RELEASE_NAME
--------------------------------------------------
11.5.10.2
1 row selected.
============================================================
Checking whether all the Base responsibilities exist or not..
============================================================
RESPONSIBILITY_NAME
----------------------------------------------------------------------------------------------------
Fixed Assets Manager
Inventory
Order Management Super User
Payables Manager
Purchasing Super User
Receivables Manager

6 rows selected.

If the above query returned less than 6 rows, please DO NOT PROCEED and contact India Localization support.

RESPONSIBILITY_KEY RESPONSIBILITY_NAME
------------------------------ ----------------------------------------------------------------------------------------------------
FIXED_ASSETS_MANAGER Fixed Assets Manager
INVENTORY Inventory
ORDER_MGMT_SUPER_USER Order Management Super User
PAYABLES_MANAGER Payables Manager
PURCHASING_SUPER_USER Purchasing Super User
RECEIVABLES_MANAGER Receivables Manager

6 rows selected.
==============================================================================
Checking whether Attributes 1 thru 5, 14 and 15 are in use by Global Data Elements..
==============================================================================
This Check is mandatory since India Localization patchset installation scripts will delete any previous registrations
of attributes 1 thru 5, 14 and 15 with Global Data Elements in the DFFs AP_INVOICES, AP_INVOICE_DISTRIBUTIONS,
FA_ADDITIONS, FA_MASS_ADDITIONS, FND_COMMON_LOOKUPS, MTL_SYSTEM_ITEMS, PER_ORGANIZATION_UNITS, RCV_TRANSACTIONS,
RCV_SHIPMENT_HEADERS, PO_LOOKUP_CODES.
The Customer must move the data to another attribute not in (1-5,14,15) since the above mentioned attributes are
required by India Localization product. Please refer to User Manual for details.

no rows selected

If the above query returned any rows, then please DO NOT PROCEED with India Localization patchset unless you migrate the data attached to that particular attribute to another attribute not in (1-5,14,15).

8. Run the ja_chk_stat.sql in 5498551 directory.
sqlplus apps/ @ja_chk_stat.sql
Refer the log prechecks_5498551.log. Only proceed if the log file does not show any issues.
applprod@vezora3:/stage/IN_Localization/5498551 $ sqlplus apps/k3ob3ia
SQL*Plus: Release 8.0.6.0.0 - Production on Thu Jul 17 15:26:30 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production

SQL> @ja_chk_stat.sql
***************************************************************************************************
This log contains various checks to see if all the pre-requisites for India Localization patchset application are
satisfied. If any errors are found, please DO NOT PROCEED with India Localization patchset and contact India
Localziation Support with this log file.
***************************************************************************************************
This log contains various checks to see if all the pre-requisites for India Localization patchset application are
satisfied. If any errors are found, please DO NOT PROCEED and contact India Localziation Support with this log file.
***************************************************************************************************
==============================================================
Checking whether JA is installed or not and the Apps Release..
==============================================================
APPLICATION_ID
--------------
7000

1 row selected.
If the above query returned 0 rows, please DO NOT PROCEED and contact India Localization support.

RELEASE_NAME
--------------------------------------------------
11.5.10.2
1 row selected.
============================================================
Checking whether all the Base responsibilities exist or not..
============================================================
RESPONSIBILITY_NAME
----------------------------------------------------------------------------------------------------
Fixed Assets Manager
Inventory
Order Management Super User
Payables Manager
Purchasing Super User
Receivables Manager

6 rows selected.

If the above query returned less than 6 rows, please DO NOT PROCEED and contact India Localization support.

RESPONSIBILITY_KEY RESPONSIBILITY_NAME
------------------------------ --------------------------------------------------------------------------------------------------
FIXED_ASSETS_MANAGER Fixed Assets Manager
INVENTORY Inventory
ORDER_MGMT_SUPER_USER Order Management Super User
PAYABLES_MANAGER Payables Manager
PURCHASING_SUPER_USER Purchasing Super User
RECEIVABLES_MANAGER Receivables Manager

6 rows selected.
==============================================================================
Checking whether Attributes 1 thru 5, 14 and 15 are in use by Global Data Elements..
==============================================================================
This Check is mandatory since India Localization patchset installation scripts will delete any previous registrations of attributes 1 thru 5, 14 and 15 with Global Data Elements in the DFFs AP_INVOICES, AP_INVOICE_DISTRIBUTIONS,
FA_ADDITIONS, FA_MASS_ADDITIONS, FND_COMMON_LOOKUPS, MTL_SYSTEM_ITEMS, PER_ORGANIZATION_UNITS, RCV_TRANSACTIONS,
RCV_SHIPMENT_HEADERS, PO_LOOKUP_CODES.
The Customer must move the data to another attribute not in (1-5,14,15) since the above mentioned attributes arerequired by India Localization product. Please refer to User Manual for details.

no rows selected

If the above query returned any rows, then please DO NOT PROCEED with India Localization patchset unless you migrate the data attached to that particular attribute to another attribute not in (1-5,14,15).

9. Ensure that the table "JA_IN_INSTALL_CHECK_INFO_D" does not exist with owner as "APPS".
The below query executed in APPS schema SHOULD NOT return any row(s) :

select owner, table_name from all_tables where table_name = 'JA_IN_INSTALL_CHECK_INFO_D' and owner = 'APPS' ;

Doesn’t exist

In case of any row returned by the above query, please follow the Metalink note # 390231.1 for resolution.

10. Ignore this step if it is a Fresh install of India Localization (or) Service Tax patch ( 4239736 ) had been already applied.

Please run the script "jai_rcv_chk_pending_delivery.sql" supplied with this patch in APPS schema as follows :
sqlplus apps/ @jai_rcv_chk_pending_delivery.sql

applprod@vezora3:/stage/IN_Localization/5498551 $ sqlplus apps/XXXXa
SQL*Plus: Release 8.0.6.0.0 - Production on Thu Jul 17 15:30:12 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> @jai_rcv_chk_pending_delivery.sql
*** NO RECEIPT PENDING FOR DELIVERY WITH SERVICE/EXCISE TAX ATTACHED EXISTS, YOU
CAN GO AHEAD WITH PATCH APPLICATION ****
PL/SQL procedure successfully completed.

Follow the directions given as output by the script.
Only if it returns the message "** NO RECEIPT PENDING FOR DELIVERY WITHSERVICE/EXCISE TAX ATTACHED EXISTS, YOU CAN GO AHEAD WITH PATCH APPLICATION ****", proceed with the rest of the steps.

In case of any other output from the above script, please follow the instructions detailed in the document "Migrate_to_Education_Cess_Service.txt" available in the "Documents" folder of this patch zip file.
AUTOMATED PATCH APPLICATION STEPS
You will need to perform the following 3 steps:
1) Extract this patch zip file to a temporary directory.
2) Change directory to 5498551.
3) Proceed as instructed in the automated patch tool user manual.

POST-PATCH APPLICATION STEPS

1. The patch application is successful if the STATUS displayed is "Patch application completed successfully."
2. For 11.5.3 customers
Run at the command prompt the following perl script :
perl dbrun_1153.pl appspwd=

3. TDS MIGRATION :
NOTE : - Migration should be done with the help of FUNCTIONAL user and the DBA alone SHOULD NOT perform migration without adequate knowledge.
- SKIP this STEP ( ie., 3. TDS MIGRATION ) if any of the below criteria is met :
a. Fresh India Localization install OR
b. Any of the below patches are applied :
- 5377690 OR- 5373375 (OLD TDS consolidated Patch) OR
- 5352145 (OLD TDS consolidated Patch) OR
- 5223033 (OLD TDS consolidated Patch) OR
- 4860026 + 4353842 (in the order given above)

For Migration of Existing Threshold Data

1. View the old Threshold Data :
Please use the following query to view the threshold data that existed before this patch application. Threshold has undergone a major change and the old data does not show up in the vendor additional info.
Threshold is no more setup for each vendor, but is defined for a specific vendor type.
Exception setups can only be assigned to specific vendor or vendor sites.
Query to view old threshold data setup for each vendor / site :

SELECT DISTINCT a.vendor_id,
a.vendor_site_id,
b.vendor_name,
DECODE(a.vendor_site_id, 0 , 'Null Site', c.vendor_site_code) "Vendor Site Code",
a.tds_section,
a.tds_amount,
decode(a.invoice_tds_flag, 'P', 'Per Invoice', 'A', 'All Invoices')
FROM ja.ja_in_vendor_tds_info_dtl a,
po_vendors b,
po_vendor_sites_all c
WHERE a.vendor_id = b.vendor_id
AND b.vendor_id = c.vendor_id
AND ( a.vendor_site_id = c.vendor_site_id OR a.vendor_site_id = 0 )

2. Apply file jai_ap_3841637_migrate_pkg_t.sql available in "misc" folder of this patch zip file using following command.

sqlplus apps/ @jai_ap_3841637_migrate_pkg_t.sql

This file creates the package that is being used in the query to validate PAN number as in step 3

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/5498551/misc $ ls
jai_ap_3841637_migrate_pkg_t.sql jai_ap_etds_4353842_mig1_apps.sql jai_ap_etds_4353842_mig2_apps.sql TDS Certificate generation.doc

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/5498551/misc $ sqlplus apps/k3ob3ia

SQL*Plus: Release 8.0.6.0.0 - Production on Thu Jul 17 16:58:55 2008
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production

SQL> @jai_ap_3841637_migrate_pkg_t.sql;
Package created.
Package body created.

3. PAN Number validation :
Vendor PAN number is of significant importance after this patch application.
Following query gives you the details of PAN number by vendor site.

SELECT DISTINCT a.vendor_id,a.vendor_site_id,b.vendor_name,
DECODE(a.vendor_site_id, 0 , 'Null Site', c.vendor_site_code) "Vendor Site Code",
a.pan_no,jai_ap_3841637_migrate_pkg_t.check_valid(a.pan_no, 10) PAN_NO_STATUS,
DECODE(a.vendor_site_id, 0, a.confirm_pan_flag, NULL) PAN_CONFIRM_FLAG
FROM ja_in_vendor_tds_info_hdr a,po_vendors b,po_vendor_sites_all c
WHERE a.vendor_id = b.vendor_id
AND b.vendor_id = c.vendor_id
AND (a.vendor_site_id = c.vendor_site_id OR a.vendor_site_id = 0 )

4. Execute the below SQL command in APPS schema :
DROP PACKAGE JAI_AP_3841637_MIGRATE_PKG_T ;

Steps 5 and 6 are required only if you find discrepancies in PAN No and PAN Confirm Flag as a result of output of step 3 above.

5. Update Script for PAN no for a vendor / site :

The following script can be used to update the PAN number for all sites (input null for vendor site) or a specific site.

UPDATE ja_in_vendor_tds_info_hdr
SET pan_no = '&New_PAN_NO'
WHERE vendor_id = &vendor_id
AND vendor_site_id = NVL(&vendor_Site_ID, vendor_site_id);

6. Update script for Confirm PAN flag :

The following script can be used to set the value of confirm_pan_flag, for all sites (input null for vendor site) or a specific site.

UPDATE ja_in_vendor_tds_info_hdr
SET confirm_pan_flag = '&Confirm_PAN_FLAG_Y_N'
WHERE vendor_id = NVL(&vendor_id_NULL_for_all_vendors, vendor_id);

B. Migration script for generating ETDS flat file :
Please note that if at all the current TDS Tax rate includes both surcharge and Cess and if the tax code does not contain any value in Surcharge field of the tax code definition, then the following steps should be executed.

1. Update the existing TDS tax code definition, so that proper value/breakup is given in the
Surcharge Field (which may include surcharge and Cess).

For example,
Take "TDS 2.244% Sec. 194(C)" tax and assume that the total tds rate given is : 2.244% which includes 10% surcharge and 2% cess.
And if the user had already entered the value: 2.244 in the field 'Percentage' and no value in the field 'Surcharge %age', then he should query that particular tax code and give the value 0.244 in the 'Surcharge %age' field.

This will ensure that post application of the patch the TDS amount would split into basic TDS amount + Surcharge amount + Cess amount all the existing transactions (as applicable)

To perform the above step, you should navigate to Setup -> Tax -> Taxes and perform the steps as mentioned in the example.

2. Then the migration script(s) present in the "misc" folder of this patch zip file have to be applied.

This Migration script performs backward calculation of the TDS amount and arrives at the breakup basic TDS Amount, Surcharge and Education CESS. ( Education CESS has been assumed as 2% )

(i) Apply jai_ap_etds_4353842_mig1_apps.sql using following command :
sqlplus apps/ @jai_ap_etds_4353842_mig1_apps.sql

This will create the temporary table for the taxes which has been used from 01-APR-2004 till date for TDS invoices. Then user needs to delete the records from this temporary tables for which CESS is not applicable before running jai_ap_etds_4353842_mig2_apps.sql

(ii) For verification of the queried data , use the query as follows.

SELECT tax_id , tax_name , tax_Rate , surcharge_rate FROM JA_IN_TAX_CODE_APP;

Based on the above data, you might want to delete some taxes (as discussed with functional user) which do not contain cess in the tax rate.

DELETE JA_IN_TAX_CODE_APP WHERE tax_id = &relevant_tax_id_from_query_above

(The tax_id of the tax code that need not be migrated because there is no cess applicability).

(iii) Apply jai_ap_etds_4353842_mig2_apps.sql using following command :

sqlplus apps/ @jai_ap_etds_4353842_mig2_apps.sql

The above script will update the cess_rate, surcharge_rate in ja_in_tax_codes and correspondingly

update the amt_of_tds, amt_of_cess and amt_of_surcharge in ja_in_ap_tds_invoices.

4. RG1 - Source Migration for Shipment / Manual AR Invoice Records
A.
check the dbms output message given after the execution of the script jai_mig_4346220.sql
i. No. of records processed ->
ii. No. of records where RG1 hit from WSH ->
iii.No. of records where RG1 hit from AR ->
iv. No. of records where RG1 hit from both places ->
v. No. of records for RG1 not hit at all ->

B.if output in step iv as given in A , has some value > 0 then the following needs to be done:-

1.Run the below sql query

select * from ja_in_localization_errors where application_id = '4346220'
/
2. Identify the register_id ( appearing as "rec_cur_get_rgi_det.register_id -> " in step 1 )
then run the sql statement in apps schema

Select * from ja_in_rg_i where register_id = < register_id from above>
/
3. Based on output of the sql query go to the View RG1 Register Entry form and query the record by giving the organization location , fin_year and slno and identify whether the transaction is caused due to a Shipment or a Ar receivable transaction.

Note :- The ref_doc_id in the table ja_in_rg_i appears as the Reference No in the screen.
4. If caused due to shipment transaction, run the below update :-
UPDATE ja_in_rg_i
SET cess_amount = ( SELECT sum(func_tax_amount)
FROM
ja_in_so_picking_lines jspl ,
ja_in_so_picking_tax_lines jsptl ,
ja_in_tax_codes jtc
WHERE
jspl.delivery_detail_id = jsptl.delivery_detail_id
AND jspl.delivery_detail_id = <&reference_no from RG1 balance screen>
AND jspl.organization_id = &organization_id
AND jspl.location_id = &location_id
AND jspl.inventory_item_id = &inventory_item_id
AND jspl.quantity = &rg1_qty
AND jtc.tax_id = jsptl.tax_id
AND upper(jtc.tax_type) IN ('EXCISE_EDUCATION_CESS','CVD_EDUCATION_CESS')
),
source = 'WSH' ,
last_update_date = sysdate ,
last_updated_by = -4346220
WHERE
register_id = ®ister_id;
and issue a commit;

5.If caused due to the AR Receivable transaction, then run the below update :-
UPDATE ja_in_rg_i
SET cess_amount = ( SELECT sum(func_tax_amount)
FROM
ja_in_ra_customer_trx jrct ,
ja_in_ra_customer_trx_lines jrctl ,
ja_in_ra_cust_trx_tax_lines jrcttl ,
ja_in_tax_codes jtc
WHERE
jrct.customer_trx_id = jrctl.customer_trx_id
AND jrct.customer_trx_id = <&reference_no from RG1 balance screen>
AND jrctl.customer_trx_line_id = jrcttl.link_to_cust_trx_line_id
AND jrct.organization_id = &organization_id
AND jrct.location_id = &location_id
AND jrctl.inventory_item_id = &inventory_item_id
AND jtc.tax_id = jrcttl.tax_id
AND upper(jtc.tax_type) IN ('EXCISE_EDUCATION_CESS','CVD_EDUCATION_CESS')
source = 'AR' ,
last_update_date = sysdate ,
last_updated_by = -4346220
WHERE
register_id = ®ister_id;

commit;

Note:- the quantity is not required to be given in case of a receivable transaction ,hence not considered in the above update.
This is because RG is at a invoice level and not at a invoice line level.

C.if output in step v given in A, has some value > 0 then please log a service request with India Localization support.

*************PLEASE DO NOT FLUSH THE JA_IN_LOCALIZATION_ERROR TABLE UNTIL ALL THE MIGRATION ISSUES HAVE BEEN RESOLVED*************************

D. IF iv and v from step A return 0 however i,ii or ii show some count then the migration is successful and a commit can be issue

5. Run the following perl script from $JA_TOP/inpatch :
perl compile_il_apps_obj.pl appspwd=

If there are invalids the script will generate "invalid_il_objects.log"

Open the log "invalid_il_objects.log" and check if the following objects are invalid :

a. VIEW JA_IN_MATCH_LINES_V IS INVALID
- Apply the sql "ja_in_match_lines_v.sql" using the following command
sqlplus apps/ @$JA_TOP/5219225/11_5_3/ja_in_match_lines_v.sql

b. TRIGGER JA_IN_PO_LINES_TAX_UPDATE_TRG IS INVALID
- Apply the sql "ja_in_po_lines_tax_update_trg.sql" using the following command
sqlplus apps/ @$JA_TOP/5219225/11_5_3/ja_in_po_lines_tax_update_trg.sql

c. TRIGGER JAIN_TDSTEMP_AFTERINSERT_TRG IS INVALID
- Apply the sql "ja_in_tds_temp_after_insert_trg.sql" using the following command
sqlplus apps/ @$JA_TOP/5219225/11_5_3/ja_in_tds_temp_after_insert_trg.sql

Re-run the perl script "compile_il_apps_obj.pl" and in case of invalid objects please log a service request with
India Localization support and upload the log "invalid_il_objects.log" in the SR.

6. To generate messages

- Go to "Application Developer" Responsibility
- Open View -> Requests
- Click on "Submit New Request"
- Click on "Single Request"
- Enter "Generate Messages" in Name field
- Enter the following parameters
Language : US
Application : Asia/Pacific Localizations
Mode : DB_TO_RUNTIME
- Click Ok and then Submit the request, ensure that request completes successfully
- Logout and Relogin

7. Please refer the documents in the "Documents" directory :

a. 60107 User Reference Manual
b. 60107 Technical Reference Manual
c. 60107 Data Sheet

8. In the following index creation steps, if an index already exists error is encountered - Ignore the error.

CREATE THE FOLLOWING INDEX CONNECTING AS "PO" USER

create index ja_in_rcv_shipment_headers_n1 on rcv_shipment_headers(receipt_num)
create index ja_in_rcv_transactions_n1 on rcv_transactions (rma_reference);

CREATE THE FOLLOWING INDEX CONNECTING AS "AR" USER

create index ja_in_ra_customer_trx_all_n1 on
ra_customer_trx_all(interface_header_attribute1, interface_header_attribute6);

CREATE THE FOLLOWING INDEX CONNECTING AS "INV" USER

create index ja_in_mtl_transactions_n1 on mtl_material_transactions(rcv_transaction_id);

9. Customers below 11.5.7 Applications Release, please ensure to apply 3291333.zip before performing this step.

For the new reports of this patch set to work,
Copy the INLOC_P.prt from the 5498551 directory to $FND_TOP/reports directory.
After copying, register the Printer Style "INLOC_BACS" and Printer Driver "INLOC_AT_EFT" with Printer Type Installed at your site.

To do this Navigate to "Install -> Printer -> Register" with System administrator Responsibility and query for all printers installed at your site.
For each printer installed, check the Type and Click on "Printer Types" button and query for all those printer types.
Add a new record under "Printer Drivers" with "INLOC_BACS" as Style and "INLOC_AT_EFT" as Driver Name and save the record.
Only after this the report will run properly and show the output. Bounce the Concurrent Manager after this step for the changes to take effect.

10. If you are getting the following error message when trying to attach the TDS tax in the
AP Invoice Distributions DFF.

QUOTE

APP-FND-01564: ORACLE error 904 in FDFGDF

Cause: FDFGDF failed due to ORA-00904: "VENDOR_SITE_ID_F":invalid identifier.

UNQUOTE

Perform the following steps :
a. Please note any customization done to AP Invoice Distributions DFF.
b. Run the below command in the patch directory :
i) If you are on FND patchset C, then replace with AP_INVOICE_DISTRIBUTIONS_C.ldt.
ii) If you are on FND patchset D or above, then replace with AP_INVOICE_DISTRIBUTIONS_E.ldt.
iii) Replace with password of APPS user.
FNDLOAD apps/ 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct patch/115/import/US/ - CUSTOM_MODE=FORCE
c. Redo the customization noted in step (a)

11. This patch replaces CUSTOM.pll on $AU_TOP/resource.
The customization which is performed in CUSTOM.pll is backed up in patch/backup/resource directory.
The customization present in patch/backup/resource/CUSTOM.pll should be added to $AU_TOP/resource/CUSTOM.pll and the CUSTOM.plx re-generated.
To re-generate the CUSTOM.plx use the below command providing the :
f60gen module=CUSTOM userid=apps/ module_type=LIBRARY

12. India Localization (IL) menus have undergone a change.
Prior to 60107, IL menus had both Base and IL submenus/functions and in 60107 the same IL menus have been changed to include only the IL submenus/functions.

For each of the IL seeded responsibilities we have created a new menu which includes IL submenus and Base submenus.

The seeded responsibilities provided by India Localization now have the following menus as mentioned below :

Responsibility | Old menu attached | New Menu attached
India Local Fixed Assets | FA_MAIN - India | India Localization Fixed Assets Menu
India Local Inventory | INV_NAVIGATE - India | India Localization Inventory Menu
India Local OM | ONT_SUPER_USER - India | India Localization Order

Mgmt Menu
India Local Payables | AP_NAVIGATE_GUI12 - India | India Localization Payables Menu
India Local Purchasing | Purchasing SuperUser GUI - India | India Localization Purchasing

Menu
India Local Receivables | AR_NAVIGATE_GUI - India | India Localization Receivables

Menu
NOTE : All customized menus created using the India Localization submenus are impacted and need to be changed accordingly.
Use "adadmin" utility to compile the menus.

applprod@vezora3:~ $ cat /tmp/5498551.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Log : Start Time [ 18-Aug-2008 18:04:38 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 5498551.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully
……..
…
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/5498551.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 18-Aug-2008 18:24:07 ]

Time 25 min
PATCH 4239736 CUMULATIVE SERVICE TAX PATCH.

Pre-requistes
Customers should be at least on IN60105D2 patchset of India Localization to apply this patch.

Important Note
This patch is created by merging
• Service Tax patch (4146708) +
• Service Tax Reports patch (4205215) +
• Service Tax patch Update (4202284).
If you have applied all the three above, then you NEED NOT apply this patch.

Patch Application Steps :

IMPORTANT FIRST STEP:
Please run the script "jai_rcv_chk_pending_delivery.sql" supplied with this patch in APPS schema, using SQL*Plus and follow the directions given as output by the script.

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736 $ sqlplus apps/xxxx
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Jul 21 13:48:36 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production

SQL> @jai_rcv_chk_pending_delivery.sql;
*** NO RECEIPT PENDING FOR DELIVERY WITH SERVICE/EXCISE TAX ATTACHED EXISTS, YOU
CAN GO AHEAD WITH PATCH APPLICATION ****
PL/SQL procedure successfully completed.

Only if it returns the message "*** NO RECEIPT PENDING FOR DELIVERY WITH SERVICE/EXCISE TAX ATTACHED EXISTS, YOU CAN GO AHEAD WITH PATCH APPLICATION ****", proceed with the rest of the steps.

In case of any other output from the above script, please follow the instructions detailed in the Document s/Migrate_to_Education_Cess_Service.txt". folder.

A FAQ "Service_Tax_FAQ.pdf" is available in the Documents folder of this patch. This document provides solution/explanations to some of the frequently asked clarifications about Service Tax Solution released by India Localization. Please go through the document before applying this patch.

1) Customers on IN60105D2 - please use the patch 4239736_105.zip. This patch will overwrite the CUSTOM.pll on your AU_TOP/resource directory. Please take a backup of the CUSTOM.pll and after successful patch application, you have to merge the code with the CUSTOM.pll overwritten by this patch.

2) Customers on IN60106 - please use the patch 4239736_106.zip

3) Customers who have already applied this patch on IN60105D2 and now upgraded to IN60106, should again apply this patch for IN60106. Please move the directories $JA_TOP/4239736 and $JA_TOP/$APPLLOG/4239736 to a different location before re-applying the patch for IN60106.

4) Extract the patch:
Extract appropriate 4239736_xxx.zip on the $JA_TOP. It will create the directory 4239736 and create the objects in that directory. Change directory to $JA_TOP/4239736.

5) Customers on FND patchset level C or above and below E

Current FND patchset H

Copy all the ldts in FND_C directory to $JA_TOP/4239736/patch/115/import/US.

6) Change directory to "driver".

7) If on Unix, give execute permissions to all the files there.

8) Run the following commands in the given order with given arguments. Make sure that you run them in Bourne-compatible shells (Bourne shell, Bash etc).
$ copy.sh 2>&1 | tee -a copy.log
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver $ copy.sh 2>&1 | tee -a copy.log
APPL_TOP is set to /u01/DEV3/apps/prodappl
JA_TOP is set to /u01/DEV3/apps/prodappl/ja/11.5.0
Copied JAIN57F4.fmb successfully to AU_TOP/forms/US.
Copied JAINACDM.fmb successfully to AU_TOP/forms/US.
Copied JAINARTX.fmb successfully to AU_TOP/forms/US.
Copied JAINCLBO.fmb successfully to AU_TOP/forms/US.
Copied JAINCPLA.fmb successfully to AU_TOP/forms/US.
Copied JAINDMAN.fmb successfully to AU_TOP/forms/US.
Copied JAINDPBO.fmb successfully to AU_TOP/forms/US.
Copied JAINDSHP.fmb successfully to AU_TOP/forms/US.
Copied JAINEORD.fmb successfully to AU_TOP/forms/US.
Copied JAINIBOE.fmb successfully to AU_TOP/forms/US.
Copied JAINIRGI.fmb successfully to AU_TOP/forms/US.
Copied JAINMREC.fmb successfully to AU_TOP/forms/US.
Copied JAINMVAT.fmb successfully to AU_TOP/forms/US.
Copied JAINOSPM.fmb successfully to AU_TOP/forms/US.
Copied JAINOTAX.fmb successfully to AU_TOP/forms/US.
Copied JAINPLAM.fmb successfully to AU_TOP/forms/US.
Copied JAINPO.fmb successfully to AU_TOP/forms/US.
Copied JAINPORE.fmb successfully to AU_TOP/forms/US.
Copied JAINPORL.fmb successfully to AU_TOP/forms/US.
Copied JAINPVDM.fmb successfully to AU_TOP/forms/US.
Copied JAINREQN.fmb successfully to AU_TOP/forms/US.
Copied JAINRFQQ.fmb successfully to AU_TOP/forms/US.
Copied JAINRG23.fmb successfully to AU_TOP/forms/US.
Copied JAINRGAC.fmb successfully to AU_TOP/forms/US.
Copied JAINRGCO.fmb successfully to AU_TOP/forms/US.
Copied JAINRGFT.fmb successfully to AU_TOP/forms/US.
Copied JAINUTAX.fmb successfully to AU_TOP/forms/US.
Copied JAINVBAL.fmb successfully to AU_TOP/forms/US.
Copied JAINVPLA.fmb successfully to AU_TOP/forms/US.
Copied JAINVRCV.fmb successfully to AU_TOP/forms/US.
Copied JAINVWRG.fmb successfully to AU_TOP/forms/US.
Copied JAIREGIM.fmb successfully to AU_TOP/forms/US.
Copied JAIRGMDT.fmb successfully to AU_TOP/forms/US.
Copied JAIRGMMT.fmb successfully to AU_TOP/forms/US.
Copied JAIRGMPT.fmb successfully to AU_TOP/forms/US.
Copied JAIRGMSP.fmb successfully to AU_TOP/forms/US.
Copied JAIRGMST.fmb successfully to AU_TOP/forms/US.
Copied JAF23A_2 to INV_TOP/reports/US.
Copied JAFRMRG1 to INV_TOP/reports/US.
Copied JAIN23D to AR_TOP/reports/US.
Copied JAIN23D to ONT_TOP/reports/US.
Copied JAINABST to PO_TOP/reports/US.
Copied JAINCVAT to PO_TOP/reports/US.
Copied JAINCVAT to INV_TOP/reports/US.
Copied JAINER1 to AR_TOP/reports/US.
Copied JAINEXCL to INV_TOP/reports/US.
Copied JAINMCEN to PO_TOP/reports/US.
Copied JAINMCENCG_EXC to PO_TOP/reports/US.
Copied JAINMCEN_EXC to PO_TOP/reports/US.
Copied JAINPLA to INV_TOP/reports/US.
Copied JAINRECI to PO_TOP/reports/US.
Copied JAINTSLS to AR_TOP/reports/US.
Copied JAIRGMCR to JA_TOP/reports/US.
Copied JAIRGMPL to JA_TOP/reports/US.
Copied JAIRGMPR to JA_TOP/reports/US.
Copied JAIST3 to JA_TOP/reports/US.
Copied JAINTAX.pll successfully to AU_TOP.
Copied JAINTAX1.pll successfully to AU_TOP.
Copied jaintax.pll successfully to AU_TOP.
Copied jaintax1.pll successfully to AU_TOP.
All files copied successfully.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver
$ dbrun.sh 2>&1 | tee -a dbrun.log

applprod@vezora3:~ $ . apps.env
applprod@vezora3:~ $ cd /u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver $ dbrun.sh k3ob3ia ja 2>&1 | tee -a dbrun.log
APPL_TOP is set to /u01/DEV3/apps/prodappl
JA_TOP is set to /u01/DEV3/apps/prodappl/ja/11.5.0
Running ja_in_create_table_3575112.sql
create table ja_in_fa_mass_additions
……
….
………………………….
Report filename : O6986832.out
Log filename : L6986833.log

Report filename : O6986833.out
Log filename : L6986834.log

Report filename : O6986834.out
Log filename : L6986835.log

Report filename : O6986835.out
Running ja_in_datafix_4194107.sql

0 rows deleted
Commit complete.

Running jai_cmn_datafix_4205215.sql
PL/SQL procedure successfully completed.

Commit complete.
Running jai_datafix_4199929_apps.sql
0 rows updated.

Commit complete.
Running jai_rcv_migration_3940588.sql
Index created.
Index created.

***** Successfully Migrated Old Receipts to New Receipts *****
----- Record Count that are already in JA :0
----- Record Count inserted into JA :0
----- Total Count Processed :0
PL/SQL procedure successfully completed.

Index dropped.
Index dropped.
Commit complete.

Finished Database driver.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver $

$ generate.sh 2>&1 | tee -a generate.log

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver $ generate.sh k3ob3ia 2>&1 | tee -a generate.log

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver $ generate.sh k3ob3ia 2>&1 | tee -a generate.log
APPL_TOP is set to /u01/DEV3/apps/prodappl
JA_TOP is set to /u01/DEV3/apps/prodappl/ja/11.5.0
Generating forms
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)

Forms 6.0 (Form Compiler): Release - Production

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
Compiling library JAINTAX...
Compiling Procedure Body UOM_CONVERT......
Compiling Package Body TAX_PRECEDENCE......
Compiling Procedure Body SHOW_INEFFECTIVE_TAX......
Compiling Package Body OTHERS......
Done.
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)

Forms 6.0 (Form Compiler): Release - Production

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
Compiling library JAINTAX1...
Done.
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)

Forms 6.0 (Form Compiler): Release - Production

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
Compiling library JAINTAX...
Compiling Procedure Body SHOW_INEFFECTIVE_TAX......

Report filename : O6986851.out
Log filename : L6986852.log

Report filename : O6986852.out
Log filename : L6986853.log

Report filename : O6986853.out
Log filename : L6986854.log

Report filename : O6986854.out
Log filename : L6986855.log

Report filename : O6986855.out
Log filename : L6986856.log

Report filename : O6986856.out
Finished Generate driver.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736/driver $

Note: Replace with password of APPS user and with password of JA user.

9) Please check the log files created in $JA_TOP/$APPLLOG/4239736 directory and its subdirectories for any issues.

Check the output logs in C:\111111\vezora3\Logs_IN_Local\4239736

10) Customers on multi-node installations, please run the following two drivers on the FORMS node, after running step 8 on Database/Concurrent nodes.
$ copy.sh 2>&1 | tee -a copy.log
$ generate.sh 2>&1 | tee -a generate.log

Replace with password of APPS user and with password of JA user.

11) Please run "$JA_TOP/4239736/compile_script.sql" as APPS user. It will create "compile_objects.sql" in current directory. Please run it to compile localization invalid objects. Run these two scripts in cyclic loop till you have no invalids reported by "compile_script.sql".

applprod@vezora3:~ $ cd /u01/DEV3/apps/prodappl/ja/11.5.0/4239736

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4239736 $ sqlplus apps/xxxx

SQL*Plus: Release 9.2.0.8.0 - Production on Tue Aug 19 13:29:35 2008

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production

SQL> @compile_script.sql;

Alter PROCEDURE JAINSOIF compile
/
…
……
………….

12) Please navigate to "Documents" folder in this patch zip file to find documents pertaining to:
a) Receipt Corrections.
b) Rounding of Excise Amounts.
c) Service Tax functionality.
d) Education Cess functionality.
e) Migrate_to_Education_Cess_Service.txt

13) If ALL of the following conditions are true then please apply patch 4211132 from metalink. You may need to run any data migration scripts that might have failed due to these invalids. Please check the dbrun.log for such issues.
a. You are on 11.5.6 or below
b. You do not plan to apply VAT patch 4245089 after this patch
c. There are invalids in the database after Step 11 above with error message such as:

PLS-00201: identifier 'INV_TXN_MANAGER_PUB.PROCESS_TRANSACTIONS' must be declared

14) If you are on IN60105D2 and do not plan to apply VAT patch 4245089, then you might find two forms JAINEORD.fmb and JAINARTX.fmb not getting generated. Please apply patch 4360220 to resolve the issue.

PATCH - 4245089 INDIA LOCALIZATION VAT SOLUTION.

Pre-requistes
-------------
1) Customers should be atleast on IN60105D2 patchset of India Localization to apply this patch.
2) Please apply Service Tax patch 4146708, Service tax reports patch 4205215 and Service tax update patch 4202284.
3) Cumulative Service Tax patch 4239736 can be applied instead of the above three patches mentioned in point 2.

Important Note: Customers who applied Cumulative Service Tax patch 4239736 on IN60105D2 and have subsequently upgraded to IN60106, should re-apply the Cumulative Service Tax patch before applying this patch and ignore all invalids until this patch is applied completely.

A FAQ "Value_Added_Tax_FAQ.pdf" is included in the Documents folder of this patch. This document provides solution/explanations to some of the frequently asked clarifications about Value Added Tax Solution released by India Localization. Please go through the document before applying this patch.

Patch Application Steps :

(Important: The notation below is given for Unix shells, particularly Bourne shell. Windows users, please use %% instead of $ and "dir\file" instead of "dir/file" notation.)

1) Extract 4245089.zip on the $JA_TOP. It will create the directory 4245089 and create the objects in that directory. Change directory to $JA_TOP/4245089.

2) Customers on FND patchset level C or above and below E:
Copy all the ldts in FND_C directory to $JA_TOP/4245089/patch/115/import/US.

3) Change directory to "driver".

4) If on Unix, give execute permissions to all the files there.

5) Run the following commands in the given order with given arguments. Make sure that you run them in Bourne-compatible shells (Bourne shell, Bash etc).

$ copy.sh 2>&1 | tee -a copy.log

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4245089/driver $ copy.sh 2>&1 | tee -a copy.log
APPL_TOP is set to /u01/DEV3/apps/prodappl
JA_TOP is set to /u01/DEV3/apps/prodappl/ja/11.5.0
Copied JAIITMCL.fmb successfully to AU_TOP/forms/US.
Copied JAINACDM.fmb successfully to AU_TOP/forms/US.
Copied JAINARTX.fmb successfully to AU_TOP/forms/US.
Copied JAINCSHP.fmb successfully to AU_TOP/forms/US.
Copied JAINEORD.fmb successfully to AU_TOP/forms/US.
Copied JAINOTAX.fmb successfully to AU_TOP/forms/US.
Copied JAINPO.fmb successfully to AU_TOP/forms/US.
Copied JAINPORE.fmb successfully to AU_TOP/forms/US.
Copied JAINPORL.fmb successfully to AU_TOP/forms/US
..
..
cp: cannot stat `jaintax.pll': No such file or directory
Could not copy jaintax.pll to AU_TOP.
cp: cannot stat `jaintax1.pll': No such file or directory
Could not copy jaintax1.pll to AU_TOP.
One of more files could not be copied. Please check the log file and proceed with the next driver only after resolving the error.

$ dbrun.sh 2>&1 | tee -a dbrun.log

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4245089/driver $ dbrun.sh k3ob3ia ja 2>&1 | tee -a dbrun.log
APPL_TOP is set to /u01/DEV3/apps/prodappl
JA_TOP is set to /u01/DEV3/apps/prodappl/ja/11.5.0
Running jai_vat_obj_ja_4245089.sql
CREATING TABLE JAI_RGM_TERMS
CREATE TABLE JAI_RGM_TERMS
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
………….
………………….

Report filename : O6986872.out
Log filename : L6986873.log

Report filename : O6986873.out
Log filename : L6986874.log

Report filename : O6986874.out
Log filename : L6986875.log

Report filename : O6986875.out
Log filename : L6986876.log

Report filename : O6986876.out
Log filename : L6986877.log

Report filename : O6986877.out
Log filename : L6986878.log

Report filename : O6986878.out
Running jai_seed_4248279_gl_jrnal_src.sql

PL/SQL procedure successfully completed.

Commit complete.
Finished Database driver.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4245089/driver $

$ generate.sh 2>&1 | tee -a generate.log

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4245089/driver $ generate.sh k3ob3ia 2>&1 | tee -a generate.log
APPL_TOP is set to /u01/DEV3/apps/prodappl
JA_TOP is set to /u01/DEV3/apps/prodappl/ja/11.5.0
Generating forms
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)

Forms 6.0 (Form Compiler): Release - Production

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
Compiling library JAINTAX...
Compiling Package Spec TAX_PRECEDENCE......
Compiling Procedure Body UOM_CONVERT......
Compiling Package Body TAX_PRECEDENCE......
Compiling Procedure Body SHOW_INEFFECTIVE_TAX......
Compiling Package Body OTHERS......
Done.
….
…….
……..
……….
Compiling WHEN-BUTTON-PRESSED trigger on REFRESH item in PROGRESS_INDICATOR data block...
No compilation errors.

Compiling WHEN-BUTTON-PRESSED trigger on CANCEL_PROPERTIES item in PROGRESS_INDICATOR data block...
No compilation errors.

Created form file /u01/DEV3/apps/prodappl/ja/11.5.0/forms/US/JAIRGMST.fmx
Log filename : L6986879.log

Report filename : O6986879.out
Log filename : L6986880.log

Report filename : O6986880.out
Log filename : L6986881.log

Report filename : O6986881.out
Finished Generate driver.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/4245089/driver $

6) Please check the log files created in $JA_TOP/$APPLLOG/4245089 directory and its subdirectories for any issues.

see logs in C:\111111\vezora3\Logs_IN_Local\4245089\

7) Customers on multi-node installations, please run the following two drivers on the FORMS node, after running step 8 on Database/Concurrent nodes.
$ copy.sh 2>&1 | tee -a copy.log
$ generate.sh 2>&1 | tee -a generate.log

10) Please generate message files for JA product using adadmin.

11) Please run "$JA_TOP/4245089/compile_script.sql" as APPS user. It will create "compile_objects.sql" in current directory. Please run it to compile localization invalid objects. Run these two scripts in cyclic loop till you have no invalids reported by "compile_script.sql".

12) User reference manual "India Localization VAT URM.pdf" is included in the "Documents" folder.

PATCH 6167056 - HANDLING SECONDARY AND HIGHER EDUCATION CESS
Instructions For Applying This Patch

1) This Patch should be applied ONLY using the India Localization Automated Patch
Application Tool provided as patch 6059025. If you have not applied the patch 6059025,
please download and apply as instructed in the Readme.

Go through Automated Patch Application Tool manual and UNDERSTAND THE USAGE OF THE TOOL.
Refer metalink note# 376756.1 for more information on the tool.
Please raise an SR for any queries regarding the tool.

3) This patch replaces CUSTOM.pll on AU_TOP/resource.
Refer the "Instructions to merge CUSTOM.pll" in the "POST-PATCH APPLICATION STEPS"
section for details.

4) This patch delivers solution for handling "Secondary and Higher Education" Cess.

5) You should read thoroughly the below sections before applying the patch :
- PRE-REQUISITES
- PRE-PATCH APPLICATION STEPS
- SPECIAL INSTRUCTIONS
- APPLY THE PATCH
- DIAGONIZE PATCH FAILURES ( IF ANY )
- POST-PATCH APPLICATION STEPS

PRE-REQUISITES

This patch should be applied only if the following patch (es) are already applied :

1) IN60107 done
2) IN60105D2 + ST (4239736) + VAT (4245089)
3) IN60106 + ST (4239736) + VAT (4245089) done

PRE-PATCH APPLICATION STEPS

1) Check if DBMS_SUPPORT package is present in your APPS schema by using the below query in APPS schema

select object_name, object_type from all_objects where object_name = 'DBMS_SUPPORT' and object_type like 'PACKAGE%' ;

If the above query does not return both DBMS_SUPPORT package and package body,
create them using below command :
sqlplus apps/apps @$ORACLE_HOME/rdbms/admin/dbmssupp.sql

2) Please take a backup of your database before the patch can be applied.

SPECIAL INSTRUCTIONS
Please ask the functional users to go through "India Localization Budget 07-08.pdf"
located in the "Documents" directory for understanding the setup and change
of behavior with this patch.

APPLY THE PATCH

This Patch should be applied ONLY using the India Localization Patch Application Tool

You will need to perform the following 4 steps :
1) Extract the patch 6167056 zip file to a temporary directory.
2) Change directory to 6167056.
3) Note that the patch application log generated gets appended for every application of the patch. It is advisable to rename the old log file generated for future reference.

4) Apply the patch as described below based on whether your installation is single-node or multi-node.

a) Single-node installation

Syntax for applying the patch :

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/6167056 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6167056.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6167056.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 19-Aug-2008 14:29:36 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 19-Aug-2008 14:29:37 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6167056.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully

…
……
…….
jai_rcv_rmaref_v.sql
jai_ar_tcs_repository_pkg.plb
jai_arra_trg.plb
jai_ar_cash_receipts_trg_pkg.plb
jai_cmn_dbg_ctx.plb
jai_rgm_thld_prc.plb
jainaptcs_b.plb
jai_ap_tcs_prc.plb
jai_ar_etcs_prc.plb
jai_cmn_misc_concurrents_pkg.plb
jai_stforms_prc.plb
jai_ar_eer1_pkg.plb
jai_cmn_mass_tax.plb
jai_trx_repo_ext.plb
jai_mtl_trxs_pkg.plb
jai_po_hook_pkg.plb
jai_rcv_opm_costing_pkg.plb
jai_arra_ariud.sql
jai_ar_cash_receipts_ariud_trg.sql

----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6167056.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 19-Aug-2008 14:37:31 ]
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/6167056 $

Log at C:\111111\vezora3\Logs_IN_Local\6167056\

For details on [ other args ] please refer to the Automated Patch Tool User Manual.

POST-PATCH APPLICATION STEPS
============================

IMPORTANT NOTE :
- Ignore steps 4 till 8, if you have applied IN60107 patch
- Steps 4, 5 and 9 are related to data migration and hence should be reviewed by both FUNCTIONAL USER and DBA.

1) Instructions to check India Localization invalids

Run the following perl script from $JA_TOP/inpatch :
perl compile_il_apps_obj.pl appspwd=

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/inpatch $ perl compile_il_apps_obj.pl appspwd=k3ob3ia
Compiling the APPS schema
.. .. .. .. completed with no invalids.
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/inpatch $

If there are invalids the script will generate "invalid_il_objects.log"
Open the log "invalid_il_objects.log" and check if the following objects are invalid :
a) TRIGGER JA_IN_PO_LINES_TAX_UPDATE_TRG IS INVALID
- Apply the sql "ja_in_po_lines_tax_update_trg.sql" using the following command
sqlplus apps/ @11_5_7/ja_in_po_lines_tax_update_trg.sql

b) TRIGGER JAIN_TDSTEMP_AFTERINSERT_TRG IS INVALID
- Apply the sql "ja_in_tds_temp_after_insert_trg.sql" using the following command
sqlplus apps/ @11_5_7/ja_in_tds_temp_after_insert_trg.sql

c) PACKAGE BODY JA_IN_RECEIPT_ACCOUNTING_PKG IS INVALID
- Apply the sql "ja_in_receipt_accounting_pkg.sql" using the following command
sqlplus apps/ @11_5_7/ja_in_receipt_accounting_pkg.sql

d) PROCEDURE JA_IN_RECEIPT_TAXES IS INVALID
- Apply the sql "ja_in_receipts_p.sql" using the following command
sqlplus apps/ @11_5_7/ja_in_receipts_p.sql

Re-run the perl script "compile_il_apps_obj.pl" and in case of invalid objects please log a service request with India Localization support and upload the log "invalid_il_objects.log" in the SR.

2) Instructions to generate messages

a) Go to "Application Developer" Responsibility
b) Open View -> Requests
c) Click on "Submit New Request"
d) Click on "Single Request"
e) Enter "Generate Messages" in Name field
f) Enter the following parameters
- Language : US
- Application : Asia/Pacific Localizations
- Mode : DB_TO_RUNTIME
g) Click Ok and then Submit the request, ensure that request completes successfully
h) Logout and Relogin

3) Instructions to merge CUSTOM.pll
The customization which is performed in CUSTOM.pll is backed up in 6167056/backup/resource directory.

Please refer metalink note# 417795.1 for merging India Localization code into the CUSTOM.pll.

Copy the CUSTOM.pll to $AU_TOP/resource and re-generate the CUSTOM.plx using the below command providing the :
f60gen module=CUSTOM userid=apps/ module_type=LIBRARY

4) TDS MIGRATION
NOTE :
- Migration should be done with the help of FUNCTIONAL user and the DBA alone SHOULD NOT perform migration without adequate knowledge.
-
SKIP this STEP ( ie., 3. TDS MIGRATION ) if any of the below criteria is met :
i) Fresh India Localization install
OR
ii) Any of the below patches are applied :
- 60107 OR
- 5377690 OR
- 5373375 (OLD TDS consolidated Patch) OR
- 5352145 (OLD TDS consolidated Patch)OR
- 5223033 (OLD TDS consolidated Patch)OR
- 4860026 + 4353842 (in the order given above)

a) For Migration of Existing Threshold Data
i) View the old Threshold Data :

Please use the following query to view the threshold data that existed before this patch application. Threshold has undergone a major change and the old data does not show up in the vendor additional info. Threshold is no more setup for each vendor, but is defined for a specific vendor type. Exception setups can only be assigned to specific vendor or vendor sites.

Query to view old threshold data setup for each vendor / site :

SELECT DISTINCT a.vendor_id,
a.vendor_site_id, b.vendor_name,
DECODE(a.vendor_site_id, 0 , 'Null Site', c.vendor_site_code) "Vendor Site Code",
a.tds_section, a.tds_amount, decode(a.invoice_tds_flag, 'P', 'Per Invoice', 'A', 'All Invoices')
FROM ja.ja_in_vendor_tds_info_dtl a, po_vendors b, po_vendor_sites_all c
WHERE a.vendor_id = b.vendor_id
AND b.vendor_id = c.vendor_id
AND (a.vendor_site_id = c.vendor_site_id OR a.vendor_site_id = 0 )

ii) Apply file jai_ap_3841637_migrate_pkg_t.sql available in "misc" folder of this patch zip file using below command :

sqlplus apps/ @jai_ap_3841637_migrate_pkg_t.sql

This file creates the package that is being used in the query to validate PAN number as in step 3.

iii) PAN Number validation :

Vendor PAN number is of significant importance after this patch application.
Following query gives you the details of PAN number by vendor site.

SELECT DISTINCT a.vendor_id,
a.vendor_site_id, b.vendor_name,
DECODE (a.vendor_site_id, 0, 'Null Site', c.vendor_site_code) "Vendor Site Code",
a.pan_no, jai_ap_3841637_migrate_pkg_t.check_valid (a.pan_no, 10) PAN_NO_STATUS,
DECODE (a.vendor_site_id, 0, a.confirm_pan_flag, NULL) PAN_CONFIRM_FLAG
FROM ja_in_vendor_tds_info_hdr a, po_vendors b,po_vendor_sites_all c
WHERE a.vendor_id = b.vendor_id
AND b.vendor_id = c.vendor_id
AND (a.vendor_site_id = c.vendor_site_id OR a.vendor_site_id = 0)

iv) Execute the below SQL command in APPS schema :
DROP PACKAGE JAI_AP_3841637_MIGRATE_PKG_T ;

Steps 5 and 6 are required only if you find discrepancies in PAN No and
PAN Confirm Flag as a result of output of step 3 above.

v) Update Script for PAN no for a vendor / site :

The following script can be used to update the PAN number for all sites
(input null for vendor site) or a specific site.

UPDATE ja_in_vendor_tds_info_hdr
SET pan_no = '&New_PAN_NO'
WHERE vendor_id = &vendor_id
AND vendor_site_id = NVL(&vendor_Site_ID, vendor_site_id);

vi) Update script for Confirm PAN flag :

The following script can be used to set the value of confirm_pan_flag, for all sites
(input null for vendor site) or a specific site.

UPDATE ja_in_vendor_tds_info_hdr
SET confirm_pan_flag = '&Confirm_PAN_FLAG_Y_N'
WHERE vendor_id = NVL(&vendor_id_NULL_for_all_vendors, vendor_id);

b) Migration script for generating ETDS flat file

Please note that if at all the current TDS Tax rate includes both surcharge and Cess and if the tax code does not contain any value in Surcharge field of the tax code definition, then the following steps should be executed.

i) Update the existing TDS tax code definition, so that proper value/breakup is given in the Surcharge Field (which may include surcharge and Cess).

For example,
Take "TDS 2.244% Sec. 194(C)" tax and assume that the total tds rate given is : 2.244% which includes 10% surcharge and 2% cess. And if the user had already entered the value: 2.244 in the field 'Percentage' and no value in the field 'Surcharge %age', then he should query that particular tax code and give the value 0.244 in the 'Surcharge %age' field. This will ensure that post application of the patch the TDS amount would split into basic TDS amount + Surcharge amount + Cess amount all the existing transactions (as applicable).

To perform the above step, you should navigate to Setup -> Tax -> Taxes and perform the steps as mentioned in the example.

ii) Then the migration script(s) present in the "misc" folder of this patch zip file
have to be applied.

This Migration script performs backward calculation of the TDS amount and arrives at the breakup basic TDS Amount, Surcharge and Education CESS. ( Education CESS has been assumed as 2% )

- Apply jai_ap_etds_4353842_mig1_apps.sql using following command :
sqlplus apps/ @jai_ap_etds_4353842_mig1_apps.sql

This will create the temporary table for the taxes which has been used from 01-APR-2004 till date for TDS invoices. Then user needs to delete the records from this temporary tables for which CESS is not applicable before running jai_ap_etds_4353842_mig2_apps.sql

- For verification of the queried data , use the query as follows.

SELECT tax_id , tax_name , tax_Rate , surcharge_rate FROM JA_IN_TAX_CODE_APP;

Based on the above data, you might want to delete some taxes (as discussed with functional user) which do not contain cess in the tax rate.

DELETE JA_IN_TAX_CODE_APP
WHERE tax_id = &relevant_tax_id_from_query_above;

(The tax_id of the tax code that need not be migrated because there is no cess applicability)

- Apply jai_ap_etds_4353842_mig2_apps.sql using following command :

sqlplus apps/ @jai_ap_etds_4353842_mig2_apps.sql

The above script will update the cess_rate, surcharge_rate in ja_in_tax_codes and correspondingly update the amt_of_tds, amt_of_cess and amt_of_surcharge in ja_in_ap_tds_invoices.

5) RG1 - Source Migration for Shipment / Manual AR Invoice Records
a) Apply file jai_mig_4346220.sql available in "admin" folder of this patch zip file using following command.

sqlplus apps/ @jai_mig_4346220.sql

Check the dbms output message given after the execution of the script jai_mig_4346220.sql
i) No. of records processed ->
ii) No. of records where RG1 hit from WSH ->
iii) No. of records where RG1 hit from AR ->
iv) No. of records where RG1 hit from both places ->
v) No. of records for RG1 not hit at all ->

b) If output in step iv as given in A , has some value > 0 then the following needs
to be done :

i) Run the below sql query
select * from ja_in_localization_errors where application_id = '4346220' ;

ii) Identify the register_id ( appearing as "rec_cur_get_rgi_det.register_id -> " in step 1 )
and then run the sql statement in apps schema

select * from ja_in_rg_i where register_id = < register_id from above> ;

iii) Based on output of the sql query go to the View RG1 Register Entry form and query
the record by giving the organization, location, fin_year and slno and
identify whether the transaction is caused due to a Shipment or
an AR receivable transaction.

NOTE : The ref_doc_id in the table ja_in_rg_i appears as the Reference No in the screen.

iv) If caused due to shipment transaction, run the below update and issue a COMMIT :

UPDATE ja_in_rg_i
SET cess_amount = ( SELECT sum(func_tax_amount)
FROM
ja_in_so_picking_lines jspl ,
ja_in_so_picking_tax_lines jsptl ,
ja_in_tax_codes jtc
WHERE
jspl.delivery_detail_id = jsptl.delivery_detail_id
AND jspl.delivery_detail_id = <&reference_no from RG1 balance screen>
AND jspl.organization_id = &organization_id
AND jspl.location_id = &location_id
AND jspl.inventory_item_id = &inventory_item_id
AND jspl.quantity = &rg1_qty
AND jtc.tax_id = jsptl.tax_id
AND upper(jtc.tax_type) IN ('EXCISE_EDUCATION_CESS','CVD_EDUCATION_CESS')
),
source = 'WSH' ,
last_update_date = sysdate ,
last_updated_by = -4346220
WHERE
register_id = ®ister_id;

COMMIT;

v) If caused due to the AR Receivable transaction, then run the below update and issue a COMMIT :

UPDATE ja_in_rg_i
SET cess_amount = ( SELECT sum(func_tax_amount)
FROM
ja_in_ra_customer_trx jrct ,
ja_in_ra_customer_trx_lines jrctl ,
ja_in_ra_cust_trx_tax_lines jrcttl ,
ja_in_tax_codes jtc
WHERE
jrct.customer_trx_id = jrctl.customer_trx_id
AND jrct.customer_trx_id = <&reference_no from RG1 balance screen>
AND jrctl.customer_trx_line_id = jrcttl.link_to_cust_trx_line_id
AND jrct.organization_id = &organization_id
AND jrct.location_id = &location_id
AND jrctl.inventory_item_id = &inventory_item_id
AND jtc.tax_id = jrcttl.tax_id
AND upper(jtc.tax_type) IN ('EXCISE_EDUCATION_CESS','CVD_EDUCATION_CESS')
source = 'AR' ,
last_update_date = sysdate ,
last_updated_by = -4346220
WHERE
register_id = ®ister_id;

COMMIT;

NOTE:
The quantity is not required to be given in case of a receivable transaction, hence not considered in the above update. This is because RG is at a invoice level and not at a invoice line level.

6) Creating Indexes
Execute the following statements to create the index :
NOTE : If an index already exists error is encountered - Ignore the error.

a) CREATE THE FOLLOWING INDEX CONNECTING AS "PO" USER
i) create index ja_in_rcv_shipment_headers_n1 on rcv_shipment_headers ( receipt_num );
ii) create index ja_in_rcv_transactions_n1 on rcv_transactions ( rma_reference );

b) CREATE THE FOLLOWING INDEX CONNECTING AS "AR" USER
i) create index ja_in_ra_customer_trx_all_n1 on
ra_customer_trx_all ( interface_header_attribute1, interface_header_attribute6 );

c) CREATE THE FOLLOWING INDEX CONNECTING AS "INV" USER
i) create index ja_in_mtl_transactions_n1 on
mtl_material_transactions ( rcv_transaction_id );

7) Printer Setup
NOTE : Customers below 11.5.7 Oracle Applications Release should apply 3291333.zip before proceeding with steps a) and b).

a) For the new reports of this patch set to work perform the below steps :
i) Copy the INLOC_P.prt from the 6167056 directory to $FND_TOP/reports directory.
ii) Register the Printer Style "INLOC_BACS" and Printer Driver "INLOC_AT_EFT" as described below :
- Naviagate to "Install -> Printer -> Register" in System administrator Responsibility
- Query for all printers installed at your site.
- For each printer installed, check the Type and Click on "Printer Types" button
and query for all those printer types.
- Add a new record under "Printer Drivers" with "INLOC_BACS" as Style and "INLOC_AT_EFT" as Driver Name and save the record.
- Bounce the Concurrent Manager after this step for the changes to take effect.

b) For printing "page-break" for India Localization reports please follow metalink note# 444034.1

8) DFF for AP Invoice Distributions

If you are getting the following error message when trying to attach the TDS tax in the AP Invoice Distributions DFF.

QUOTE

APP-FND-01564: ORACLE error 904 in FDFGDF

Cause: FDFGDF failed due to ORA-00904: "VENDOR_SITE_ID_F":invalid identifier.

UNQUOTE

Perform the following steps :
a) Please note any customization done to AP Invoice Distributions DFF.
b) Run the below command in the patch directory :
- If you are on FND patchset C, then replace with AP_INVOICE_DISTRIBUTIONS_C.ldt.
- If you are on FND patchset D or above, then replace with AP_INVOICE_DISTRIBUTIONS_E.ldt.
- Replace with password of APPS user.
FNDLOAD apps/ 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct patch/115/import/US/ - CUSTOM_MODE=FORCE
c) Redo the customization noted in step (a)

9) SHE Cess migration
------------------

Refer to the migration section in 'India Localization Budget 07-08.pdf' to pass manual GL entries
for accounting 1% SHE Cess.

The following log files in the location specified by the below query executed in APPS schema
will give details of accounting entries to be passed.

Query :
SELECT value FROM v$parameter WHERE name = 'utl_file_dir';

Log files :
om_accounting.log
ar_accounting.log
ar_service_accounting.log
po_accounting.log
ap_service_accounting.log

10) Run the 'India Excise Reconciliation' Concurrent from India Local Purchasing responsibility from
1st March 2007 for all registers and all organizations.

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/6167056 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6167056.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6167056.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 28-Jul-2008 09:47:46 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 28-Jul-2008 09:47:47 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6167056.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully

----------------------------------------------------------------------------
Objects that WILL be applied
----------------------------------------------------------------------------
Object Name Version -> Patch Existing
----------------------------------------------------------------------------
resource/CUSTOM.pll 115.9.6107.2 NA
resource/JAINTAX1.pll 115.13.6107.3 NA
resource/JAINTAX.pll 115.9.6107.9 NA
resource/JAINHELP.pll 115.1.6107.1 NA
..
..
...
STATUS :
Patch application completed successfully.
Please check /tmp/6167056.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 28-Jul-2008 09:48:03 ]

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/6167056
PATCH 6079063 - IL SUPPORT FOR INTER ORGANIZATION SUPPORT
REF : 2942973 - ENH:INVENTORY TRANSFER TRANSACTION DOES NOT UPDATE RG REGISTERS
This Patch should be applied on the TEST instance first, perform rigorous test cycles, after you are satisfied with the result of the cycles, apply this patch on the PRODUCTION Instance.

Never apply it directly on the Production instance without applying on the test.

For mutli-node installations, the patch should FIRST be applied on the Database node using argument "mode=D" of the India Localization Patch Application Tool.

Pre-requisites

Oracle Applications Release 11.5.10.2 (3480000) + 6079248 ( ENH:SECONDARY AND HIGHER EDUCATION CESS - BUDGET 2007 )

Special Instructions

A) Please refer to the "documents" folder for the following :
1. India Localization Inter Org Transfer.pdf ( to be used by Functional User )

Automated Patch Application Steps

If you have applied the patch 6059025 from metalink (India Localization Patch Application Tool), you should be able to apply this patch using that tool. Please follow the user manual supplied in the patch 6059025 to apply this patch. You will need to perform the following 3 steps:

1) Extract this patch zip file to a temporary directory.
2) Change directory to 6079063.
3) Proceed as instructed in the automated patch tool user manual.

applprod@vezora3:/stage/IN_Localization/6079063 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6079063.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6079063.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 19-Aug-2008 15:59:36 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 19-Aug-2008 15:59:46 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6079063.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully

----------------------------------------------------------------------------
Objects that WILL be applied
----------------------------------------------------------------------------
Object Name Version -> Patch Existing
----------------------------------------------------------------------------
resource/JAINVMTX.pll 115.16.6107.3 NA
forms/US/JAINEXCDET.fmb 115.10.6107.2 NA
forms/US/JAINVMTX.fmb 115.19.6107.2 NA
patch/115/import/US/JAI_INV_TRANSACTIONS_C.ldt 115.0.6107.1 -
patch/115/import/US/JAI_INV_TRANSACTIONS_E.ldt 115.0.6107.1 -

----------------------------------------------------------------------------
******************* No rdf files to copy ********************
----------------------------------------------------------------------------
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6079063/backup.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6079063.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 19-Aug-2008 16:00:37 ]

applprod@vezora3:/stage/IN_Localization/6079063

Total Time 5 minutes

PATCH 3485155 ORACLE PROJECTS FAMILY PACK M
FAMILY PACK 11i.PJ_PF.M stopped here 19_08-2008
Please refer to MetaLink note 302074.1 for Patch Descriptions

PATCH 6375875
This patch is applicable on top of 11i.PJ_PF.M RUP3

This patch is a Pre Install patch to be applied
After applying patch - #5105878: Oracle Projects Rollup Patch 3 for Oracle
Projects Family Pack M (11i.PJ_PF.M)

AND

Before applying patch - 5644830 # Oracle Projects Rollup Patch 4 for Oracle
Projects Family Pack M (11i.PJ_PF.M)and

Warning: This patch contains a branched or advanced version of the following
files:

$fpa patch/115/sql FPAVINVB.pls 115.31
$fpa patch/115/sql FPAVINVS.pls 115.26
$fpa patch/115/sql fpadrpobjs.sql 115.59
$fpa patch/115/sql fpastrobj.sql 115.29

This fix may be overwritten if you apply a more current patchset or any other
one-off patch.

Please contact Oracle Worldwide Support with any questions concerning accepting
this patch.

Description
1. Description

Old Behavior
-------------
Patch application failure was seen on applying MRUP4 patch
after applying MRUP3 patch.

New Behavior
-------------
Patch application will not fail on aplying MRUP4 after
applying MRUP3.

2. Pre-requisite or Co-requisite which is not included with this patch:

None

3.Patch Applicable for versions/releases:

This patch is a Pre Install patch to be applied
After applying patch - #5105878: Oracle Projects Rollup Patch 3 for Oracle
Projects Family Pack M (11i.PJ_PF.M)

AND

Before applying patch - 5644830
# Oracle Projects Rollup Patch 4 for Oracle Projects Family Pack M (11i.PJ_PF.M)

4.Dependent Applications:
None

5.Patch to be applied:
Server

6.Patch applicable only when a particular application installed:
Oracle Projects

7.Pre-patch application steps
None

8.Post patch application steps

9.Successful patch installation checks:
Please check the log files after patch application for errors(if any).
Adpatch should be through without errors.

PATCH 5644830 ROLLUP PATCH 4 FOR ORACLE PROJECTS FAMILY PACK M

Install the Oracle Projects Rollup Patch 4 for Oracle Projects Family Pack M only after installing Oracle Projects Family Pack M (11i.PJ_PF.M) (patch 3485155 OracleMetaLink Note 302074.1

Oracle Projects Rollup Patch 4 for Oracle Projects Family Pack M (11i.PJ_PF.M)
also includes the features and software updates provided in the following rollup
patches:
. Oracle Project Management Family Pack M Rollup Patch (patch 4461989).
For information about the features and software updates included in
this patch,refer to OracleMetaLink Note 331007.1.
. Oracle Projects Rollup Patch 2 for Oracle Projects Family Pack M
(11i.PJ_PF.M) (patch 4997599). For information about the software
updates included in this patch, refer to OracleMetaLink Note
351048.1.
. Oracle Projects Rollup Patch 3 for Oracle Projects Family Pack M
(11i.PJ_PF.M) (patch 5105878). For information about the features
and software updates included in this patch, refer to OracleMetaLink
Note 361295.1.

Attention:

If you have customized workflow files, please create a backup before applying this patch. Applying this patch will overwrite your customized workflow files.

If you have not applied Oracle Project Management Family Pack M Rollup Patch (patch 4461989), then perform the Pre-Installation Steps and the Functional Prerequisites steps described in the Instructions for Applying Oracle Project Management Family Pack M Rollup Patch section of OracleMetaLink Note 331007.1.

If you have not applied Oracle Projects Rollup Patch 3 for Oracle Projects Family Pack M (patch 5105878), then perform the Pre-Installation Steps and the Functional Prerequisites steps described in the Instructions for Applying Oracle Projects Rollup Patch 3 for Oracle Projects Family Pack M section of OracleMetaLink Note 361295.1.

Additional Functional Prerequisites:

The following table lists patches and steps that are required if you are currently using or planning to use the corresponding features:

Product Feature Prerequisite Patch / Step
Oracle Microsoft Project Projects ADI Functionality for Family N/A
Oracle Transaction Entry Using Projects ADI Functionality for Family N/A
Project Costing Microsoft Excel Interface Pack M Rollup Patch 4 - Patch 5367017

There are no patch application order dependencies between Oracle Projects Rollup
Patch 4 for Oracle Projects Family Pack M and the patch listed in the above table.

The following must be completed after running the unified driver using
AD Administration (adadmin):

1. Generate message files
2. Compile APPS schema(s)
3. Compile flexfield data in AOL tables

Please contact Oracle Worldwide Support with any questions about this patch.

Prerequisite Updates
Please refer to the Pre-Installation Steps and Functional Prerequisites in section 5 of the OracleMetaLink Note 361295.1, About Oracle Projects Rollup Patch 3 for Oracle Projects Family M (11i.PJ_PF.M).

Description
For a list of software updates pertaining to this patch, refer to OracleMetaLink Note 423428.1, Software Updates for Oracle Projects Rollup Patch 4 for Oracle Projects Family Pack M(11i.PJ_PF.M).

PATCH 6410693 - IL SUPPORT FOR PROJECT COSTING.
Before applying the patch, please refer Metalink note 433764.1 to prevent any odf application issues during patch application.

For mutli-node installations, the patch should FIRST be applied on the Database node using argument "mode=D" of the India Localization Patch Application Tool.

Never apply it directly on the Production instance without applying on the test.

This patch replaces CUSTOM.pll on AU_TOP/resource. Refer the "Instructions to merge CUSTOM.pll" section for details.

Pre-requisite steps

1. Oracle Applications Release 11.5.10.2
2. Apply prerequisite patch # 5842122 if you are on 11.5.10 CU2 level.
or
Apply prerequisite patch # 5644830 if you are on Projects Family Pack M level.

3. Follow the below steps :

i) Ensure that you have the following files in JA_TOP/inpatch directory :
a. jai_get_db_obj.sql
b. jai_get_view.sql

ii) Please verify that the patch# 5765161 ( old Project Costing ) is applied by running following query in APPS schema
select * from jai_applied_patches where patch_number = 5765161 ;

a. If the patch# 5765161 is NOT applied then please IGNORE THIS STEP 3 and proceed to next step ( step 4 ).

b. If the patch# 5765161 is applied then perform the below steps :
- Change to "6410693/validation" directory
- Provide execute permissions to jaipatch_validation.pl and execute the below command
on Database, concurrent and forms tiers providing the APPS password.
Command:
perl jaipatch_validation.pl val_file=6410693.val appspwd=
- Ensure that the validation script "jaipatch_validation.pl" completed successfully.

applprod@vezora3:/stage/IN_Localization/6410693 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6410693.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6410693.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 10:12:11 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 10:12:18 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6410693.drv....
Completed Successfully
Populating the database versions for SQL files...
.......
.......
...
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
Object Name
----------------------------------------------------------------------------
jai_pa_costing.pls
jai_pa_tax_pkg.pls
jai_pa_pref_pkg.pls
jai_pa_setup_ctx.pls
jai_pa_billing_pkg.pls
jainexsc_s.sql
ja_in_inst_interface_p.sql
jainexsc_b.sql
jai_pa_costing.plb
jai_pa_tax_pkg.plb
jai_pa_pref_pkg.plb
jai_pa_setup_ctx.plb
jai_pa_billing_pkg.plb
jai_pdia_ariud.sql
ja_in_loc_ar_hdr_update_trg.sql

----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6410693.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 10:15:57 ]

PATCH# 6167056."ENH:SECONDARY AND HIGHER EDUCATION CESS ( BUDGET 2007 )

IMPORATANT NOTE :
If step 3.ii.b is performed and even if Budget 2007 patch is already applied, perform the following :
i) Re-apply the Budget 2007 patch#6167056 using the "India Localization Patch Application Tool" and
ii) Ignore the Pre-patch and Post-patch application steps of the Budget 2007 patch#6167056.

applprod@vezora3:/stage/IN_Localization/6167056 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6167056.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6167056.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 10:24:48 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 10:24:48 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6167056.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
.......
........
...
Backed up objects in /stage/IN_Localization/6167056/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
ja_in_ap_st_forms_insert_p.sql patch/115/sql JA_TOP
ja_in_ar_st_forms_insert.sql patch/115/sql JA_TOP
ja_in_iso_st_forms_insert.sql patch/115/sql JA_TOP
ja_in_con_populate_st_forms_p.sql patch/115/sql JA_TOP
jai115fn_ap_E.ldt patch/115/import/US JA_TOP
jai115fn_ar_E.ldt patch/115/import/US JA_TOP
jai115fn_fa_E.ldt patch/115/import/US JA_TOP
jai115fn_inv_E.ldt patch/115/import/US JA_TOP
jai115fn_ont_E.ldt patch/115/import/US JA_TOP
jai115fn_po_E.ldt patch/115/import/US JA_TOP
jai115lu_E.ldt patch/115/import/US JA_TOP
jai115mg_E.ldt patch/115/import/US JA_TOP
jai115_falku.ldt patch/115/import/US JA_TOP
jai115cp_F.ldt patch/115/import/US JA_TOP
jai115df_E.ldt patch/115/import/US JA_TOP
jai115st_fndrssub724_E.ldt patch/115/import/US JA_TOP
jai115st_fndrssub724_links_E.ldt patch/115/import/US JA_TOP
jai115rg_E.ldt patch/115/import/US JA_TOP
jai115pr_E.ldt patch/115/import/US JA_TOP
jai115_glcat.ldt patch/115/import/US JA_TOP
jai115glsrc.ldt patch/115/import/US JA_TOP
ja_in_reqn_curr_upd_trg.sql patch/115/sql JA_TOP
ja_in_tran_rg_entry_trg.sql patch/115/sql JA_TOP
ja_in_mass_tax_changes_p.sql patch/115/sql JA_TOP
ja_in_create_57f4_trg.sql patch/115/sql JA_TOP
ja_in_create_releases_57f4.sql patch/115/sql JA_TOP
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6167056.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 10:27:08 ]

Automated Patch Application Steps
=================================
If you have applied the patch 6059025 from metalink (India Localization Patch Application Tool), you should be able to apply this patch using that tool. Please follow the user manual supplied in the patch 6059025 to apply this patch. You will need to perform the following 3 steps:

1) Extract this patch zip file to a temporary directory.
2) Change directory to 6410693.
3) Proceed as instructed in the automated patch tool user manual.

Post-Patch Application Steps
=============================

1. Report any invalids by running the following perl script from $JA_TOP/inpatch :
perl compile_il_apps_obj.pl appspwd=

In case of invalids, please log a service request with India Localization support providing the script generated log "invalid_il_objects.log".

2. Please ask the functional users to go through "India Localization Support for Project Costing.pdf" available in the "Documents" folder for understanding the setup and change of behavior with this patch.

3. Apply the post mandatory Budget patch# 6397595

4. If you are on 11i.PA.M ( Projects Family Pack M ) level, please apply the patch# 6344634

Instructions to merge CUSTOM.pll
================================
The CUSTOM.pll is backed-up in patch/backup/resource directory before getting overwritten by the CUSTOM.pll included in this patch.
The customization present in patch/backup/resource/CUSTOM.pll should be added to AU_TOP/resource/CUSTOM.pll and the CUSTOM.plx re-generated.
To re-generate the CUSTOM.plx use the below command providing the :
f60gen module=CUSTOM userid=apps/ module_type=LIBRARY

applprod@vezora3:/stage/IN_Localization/6410693 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6410693.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6410693.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 10:35:43 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 10:35:43 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6410693.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
…..
……..
…..
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6410693/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
jai_cmn_dbg_ctx.pls patch/115/sql JA_TOP
jai_pa_cmt_txn_v.sql patch/115/sql JA_TOP
ja_in_balance_transfer.sql patch/115/sql JA_TOP
ja_in_inst_interface_p.sql patch/115/sql JA_TOP
jai_cmn_dbg_ctx.plb patch/115/sql JA_TOP
JAI_ARSETUP_E.ldt patch/115/import/US JA_TOP
JAI_ARSETUP_F.ldt patch/115/import/US JA_TOP
TAX_TYPE_PO_E.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_E.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_F.ldt patch/115/import/US JA_TOP
JAI_TRX_SRC_PA.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_IPROC_E.ldt patch/115/import/US JA_TOP
JAINTCSCR_JA_F.ldt patch/115/import/US JA_TOP
JAINITCR_SQLAP_F.ldt patch/115/import/US JA_TOP
RCV_SHIPMENT_HEADERS_2_E.ldt patch/115/import/US JA_TOP
JAI_PROFILES_IPOC_E.ldt patch/115/import/US JA_TOP
ja_in_tran_rg_entry_trg.sql patch/115/sql JA_TOP
ja_in_loc_ar_hdr_update_trg.sql patch/115/sql JA_TOP
ja_in_reqn_curr_upd_trg.sql patch/115/sql JA_TOP

----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************

----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6410693.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 10:36:05 ]

PATCH 6410725 - IL SUPPORT FOR PROJECT BILLING SOLUTION
Before applying the patch, please refer Metalink note 433764.1 to prevent any odf
application issues during patch application.

-- Issue # 1 : 'JA%' sequence should not exist in the APPS Schema

-- Step 1. Check for sequences created in APPS schema by using the following query executed in APPS schema :

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS
WHERE OBJECT_NAME LIKE 'JA%' AND OBJECT_TYPE = 'SEQUENCE' AND OWNER = 'APPS';

Expected o/p:
no rows returned

--Step 2. For each sequence returned by query in Step 1, check if the sequence exists in JA schema.

--If the sequence exists in JA schema, the below query will return a row :

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS
WHERE OBJECT_NAME = '' AND OBJECT_TYPE = 'SEQUENCE' AND OWNER = 'JA';

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME = 'JA_IN_BATCH_NUMBER' AND OBJECT_TYPE = 'SEQUENCE' AND OWNER = 'JA';

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME = 'JA_IN_LC_MASTER_S' AND OBJECT_TYPE = 'SEQUENCE' AND OWNER = 'JA';

--Step 3. If sequence exists in JA schema then connect to JA schema and perform the following :

--a. Execute the following query and note the value returned by the query :
SELECT JA..NEXTVAL FROM DUAL ;

--b. DROP SEQUENCE JA. ;

--Step 4. Connect to APPS schema and perform the following :

--a. Execute the following query and note value returned by the query :
SELECT APPS..NEXTVAL FROM DUAL ;

SELECT APPS.JA_IN_BATCH_NUMBER.NEXTVAL FROM DUAL ; -- result 1

SELECT APPS.JA_IN_LC_MASTER_S.NEXTVAL FROM DUAL ; -- result 1

b. DROP SEQUENCE APPS. ;

DROP SEQUENCE APPS.JA_IN_BATCH_NUMBER ;

DROP SEQUENCE APPS.JA_IN_LC_MASTER_S ;

--Step 5. Connect to JA schema, replace the with the MAXIMUM value obtained in Step3.a. , Step4.a

CREATE SEQUENCE JA. START WITH INCREMENT BY 1 CACHE 20;

CREATE SEQUENCE JA.JA_IN_BATCH_NUMBER START WITH 1 INCREMENT BY 1 CACHE 20;

CREATE SEQUENCE JA.JA_IN_LC_MASTER_S START WITH 1 INCREMENT BY 1 CACHE 20;

GRANT ALL ON JA. TO APPS;

GRANT ALL ON JA.JA_IN_BATCH_NUMBER TO APPS;

GRANT ALL ON JA.JA_IN_LC_MASTER_S TO APPS;

--Step 6. Connect to APPS schema and create the synonym for the sequence using :

CREATE SYNONYM APPS. FOR JA. ;

CREATE SYNONYM APPS.JA_IN_BATCH_NUMBER FOR JA.JA_IN_BATCH_NUMBER ;

CREATE SYNONYM APPS.JA_IN_LC_MASTER_S FOR JA.JA_IN_LC_MASTER_S ;

--Issue # 2 : No 'JA%' table should not exist in the APPS Schema

--Step 1. Check for tables created in APPS schema by using the following query executed in APPS schema :

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME LIKE 'JA%' AND OBJECT_TYPE = 'TABLE' AND OWNER = 'APPS';

Expected o/p:
no rows returned

--Step 2. For each table returned by query in Step 1, check if the table exists in JA schema.

--If the table exists in JA schema, the below query will return a row :

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME = '' AND OBJECT_TYPE = 'TABLE' AND OWNER = 'JA';

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME = 'JA_IN_AP_TDS_SERVICES_TMP' AND OBJECT_TYPE = 'TABLE' AND OWNER = 'JA';

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME = 'JA_IN_PO_ST_FORMS_DTL_TEMP' AND OBJECT_TYPE = 'TABLE' AND OWNER = 'JA';

SELECT OBJECT_NAME, OBJECT_TYPE, OWNER FROM ALL_OBJECTS WHERE OBJECT_NAME = 'JA_IN_PO_ST_FORMS_HDR_TEMP' AND OBJECT_TYPE = 'TABLE' AND OWNER = 'JA';

--Step 3.
--CASE A : If table does not exist in JA schema, then connect to JA schema and perform the following :

a. CREATE TABLE JA. AS SELECT * FROM APPS. ;
--Connect as apps

grant select on APPS.JA_IN_AP_TDS_SERVICES_TMP to ja;

grant select on APPS.JA_IN_PO_ST_FORMS_DTL_TEMP to ja;

grant select on APPS.JA_IN_PO_ST_FORMS_HDR_TEMP to ja;

CREATE TABLE JA.JA_IN_AP_TDS_SERVICES_TMP AS SELECT * FROM APPS.JA_IN_AP_TDS_SERVICES_TMP;

CREATE TABLE JA.JA_IN_PO_ST_FORMS_DTL_TEMP AS SELECT * FROM APPS.JA_IN_PO_ST_FORMS_DTL_TEMP ;

CREATE TABLE JA.JA_IN_PO_ST_FORMS_HDR_TEMP AS SELECT * FROM APPS.JA_IN_PO_ST_FORMS_HDR_TEMP ;

b. DROP TABLE APPS. ;

DROP TABLE APPS.JA_IN_AP_TDS_SERVICES_TMP;

DROP TABLE APPS.JA_IN_PO_ST_FORMS_DTL_TEMP ;

DROP TABLE APPS.JA_IN_PO_ST_FORMS_HDR_TEMP ;

--CASE B : If the table exists in JA schema, then

--a. Migrate the data from table in APPS schema to table in JA schema using following insert.

INSERT INTO JA. ( ) SELECT FROM APPS. ;
COMMIT;

b. DROP TABLE APPS. ;

For mutli-node installations, the patch should FIRST be applied on the Database node
using argument "mode=D" of the India Localization Patch Application Tool.
Never apply it directly on the Production instance without applying on the test.

This patch replaces CUSTOM.pll on AU_TOP/resource.
Refer the "Instructions to merge CUSTOM.pll" section for details.

Pre-requisite steps
1. Oracle Applications Release 11.5.10.2

2. Copy the following files patch 6410725 directory to $JA_TOP/patch/115/import directory
i) patch/115/import/jaipaprf.lct
ii) patch/115/import/jaipacxdef.lct

applprod@vezora3:/stage/IN_Localization/6410725/patch/115/import
$ cp jaipacxdef.lct jaipaprf.lct /u01/DEV3/apps/prodappl/ja/11.5.0/patch/115/import/

3. Follow the below steps :

i) Ensure that you have the following files in JA_TOP/inpatch directory :
a. jai_get_db_obj.sql
b. jai_get_view.sql

ii) Please verify that the patch# 5876390 ( old Projects Billing ) is applied by running following query in APPS schema

select * from jai_applied_patches where patch_number = 5876390 ;

a. If the patch# 5876390 is NOT applied then please IGNORE THIS STEP 3 and proceed to next step ( step 4 ).

b. If the patch# 5876390 is applied then perform the below steps :
- Change to "6410725/validation"
- Provide execute permissions to jaipatch_validation.pl and execute the below command
on Database, concurrent and forms tiers providing the APPS password.
Command:
perl jaipatch_validation.pl val_file=6410725.val appspwd=
- Ensure that the validation script "jaipatch_validation.pl" completed successfully.

4. Apply the "ENH:SECONDARY AND HIGHER EDUCATION CESS ( BUDGET 2007 )" patch# 6167056.

IMPORATANT NOTE :
If step 3.ii.b is performed and even if Budget 2007 patch is already applied, perform the following :
i) Re-apply the Budget 2007 patch#6167056 using the "India Localization Patch Application Tool" and
ii) Ignore the Pre-patch and Post-patch application steps of the Budget 2007 patch#6167056.

Automated Patch Application Steps
=================================
If you have applied the patch 6059025 from metalink (India Localization Patch Application Tool), you should be able to apply this patch using that tool. Please follow the user manual supplied in the patch 6059025 to apply this patch. You will need to perform the following 3 steps:

1) Extract this patch zip file to a temporary directory.
2) Change directory to 6410725.
3) Proceed as instructed in the automated patch tool user manual.

applprod@vezora3:/stage/IN_Localization/6410725 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6410725.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6410725.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 10:40:33 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 10:40:33 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6410725.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
………
………..
…………….
----------------------------------------------------------------------------
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6410725/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
jai_cmn_dbg_ctx.pls patch/115/sql JA_TOP
ja_in_balance_transfer.sql patch/115/sql JA_TOP
jai_cmn_dbg_ctx.plb patch/115/sql JA_TOP
JAI_ARSETUP_E.ldt patch/115/import/US JA_TOP
JAI_ARSETUP_F.ldt patch/115/import/US JA_TOP
TAX_TYPE_PO_E.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_E.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_F.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_IPROC_E.ldt patch/115/import/US JA_TOP
JAI_RESPONSIBILITIES_E.ldt patch/115/import/US JA_TOP
JAINTCSCR_JA_F.ldt patch/115/import/US JA_TOP
JAINITCR_SQLAP_F.ldt patch/115/import/US JA_TOP
RCV_SHIPMENT_HEADERS_2_E.ldt patch/115/import/US JA_TOP
OTHER_AR_E.ldt patch/115/import/US JA_TOP
JAI_PROFILES_IPOC_E.ldt patch/115/import/US JA_TOP
ja_in_tran_rg_entry_trg.sql patch/115/sql JA_TOP
ja_in_reqn_curr_upd_trg.sql patch/115/sql JA_TOP

----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************

----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6410725.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 10:41:08 ]

applprod@vezora3:/stage/IN_Localization/6410725 $

Post-Patch Application Steps

1. Attach "India Local Project Billing" responsibility to application user
2. Report any invalids by running the following perl script from $JA_TOP/inpatch :
perl compile_il_apps_obj.pl appspwd=

applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/inpatch $ perl compile_il_apps_obj.pl appspwd=k3ob3ia
Compiling the APPS schema
.. .. .. .. .. completed with no invalids.
You have new mail in /var/spool/mail/applprod
applprod@vezora3:/u01/DEV3/apps/prodappl/ja/11.5.0/inpatch $

In case of invalids, please log a service request with India Localization support providing the script generated log "invalid_il_objects.log".

3. Please ask the functional users to go through "India Localization Support for Project Billing.pdf" available in the "Documents" folder for understanding the setup and change of behavior with this patch.

PATCH 637595 POST MANDATORY BUDGET PATCH 2007 ON TOP OF IPROC/ISUPP/PROJECTS/ENCUMBRANCE

4. Apply the post mandatory Budget patch# 6397595

applprod@vezora3:/stage/IN_Localization/6397595 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6397595.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6397595.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 11:01:40 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 11:01:40 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6397595.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
…..
…….
…..
Backed up objects in /stage/IN_Localization/6397595/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
ja_in_tax_pkg.sql patch/115/sql JA_TOP
ja_in_distribution_matching_p.sql patch/115/sql JA_TOP
ja_in_pay_on_recpt_dist_match_p.sql patch/115/sql JA_TOP
ja_in_receipts_p.sql patch/115/sql JA_TOP
ja_in_apportion_factor_ap_tax.sql patch/115/sql JA_TOP
jai_ractl_trg.plb patch/115/sql JA_TOP
jai_rgm_trx_processing_pkg_b.sql patch/115/sql JA_TOP
jai_trx_repo_ext.plb patch/115/sql JA_TOP
jai_rgm_om_ar_vat_accounting_pkg_b.sql patch/115/sql JA_TOP
jai_stforms_prc.plb patch/115/sql JA_TOP
jai115fn_ap_E.ldt patch/115/import/US JA_TOP
jai115fn_ar_E.ldt patch/115/import/US JA_TOP
jai115fn_fa_E.ldt patch/115/import/US JA_TOP
jai115fn_inv_E.ldt patch/115/import/US JA_TOP
jai115fn_ont_E.ldt patch/115/import/US JA_TOP
jai115fn_po_E.ldt patch/115/import/US JA_TOP
jai115lu_E.ldt patch/115/import/US JA_TOP
jai115mg_E.ldt patch/115/import/US JA_TOP
jai115_falku.ldt patch/115/import/US JA_TOP
jai115cp_F.ldt patch/115/import/US JA_TOP
jai115df_E.ldt patch/115/import/US JA_TOP
jai115st_fndrssub724_E.ldt patch/115/import/US JA_TOP
jai115st_fndrssub724_links_E.ldt patch/115/import/US JA_TOP
jai115rg_E.ldt patch/115/import/US JA_TOP
jai115pr_E.ldt patch/115/import/US JA_TOP
jai115_glcat.ldt patch/115/import/US JA_TOP
jai115glsrc.ldt patch/115/import/US JA_TOP
ja_in_apps_ar_lines_insert_trg.sql patch/115/sql JA_TOP
ja_in_tran_rg_entry_trg.sql patch/115/sql JA_TOP
JAINPO.fmb forms/US /u01/DEV3/apps/prodappl/au/11.5.0/forms/US
JAINPORE.fmb forms/US /u01/DEV3/apps/prodappl/au/11.5.0/forms/US
JAINREQN.fmb forms/US /u01/DEV3/apps/prodappl/au/11.5.0/forms/US
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6397595.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 11:02:47 ]

Instructions to merge CUSTOM.pll
================================
The CUSTOM.pll is backed-up in patch/backup/resource directory before getting overwritten by the CUSTOM.pll included in this patch.

The customization present in patch/backup/resource/CUSTOM.pll should be added to AU_TOP/resource/CUSTOM.pll and the CUSTOM.plx re-generated.

To re-generate the CUSTOM.plx use the below command providing the :
f60gen module=CUSTOM userid=apps/ module_type=LIBRARY

Total Time 5 minutes
PATCH 6410766 - IL SUPPORT FOR ISUPPLIER
Steps :

i) Ensure that you have the following files in JA_TOP/inpatch directory :
a. jai_get_db_obj.sql
b. jai_get_view.sql

Verify that the patch# 5961325 is applied by running following query in APPS schema

SQL*Plus: Release 9.2.0.8.0 - Production on Wed Aug 20 11:06:20 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> select * from jai_applied_patches where patch_number = 5961325 ;
no rows selected

If the patch# 5961325 is NOT applied then IGNORE THIS STEP 2 and proceed to step 3.

b. If the patch# 5961325 is applied then perform the below steps :
- Change to "6410766/validation" directory
- Provide execute permissions to jaipatch_validation.pl and execute the below command
on Database, concurrent and forms tiers providing the APPS password.
Command:
perl jaipatch_validation.pl val_file=6410766.val appspwd=xxxxx

- Ensure that the validation script "jaipatch_validation.pl" completed successfully.

3. Apply the "ENH:SECONDARY AND HIGHER EDUCATION CESS ( BUDGET 2007 )" patch# 6167056.

IMPORATANT NOTE :
If step 2.ii.b is performed and even if Budget 2007 patch is already applied, perform the following :
i) Re-apply the Budget 2007 patch#6167056 using the "India Localization Patch Application Tool" and
ii) Ignore the Pre-patch and Post-patch application steps of the Budget 2007 patch#6167056.

1) Extract this patch 6410766 zip file to a temporary directory.
2) Change directory to 6410766.
3) Proceed as instructed in the automated patch tool user manual.

applprod@vezora3:/stage/IN_Localization/6410766 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6410766.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6410766.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 11:12:10 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 11:12:10 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6410766.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
………..
……….
……….
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6410766/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
jai_cmn_dbg_ctx.pls patch/115/sql JA_TOP
ja_in_inst_interface_p.sql patch/115/sql JA_TOP
ja_in_po_calc_tax_p.sql patch/115/sql JA_TOP
ja_in_balance_transfer.sql patch/115/sql JA_TOP
jai_po_hook_pkg.plb patch/115/sql JA_TOP
jai_cmn_dbg_ctx.plb patch/115/sql JA_TOP
TAX_TYPE_PO_E.ldt patch/115/import/US JA_TOP
JAI_ARSETUP_E.ldt patch/115/import/US JA_TOP
JAI_ARSETUP_F.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_IPROC_E.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_E.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_F.ldt patch/115/import/US JA_TOP
RCV_SHIPMENT_HEADERS_2_E.ldt patch/115/import/US JA_TOP
JAINITCR_SQLAP_F.ldt patch/115/import/US JA_TOP
JAINTCSCR_JA_F.ldt patch/115/import/US JA_TOP
ja_in_loc_ar_hdr_update_trg.sql patch/115/sql JA_TOP
ja_in_reqn_curr_upd_trg.sql patch/115/sql JA_TOP
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6410766.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 11:14:00 ]
applprod@vezora3:/stage/IN_Localization/6410766 $

Post-Patch Application Steps

1. Perform the following steps to apply the RCV_SHIPMENT_HEADERS DFF :
i. Please note any customization done to RCV_SHIPMENT_HEADERS DFF.
ii. Run the below command in the patch directory :
a. If you are on FND patchset C, then replace with RCV_SHIPMENT_HEADERS_2_C.ldt.
b. If you are on FND patchset D or above, then replace with RCV_SHIPMENT_HEADERS_2_E.ldt.
c. Replace with password of APPS user.
FNDLOAD apps/ 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct patch/115/import/US/ - CUSTOM_MODE=FORCE
iii. Redo the customization noted in step (a)

2. If you would like to utilize the functionality of Oracle India Local iSupplier, you
must create a custom India Local iSupplier responsibility (as per instructions below) and assign it to users.

To add the Custom responsibility:
a. From the Oracle System Administrator menu, select Security > Responsibility > Define.
b. Enter the following values.
Responsibility Name : XXXXXXXXXX
Application : iSupplier Portal
Responsbility Key : XXXXXXXXXX
Description : XXXXXXXXXX

Available form(Radio button): Select the following
(X) "Oracle Self Service Web Applications"

Data Group:
Name : Standard
Application : iSupplier Portal

Menu : "ILS iSupplier Portal New Application Menu" (Please note that this menu contains personalized IL functions)

Apply Securing Attributes to Custom Responsibility

There are three securing attributes that can be used to control access. These attributes are all seeded with the pre-defined Oracle iSupplier Portal responsibilities that are released with the product: (Please refer iSupplier implementation guide for details)

? ICX_SUPPLIER_ORG_ID - Identifier for the supplier.
? ICX_SUPPLIER_SITE_ID - Identifier for the supplier site.
? ICX_SUPPLIER_CONTACT_ID - Identifier for the supplier contact.

1. Select Securing Attributes region in Responsibility form, search for the three securing
attributes that have to be applied to this responsibility.
2. When you have identified all the attributes to apply to this responsibility,
select ICX_SUPPLIER_CONTACT_ID > click Values button and give ?9999,
select ICX_SUPPLIER_SITE_ID > Click Values button and give -9999.

d. Click Save.

ii. Assign Responsibilities to Users
-----------------------------------------
a. From the Oracle System Administrator menu, select Security > User > Define.
b. Enter the name of the user to whom you wish to grant the responsibility.
c. In the Direct Responsibilities section, enter the custom responsibility in the
Responsibility text box.
d. Click Save.

3. Also please ask the functional users to go through "India Localization iSupplier URM.pdf" available in the "Documents" folder for understanding the setup and change of behavior with this patch

4. No further personalizations should be done on top of India Localization personalizations.

5. Apply the post mandatory Budget patch# 6397595 already applied

PATCH 6410797 - IL SUPPORT FOR INDIA IPROCUREMENT.
Before applying the patch, please refer Metalink note 433764.1 to prevent any odf application issues during patch application.

For mutli-node installations, the patch should FIRST be applied on the Database node using argument "mode=D" of the India Localization Patch Application Tool.

Steps :

i) Ensure that you have the following files in JA_TOP/inpatch directory :
a. jai_get_db_obj.sql
b. jai_get_view.sql

ii) Please verify that the patch# 6012240 ( old iProcurement ) is applied by running following query in APPS schema

select * from jai_applied_patches where patch_number = 6012240 ;

If the patch# 6012240 is NOT applied then please IGNORE THIS STEP 3 and proceed to next step ( step 3 ).

If the patch# 6012240 is applied then perform the below steps :
- Change to "6410797/validation" directory
- Provide execute permissions to jaipatch_validation.pl and execute the below command
on Database, concurrent and forms tiers providing the APPS password.
Command:
perl jaipatch_validation.pl val_file=6410797.val appspwd=
- Ensure that the validation script "jaipatch_validation.pl" completed successfully.

Extract this patch 6410797 zip file to a temporary directory.

applprod@vezora3:/stage/IN_Localization/6410797 $ ls
6410797.drv admin documents forms jai_6410797.sql mds oracle patch Readme_6410797.txt reports resource validation

applprod@vezora3:/stage/IN_Localization/6410797 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6410797.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6410797.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 11:20:53 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 11:20:53 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6410797.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
…..
….
..

Copied oracle/apps/ja/por/reqmgmt/webui/ILExpSearchCO.class successfully to /u01/DEV3/apps/prodcomn/java/oracle/apps/ja/por/reqmgmt/webui.
Copied oracle/apps/ja/icatalog/shopping/webui/ILItemCompareCO.class successfully to /u01/DEV3/apps/prodcomn/java/oracle/apps/ja/icatalog/shopping/webui.
Copied oracle/apps/ja/icatalog/shopping/webui/ILShoppingClientHelper.class successfully to /u01/DEV3/apps/prodcomn/java/oracle/apps/ja/icatalog/shopping/webui.
Copied oracle/apps/ja/reqn/webui/ILSearchResultsCO.class successfully to /u01/DEV3/apps/prodcomn/java/oracle/apps/ja/reqn/webui.
Copied oracle/apps/ja/icatalog/shopping/webui/ILAdvancedSearchCO.class successfully to /u01/DEV3/apps/prodcomn/java/oracle/apps/ja/icatalog/shopping/webui.
Copied oracle/apps/ja/por/req/webui/ILReqDescCO.class successfully to /u01/DEV3/apps/prodcomn/java/oracle/apps/ja/por/req/webui.
----------------------------------------------------------------------------
Copying rdfs.
----------------------------------------------------------------------------
******************* No rdf files to copy ********************
----------------------------------------------------------------------------
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6410797/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
ja_in_balance_transfer.sql patch/115/sql JA_TOP
TAX_TYPE_PO_E.ldt patch/115/import/US JA_TOP
JAI_ARSETUP_E.ldt patch/115/import/US JA_TOP
JAI_ARSETUP_F.ldt patch/115/import/US JA_TOP
JAI_MESSAGES_IPROC_E.ldt patch/115/import/US JA_TOP
JAINITCR_SQLAP_F.ldt patch/115/import/US JA_TOP
JAINTCSCR_JA_F.ldt patch/115/import/US JA_TOP
JAI_PROFILES_IPOC_E.ldt patch/115/import/US JA_TOP
ja_in_reqn_tax_update_trg.sql patch/115/sql JA_TOP
ja_in_reqn_curr_upd_trg.sql patch/115/sql JA_TOP
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6410797.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 11:22:19 ]
applprod@vezora3:/stage/IN_Localization/6410797 $

Post-Patch Application Steps

1. If you would like to utilize the functionality of Oracle India Local iProcurement, you
must create a custom India Local iProcurement responsibility (as per instructions below) and assign it to users.

i. To add the Custom responsibility:
---------------------------------
a. From the Oracle System Administrator menu, select Security > Responsibility > Define.
b. Enter the following values.
Responsibility Name : XXXXXXXXXX
Application : Self-Service Web Applications
Responsbility Key : XXXXXXXXXX
Description : XXXXXXXXXX

Available form(Radio button): Select the following
(X) "Oracle Self Service Web Applications"

Data Group:
Name : Standard
Application : Self-Service Web Applications

Menu : "India Local Procurement home" (Please note that this menu contains personalized IL functions)

d. Click Save.

ii. Assign Responsibilities to Users
--------------------------------
a. From the Oracle System Administrator menu, select Security > User > Define.
b. Enter the name of the user to whom you wish to grant the responsibility.
c. In the Direct Responsibilities section, enter the custom responsibility in the
Responsibility text box.
d. Click Save.

iii.Assign User Authorisations
--------------------------
Two new Profiles specific to iProcurement for IL Support are added to System Profile Values to restrict tax modification and entry:
a. ?IL: Access iProcurement Tax information? - Authority to modify IL taxes in iProcurement
b. ?IL: Allow iProcurement RTV CENVAT Process? - Authority to claim CENVAT during iProcurement Return to Vendor transactions.
c. Default values for these profiles are set to ?NO? implying No authorization.System Administrators should set the profile values to each iProcurement users with appropriate values to ensure the proper user authorization levels.

2. Also please ask the functional users to go through "India Localization iProcurement URM.pdf" available in the "Documents" folder for understanding the setup and change of behavior with this patch

3. No further personalizations should be done on top of India Localization personalizations.

4. Apply the post mandatory Budget patch# 6397595

5. Report any invalids by running the following perl script from $JA_TOP/inpatch :
perl compile_il_apps_obj.pl appspwd=

In case of invalids, please log a service request with India Localization support providing the script generated log "invalid_il_objects.log".

Total Time 5 minutes

PATCH 6053828 IN_LOCALIZATION TAXES WERE NOT CONSIDERED IN ENCUMBRANCE ACCOUNTING
Using adapatch
Old Behaviour

In Oracle Purchasing, India Localization Taxes were Not considered in Encumbrance Accounting.

New Behaviour
In Oracle Purchasing, India Localization Taxes are Now considered in Encumbrance Accounting.

Patch Applicable for versions/releases:
This patch is applicable only on top of Oracle Applications release 11.5.10 and/or Supply Chain Management Family Pack J.

Done 10 minutes
PATCH 5883053 ATO MODEL NOT GETTING INVOICED WHEN CONFIG ITEMS ARE NOT INVOICE ENABLED.
This patch requires additional prerequisite patches to have been successfully applied to your system before it can be applied.

Prerequisite patches,
3167649 - AOL/FLEXFIELDS ROLLUP PATCH I (OCT/2004) already applied
3582074 - AD_TSPACE_UTIL API PREREQ PATCH already applied
2032040 - WORKFLOW 2.6 FOR APPLICATIONS 11I already applied
2385942 - AOL/CONCURRENT PROCESSING ROLLUP PATCH C already applied
3562652 - AOL/AFMDMSG.LCT PREREQ PATCH C already applied
2733334 - AOL/CP JAVA ROLLUP PATCH A (JAN/2003) already applied
3313183 - AOL/AFDICT.LCT PREREQ PATCH C already applied

Old Behaviour
In Oracle Inventory for ATO item, "Create Intercompany AR Invoice" program was not invoicing ATO model item when the following conditions satisfy
1) Sales Order flow with 'Old Accounting'
2) Profile "INV: Use Model & Options for Configuration Pricing" is 'Y'
3) The configured item is not Invoice Enabled

New Behaviour

In Oracle Inventory for ATO item, "Create Intercompany AR Invoice" program is invoicing ATO model item when the following conditions satisfy.
1) Sales Order flow with 'Old Accounting'
2) Profile "INV: Use Model & Options for Configuration Pricing" is 'Y'
3) The configured item is not Invoice Enabled

Note :

The issue is fixed in Release 12 , patch 5373455

Patch Applicable for versions/releases:
Inventory patchset 'J' / SCM Family Pack J

Patch applicable only when a particular application installed:
Oracle Inventory

Successful patch installation checks:
The version of $INV_TOP/lib/inliar.o should be 115.99.115100.27

Done 40 minutes
PATCH 6030861CST:COSTING CHANGES TO SUPPORT INDIA LOCALIZATION SUPPORT FOR ENCUMBERANCE
1. Pre-requisite should be applied before applying this patch.
• Patch 2177442 (or AD MiniPack "F" or higher).
• Patch 5883053

8. Post patch application steps
Launch the cost manager after application of patch.

9. Successful patch installation checks:
Verify the version of following files as:
$BOM_TOP/patch/115/sql/CSTACDPB.pls 115.58.115100.23
$BOM_TOP/patch/115/sql/CSTAVCPB.pls 115.64.115100.32
$BOM_TOP/patch/115/sql/CSTAVCPS.pls 115.10.115100.4
$BOM_TOP/patch/115/sql/CSTCOHKB.pls 115.0.115100.3
$BOM_TOP/patch/115/sql/CSTCOHKS.pls 115.0.115100.2
$PO_TOP/patch/115/sql/RCVVRUTB.pls 115.30.11510.14
$INV_TOP/src/inltcp.lpc 115.120.115100.34

Description
Old Behavior:
In Oracle cost management, Encumbrance amount does not includes localization taxes while creating Encumbrance reversal entry.

New Behavior:
In Oracle cost management, Encumbrance amount includes localization taxes while creating Encumbrance reversal entry

Done 40 minutes
PATCH 6372361 - IL SUPPORT FOR ENCUMBRANCE ACCOUNTING
Pre-requisites

• Oracle Applications 11.5.10.CU2 or above
• 6167056 ( IL Budget Patch. To be applied using IL patch tool ) already applied
• 6053828 already applied
• 6030861 already applied

Apply the above mentioned ADPATCH compliant patches in 3 and 4 along with their prerequisites as mentioned in their corresponding Readme.

Automated Patch Application Steps

1) Extract this patch zip file to a temporary directory.
2) Change directory to 6372361.
3) Proceed as instructed in the automated patch tool user manual.

Post-Patch Application Steps

1. Apply the post mandatory Budget patch# 6397595

Special Instructions
Please ask the functional users to go through "IL Support for Encumbrance - URM.pdf" for understanding the change of behavior with this patch.

applprod@vezora3:/stage/IN_Localization/6372361
applprod@vezora3:/stage/IN_Localization/6372361 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6372361.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6372361.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 12:13:04 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 12:13:05 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6372361.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully

.............
............
.....

Copying rdfs.
----------------------------------------------------------------------------
******************* No rdf files to copy ********************
----------------------------------------------------------------------------
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6372361/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
CSTCOHKB.pls patch/115/sql Database
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
Object Name
----------------------------------------------------------------------------
jai_encum_prc.pls
jai_encum_prc.plb
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6372361.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 12:13:08 ]
applprod@vezora3:/stage/IN_Localization/6372361 $

Total Time 4 minutes

PATCH 6397595 - POST MANDATORY BUDGET PATCH 2007
This Patch should be applied ONLY using the India Localization Automated Patch
This patch delivers the following bug-fixes :
Patch# Description
6356777 PG:INDIA - BOE WRITE OFF REPORT GOING IN ERROR....
6324933 JAINSTFM(11.5.10.6107.2) HAS PARTY NUMBER INSTEAD OF CUSTOMER NUMBERS.
6316046 ETDS OUTPUT FAILS DURING VALIDATION
6309878 INDIA L TAXES ARE NOT DEFAULTING IN RMA SALES ORDER WITH REF AS SALES ORDER
6278839 'INDIA - STATEMENT OF ACCOUNTS FOR THE SUPPLIER' NOT GIVING CORRECT INFORMATION
6242698 INDIA DEBTORS LEDGERR NOT REFLECTING CORRECT BALANCE FOR NEGATIVE CREDIT MEMO
6242362 INDIA LOCAL-ORGANISAITON ADDITIONAL INFO-S&H ACCOUNTS NOT SAVED
6209421 ADJ TO ACCTD AMOUNTS OF RECEIPT NOT REFLECTED CORRECTLY IN INDIA CASH BANK
6208777 INDIA LOC - INVOICE GETTING GENERATED WITH WRONG ACCOUNTING IN DISTRIBUTION
6169382 VAT IS NOT CALCULATED ON VAT ASSESSABLE PRICE LIST
6164511 INDIA LOCAL-CTO: PLAREG NOT GEN, AR TAXES NOT UPDATED, SPLIT SHOWS WRONG VAT AV
6156969 INDIA LOCALIZATIONS: TDS AMOUNT IS BEING WRONGLY COMPUTED IN ETDS RETURNS
6153922 6079248 PATCH SHOWS ***ERROR! COULD NOT GENERATE JAINTSLS.REP. SKIPPING..
6147494 INDIA CTO * ITEM: VAT AV DEFAULTS TO ZERO, ORA-20001: APP-: CANNOT FIND ITEM
6138127 INDIA LOC- CTO RMA CREDIT MEMO CREATED WITHOUT LOCALISATON TAXES
6124751 BUDGET 0708 PATCHES APPLIED - TDS CERTIFICATES COMING ON THE BASIS OF CHECK IDS
6115608 RG23D SCREEN SHOWS ERROR FOR SUPPLIER NAME MORE THAN 60 CHARACTERS
6113456 FRM 40735 KEY COMMIT TRIGGER - RG CONSOLIDATION SCREEN
6110274 DISCOUNT IS NOT GETTING CALCULATED AS PER THE DEFINED IN THE PAYMENT TREMS
6084692 CORRECT TAXES ARE APPEAR IN THE RECEIPTS ONLY AFTER CLICKING THE APPLY BUTTON
6081946 IMPROPER TDS CERTIFICATE FORMAT AND INCORRECT DATA
6081519 EXCISE INVOICE NUMBER NOT DISPLAYED PROPERLY ON CLAIM MODVAT FORM.
6076466 PROBLEM IN "INDIA - CREDITORS TRIAL BALANCE REPORT"

3) You should read thoroughly the below sections before applying the patch :
- PRE-REQUISITES
- APPLY THE PATCH
- DIAGONIZE PATCH FAILURES ( IF ANY )

PRE-REQUISITES
1. One or more of the following enhancements :
Enhancement Patch delivered ( latest / obsoleted )
IL Support for Project Costing 6410693 / 6141516
IL Support for Project Billing 6410725 / 6141521
IL Support for iSupplier 6410766 / 6141531
IL Support for iProcurement 6410797 / 6141534
IL Support for Encumbrance 6372361 / 6046998

APPLY THE PATCH
This Patch should be applied ONLY using the India Localization Patch Application Tool provided
as patch 6059025. If you have not applied the patch 6059025, please download and apply as
instructed in the readme.

Please go through Automated Patch Application Tool manual and UNDERSTAND THE USAGE OF THE TOOL.
You are requested to raise an SR for any queries regarding the tool.

You will need to perform the following 4 steps :

1) Extract the patch 6397595 zip file to a temporary directory.
2) Change directory to 6397595.
3) Note that the patch application log generated gets appended for every application of the patch.
It is advisable to rename the old log file generated for future reference.
4) Apply the patch as described below based on whether your installation is
single-node or multi-node.
a) Single-node installation
Syntax for applying the patch :
perl $JA_TOP/inpatch/indpatch.pl drvr_file=6397595.drv fnd_patchset= [ other args ]
For details on [ other args ] please refer to the Automated Patch Tool User Manual.

DIAGONIZE PATCH FAILURES ( IF ANY )
1) The patch application is successful if the STATUS displayed is
"Patch application completed successfully."

2) If the patch had Failed to apply the objects, locate the logfile generated by the
Automated Patch application tool and search for "**Error" in the log file.

3) Please refer below metalink notes to resolve some common errors :
Note Description
382862.1 Error! Could not copy reports/US
433764.1 ODF application issues/errors when applying India localization patch
417789.1 **Error from maintain_thhold_grps :Effective Total invoice amount

4) If you have any other errors in the log file which you are not able to resolve, please log
an SR with the log files generated.
For more details on types on log files generated refer metalink note# 376756.1

applprod@vezora3:/stage/IN_Localization/6397595 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6397595.drv fnd_patchset=H appspwd=k3ob3ia japwd=ja systempwd=Ka3bU3rO logfile=/tmp/6397595.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 20-Aug-2008 12:21:15 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 20-Aug-2008 12:21:15 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6397595.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully
----------------------------------------------------------------------------
Objects that WILL be applied
----------------------------------------------------------------------------
Object Name Version -> Patch Existing
----------------------------------------------------------------------------
admin/jai_drop_apps_sequences.sql 115.0.6107.1 -
admin/jai_obs_5219225.sql 115.3.6107.1 -
admin/jai_obs_ap_5231219.sql 115.1.6107.1 -
admin/jai_obs_apps_indexes.sql 115.0.6107.1 -
admin/jai_obs_ar_4706878.sql 115.0.6107.1 -
admin/jai_obs_4742427.sql 115.0.6107.1 -
admin/jai_drop_proc_5235574.sql 115.0.6107.1 -
admin/jai_obs_cmn_obj.sql 115.0.6107.1 -
admin/jai_obs_jainpost_5640972.sql 115.0.6107.1 -
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6397595/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
jai115fn_ap_E.ldt patch/115/import/US JA_TOP
jai115fn_ar_E.ldt patch/115/import/US JA_TOP
jai115fn_fa_E.ldt patch/115/import/US JA_TOP
jai115fn_inv_E.ldt patch/115/import/US JA_TOP
jai115fn_ont_E.ldt patch/115/import/US JA_TOP
jai115fn_po_E.ldt patch/115/import/US JA_TOP
jai115lu_E.ldt patch/115/import/US JA_TOP
jai115mg_E.ldt patch/115/import/US JA_TOP
jai115_falku.ldt patch/115/import/US JA_TOP
jai115cp_F.ldt patch/115/import/US JA_TOP
jai115df_E.ldt patch/115/import/US JA_TOP
jai115st_fndrssub724_E.ldt patch/115/import/US JA_TOP
jai115st_fndrssub724_links_E.ldt patch/115/import/US JA_TOP
jai115rg_E.ldt patch/115/import/US JA_TOP
jai115pr_E.ldt patch/115/import/US JA_TOP
jai115_glcat.ldt patch/115/import/US JA_TOP
jai115glsrc.ldt patch/115/import/US JA_TOP
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************

----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /tmp/6397595.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 20-Aug-2008 12:22:14 ]

applprod@vezora3:/stage/IN_Localization/6397595 $

Total Time 4 minutes

POST INSTALL ISSUES

PATCH 6417355 UNABLE TO APPLY PREPAYMENTS WHERE TDS TAX IDS ARE NOT PRESENT
applprod@vezora7:/stage/IN_Localization/6417355 $ perl $JA_TOP/inpatch/indpatch.pl drvr_file=6417355.drv fnd_patchset=H appspwd=ng02mita japwd=ja systempwd=Ro2sE89 logfile=/home/applprod/6417355.log
============================================================================
| INDIA LOCALISATION - PATCH APPLICATION TOOL |
============================================================================
| Copyright (c) 2005 Oracle Corporation Redwood Shores, California, USA |
| All rights reserved. |
============================================================================
Current Time [ 02-Apr-2009 14:44:58 ]
Checking the environment variables....
Successfully completed
Checking the parameters to the patch application script ....
Completed Successfully
Checking the validity of arguments...
Completed Successfully
Log : Start Time [ 02-Apr-2009 14:44:58 ]
Checking application tool compatibilty with driver file...
Completed Successfully
Checking the validity of the 6417355.drv....
Completed Successfully
Populating the database versions for SQL files...
Completed Successfully
Parsing the driver file...
Completed Successfully
----------------------------------------------------------------------------
Objects that WILL be applied
----------------------------------------------------------------------------
Object Name Version -> Patch Existing
----------------------------------------------------------------------------
patch/115/sql/jaiaptpp_b.sql 115.10.6107.5 115.10.6107.4
----------------------------------------------------------------------------
Objects that will NOT be applied
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
Objects that are NOT considered for this mode of installation
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
Applying Database/mds objects.
----------------------------------------------------------------------------
Applied jaiaptpp_b.sql successfully.
******************* No mds files to copy ********************
******************* No xmlp files to copy ********************
----------------------------------------------------------------------------
Skipping following ldt files for Applications FND patchset level [H].
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
Applying forms/plls/java.
----------------------------------------------------------------------------
******************* No pll files to apply ********************
******************* No fmb files to apply ********************
******************* No java_top files to copy ********************
----------------------------------------------------------------------------
Copying rdfs.
----------------------------------------------------------------------------
******************* No rdf files to copy ********************
----------------------------------------------------------------------------
Backup details
----------------------------------------------------------------------------
Backed up objects in /stage/IN_Localization/6417355/backup.
----------------------------------------------------------------------------
Object Name Backup -> Sub-directory Source-Top/Database
----------------------------------------------------------------------------
jaiaptpp_b.sql patch/115/sql JA_TOP
----------------------------------------------------------------------------
Backup NOT taken for following non-available objects.
----------------------------------------------------------------------------
*********************** No objects ***************************
----------------------------------------------------------------------------
STATUS :
Patch application completed successfully.
Please check /home/applprod/6417355.log for patch application details.
----------------------------------------------------------------------------
Log : End Time [ 02-Apr-2009 14:45:03 ]

Indian Payroll Localization Patchset Împlementation

2009-08-09T01:38:00.002+01:00