This chapter covers the following topics:
This section provides a general checklist of tasks that are required for the upgrade and describes The Upgrade Manual Script (TUMS), which examines your current configuration and creates a report detailing which of the tasks in these instructions you must complete and which ones you can ignore.
It also contains a reminder that you must have applied the 11i.AD.I.6 Minipack before you can continue with the remaining upgrade preparation tasks.
Note: If you have not already reviewed the information in Business Impact and Functional Changes in Chapter 1, do so before you begin. It is especially important that both the DBA and the application specialists be familiar with the tasks in Appendix E, Appendix F, Appendix G, and Appendix I, as the information that can help reduce system downtime and verify data migration.
Applies to 11i release level: All
TUMS step key: N/A
If you have not previously done so, apply the 11i.AD.I.6 minipack on all application tier nodes. It must be present in your system in order to upgrade to Release 12.1.1.
Note: See About Oracle Applications DBA Minipack 11i.AD.I.6 (Doc ID: 233044.1).
Applies to 11i release level: All
TUMS step key: N/A
The TUMS report lists tasks that you can omit from the upgrade because they do not apply to your system (for example, a task required for a product that you do not use or for applying a patch that you have previously applied). TUMS is delivered in a patch, which supplies the scripts you need to examine your system and create the report. We strongly recommend you create and review the TUMS report before you begin the upgrade.
Download and apply TUMS patch.
Download patch 7705743 and apply it to the administration server node on your Release 11i APPL_TOP. It supplies you with the script (adtums.sql) you need to generate the TUMS report (tumsr12.html).
Generate the TUMS report.
To generate the report:
UNIX:
$ cd $AD_TOP/patch/115/sql
$ sqlplus <APPS username> / <APPS password> @adtums.sql <DIRECTORY>
Windows
C:\> cd %AD_TOP%\patch\115\sql
C:\> sqlplus <APPS username> / <APPS password> @adtums.sql <DIRECTORY>
For the <DIRECTORY> value, enter the full path of the directory that you want the report to be written to. This directory must be listed in the UTL_FILE_DIR parameter of the init.ora file before TUMS can write the report and must have the appropriate WRITE permissions.
Review the report.
The tumsr12.htm report lists the steps (identified by the TUMS step key in this book) that do not apply to your installation. You may safely ignore any steps listed in this report.
These tasks pertain to all users. You must complete them before you continue with the product-specific tasks in this chapter. All the steps in this section can be performed while the system is up and running, and are performed on the Release 11i APPL_TOP.
Applies to 11i release level: All
TUMS step key: N/A
Make a cold backup of the Oracle E-Business Suite database. You can use it to restore the database should you encounter problems during the upgrade process.
Note: Shut down the database with the NORMAL option. You may not be able to restore it from the backup if you use the IMMEDIATE or ABORT option.
In addition to the database files, back up the APPL_TOP, product customizations, and customized help files (in HTML).
Note: The upgrade process does not save customizations. You should copy all your customized files and put them in a safe place so you can reapply the customizations after the upgrade.
Applies to 11i release level: All
TUMS step key: N/A
You may have customized your system for business use. Take note of these important considerations before upgrading custom database objects:
The Oracle E-Business Suite Developer’s Guide contains extensive instructions about naming standards and issues related to upgrading custom database objects. Familiarize yourself with this information before you begin the upgrade.
Run several test upgrades and track their impact on your custom database objects.
Rename any custom database objects with Applications prefixes that you have created so that they do not conflict with Oracle object names.
Note: Failure to test the impact on custom database objects before the upgrade can result in a loss of functionality.
At your discretion, and depending on the customizations in your system, you should also perform the following tasks:
Preserve the CUSTOM library by making a backup copy of CUSTOM.pll. You can use this copy later in the upgrade process to migrate your CUSTOM library to Release 12.1.1.
If you have customized forms with Oracle Forms 6i, upgrade them to Oracle Forms 10i after the upgrade.
Applies to 11i release level: All
TUMS step key: FND_ENABLE_MULTI_ORG
Multiple Organizations architecture supports performance improvements across all Oracle Applications. It also supports Multiple Organizations Access Control, which enables an Applications responsibility to access multiple operating units if desired. This release requires that Multiple Organizations be enabled. If you have not done so already, you must convert to this architecture now.
Converting to Multiple Organizations does not require the use of multiple operating units or sets of books - it does enable you to use this functionality at any time in the future. If you are converting from a Single Organization architecture to a Multiple Organization architecture, complete the following steps:
Create an operating unit.
Assign the operating unit you created to the profile option MO:Operating Unit.
Note: See the following documentation references: Oracle Applications Multiple Organizations Implementation Guide, Use of Multiple Organizations (Multi-Org) in Release 11i (Doc ID: 210193.1), and MOAC in Oracle Purchasing (Doc ID: 404800.1). HRMS users should also see Setting Up Multiple Organizations in Oracle HRMS (Doc ID: 259546.1)
Applies to 11i release level: All
TUMS step key: N/A
To drop all event alert database triggers in custom schemas, run the alrdtrig.sql script, located in $ALR_TOP/admin/sql (in your Release 11i system). Re-create the triggers after the upgrade is complete.
Applies to 11i release level: All
TUMS step key: N/A
Make sure you allocate sufficient tablespace. For guidelines based on an upgrade of the largest Oracle production system (oraprod), see Applications Release 12 Upgrade Sizing and Best Practices (Doc ID: 399362.1).
Applies to 11i release level: All
TUMS step key: N/A
To prepare your system for the Oracle Applications Tablespace Model (OATM) functionality, you must run some preparation scripts. Download and unzip the new patch 7197489. Follow the instructions in the readme for running these scripts:
The tablespace model for this release (OATM) is based on database object type rather than product affiliation. The adgncons.sql script prepares adcrtbsp.sql, configures the database to hold the new products to be added during the upgrade, and switches your system to use the new tablespace model.
Generated by adgncons.sql, this script creates the new tablespaces, allocates unlimited tablespace to all APPS users, updates fnd_product_installation table with correct data and index tablespace information, assigns default tablespace to all APPS users, and sets the new_ts_mode flag in fnd_product_groups to Y.
Be sure to review the locations of the dbf files for each new tablespace listed in adcrtbsp.sql, and change the locations in the script as necessary. Ensure that you have adequate disk space for all the changes and additions that adcrtbsp.sql is going to make.
Note: Oracle has tested successfully an extent size of 128 K for small systems (for example, 100 GB database or the Vision database), and, for large multi-terabyte system, an extent size of 4-10 MB has been tested successfully.
(adgrants_nt.sql for Windows) Grants SYS privileges needed by Applications, and creates required views in SYS.
Note: Running the preparation scripts creates tablespaces and prepares the database objects only for new products. To migrate existing products to OATM, follow the instructions in Oracle E-Business Suite System Administrator’s Guide - Configuration.
This portion of the upgrade applies to all users. Complete these tasks before you perform the product-specific tasks in this chapter.
Perform the following tasks for Oracle Alert.
Applies to 11i release level: All
TUMS step key: FND_WORKFLOW_TASKS
Oracle Alert leverages the Workflow Notification Mailer to send alert e-mail messages and process responses, obsoleting the previous e-mail implementation. All incoming responses to alerts sent by the previous Oracle Alert E-mail implementation must be completed before the upgrade.
If you use response processing alerts and you have not already converted Oracle Alert to the Workflow Notification Mailer, convert now by applying Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (patch 5903765) to your Release 11i APPL_TOP. This roll up patch causes Oracle Alert to use the Workflow Notification Mailer for new alerts, but allows you to continue to run the Alert Response Processor for incoming responses sent before the conversion. Continue to run the Response Processor until you have no more outstanding responses of this kind.
Note: See About Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (Doc ID: 444524.1) for more information.
Complete the tasks only if you are using Customer Relationship Management products.
Perform these tasks if you are have Oracle Marketing or Sales products or Oracle Trade Management products active in your system.
Applies to 11i release level: All
TUMS step key: AMS_OSO_PLM_CHK
This release includes significant changes to the Product Lifecycle Management module, a hierarchical product catalog that expands the functionality and alignment among Oracle Sales, Oracle Marketing, and Oracle Intelligence products. There are several paths to creating the new product catalog, based on individual system configuration. For a description of all the options and the steps required to implement them, refer to Oracle Applications Sales & Marketing Product Catalog Upgrade (Doc ID: 396079.1).
Note: See Oracle Product Lifecycle Management User’s Guide for more information. See also Oracle Product Lifecycle Management Implementation Guide.
Perform these tasks if you are using Oracle Incentive Compensation.
Applies to 11i release level: All
TUMS step key: CN_PAYRN_REP_CHK
To verify that your Sales Compensation setup data is ready for the upgrade, download and apply patch 4963569 to your Release 11i APPL_TOP. This patch contains cnupgchki.sql (located in the first directory in utl_file_dir). Run this script manually. It creates a report that tells you what pre-upgrade steps are required. You can also view the results of the report in concatenated format in the AutoPatch log file (cnupgchki.log).
The following remedies are suggested for errors listed in the report:
| If this error exists... | Take this action before running the upgrade... |
|---|---|
| Calculation processes are not completed | Complete all calculation processes before the upgrade. |
| The following is a list of payruns that have not been paid | Pay these payruns before the upgrade. |
| The following salesreps have calculated lines that are not posted | Post all commission lines before the upgrade. |
| There are non-zero posted transactions that are not loaded | Load and pay all posted transactions before the upgrade. |
| The following salesreps have posted transactions that have not been paid | Pay all posted transactions before the upgrade. |
| The following salesreps have inconsistent data between commission lines and posted lines | Resolve these inconsistencies before the upgrade. |
Perform these tasks if you are using Oracle TeleService.
Applies to 11i release level: All
TUMS step key: N/A
Service upgrade scripts have been enhanced to allow you to choose the most appropriate upgrade path based on the value in the profile option Service: Upgraded Release (For Development User Only). The value in the profile option indicates the current Service version before the upgrade. Valid values are: 1158, 1159, and 11510.
Service upgrade scripts perform only the minimum upgrade logic required from the version specified in the profile option. If there is no value available for this profile option, then the upgrade scripts execute all logics from 11.5.8. If you don’t already have this profile option, then you can create it with an internal name CS_SR_UPDATE_RELEASE. Set the appropriate value (such as 1159, 11510, and so on) at the System level.
Perform these tasks only if you are using Oracle Mobile Field Service.
Applies to 11i release level: All
TUMS step key: CSM_SYNC_DATA
All Mobile Field Service users with changes pending in their mobile device should synchronize the mobile server. Do not make any additional changes using the Mobile Field Service application until the upgrade is complete, and all users have successfully re-synchronized.
Complete these tasks only for the Financials and Procurement products that are active in your system.
Perform these tasks only if you are using Oracle Financials for India
Applies to 11i release level: Patch level lower than IN60105D2
TUMS step key: JAI_CHECK_CUST
This step applies if you are not at the following patch levels. If you have already applied the patch set, or a later one, you can omit this step.
Oracle Financials for India patch set IN60105D2 (included in Release 11i patch 4153130)
Oracle Financials for India Service Tax Solution (Release 11i stand-alone patch 4239736)
Oracle Financials for India Value Added Tax Solution (Release 11i stand-alone patch 4245089)
Oracle Financials for India Tax Deduction at Source Solution (Release 11i stand-alone patch 4860026)
If you have not applied patch set IN60105D2 and the three stand-alone patches, then apply the patch set (included in patch 4153130), and the consolidated patch 4923208 for the stand-alone patches before you upgrade.
Perform these tasks only if you are using Oracle General Ledger.
Applies to 11i release level: All
TUMS step key: GL_MRC_REVIEW_SETUP
The Accounting Setup Manager replaces many forms and user interfaces in this release. We recommend that you run the Accounting Setup Manager Pre-Update Diagnosis report to identify potential incompatibilities that would prevent you from using some new features. The report identifies Release 11i setup for Multiple Reporting Currencies, General Ledger, Global Accounting Engine, Assets, Payables, and Receivables. In order to run this report successfully, apply patch 5259121 to your Release 11i APPL_TOP.
To access the report, run the Accounting Setup Manager Pre-Update Diagnosis report in the Standard Request Submission form from a General Ledger responsibility. Review the report and fix any setup it identifies as problematic. Note that modifying setup configurations is not easily done after the upgrade is complete.
Note: You can run the upgrade successfully without running this report or modifying the setup. All the features will function similarly to Release 11i. However, you may not be able to take advantage of some new functionality.
The report also details what changes, if any, the upgrade will have on certain objects. The following areas of the report show details in a tabular format. The table columns show necessary information, such as the reporting set of books name, currency, and description for unassigned reporting sets of books.
Sets of Books: Review Sets of Books To Be Upgraded to Secondary Ledgers
Multiple Reporting Currencies: Unassigned Reporting Sets of Books
Multiple Reporting Currencies: One Reporting Set of Books Assigned to Multiple Primary Sets of Books
Multiple Reporting Currencies: Reporting Sets of Books With Translated Currencies
Multiple Reporting Currencies: General-Ledger-Only Reporting Sets of Books
Multiple Reporting Currencies: Inconsistent General Ledger Conversion Rules
Multiple Reporting Currencies: Inconsistent Setup
Multiple Reporting Currencies: Incomplete Setup
Perform these tasks only if you are using Oracle iPayments.
Applies to 11i release level: See text for conditions
TUMS step key: IBY_SEC_UPGRADE
Complete this step only if you are using credit card encryption in Release 11i.
Oracle Payments (renamed from iPayments in Release 11i) handles credit card encryption, along with encryption of other payment cards and third-party bank accounts. If you are using Credit Card Encryption in Release 11i, then you need to prepare your data for the upgrade to the new encryption model.
Recommended: If you are using the Oracle Applications Credit Card Encryption feature that was introduced as a patch after Release 11.5.10, we recommend you complete all the historical credit card data migration programs provided with the patch. See the "Upgrade Steps for Credit Card Encryption" section in Oracle Applications Credit Card Encryption (Doc ID: 338756.1) for more information.
Required: If you are using the Oracle iPayment encryption feature, and have not yet moved to the enhanced Oracle Applications Credit Card Encryption feature, then you must apply patch 4607647 to your Release 11i APPL_TOP and complete the steps described in the Oracle Applications Credit Card Encryption white paper.
Perform these tasks only if you are using Oracle Internet Expenses.
Applies to 11i release level: All
TUMS step key: OIE_IMPORT_INTERCOMPANY_CHECK
Perform this step only if you have intercompany data in Internet Expenses (OIE) interface records that must be imported into Oracle Payables.
In this release, the Expense Report Import concurrent program is obsolete. Therefore, you must submit this program prior to the upgrade to ensure that all intercompany data in Internet Expenses interface records is imported into Oracle Payables. Fix any rejections and resubmit the program until all records are imported successfully.
Perform these tasks only if you are using Oracle Payables.
Applies to 11i release level: All
TUMS step key: AP_IMPORT_INVOICES_CHECK
In this release, global descriptive flex fields (GDFs) are obsolete and are moved into tax and payment columns. Several validations are performed based on the country the invoice is imported from on these GDFs. They are not upgraded in the open interface tables.
Import all invoices that have not yet been imported by running the Open Interface Import program on the 11i APPL_TOP. Resolve any rejections and resubmit the program until all invoices are imported.
Applies to 11i release level: All
TUMS step key: AP__CNFM_PAY_BATCH_CHECK
With the introduction of Oracle Payments, the new payment batch model is not compatible with 11i payment batches. To ensure that there are no in-process payment batches included in the upgrade processing, either confirm or cancel all payment batches before you begin.
Perform these tasks only if you are using Oracle Subledger Accounting and any of the associated products (see list included in Step 1).
Applies to 11i release level: All
TUMS step key: N/A
During the upgrade, existing accounting data from the subledgers is upgraded into the new Oracle Subledger Accounting data model. By default, the upgrade updates the data for the current fiscal year, as well as the necessary periods of the previous fiscal, to ensure that there are at least six periods included in the upgrade (occurs when the upgrade is performed in the first half of the fiscal year).
You may need to run the SLA Pre-Upgrade program if you are using Oracle General Ledger and at least one of the following subledgers: Assets, Cost Management, E-Business Tax, Payables, Receivables, or Projects Accounting. This optional program allows you to change the default number of periods of historic data to be upgraded.
You can define a larger range of periods to be upgraded, and you can decide to perform the upgrade for all or most of the data during the downtime phase. This is an important decision because some of the Oracle Subledger Accounting functionality, such as accounting reversals and business flows, rely on the existence of previous accounting data.
If you do not perform a complete upgrade of the accounting data, Oracle Subledger Accounting allows you to perform an additional upgrade of the data by running the SLA post-upgrade process whenever the missing data is required (see Subledger Accounting in Appendix G). This program is executed at the same time as daily operations. As a result, it may have an impact on overall system performance.
If you need to change the default number of periods of historic data to be upgraded, you must apply patch 5233248 to your Release 11i APPL_TOP and submit the SLA Pre-Upgrade program. When submitting this program, you can enter the following parameters:
Migrate all sets of books: Possible values are Yes (SLA Pre-Upgrade program updates the periods in all sets of books) or No (SLA Pre-Upgrade program updates the periods that belong to the selected set of books).
Set of books: Set of books to be upgraded where you have selected to upgrade one set of books.
Start Date: Date to be used to determine the first period to be upgraded. Does not have to be the starting date of a period - the initial period is determined as the first period in which this date falls.
Perform these pre-upgrade tasks only if you are using Oracle Leasing and Finance Management.
TUMS Step Key: OKL_LIC_CHK
Following are the mandatory pre-upgrade steps that must be completed before upgrading to Release 12.1.1
If you are upgrading from 11i OKLG, then apply the OKLG Pre-Upgrade patch (patch 6027572) on 11i OKLG code line. If you are upgrading from 11i OKLH, then apply OKLH Pre-Upgrade patch (patch 6027561) on 11i OKLH code line.
Note: If you are currently on 11i OKLG, then the minimum requirement is that you upgrade to 11i OKLG Rup3 (patch 4487651). If you are currently on 11i OKLH, then the minimum requirement is that you upgrade to 11i OKLH Rup3 (patch 5350898). If you are currently on any other 11i codeline, then the minimum requirement is that you install 11i OKLH and upgrade to 11i OKLH Rup3 (patch 5350898).
Run OKL Billing Pre-Upgrade Report to check for pending transactions that have not been transferred to Oracle Receivables. If there are any pending transactions, then you must run the following concurrent programs in the order given to clear the pending transactions:
Master Item - Process Billable Streams
Master Program - Prepare Receivables
Master Program - Receivables Bills Consolidation
Master Program - Receivables Invoice Transfer
Autoinvoice Master program
Fetch AR Invoice Numbers
Repeat these steps until all pending transactions are cleared.
Run OKL Disbursement Pre-Upgrade Report to check for pending transactions that have not been transferred to Oracle Payables. If there are any pending transactions, then you must run the following concurrent programs in the order given to clear the pending transactions:
Pay Invoice Prepare for AP Transfer
Pay Invoices Transfer to AP Invoice Interface
Investor Payables Consolidation
Payables Open Interface Import
Repeat these steps until all pending transactions are cleared.
Run the OKL Accounting Pre-Upgrade Report to check for pending transactions that have not been transferred to Oracle General Ledger. Also check for any accounting setup discrepancies. If there are pending transactions or setup discrepancies, then you must complete the following steps to clear the pending transactions and setup discrepancies:
Run the Accounting Entry Process
Correct accounting entries posted to the OKL sub ledger with an error using the Correct Accounting Entries window.
Run General Ledger Transfer
If any accounting templates are found that have more than two template lines, then update the accounting templates that have more than two accounting template lines and remove the percentage allocation.
Run the OKL Multi-GAAP Pre-Upgrade Report to determine which operating units can be upgraded to Automated Accounting for Multi-GAAP. The report lists those operating units that can be upgraded to Automated Accounting for Multi-GAAP, and those that are not eligible. The report lists the reasons why a particular operating unit cannot be upgraded to Automated Accounting and the conditions that must be met before the operating unit can be upgraded to Automated Accounting. To make an operating unit eligible for upgrade to Automated Accounting, ensure that the following conditions in the pre-upgrade environment are met:
The Reporting Product Asset Book profile option in 11i is defined.
The set of books associated with the Reporting Product Asset Book must not be the same as the set of books associated with its corresponding Corporate Book.
For all Multi-GAAP contracts, the local product and the reporting product must satisfy the following conditions:
The revenue recognition method of the local and reporting product must be the same.
The interest calculation basis of the local and reporting product must be the same.
If the book classification of the local product is Lease (Direct Finance lease, Operating lease or Sales Type lease), then the book classification of the reporting product must also be Lease (Direct Finance lease, Operating lease or Sales Type lease).
If the book classification of the local product is Loan, then the book classification of the reporting product must also be Loan.
If the book classification of the local product is Revolving Loan, then the book classification of reporting product must also be Revolving Loan.
The pricing engine of the Stream Generation Templates associated with the corresponding Accounting Templates of the local and reporting products must be the same.
All assets on all of the contracts in the Operating Unit must have the same corporate asset book.
For Multi-GAAP contracts, all assets on the Multi-GAAP contracts in the Operating Unit must have been created in the same tax asset book defined on the Reporting Product Asset Book profile option.
Re-running the OKL Multi-GAAP Pre-Upgrade Report upon making any changes in the pre-upgrade environment confirms if the particular operating unit is eligible for upgrade to Automated Accounting.
The following steps must be completed to select one or more operating units to be upgraded to Automated Accounting:
Navigate to Setup > Operational Options.
Click the Upgrade button to open the new Upgrade user interface.
Select the Automated Accounting value from the list of values for those operating units that need to be upgraded to Automated Accounting.
Click the Apply button to save the changes.
If a specific operating unit is not eligible to be upgraded to Automated Accounting, then the user interface displays the appropriate error message.
The secondary representation method can be defined as Automated Accounting only for those operating units that meet the above conditions.
Defining the secondary representation method value for operating units is an optional pre-upgrade step. If the secondary representation method is not defined in the pre-upgrade 11i environment, then the operating units will be upgraded with the following default values for the secondary representation method:
If the operating unit is not a Multi-GAAP operating unit in 11i, then the secondary representation method will be upgraded to Not Applicable in this release.
If the operating unit is a Multi-GAAP operating unit in 11i, then the secondary representation method will be upgraded to Report in this release.
Perform these tasks only if you are using Oracle Projects.
Applies to 11i release level: All
TUMS step key: PA_COMPLETE_DIST_TIEBACK_EXP
If you create expense reports using Pre-Approved Expenditure Entry or import unaccounted expense reports from external systems, then run the following concurrent programs for each operating unit that uses Oracle Projects as a source entry point for expense report creation, adjustment, or both:
PRC: Distribute Expense Report Costs
PRC: Interface Expense Reports to Payables
Expense Report Import (must be run from the Payables responsibility)
PRC: Tieback Expense Reports from Payables
Your Projects application specialist should ensure that all transactions are successfully interfaced and that no exceptions remain.
Applies to 11i release level: All
TUMS step key: PA_JRNL_IMPORT_TIEBACK_REV
Run the following concurrent programs for each operating unit implemented in Oracle Projects and Oracle Grants Accounting. Ensure there are no exceptions.
Journal Import: Complete Journal Import in General Ledger for all project journal sources
PRC: Tieback Labor Costs from General Ledger
PRC: Tieback Usage Costs from General Ledger
PRC: Tieback Total Burdened Cost from GL
PRC: Tieback Cross Charge Distributions From General Ledger (does not apply to Grants Accounting)
PRC: Tieback Revenue from General Ledger
Complete these tasks only for the Public Sector/University products that are active in your system.
Perform these tasks only if you are using Oracle Student Systems.
Applies to 11i release level: All
TUMS step key: IGS_UNV_CHECK_CUST
If you plan to use Student Recruiting in subsequent releases of Oracle E-Business Suite, then follow the instructions in this task to set up the key flexfield related to the Product Catalog as a single, unverified, alphanumeric segment to enable the upgrade scripts to migrate Academic Interests (Entry Status, Program, and Unit Set Code Data) to Product Catalog. Perform the steps on your Release 11i APPL_TOP.
Determine flex structure:
To determine the flex structure associated with the product catalog, complete these steps.
From the Development Manager responsibility, open the Default Category Sets form (Setup > Item Categories) and query all records.
Navigate to the record with the Functional Area Value of Product Reporting (FUNCTIONAL AREA_ID = 11) and make a note of the Category Set and Description values.
From the Development Manager responsibility (Setup > Setup Workbench > Catalogs), search for the Catalog with the name Category Set or Description that you noted in the previous step.
Click the retrieved record to find the flex structure associated with it.
From the Development Manager responsibility, navigate to Setup > Setup Workbench > Catalogs (tab) > Categories (sub-tab) > Create Category (side navigation bar).
On the Create Category page, enter the flex structure value that you obtained in the previous step. Click Continue.
On the next page, enter Product Cat and description EXACTLY as follows: OSS Academic Interest. Click Apply.
Modify the flex structure:
To modify the flex structure, complete these steps.
From the System Administrator responsibility, navigate to the Key Flexfield Segments form (Application > Flexfield > Key > Segments), using the Inventory and Flexfield Title: Item Categories filter.
In the list, find the structure associated with the one that matches the ID_FLEX_STRUCTURE_CODE retrieved in your query.
Uncheck the Freeze Flexfield Definition check box, if required, and click Segments.
Ensure that there is only a single segment associated with the Flex Structure assigned to the SEGMENT1 column. Click Value Set to examine the Value Set associated with the single segment.
Ensure that the format type is Char, the maximum size is 40, the validation type is None, and that none of the validation check boxes are enabled (for example, Numbers Only). The easiest way to accomplish this is to assigned the seeded 40 Chars Value Set to the segment.
Save the flexfield information, freeze the definition, and compile it.
Note: The data is not migrated when the Entry Status is closed. Entry Status and its relationship to Test Types and Organizational Units are obsolete. Therefore, no data is migrated from old Recruitment tables (IGS_RC_I_E_ORGUNITS and IGS_RC_I_E_TESTTYOS to the new Student Recruiting tables IGR__I_E_ORGUNITS and IGR_I_E_TESTTYPS, respectively.
The tasks in this section are required only if you are using Oracle Supply Chain Management products.
Perform the following tasks if you are using Oracle Bills of Material (BOM).
Applies to 11i release level: All
TUMS step key: BOM_CHECK_FOR_BOM_HEADER_DUPLICATES
Run the following query and verify the output:
select count(*)
from BOM_BILL_OF_MATERIALS
where ASSEMBLY_ITEM_ID IN
(select distinct ASSEMBLY_ITEM_ID
from BOM_BILL_OF_MATERIALS
group by ASSEMBLY_ITEM_ID,ORGANIZATION_ID,ALTERNATE_BOM_DESIGNATOR
having count(*) > 1 );
If the above query returns greater than '0' as the output, then perform the following steps:
Take backup of bom_bill_of_materials and bom_structures_b tables.
Refer to Note ID: 370841.1 and run the script provided in section 2: 'Query to Find list of duplicate BOMs' column within the 'Verification' section to identify duplicate records.
If there are duplicate records, then run the scripts provided in the 'A. DATAFIX' column within the 'Solution' section to fix duplicate records by populating 'Alternate Designator'.
Note: You must eliminate duplicate records before upgrading to Release 12.1.1.
Perform these tasks only if you are using Oracle Depot Repair.
Applies to 11i release level: 11.5.9
TUMS step key: CSD_DATA_CHECK
Apply Data Verification patch 5382135 to your Release 11i APPL_TOP. You can apply it as a hot patch by setting options=hotpatch when you run AutoPatch. If you apply it as a hotpatch, DO NOT merge it with any other patches.
The patch runs a script (csdpremr.sql), which generates an output file (csdpremr.lst) in the first directory defined in the utl_file_dir parameter. The output file lists problematic data and describes a resolution.
After you complete the necessary corrective action, rerun csdpremr.sql under the $CSD_TOP/patch/115/sql directory using SQL*Plus and continue to correct data until no further errors are reported.
Perform these tasks if you are using Oracle Enterprise Asset Management (EAM).
You must set up the Install Base Parameters and Services Profile Option in accordance with Note 884201.1. If this note is not checked and the IB Parameters are not verified and set up as described, then the eamsnupd.sql file will fail during patching, therefore creating data corruptions and the upgraded database will be compromised. Asset Numbers Upgrade will fail, and half of the Asset Numbers will be lost after the upgrade process.
Perform these tasks only if you are using Oracle Process Manufacturing.
Applies to 11i release level: All
TUMS step key: GMA_PREP_MIGRATE
To successfully migrate Oracle Process Manufacturing (OPM) Inventory data to Oracle Inventory, you must complete data cleanup and setup steps before the upgrade.
Perform the steps in the order listed, and before you continue with other tasks in subsequent sections.
Note: See OPM Release 12 Migration (Doc ID: 376683.1) for more information. Note that this reference is not a single document. It is a repository of OPM migration documentation.
Map data (all releases)
Map the data using the Convergence Migration Setup user interface in the OPM system Administration responsibility. Apply patches 4563075 and 6694260 to your Release 11i APPL_TOP for the user interface. See the OPM Migration Reference Guide in Doc ID: 376683.1 for details.
Run SQL validation scripts (all releases)
Apply patches 4699061 and 6696828 to your Release 11i APPL_TOP for the SQL validation scripts. See the OPM Migration Reference Guide in Doc ID: 376683.1 for details.
Migrate OPM organization and items (all releases)
Apply patch 4582937 to your Release 11i APPL_TOP and follow the instructions in the readme file. You can migrate OPM organizations and items discretely before the upgrade to reduce downtime.
Update Forecast headers in Forecast Set (all releases)
For 11.5.9 or Family Pack K and lower, apply patch 4268525 to your Release 11i APPL_TOP and follow the instructions in the readme. For all other releases, update Forecast headers to have a value entered in Forecast Set. Only those forecasts that have a value in this field are migrated.
Note: See Oracle Process Manufacturing Migration Reference Guide for more information.
Applies to 11i release level: All
TUMS step key: GMA_PREP_MIGRATE_FINISH
Make sure you have completed all the steps in the previous task prior before you begin this task. Perform the steps in the order listed. Users must be logged off the system.
Review, act on, and dispose of information in Oracle ASCP tables. (required for all releases that use ASCP)
Review, act on, and dispose of information provided in the Oracle Advanced Supply Chain Planning application tables: GMP_APS_OUTPUT_TBL and GMP_APS_OUTPUT_DTL.
Review, act on, and dispose of information in OPM MRP table. (all releases that use OPM MRP)
Review, act on, and dispose of the information in the OPM table: MR_ACTN_TBL.
Prepare for the batch snapshot (if there are open batches)
Take a snapshot to recreate all the open batches, then apply patch 4458024 to your Release 11i APPL_TOP.
Close all batches with a status of Completed (all releases)
Navigate to the Migration Setup User Interface Batches tab. Choose Mass Batch Close from the Action menu. See the OPM Migration Reference Guide in Doc ID: 376683.1 for details.
Capture snapshot (all releases)
Click the Process Batches for Migration button on the Convergence Migration Setup user interface to capture a snapshot of the open batches to be used during the post-migration process (that recreates the batches). See the OPM Migration Reference Guide in Doc ID: 376683.1 for details.
Complete or cancel pending transfer (11.5.10, or Family Pack K and later)
See the OPM Inventory Management User’s Guide for details about how to complete a pending transfer. Or, apply patch 4350832 to your Release 11i APPL_TOP to cancel pending transfers.
Back order or ship OPM Order Management Fulfillment sales orders that are pick-confirmed or staged prior to migration (all releases)
If these order lines are not shipped prior to the migration, then the only way to make them visible for updates to Oracle Inventory is to back order them prior to the migration.
Run Preliminary Inventory Close Process for all warehouses under all the OPM Companies (all releases). Do not run Final Inventory Close for the period in which you are running the upgrade.
Refer to the following table for instructions:
| If you are a... | Follow these instructions... |
|---|---|
| Standard Costing user | Post inventory and resource transactions to OPM Subledger and export to GL: Run the OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. See the OPM Manufacturing Accounting Controller User's Guide and the Oracle General Ledger User's Guide for details. Note: Once you upgrade, you cannot post the transactions created prior to the upgrade. |
| Actual Costing user | Run Actual Cost Process to calculate the cost and then post inventory and resource transactions to OPM Subledger and export to GL: Run the OPM Actual Cost Process, OPM Cost Update Process, OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. See the OPM Manufacturing Accounting Controller User's Guide and the Oracle General Ledger User's Guide for details. Note: Once you upgrade to Release 12.1.1, the Actual Cost program looks at transactions under process organizations recorded only in Oracle Inventory — the average cost calculations after the upgrade do not consider the transactions created in the Release 11i OPM Inventory system. As a result, the average cost calculated may not be accurate if the upgrade is done during the middle of a costing period and there are transactions in OPM Inventory for the same costing period. If possible, consider doing the upgrade at the beginning of a costing period. By doing so, you can ensure that a majority of transactions in that costing period are recorded In this release, thereby arriving at a more accurate average cost when you run the OPM Actual Cost Process. Once you upgrade, you cannot post the transactions created prior to the upgrade. |
| Lot Costing user | Run Lot Cost Process to calculate the cost, and then post inventory and resource transactions to OPM Subledger and export to GL: Run the OPM Lot Cost Process, OPM Cost Update Process, OPM Subledger Update, OPM GL Export, and General Ledger Journal Import. See the OPM Manufacturing Accounting Controller User's Guide and the Oracle General Ledger User's Guide for details. Note: Once you upgrade, you cannot post the transactions created prior to the upgrade. Note for Lot Cost Simulation Users: If you are using Lot Costs as additional cost method for simulation purposes, run the lot cost process in final mode before migration. Otherwise, the costs created in test mode may be wiped out when you run the process again in the upgraded system. |
Run the GMF validation scripts (all releases)
Refer to OPM Release 12 Migration (Doc ID: 376683.1) for details.
Migrate OPM Order Fulfillment to Order Management (all releases that use OPM Order Fulfillment)
Refer to the OPM Migration Reference Guide in Doc ID: 376683.1 for details.
Note: The migration process varies depending on your version.
Perform these tasks only if you are using Oracle Service Contracts.
Applies to 11i release level: All
TUMS step key: OKS_VALIDATE_GCD
In Release 11i, the global contracts default (GCD) setup had three different currency codes for each of the three threshold amounts: Active, Credit Card, and Electronic Renewal. In this release, only one currency (Base Currency) code is used for all the three amounts.
If there are different types of currency codes specified for these amount fields in the Global Contracts Defaults user interface, then the upgrade does not populate the base currency code. If the three currency codes are the same, then the currency code for Active threshold becomes the new Base currency.
If the codes are different, then populate the Global Contracts Defaults user interface with a single type of currency code before migration. Go to the Navigator and choose Setup > Service Contracts > Global Contracts Defaults to update contract defaults.
Applies to 11i release level: 11.5.9
TUMS step key: OKS_VALIDATE_RULE
This step is not required if you have already followed the downtime reduction technique steps mentioned in Service Contracts 12.0 Rules and Time Values Migration (Doc ID: 372469.1). See Appendix E, "Reducing Downtime" for more information.
Before Oracle Applications 11.5.10, Oracle Service Contracts used a set of Rules and Time Values tables to store contract attributes that were not included in base Oracle Core Contracts or Oracle Service Contracts header and lines tables. In Oracle Applications release 11.5.10 and later, new architecture eliminates the generic rules and time values data structures.
To validate the data, follow these steps:
Apply patch 4684603 to your Release 11i APPL_TOP. Follow the instructions in the readme file.
Log in to Oracle Applications and choose the Service Contracts Manager responsibility.
Run the Service Contracts Validate Rule Data concurrent request for the header level. (You can select the level from the concurrent request parameters screen.)
After the request is successfully completed, check the Output Log file for records that may have failed validation due to data issues. Click the View Output button after selecting the row corresponding to the main request to view errors. If there are no errors, then you can move directly to Step 6.
If there are errors in the Output log file, then navigate to View/Show navigator on the menu and choose the Rules Migration Utility form to view fields with data validation issues. Enter correct values for these records directly on this form, and save the changes. Ensure that all errors identified are corrected.
Run the concurrent request for the Header history level, the Line level, and the Line history level. Correct all errors and re-run the request until all errors have been corrected.
In this section, you complete final preparation tasks for your existing Release 11i system and create the new environment for Oracle E-Business Suite Release 12.1.1.
Applies to 11i release level: All
TUMS step key: N/A
This release employs cost-based optimization, which examines FND table statistics to determine the most efficient access paths and join methods for executing SQL statements. These statistics are gathered by the FND_STATS process, which you initiate by running the Gather Schema Statistics concurrent program.
Note: You should gather schema statistics on a regular basis to fully utilize the cost-based optimization feature. In preparation for an upgrade, this should be one of the last tasks you perform for initiating the upgrade downtime so that the statistics are current.
From your Release 11i APPL_TOP, complete the following steps:
Log in to Oracle Applications with the System Administrator responsibility.
Navigate to the Submit Request window (Request > Run).
Submit the Gather Statistics program.
Set the schema name to ALL to gather statistics for all Oracle Applications schemas (having an entry in the FND_PRODUCT_INSTALLATIONS table). In addition to gathering index and table-level statistics, the program gathers column-level histogram statistics for all columns listed in the FND_HISTOGRAM_COLS table.
Note: If your database is already at Oracle 10g, then we recommend that you use the Gather Auto option for this concurrent program. This option gathers statistics for objects that are either lacking statistics or whose rows have changed significantly (default 10%) since the last time you gathered statistics.
Note: See Query Optimization in Oracle E-Business Suite Concepts for more information.
Applies to 11i release level: All
TUMS step key: N/A
Make a cold backup of the Oracle E-Business Suite database. If you encounter problems during the upgrade process, you can use this backup to restore your system to the same state as before you began the upgrade.
Note: Shut down with the NORMAL option. You may not be able to restore the database from the backup if you use the IMMEDIATE or ABORT option.
Applies to 11i release level: All
TUMS step key: N/A
Use the Rapid Install wizard to lay down the file system and install the new technology stack for your Release 12.1.1 Oracle E-Business Suite system. The wizard collects configuration parameters and stores them in a configuration file (config.txt) in the Applications file system. When you run Rapid Install, it uses these values to lay down the file system structure and technology stack components for your configuration. As it runs, it creates a context file (<CONTEXT_NAME>.xml) that contains all the parameters that describe your system. This context file is created and managed by AutoConfig.
Note: See Oracle E-Business Suite System Administrator’s Guide - Configuration for more information about AutoConfig.
Be prepared to supply basic information about your system such as port specifications, existing and new database node descriptions (including mount points), user names and passwords, product license types, internationalization and language settings, and mount points for other nodes in your system.
Follow the instructions in Chapter 1 of Oracle E-Business Suite Installation Guide: Using Rapid Install to prepare your environment for the new system. Then, start Rapid Install by typing rapidwiz on the command line. The Welcome screen lists the components that are included in, or supported by, this release of Oracle E-Business Suite. Click Next.
On the Wizard Operation screen, select Upgrade to Oracle E-Business Suite Release 12.1.1. Click Next.
On the Select Upgrade Action screen, select Create Upgrade File System.
In the associated screen flow, enter the parameters required to set up your new environment. Then, run Rapid Install.
Note: Rapid Install (as it runs AutoConfig) records errors in the AutoConfig log file. These errors occur because the database has not yet been upgraded. They can be safely ignored. The errors will be resolved when you run Rapid Install (and AutoConfig) in Step 2 of the Finish the Upgrade section of Chapter 3.
Note: Oracle E-Business Suite Installation Guide: Using Rapid Install contains complete instructions for running Rapid Install for both new installations and upgrades. Chapter 3 contains the information specific to running an upgrade.
Run Rapid Install again after the upgrade to configure and start the servers and services. Rapid Install also delivers the unified upgrade driver that you will use later to perform the upgrade.
Applies to 11i release level: 11.5.9 (CU2) for 10g Release 2, 11.5.10 (CU2) for 10g Release 2 and 11g Release 1.
TUMS step key: N/A
Oracle E-Business Suite Release 11.5.9 (with CU2 applied) and Release 11.5.10 (with CU2 applied) are certified for use with Oracle 10g Release 2, while 11.5.10 (with CU2) is certified for use with Oracle 11g Release 1. If you have not already done so, you can upgrade your production database to at least 10g now, before the upgrade downtime. Follow the instructions in Database Preparation Guidelines for an Oracle Applications Release 12.1.1 Upgrade (Doc ID: 761570.1).
Note: A database upgrade at this point in the upgrade process applies only to the Oracle E-Business Suite release levels cited. You can perform the database upgrade during the downtime window as described in Chapter 3, if you have not done so previously.