Wednesday 30 September 2020

Oracle E-Business Suite Release 12.2.10 Readme (Doc ID 2666934.1)

 

In this Document

Section 1: Prepare

For information about known issues associated with specific products in Oracle E-Business Suite Release 12.2.10 and possible workarounds for those issues, please reference the Known Issues section of your specific product Release Note documents.

In Release 12.2.0 and higher, patching is performed by running the new adop (AD Online Patching) utility. You must use adop instead of the adpatch utility that was provided in previous releases. Download and unzip all the patches to the default Patch Top location for R12.2 ($APPL_TOP_NE/../patch). For more information about the adop utility, refer to Oracle E-Business Suite Concepts (Part No. E22949) and Oracle E-Business Suite Maintenance Guide, Release 12.2 (Part No. E22954).

Oracle E-Business Suite 12.2.10 Release Update Pack requires Oracle Fusion Middleware Technology Stack (FMW) 11.1.1.9 (11g Release 1 Patch Set 7). New Installation and Upgrade (upgrading to Oracle E-Business Suite Release 12.2.10 from Release 11i, 12.0, or 12.1) customers should use StartCD 12.2.0.51. StartCD 12.2.0.51 (Patch 22066363, RAPID INSTALL STARTCD 12.2.0.51) installs Oracle Fusion Middleware 11g PS7 (11.1.1.9.0).

Note: Before installing or upgrading, you should read and follow the instructions in the installation and upgrade notes for your platform:
  • My Oracle Support Knowledge Document 1330701.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64
  • My Oracle Support Knowledge Document 1330702.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Oracle Solaris on SPARC (64-bit)
  • My Oracle Support Knowledge Document 1330703.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for IBM AIX on Power Systems (64-bit)
  • My Oracle Support Knowledge Document 1330704.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for HP-UX Itanium
  • My Oracle Support Knowledge Document 1330706.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Microsoft Windows (64-bit)

Section 2: Obsolete Products in Release 12.2.10

The following products are obsolete in Release 12.2.10:

  • Oracle Demand Planning (obsolete in Release 12.2.5 and above)
  • Oracle Manufacturing Scheduling (obsolete in Release 12.2.5 and above)

A migration plan exists for customers who have purchased these products in earlier releases. Contact your Sales Representative or Account Manager for more information.

Support will be provided to existing customers on earlier releases, in accordance with the Oracle Lifetime Support Policy.

Section 3: Upgrade Database to 11.2.0.4 or higher

If your Oracle E-Business Suite instance is currently on Database version 11.2.0.3, then you should now upgrade to Database 11.2.0.4 or 12.1.0.2 or 19c before proceeding with the next steps by following the process documented in the appropriate Interoperability Notes:

  • My Oracle Support Knowledge Document 2552181.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
  • My Oracle Support Knowledge Document 1926201.1, Interoperability Notes Oracle EBS 12.2 with Oracle Database 12c Release 1
  • My Oracle Support Knowledge Document 1623879.1, Interoperability Notes E-Business Suite Release 12.2 with Database 11g Release 2
Note: Database desupport schedules have important operational and planning implications for Oracle E-Business Suite environments. Oracle recommends that you review the following document that details the latest database support policies and desupport schedules:
  • My Oracle Support Knowledge Document 742060.1, Release Schedule of Current Database Patch Sets

Section 4: Apply Required Database Patches and Update Database Initialization Parameters

4.1 Apply Required Database Patches

Before you apply the AD and TXK Delta 12 release update packs (RUPs), you must run the latest version (available via Patch 17537119) of the EBS Technology Codelevel Checker (ETCC). Use the command checkDBpatch.sh (on UNIX) or checkDBpatch.cmd (on Windows).

Running the latest version is required in order to:

  1. Check that all the required database patches have been applied. To learn more about the prerequisite database patches needed for applying the AD-TXK Delta 12 RUPs, refer My Oracle Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.
  2. Ensure all the required ETCC database objects will be found by the AD-TXK Delta 12 RUP installation process. This means that even if you already have all the required database patches installed, you must still run the latest version of ETCC on your database.

4.2 Set Database Parameter (Conditional)

  1. Optimizer Adaptive Optimization

    2. If you are using Oracle Database 12.1.0.2, optimizer adaptive features are controlled by the database initialization parameter optimizer_adaptive_features. this parameter should always be set to 'false'. This setting should be completed before proceeding with the next steps and should not be changed thereafter.

    Note (for Windows customers on 12cR1 only): Customers who have applied Patch 27440294 "WINDOWS DB BUNDLE PATCH 12.1.0.2.180417(64bit)" or later should refer to Table 1.5 in My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes, for specific instructions before starting the database.

    Note: If you are using Oracle Database 19c, optimizer adaptive features are no longer controlled by the database initialization parameter optimizer_adaptive_features. Instead, these features are controlled by two new parameters: optimizer_adaptive_plans, which defaults to TRUE, and optimizer_adaptive_statistics, which defaults to FALSE.

    For more information, see My Oracle Support Knowledge Document 396009.1, Database Initialization Parameters for Oracle E-Business Suite Release 12.
    optimizer_adaptive_features=false

    You can verify the parameter was set correctly by running the following command, which should return the value FALSE:

    SQL>show parameter optimizer_adaptive_features
  2. _disable_actualization_for_grant (applicable to Oracle Database 11.2.0.4, Oracle Database 12.1.0.2, and Oracle Database 19c)

    3. Set the parameter _disable_actualization_for_grant to true.

    _disable_actualization_for_grant=true

    You can verify the parameter was set correctly by running the following command, which should return the value TRUE:

    SQL>show parameter _disable_actualization_for_grant

Section 5: Apply Consolidated Seed Table Upgrade Patch (Required)

Note: This step is applicable only for new installation customers and customers upgrading from Oracle E-Business Suite Release 12.2.2 to Release 12.2.10.

Note: You can skip this step if you have upgraded to Release 12.2.0 using the latest Consolidated Upgrade Patch 30399970:12.2.0 (CUP11) or earlier Consolidated Upgrade Patches:
  1. Stop all application tier services on the run file system.

    UNIX:

    sh $ADMIN_SCRIPTS_HOME/adstpall.sh

    Windows:

    C:\>%ADMIN_SCRIPTS_HOME%\adstpall.cmd

  2. Start up only the Oracle Weblogic Admin Server on the run file system.

    UNIX:

    $ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

    Windows:

    C:\>%ADMIN_SCRIPTS_HOME%\adadminsrvctl.cmd start

  3. Apply the consolidated seed table upgrade Patch 26787701:12.2.0 on the run file system using adop hotpatch mode.

    $ adop phase=apply patches=26787701 hotpatch=yes

    Note: For existing non-American languages in the system, skip NLS patch application for this. It is not required.

  4. Start up all application tier services.

    Note: This step is applicable only for customers upgrading from Oracle E-Business Suite Release 12.2.2 to Release 12.2.10.

    UNIX:

    $ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

    Windows:

    C:\>%ADMIN_SCRIPTS_HOME%\adstrtal.cmd

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

Note: Review My Oracle Support Knowledge Document 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2, and follow the instructions to apply the required codelevel of AD and TXK for your system.

Section 7: Perform Pre-Update Steps (Conditional)

Perform the following pre-update steps only if you have licensed this product:

  • Customer Relationship Management tasks:

    • Oracle Mobile Field Service

      For Oracle Mobile Field Service Store and Forward Multiple Platforms Support, Oracle Lite is not required and it should be uninstalled. Refer to subsection 'Pre-Installation Step' of My Oracle Support Knowledge Document 2188514.1, Oracle Mobile Field Service for Oracle E-Business Suite Release Notes, to drop the mobileadmin schema.

  • Oracle E-Business Suite Mobile Apps tasks:

    • Oracle Mobile Maintenance for Oracle E-Business Suite

      The Oracle Mobile Maintenance "Disconnected" feature uses the Oracle Mobile Field Service Multiplatform framework, which does not require Oracle Lite and it should be uninstalled if it exists. If you plan to implement Oracle Mobile Maintenance for Oracle E-Business Suite built with Oracle E-Business Suite Mobile Foundation Release 7.0 or above, connect as system user and drop the repository using the following command:

      SQL > Drop user mobileadmin cascade;

      For more information, refer to subsection 'Step 1: Performing Conditional Pre-Install Tasks' in Oracle E-Business Suite Mobile Apps Administrator's Guide, Release 12.1 and 12.2 (Part No. E64384).

    • Oracle Mobile Service Manager for Oracle E-Business Suite

      Refer to the subsection 'Pre-Installation Step' of My Oracle Support Knowledge Document 2107368.1, Oracle Mobile Service Manager for Oracle E-Business Suite Release Notes, to drop the mobileadmin schema.

  • Supply Chain Management tasks:

    • Oracle Flow Manufacturing

      If you have a lower version of the file(s) listed below or you have performed customizations on any of these packages, create a back-up of your file(s) under $APPL_TOP_NE/.

      Package NameFile Version
      FLM_KANBAN_CUSTOM_PKGflmkacps.pls
      120.3.12020000.2

      flmkacpb.pls
      120.3.12020000.2

      After applying the Oracle E-Business Suite 12.2.10 Release Update Pack, redo the customization in the new version of the specification and the body.

    • Oracle Install Base

      Check your system for possible corruption on the user-defined Installed Base Transaction SubTypes. If additional Installed Base Transaction SubTypes or changes to the user-defined Installed Base Transaction SubTypes are identified, you must fix them before applying the Oracle E-Business Suite 12.2.10 Release Update Pack.

      Refer to My Oracle Support Knowledge Document 1681308.1, Generic Datafix For Installed Base Transaction SubTypes Data Corruption Caused by csitxnst.ldt, for instructions.

    • Oracle Landed Cost Management

      If you have a lower version of the file(s) than the one below and have done customization, create a back-up of your file(s) under a location outside both APPL_TOPs or under $APPL_TOP_NE/../log.

      Package NameFile Version
      INL_CUSTOM_PUBINLPCUSB.pls
      120.6.12020000.7

      INLPCUSS.pls
      120.5.12020000.6

      After applying the Oracle E-Business Suite 12.2.10 Release Update Pack, redo the customization in the new version of the specification and the body. For more information, refer to My Oracle Support Knowledge Document 1211843.1, How to Proceed for Customizing LCM Hooks INLPCUSB.pls.

    • Oracle Mobile Application Server

      If you have a lower version of the file(s) listed below or you have performed some modifications in the below file, create a back-up of your file(s) under $APPL_TOP_NE/.

      DirectoryFile NameFile Version
      $INST_TOP/admin/installmwa.cfg120.2.12020000.8

      After applying the Oracle E-Business Suite 12.2.10 Release Update Pack, redo the modification in the new version of the file.

    • Oracle Warehouse Management

      If you have a lower version of the file(s) listed below or you have performed customizations on any of these packages, create a back-up of your file(s) under $APPL_TOP_NE/.

      Package NameFile Version
      WMS_LABEL_CUSTOM_PKGWMSLACPB.pls
      120.0.12020000.3

      WMSLACPS.pls
      120.1.12020000.5
      WMS_XDOCK_CUSTOM_APIS_PUBWMSXDCAS.pls
      120.2.12020000.5

      WMSXDCAB.pls
      120.1.12020000.3
      WMS_RE_Custom_PUBWMSPPPUS.pls
      120.6.12020000.4

      WMSPPPUB.pls
      120.5.12020000.2

      After applying the Oracle E-Business Suite 12.2.10 Release Update Pack, redo the customization in the new version of the specification and the body.

    • Oracle Work in Process

      If you have a lower version of the file(s) listed below or you have performed customizations on any of these packages, create a back-up of your file(s) under $APPL_TOP_NE/.

      Package NameFile Version
      WIP_WS_CUSTOMwipwsctb.pls
      120.9.12020000.19

      wipwscts.pls
      120.3.12020000.17

      After applying the Oracle E-Business Suite 12.2.10 Release Update Pack, redo the customization in the new version of the specification and the body.

Section 8: Apply Oracle E-Business Suite 12.2.10 Release Update Pack

Having applied the latest available AD and TXK Release Update Pack (RUP) and having also performed the necessary pre-update steps mentioned in the above sections, you can now proceed with applying the Oracle E-Business Suite 12.2.10 Release Update Pack based on your installation type.

If you are...Follow this path...
Upgrading to Oracle E-Business Suite Release 12.2.10 from Release 11i, 12.0, or 12.1Path A
Installing a new Oracle E-Business Suite systemPath A
Already using Oracle E-Business Suite Release 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.2.8 or 12.2.9Path B

8.1 Path A — Upgrade and New Installation Customers upgrading to Oracle E-Business Suite 12.2.10 Release Update Pack

  1. Source the run edition applications environment.

    UNIX:

    $ . <INSTALL_BASE>/EBSapps.env run

    Windows:

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

  2. Stop Oracle WebLogic Server's Admin Server and Node Manager services.

    To apply a patch in downtime mode, you must shut down all application tier services, including the Oracle WebLogic Server Admin Server and Node Manager.

    1. Stop the Oracle WebLogic Server Admin Server on the run file system.

      UNIX:

      $ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

      Windows:

      C:\>%ADMIN_SCRIPTS_HOME%\adadminsrvctl.cmd stop

    2. Stop the Oracle WebLogic Server Node Manager service on the run file system.

      UNIX:

      $ sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

      Windows:

      C:\>%ADMIN_SCRIPTS_HOME%\adnodemgrctl.cmd stop

  3. Apply Oracle E-Business Suite 12.2.10 Release Update Pack Patch 30399999 on the run edition application environment, using downtime mode.

    UNIX:

    $ adop phase=apply apply_mode=downtime patches=30399999

    Windows:

    C:\>adop phase=apply apply_mode=downtime patches=30399999

    Note: Customers using Visual Studio 2013 or Visual Studio 2017: Follow the instructions mentioned in the section 'Applying patches when using Visual Studio 2013/2017' of My Oracle Support Knowledge Document 1330706.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Microsoft Windows x64 (64-bit).

  4. Start all application tier services on the run file system.

    UNIX:

    $ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

    Windows:

    C:\>%ADMIN_SCRIPTS_HOME%\adstrtal.cmd

  5. Perform adop cleanup action.

    UNIX:

    $ adop phase=cleanup

    Windows:

    C:\>adop phase=cleanup

  6. 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 ensure that both file systems are in sync before applying patches using the regular adop cycle on the other file system.

    $ adop phase=fs_clone

8.2 Path B — Existing Customers (Release 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.2.8 or 12.2.9) upgrading to Oracle E-Business Suite 12.2.10 Release Update Pack

  1. Source the run edition applications environment.

    UNIX:

    $ . <INSTALL_BASE>/EBSapps.env run

    Windows:

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

  2. Start an online patching cycle.

    $ adop phase=prepare

  3. Upgrade Fusion Middleware Technology Stack to 11.1.1.9 (11gR1 PS7).

    Upgrade Fusion Middleware Technology Stack (FMW) to 11.1.1.9 (11gR1 PS7) on the patch file system by following the instructions in the below mentioned document:

    • Fusion Middleware Technology Stack (FMW) to 11.1.1.9 (11gR1 PS7) — My Oracle Support Knowledge Document 1590356.1, Fusion Middleware Technology Stack of Oracle E-Business Suite Release 12.2 to 11.1.1.9 (11gR1 PS7)

    Note: Upgrade of Fusion Middleware Technology Stack (FMW) must be done on the patch file system, as you are currently in an active online patching cycle. However, you should not invoke any other adop actions, such as finalize, cutover, cleanup, or fs_clone in the patching cycle; these actions are executed in later steps, as mentioned in the appropriate parts of this document.

  4. Apply the latest application tier technology patches.

    On the patch file system, apply the latest application tier technology patches documented in 'Section 3: Application Tier Technology Patches and Bug Numbers' of My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes. This document also describes how to use the EBS Technology Codelevel Checker (ETCC) to check if all the prerequisite application tier technology patches have been installed.

    Run the Middle Tier EBS Technology Codelevel Checker (MT-ETCC) on the Oracle E-Business Suite application tier nodes and apply any missing application tier technology patches.

    Note: Refer to My Oracle Support Knowledge Document 1355068.1, Oracle E-Business Suite 12.2 Patching Technology Components Guide for instructions on how to apply technology patches.

    Note: Oracle recommends applying the most recent Oracle WebLogic Server Patch Set Update (PSU) so you can benefit from the latest enhancements and fixes. For more information, refer to My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.

    Oracle E-Business Suite 12.2.10 Release Update Pack Patch 30399999 or higher requires a minimum Oracle WebLogic Server PSU version of 10.3.6.0.190416 Patch 29204678. Therefore, you must apply the Oracle WebLogic Server PSU version 10.3.6.0.190416 Patch 29204678 and then re-run the Middle Tier EBS Technology Codelevel Checker (MT-ETCC) on the Oracle E-Business Suite application tier nodes.

    Note: As you are currently in an active online patching cycle, you should apply application tier technology patches on the patch file system. However, you should not invoke any other adop actions such as finalize, cutover, cleanup, or fs_clone in the patching cycle; these actions are executed in later steps, as mentioned in the appropriate parts of this document.

  5. Apply Oracle E-Business Suite Release 12.2.10 Patch 30399999.

    UNIX:

    $ adop phase=apply patches=30399999

    Windows:

    C:\>adop phase=apply patches=30399999

    Note: Customers using Visual Studio 2013 or Visual Studio 2017: Follow the instructions mentioned in the section 'Applying patches when using Visual Studio 2013/2017' of My Oracle Support Knowledge Document 1330706.1, Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Microsoft Windows x64 (64-bit).

  6. 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

    Windows:

    C:\>adop phase=finalize
    C:\>adop phase=cutover
    C:\><INSTALL_BASE>\EBSapps.cmd run
    C:\>adop phase=cleanup

  7. 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 9: Post-Update Steps

Note: If you are upgrading from Release 11i, 12.0.x or 12.1.x to Release 12.2.10, then you must continue with 12.2.0 post upgrade steps mentioned in the Upgrade guides before performing the below steps.

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

    Apply Oracle E-Business Suite Release 12.2.10 Online Help Patch 30399996 using adop hotpatch mode on the run file system.

    $ adop phase=apply patches=30399996 hotpatch=yes
  2. Verify security configurations (required)

    If you have upgraded to Oracle E-Business Suite 12.2.10 Release Update Pack from Oracle E-Business Suite 12.2.6 Release Update Pack (or earlier) and after you apply the Release Update Pack (RUP) or perform an upgrade, your Oracle E-Business Suite system is locked down until the system administrator configures or acknowledges the recommended security configurations in the Secure Configuration Console to unlock the system for normal usage. To access this console, a user must have a responsibility that includes the Applications System (OAM_APP_SYSTEM) function privilege, such as the seeded System Administration or System Administrator responsibilities, and must be registered as a local user with Oracle E-Business Suite. The administrator must log in to Oracle E-Business Suite using the local login page (http(s)://[host]:[port]/OA_HTML/AppsLocalLogin.jsp) to navigate to the console and unlock the system. If a user with local system administrator privileges is not available, you can access the Secure Configuration Console through a command line utility. For more information, see "Secure Configuration Console" in the Oracle E-Business Suite Security Guide, Part No. E22952.

  3. Complete Password Hashing Migration (conditionally required)

    If you have not already migrated to a password hashing scheme for Oracle E-Business Suite user passwords, then when you apply Oracle E-Business Suite 12.2.10 Release Update Pack, your instance is upgraded to a partial migration to the SHA256 hash mode. With a partial migration, users on an earlier encryption mode can still log in and their passwords will still be encrypted, but all subsequent password changes will switch these users to the advanced hash mode.

    It is strongly recommended that you complete the migration by running the AFPASSWD utility with the following command:

    AFPASSWD -P BACKGROUND

    This command will migrate all user passwords that can be migrated over to the current password hashing scheme.  This operation cannot be reversed.

    If you prefer to use a different hash mode such as SHA384 or SHA512 instead of SHA256, then you can perform another partial migration to switch to that hash mode before you complete the migration. For example:

    AFPASSWD -m [SHA384|SHA512] PARTIAL
    AFPASSWD -P BACKGROUND

    For more information, see Using AFPASSWD to Migrate to a Password Hashing Scheme, Oracle E-Business Suite Maintenance Guide.

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

    Release 12.2 includes a new security feature, flexfield value set security; it controls who can create or modify flexfield values in the Flexfield Values Setup window (FNDFFMSV). Flexfield value set security requires some mandatory setup steps before any users can create or update values in the Values window. You must perform this step if you have not already done so for a previous version of Release 12.2.

    Note: See the Flexfield Value Set Security chapter in Oracle® E-Business Suite Flexfields Guide, Release 12.2 (Part No. E22963).

  5. 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 NameProduct Name
    ymsOracle Yard Management
    cmiOracle In-memory Cost Management

  6. Perform Product-Specific Steps (conditional)

    After you have completed the steps to update all nodes with the latest code level, perform the following post-update steps only if you have licensed this product:

    • Application Technology tasks:

      • Oracle Application Framework: Release 12.2.5 introduced an updated Look and Feel for Oracle Application Framework-based pages, the Oracle Alta UI. Ensure that you either set the Oracle Applications Look and Feel profile option to "Alta Look and Feel" or to a Look and Feel that extends the Alta Look and Feel, or leave this profile option blank to use the standard Alta Look and Feel by default. Oracle supports only this standard Look and Feel, or one that extends it, for R12.ATG_PF.C.Delta.5 and higher. Oracle no longer supports the Look and Feel options of previous releases. For more details, refer to My Oracle Support Knowledge Document 1315510.1, Oracle Application Framework Profile Options. Additionally, if you have customized or extended the base functionality of any Oracle Application Framework-based applications, review My Oracle Support Knowledge Document 1927975.1, Oracle E-Business Suite Release 12.2 Upgrade Considerations for OA Framework-based Applications, to evaluate whether any adjustments to custom code are needed.
      • Oracle E-Business Suite Integrated SOA Gateway: Oracle E-Business Suite Integrated SOA Gateway requires post manual installation steps. If you are using the Oracle E-Business Suite Integrated SOA Gateway feature for web service generation, deployment, and invocation, perform the steps documented in My Oracle Support Knowledge Document 1311068.1, Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2.
        Note: Oracle E-Business Suite Integrated SOA Gateway has product dependencies on Oracle SOA Suite and Oracle E-Business Suite Adapter for SOAP based web services. REST based web services do not have this dependency. You are not required to install Oracle SOA Suite if you plan to use only the REST based web services provided by Integrated SOA Gateway.
      • Oracle Report Manager: Beginning in Release 12.2.5, you can optionally choose to create financial report templates and Financial Statement Generator reports in the Office Open XML (OOXML) format. If you have existing financial report templates that were created before you enabled the OOXML format, then you must migrate these templates to the new format. To do so, submit a concurrent request for the Template Migration (FRM_TEMPLATE_MIGRATION) program. For more information, see: Using the Office Open XML Format, Oracle Report Manager User's Guide.
      • Oracle Workflow:
        1. If your Oracle Fusion Middleware version is earlier than 11.1.1.9, then you must enable JSSE SSL in the Oracle E-Business Suite context file. This step is required for the Oracle Workflow Status Monitor to be displayed. Use Oracle Applications Manager to update the Oracle E-Business Suite context file.
          • Log in to Oracle E-Business Suite as a system administrator.
          • Navigate to System Administration: Oracle Applications Manager > AutoConfig.
          • Select the application tier context file, and choose Edit Parameters.
          • Search for the s_enable_jsse variable by selecting OA_VAR in the search list of values and entering s_enable_jsse in the search text box. Then choose the Go button.
          • By default, the s_enable_jsse variable is set to false. Change this value to true to enable JSSE SSL. Refer to the description of the context variable for more information.
          • Choose the Save button.
          • Enter a reason for the update, such as Enabling JSSE SSL. Then choose the OK button.
          • Execute AutoConfig and restart all application tier services. For more information about AutoConfig, see: Technical Configuration, Oracle E-Business Suite Setup Guide.

        2. Verify the required Oracle Workflow directory service assignments for the SYSADMIN user, and run the Workflow Directory Services User/Role Validation concurrent program (FNDWFDSURV) to update the assignment records if necessary.

          Perform the following three checks to verify the directory service assignments:

          • Log in to Oracle E-Business Suite as the SYSADMIN user and check whether the Application Diagnostics responsibility appears for this user in the navigator. If not, then run the Workflow Directory Services User/Role Validation concurrent program with the parameters listed below.
          • Execute the following SQL query:
            SELECT ASSIGNING_ROLE, LAST_UPDATE_DATE, USER_ORIG_SYSTEM, USER_ORIG_SYSTEM_ID, ROLE_ORIG_SYSTEM, ROLE_ORIG_SYSTEM_ID FROM WF_USER_ROLE_ASSIGNMENTS WHERE USER_NAME = 'SYSADMIN' AND ROLE_NAME = 'FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD';

            If the originating system or originating system ID is null for either the user or the role in any of the records returned by this query, then run the Workflow Directory Services User/Role Validation concurrent program with the parameters listed below.

          • Execute the following SQL query to obtain the originating system ID of the Application Diagnostics responsibility in your Oracle E-Business Suite instance:
            SELECT ORIG_SYSTEM_ID FROM WF_LOCAL_ROLES WHERE NAME = 'FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD';

            Next, execute the following SQL query, replacing <RESP_ID> with the originating system ID returned by the previous query:

            SELECT * FROM FND_USER_RESP_GROUPS WHERE RESPONSIBILITY_ID = <RESP_ID> AND USER_ID = 0;

            If this query does not return any rows, then run the Workflow Directory Services User/Role Validation concurrent program with the parameters listed below.

          To update the assignment records for the SYSADMIN user, run the Workflow Directory Services User/Role Validation concurrent program with the following parameters:

          • Batch size: 10000 (the default value)
          • User name: SYSADMIN
          • Role name: FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD
          • Fix dangling users: No
          • Add missing user/role assignments: Yes
          • Update WHO columns in WF tables: Yes
          • Number of Parallel Processes: Optionally specify the number of parallel processes you want to use when running the program.

          For more information about this program, see: Validating Directory Service Information, Oracle Workflow Administrator's Guide.

    • Customer Relationship Management tasks:

      • Oracle® Advanced Scheduler and Field Service: If you plan to leverage real-time travel calculations for geo-coding and routing in Advanced Scheduler and Field Service, refer to My Oracle Support Knowledge Document 1560522.1, Navteq ODF Installation Steps For Advanced Scheduler 12.2.2 or later, for Navteq ODF data installation and configuration steps. Note that the installation of ODF data and the corresponding deployment configuration is a one-time setup.
      • Oracle® Incentive Compensation customers: If you are implementing Oracle Incentive Compensation Analytics, refer to the appropriate My Oracle Support knowledge document below, for the complete deployment and configuration steps of Oracle Incentive Compensation Analytics for ODI:
        • Fusion 11g Middleware
          • Document 1580131.1, How to deploy and configure Oracle Incentive Compensation Analytics for Oracle Data Integrator 11g
        • Fusion 12c Middleware
          • Document 2123153.1, How to deploy and configure Oracle Incentive Compensation Analytics for Oracle Data Integrator 12c
      • Oracle® Price Protection customers: For complete installation, configuration and deployment steps, refer to the My Oracle Support knowledge document that is relevant to your Oracle SOA Suite version:
      • Oracle® Spares Management customers: If you have implemented or plan to implement the Application Developers Framework (ADF) based Planners Dashboard, refer to My Oracle Support Knowledge Document 1925014.1, Spares Management: 12.2.4+ ADF Planners Dashboard Deployment Guide for the complete installation and configuration steps.

    • Oracle Projects Suite tasks:

      • Post Deployment Steps For Microsoft Project Integration Changes (Conditional)
        • If you have implemented Microsoft Project to Oracle Projects Integration, re-install the Microsoft Project Integration.

    • Financials tasks:

      • Oracle® Subledger Accounting: Re-validate all Applications Accounting Definitions (AAD) in the system by running the concurrent request, Validate Application Accounting Definitions, after applying this patch for the changes to become effective. Refer to My Oracle Support Knowledge Document 1406203.1, Steps to Run Import And Validate AAD (Application Accounting Definition) with troubleshooting for instructions on how to validate AAD.

    • Human Resources tasks:

      • Human Resources Legislative customers only: Refer to My Oracle Support Knowledge Document 1469456.1 for details on the patches supplying the latest legislative data definitions and for instructions on how to actually apply this data to your system.
      • Single Latest Balance Table Upgrade (For Payroll customers only): If one or more business groups have not been upgraded to the single latest balance table, run the concurrent program 'Generic Upgrade' for 'Single Latest Balance Table Upgrade' to upgrade to Single Latest balance table.
        • The upgrade is executed by the business group. Refer to My Oracle Support Knowledge Document 1937092.1, How to determine which business groups need to be upgraded to "Single Latest Balance Table", for information about the SQL command that enables the display of business groups that were not executed.
      • Submit the Update Action Type of Assignment Action (For Payroll customers only): If the Upgrade Action Type was not executed globally, run the 'Generic Upgrade' concurrent program for 'Update Action Type of Assignment Action'. If the Assignment Action Type is set in the Assignment Actions table, the performance improves for payroll processes.
        • Refer to My Oracle Support Knowledge Document 1947737.1, How to determine which business groups need upgrade "Update Action Type of Assignment Action" for more information.

    • Procurement tasks:

      • Oracle® Purchasing with Oracle® Transportation Management: Oracle Purchasing is integrated with Oracle Transportation Management. If you have licensed both products and would like to use Oracle Transportation Management with Oracle Purchasing, execute the post-update steps listed in My Oracle Support Knowledge Document 1362803.1, About Oracle Transportation Management Integration with Oracle E-Business Suite R12.2+.

    • Supply Chain Management tasks:

      • Oracle® Complex Maintenance Repair and Overhaul: If you are using or plan to use Enigma 3C with Oracle Complex Maintenance Repair and Overhaul (CMRO), refer to the following My Oracle Support knowledge documents for the required post-update steps:
      • Oracle® Flow Manufacturing: If you are using or plan to use electronic kanban, refer to My Oracle Support Knowledge Document 1517173.1, 12.2 Electronic Kanban Deployment Guide for the complete deployment setup.
      • Oracle® In-Memory Cost Management for Discrete Industries or Oracle® In-Memory Cost Management for Process Industries: Refer to My Oracle Support Knowledge Document 1632072.1, Oracle In-Memory Cost Management Installation and Configuration Guide for Release 12.2, for complete installation and configuration steps.
      • Oracle® Manufacturing Operations Center: Refer to My Oracle Support Knowledge Document 2679475.1, Oracle Manufacturing Operations Center Installation Note, Release 12.2.10, for the complete installation and configuration steps.
      • Oracle® Shipping Execution: If you have licensed the Oracle Transportation Management and use or plan to use the International Trade Management integrated with Global Trade Management, apply Global Trade Management Patch 18472094.
      • Oracle® Shipping Execution with Oracle® Transportation Management: If you have licensed both Oracle Transportation Management and Oracle Shipping Execution and are already using or plan to use Oracle Transportation Management with Oracle Shipping Execution, refer to My Oracle Support Knowledge Document 1362803.1, About Oracle Transportation Management Integration with Oracle E-Business Suite R12.2+, for the required post-update steps.
      • Oracle® Warehouse Management with Oracle® Transportation Management: If you have licensed both Oracle Transportation Management and Oracle Warehouse Management and are already using or plan to use Oracle Transportation Management with Oracle Warehouse Management, refer to My Oracle Support Knowledge Document 1362803.1, About Oracle Transportation Management Integration with Oracle E-Business Suite R12.2+, for the required post-update steps.
      • Oracle® Yard Management: If you plan to use Oracle Yard Management, refer to My Oracle Support Knowledge Document 1672903.1, Oracle Yard Management, deployment steps for ADF components, for the deployment steps.

    • Value Chain Planning tasks:

      • Oracle® Value Chain Planning: Oracle Value Chain Planning includes Advanced Supply Chain Planning, Demand Planning, Inventory Optimization, Global Order Promising, Collaborative Planning, Production Scheduling, Strategic Network Optimization, Service Parts Planning, Advanced Planning Command Center, and Demand Signal Repository. If you have licensed any of these products, perform the steps outlined in My Oracle Support Knowledge Document 1361221.1, Release 12.2.x Oracle Value Chain Planning Installation Notes – Known Issues, FAQ and Latest Patch Information to enable these applications.

    • Oracle® E-Business Suite Information Discovery customers: Refer to My Oracle Support Knowledge Document 2344818.1, Installing Oracle E-Business Suite Information Discovery, Release 12.2 V9, for the complete installation and configuration steps.

    • Oracle® E-Business Suite Mobile Apps customers: Refer to My Oracle Support Knowledge Document 1641772.1, Oracle E-Business Suite Mobile Apps, Release 12.1 and 12.2 Documentation Index, for guidance on installing and configuring your app.

  7. Perform NLS-related Step (conditional)

    You may have languages other than American English installed on your Release 12.2.0 system. If so, you must apply the Release 12.2.10 NLS software patch for each of the existing languages in the system. After applying the Release 12.2.10 NLS software patch, apply the Release 12.2.10 Online Help patch for the language, if available. Refer to My Oracle Support Knowledge Document 405992.1, Oracle E-Business Release 12.2, 12.1 and 12.0 Translation Scope and Availability for scope of Online Help languages.

    Note: If you plan to install new languages after you apply Release 12.2.10 Patch 30399999, refer to My Oracle Support Knowledge Document 1314621.1, Oracle E-Business Suite NLS Release Notes.

  8. Run the Patch Wizard for current recommended and high priority product patches.

    Patch Wizard is a tool included with Oracle Application Manager. Patch Wizard reviews recommended and high priority patches against those that have been applied on your system. Patches can be downloaded and merged using the tool. You can review patch impact to determine how a specific patch or several patches will affect your system. Refer to My Oracle Support Knowledge Document 976188.1, Patch Wizard Utility.

    Note: If your environment does not allow the patch wizard utility, review My Oracle Support Knowledge Document 1400757.1, How to Find Oracle E-Business Suite Recommended Patches.

Section 10: Apply Additional Critical Patches

None at this time. You should periodically check this Document 2666934.1 on My Oracle Support for updates.

Section 11: List of Included Patches

The table in this section lists product families that have patches included in Oracle E-Business Suite Release 12.2.10 and provides links to details about those patches. For more information about the products associated with each product family, refer to My Oracle Support Knowledge Document 2666850.1, Oracle E-Business Suite Product Specific Release Notes, Release 12.2.10.

To view the documentation resources that are available for a specific product, refer to the links in the following table:

PatchProduct FamilyProduct Family Readme Document
R12.ATG_PF.C.DELTA.9 Patch 30399994Applications Technology (ATG_PF)Document 2661861.1
R12.CC_PF.C.DELTA.10 Patch 30648547Customer Relationship Management (CC_PF)Document 2666830.1
R12.FIN_PF.C.DELTA.10 Patch 30616299Financials (FIN_PF)Document 2666833.1
R12.HR_PF.C.DELTA.14 Patch 30096069Human Resources (HR_PF)Document 2656548.1
R12.PJ_PF.C.DELTA.10 Patch 30649738Projects (PJ_PF)Document 2666911.1
R12.PRC_PF.C.DELTA.10 Patch 30682300Procurement (PRC_PF)Document 2666926.1
R12.SCM_PF.C.DELTA.10 Patch 30639001Supply Chain Management (SCM_PF)Document 2666945.1
R12.SCP_PF.C.DELTA.11 Patch 30638777Oracle Value Chain Planning (SCP_PF)Document 2666932.1

Oracle E-Business Suite 12.2.10 Release Update Pack also includes the below patches. For more information and instructions, refer to the patches' corresponding My Oracle Support knowledge documents listed below.

PatchesReadme Document

April 2020 Oracle E-Business Suite Critical Patch Update for Release 12.2

Document 2650675.1

Oracle E-Business Suite Person Data Removal Tool (PDRT) Patches

Document 2388237.1

Oracle E-Business Suite 12.2 Consolidated patch for Mobile Release 9.0

Document 1642431.1

Section 12: Known Issues

12.1 Oracle Human Resources

Customers upgrading to the Oracle E-Business Suite 12.2.10 Release Update Pack, while creating trigger PER_KR_ADDRESSES_F3, will encounter the following error for the file PER_KR_ADDRESSES_X3.sql in the adworker log. This error can safely be ignored.

PL/SQL procedure successfully completed.
ERROR:
ORA-24344: success with compilation error
ORA-06512: at line 44
Warning: PL/SQL compilation errors.
Commit complete.
Posted by at

No comments:

Post a Comment


No one has ever become poor by giving

Subscribe to: Post Comments (Atom)