Performing Post-Upgrade Tasks

This chapter covers the following topics:

Database and System Administration Tasks

You must complete all of the tasks in this section to finish the upgrade. All tasks must be completed during system downtime on the Release 12.2 Oracle E-Business Suite instance.

  1. Verify completion of Compile Security concurrent program (required)

    You must wait and verify that the 'Compile Security' concurrent program successfully completed before attempting to log into EBS. You can run the following pl/sql block to view the status of this concurrent request:

    $ set serverout on
     declare
       res boolean;
       request_id number := null;
       phase varchar2(80);
       status varchar2(80);
       dev_phase varchar2(80);
       dev_status varchar2(80);
       message varchar2(255);
     begin
       res :=  fnd_concurrent.get_request_status(request_id,           
       'FND',
       'FNDSCMPI',
       phase,
       status,
       dev_phase,
       dev_status,
       message);
        if (res) then
           dbms_output.put_line('Request Id : ' || request_id);
           dbms_output.put_line('Phase : ' || phase);
           dbms_output.put_line('Status : ' || status);
           dbms_output.put_line('Completion Message : ' || message);
        else
           dbms_output.put_line('Unable to retrieve the information');
        end if;
     end;
     /
     .

    Results should appear as follows:

    • Phase: Completed

    • Status: Normal

    • Completion Message: Normal Completion

  2. Verify completion of concurrent programs (required)

    The upgrade process creates numerous concurrent program requests. Once you bring up the application tier, these programs run automatically to complete tasks such as data cleanup and upgrades to historical data, among others.

    Note: Before you continue, ensure that all concurrent programs generated by the upgrade have run successfully. Refer to Managing Concurrent Processes of this guide for a sample list of concurrent programs.

  3. Drop Obsoleted Product Schema (optional)

    Note: This step should be executed only after completing the Verify completion of concurrent programs post-upgrade task.

    1. Ensure no objects exist in the product schema to be obsoleted. If objects exist in the schema, then they should be removed before dropping the schema.

    2. After determining the schema is empty and no customizations or dependencies exist, the schema can be dropped using addropschema.sql.

      Usage: sqlplus apps @<AD_TOP>/patch/115/sql/addropschema.sql <SYSTEM_Password> <APPLSYS_Schema> <Obsoleted_Product_Schema_Name>

      Example:

      $ sqlplus apps/apps @<AD_TOP>/patch/115/sql/addropschema.sql manager applsys bsc

      Note: Enter the apps password when prompted.

    3. Obsolete Product Schemas that can be considered for dropping include:

      • ABM, AHM, AMF, AMW, BIL, BIV, BIX, BSC, CSS, CUE, CUF, CUI, CUN, CUP, CUS, DDD, EAA, EVM, FEM, FII, FPT, FTP, GCS, HCC, IBA, IBP, IGF, IGS, IGW, IMT, IPD, ISC, ITA, JTS, ME, MST, OKB, OKI, OKO, OKR, OZP, OZS, PFT, POA, PSB, RCM, RHX, RLA, VEH, XNC, XNI, XNM, XNS, ZFA, ZPB, ZSA.

      • The following schemas must be retained to support technical dependencies from other products:

        HRI, BIM, OPI, PMI, ENI, PJI, FTE, EGO

        Note: Some schemas may be active for other licensed products although these products are listed as obsolete in Planning for an Upgrade. In these cases, the functionality is removed.

  4. Drop dangling synonyms (optional)

    After dropping obsoleted product schema, you must run the following script to drop dangling synonyms:

    $ sqlplus APPS/****@DB @$AD_TOP/sql/adzd_drop_synonyms.sql
  5. Reset ORACLE schema passwords (recommended)

    During the upgrade, Rapid Install preserves the passwords that you previously set for existing products. However, as it creates a schema for each new product installed, if you did not enter a password in the Rapid Install wizard, then it sets up a default password derived from the product abbreviation (short name). To maintain product security, reset these default passwords now.

    Conditional Action: Perform the steps to change the passwords as described in the Oracle E-Business Suite Password Management section in the Oracle E-Business Suite Maintenance Guide.

  6. Change the WLS Admin Default Password (recommended)

    For security purposes, you should now change the default password for the WLS Admin account as follows:

    1. Run the following command to stop all application tier services except the Node Manager and the Admin Server:

      $ EBSAPPS.env run
       $ ADMIN_SCRIPTS_HOME/adstpall.sh –skipNM -skipAdmin
      
    2. Run the following command to change the WLS Admin password:

       $ perl FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl
         -action=updateAdminPassword
      

      Note: You will be prompted for the password information.

      For Windows Users:

      Run the following commands on Windows platforms:

      C:\> <ADMIN_SCRIPTS_HOME>\adadminsrvctl.cmd stop
      C:\> <ADMIN_SCRIPTS_HOME>\adnodemgrctl.cmd stop

      Start the Node Manager by running the following commands on Windows:

      C:\> cd %INST_TOP%\admin\install
      C:\> adsvNodeManager.cmd
      

      Exit the command prompt after executing 'adsvNodeManager.cmd' and start services from a new command prompt.

    3. Restart all services with the following command:

       $ adstrtal.sh

    Additional Information: For additional information refer to Oracle E-Business Suite Setup Guide Release 12.2 (Part No. E22953).

  7. Apply recommended patches (recommended)

    Use Patch Wizard to generate a list of recommended patches for your environment and apply the list of recommended patches to your environment.

    Suggested Reading: Additional information regarding the use of Patch Wizard is available in Oracle E-Business Suite Releases 11i and 12.x: Required Updates for Patch Wizard (Doc ID: 1267768.1)

  8. Apply recommended security patches (recommended)

    1. Oracle highly recommends that you apply the latest critical patch update to your Oracle E-Business Suite environment.

      Required Action: Go to the Critical Patch Updates, Security Alerts and Third Party Bulletin web page located at: www.oracle.com/technetwork/topics/security/alerts-086861.html.

      From this page, go to the latest Critical Patch Update page and select the link to Oracle E-Business Suite. From this page, select the link to the Oracle E-Business Suite MOS Note for the current CPU. Review and apply the CPU patches according to the referenced MOS note.

    2. Oracle highly recommends that you enable TLS. You will enable TLS after you upgrade to Oracle E-Business Suite Release 12.2. You must apply the prerequisite patch requirements to enable TLS.

      Required Action: Review the prerequisite patch requirements in Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID: 1367293.1), Section 5.1 for TLS 1.2 with Backward Compatibility, and Section 6.1 for TLS 1.2 Only. Apply all required patches and prerequisites to enable TLS.

  9. Install online help (recommended)

    To install the American English online help, run the database portion of the online help patch (u10201000.drv). It is located in $AU_TOP/patch/115/driver directory. You must apply the American English online help patch driver ($AU_TOP/patch/115/driver/u10201000.drv) using AD Online Patching (adop) with phase=apply hotpatch=yes and options=nocopyportion,nogenerateportion,forceapply.

    $ adop phase=apply patchtop=$AU_TOP/patch/115 patches=driver:u10201000.drv options=nocopyportion,nogenerateportion,forceapply hotpatch=yes
  10. Apply online help for Oracle E-Business Suite Release Update Pack (recommended)

    Action: Refer to the Oracle E-Business Suite Release Update Pack Readme (applied in the Performing the Upgrade chapter) and apply the corresponding Oracle E-Business Suite Release Online Help patch.

  11. Apply latest product patches (required)

    Determine the latest product-specific patches. Then, download the American English patches. You must apply the patches using AD Online Patching (adop).

    Additional Information: See Patch Wizard Main Page in Oracle E-Business Suite Maintenance Procedures Guide.

    If you have languages other than American English registered in your system, then follow instructions in the following step.

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

    If you have not already granted flexfield value set access in a previous version of Release 12.2, then you must perform this step.

    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 user can create or update values in the Values window.

    Note: Follow the required steps in the Flexfield Value Set Security chapter in the Oracle E-Business Suite Flexfields Guide, Release 12.2.

  13. Installing NLS upgrade patch driver and NLS Online Help (conditional)

    For additional NLS languages active in the system, once the American English upgrade and recommended Release Update Pack level have been applied, you can then upgrade your NLS software for existing languages by performing either one of the following steps:

    1. Using the Translation Synchronization Patch followed by applying the NLS Online Help patch if available.

    2. Installing the R12.2.0 NLS software available in Oracle Software Delivery Cloud, followed by installing NLS versions of all US patches applied to your system including recommended Release Update Pack. You must then apply the NLS Online Help patch if available.

    Conditional Action: All NLS patches, including the Translation Synchronization Patch must be called through AD Online Patching (adop). Follow instructions in the Post-Installation Tasks section of the Oracle E-Business Suite NLS Release Notes, Release 12.2 (Doc ID: 1314621.1) for your release level. For additional information, refer to Oracle E-Business Suite Translation Synchronization Patches (Doc Id: 252422.1).

  14. Re-enable custom triggers, constraints, and indexes (conditional).

    During the upgrade, custom triggers or constraints may have been modified. If you disabled these triggers and constraints, then identify any data updates that must be made before you re-enable them.

    If you dropped any custom indexes, then review the new data model to determine if the index is necessary before you redefine it.

  15. Manually add custom redirects and resources to configuration files (conditional)

    The Allowed Redirects and Allowed Resources features are enabled by default after your upgrade. Consequently, if you use custom redirects and resources, such as JSPs and servlets, in your environment, then you must manually add these to your configuration files for allowed redirects and allowed resources, respectively.

    Additional Information: For additional information, see 'Allowed Redirects' and 'Allowed Resources' in the Oracle E-Business Suite Security Guide.

  16. Update and verify custom responsibilities (conditional)

    Verify that all custom responsibilities use the correct menu. From the System Administrator responsibility, navigate to Security > Responsibilities. Query each custom responsibility and update as necessary.

  17. Migrate custom development to new technologies (recommended)

    In this release, Oracle E-Business Suite is migrating to new technologies in certain areas. If you have built custom development on the out-dated technologies, you should migrate to the new technologies as part of the upgrade.

    Note: See Preparing Custom Development for Next Oracle Applications Release (Doc ID: 374398.1) for more information.

    mod_plsql:

    If you have custom development on mod_plsql, migrate your web pages to Oracle Application Framework.

    Note: See Oracle Application Framework Developer's Guide (Doc ID: 1315485.1) for more information.

    Oracle Reports Server Reports:

    If you have custom development that uses reports that are run through Oracle Reports Server, the following migration alternatives are available.

    New Technology Advantages and Considerations
    Convert to Oracle XML Publisher Prepares your application both for E-Business Suite Release 12 and for Oracle Fusion Applications. Allows you to take advantage of the benefits of XML Publisher. Some automated tools are available to help you migrate to XML Publisher. See Oracle XML Publisher Administration and Developer's Guide for more information.
    Convert to Oracle Application Framework May be appropriate for some reporting needs. However, note that no automated migration tools are available. You must rewrite any charts using the Framework Charting tool (BI Chart Bean). See Oracle Application Framework Developer's Guide (Doc ID: 1315485.1).
    Run through the Concurrent Manager If you follow coding standards, you must modify your PL/SQL code to meet the concurrent manager standards. In particular, you must use some user exits. Rewrite any charts using the Oracle Reports Charting tool (BI Chart Bean). See Oracle E-Business Suite Developer's Guide and Oracle Reports: Building Reports for more information.

    Oracle Graphics Integrations with Oracle Forms:

    If you have custom development that uses Oracle Graphics (Charting) integrated with Oracle Forms, the following alternatives are available.

    New Technology Advantages and Considerations
    Convert both the form and the chart to a Framework-based application. Prepares your application both for Release 12 and for Oracle Fusion Applications.
    Convert the chart to a Framework-based page that can be launched from Oracle Forms. See Oracle Application Framework Developer's Guide (Doc ID: 1315485.1)

    AK Mode:

    • Personalizations

      Personalized Oracle E-Business Suite Framework-based pages in the AK repository, are automatically migrated from AK to MDS during the upgrade - if the AK and MDS repositories are in the same database instance.

      The upgrade does not automatically migrate custom personalizations if the AK and MDS repositories are in separate instances. In this case, you must run the Personalization Migration tool manually to perform the migration.

      Note: See Migrating AK Personalizations in Oracle Application Framework Personalization Guide for more information.

    • AK/ICX Web Inquiries

      If you have previously used AK/ICX Web Inquiries, then use the Oracle Application Framework Search feature to recreate search regions that can be personalized.

      Note: See Implementing Specific UI Features in Oracle Application Framework Developer's Guide (Doc ID: 1315485.1)

  18. Migrate the CUSTOM library (conditional)

    Before you copy custom code in the CUSTOM library to the new directory structure, refer to the backup you previously created and verify that the customizations are valid for the new version of Oracle Applications.

    For valid customizations, place a copy of the new CUSTOM library (CUSTOM.pll) in a safe place. It is located in the $AU_TOP/resource directory (UNIX), or the %AU_TOP%\resource directory (Windows). Then, make a copy of the old Oracle Forms CUSTOM library and place it in the new directory. Upgrade to Oracle Forms Developer 10g by regenerating the library. Or, you can cut and paste the existing custom code into the new library, and then regenerate it.

    Note: See Using the CUSTOM Library in the Oracle E-Business Suite Developer's Guide.

  19. Copy and re-customize modified scripts or reports (conditional)

    Copy custom shell scripts or reports to the custom application directories and re-customize the copy as necessary.

    Note: See Customization Standards in Oracle E-Business Suite Developer's Guide.

  20. Copy existing custom start scripts (conditional)

    If you have customized the concurrent manager startup script ($FND_TOP/bin/startmgr.sh on UNIX), then you must copy the customized script from the old environment to the new environment. You should then verify that your customizations are valid for the new environment.

    Warning: Oracle does not recommend customizing this script. If you perceive a need to change this script, then contact Oracle Support before making changes. For more information, see the Oracle E-Business Suite Setup Guide.

    Note: The default location in UNIX for the startmgr script is $FND_TOP/bin. For more information, see the Oracle E-Business Suite Setup Guide.

  21. Review user responsibility assignments (recommended)

    Although user/responsibility assignments are preserved during the upgrade, the effective permissions granted by the seeded responsibilities, menus, functions, and report security groups may have changed. Use the information on the Forms or Security reports in the System Administrator responsibility to confirm that permissions granted by responsibilities continue to meet the requirements of the job roles (without granting more privileges than are necessary).

    Note: See Organizing Programs into Request Groups in the Oracle E-Business Suite Setup Guide for more information.

  22. Configure applications client software for forms applet (required).

    Action: The connection between the client and the applications forms is provided through an applet in the client web browser. Instead of using the browser's own JVM, Oracle E-Business Suite uses the Sun Java (J2SE) native plug-in. You can find download instructions in Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 (Doc ID: 393931.1).

Alerts

These tasks apply to Oracle Alerts.

  1. Associate organization names with custom Alert definitions (conditional)

    Manually update custom alerts that you want to assign to a particular organization:

    1. As the Alerts Manager, navigate to the Alerts form (Alert > Define) and query the definition.

    2. Choose Alert Details, then display the Installations tabbed region in the Alert Details window.

    3. Enter the ORACLE ID and organization name that you want to run this alert against.

    4. Make sure you check Enabled before saving the changes.

Multiple Organizations

These tasks apply to Multiple Organizations for Oracle E-Business Suite.

  1. Set operating unit mode for customizations (conditional)

    With the introduction of multiple organizations In this release, an applications responsibility can access multiple operating units. Some concurrent programs have been enhanced to be able to process multiple operating units simultaneously, whereas for most others, the operating unit must be specified when you run the program.

    To support this new functionality, concurrent programs are defined with an operating unit mode of S for single operating unit or M for multiple operating units. This mode is set automatically during the upgrade.

    However, if you have modified the definition for any concurrent programs, then the upgrade will not set the operating unit mode in order to preserve the customization. Depending on how you run the customized program, you may need to set the operating unit mode manually. Run the following SQL command to set a concurrent program for a single operating unit:

    $ UPDATE FIND_CONCURRENT PROGRAMS
    $ SET MULTI_ORG_CATEGORY='S'
    $ WHERE CONCURRENT_PROGRAM_NAME = '<your program name>'

    Enter M instead of S for multiple operating units.

    If you want to know which setting is appropriate for a given program, then you may review the setting in the appropriate .ldt file.

    Note: If you have customized the concurrent program definition, this setting may not be appropriate given the way you use the program.

Oracle Web Applications Desktop Integrator

These steps apply to Oracle Web Applications Desktop Integrator and to products that use Oracle Web Applications Desktop Integrator to generate spreadsheets.

  1. Recreate existing spreadsheets (conditional)

    Applies to 11i release level: All

    TUMS step key: N/A

    Spreadsheets created in previous versions of Oracle Web Applications Desktop Integrator do not interact with Oracle E-Business Suite products after the upgrade. You must replace existing spreadsheets with ones that you create using the new technology stack. Follow the procedures in your product-specific documentation to create the new spreadsheets.

Workflow

These steps apply only to Oracle Workflow.

  1. Update Status Monitor URLs (required)

    Applies to 11i release level: All

    TUMS step key: N/A

    Oracle Workflow provides URL access to the Status Monitor through the Application Framework Agent, rather than through the PL/SQL Web agent used in Release 11i. Run the Workflow Plsql Cartridge Dependency Removal From Data concurrent program to update the Status Monitor URLs that appear in existing workflow attribute values to the new Web agent structure. The program updates item attribute values for active workflow processes and message attribute values for open notifications.

    Note: The update for message attribute values applies only to notifications accessed through the Worklist Web pages. Status Monitor links in e-mail notifications that were sent or generated before the upgrade cannot be automatically updated. Log on to Oracle E-Business Suite separately to access the Status Monitor after the upgrade.

Oracle E-Business Suite Integrated SOA Gateway

Conditional Action: Oracle E-Business Suite Integrated SOA Gateway requires manual post-installation steps. If you want to use the Oracle E-Business Suite Integrated SOA Gateway feature for Web service generation, deployment, and invocation, then perform the steps documented in Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID: 1311068.1).

Note: After the upgrade, the deployed WSDL URL for a generic XML Gateway service will be changed. You may have to replace it with the new WSDL URL and service location or address accordingly in Web service clients while invoking the generic XML Gateway service. For more information about XML Gateway Web services, see the Oracle XML Gateway User's Guide.

Oracle XML Gateway

Conditional Action: Complete the installation and setup tasks described in Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID: 1311068.1) for enabling Oracle E-Business Suite Integrated SOA Gateway and generic XML Gateway services.

Note: After the upgrade, the deployed WSDL URL for a generic XML Gateway service will be changed. You may have to replace it with the new WSDL URL and service location or address accordingly in Web service clients while invoking the generic XML Gateway service. For more information about XML Gateway Web services, see the Oracle XML Gateway User's Guide.

Customer Relationship Management Tasks

Complete the tasks in this section before you allow users to use Oracle Customer Relationship Management (CRM) products.

Email Center

These tasks apply only to Oracle Email Center.

  1. Migrate Email Center data (recommended)

    Applies to 11i release level: All

    TUMS step key: IEM_PROD_CHK

    You can migrate Email Center data to the new architecture in two phases: live messages and historical messages. To accommodate the migration, a set of migration tools is delivered with Email Center in this release. They consist of a Download Processor, concurrent programs, and a Migration Console.

    If you choose to perform the data migration, which includes both configuration and email data, then these tools are available to help with this process. Before you launch the migration process, you must:

    • Stop the Email Server middle-tier process (IMAP, Postman, and so on)

    • Stop or cancel pending Email Center concurrent requests

    • Stop all Apache servers

    • Log out of Email Center while the data migration is running

    • Make sure there are no live messages in the pre-processing queue or pending outbound requests for the Outbox Processor. The migration tools check for these conditions and displays the data on the Migration Console.

    Note: Refer to Oracle Email Center Migration to Release 12 (Doc ID 549036.1) for more Email Center migration specific details.

Mobile Field Service

These tasks apply only to Oracle Mobile Field Service.

  1. Migrate to the New Mobile Field Service Application (conditional)

    Applies to 11i release level: All

    TUMS step key: CSM_SYNC_DATA_POST

    Oracle Mobile Field Service has been redesigned for this release. If you use this product, complete the steps described in Oracle Mobile Field Service Post-upgrade Instructions for Oracle Applications Release 12 (Doc ID: 386682.1).

Sales and Telesales

These tasks apply only to Oracle Sales and Telesales. For upgrading from ASN.B to Release 12, see: Sales upgrade from ASN.B to Release 12. ASN.B is Oracle Sales Mini-pack 11i.ASN.B. Refer to About Oracle Sales Mini-pack 11i.ASN.B (Doc ID: 292871.1).

  1. Run concurrent programs (required)

    Applies to 11i release level: All

    TUMS step key: AS_DENORM_CP_CHK

    Perform the following steps to update and refresh the AS_ACCESSES_ALL and AS_SALES_CREDITS_DENORM tables:

    • From the Oracle Sales Administrator responsibility, navigate to Concurrent Requests > Run.

    • Run the "Update as_accesses_all denorm flag" request set.

    • Run the "Refresh of as_sales_credits_denorm" concurrent program.

      Note: If you are at the 11.5.10.2CU release level, then you can reduce downtime by running the concurrent process request set "Update as_accessess_all denorm flag" as a pre-upgrade step.

  2. Migrate Sales methodologies for opportunities (required – application specialist)

    Applies to 11i release level: All

    TUMS step key: N/A

    This step must be performed by the Sales and Telesales application specialist before you allow users to log on.

    This release requires you to set a sales methodology if a sales stage is specified in an opportunity. Once specified, you cannot change to any other sales methodology. To avoid errors and improper migration, your application specialist must follow the instructions in the Migrate Sales Methodologies for Opportunities section of Sales and Telesales in the Upgrade by Request appendix.

  3. Migrate Sales credits (required – application specialist)

    Applies to 11i release level: All

    TUMS step key: N/A

    This step must be performed by the Sales and Telesales application specialist before you allow users to log on.

    In this release, only one sales person per opportunity line receives the entire revenue credits for that line. The Release 11i Sales feature that allowed multiple sales people to receive credits on a single opportunity line is obsolete. Before you can use the upgraded Sales and Telesales products, your application specialist must follow the instructions in the Migrate Sales Credits section of Sales and Telesales in the Upgrade by Request appendix.

Sales Upgrade From 11i.ASN.B to Release 12.2

Customers upgrading from 11i.ASN.B to Release 12.2 must run two concurrent requests and are not required to run all the 11i.ASN.B enabling steps a second time:

  1. Run ASN Migrate Duplicate Salesrep Main Program.

    This concurrent request removes duplicate sales team members. You should run this request at downtime as part of the upgrade process.

  2. Run ASN Post Upgrade Log and Customer Update.

    This concurrent request updates the endday log flags for Sales Credit, Opportunity Lines, and synchronizes the Customer Id of opportunity sales team with opportunity header data. You can run this request after the upgrade process at up time.

Financials and Procurement Tasks

Complete the tasks in this section before you allow users to log on to Oracle Financials and Procurement products.

Advanced Collections

This task applies for customers using Advanced Collections with Strategies.

Post Migration Verification Steps

  1. From the Collections Administrator responsibility, confirm the Collections Business Level in the Setup Checklist.

  2. From the System Administrator responsibility, start the concurrent program Workflow Background Process for the following Item Types:

    • IEXSTRY - IEX: Collection Strategy Work Flow

    • IEXSTFFM - IEX: Strategy Fulfilment Mailer

    • IEXSTRCM - IEX: Strategy Custom Work Flow

  3. Run the script $IEX_TOP/patch/115/sql/iexumchk.sql to set the profile option Unit of Measure (UOM) to 'time'.

Financials for India

These tasks apply only to Oracle Financials for India.

  1. Apply custom logic for Projects functionality (conditional)

    Applies to 11i release level: All

    TUMS step key: JAI_CHECK_PA_CUST

    In this release, Oracle Financials for India (JAI) supports a Projects Costing/Billing solution, which includes a custom version of the Projects commitment view and creates a pre-processing extension registration in the transaction source definition for Purchase Receipts. Because this custom logic applies only to customers who want to use the Projects functionality provided by JAI, the customized files are released as a standalone patch (12699629).

    Refer to the following table to determine whether to apply this patch to your system:

    Action Release 11i uses JAI Projects? Release 12.2 uses JAI Projects? Apply Patch?
    Upgrading from Release 11i to Release 12.2 No Yes Yes
    Upgrading from Release 11i to Release 12.2 Yes Yes Yes
    Upgrading from Release 11i to Release 12.2 No No No

    Note: See Oracle Financials for India Implementation Guide for more information.

Internet Expenses

These tasks apply only to Oracle Internet Expenses.

  1. Ensure that document categories have valid sequences (conditional)

    Applies to 11i release level: All

    TUMS step key: OIE_DOC_SEQUENCE_CHECK

    Internet Expenses creates employee invoices using the document category Expense Report Invoices (EXP REP INV). You should ensure that a valid sequence is assigned to this document category.

    In addition, Internet Expenses no longer creates credit card provider invoices using the document category Mixed Invoices (MIX INV). Instead, it uses the Payment Request (PAY REQ INV) document category. You should ensure that a valid sequence is assigned to the Payment Request (PAY REQ INV) document category as well.

Payments

These tasks apply only to Oracle Payments (renamed from iPayments in Release 11i).

  1. Enter encryption key for Payments (conditional)

    Applies to 11i release level: All

    TUMS step key: IBY_WALLET_SETUP

    If you used Oracle Applications Credit Card Encryption in Release 11i, then enter the same value you used for your system security key (also known as private key) in the Oracle Wallet Manager configuration. Then, complete the encryption setup on the System Security Options page. You must complete this setup before you begin any payment processing or transactions will fail.

    Note: Refer to How To Rotate/Migrate Oracle Payments System Key in R12 ( Doc ID: 1330774.1)

  2. Complete payment profile options for Netherlands (conditional)

    Applies to 11i release level: All

    TUMS step key: IBY_PMT_FILE_FORMAT_NL

    If you used global descriptive flexfields to control payment file formatting in Release 11i , then edit the Oracle Payments EFT payment format template to pass required EFT values or create the values as a bank instruction on the Payment Process Profile in Oracle Payments.

    You must complete this task before you begin any invoice or payment processing. If it is not complete, then you cannot track the required attributes for your transactions.

    Note: See Financials Upgrade Impact for more information.

  3. Complete Danish payment means and channels (conditional)

    Applies to 11i release level: All

    TUMS step key: IBY_PMT_MEANS_DK

    If you used global descriptive flexfields to control payment means and channels in Release 11i, then edit the Oracle Payments Danish payment format template to pass payment means and payment channel information before you begin any invoice or payment processing. Also, enter required payment validations for each payment method (migrated from payment categories) in Oracle Payments.

    You must complete this task before you can track the required attributes for your transactions.

    Note: See Financials Upgrade Impact for more information.

  4. Complete remittance advice controls for Italy (conditional)

    Applies to 11i release level: All

    TUMS step key: IBY_REMIT_ADV_CONTROL_IT

    If you used global descriptive flexfields to control the remittance advice controls (Profile Option for Company Details) for Italy in Release 11i, then edit the Oracle Payments EFT payment format template to control whether the company details are printed.

    If you do not complete this task before you begin any invoice or payment processing, you cannot track the required attributes for your transactions.

    Note: See Financials Upgrade Impact for more information.

Oracle Purchasing

Complete the installation, configuration, and deployment steps to use Oracle BPEL Process Manager 11g with Oracle E-Business Suite Release 12.2.0. See My Oracle Support (Doc ID: 1362803.1).

Note: The prebuilt BPEL business processes in Oracle E-Business Suite Release 12.2 are certified with Oracle SOA Suite 12c, Oracle SOA Suite 11g. The BPEL 10g based prebuilt integrations are not supported in Oracle E-Business Suite Release 12.2. Customers upgrading to Oracle E-Business Suite Release 12.2 from 11i must migrate to Oracle SOA Suite 11g or Oracle SOA Suite 12c. Refer to Integrating Oracle E-Business Suite Release 12.2 with Oracle BPEL in Oracle SOA Suite 11g R1 (Doc ID: 1584883.1) and Integrating Oracle E-Business Suite 12.2 with BPEL in SOA Suite 12c (Doc ID: 1951625.1). Follow the respective documentation to deploy these BPEL processes.

Oracle Purchasing (available as part of Oracle Order Procurement) is integrated with Oracle Transportation Management. If you have licensed both Oracle Transportation Management and Oracle Order Purchasing and will use Oracle Transportation Management with Oracle Purchasing, then perform the post-update steps outlined in Oracle Transportation Management Integration with Oracle E-Business Suite Post-Update Steps, Release 12.2.0 (Doc ID: 1362803.1).

Cash Management

The Bank Account Type values are now located in the Cash Management Lookups. The seeded values are SAVINGS, CHECKING and OTHER. Review your bank account type values used in 11i and add your custom values to the Bank_account_type lookup in the Oracle Cash Management Lookups window.

Human Resource Management (HRMS)

Complete the tasks in this section before you allow users to log on to Human Resources Management products.

Human Resources

  1. Apply latest HRMS Legislative Updates (required)

    Applies to 11i release level: All

    TUMS step key: PER_HRGLOBAL

    To maintain required legislative compliance, you must apply all legislative data updates. The updates are maintained regularly to be in line with government and country-specific legal requirements. See the latest HRMS (HR Global) Legislative Data Patch (Doc ID: 1469456.1) for information and instructions on how to ensure that your system is up to date.

    Note: If you are using only Oracle HR Shared for use with another Oracle E-Business Suite product, then DO NOT apply this legislative data.

  2. Check downtime reduction report (recommended)

    Applies to 11i release level: All

    TUMS step key: PER_R12_DTR

    Log on as System Administrator and submit the Data Update Process Status Report concurrent request. It identifies a number of data update tasks, which may run for an extended period of time if you have a large volume of data that requires manipulation.

    Note: See Guide to the Data Update Status Report (Doc ID: 315932.1) for more information.

Payroll

These tasks apply only to Oracle Payroll.

  1. Install or Update Vertex for Payroll (required)

    Applies to 11i release level: All

    TUMS step key: PAY_VERTEX

    Oracle Payroll uses the Vertex Quantum Payroll Tax Series in the United States and Canada. The HRMS data in this release contains version 4.0 of this third-party product. If you run Oracle Payroll in the United States or Canada, see the information about advanced configuration steps allowed by Payroll, and the information about installing or updating the Vertex software, in Installing Quantum for Oracle Payroll (Doc ID: 224273.1).

    Note: The Quantum setup (through concurrent programs "Quantum Program Update Installer" and "Quantum Data Update Installer") must be run before running the payroll.

  2. Run the QuickPay Exclusions Data Upgrade process (recommended)

    Applies to 11i release level: All

    TUMS step key: PAY_QUICK_EXCL_UPG

    If you have not previously run the QuickPay Exclusions Data Upgrade process, you should do so now. From the System Administrator responsibility, run the Generic Upgrade Mechanism concurrent program from the Processes and Reports menu. It accepts a single parameter (the name of the data update process to be executed). Set the parameter to QuickPay Exclusions Table Upgrade.

  3. Create translated Database Item names for Japanese Localizations (conditional)

    Applies to 11i release level: All

    TUMS step key: PAY_QUICK_EXCL_UPG_JP

    If you currently use, or plan to use, Oracle Payroll in an NLS environment, apply the consolidated hrglobal translation patch to deliver translated names for Element Types, Element Input Values, Balance Types, Balance Dimensions, and Global Values. Then, run the Generate Payroll Dynamic Database Item Translations concurrent program and check the log file for errors.

    Note: See HRMS (HR Global) Legislative Data Patch (Doc ID: 1469456.1) for details.

    This program invalidates Customers' Formulas if they contain variables whose names clash with the new Database Item names. Any invalidated Formulas are listed in the concurrent program log. You must correct and re-compile them before they can be used. If a seeded Formula contains a variable whose name clashes with a new Database Item name, that new name will not be applied in order to maintain seed data consistency.

    When running the concurrent program, selecting Yes for the parameters Element Types, Element Input Values, and Balances causes translated Database Items to be created using the corresponding translations. Select Yes for the Localization parameter only if you run payrolls for countries that provide localized database item translation code (see New and Changed Components section of the About Doc for each country). If you select No for all parameters, the program logs any errors for Global Value translated Database Items.

  4. Compile Japanese flexfields after generating messages (required)

    Applies to 11i release level: All

    TUMS step key: PAY_COMPILE_FLEX_JP

    A number of the Japanese Flexfields have value sets with translated prompts for some of the Quickpick columns. These values must be seeded in the NLS language for the flexfield to compile cleanly. The seeding occurs when the messages are compiled. You may see some Japanese flexfields that appear as invalid. Resolve this issue by using AD Administration first to generate messages, and then to re-generate flexfields that failed to cleanly compile.

  5. Enable Subledger Accounting (SLA) (conditional)

    Applies to 11i release level: All

    TUMS step key: PAY_ENABLE_SLA

    If you intend to enable Subledger Accounting for Oracle HRMS in the first available version of Release 12, then you must perform a manual upgrade sequence to support your transfers to SLA. The manual sequence includes these steps:

    1. Set up Journal Line Definitions

    2. Set up the Application Accounting Definition

    3. Set up the Method for each chart of accounts

      Note: See Performing a Manual Upgrade to Enable Subledger Accounting (SLA) for Oracle HRMS Release 12 (Doc ID: 399632.1) for details.

    This manual upgrade sequence is required only for the current Release 12 software. However, an automated version is planned for a future release. When it is made available, the manual upgrade sequence will not be necessary.

    See Performing a Manual Upgrade to Enable Subledger Accounting (SLA) for Oracle HRMS Release 12 (Doc ID: 399632.1) for details about releases that require you to run the upgrade sequence manually.

    Note: Optionally, if you want to migrate historical payroll data to SLA that has been posted to GL prior to availability of SLA functionality, then run the concurrent program Upgrade Historical Payroll Data to SLA for payroll system data synchronization.

Projects Tasks

Complete the tasks in this section before users log on to Oracle Projects products.

Project Costing

Applies to 11i release level : All

Compile all Fast Formulas via FFXBCP (Doc ID: 167689.1)

This step applies to all customers upgrading to Release 12.2 and wanting to use the HR Rate by Criteria for labor rates, to be used in forecast or labor cost distribution in the Projects application.

Property Manager

These tasks apply only to Oracle Property Manager.

  1. Create accounts distribution for leases (conditional)

    Applies to 11i release level: All

    TUMS step key: PN_CREATE_ACCT_DIST_LEASE

    If a lease with normalized payment terms does not contain a liability and accrued liability account or normalized billing terms, then create an accounts distribution. Navigate to View > Requests > Submit a new request > Create Accounts Distribution. Supply the following information:

    • Lease Class: Create accounts distributions for revenue leases, expense leases, or subleases

    • Lease Number range: Range of leases for which you want to create the accounts distribution

    • Location Code range: Location or a range of locations if you want to create accounts distributions for leases with tenancies for the specified location range

    • Account information: Appropriate Receivable, Accrued Asset, Liability, and Accrued Liability accounts depending on whether you are creating an accounts distribution for expense leases, or revenue leases and subleases

Oracle Fusion Project Management and E-Business Suite Projects Coexistence

You can use Oracle Fusion Project Management to manage your projects and resources. After you are ready to start performing financial management activities such as collecting costs and billing, you can import the project into Oracle E-Business Suite (EBS) Projects, and generate the project budget.

Use Oracle Fusion Project Management for collaboration, scheduling, resource management, and progress tracking. As resources report actual hours in Oracle EBS Projects, export the resource to Oracle Fusion Project Resource Management and track the resource utilization.

You must complete the following post-install steps to enable the coexistence:

  1. Get the SSL certificate.

  2. Import the SSL certificate to the EBS instance.

  3. Set the Username token authentication credentials for the service.

  4. Add the service invocation subscription to invoke the service.

  5. Add a subscription to the events.

Applying Patches

Download and apply patch 24610809:R12.PJT.C from My Oracle Support.

Obtain the SSL certificate

Complete the following steps to export the SSL certificate from your browser. The following steps describe the process using Mozilla Firefox:

  1. Click the site identity button located in the address bar of your browser.

  2. Click the More Information button.

  3. Select Security.

  4. Click View Certificate.

  5. Review the certificate details on the General tab. Verify that the imported SSL certificate is valid.

  6. Select the Details tab.

  7. Click Export…

  8. Export the certificate to your directory.

  9. Save the certificate using the host name of the web service provider. For example, if the host name is *.example.com, then save the certificate as: *.example.com.cer.

Importing the SSL Certificate to the EBS Instance

Perform the following steps to transfer the exported certificate to the EBS instance:

  1. Use Secure File Transfer Protocol (SFTP) to export the server name to the EBS instance. For example, sftp <servername>.example.com.

  2. Enter your username and password when prompted.

  3. Use the put command to enter the certificate into the instance. For example, put *.example.com.cer.

  4. Log in to the EBS instance using telnet command.

  5. Select a directory in which to save the certificate file.

  6. Import the certificate to the EBS keystore. Ensure that you are in the same directory where you saved the certificate.

    • Use the keytool command to complete the task. For example, if your certificate name is *.example.com.cer, then the command will be:

      keytool -import -alias FusionCert -file *.example.com.cer -keystore $AF_JRE_TOP/lib/security/cacerts.

  7. Enter the keystore password when the system requests it.

  8. Restart the EBS server after importing the certificate.

  9. To update the certificate to an updated release, delete the previously imported certificate. Use the following command:

    keytool -delete -alias <mydomain> -keystore $AF_JRE_TOP/lib/security/cacerts.

Setting the Username Token Authentication Credentials for the Service

Use the following information to set the user name token credentials:

  1. 1. sqlplus apps/apps@db @$FND_TOP/sql/afvltput.sql <Module> <Key> <Value> to store your key, module, and password.

    Note: The password is stored in the fndvault and remains secured from the end user when creating subscriptions. Users provide the module and the key and must remember it for later use.

  2. Enter unique Key and Module pairs to identify passwords.

    • Module: PA

    • Key: PA_MGMT_SERVICES_USA

    • Value: Welcome1

Adding the Service Invocation Subscription to Invoke the Service

Use the following Service Invocation Subscription details to invoke the service:

Adding a Subscription to the Events

Perform the following steps after you have added the Fusion SSL certificate to the EBS instance:

  1. Sign in to the Oracle E-Business Suite application using login credentials that provide access to the Workflow Administrator Web Applications responsibility.

  2. Navigate to Workflow Administrator Web Applications > Administrator Workflow > Business Events.

  3. You must add four business events. They include:

    • oracle.apps.pa.coexist.project.invoke

    • oracle.apps.pa.coexist.projectplan.invoke

    • oracle.apps.pa.coexist.update.task.invoke

    • oracle.apps.pa.coexist.fileupload.invoke

  4. Search for the predefined business event oracle.apps.pa.coexist.project.invoke.

  5. Click GO.

  6. Find your search result under the Results: Events section. Click Subscriptions.

  7. Click Create Subscription.

  8. In the Create Event Subscription page, enter the following subscription details:

    1. System: <EBS Instance>

    2. Source Type: Local

    3. Event Filter: This field is auto populated

    4. Execution Phase: Select a value between 1-99

    5. Status: Enabled

    6. Rule Data: Message

    7. Action Type: Invoke Web Service

    8. On Error: Stop and Rollback

  9. Click Next.

  10. In the Select a WSDL Source section, enter the WSDL URL.

    • The WSDL URL is the URL of the Oracle Fusion Cloud instance you are using to register this event.

    • Enter the URL in the following format: https://<host name>.<domain name>: port. For example, enter:

      https://101.us.vision.com:98335/pjtCommonProject/ProjectServiceV2?wsdl.

  11. Click Next to select the service. The Service Name field is populated with ProjectServiceV2 in the Select Service section.

  12. Click Next and select the service port.

  13. Click Next and select the operation. In this example it is findProjectPlan.

    Note: All services used for integration with Oracle E-Business Suite are synchronous services.

  14. Click Next to complete the subscription registry and link it with the predefined business event.

  15. In the Create Event Subscription – Invoke Web Service section. The application provides the Subscription Parameters and User ID with access to the service and the parameters to retrieve the password from the vault. For customizations in Service Invocation, users can extend the default java class oracle.apps.fnd.wf.bes.WebServiceInvokerSubscription and provide the extended class in place of Java Rule Function.

  16. Add the other three business events using the above steps 4 through 15. The corresponding operations and service names for each business event include:

    • Business Event: oracle.apps.pa.coexist.projectplan.invoke

      Operation: findProjectByProjectId

      Service Name: ProjectServiceV2

    • Business Event: oracle.apps.pa.coexist.update.task.invoke

      Operation: updateProjectPlan

      Service Name: ProjectServiceV2

    • Business Event: oracle.apps.pa.coexist.fileupload.invoke

      Operation: uploadFileToUcm

      Service Name: ERPIntegrationService

Supply Chain Management Tasks

Complete the tasks in this section before users log on to Supply Chain Management products.

Mobile Applications

These tasks apply only to Oracle Mobile Applications.

  1. Review MWA Server Administration Task Changes (required)

    Applies to 11i release level: All

    TUMS step key: MWA_SERV_ADMIN

    The Mobile Applications (MWA) Server administration configurations, command scripts, and security enhancements for the command scripts used to manage mobile server startup and shutdown Services are in a new location. Also, MWA Services can be managed using the Oracle Applications Manager (OAM) AutoConfig utility. See Oracle Mobile Wireless Application: Release 12 Server Procedure Changes (Doc ID: 394495.1) for more information.

Oracle Process Manufacturing

These tasks apply only to Oracle Process Manufacturing. For general information related to migration, refer to Oracle Process Manufacturing (OPM) Release 12.1 Migration (Doc ID: 376683.1). Disregard the Migration Checklist.

Note: Do not open the Oracle Process Manufacturing application until you complete all of the following tasks. Any patch referenced in this document must be applied using the Oracle ADOP utility.

  1. Complete Inventory Convergence for OPM (conditional)

    Applies to 11i release level: All

    TUMS step key: GMA_INV_CONVERGENCE

    If you do not have OPM enabled in your system, then you can omit this step. Refer to the OPM Migration Checklist document which is linked from Oracle Process Manufacturing (OPM) Migration from 11i to Release 12.1 and Higher (Doc ID: 376683.1) and perform the steps in the order listed under the Post-Migration section.

    Note: See the Oracle Process Manufacturing Migration Reference Guide for details on data migration. In addition, refer to the OPM System Administration User's Guide and the OPM Process Execution Forms Will Not Open In R12 After Migration/Upgrade article (Doc ID: 1354718.1).

Oracle Product Hub

These tasks apply only to Oracle Product Hub.

  1. Creating Versions of Item Catalog Categories (recommended)

    Applies to 11i release level: All

    TUMS step key: EGO_VERSION_ICC

    In EBS release 12.1.2 and higher, you can choose to create a different version of an item catalog category (ICC) when you change a transaction attribute for structure component in the ICC if you set the profile option "Enable PIM for Telco Features" to Yes. When you enable the use of ICC versions, the system automatically creates a draft version for every new ICC created. You cannot choose to create versions for some ICCs, but not others. After upgrading from a release prior to 12.1.2 and after setting the profile option "Enable PIM for Telco Features" to Yes, you must create a released version for each existing ICC. Oracle provides an upgrade API that automatically performs this task. A database administrator can invoke the upgrade API from the back end after you set the profile option "Enable PIM for Telco Features" to Yes.

    Upgrade API Sample Call

    $ DECLARE
    		uid NUMBER;
    		rid NUMBER;
    		rad NUMBER;
    		sgid NUMBER;
    $ BEGIN
    $ SELECT
    $ USER_ID,RESPONSIBILITY_ID,RESPONSIBILITY_APPLICATION_ID,SECURITY_GROUP_ID
    $ INTO
    		uid, rid, rad, sgid
    $ FROM
    		FND_USER_RESP_GROUPS
    $ WHERE
    $ USER_ID = (SELECT USER_ID FROM FND_USER WHERE USER_NAME ='SYSADMIN')
    $ AND RESPONSIBILITY_ID =
    $ (SELECT RESPONSIBILITY_ID FROM FND_RESPONSIBILITY_VL WHERE
    $ RESPONSIBILITY_KEY = 'SYSTEM_ADMINISTRATOR');
    $ FND_GLOBAL.apps_initialize (uid, rid, rad, sgid);
    $ ego_p4t_upgrade_pvt.upgrade_to_pim4telco(null);
    $ END
  2. Licensing Product Hub for Communications (conditional)

    Applies to 11i release level: All

    TUMS step key: EGO_ENABLE_LIB

    If you license Product Hub for Communications, release 12.1.2 or later, Oracle Product Hub provides seeded libraries containing attribute groups, attributes, and value sets that are used primarily within the Telecommunications industry. These libraries are not automatically installed. The system administrator must run FND load commands to upload each library after installing the Oracle Product Hub for Communications patch. You can find these commands in the Seeded Item Metadata Libraries appendix, Oracle Product Hub Implementation Guide.

  3. PIM publication web services require manual post installation steps (conditional)

    Applies to 11i release level: All

    TUMS step key: EGO_WS_POST_INSTALL

    If you are using the Publication feature in Oracle Product Hub for Communications, then perform the steps outlined in (Doc ID: 1336146.1).

  4. Update Existing Item Attributes (conditional)

    Applies to: N/A

    For the item attributes SHIPPABLE_ITEM_FLAG, INTERNAL_ORDER_ENABLED_FLAG, INTERNAL_ORDER_FLAG in MTL_SYSTEM_ITEMS_B table, the valid combination of values is either Y,Y,Y or N,N,N. Any other combination is considered as data discrepancy. Customers can chose a valid combination for these item attributes depending on their business requirements and execute an appropriate concurrent program to correct such discrepancy. Refer to Data Fix: Items having invalid combination of SHIPPABLE_ITEM_FLAG, INTERNAL_ORDER_ENABLED_FLAG, INTERNAL_ORDER_FLAG attributes (Doc ID: 1676349.1) for instructions to identify and correct any items that have such data discrepancy.

  5. Setting Profile Option (required)

    Applies to 11i release level: All

    TUMS step key: EGO_ENABLE_PROFILE

    If you are using Product Lifecycle Management (EGO product) in Release 11i, then you must manually set the profile option EGO: Enable Product Lifecycle Management to 'Yes' after the upgrade.

  6. Gather Table Statistics (recommended)

    Applies to 11i release level: All

    TUMS step key: EGO_GATHER_STATS

    Considerable changes have been made to the data model that stores Item user-defined attributes in Release 12.1 and above. Therefore, Oracle recommends gathering table statistics for the following EGO tables:

    • EGO_MTL_SY_ITEMS_EXT_B

    • EGO_MTL_SY_ITEMS_EXT_TL

  7. Use the Product Workbench (required)

    Applies to: Release 12.2

    If you plan to use the Product Workbench, you must enable it by adding it to the whitelist of JavaServer Pages (JSPs).

    Additional Information: Refer to Allowed JSPs, Oracle E-Business Suite Security Guide.

Oracle Service Contracts

These tasks apply only to Oracle Service Contracts.

  1. Monitor Deferred Upgrade Tasks (conditional)

    Applies to 11i release level: All

    TUMS step key: OKS_VALIDATE_CONCURRENT_PROGS

    Certain tasks were initiated by a series of concurrent programs that were launched during the upgrade. To reduce downtime, the completion of those tasks was deferred until the system came back online. They are executed when the concurrent manager starts after the upgrade.

    The programs are as follows. You should monitor the completion of the tasks and re-submit any of the programs that may error out.

    • Launch Process Workflow for existing Service Contracts

    • Service Contracts Update Base Annualized Factor Manager

    • Service Contracts Update History Annualized Factor Manager

    • Service Contracts eBTax Migration

    • Service Contracts ASO Queue Migration

    • Service Contracts Update Base Tax Columns Manager

    • Service Contracts Update History Tax Columns Manager

    • Create Contract Header Text Index

Oracle Shipping Execution

Oracle Shipping Execution (available as part of Oracle Order Management) is integrated with Oracle Transportation Management. If you have licensed both Oracle Transportation Management and Oracle Order Management and will use Oracle Transportation Management with Oracle Shipping Execution, then perform the post-update steps outlined in Oracle Transportation Management Integration with Oracle E-Business Suite Post-Update Steps, Release 12.2.0 (Doc ID: 1362803.1).

Note: The prebuilt BPEL business processes in Oracle E-Business Suite Release 12.2 are certified with Oracle SOA Suite 12c, Oracle SOA Suite 11g. The BPEL 10g based prebuilt integrations are not supported in Oracle E-Business Suite Release 12.2. Customers upgrading to Oracle E-Business Suite Release 12.2 from 11i must migrate to Oracle SOA Suite 11g or Oracle SOA Suite 12c. Refer to Integrating Oracle E-Business Suite Release 12.2 with Oracle BPEL in Oracle SOA Suite 11g R1 (Doc ID: 1584883.1) and Integrating Oracle E-Business Suite 12.2 with BPEL in SOA Suite 12c (Doc ID: 1951625.1). Follow the respective documentation to deploy these BPEL processes.

Oracle Order Management

If you are using Available To Promise (ATP) functionality in the Order Management application and running ATP Data Collections, then you must refer to the Oracle Value Chain Planning Installation Notes, Release 12.2 - FAQ And Latest Patch Information document (Doc ID: 1361221.1) for Value Chain Planning (VCP) applications. Check for the latest cumulative patch to apply with VCP applications.

This is required because the ATP and ATP Data Collections functionality is controlled by Value Chain Planning applications code.

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, then perform the steps outlined in Oracle Value Chain Planning Installation Notes Release 12.2 (Doc ID: 1361221.1) to enable these applications. If you are deploying Value Chain Planning Applications on a RAC RDBMS, then you must also refer to RAC Configuration Setups For Running MRP Planning, APS Planning, and Data Collection Processes (Doc ID: 279156.1) and RAC for GOP - Setups for Global Order Promising (GOP) When Using a Real Application Clusters (RAC) Environment (Doc ID: 266125.1) to understand restrictions and requirements for running application processes in a RAC environment.

Oracle Warehouse Management

Oracle Warehouse Management is integrated with Oracle Transportation Management. If you have licensed both Oracle Transportation Management and Oracle Warehouse Management, and you plan to use Oracle Transportation Management with Oracle Warehouse Management, then perform the post-update steps outlined in Oracle Transportation Management Integration with Oracle E-Business Suite Post-Update Steps, Release 12.2.0 (Doc ID: 1362803.1).

Note: The prebuilt BPEL business processes in Oracle E-Business Suite Release 12.2 are certified with Oracle SOA Suite 12c, Oracle SOA Suite 11g. The BPEL 10g based prebuilt integrations are not supported in Oracle E-Business Suite Release 12.2. Customers upgrading to Oracle E-Business Suite Release 12.2 from 11i must migrate to Oracle SOA Suite 11g or Oracle SOA Suite 12c. Refer to Integrating Oracle E-Business Suite Release 12.2 with Oracle BPEL in Oracle SOA Suite 11g R1 (Doc ID: 1584883.1) and Integrating Oracle E-Business Suite 12.2 with BPEL in SOA Suite 12c (Doc ID: 1951625.1). Follow the respective documentation to deploy these BPEL processes.

System Administration

This section applies to all users, regardless of which products are registered as active.

Configure SSL for Web Services

  1. Configure SSL for Web Services (conditional)

    Applies to 11i release level: All

    TUMS step key: N/A

    If you have implemented Secure Sockets Layer (SSL) and plan to use Web Services, then you must generate certificates using the Oracle Wallet Manager from your Oracle E-Business Suite Server home ($IAS_ORACLE_HOME). Set up a password to protect your certificates.

    Additional Information: See Enabling SSL in Release 12.2 for more information.

    Use the Oracle Wallet Manager to generate the Wallet file. Then, follow these steps to complete the configuration:

    1. Set the s_websrv_wallet_file parameter in the Applications context file to the location of the Web Services Wallet file. Note that the value is a file location, not a URL.

      UNIX:

      $ /etc/ORACLE/Wallets/system1/exported_wallet

      Windows:

      D:\> oracle\system1\exported_wallet
    2. Place the exported file in this location.

    3. Provide the password for the exported Wallet file by running the following script:

      $ FND_TOP/patch/115/sql/txkSetWalletPass.sql

Secure Configuration

  1. Perform the following if you have upgraded to Release Update 12.2.6 or higher:

    Tip: After you apply Patch 24744399:R12.FND.C (a mandatory post requisite for R12.ATG_PF.C.Delta.6) or upgrade to Oracle E-Business Suite Release 12.2.7 Release Update Pack (which includes patch 24744399:R12.FND.C), your system will be 'locked down' until a local system administrator resolves or acknowledges the recommended security configurations in the Secure Configuration Console.

    • Login to the Oracle E-Business Suite

      Upon initial login as a local system administrator that has the Functional Administrator responsibility, you are automatically directed to the Secure Configuration Console.

    • Resolve or acknowledge security configurations

      You must now either resolve or acknowledge the recommended security configurations in the Secure Configuration Console.

    Suggested Reading: Oracle E-Business Suite Release 12.2 Security Guide, Part 2: Secure Configurations in the Secure Configuration Console chapter.

  2. Review and Deploy Security Guidelines (Recommended for all Oracle E-Business Suite releases)

    • Follow the Secure Configuration Guidelines

      Tip: You must follow all recommended secure configuration guidelines as documented in the Security Guide. At a minimum, Oracle recommends that you configure the following:

      1. Allowed JSPs feature

      2. TLS for inbound, outbound, and loopback connections

      Action: Review and deploy the recommended security guidelines documented in Oracle E-Business Suite Release 12.2 Security Guide, Part 2: Secure Configurations.

      Action: Follow the instructions in Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID: 1367293.1) to encrypt inbound, outbound, and loopback connections.

      Tip: If you have any computers requiring direct access to the database that are not registered nodes in AutoConfig (such as OAM clients), then you must explicitly grant access.

    • Execute the Security Check Scripts

      Action: Regularly run the Security Check Scripts on your production instance to ensure that it is, and continues to be in compliance with the recommendations in this document. For information on how to run the Security Check Scripts, run the scripts according to Security Configuration and Auditing Scripts for Oracle E-Business Suite (Doc ID: 2069190.1).

      Tip: If you upgraded to Oracle E-Business Suite Release 12.2.6 or higher, then you can use the Secure Configuration Console on an ongoing basis to perform necessary checks on your environment.

Backing Up Oracle E-Business Suite

Oracle strongly recommends that you perform a full system backup of your Oracle E-Business Suite Release 12.2 including the Run and Patch file systems (fs1 and fs2), the Non-Edition file system (fs_ne), all technology stack component Oracle homes, and the database.

System Maintenance Tasks

After you have verified that the system and the product upgrades are complete, perform the "clean-up" tasks described in this section.

System Maintenance

  1. Delete obsolete product files (recommended)

    Delete the product files for the previous release (if you have not done so already). You may want to retain report output files or customized programs. Output files are stored in the old log and output subdirectories under each product's top directory, under the log and output directories you created, or under a common directory.

    To remove obsolete files for an old release, change to the top directory of that release and enter the following command:

    UNIX:

    $ rm -rf <old APPL_TOP>

    Here is an example:

    $ rm -rf /d01/appl/r10

    Windows:

    C:\> rd /s /q <old APPL_TOP>

    Here is an example:

    C:\> rd /s /q \APPL110
  2. Register new products (conditional)

    New products added since Release 12 are not automatically registered in the database. If you intend to use new products, then register them using License Manager. See Oracle E-Business Suite Maintenance Guide for instructions.

    Additional Information: See the Oracle E-Business Suite Maintenance Guide for instructions to license new products.

    By default, the Java Color Scheme profile option should be set to 'Standard' for all sessions and optimal system response time. The upgrade process sets this default value for all instances. However, setting this profile option to a different value may work better for some systems.

    Additional Information: See the Oracle E-Business Suite Setup Guide and the Oracle E-Business Suite User's Guide for more information.

  3. Update Java Color Scheme profile option for selected users (conditional)

    By default, the Java Color Scheme profile option should be set to "standard" for all sessions for optimal system response time. The upgrade process sets this default value for all instances. However, setting this profile option to a different value may work better for some systems. See Oracle E-Business Suite Setup Guide and Oracle E-Business Suite User's Guide for more information.

  4. Complete Workflow Notification Mailer configuration (required)

    Applies to 11i release level: All

    TUMS step key: MP_WORKFLOW_TASKS

    Before you send Oracle Workflow e-mail notifications, you must complete the Workflow Notification Mailer configuration, using the Notification Mailer Configuration wizard in Oracle Applications Manager.

    1. Log on to Oracle Applications Manager.

    2. From the Applications Dashboard, select the Workflow Manager from the "Navigate to" pull-down menu. Click Go.

    3. In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page. The Notification Mailers status icon should show a status of Down.

    4. On the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the notification mailer configuration wizard.

    5. In the Outbound Email Account (SMTP) region, enter the name of the outbound SMTP mail server.

    6. If you want to enable inbound e-mail processing, select the Inbound Processing parameter in the Inbound Email Account (IMAP) region, and enter the name of the inbound IMAP mail server, user name and password of the mail account that the notification mailer uses to receive e-mail messages, and the reply-to address of the e-mail account that receives incoming messages, to which notification responses should be sent.

    7. Click Apply.

    8. Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component status is Running.

      Additional Information: See Oracle Workflow Administrator's Guide for more information.

    If you have previously implemented the C-based Notification Mailer concurrent program or the Generic Service Management Notification Mailer, the tag definitions and configuration parameter settings for those parameters that are still applicable are automatically transferred to the Java-based Workflow Notification Mailer configuration parameters.

  5. Complete Transport Agent setup (conditional)

    If you are using a proxy server to handle your outbound Oracle Transport Agent requests, then set following OXTA parameters in the container configuration:

    • OXTAOutUseProxy=True

    • OXTAOutProxyHost=<Your proxy server name>

    • OXTAOutProxyPort=<Your proxy server port>

    To set the parameters, go to the Oracle Applications Manager Site Map and choose AutoConfig > Applications Node > Edit Parameters. Then, use the Search field to find OXTA. After you set the parameters, run AutoConfig to regenerate the wls.properties file (FMW_Home/Oracle_EBS-app1/applications/oafm/APP-INF/wls.properties).

    Note: See Oracle XML Gateway User's Guide for more information.

  6. Complete Setup for Oracle XML Gateway (required)

    The Oracle XML Gateway engine uses style sheets from an operating system directory you define as a database directory for PL/SQL file I/O in your Oracle E-Business Suite instance. You must also specify the same directory in the ECX: XSLT File Path profile option. The profile option value must be an absolute path and cannot contain a symbolic link or other operating system-specific parameters.

    Additional Information: See My Oracle Support Knowledge Document 2525754.1, Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2 for more information.

    Also, ensure that the following profile options are set at site level for Oracle XML Gateway. If you have previously set these profile options, then no action is necessary, as the upgrade preserves these values.

    Profile Option Description
    ECX: XSLT File Path Path to the directory specified as the location for style sheets to be used for XSLT transformations. This value must be a database directory defined for PL/SQL file I/O. Ensure that there is no slash at the end of the directory name.
    ECX: System Administrator Email Address Address to which Oracle XML Gateway error notifications should be sent.
    ECX: Server Time Zone Time zone the database server is running in.

    Note: See Oracle XML Gateway User's Guide for more information.

Oracle XML Publisher Tasks

These tasks apply to all users, regardless of which products are registered as active.

  1. Enable PDF printing (required)

    The PDF Publisher print style and PASTA_PDF printer driver provide the capability to print PDF files using a third-party utility. You can use this style and driver to print a generated PDF. The Pasta Universal Printer type has been associated with the style and driver for ease of use.

    Action: Refer to the Oracle XML Publisher Administration and Developer's Guide, Release 12, for configuration steps. For access to the Oracle XML Publisher Administration and Developer's Guide and the latest updates, refer to Notes for Using Oracle Business Intelligence Publisher 10g in Oracle E-Business Suite Release 12.2 (Doc ID: 1640073.1).

  2. Specify a temporary directory for XML Publisher (required)

    Use the Oracle XML Publisher's Administration interface to assign a temporary directory for the site level. The temporary directory improves performance and allows unlimited XML file size.

    Additional Information: See Oracle XML Publisher Administration and Developer's Guide for more information about this directory.

Post-Upgrade Steps of Oracle E-Business Suite Release Update Pack for Release 12.2

You must complete the Post-Upgrade steps described in the Oracle E-Business Suite Release Update Pack Readme specific to the Oracle E-Business Suite Release Update Pack (RUP) that you have upgraded to that is described in the Apply the Latest E-Business Suite Update Pack for Release 12.2 section of this chapter.

Required Action: For example, if you upgrade to Oracle E-Business Suite Release 12.2.7, then you must complete all Post-Uprade steps described in Oracle E-Business Suite Release 12.2.7 Readme (Doc ID: 2230783.1).

Mandatory Steps Applicable for All Upgrade Customers

Required Action: Refer to Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID: 1320300.1) and perform all applicable post upgrade steps in Section 1: Notes for All Customers, and Section 3: Notes for Upgrade Customers such as 'Create Snapshot'.

Additional Tasks

This section points to additional tasks that may be necessary, and suggests documentation that describes those tasks.

Reapplying Application Tier Customizations

If your system includes customized forms, reports, programs, libraries, or other application files, then reapply all changes that you need for this release.

Required Action: Re-deploy your customizations following the instructions in Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID: 1577661.1), Section 1.5, Deploying Custom Application Tier Objects.

Migrating Portlets Preferences Store

If you are using Oracle E-Business Suite portlets, then copy the Portlets Preference Store directory from your Oracle E-Business Suite Release 12 10_1_3_Oracle_Home/portal/portletdata directory to following non editioned directory on your new new Oracle E-Business Suite Release 12.2 file system:

$ <s_ne_base>/inst/<s_contextname>/oracle_common/portal/portletdata

Note: Autoconfig context variable s_portlet_preference_store_directory by default points to the same directory.

Additional Information: Refer to section 15.4.2.4.2 Migrating Customizations from the Default Production Location in the Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter Portal, and ADF 11g Release 1 (11.1.1.7.0).

Note: This applies to all customers using Oracle E-Business Suite portlets with EBS 12.1.3, regardless of whether they integrate with Oracle Portal or Oracle WebCenter consumer.

For Portal 10g

Oracle E-Business Suite customers upgrading from Release 12.0 or 12.1 to Release 12.2 and already having Oracle Portal 10g configured:

  1. Conditional Action: Upgrade Oracle Portal 10g to Oracle Portal 11g as described in section 10 of the Integrating Oracle Portal 11.1.1 with Oracle E-Business Suite Release 12 document on My Oracle Support (Document ID: 1074334.1).

  2. Migrate Portlets Preferences Store.

For Portal 11g

Oracle E-Business Suite customers upgrading from Release 12.0 or 12.1 to Release 12.2 and already having Oracle Portal 11g configured:

  1. Migrate Portlets Preferences Store.

Regenerating Business Views (conditional)

If you are using Business Views, then regenerate your business views by running the Generate Business Views by Application concurrent program using the Business View Setup responsibility:

If you don't have the Business Views Setup responsibility assigned to the SYSADMIN user, then complete the following:

Understanding Oracle E-Business Suite System Administration Tasks

Suggested Reading: Ensure you are completely familiar with information in the Oracle E-Business Suite Setup Guide and the Oracle E-Business Suite Security Guide. In addition, you should understand the information in the Oracle E-Business Suite Maintenance Guide, Release 12.2. This document contains important details about AD utilities as well as instructions on how to patch your system and perform manual maintenance tasks.

Implementing New Product and Country-specific Functionality

Suggested Reading: Refer to the implementation or setup guides (or implementation or setup section of the user's guides) associated with the Oracle E-Business Suite products in your system for instructions on implementing or setting up new products and features.

Resizing the Database

The size of the production database depends on the products that you have licensed and the additional features (such as multiple languages or multiple organizations) that you have configured in your system. Refer to the product-specific documentation.

Optional Advanced Configurations

You may have identified the need to scale your environment due to sizing requirements or for high availability. You may now scale the environment.

Scale the Environment

Upgrading to Oracle E-Business Suite Release 12.2 is performed with a single application tier node and a single database node even if you are using RAC. Scaling the environment is a post-upgrade task. Now that the upgrade is complete, you may scale your environment according to production level requirements by adding application tier nodes and database RAC nodes.

Adding Application Tier Nodes

Conditional Action: If you need to add additional application tier nodes, then configure load balancing as described in Using Load-Balancers with Oracle E-Business Suite Release 12.2 (Doc ID: 1375686.1).

When deploying multiple application tier nodes for an Oracle E-Business Suite environment, you can use a Shared Application Tier Filesystem or replicate the filesystem on every node in the environment.

Tip: Oracle highly recommends that you use a Shared Application Tier Filesystem.

When directed in Using Load-Balancers with Oracle E-Business Suite Release 12.2 (Doc ID: 1375686.1), follow the steps in one of the following notes to create a new application tier node:

Adding Database Tier Nodes to RAC

Conditional Action: If you are adding additional database tier nodes to Oracle Real Application Clusters (RAC) to meet scalability or high availability requirements, then follow the steps in Oracle E-Business Suite Release 12.2: Adding or Deleting 11gR2 Oracle RAC Nodes (Doc ID: 1570554.1).

Performing DMZ Configuration

Conditional Action: If you need to configure Oracle E-Business Suite Release 12.2 for access from the Internet, then review and follow the steps documented in Oracle E-Business Suite Release 12.2 Configuration in a DMZ (Doc ID: 1375670.1).

Validating Custom and Third-Party Products

Oracle E-Business Suite Release 12.2 includes significant database and file system architecture changes designed to support Online Patching. Therefore, integrations with Oracle E-Business Suite may need to be modified to comply with new deployment and development standards in order to work correctly with Oracle E-Business Suite Release 12.2. Examples include custom and third-party integrations, as well as integrations with other Oracle products such as Oracle Application Express.

Additional Information: Refer to Guidance for Integrating Custom and Third-Party Products With Oracle E-Business Suite Release 12.2 (Doc ID: 1916149.1).

If you identified external integrations that require updates to meet certification requirements with Oracle E-Business Suite Release 12.2 or require additional steps to deploy, then perform those actions now. Validate all external integrations once the necessary steps have been performed.

Additional Information: For more information, refer to Preparing External Integrations.

Backing Up Oracle E-Business Suite

Oracle strongly recommends that you perform a full system backup of your Oracle E-Business Suite Release 12.2 including the Run and Patch file systems (fs1 and fs2), the Non-Edition file system (fsne), all technology stack component Oracle homes, and the database.

Logging On to Oracle E-Business Suite

To start Oracle E-Business Suite and access all Oracle E-Business Suite products, go to the Oracle E-Business Suite Login page, located at the following URL:

http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin

For example:

http://oraapps1.example.com:8000/OA_HTML/AppsLogin

The system administrator should log on the first time using the sysadmin logon account that is pre-configured in the Applications installation. Use the System Administrator responsibility to launch an Oracle E-Business Suite session where you can complete the required implementation steps.

Note: See the Oracle E-Business Suite Setup Guide. See also the Oracle E-Business Suite User's Guide.

Functional Verification Tasks

The Functional Verification Tasks appendix in this guide contains optional tasks to verify that your transaction data was upgraded as expected.

Action: Refer to the Functional Verification Tasks appendix for details.