15 September 2014

Step by Step Oracle E-Business Suite Upgrade from R12.2.3 to R12.2.4



Follow the below mentioned steps in sequential order to upgrade from Oracle E-Business Suite Release 12.2.3 to 12.2.4

Section 4: Apply the Latest AD and TXK Delta Release Update Packs

Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

Section 2: Apply Required Technology Patches

Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)

Section 3: Apply the R12.AD.C.Delta.5 and R12.TXK.C.Delta.5 Release Update Packs

If you are...
Follow this path...
Upgrading to Oracle E-Business Suite Release 12.2 from Release 11i, 12.0, or 12.1
Installing a new Oracle E-Business Suite system
Already using Oracle E-Business Suite Release 12.2
(below AD/TXK R12.AD.C.Delta.5 and R12.TXK.Delta.5 codelevel)

3.1 Path A - Upgrade and New Installation Customers


1.  Source the run edition environment file.
$ . <EBS_ROOT>/EBSapps.env run
2.  Apply the latest Application Tier Technology patches on the run file system.

3. Start up only the Weblogic AdminServer service on the run edition application tier file system.
$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
4. Unzip patches and run adgrants.
  1. Download and unzip the following patches:
Note: You should also download and unzip any applicable patches from Section 4: Apply Additional Critical Patches.
  1. Follow the instructions in the patch readme of Patch 18283295:R12.AD.C.Delta.5, to execute adgrants.
5. Apply Patch 18283295:R12.AD.C.Delta.5 (plus additional critical patches) in hotpatch mode on the run edition application tier file system. Windows users also need to merge and apply two additional patches, as shown.
UNIX:
$ adop phase=apply patches=18283295 hotpatch=yes
6. Apply Patch 18288881:R12.TXK.C.Delta.5 merged with Patch 18886213:R12.TXK.C (plus additional critical patches) in hotpatch mode on the run edition application tier file system:
$ adop phase=apply patches=18288881,18886213 hotpatch=yes merge=yes
8.Complete the online patching cycle by running the following commands in the order
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=finalize
$ adop phase=cutover
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=cleanup
9.Synchronize the file systems (conditional)
  • If you are ultimately going to apply the Oracle E-Business Suite 12.2.2 Release Update Pack, you must now synchronize the file systems by running the following command:
$ adop phase=fs_clone
6.2 Path B - Existing Customers (Release 12.2.2 or Release 12.2.3) upgrading to Oracle E-Business Suite 12.2.4 Release Update Pack

    Source the run edition applications environment.

    UNIX:
    $ . <INSTALL_BASE>/EBSapps.env run

    Windows:
    C:\><INSTALL_BASE>\EBSapps.cmd run

    Start an online patching cycle.
    $ adop phase=prepare

    Apply Oracle E-Business Suite Release 12.2.4 Patch 17919161.

    UNIX:
    $ adop phase=apply patches=17919161
  
    Complete the online patching cycle by running the following commands in the order shown.

    UNIX:
    $ adop phase=finalize
    $ adop phase=cutover
    $ . <INSTALL_BASE>/EBSapps.env run
    $ adop phase=cleanup
  
    Synchronize file systems

    Synchronize the file systems using the command shown below. This action will copy the new run edition code and configuration to the other file system, to help the next online patching cycle complete faster.
    $ adop phase=fs_clone
Section 7: Post-Update Steps

1.Apply Oracle E-Business Suite Release 12.2.4 Online Help

Apply Oracle E-Business Suite Release 12.2.4 Online Help Patch 17919162 merged with Patch 19290141 using adop hotpatch mode on the run file system.
$ adop phase=apply patches=17919162,19290141 hotpatch=yes merge=yes

2.Grant flexfield value set access to specific users (required)


Register new products (conditional)

The new products below (added in Release 12.2.4) are not automatically registered in your system. If you intend to use new products, register them using License Manager. For instructions, refer to Oracle E-Business Suite Maintenance Guide, Release 12.2 (Part No. E22954).
Product Short Name       Product Name
yms        Oracle Yard Management
cmi         Oracle In-memory Cost Management






Perform Product-Specific Steps (conditional) :-
Customer Relationship Management tasks:

    Run the "Update Time Structure" concurrent program.

    Run the "Update Time Structure" concurrent program, if it was not executed after opening the latest General Ledger period.

    Verify whether this concurrent program was already executed by running the following query in APPS user.
    SELECT COUNT(*)
    FROM OZF_TIME_DAY
    WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND END_DATE;

    If the query returns 1, the concurrent program was already executed; there is no need to execute it again. If the query returns 0, execute the concurrent program. Suggested parameters are:
        FROM DATE: 1-JAN-1997 0:0:0
        TO DATE: (the last date previously defined in General Ledger)
        All Level : Y


    It is recommended to schedule this program to run at regular intervals whenever new GL periods are opened. If not executed, YEAR_ID column in table OZF_FUNDS_UTILIZED_ALL_B will not be populated.


Navigate to Oracle Trade management Administrator responsibility --> view  --> request  --> Submit a new request  --> click ok --> enter concurrent program name (Update Time Structure)  --> enter below parameter --> click submit.






References
  • Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
  • Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
  • Oracle E-Business Suite Release 12.2.4 Readme (Doc ID 1617458.1)

No comments: