Skip Headers

Oracle E-Business Suite Upgrade Guide
Release 11i to 12.1.1
Part Number E16342-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Verification Tasks

This appendix contains optional tasks that can be performed to verify that your transaction data was upgrade as expected.

This appendix covers the following topics:

Customer Relationship Management

This section contains upgrade verification tasks for the Oracle Customer Relationship Management (CRM) product family.

Email Center

These tasks apply only to Oracle Email Center.

Verify Email Accounts

After the upgrade, all email accounts except INTENT should be available. You can verify these accounts from the Email Center Administrator console screens in the upgraded environment. Administrators should plan to update the account properties and activate accounts as needed.

In addition, administrators should log in as a supervisor and verify that email messages from the live queues and Inbox can be viewed and replied to.

Incentive Compensation

These tasks apply only to Oracle Incentive Compensation.

Validate Existing Objects

Verify that the concurrent requests to generate collection and formula packages have been completed. Verify that the classification packages, collection packages, and formula packages are successfully generated and valid. If needed, regenerate these packages before using the product.

Verify Integration Points for External Modules

If your system uses external modules, ensure that the following integration points are still valid:

Marketing

These tasks apply only to Oracle Marketing.

Verify Migrated Campaign and Activity Data

From the Campaign workbench, verify that the header information and the mid-tabs were migrated as expected. From the Activity workbench, verify that the header information and activities with different channels (like Email, Fax, Advertising, and Telemarketing) were migrated as expected.

In addition, on the Additional Information mid-tab, turn on the deep links using OA Personalization, and verify that the associations are correct

TeleService

These tasks apply only to Oracle TeleService.

Verify Upgraded Data

Perform the following basic functions the ensure that the application is working as expected:

Monitor Historical Message Migration

You can use the Email Center migration screens to monitor the status of the message migration process. In case of error, the screen displays descriptive error messages. You should act on each message as required. In case of environment issues during the migration, you can re-run messages selectively.

Territory Manager

These tasks apply only to Oracle Territory Manager.

Verify Responsibilities and Roles for RBAC

To ensure that the upgrade to Role-based Access Control (RBAC) is complete, verify the following for your users:

Verify Availability of Territory Types

The named account type should exist by default. If the system contained geographical territories in 11i, there should be a geography type available with the enabled geographical matching attributes from 11.5.10. For non-geographical and non-named account territories that existed in 11.5.10, there should be a general <usage> type that contains all the enabled matching attributes.

Verify Mapping of the Territory Hierarchy View

Territories mapped from 11i should show the appropriate territory type and should have an end date defaulted to +10 years from the start date if the territory did not previously have an end date. In addition:

Financials and Procurement Tasks

This section contains upgrade verification tasks for the Oracle Financials and Procurement product family. These steps should be performed by the product specialist and/or a functional user.

To set up the verification, run benchmark reports for certain Release 11i transaction data before the upgrade. Then, after the upgrade is complete, run the same reports on the upgraded data and compare the results with the pre-upgrade versions. The transaction data in both sets of reports should match.

Advanced Global Intercompany System

These tasks apply only to Oracle Advanced Global Intercompany System.

You should review the Advanced Global Intercompany System organizations to ensure that each organization is assigned to a legal entity. In some cases, the automatic upgrade may not identify a single legal entity to associated to any intercompany organization. In that case, the organization is inactivated and you must update it with the correct legal entity before using it in transactions.

Assets

These tasks apply only to Oracle Assets.

Subledger Accounting Upgrade

You should run selected reports and run some online inquiries both before and after the upgrade to verify that your data has no discrepancies.

Verification Reports

Run the following reports prior to the upgrade in the Release 11i environment, and then again after the upgrade in the new environment. Compare the results to see if there are any discrepancies. You can run the reports for past periods or for a range of past periods or for the current period as applicable. However, it is important to note that when choosing the periods, you should choose only those that are within the range of periods that you ran the upgrade for.

You should also run the Account Drill Down Report in a Release 11i environment and the Account Analysis Report on the same set of data and compare the results.

Online Query

In your Release 11i environment, go to Inquiry > Financial Information and query a few assets. Click Books > Transactions, then go to Tools > view Accounting. Make sure you are looking at the accounting for transactions that happened in the current fiscal years.

In the new environment, use the same menu path and perform an online accounting inquiry for the same assets and transactions and compare the results. Note that in this release, the menu path takes you to the Oracle Applications Framework page.

E-Business Tax

These tasks apply only to Oracle E-Business Tax.

Tax Transaction Audit and Reconciliation Reports

To ensure that transaction tax information has been correctly upgraded, run the Payables Tax Audit Trail report and the Receivables Tax Reconciliation report for the current tax period before the upgrade to set a benchmark of transaction information.

Then immediately after the upgrade, run the same reports in the new environment for the same period and compare the results to ensure that the tax values are still the same.

Payables and Receivables Transaction Query

For a sample of Payables and Receivables transactions, record the details of the associated tax for these transactions before migration, and then query them again after the upgrade to ensure that the tax has been correctly upgraded.

Duplicate the same transactions and re-trigger to ensure that the new E-Business Tax-based calculation is consistent with the previous calculation.

Financials for the Americas

These tasks apply only to Oracle Financials for the Americas.

Brazilian Receivables Bank Transfer Accounting Entries

For occurrences that were already posted to the General Ledger prior to the upgrade, verify that the journal entries created in Subledger Accounting are synchronized with those created in General Ledger.

For occurrences that were not yet posted to General Ledger prior to the upgrade, run the Create Accounting program in draft mode (for the Receivables application and the Brazilian Bank Collection Occurrence Documents and Standard Receipts process category codes) to verify that the Subledger Accounting journal entries are created in the same way as they would have been in Release 11i.

Financials for India

These tasks apply only to Oracle Financials for India.

Verify Sample Reports

Verify the following sampling of reports (standard and customized), both before and after the upgrade and migration of data. Compare the data in the reports for accuracy.

The list of standard reports includes:

In addition, run the Income Tax Act Fixed Assets Schedule and Depreciation Detailed Report.

General Ledger

These tasks apply only to Oracle General Ledger.

Accounting Setup Manager Post-update Diagnosis Report

Run the Accounting Setup Manager Pre-update Diagnosis report prior to the upgrade and the Post-update Diagnosis report after the upgrade in the Standard Request Submission form in a General Ledger responsibility.

The diagnosis includes the following areas:

Review the report and verify that the changes suggested by the Pre-upgrade report were actually performed during the upgrade process.

Upgrade Verification with Reports

As a good practice, you should compare financial data and balances before and after the upgrade. We recommend that you submit common reports, such as the Account Analysis, Journals reports, Trial Balance report, and Financial Statements to compare balances and journals before and after the upgrade to ensure that the data was properly upgraded.

Global Accounting Engine

The following tasks apply only to Global Accounting Engine.

Run Accounting Reports

You should run the Global Accounting Engine accounting reports before the upgrade and the corresponding Subledger accounting reports after the upgrade to ensure that you have a proper audit trail of the upgraded accounting data. The reports are as follows:

Global Accounting Engine Subledger Accounting
Daily Journal Book Daily Journal Report
Account Ledger by Account Account Analysis Report
Supplier and Customer Subledger by Account Third Party Balances Summary
Supplier and Customer Balance by Account Third Party Detail and Balances Report

iProcurement

These tasks apply only to Oracle iProcurement.

Catalog Data Upgrade

In the iProcurement post-upgrade interface, you can see the data exceptions report and the list of newly created global blanket agreements by choosing the Configuration tab from the iProcurement Catalog Administration responsibility. Under Configuration, the Release 12 Upgrade Summary continues two tabs: Exceptions and New Agreements.

Exceptions Report:

Any data listed in the data exceptions report under the Exceptions tab is not available in iProcurement. To fix data issues, follow these steps:

  1. Download the XML file, if available in the exceptions report.

    For the upgrade process, the XML file can be downloaded for any error condition in the data exceptions report. There is one compressed file for each supplier/supplier site/contract/language combination. Within the compressed file, there may be multiple files for the action SYNC per each language in which data is available. The file name is ItemException_language.xml.

  2. Fix any data that appears in the downloaded file.

  3. Create or find a global blanket agreement (GBPA).

    You must load the content of the file into a GBPA. See the Upload feature in Oracle iProcurement Implementation and Administration Guide for more information on uploading content to a GBPA.

    Note: The upgrade data exceptions report is permanent. That is, even if you load the data into GBPAs with the XML file provided, you will continue to see the exception listed in the report.

Agreements Summary:

The upgrade automatically validates and approves all newly created GBPAs. Buyers have access to these agreements through Oracle Purchasing and requesters can search for the content of these agreements in Oracle iProcurement.

The New Agreements tab lists GBPAs based on contract purchase agreements (CPAs). You can see the CPA number used as source data in the GBPA header and the resulting GBPA numbers in the CPA attachment section. See Oracle Purchasing User’s Guide for more details on these documents.

Content Security Upgrade

For the content zones created as a result of the 11.5.9 and 11.5.10 migration, the upgrade uses the catalog name as the content zone name. To maintain responsibility and operating unit level access restrictions, multiple instances of content zones with the same catalog name may be created.

Catalog and Stores - Before the Upgrade

Content Zones - After the Upgrade

After running the upgrade script, check the Manage Content Zones screen in the e-Content Manager. It is possible that some catalogs have not been upgraded completely. In those cases, a warning icon is displayed next to the content zone name.

Note: Any content zone displayed with a warning icon requires further manual configuration before it will function properly.

In this release, content security restricts the number of suppliers, supplier sites, and categories that can be used in defining a content zone. A 2000 byte limit exists for performance concerns. In Releases 11.5.9 and 11.5.10, you could configure local catalogs to include up to 300 specific suppliers. During the upgrade process, iProcurement determines if the number of catalog restrictions for a given catalog can be translated into a string of less than 2000 bytes. When this is possible, iProcurement migrates the catalog into the new content zone(s) completely and automatically. No further user action is necessary.

When a string of 2000 bytes cannot fully encompass the scope of catalog restrictions for a given catalog, iProcurement is not able to migrate the entire catalog completely into the content zones. When this happens, a warning icon is displayed next to the content zone(s) on the Manage Content Zone screen.

Example:

In the following example, you must manually divide the list of suppliers and categories restrictions into two or more content zones.

Suppose a “Stationery Supplies” store contains a single local catalog named “Local.” The catalog contains a selection of several suppliers. During the upgrade process, iProcurement cannot translate all specific suppliers into a single content zone because of its 2000 byte limit, so a warning icon is displayed next to the “Local” content zone in the Manage Content Zones screen.

In order to retain the shopping behavior requesters experienced in iProcurement, a Catalog Administrator must manually remove some of the 300 suppliers referenced in the “Local” content zone and create a second content zone to include those suppliers. Both of these content zones can be included in the “Stationery Supplies” store.

Legal Entity Configurator

These tasks apply only to Oracle Legal Entity Configurator.

Legal Entities and Establishments

You should perform a review of all legal entities and establishments in your system after the upgrade is complete to ensure that the correct legal structure is in place. You can access this information by using the Search Page in the Legal Entity Configurator.

You can find detailed information about the assumptions made during the migration and the data migrated from country-specific fields in the Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12.

If you need to create or upgrade legal entities and establishments, then see the Oracle Financials Implementation Guide for instructions.

Payables

These tasks apply only to Oracle Payables.

Trial Balance Reconciliation

In your Release 11i environment, run the Accounts Payable Trial Balance, Posted Invoice Register, and Posted Payment Register reports. After the upgrade, run the Open Account Balances Listing Report, Posted Invoice Register, and Posted Payment Register in your upgraded environment and compare the results.

Note: The reports run for a ledger or a ledger set, not within the context of a single operating unit. The Release 11i Trial Balance and Posted Invoice and Payment Registers run within a single operating unit. Depending on your system configuration, you may need to sum several of the 11i reports to tie to the new versions.

Invoice and Payment Processing

To verify the integration with Oracle Payments and the upgrade of existing invoices, submit a payment batch with limited selection criteria in order to pay a few invoices.

Tax Setup and Processing

See E-Business Tax in this appendix.

Accounting Setup and Processing

Query an invoice that was not validated prior to the upgrade, then submit accounting for that invoice. Query an invoice that was accounted before the upgrade, cancel it, pay it, and then account for the payment. See Global Accounting Engine in this appendix.

Payments

These tasks apply only to Oracle Payments. In general, your planning for upgrade verification should involve testing in the two payment process areas:

System Security Options

Oracle Payments provides this new page where system-level settings for encryption, masking, and credit card security can be controlled. When your upgrade is complete, you should plan on reviewing the seeded settings in this page to ensure they meet your business needs. For example, in Release 11i masking of credit card values is controlled in different ways throughout the applications. In this release, the central setting in this page controls all masking. You will want to review the setting in this page and modify it if needed.

Oracle Payables Impact

You may want to run reports for use in your upgrade verification testing. For example, you may want to use the Suppliers Report in Oracle Payables to verify the data upgrade for payment details and bank accounts on the payees created in Oracle Payments. You can use any reports that you ran before the upgrade to help verify upgraded data. In addition, there are some key setup entities that should be reviewed and used in testing payment processing.

Disbursement System Options

This setup page allows you to review and set system options used in the funds disbursement payment process. You should plan on reviewing the upgraded and seeded settings in this page to ensure they meet your business needs. For example, the option to allow override of the payee’s bank account on a proposed payment is upgraded from the equivalent setting in AP Payables Options. You will want to verify that the upgrade correctly set this option for each of your operating units.

Oracle Receivables Impact

You may want to run reports for use in your upgrade verification testing. For example, you may want to run the Oracle Receivables Customer Detail Listing report to help verify the data upgrade for payment details and bank accounts on the payers created in Oracle Payments. You can use any reports that you ran before the upgrade to help verify upgraded data. In addition, there are some key setup entities that should be reviewed and used in testing payment processing.

Upgrade Verification Planning for Release 11i iPayment Users

It is important that you plan to review the overall setup for the funds capture process flow. In particular, you should plan time to verify that the settings upgraded to the new process profiles, transmission configurations, and payment system accounts are correct. The upgrade program automatically migrates settings found in iPayment. However, due to the complex nature of areas like network configurations and required values for communication with your payment processors, the upgrade may not create all the new data as you expect.

You should also plan on reviewing the Payee configurations after you upgrade. You should review all the settings, but specifically check that the operating unit assignments are set the way you expect. These are set based on transactions in Oracle Receivables and the upgraded settings should be checked to ensure that you will process new funds capture transactions in the way you expect.

Once you have reviewed and made any corrections to the upgraded configurations, you should run a test payment process with each configuration that you plan to use in production.

Payment Processing Extensions and Customizations

With the introduction of Oracle Payments, the data model used for payment processing this release is considerably different than that in Release 11i. Please note in particular that the formatting of payment files has changed completely with the new framework and Oracle XML Publisher integration. It is important that you review any custom payment formats, extensions or other customizations that you have created in this business area, and plan for obsoleting them by using new functionality or rebuilding them to work on the new model. You should plan on testing any custom payment formats, extensions, or other customizations that you have created, and verify that they work with the new payments architecture.

Receivables

These tasks apply only to Oracle Receivables.

Integration with Oracle E-Business Tax

See the E-Business Tax section of this appendix.

Integration with Oracle Subledger Accounting

Integration with Oracle Payments for Funds Capture

See the Payments section of this appendix.

Balance Forward Billing

Late Charges Enhancements

Customer User Interface Redesign

Query upgraded customer records and verify that setup attributes at the account, account site, and business purpose levels are the same as in Release 11i.

Sourcing

The following tasks apply only to Oracle Sourcing.

Header Requirements Verification

After the upgrade, log in as a sourcing buyer. Create a draft negotiation and verify that there is a Requirements section on the Create Negotiation: Header page. Also, confirm that the Header Attribute section is not available. Verify that Section Name has replaced Group Name.

Template Migration

After the upgrade, log in as a sourcing buyer. Retrieve an existing auction or Request for Quote (RFQ) template and verify that at the header level, there is a new field for Operating Unit. Verify that there is also a check box for Global Template.

Trading Community Architecture

The following tasks apply only to Oracle Trading Community Architecture.

Address Validation

To ensure the address validation setting has been correctly upgraded please check the following:

Treasury

The following tasks apply only to Oracle Treasury.

Bank Account Migration

In this release, internal bank accounts are migrated from Treasury to Cash Management. Prior to the upgrade, take a snapshot of ALL (company, subsidiary, and counterparty) bank accounts and all their attributes. Also, take note of all counterparties used as banks.

After the upgrade, perform the following steps to verify that the bank accounts are properly migrated:

Note: See the Oracle Cash Management User Guide for details.

Bank Account Balance Migration

In this release, bank account balances are migrated from Treasury to Cash Management. Prior to upgrade, identify a sample set of company, subsidiary, and notional cash pool bank accounts and take a snapshot of the bank account balance details of these accounts. Also, take a snapshot of all interest rates that are set up as default rates for bank account balances. These rates are not going to be upgraded and you will need to recreate them after upgrade as interest rate schedules.

After the upgrade, perform the following steps to verify that the company and subsidiary bank accounts are properly migrated:

After the upgrade, perform the following steps to verify that the notional cash pool balances are properly migrated:

Note: See the Oracle Cash Management User's Guide for details.

U.S. Federal Financials

The following tasks apply only to Oracle U.S. Federal Financials.

Treasury Confirmation and Reconciliation

Submit a payment process request from Oracle Payables with limited selection criteria in order to pay a few invoices. Have Treasury confirm the payment instruction in the the Treasury Confirmation and Reconciliation window and verify the subledger accounting was created as expected. This verifies not only the integration with Payments and the upgrade of existing Payables invoices, but also the treasury confirmation process and accounting in U.S. Federal Financials.

Budget Execution

Enter budget execution transactions at various budget levels to verify the accounting is created as expected.

Projects

This section contains upgrade verification tasks for the Oracle Projects product family.

Property Manager

The following tasks apply only to Oracle Property Manager.

Verify Upgraded Data

Perform these steps to verify that E-Business Tax, Subledger Accounting, and Legal Entity data was successfully upgraded:

E-Business Tax:

Subledger Accounting:

Legal Entity:

Projects

The following tasks apply only to Oracle Projects.

Verify Subledger Accounting Integration

In your Release 11i environment, run the AUD: Revenue Audit report for an accounting period in the current fiscal year that has been closed. After the upgrade, run the same report in your upgraded environment and compare the results.

Verify E-Business Tax Upgrade

Use the Event Types, Expenditure Types, and Invoice Review screens to check for invoices, event types, and expenditure types to make sure that they were upgraded successfully.

Verify Resource List Migration

You can view existing resource lists that were successfully migrated to resource planning lists on the Planning Resource Lists page. You can also verify that the planning resources are the same as the resource list members.

Also the Resource Breakdown Structures page displays a resource breakdown structure with the same name as the resource list. Verify that the nodes of the resource breakdown structure are the same as the resource list members, and have the same two-level hierarchy if the resource list was grouped.

Supply Chain Management

This section contains upgrade verification tasks for the Oracle Supply Chain Management product family.

Cost Management

These tasks apply only to Oracle Cost Management.

Verify Subledger Accounting Integration

To verify that the integration with Subledger Accounting was successful and that the data contains no discrepancies, complete these steps:

  1. Verify that the accounting events for transactions prior to upgrade are available in the Subledger Accounting (SLA) events page. Verify and match the corresponding Journal Entries (headers and lines) for these accounting events.

  2. Use the following reports to show balances and values derived from the accounting entries prior to the upgrade:

    Report Name Use
    Material Account Distributions (Details and Summary) View the accounts charged for inventory transactions
    WIP Account Distributions (Details and Summary) View account information for work-in-process transactions
    Discrete Job Value (Average and Standard) Analyze a summary of the transactions behind the charges and variances for each job
    Receiving Account Distributions View accounting distributions for receiving transactions
  3. Use the Journal Entries Report - Cost Management to summarize the upgraded accounting entries in SLA by organization and accounting class. Compare the summarized account balance at the organization level between the reports listed in the reports in Step 2, and the SLA Journal Entry report.

Order Management

The following tasks apply only to Oracle Order Management.

Verify and Review Upgrade Error Report

The upgrade process automatically produces a report (ontexc16.lst) that lists recommendations about, or errors that occurred during, the upgrade of Pre-Payment Order, Profiles moved to System Parameters, and Order Management Defaulting Rules. The report is located at $APPL_TOP/admin/<SID>SID>/out (UNIX) or %APPL_TOP%\admin\<SID>SID>\out (Windows), where <SID> is the value of the ORACLE_SID or TWO_TASK.

After the upgrade is complete, and before you use Oracle Order Management, you should review the report and fix any issues you find there.