This chapter covers the following topics:
This section provides a general checklist of tasks that are required to finish the upgrade.
Complete the tasks in this section before you complete the product-specific tasks.
These tasks must be carried out regardless of the products that are active in your system.
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. You can run these programs in the background, while your system is up and running and users are active, unless otherwise instructed in the product-specific sections of this book.
Before you continue, be sure all the concurrent programs generated by the upgrade have run successfully. In the Required Post Upgrade Jobs section of Applications Release 12 Upgrade Sizing and Best Practices (Doc ID: 399362.1), you will find a list of the distinct concurrent programs included in the upgrade process. The Best Practices section includes a recommendation on how to isolate these programs (and all their executions) into a separate concurrent manager queue, which you can use for processing.
Applies to 11i release level: All
TUMS step key: N/A
To install the American English online help, run the database portion of the online help patch (u6746000.drv). It is located in $AU_TOP/patch/115/driver directory. Set the AutoPatch options=hotpatch,nocopyportion,nogenerateportion.
If you have languages other than American English registered in your system, then check if the NLS version of the Online Help is available. If it is available, then download and apply the NLS version of the online help patch for each active language. Follow the instructions in the Post-installation Tasks section of the Oracle E-Business Suite NLS Release Notes for your release level.
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.
Applies to 11i release level: All
TUMS step key: N/A
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.
If you have custom development on mod_plsql, migrate your web pages to Oracle Application Framework.
Note: See Oracle Application Framework Developer’s Guide in Oracle Application Framework Documentation Resources, Release 12 (Doc ID: 391554.1) for more information.
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, available from the Oracle Application Framework Documentation Resources, Release 12 (Doc ID: 391554.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. |
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, available from the Oracle Application Framework Documentation Resources, Release 12 (Doc ID: 391554.1). |
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, which is available from Oracle Application Framework Documentation Resources, Release 12 (Doc ID: 391554.1)
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 Oracle E-Business Suite Developer’s Guide.
Copy custom shell scripts or reports to the custom application directories and re-customize the copy as necessary.
Note: See Product Customization Standards in Oracle E-Business Suite Developer’s Guide.
If you have customized the concurrent manager startup script (startmgr), then copy the script from the old environment to the new environment. Then, verify that the customizations are valid for the new environment.
Note: The default location in UNIX for the startmgr script is $FND_TOP/bin. For more information, see Oracle E-Business Suite System Administrator’s Guide - Configuration.
Applies to 11i release level: All
TUMS step key: N/A
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 Oracle E-Business Suite System Administrator’s Guide - Security for more information.
These tasks apply to Oracle Alerts.
Manually update custom alerts that you want to assign to a particular organization:
As the Alerts Manager, navigate to the Alerts form (Alert > Define) and query the definition.
Choose Alert Details, then display the Installations tabbed region in the Alert Details window.
Enter the ORACLE ID and organization name that you want to run this alert against.
Make sure you check Enabled before saving the changes.
These tasks apply to Multiple Organizations for Oracle E-Business Suite.
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.
Report Manager Release FRM.G changed the database location of reports and security rules. To migrate your data to the new location, perform the tasks in this section.
Note: These tasks apply only if you are using Client Server ADI’s Request Center functionality to publish to the database, and you wish to manage the published reports and security rules using the new Report Manager tools. If you are not using Report Manager, or if you are using Report Manager Patchset G or later, then you can omit this section.
Applies to 11i release level: All
TUMS step key: N/A
Add the concurrent program Data Migration Program (Application: Report Manager) to a request group. See the Oracle E-Business Suite System Administrator’s Guide - Configuration if you need more information.
Applies to 11i release level: All
TUMS step key: N/A
The data migration program moves your existing user to value security rules and published reports to the new schema. It also updates existing form functions to point to the new report locations.
These steps apply to Web ADI and to products that use Web ADI to generate spreadsheets.
Applies to 11i release level: All
TUMS step key: N/A
Spreadsheets created in previous versions of Web ADI 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.
These steps apply only to Oracle Workflow.
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 Applications separately to access the Status Monitor after the upgrade.
Applies to 11i release level: 11.5.8
TUMS step key: N/A
If you upgrade from an Oracle E-Business Suite release earlier than Release 11.5.9, then run the Synchronize Product License and Workflow BES License (FNDWFLIC) concurrent program after the upgrade. It updates the license status of the existing events and subscriptions in your Event Manager so that Oracle Workflow can automatically update the license status for relevant events and subscriptions if you subsequently license another product.
Complete the steps described in My Oracle Support (Doc ID: 556540.1) for enabling Oracle E-Business Suite Integrated SOA Gateway Release 12.1.1 from Oracle E-Business Suite Release 11i.
Complete the tasks in this section before you allow users to use Oracle Customer Relationship Management (CRM) products.
These tasks apply only to Oracle Email Center.
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 opt 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.
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.
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, you can reduce downtime by running the concurrent process request set "Update as_accessess_all denorm flag" as a pre-upgrade step.
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 Appendix G, "Upgrade by Request".
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 Appendix G, "Upgrade by Request".
Customers upgrading from ASN.B to Release 12 must run two concurrent requests and are not required to run all the ASN.B enabling steps a second time:
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.
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.
These tasks apply only to Oracle Mobile Field Service.
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).
Complete the tasks in this section before you allow users to log on to Oracle Financials and Procurement products.
These tasks apply only to Oracle Financials for India.
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 (7479204).
Refer to the following table to determine whether to apply this patch to your system:
| Action | Release 11i uses JAI Projects? | Release 12.1.1 uses JAI Projects? | Apply Patch? |
|---|---|---|---|
| Upgrading from Release 11i to Release 12.1.1 | No | Yes | Yes |
| Upgrading from Release 11i to Release 12.1.1 | Yes | Yes | Yes |
| Upgrading from Release 11i to Release 12.1.1 | No | No | No |
Note: See Oracle Financials for India Implementation Guide for more information.
These tasks apply only to Oracle Internet Expenses.
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.
These tasks apply only to Oracle Payments (renamed from iPayments in Release 11i).
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 new transactions will fail.
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.
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.
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.
Complete the tasks in this section before you allow users to log on to Human Resources Management products.
Important: Customers using Oracle iRecruitment and running database 11gR1 version 11.1.0.7 must add the following line to their database initialization file:
event="31151 trace name context forever, level 0x100"
Setting this event provides a fix for the issue reported in bug 6952870.
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: 145837.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.
Applies to 11i release level: All
TUMS step key: PSP_TASKS
If you currently use Oracle Labor Distribution and have not previously applied HRMS Family Pack H (or later), there may be Labor Distribution tables that contain invalid data. Run the concurrent program PSP: Post Upgrade Bad Data Report from the Labor Distribution Superuser responsibility to determine whether any Labor Distribution tables have invalid data.
The report lists the Labor Distribution tables where the Human Resources Management business group and GL set of books could not be updated. You cannot access these records through the application itself. To help identify the records, the report process marks each one that could not be updated with a value of -999.
Perform the actions indicated, and re-run the report until no further action messages are reported.
Note: See Labor Distribution (PSP) Post Upgrade Bad Data Report (Doc ID: 270447.1) for more information.
Applies to 11i release level: All
TUMS step key: PER_HRU_SAL_PROPOSALS
If you previously created customized salary components (as described in Oracle Human Resources Management Systems Implementation Guide Release 11i), you may need to re-run the associated SQL script to re-seed custom salary components. You can determine if this action is necessary by referring to the Release 12 version of the implementation guide to ensure that your customizations in the salary component area are re-implemented as expected.
Applies to 11i release level: All
TUMS step key: OTA_DATA_MIG_REP
The upgrade automatically updates Oracle Training Administration to enable new functionality and changes the product name to Learning Management. During the upgrade, a concurrent request was submitted to determine what further action is required. See Guide to the OTA Classic Upgrade Report (Doc ID: 269571.1) for a description.
If you currently use the integration between OTA and Oracle iLearning, follow the instructions in OTA-iLearning Integration Migration to Oracle Learning Management (OLM) (Doc ID: 271719.1).
Applies to 11i release level: All
TUMS step key: PER_RIW_WINRUNNER
If you currently use HRMS Configuration Workbench with Winrunner, then you need to apply an additional patch (5441645), which contains updated Winrunner files for this release. The patch readme describes how to apply the patch and any post-patch verification checks that may be necessary.
Applies to 11i release level: All
TUMS step key: OTA_TIMEZONE_CONV
OTA.J.Rollup.1 and Release 12 include the Time Zone conversion for Oracle Learning Management upgrade. It requires you to examine the Update Time Zone concurrent manager log file that is automatically generated during the upgrade process. For additional information, or if you encounter any errors, follow the instructions in Guide to the Time Zone Update (Doc ID: 371179.1).
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.
Examples of some updates that run during the upgrade (and are present in the downtime reduction report) include:
Unmerge contacts from TCA (Doc ID: 279449.1)
PSP: Migrate to OAFramework Effort Reporting (Doc ID: 302304.1)
Applies to 11i release level: Earlier than Family Pack K
TUMS step key:
Family Pack K supplies definitions of standard person-name formats to define the structure of person names. You can use this feature to:
Define the format of the Full Name that appears in the HRMS forms-based interface (for example, in the Find Person window)
Change other supplied formats (Display Name and List Name) for use in custom code
Define your own name formats for use in custom code
If you upgrade from an Oracle E-Business Suite release earlier than Oracle HRMS Family Pack K, then you must run the Update Person Names concurrent program to update stored person names in the specified legislation or in all business groups. If you do not, then HRMS does not populate or update stored person names. Therefore, names may be null or appear in an unexpected format.
Note: See Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide for details.
These tasks apply only to Oracle Approvals Management.
Applies to 11i release level: All
TUMS step key: AME_NEW_RESP
After the upgrade, you must migrate new responsibilities to existing Approvals Management Engine (AME) users. From the System Administrator responsibility, attach the Approvals Management Post-Upgrade Process concurrent program to the System Administrator Reports request group. Then, run the concurrent program to attach the new responsibilities.
Note: If you have previously applied 11i.AME.B, then omit this step.
These tasks apply only to Oracle Payroll.
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 2.7 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).
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.
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: 145837.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.
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.
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:
Set up Journal Line Definitions
Set up the Application Accounting Definition
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.
Complete the tasks in this section before users log on to Oracle Intelligence products.
Applies to 11i release level: All
TUMS step key: N/A
This release includes Embedded Data Warehouse (EDW) Release 4.3, which requires post-installation steps to complete the implementation. See the Oracle Embedded Data Warehouse Install Guide (A90299-05) for instructions.
Applies to 11i release level: All
TUMS step key: N/A
This release supports the use of Discoverer 10g (10.1.2.0.2) End User Layer (EUL). If you are using any of the following products, then you must implement Discoverer EUL.
| Short Name | Product |
|---|---|
| ams | Marketing |
| amw | Internal Controls Manager |
| ap | Payables |
| ben | Advanced Benefits |
| bis | Business Intelligence System |
| bix | Interaction Center Intelligence |
| ce | Cash Management |
| cn | Sales Compensation |
| eni | Product Development Intelligence |
| fem | Enterprise Performance Foundation |
| fii | Financials Intelligence |
| ftp | Transfer pricing |
| hri | Human Resources Intelligence |
| ibe | iStore |
| isc | Supply Chain Intelligence |
| msc | Advanced Supply Chain Planning |
| oki | Contracts Intelligence |
| opi | Operations Intelligence |
| ota | Learning Management |
| ozf | Trade Management |
| pa | Projects |
| pay | Payroll |
| per | Human Resources |
| pft | Performance Analyzer |
| pfi | Projects Intelligence |
| pjm | Project Manufacturing |
| pmi | Process Manufacturing Intelligence |
| poa | Purchasing Intelligence |
| psb | Public Sector Budgeting |
If you are a new Discoverer EUL customer, then proceed to the implementation steps. If you are an existing Discoverer 4.1 customers, then you must upgrade to Discoverer 10g. See Using Discoverer 10g with Oracle Applications R12 (Doc ID: 373634.1) for instructions.
Applies to 11i release level: All
TUMS step key: N/A
This release includes Daily Business Intelligence Release 8.0. See the Oracle Daily Business Intelligence Implementation Guide for information.
Applies to 11i release level: All
TUMS step key: N/A
This release includes Balanced Scorecard Release 5.0. See the Oracle Balanced Scorecard Install Guide for information.
These tasks apply only to Oracle Daily Business Intelligence for Marketing.
Applies to 11i release level: All
TUMS step key: N/A
To verify your upgraded data, make sure you can complete a request set for Initial Load and Incremental without any errors. In addition, all Dashboard reports and links should be accessible.
These tasks apply only to Oracle Daily Business Intelligence for Sales.
Applies to 11i release level: All
TUMS step key: N/A
Set the BIL: Oracle Sales Implementation Date (mm/dd/yyyy) profile option to the date on which Oracle Sales is installed.
Then, from the Daily Business Intelligence Administrator responsibility, click Run Request Sets from the Data Summarization portion of the screen. From the pop-up window, select Request Set. Search for the Sales initial request set and click Submit.
The request set must run without any errors.
Applies to 11i release level: All
TUMS step key: N/A
To verify your upgraded data, make sure you can complete an Initial Load request set without any errors. In addition, all Dashboard reports and links should be accessible.
Complete the tasks in this section before users log on to Oracle Projects products.
These tasks apply only to Oracle Property Manager.
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
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:
Get the SSL certificate.
Import the SSL certificate to the EBS instance.
Set the Username token authentication credentials for the service.
Add the service invocation subscription to invoke the service.
Add subscription to the events.
Apply the following patches to begin the post-install steps:
Prerequisite patches:
16872352:R12.OWF.B
17200092:R12.OWF.B
Download and apply patch 22328995:R12.PJT.B from My Oracle Support.
Complete the following steps to export the SSL certificate from your browser. The following steps describe the process using Mozilla Firefox:
Click the site identity button located in the address bar of your browser.
Click the More Information… button.
Select Security.
Click View Certificate.
Review the certificate details on the General tab. Verify that the imported SSL certificate is valid.
Select the Details tab.
Click Export…
Export the certificate to your directory.
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.
Perform the following steps to transfer the exported certificate to the EBS instance:
Use Secure File Transfer Protocol (SFTP) to export the server name to the EBS instance. For example, sftp <servername>.example.com.
Enter your username and password when prompted.
Use the put command to enter the certificate into the instance. For example, put *.example.com.cer.
Login to the EBS instance using telnet command.
Select a directory to put the certificate file.
Import the certificate to the EBS keystore. Ensure that you are on the same directory where you put 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.
Enter the keystore password when the application requests for it.
Restart the EBS server after importing the certificate.
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.
Use the following information to set the user name token credentials:
sqlplus apps/apps@db @$FND_TOP/sql/afvltput.sql <Module> <Key> <Value> to store your key, module, and password.
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 they have to remember it for later use.
Enter unique Key and Module pairs to identify passwords.
Module: PA
Key: PA_MGMT_SERVICES_USA
Value: Welcome1
Use the following Service Invocation Subscription details to invoke the service:
Subscription type: Invoke web service
WSDL URL: SSL enabled service URL
Select the Service Port and Service Operation
Subscription parameters:
WFBES_SOAP_USERNAME: username for the web service
WFBES_SOAP_PASSWOD_MOD: Module name according to the above step (PA)
WFBES_SOAP_PASSWORD_KEY: Module key according to the above step (PA_MGMT_SERVICE_USA)
The service constructs the SOAP header and username token based on the information provided.
Payload information passed by the program at run time is appended to the header prepared above as the soap body.
Perform the following steps after you have added the Fusion SSL certificate to the EBS instance:
Sign in to the Oracle E-Business Suite application using login credentials that provide access to the Workflow Administrator Web Applications responsibility.
Navigate to Workflow Administrator Web Applications > Administrator Workflow > Business Events.
Search for the predefined business event oracle.apps.pa.coexist.project.invoke.
Click GO.
Find your search result under the Results: Events section. Click Subscriptions.
Click Create Subscription.
In the Create Event Subscription page, enter the following subscription details:
System: <EBS Instance>
Source Type: Local
Event Filter: This field is auto populated
Execution Phase: Select a value between 1-99
Status: Enabled
Rule Data: Message
Action Type: Invoke Web Service
On Error: Stop and Rollback
Click Next.
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.
Click Next to select the service. The Service Name field is populated with ProjectService in the Select Service section.
Click Next and select the service port.
Click Next and select the operation. In this example, it is findProjectPlanByProjectName.
Select an operation. For example, select findProjectPlanByProjectName.
Note: All services used for integration with Oracle E-Business Suite are synchronous services.
Click Next to complete the subscription registry and link it with the predefined business event.
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.
Complete the tasks in this section before users log on to Supply Chain Management products.
These tasks apply only to Oracle Mobile Applications.
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.
These tasks apply only to Oracle Process Manufacturing.
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.
Perform the following steps in the order listed. Complete all the steps before you proceed to the next task.
Review and correct migration error messages (all releases)
Use the View Migration Log user interface that is available in OPM System Administration to view the messages. You must correct all errors before you proceed to the next step.
Run transformation migrations for OPM data (all releases)
Apply patch 6677049 to your Release 12.1 APPL_TOP. It runs the following migrations:
Transformation of organization_id, inventory_item_id, lot_number, and uom columns in these OPM application tables: Quality Management, Product Development, Process Execution, and Process Planning. It also transfers the same columns in the Order Management and Shipping tables.
Migration of forecast data
Transformation of purchase order and receiving tables
Run transformation migrations for OPM Financial data (all releases)
Apply patch 4690072 to your Release 12.1.1 APPL_TOP. It runs the following migrations:
Transformation of organization_id, inventory_item_id, uom, lot_number, and uom columns in the OPM Financials tables.
Migration of OPM financials data
Migrate OPM Regulatory data (all releases)
Apply patch 4688012 to your Release 12.1.1 APPL_TOP (if you use OPM Regulatory Management).
Recreate open batches (all releases)
Run the Process Execution Migration Recreate Open Batches concurrent program (if you took a snapshot before the upgrade).
Migrate OPM Edit Text to attachments (all releases)
Run the GMA: Edit Text Migration concurrent program to migrate the OPM Edit Text to attachments for the organizations, items, lots, grades, and reason codes.
Note: See the Oracle Process Manufacturing Migration Reference Guide for details on data migration. See also OPM System Administration User’s Guide.
These tasks apply only to Oracle Service Contracts.
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
Concurrent program to create contract header text index
Compile the Common Calculation Engine Message file. You must complete this step to see the appropriate messages in the concurrent manager log when you run a mapping calculation.
To compile the Common Calculation Engine Message file
Sign onto the E-Business Suite using the Application Developer responsibility.
Select Run under the Other: Requests link in the right-hand region of the responsibility menu.
Select the single request option, and then the List of Values (LOV) to select the concurrent job; Generate Messages.
Complete the following parameters:
Language: US
Application: Enterprise Performance Foundation
Mode: DB_TO_RUNTIME
File Application Shortname: <leave blank>
Filename: <leave blank>
Click Submit to finish the process.
Once the concurrent request completes, you should have a US.msb file located under the $FEM_TOP/MESG directory on the file system where the applications instance is installed.
Add the iSetup Responsibility for the Import/Export User(s).
Refer to How To Extract and Load Rules in Enterprise Performance Foundation R12 in My Oracle Support (Doc ID: 751290.1) to enable Import/Export using iSetup in Release12.
After you have verified that the system and the product upgrades are complete, perform the "clean-up" tasks described in this section.
Applies to 11i release level: All
TUMS step key: N/A
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:\> del /s /q <old APPL_TOP>
Here is an example:
C:\> del /s /q \APPL110
Applies to 11i release level: All
TUMS step key: N/A
During the upgrade process Oracle Applications marks columns in the data dictionary that are unused. You can safely drop these columns now.
Note: See the Oracle Database Administrator’s Guide 10g Release 2 (10.2) or Oracle Database Administrator’s Guide 11g Release 1 (11.1) for details.
Applies to 11i release level: All
TUMS step key: N/A
New products added since Release 11i was initially made available (May 2000) are not automatically registered in the database. If you intend to use new products, register them using License Manager. See Oracle E-Business Suite System Administrator’s Guide - Maintenance for instructions.
Applies to 11i release level: All
TUMS step key: N/A
By default, the Java Color Scheme profile option should be set to "swan" for all sessions for optimal system response time. The upgrade process sets the value 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 System Administrator’s Guide - Maintenance and Oracle E-Business Suite User’s Guide for more information.
This section points to additional tasks that may be necessary, and suggests documentation that describes those tasks.
Release update packs (RUPs) are released a regular intervals, generally quarterly or twice a year. Each RUP is cumulative - it delivers error corrections and system updates, not only for the most current release update pack, but also for all the RUPs that preceded it. You can apply the latest release update pack (RUP) to keep your system at the most current release level available.
Note: See Oracle Applications Documentation Resources, Release 12.1 (Doc ID: 790942.1). This "documentation road map contains links to the readmes that describe all release update packs made available since the initial release of Oracle Applications 12.0. See also Oracle Applications Release Notes (Doc ID: 5493891.1)
Make sure you are completely familiar with the information in the Oracle E-Business Suite System Administrator’s Documentation Set. In addition, you should understand the information in Oracle E-Business Suite Maintenance Utilities, Oracle E-Business Suite Maintenance Procedures, and Oracle E-Business Suite Patching Procedures. These volumes contain important details about AD utilities, as well as instructions on how to patch your system and perform manual maintenance tasks.
During the upgrade, your system was converted automatically to the new Oracle Applications Tablespace Model (OATM). This model is based on database object type rather than product affiliation, making it simpler to manage and requiring far fewer tablespaces and operating system files.
The upgrade process created tablespaces for all new products, configured the database for the new tablespace model, and created new objects. However, it did not automatically migrate your existing objects. We strongly recommend that you perform this migration now. For more information, see Oracle E-Business Suite System Administrator’s Guide - Configuration for migration information.
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. Refer to Oracle Applications Documentation Resources, Release 12.1 (Doc ID: 790942.1) for other product-specific issues.
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.
Have the operating system administrator back up the Oracle E-Business Suite product files, including COMMON_TOP and the technology components. Have the database administrator back up the Oracle E-Business Suite database and Oracle Home components.
Review the recommended security processes documented in Best Practices for Securing Oracle Applications Release 12 (Doc ID: 403537.1). In particular, if you have any computers requiring direct access to the database that are not registered nodes in AutoConfig (such as OAM clients), you must explicitly grant access.
Oracle strongly recommends that you apply the latest available Critical Patch Update after you upgrade to Release 12.1.1.
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.oracle.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 Applications Forms session where you can complete the required implementation steps.
Note: See Appendix F in the Oracle E-Business Suite System Administrator’s Guide - Security. See also the Oracle E-Business Suite User’s Guide.