11i Assessment Questionnaire

ORACLE APPLICATIONS
MIGRATION DISCOVERY
DISCOVERY QUESTIONNAIRE
Year 2000 Readiness Disclosure
Author: AGSL - Methods/Tools

Creation Date: June 17, 2002
Last Updated: November 2, 1998
Control Number: 1C
Version: 1.2
Approvals:
<Approver 1>
<Approver 2>
Copy Number _____

Migration Discovery Questionnaire Release 1.2.0
Part No. <Part Number>
Copyright © 1998, Oracle Corporation
All rights reserved.
Authors: Steve Buchan, Gary Burns, Joyce Knapp, Bill Matson, Fred J. Walker
Contributors: Mary Allgood, Lori Coleman, Ahmer Hasan, Cheryl Hornbaker, Michael Kurtz, Greg Kuhn, Nancy
McDowell, Connie Meyers, Walter Rewar, Mauricio Rojas, Debbie Seib, Tom Wainwright, Caroline Wheaton
Editors: Linda Goossens
The programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous
applications. It shall be licensee’s responsibility to take all appropriate fail-safe, back up, redundancy and other
measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims
liability for any damages caused by such use of the Programs.
This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement
containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is
prohibited.
If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered
with Restricted Rights and the following legend is applicable:
Restricted Rights Legend Programs delivered subject to the DOD FAR Supplement are ‘commercial computer
software’ and use, duplication and disclosure of the Programs shall be subject to the licensing restrictions set forth in the
applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are
‘restricted computer software’ and use, duplication and disclosure of the Programs shall be subject to the restrictions in
FAR 52.227-14, Rights in Data --General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle
Parkway, Redwood City, CA 94065.
The information contained in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free.
ORACLE, Oracle Designer, Oracle Developer, SQL*Plus, SQL*Loader, SQL*Net, CASE*Method, ORACLE Parallel Server,
PL/SQL, Pro*C, SQL*Module are registered trademarks of Oracle Corporation, Redwood City, California.
AIM Advantage, CDM Advantage, EMM Advantage, PJM Advantage, Oracle Cooperative Applications, Oracle Financials,
Oracle Alert, Oracle Manufacturing, Oracle Inventory, Oracle Bills of Material, Oracle Engineering, Oracle Capacity, Oracle
Commissions, Oracle Master Scheduling, Oracle MRP, Oracle Work in Process, Oracle General Ledger, Oracle Assets, Oracle
Order Entry, Oracle Cost Management, Oracle Payables, Oracle Receivables, Oracle Personnel, Oracle Payroll, Oracle
Purchasing, Oracle Quality, Oracle Sales and Marketing, Oracle Service, and Application Object Library are trademarks of
Oracle Corporation, Redwood City, California.
Oracle Method is a service mark of Oracle Corporation, Redwood City, California.
Microsoft and MS-DOS are registered trademarks and Windows, Word for Windows, Powerpoint,
Excel, and Microsoft Project are trademarks of Microsoft Corporation. Visio is a trademark of
Visio Corporation. Project Workbench and Project Bridge Modeler are registered trademarks of
Applied Business Technology. All other company or product names mentioned are used for
identification purposes only and may be trademarks of their respective owners.
407231.doc Copyright © 1998, Oracle Corporation II. Overall Upgrade Project Scope and Approach ii
Document Control
Change Record
Date Author Version Change Reference
Reviewers
Name Position
Distribution
Copy No. Name Location
1 Library Master Project Library

2 Project Manager
3
407231.doc Copyright © 1998, Oracle Corporation II. Overall Upgrade Project Scope and Approach iii
Contents
Document Control.....................................................................................................................iii
I. Introduction.............................................................................................................................6
Purpose.................................................................................................................................6
Background..........................................................................................................................6
Year 2000 and EMM...........................................................................................................6
Scope and Application.........................................................................................................7
How This Document Is Structured......................................................................................7
How to Use this Document..................................................................................................8
II. Overall Upgrade Project Scope and Approach......................................................................9
Introduction [A.]..................................................................................................................9
Upgrade Project Constraints [a.]...................................................................................... .........9
High-Level Project Scope [B.].............................................................................................9
High-Level Upgrade Project Scope [a.].................................................................................... .9
Detailed Project Approach [C.].........................................................................................12
Upgrade Project Objectives [a.]............................................................................... ...............12
Phasing [b.].............................................................................................................. ...............12
Staffing [c.]....................................................................................................... ......................12
Testing [d.]................................................................................................................ ..............13
Project Management [e.] ............................................................................................. ...........14
Business Process Change [f.] .................................................................................... .............15
Implementation of New Features [g.] .................................................................................... .15
Implementation of New Modules [h.]..................................................................... ................15
Technical Architecture Changes [i.].......................................................................... ..............16
Changes to Applications Architecture (Multi-Org) [j.]...................................... .....................17
Multiple Reporting Currencies requirements [m.]............................................................ ......19
Support for the Euro Common Currency [n.].............................................................. ............19
Audit Requirements [o.]....................................................................................................... ...20
Project Communications [p.] ................................................................................................ ..20
Language Support (NLS) [q.]............................................................................................. .....20
Physical Location(s) of Project Team(s) [r.]................................................................... .........20
Network Considerations [s.]............................................................................ .......................21
2.III . Current Systems Infrastructure......................................................................................22
Common for All Environments [A.]........................................................................................23

Oracle Applications Environments [a.]................................................................... ................23
Corporate Network [b.]............................................................................................. ..............23
Support Infrastructure [c.]............................................................................................. ..........24
Oracle Applications Environment - [B.]..................................................................................25
Oracle Application Modules [a.]................................................................................. ............26
Customizations [b.].................................................................................................. ...............28
Current Data Condition [c.]............................................................................... .....................29
Current Documentation Status [d.]..................................................................... ....................29
Configuration - General [e.]........................................................................................... .........30
Backup and Recovery Support [f.]........................................................................ ..................30
Required Non-Oracle Applications Software Upgrades [g.]................................. ..................31
Environment Synchronization [h.]........................................................................................... 31
Printers [i.]................................................................................................................... ...........31
Master Database Layer [C.]...............................................................................................32
Hardware [a.]......................................................................................................... .................33
Operating System [b.]........................................................................................... ..................33
Oracle Database Server [c.]............................................................................... .....................34
Third-Party Software Installed [d.]..................................................................... ....................35
Interfaces [e.].................................................................................................... ......................35
Custom Extensions [f.] ....................................................................................................... ....36
Applications Server Layer (NCA only) [D.].....................................................................47
Oracle Applications Server (NCA and WEB Deployed Applications Only) [a.].....................47
Forms Listener [b.]................................................................................................................ ..48
Hardware [c.]....................................................................................................... ...................48
Operating System [d.]........................................................................................... ..................48
Third-Party Software Installed [e.]........................................................................................ ..49
Custom Extensions [f.]....................................................................................................... .....49
Custom Applications [g.]....................................................................................................... ..50
Client Device Layer [E.]....................................................................................................51
Terminal Emulation (Character mode Only) [a.]................................................ ....................51
Browser Version (NCA and Web Deployed Applications Only) [b.]............................... ........52
JVM Environment (NCA and Web Deployed Applications Only) [c.]........................ ............52
Hardware [d.].............................................................................................................. ............52
Operating System [e.].............................................................................................................. 52
Third-party Software Installed [f.]........................................................................ ..................53
Custom Extensions - (Smart Client only) [g.]................................................................ .........53
Custom Applications (Smart Client only) [h.]........................................................................ .54
Issues.........................................................................................................................................55
General...............................................................................................................................55
Open Issues........................................................................................................................55
Closed Issues......................................................................................................................55
I. Introduction
Purpose
Migration Discovery is an activity designed to assist in the gathering of information to facilitate
the development of detailed upgrade project plans and overall project estimates.
Background
Oracle’s EasiPath Migration Method (EMM) provides guidelines and productivity tools for teams
conducting upgrade projects. EMM is Oracle’s life-cycle method and tool kit for migrating from
one release of the Oracle Applications to another.
At times, a Migration
Discovery may occur
following a Preliminary Relationship
Migration Assessment. Between Assessment EasiPath Migration Method
Migration
Tools Update Transition Production
t ion Assessment & Test
ma
Migration Discovery In
for
f
then provides enough cyo
ra
information to support ccu
d/A Migration
the detailed project ere Discovery
ath
planning and project ils
G
ta
estimating activities. De
Preliminary
Later during the Migration

Assessment
application upgrade,
while in the Migration
Assessment phase, the
details of the upgrade
elements are defined in
further detail. The
diagram above illustrates the relationships among each of these three migration tools that can be
used to support the information gathering requirements for an upgrade project. Again,
information gathered in each tool is carried forward as input to the next tool. Each of these
information gathering tools are designed to link to each other.
Preliminary Migration Assessment and Migration Discovery activities are optional, but
recommended.
Year 2000 and EMM

Many organizations are upgrading their Oracle Applications environments to support Year 2000
objectives. In the past, two character date coding was an acceptable convention due to perceived
costs associated with the additional disk and memory storage requirements of full four character
date encoding. As companies approach the year 2000, it is now evident that a full four character
coding scheme is more appropriate.
In the context of the EasiPath Migration Method (EMM), we use the convention Century Date
support rather than Year2000 support. We feel that coding for any future century date is now the
modern business and technical convention.
Scope and Application
The scope of the Migration Discovery activity consists of the steps necessary to obtain sufficient
information to effectively estimate and prepare for the upgrade of Oracle applications, including
achieving Century Date compliance.
For clients with multiple Oracle application environments, the Migration Discovery scope may
include all environments or a subset. However, if a subset is addressed, care must be taken to
ensure that dependencies between environments are considered.
To conduct a Migration Discovery, follow the six steps listed below:
• Complete as much of the questionnaire by client personnel in advance of the arrival of

trained consulting personnel.
• Interview site personnel using the questionnaire to guide the activity.
• Analyze site documentation including: systems, customization, interface, integration, and
operating documentation where available.
• Complete a preliminary assessment of existing customizations resulting in an estimate of
which customizations need to be migrated to the new Oracle Applications release and
how much work will be required to align the customizations for the new technical
environment.
• Consolidate the information from the activities above and develope metrics for input to
the project estimating activity.
Use this document to:
• Help facilitate the Migration Discovery activity.

• Conduct interviews and document the results.
• Record key outputs from any diagnostic tools used to identify Century Date compliance
problems.
• Act as the central repository for Migration Discovery information.
• Support the development of information to be used by downstream activities such as
detailed project planning and estimation.
How This Document Is Structured

This document is structured to accommodate the survey of one or more environments that may be
in use. Structurally, the document looks at what is common across the organization followed by
repeating sections specific to each of the environments.
Migration Discovery Questionnaire
Introduction
Overall Upgrade Project Information
Common For All Environments
Oracle Applications Environment

Master Database Layer
(Repeated for each environment)
Applications Server Layer
Client Device Layer
How to Use this Document
The typical Migration Discovery would involve client personnel working in advance of the
arrival of consultants to complete as much of this document as possible. Many of the questions
may require assistance and may have to await the arrival of the trained consultants before being
answered.
The client is asked to appoint a single point of contact for the Migration Discovery activity. This
individual would then circulate the document among those who would most likely be able to
answer questions posed by the questionnaire.
This document is designed to be directly used during information gathering and consultant-
facilitated interviews to provide:
• explanations of why topics should be addressed

• questions to be answered
• convenient formatted space after each question to record the answer
• empty tables where information from an automated code assessment tool can be recorded
• a repository document that will be referred to extensively by the upgrade project manager
Once the Migration Discovery Questionnaire is completed, it is assessed off-site. During this
assessment, technical details and outstanding questions regarding the upgrade approach and
strategy are resolved, and a project approach and detailed estimate of the shared labor effort is
completed.
If multiple Oracle application environments are within the Migration Discovery scope, complete
separate environment sections of the questionnaire for each environment, then integrate them
into one final document.
Check boxes, such as the examples shown below, are used throughout the document to help
gather and classify information. When you see check boxes later in the document please put a
check mark in the appropriate check box(es):
• Base Software Upgrade

• Retrofit Misaligned Customizations
• No Customizations
II. Overall Upgrade Project Scope and Approach
Introduction [A.]
This section captures information relating to the overall scope and approach for the upgrade
project. Later sections of this document will focus on the specific Oracle Application
environments being upgraded.
Upgrade Project Constraints [a.]

Constraints impacting the upgrade project should be considered. Other projects may have
implementation dates requiring the Oracle Applications upgrade to be completed by a certain
date. Mergers or acquisitions may result in additional timing requirements. Certain staff may
only be available at certain times. Hardware and software availability and order lead times may
influence the project schedule.
At times, constraints may reasonably be expected to cause the development of a phased approach
to the upgrade. Perhaps the first phase may deal with a very basic upgrade to achieve the
enterprise’s Century Date objectives. This may be followed by a more ambitious phase to review
new features in the applications, and apply them to the enterprise, or the removal of prior
customizations that are no longer needed.
1. When should the production upgrade be completed?
<answer>
2. Are there any other projects underway, or planned, that will have an impact on the
completion of the Oracle Applications upgrade project?
<answer>
3. Are there any hardware, software, or business constraints that will affect the timing of the
upgrade?
<answer>
High-Level Project Scope [B.]

Identify the high-level project scope in terms of how much process re-alignment and optional
activities are planned for the upgrade project.
High-Level Upgrade Project Scope [a.]

1. Place a check mark in the appropriate box or boxes (see below for details):
• Comprehensive
• Basic Upgrade
• Minimal Upgrade
Minimal Upgrade
At a minimum, you need to undertake the Base Software Upgrade and Retrofit. Misaligned
Minimal
Retrofit Misaligned Customizations
Base Software Upgrade
Customizations. These are customizations that no longer work as a result of changes to the
applications or environments. In many cases, this is a natural phase end boundary. It is
important to ensure that you are at least on release 10.7 for Year/2000 capabilities in time to
align to your first use of dates in the new century. Also note that forward use of dates for
planning, budgeting, and forecasting often occur a year to two earlier than the current date.
Basic Upgrade
Normally, a migration also includes the objective to remove prior customizations that have been
Remove Customizations Eclipsed by

New Features
Basic

eclipsed by new application features. In some cases, the old customizations may continue to
function; however, it would be advantageous to reduce the number of customizations as Oracle
enhances the capabilities of the applications. This may occur in a phase subsequent to the
achievement of the minimal migration approach.
Comprehensive Upgrade
To ensure that your enterprise is achieving the highest return on investment in Oracle’s
applications, you should consider a detailed review of the entire inventory of capabilities of the
applications in the new release by performing a Business Process Re-Alignment exercise. Often
capabilities have been added to the applications that can be directly applied to areas of your
business where processes were not supported in the past. This may also be a subsequent phase.
Re-Engineer Business Processes to take Advantage

of New Features
Comprehensive
Remove Customizations Eclipsed by
New Features

•
Detailed Project Approach [C.]
The approach to the upgrade project may be influenced by many factors. Answer the following
questions to obtain information necessary to determine the most effective project approach.
These specific aspects of the Detailed Project Approach will form the basis for the project. These
rules of engagement are further documented during detailed project planning and are agreed to
and administered by everyone on the project.
Upgrade Project Objectives [a.]

Understanding the key objectives for the upgrade project is essential. “Upgrading Oracle
Applications” is not a business objective. “Achieving Century Date compliance”, “maintaining
eligibility for Oracle support”, and “improving business process efficiency through the use of new
release features” are examples of business objectives.
1. What are the key objectives for this upgrade project?
<answer>
2. How will success be measured?
<answer>
Phasing [b.]
For complex upgrades, there may be a need to phase the work effort into multiple upgrade
projects. Various Oracle Application environments may exist with different releases,
customizations, languages, and currencies. They may exist in different locations and be
influenced by different sets of business factors. Upgrading the enterprise-wide solution in phases
can add substantial complexity.
However, for clients that have multiple production environments, it may be more advantageous to
address each environment upgrade as a separate, stand-alone project.
1. Identify any business factors requiring Oracle Application environment upgrades to occur at
different times.
<answer>
2. Identify any software issues requiring Oracle Application environment upgrades to occur at
different times.
<answer>
3. Identify any hardware factors requiring Oracle Application environment upgrades to occur at
different times.
<answer>
Staffing [c.]
Staffing approaches may include in-house personnel and various other third-party software and
consulting organizations.
1. Generally, the plan is to principally staff the project with in-house resources, external
resources, or a combination:
• In-house, no external (Migration Discovery only)

• In-house, some external for planning/QA (detailed project planning/QA)
• External, some internal for planning/QA (turnkey upgrade)
• External, some internal for planning/QA/Technical (turnkey upgrade with assistance from
the client’s technical staff)
• Combination, as required, dependent on available staff by skill set or area (standard
upgrade project)
2. What client staff will be available for full-time or part-time assignment to the upgrade
project? When will they be available and for how long?
<answer>
3. What are normal business hours for the client staff? Are overtime hours allowed, and if so
are they willing to work them?
<answer>
4. Are there any specific client staffing issues, such as a mandatory shutdown for inventory
counting or maternity leave?
<answer>
5. Are there third-party consulting staff that the client would like assigned to the Oracle
upgrade project? If so, when will they be available and for how long? What are their
skill sets? What are their billing rates?
<answer>
6. If third-party software will be affected and the project requires third-party vendor staff to be
involved, what staffing commitments will have to be made, and who are the contacts for
discussing this issue?
<answer>
Testing [d.]
The testing approach can significantly influence the calendar time and resource cost for upgrade
projects.
1. What client resources will be provided for testing, and what are their skill areas?
<answer>
2. Are there any existing site documented test scenarios that should be used, or will the upgrade
team need to create them?
<answer>
3. How many test upgrade cycles would the client like performed prior to the production
upgrade?
<answer>
4. Will it be necessary to perform a User Acceptance Test of the production environment before
using/accepting the system?
<answer>
5. Is there sufficient hardware capacity to perform test upgrades, such as disk space for test
environments and CPU capacity for executing tests?
<answer>
6. Will internal or external auditors be involved in review or certification of the test plans and
test results? Have these individuals been notified or scheduled?
<answer>
7. Will testing software be used to automate portions of the testing process? If yes, which
software tool will be used?
<answer>
Project Management [e.]

The project management approach can greatly influence the risk associated with achieving
project objectives, including the schedule and cost objectives.
1. Who is responsible for creating and updating the project plan?
<answer>
2. What method will the project plan be based upon?
Suggestion: Oracle recommends using the EasiPath Migration Method.
<answer>
3. How will project management report to executive management? For example, will there be
an executive steering committee and a project sponsor?
<answer>
4. How will the project library be managed?
<answer>
5. How will custom software be controlled? What configuration management system is used?
<answer>
6. What existing custom coding standards are to be followed for custom extensions?
<answer>
7. How will project acceptance occur? Who will officially accept the upgrade?
<answer>
8. What requirements are there for project personnel time recording, including both internal
and external resources?
<answer>
Business Process Change [f.]

Including business process changes in the upgrade project scope can have a major impact on
calendar time, resources, risk, and project complexity.
Oracle usually recommends that discretionary business process changes be made after the Oracle
Applications upgrade is complete. This will reduce project risk, complexity, and cost. Non-
discretionary business process changes may be required due to functionality changes in the new
Oracle Applications release.
1. What specific business process changes must be made as part of the upgrade project?
<answer>
2. Have these changes been scrutinized to ensure they cannot be postponed until after the
upgrade?
<answer>
Implementation of New Features [g.]

Upgrading Oracle Applications does not always require implementing new functionality. Key
individuals within the enterprise may want to implement unused functions in the current release
or new functions in the new release as part of the upgrade project. This can add substantial time
and cost to the project. Oracle usually recommends postponing implementing new functionality
until after the upgrade.
1. Generally, implementation of new features:
• will occur if required as part of the upgrade

• will occur with support of a business case and Senior Management approval
• will freely occur as part of the upgrade project as driven by business benefits
2. Are there specific plans to implement new Oracle Applications features as part of the
upgrade project? If so, what features in particular:
<answer>
Implementation of New Modules [h.]

Often it may be advantageous to implement a new Oracle Application module to replace an
existing legacy application and associated integration points into the Oracle Applications
environment. An example may be the replacement of an in-house project accounting application,
and its interfaces with the Oracle Project Accounting module. The diagram below show this
possible scenario.
Current Release Environment New Release Environment
Oracle Applications Oracle Applications
ENG ENG
OE AR OE AR
BOM INV GL BOM INV GL
PA
MRP MRP
WIP WIP
PO AP
PO AP
COST COST
Legacy
Project
Accounting
1. Are there any plans to implement additional Oracle Applications modules as part of the
upgrade?
<answer>
2. If so, which application products are considered, and what are the business reasons for
wanting to implement those applications?
<answer>
Suggestion: If the site requires the implementation of additional Oracle Application Modules, then
you need to use those tools supporting an AIM module implementation to estimate the amount of
effort to implement the new module.
Technical Architecture Changes [i.]

The goals of the upgrade project may include technical architecture changes. This can add
substantial calendar time, risk, and cost to the upgrade project.
Suggestion: Oracle usually recommends postponing discretionary architectural changes until after the
applications upgrade. Such changes could include migrating the user interface from character to Smart Client
(SC), character to Network Computing Architecture (NCA), or SC to NCA. Implementing the Oracle Parallel
Server option may also be a consideration.
1. Are there plans to include technical architecture changes in the scope of the upgrade project?
If so, Generally, changes to technical architecture:
• will occur if required as part of the upgrade

• will occur with support of a business case and senior management approval
• will freely occur as part of the upgrade project as driven by business needs and expected
benefits
2. Are there specific plans to implement technical architecture changes as part of the upgrade
project? If so, what changes in particular?
<answer>
3. What technical architecture changes should be made as part of the upgrade project?
<answer>
Changes to Applications Architecture (Multi-Org) [j.]
With release 10.6, Oracle introduced the capability to support multiple operating organizations
within the same installation using Multi-Org.
Prior to this feature being introduced, many organizations achieved similar capabilities by
installing several installations of an Oracle sub-ledger application such as Payables or
Purchasing, linking them to a single installation of General Ledger. In some situations, multiple
installations of General Ledger may have been established.
Warning: An upgrade project of this nature is quite complex, and Oracle strongly recommends that customers
do not attempt this without this assistance of Oracle Consulting. This type of project would require the direct
updating of internal Oracle data structures, and Oracle does not recommend the direct updating of internal data
structures.
Although there is no direct, automated upgrade capability available to these sites, there may be
intent to take advantage of the Multi-Org capabilities via an upgrade by establishing new
environments, and undertaking a complex, scripted data migration.
Suggestion: For those sites contemplating a Multi-Install to Multi-Org transition, Oracle has developed a tool
kit to assist with this process. This tool kit is of a very technical nature and use of it requires very specialized,
and experienced resources. For these reasons, the use of the tool kit is limited to use by Oracle Consulting. If
the upgrade project involves contract resources other than Oracle Consulting, Oracle recommends that the
project explore the use of the this kit with Oracle Consulting. As a very limited number of customers will be
executing this one-time activity, Oracle does not plan to release this kit beyond Oracle Consulting.
To understand if any activity is planned in this area, please complete the following where
appropriate:
The four most common types of upgrades involving multiple Sets of Books (SOBs) are shown
below:
• A single set of books environment will be upgraded to a Multi-Org environment.

Oracle Apps Release 10.4 Oracle Apps Release 10.7
ENG
ENG
OE AR
OE AR
INV GL
BOM GL
BOM INV
MRP IO
SOB SOB
MRP IO
WIP
PO AP WIP PO AP
COST
COST
In the diagram above, the Current Release Environment has 1 Set of Books (SOB) in
General Ledger and 1 Inventory Organizations (IO) in Inventory. In addition, the
subledger products (OE, AR, PO, and AP) are only installed once.
In the New Release Environment, there is still 1 SOB in GL and 1 IO in Inventory.
However, 1 Multi-Org Operating Unit (represented by a circle) has been set up to allow
the subledger products (OE,AR,PO and AP) to capture transactions by the default
Operating Unit (ORG_ID).
• Multiple install environment will be upgraded to a Multi-Org environment.

Oracle Apps (Release 10.4 ) Oracle Apps (Release 11)
ENG OE-2 AR-2 ENG

OE-1 AR-1 OE AR
INV-2
BOM INV-1 GL BOM INV GL
SOB1 SOB1
IO1
MRP MRP
SOB2 IO2 SOB2

PO-2 AP-2
WIP WIP
PO-1 AP-1 AP
PO
COST COST
In the diagram above, the Current Release Environment has one install of General
Ledger with 2 Sets of Books (SOBs). Because there are multiple sets of books in GL,
there are multiple installs of the Inventory, OE, AR, PO, and AP modules.
In the New Release Environment, the Multi-Org features will be used. Therefore, there
is only one install of the Oracle Applications modules. There are 2 SOBs in GL and 2
Inventory Organizations (IOs) in Inventory. There are 2 Operating Units (represented
by circles) in each of the subledger modules. Each Operating Unit captures transactions
for a specific organization (Org_ID).
• Multiple install environment will be upgraded to a Multiple install environment.

Oracle Apps (Release 10.4) Oracle Apps (Release 10.7)
ENG ENG OE-2 AR-2

OE-2 AR-2
OE-1 AR-1 INV-2 OE-1 AR-1
INV-2
GL BOM GL
BOM INV-1 INV-1
SOB1 SOB1
MRP MRP
SOB2
PO-2 AP-2
SOB2 PO-2 AP-2
WIP WIP
PO-1 AP-1 PO-1 AP-1
COST COST
In the diagram above, the Current Release Environment has one install of General
Ledger with 2 Sets of Books (SOBs). Because there are multiple sets of books in GL,
there are multiple installs of the Inventory, OE, AR, PO, and AP modules.
The architecture employed in the New Release Environment will be the same as the
architecture employed in the existing environment. One install of GL with 2 Sets of
Books (SOBs) and multiple installs of the sub-ledgers.
• Multiple production environments will converge into a single Multi-Org production

environment.
Current Release Environments New Release Environment
Oracle Apps (Release 10.4 )
Oracle Apps (Release 11)

ENG
OE AR
GL ENG
BOM INV
OE AR
IO1
MRP SOB1
BOM INV GL
WIP PO AP IO1 SOB1
MRP
COST
SOB2
IO2
WIP
PO AP
Oracle Apps (Release 10.5)
COST
ENG
OE AR
INV GL
BOM
IO2
MRP SOB2
WIP PO AP
COST
In the diagram above, there are two separate production Current Release Environments. Each
environment has one has 1 Set of Books (SOB) in General Ledger and 1 Inventory
Organizations (IO) in Inventory. In addition, the subledger products (OE, AR, PO, and AP)
are only installed once within the production environment.
In the New Release Environment, the Multi-Org features will be used. Therefore, there is
only 1 production environment and 1 install of the Oracle Applications modules. There are
2 SOBs in GL and 2 Inventory Organizations (IOs) in Inventory. There are 2 Operating
Units (represented by circles) in each of the subledger modules. Each Operating Unit
captures transactions for a specific organization (Org_ID).
1. How will Multi-Org affect the Application Architecture for this upgrade?
<Answer>
Multiple Reporting Currencies requirements [m.]

Although assumed by many to be a pan-European issue, many companies outside of the
European Union will require Multiple Reporting Currencies (MRC) support for their European
operations. For European sites, support for MRC is critical.
1. Will there be a need to address MRC requirements during the upgrade?
<answer>
Support for the Euro Common Currency [n.]

Similar in nature to the MRC issue, support for the Euro is often seen as a European issue.
Again, support for the Euro may be required for many non-European companies.
1. Will there be a need to address Euro Currency requirements during the upgrade?
<answer>
Audit Requirements [o.]
There may be a requirement to audit the upgrade project. If so, time should be budgeted for
project team staff to support this activity.
1. Is there a requirement for the project to be audited? If so, how much project team staff
should be budgeted to support the audit?
<answer>
Project Communications [p.]

Oracle Application environments may be located in countries with different native languages. It
may be important for some, or all, project team members to be fluent in the native language
associated with each upgrade team’s physical location. Alternatively, it may be possible to agree
upon one language for team communication. In some cases, translation services may be
required.
1. Are there any language issues potentially requiring project personnel fluent in certain
languages or requiring translation services?
<answer>
Language Support (NLS) [q.]

Oracle Applications software supports the installation of any one of many languages.
1. Please identify your language requirements for each of these elements:

• Forms, boilerplate text
• Reports
• Database messages, operating system messages, and on-line help text
• Navigation data such as menus and responsibilities
• Lookup data such as SO_LOOKUPS
• Master data such as Inventory Items and Chart of Accounts descriptions
• Transactional data such as Sales Orders or Purchase Orders
Warning: The installation of more than one simultaneous language in an environment requires the
installation of the Oracle Consulting Multi Language Support (MLS) option. As of Release 11.1, this
option is only available from Oracle Consulting. For more information contact
ace_admin@us.oracle.com.
<answer>
2. When will language translations be available in your language for the new release?
<answer>
3. Is the Oracle Consulting MLS solution installed in this environment?
<answer>
Physical Location(s) of Project Team(s) [r.]

Determine where the project team will be physically located.
1. Where will the upgrade project team(s) be physically located?
<answer>
2. Will this location(s) provide efficient access to key client personnel? Will travel be required
when project team and enterprise staff must be at the same location?
<answer>
Network Considerations [s.]

1. If a client/server environment is being employed, is there a stable network to allow
continuation of work during brown outages?
1. <answer>
2. III . Current Systems Infrastructure
Answer the questions below which describe the current systems infrastructure to be upgraded. Since there may be more than one Oracle
Applications environment to be upgraded, this section contains one subsection with common questions for all Oracle Application
environments, followed by a section to be completed for each Oracle Application environment.
A separate subsection of this questionnaire is provided for the following elements of an Oracle Applications environment:
• Common for All Environments - characteristics applying to all three possible architectural layers bulleted below
• Master Database Layer - the layer containing the Oracle database which will include one CPU unless the Parallel Server
option is used where there will be at least two CPUs
• Applications Server Layer - One or more CPUs running Oracle Application Server communicating with the Master Database
layer for database access and Client devices for user interface processing
• Client Device Layer - At least one client device such as a PC or NC communicating with the Applications Server layer
407231.doc Copyright © 1998, Oracle Corporation Oracle Applications Environment - [B.] 22

Common for All Environments [A.]
Record answers to the following questions describing common elements for all Oracle Application Environments to be upgraded.
Oracle Applications Environments [a.]

Capturing information about all Oracle Application Environments to be upgraded is essential. Such environments may include different
sets of Oracle Application modules using different languages and currencies located in different countries. Be sure to identify
dependencies among these environments which could have a major impact on the upgrade project plan, particularly if a phased upgrade
approach is employed:
1. What Oracle Application environments are in use?
Application Physical Primary Contact Release User Interface: Technical Architecture (2-tier Dependencies on Other
Environment Name Location Name, Phone and (Character, SC, or character, 2-tier SC, 3-tier Application Environments
Email Address Browser) NCA)
EURO-PROD DB-Paris, Jar Dehooeekn 10.7 Character and Smart 2-tier SC EURO-TEST is a mirror on
Clients-Europe Client EURO-PROD, EURO-TRAIN
EURO-TEST DB-Paris Jar Dehooeekn 10.7 Character and Smart 2-tier SC
Clients-Europe Client
EURO-TRAIN DB-UK Jar Dehooeekn 10.7 Character and Smart 2-tier SC
Clients-World Client
Wide
Corporate Network [b.]

Accurate information about overall data communication networks utilized by Oracle Applications Environments is important to assess
upgrade project requirements.
1. What data communication networks are in use?
Network LAN/WAN Geographical Area Bandwidth Protocols Latency Contact Name, Oracle Application Note
Name Covered Phone, Email Environment
Address Supported

Support Infrastructure [c.]
Available support services must be identified as they may be leveraged by the upgrade team.
1. What support services would be provided to the Oracle Applications upgrade project team such as Database Administrator, Systems
Administration, computer operations, backup and recovery, and help desk?
<answer>
1. Is there a help desk where users can call with questions concerning Oracle Applications, networks, or other technical questions?
<answer>
2. Do you have remote dial-in capabilities so that Oracle Analysts can access the system(s) running Oracle Applications for diagnostic
purposes, or project team members can use dial-up networking to access Oracle systems?
<answer>
3. What production support staff exists, such as Database Administrator, Oracle Applications Systems Administrator, Network
Administrator, and computer operations personnel? What are the normal working hours for individuals performing these roles?
<answer>
4. Does the customer use Oracle MetaLink and if so, to what extent?
<answer>
5. How does the customer receive patches?
<answer>
6. How does the customer manage the application of patches to the environments?
<answer>

Oracle Applications Environment - [B.]
Record information about a specific Oracle Applications Environment in this section. If there are multiple Oracle Application
Environments, duplicate this section and answer the questions as appropriate for each environment. It is essential to treat each Oracle
Applications Environment separately when assessing upgrade requirements even if the client indicates they are identical. Experience has
shown that seemingly subtle differences can have major impacts on upgrade projects.
In this section we refer to the three architecture layers in Oracle Applications. The diagram below shows these three architecture layers.
The diagram also shows three user interfaces that can be used to access Oracle Applications. The following list gives an explanation of
the diagram for each user interface:
• Character User Interface - The Oracle Database, Oracle Applications software, and the terminal (or PC with terminal emulation)
all reside at the Master Database Layer.
• SmartClient User Interface - The Oracle Database and Oracle Applications software reside on the Master Database Layer. The
Client Side Oracle Applications reside in a PC at the Client Device Layer.
• NCA User Interface - The Oracle Database resides at the Master Database Layer. The Oracle Applications software and the
Oracle Applications Server reside at the Applications Server Layer. An NC (or PC with a browser) resides at the Client
Device Layer.

3 Architecture Layers For Oracle Applications
Character SmartClient NCA

User Interface User Interface User Interface
Oracle Oracle Oracle Oracle

Oracle Database
Database Applications Database
Applications
(Server Side)
Software
Master Database
Layer CPU
CPU CPU
CPU CPU CPU
Oracle
Applications
Server
Applications Server
Layer CPU
CPU
Client Device Oracle

Terminal PC
Layer Applications PC w/
or Oracle Apps
Software Browser
PC (Client Side)
Oracle Application Modules [a.]

Answer the following questions concerning the Oracle Application modules installed in this environment. Oracle Application
software will only be present at the Master Database Layer for Character and Smart Client implementations. Oracle Application
software runs on the Application Server Layer for NCA and Web Applications configurations.
Attention: Note that Character, Smart Client, and NCA can coexist depending on the release version. See the table below for specifics:
Release Character SmartClient NCA Character Charter

& SmartClient SmartClient & NCA
Prior to 10.6 Yes No No No No

10.6 Yes Yes No Yes No
10.7 Yes Yes Yes Yes Yes (GL NCA only)
11 No No Yes No No

The table above shows the various user interface options that are available. An explanation of these options for each release is listed
below:
• Prior to 10.7 the user interface options are Character, SmartClient, and a combination of Character and SmartClient.
• With release10.7 the user interface options are Character, SmartClient, and NCA. In addition, you can combine Character with
SmartClient, Character with NCA, or Character and SmartClient with NCA (GL only).
• With release 11 the user interface option is NCA.
1. Complete the following tables to identify the current Oracle Applications software in production:
Identifier/ Oracle Major Module Prod Number Patch Status # of Named # of Concurrent Users
Sequence Application Release Version Users
Module (SC only)
Sample-1 AOL 10.7 6.1.1 16.1 Current 114 35

Sample-2 GL 10.7 9.0.9 16.1 Current 114 6
Identifier/ Oracle User Tier: (Database Layer, Share Status - pre- Data Segregation Approach
Sequence Application Interface: Application Server 10.7: (Fully Installed (None, Multiple Installs, Multi-Org Feature)
Module (Character, Layer, Client Device or Shared)
SC, or Layer)
Browser)
Sample-1 AOL Char, SC DB, Client Installed None

Sample-2 GL Char, SC DB, Client Installed None
Identifier/ Oracle Planned Planned Planned Patch Level Goal # of # of

Sequence Application Major Module Prod Number (SC only) Named Concurrent
Module Release Version Users Users
Sample-1 AOL 11.1 TBD N/A Current 114 35

Sample-2 GL 11.1 TBD N/A Current 114 6

Identifier/ Oracle User Interface: Tier: (Database Layer, Multi-Org Plans Comments
Sequence Application (Character, SC, or Application Server Layer,
Module Browser) Client Device Layer)
Sample-1 AOL Browser DB, AS, Client None None

Sample-2 GL Browser DB, AS, Client None None
2. Is the intent to upgrade the multiple application installs and then consolidate to Multi-Org later, or is there a conversion plan? If so,
what is the plan?
<answer>
3. What globalizations/localizations are installed?
<answer>
4. How many Sets of Books are in use?
<answer>
5. What languages are installed?
<answer>
Customizations [b.]
Identify, at a high-level, each of the customizations that currently exist for this environment. There are specific relationships between
these high-level customizations and specific code and database objects identified in detail at the specific level.
1. What high-level customizations currently exist for this environment?
Identifier / Name/Function of extension Master Application Client Device Specification/ Is the Comments
Sequence Database Server Layer Documentation documentation
Layer Layer current?
EXT-02 Work Order Validation YES NO NO $CPO_TOP/install/do Supports on-line validation of

c/EXT-02.doc maintenance work order
numbers on PO lines and
associated AP Invoice Lines
EXT-09 Auto-Pay/Pay on Receipt YES NO N/NO $CPO_TOP/install/do Supports auto generation of
c/EXT-09.doc invoices for payment
processing for vendors that
have the ‘Auto-Pay’ attribute.
Likely eclipsed by new
Identifier / Name/Function of extension Master Application Client Device Specification/ Is the Comments
Sequence Database Server Layer Documentation documentation
Layer Layer current?
application functionality
EXT-04 Performance Variance Calculator YES NO NO $CPO_TOP/install/do Supports vendor commit to
c/EXT-04.doc ship performance evaluation
Current Data Condition [c.]

A frequently overlooked potential problem area is the condition of data. Maintenance activities since the initial Oracle Applications
implementation may have resulted in customizations with bugs, allowing incorrect data to be entered. Hopefully, no direct (SQL)
updates to production data outside of the Oracle Applications have occurred which may have introduced corrupt data.
Oracle’s AutoInstall utility will often not allow incorrect data to be migrated to the new production environment and will produce error
reports. Substantial time and resources could be required to correct such production data errors.
1. What is the condition of existing production data to be migrated to the new production environment?
<answer>
2. Should current production data be analyzed to ensure accuracy before the production upgrade? If so, will this be within the upgrade
project scope?
<answer>
Current Documentation Status [d.]

Documentation concerning the existing environment can be leveraged by the upgrade team, potentially reducing the time and resources
needed.
1. Is there documentation for the current Oracle Application setups? If so what is included?
<answer>
2. Is there procedure level documentation for the user? If so, what does it include?
<answer>
3. Does current customization documentation exist? What does it include?
<answer>

4. Are test scripts (specific to existing customizations, interfaces), which could be used for testing modified customizations to be
migrated, available? What is included?
• <answer>
Configuration - General [e.]

Answer the following questions pertaining to all three possible architectural layers:
1. Is this application environment OFA (Optimal Flexible Architecture) compliant? If not, what conventions have been used to ensure
a consistent, stable easy to maintain Oracle Applications Environment?
<answer>
2. If necessary, is it acceptable to create an environment which does not meet your non-OFA compliant standards during the
applications upgrade?
<answer>
Backup and Recovery Support [f.]

1. What backup and recovery policies, facilities, and procedures are in place at this time, or would be developed to support the project?
<answer>
2. When was the last time a recovery was successfully done?
<answer>
3. When was the last cold backup taken?
<answer>
4. When was the last hot backup taken?
<answer>

Required Non-Oracle Applications Software Upgrades [g.]
Third party software interfacing with Oracle software may be incompatible with the new Oracle Applications release. Other Oracle
database and operating systems may need to be upgraded. Such issues must be evaluated and addressed in the upgrade plan.
1. Will the Oracle Applications upgrade require an Operating System upgrade? If so, to what release?
<answer>
2. Will the Oracle Applications upgrade require an Oracle database upgrade? If so, to what release?
<answer>
3. Will any third party application software require upgrades due to the Oracle Applications upgrade? If so, to what release?
<answer>
Environment Synchronization [h.]

Usually, separate instances are maintained for Oracle Applications environments such as Production, Test, and Training. Normally, the
non-production instances are refreshed from the newly upgraded production instance so that all of them are running the upgraded
applications with migrated customizations (if any) and are synchronized going forward.
In some cases, investments may have been made to develop sophisticated training or test data which would be overwritten if refreshed
from the new production instance. If unique aspects of a non-production instance must be migrated, that instance may require a separate
upgrade so that the overall upgrade for the associated Oracle Application Environment could include multiple upgrades. Since this
approach will substantially increase the cost and resources required, it is seldom used.
1. What non-production instances of the Oracle Applications and database are maintained for this Oracle Applications Environment
(examples would be development, test, training)?
<answer>
2. Is it acceptable to refresh the non-production instances by copying the upgraded production instance or are there unique
customizations or data which need to be maintained after the production upgrade?
<answer>
Printers [i.]
Printers represent a frequent stumbling block during upgrades (particularly if changes have been made to standard definitions).
1. Are there standard system printers?
<answer>
2. Have changes been made to the standard print definitions?

<answer>
3. Do any printers directly attach to Oracle Application client devices?
<answer>
4. If modified printer description files exist, where are they being used by the Oracle Applications?
<answer>
Master Database Layer [C.]

The following questions address the Master Database Layer for this Oracle Applications Environment. This layer includes one CPU if
the Oracle Parallel Server option is not in use or more than one if it is being used.
In this section the questions relate to the Master Database Layer. The diagram below shows the Master Database Layer and each of the
system components by user interface. There are three user interfaces for Oracle Applications. The following list shows the system
components for each user interface:
• Character User Interface - The Oracle Database, Oracle Applications software, and the terminal (or PC with terminal emulation)
all reside at the Master Database Layer.
• SmartClient User Interface - The Oracle Database and Oracle Applications software reside on the Master Database Layer.
• NCA User Interface - Only the Oracle Database resides at the Master Database Layer.

Master Database Layer
Character User Interface SmartClient User Interface NCA User Interface
Oracle Oracle Oracle Oracle

Oracle Database Database
Database Applications
Applications
(Server Side)
Software
CPU CPU
CPU
CPU CPU CPU
Hardware [a.]
Record answers to the following questions concerning the hardware used at the Master Database Layer.
1. What are the make, model, memory, number of CPU’s, and their options (e.g., speed and cache) for the database server?
<answer>
2. What is the total disk space and the amount of disk space available for the upgrade?
<answer>
3. Is the test environment that the project team will be using to perform the test upgrade the same as the current production
environment? For example, the production upgrade O/S is version 10.2 and the test upgrade O/S is version 11, or there are 10 CPU’s
with 2Gigs of memory on the production server and 2 CPU’s with 1Gig of memory on the test server
<answer>
Operating System [b.]

Capture the characteristics of the operating system in use at the Master Database Layer. If the Parallel Server Option is used, the same
operating system and version must be running on each CPU sharing the Oracle database.
1. What operating system and version is in use?
<answer>
2. For UNIX operating systems, what Shell is in use for the Oracle Database account owner?
<answer>
3. What text editor is in use to develop and maintain shell scripts?
<answer>
4. Does the site use raw or file system organized disks?

<answer>
5. Are there any optimization techniques in place? (i.e. stripping, mirroring)
<answer>
Oracle Database Server [c.]

Answer the following question about the Oracle Database Server installed on the Master Database Layer.
1. What release of the Oracle Server release is installed on this layer?
<answer>
2. What is the Oracle Server patch status?
<answer>
3. Is the Oracle Parallel Server option being used?
<answer>
4. Is replication being used? If so, how many distributed replication databases are in use?
<answer>
5. Is the National Language option being used? If so, what languages are in use?
<answer>
6. Are there plans for upgrading the database server, aside from the applications upgrade project? If so, what is the new version and
when are the plans to upgrade?
7. What is the current size of the production database?
• Under 10 GB
• Between 10 and 30 GB
• Between 30 and 50 GB
• Over 50 GB
1. Where are the database log files stored?
<answer>
2. Is Multiple Language System Support being used? If so, what languages are being used?
<answer>
Third-Party Software Installed [d.]

Document characteristics of third-party software running at this layer.
1. What third-party software is installed at the Master Database Level?
<answer>
2. If third party software is being used, what are the dependencies between it and Oracle software that should be considered during the
Oracle Applications upgrade?
<answer>
3. What server management tools are in use at this time? Are they compatible with planned upgrades to the Oracle Server
environment?
<answer>
Interfaces [e.]
Upgrade activities may be required regarding interfaces between Oracle Applications and other applications. Interfaces may use Oracle
application tables which may change from release to release. Ensure any interfaces and related custom applications developed using
Oracle tools are identified along with the version of Oracle tools employed.
1. What interfaces between Oracle Applications and other applications exist?
Identifier / Source System/Applications Destination Content Hot or Frequency Volume (Ave Standard Technical
Sequence System/ Batch (e.g., Daily, # of records Oracle Environment
Application Monthly) or Interface API
transactions
INT-01 Lease Management (MVS/TSO) Oracle-AP AP Invoices Batch Nightly 300/night No SQL*Loader, SQL/Plus
INT-02 Costing (ISIS) Oracle-GL GL Journals Batch Nightly 45,000/night Yes, GLJE SQL*Loader

Identifier / Source System/Applications Destination Content Hot or Frequency Volume (Ave Standard Technical
Sequence System/ Batch (e.g., Daily, # of records Oracle Environment
Application Monthly) or Interface API
transactions
Identifier / DDL Code (Location and Name) Execution Code (Location and Century Date Century Date Migration Migration Notes
Sequence Name) Destination Source Complexity
Plan
INT-01 $CAP_TOP/install/sql/int01a.sql, $CAP_TOP/sql/int01.sql, Reviewed, OK Reviewed, OK Migrate VE Check to see if

$CAP_TOP/install/sql/int01b.sql $CAP_TOP/bin/int01.ldr tables have
changed
INT-02 N/A $CAP_TOP/bin/int02.ldr Reviewed, needs Reviewed, Migrate VE Code rework for
YYYY needs YYYY C/Date
Custom Extensions [f.]

Custom database server extensions at the Master Database Layer may include customized Oracle Application tables for Character, Smart
Client, or NCA environments. Character Mode and SmartClient implementations may also include custom reports, Alerts, Workflows or
menus at this layer. Custom forms (screens) may also exist at this layer only for Character Mode implementations.
Answer the following questions to obtain key characteristics of such customizations.
1. What custom database server objects exist at the Master Database Layer?
Identifier / Object Name Type Schema DDL Code Description

Sequence - Schema, Table
- Synonym, View
- Grants, Profile
- Sequences
EXT-02/ DSO.001 CUST SCHEMA CUST $CFND_TOP/inst Schema for customer’s custom
all/sql/cust_schem extensions and database objects
.sql
EXT-02/ DSO.002 MAINTENANCE_WORK_ORDERS TABLE CUST $CPO_TOP/instal Create Script for Maintenance Work
l/sql/mwo.sql Orders Table
EXT-02/ DSO.003 MAINTENANCE_WORK_ORDERS GRANT (Select) to PO, FND $CPO_TOP/instal Create Script for Maintenance Work
l/sql/mwo.sql Orders Table

Identifier / Century Date Migration Oracle Notes
Sequence Complexity Standards
(VE, E, M, C) Used
EXT-02/ DSO.001 N/A VE

EXT-02/ DSO.002 To be reviewed VE Check format of any date columns during project
EXT-02/ DSO.003 N/A VE Strip out grants portion of $CPO_TOP/install/sql/mwo.sql into new script so that it can
be rerun anytime grants are lost
2. If any of the standard (as-shipped) Oracle Applications database objects (tables, grants, etc.) have been changed, data may be lost
during the upgrade or the applications may not function correctly following upgrade. Identify the changes made to the Oracle
Application tables below:
Warning: Oracle does not support changing Applications tables.
Identifier / Object Name Type Schema DDL Code Description of change from what was installed as
Sequence - Schema, Table (Alter Object Script) shipped
- Synonym, View
- Grants, Profile
- Sequences
EXT-09/ DSSO.001 PO_VENDORS TABLE CUST $CPO_TOP/install/sql/m Additional column added ‘AUTO_PAY’ char(1) to
wo.sql support auto invoice generation on receipt
EXT-09/ DSSO.002 PO_VENDORS GRANT (Select) to CUST $CPO_TOP/install/sql/m Grant script
wo.sql
Identifier / Century Date Migration Notes/Plan

Sequence Complexity
(VE, E, M, C)
EXT-09/ DSSO.001 Reviewed, OK C Review/Migration to new functionality in this area and retire extension and modification to standard table.
AutoInstall will note extra column on upgrade - ignore. Related to extension: EXT-005.
EXT-09/ DSSO.002 N/A VE Review/Migration to new functionality in this area and retire extension and modification to standard table.
Identifier / Century Date Migration Notes/Plan
Sequence Complexity
(VE, E, M, C)
AutoInstall will note extra column on upgrade - ignore. Related to extension: EXT-005.
3. What custom database server extensions (triggers, packages/procedures) exist at the Master Database Layer?
Identify if any custom PL/SQL packages/procedures that have been developed which alter or add functionality (list package name,
purpose, intent to migrate the package, whether Date manipulation code is included and its Century Date compliance status, file
location as well as a reference to documentation if available).
Identifier / Name/Function of extension Schema Type Table(s) On-Action DDL Code

Sequence - Package (Triggers) (Triggers)
- Trigger
EXT-02/ TRG.001 Work Order Validation Trigger PO Trigger PO_LINES Insert, $CPO_TOP/install/sql/ext01.sql
Update
EXT-02/ PKG.004 Work Order Validation Package PO Package N/A N/A $CPO_TOP/install/sql/ext02.sql
Identifier / Century Date Migration Migration Notes

Sequence Plan Complexity
EXT-02/ TRG.001 Reviewed, OK Migrate Low Check to see if tables have changed
EXT-02/ PKG.004 Reviewed, OK Migrate Low Check to see if tables have changed
4. What standard (as-shipped) database server extensions (triggers, packages/procedures) have been altered at the Master Database
Layer?
Identify if any standard (as-shipped) PL/SQL packages/procedures or triggers have been altered which alter or add functionality (list
package name, purpose, intent to migrate the package, whether Date manipulation code is included and its Century Date compliance
status, file location, as well as a reference to documentation if available).

Identifier / Name/Function of extension Schema Type Table(s) On-Action DDL Code
Sequence - Package (Triggers) (Triggers)
- Trigger
EXT-07/ TRG.002 POP_CMERGE_REQ - PO Package PO_REQUSITI N/A Orig:$PO_TOP/install/sql/pocmerge.pkb

Customer Merge Package for PO ON_LINES, Cust: $CPO_TOP/install/sql/pocmerge.pkb
PO_LOCATIO
N_ASSOCIATI
ONS,
Identifier / Century Date Migratio Migration Notes

Sequence n Complexity
Plan
EXT-07/ TRG.002 Reviewed, OK Migrate Low Check to see if tables have changed
7. If ‘C’ code has been developed or customized, is there a C compiler installed? If so, what version?
<answer>
8.
Suggestion: If the parallel server option is being used, provide this for each CPU.
6. Identify any ‘C’ code that has been added to the Master Database Layer:
9.
Identifier / Name/Function of extension Libraries Used ‘C’ Source Code Make file
Sequence
EXT-04/ VARCAL Performance Variance Calculator lib.a, onx, varc $CPO_TOP/install/bin/ $CPO_TOP/install/bin/VARCAL.mk
EXT04.src

Identifier / ‘C’ Executable Century Migration Migration Notes
Sequence Date Complexity
Plan
EXT-04/ VARCAL $CPO_TOP/bin/VARCAL Not Migrate High Check to see if tables have changed
Compliant
10.
11. Identify any ‘C’ code that has been modified from standard (‘as-shipped’) code at the Master Server Layer:
Attention: Oracle does not normally release ‘C’ source. However, some sites may request source for specific requirements.
12.
Identifier / Name/Function of extension libraries used ‘C’ Source Code Make file
Sequence
EXT-05/ RTP Online RCV Transaction Manager (Online rcvoltm.o, Orig: $CPO_TOP/PO/lib/CPO.mk
Advise for high-priority receipt of $(APPL_LIBS), $PO_TOP/lib/rcvoltm.c
maintenance materials) ${LFNDLIB) Cust:
$CPO_TOP/lib/ccvoltm.
c
Identifier / ‘C’ Executable Century Migration Migration Notes

Sequence Date Complexity
Plan
EXT-05/ RTP $CPO_TOP/bin/CCVOLTM linked to Compliant Migrate Medium Check to see if ‘c’ source has changed
$PO_TOP/bin/RCVOLTM
8. If modifications to standard (Oracle shipped) Forms 2.3 screens (character mode only at the Master Database Layer) have been
made, provide the Oracle Application module name, form name, a brief summary of the changes, intent to migrate the extension,
whether date logic was added or changed and its Century Date compliance status, file location, as well as a reference to
documentation if available.

Identifier / Form Long Name Ship Form Name, Code Path Modified Form Name, Code Path Comments
Sequence
EXT-02/APXINMSI Enter Invoices $AP_TOP/forms/APXINMSI.inp $CAP_TOP/forms/APCXINMSI.inp

EXT-02/POXPIMSI Enter Purchase Orders $PO_TOP/forms/POXPIMSI.inp $PO_TOP/forms/POXPIMSI.inp
EXT-09/ APXVDMVD Enter Vendors $AP_TOP/forms/APXVDMVD.inp $CAP_TOP/forms/APXVDMVD.inp

EXT-02/APXINMSI Reviewed Migrate to NCA, Very Complex Check to see if tables have changed
custom code, Reapply
OK customizations to
latest version of
form
EXT-02/POXPIMSI Reviewed Migrate to NCA, Very Complex Check to see if tables have changed, Also .. this form is in the wrong code path. Should be
custom code, Reapply in the CPO_TOP code path and executed from there. Will need to download the current
OK customizations to non-customized (‘as-shipped) source for final Century date review through Ravel tool.
latest version of
form
EXT-09/ APXVDMVD To be May eliminate as TBD May no longer be required due to new feature introduced in latest release
Reviewed eclipsed
Detailed Century date review statistics from the Unravel/2000 tool:
Identifier / # of # of # of # of # of # of # of Date # of # LOC Total Notes

Sequence Base Control Fields Triggers Triggers SQL Variables Related with LOC
Table Blocks with Date Lines Date Date
Blocks Ref. Variables Ref
EXT-02/APXINMSI 3 1 132 37 22 345 35 23 17

EXT-02/POXPIMSI 4 1 145 56 12 735 53 22 33
EXT-09/ APXVDMVD 6 1 167 54 34 105 24 34 23
9. If new Forms 2.3 forms (character mode only for the Master Database Layer) have been developed, please provide form name,
purpose, intent to migrate the new form, whether date related code is present and its Century Date compliance status, file location,
as well as a reference to documentation if available.
Identifier / Form Long Name New Form Name, Code Path Comments
Sequence

Identifier / Form Long Name New Form Name, Code Path Comments
Sequence

Detailed Century date review statistics from the Unravel/2000 tool:
Identifier / # of # of # of # of # of # of # of Date # of # LOC Total Notes

Sequence Base Control Fields Triggers Triggers SQL Variables Related with LOC
Table Blocks with Date Lines Date Date
Blocks Ref. Variables Ref
13. If RPT reports have been modified, please complete the information below:
Note: RPT was last used in Release 10.7 of the Oracle Applications. In the 10.7 release, very few of the standard ‘as-shipped’ reports were written in RPT.
14.
Report File Path Description of Report Migrate # of # of Date # of # of LOC Total Note
Name Name (Y or N) SQL Variables Related with Date LOC
Lines Date Ref.
Variables

15. If RPT new reports have been created, please complete the information below:
16.
Lines Date Ref.
Variables
12. If SQL*Reportwriter programs have been modified, please provide program name, purpose, intent to migrate the report, whether
date related code is present and its Century Date compliance status file location, as well as a reference to documentation if available.
Note: SQL*Reportwriter (SRW) was last used in release 9.4.x of the Oracle Applications. With release 10.x, most reports were migrated to Oracle Reports 2.0
Module Name File Path Description of Module Migrate Date Century Date Doc Note
Name (Y or N) Code Compliance Ref.
Present (Y or N)
(Y or N)
13. If SQL*Reportwriter programs have been developed, please provide program name, purpose, intent to migrate the report, whether
date related code is present and its Century Date compliance status file location, as well as a reference to documentation if available.
Present (Y or N)
(Y or N)

14. If Reports2.0 programs have been modified, please complete the information below:
Note: Oracle Reports 2.0 was first supported with the early release 10.x versions of the Oracle Applications.
Present (Y or N)
(Y or N)
15. If Reports2.0 programs have been developed, please complete the information below:
Present (Y or N)
(Y or N)
17. If Reports 2.5/3.0 reports have been modified, please complete the information below:
18.
Lines Date Ref.
Variables
19. If new Reports 2.5/3.0 reports have been created, please complete the information below:
20.

Lines Date Ref.
Variables
21. If Reports 4.0 are in use, please complete the information below:
22.
Lines Date Ref.
Variables
23. If any SQL or PL/SQL code exists for execution by Concurrent Management or other initiating processes, list it below:
Suggestion: This would not include any code that exists in the server as a PL/SQL Package or Procedure. This would be code that is
executed via the SQL or PL/SQL parser.
24.
Package Body Path Description Migrate # of # of Date # of # of LOC Total Note

Name Name(s) (Y or N) SQL Variables Related with Date LOC
Lines Date Ref.
Variables
25. Have any operating system Shell scripts been developed?

26.

Script Name File Name Path Description of File LOC LOC # of Date Migrate Doc Ref. Note
Script Type with Fields (Y or N)
Date
Ref

Applications Server Layer (NCA only) [D.]
The Applications Server Layer is the second tier in an NCA install where Oracle Applications software is installed.
In this section, the questions relate to the Applications Sever Layer. The diagram below shows the Applications Server Layer and each of
the system components by user interface. There are three user interfaces for Oracle Applications. The following list shows the system
components for each user interface:
• Character User Interface - No system components reside at the Applications Server Layer.
• SmartClient User Interface - No system components reside at the Applications Server Layer.
• NCA User Interface - The Applications Server and Oracle Applications software reside at the Applications Server Layer. There
may be more than one CPU running the Oracle Applications Server.
Applications Server Layer

Oracle Oracle
Applications Applications
Software Server
CPU
CPU
Oracle Applications Server (NCA and WEB Deployed Applications Only) [a.]
The Oracle Applications Server runs on the CPU(s) associated with the Applications Server Layer for NCA and WEB Deployed
Application installations.
1. What Oracle Applications Server software release is in use?

<answer>
2. What is the Oracle Application Server patch status?
<answer>
Forms Listener [b.]

Oracle forms Listener software is required at the Applications Server Layer for NCA installs.
1. What Forms Listener release is in use?
<answer>
2. What is the Forms Listener patch status?
<answer>
3. What options, if any, are installed?
<answer>
Hardware [c.]
One or more CPUs may be needed to support the Applications Server Layer.
1. What are the make, model, memory, and options (e.g., speed and cache) for the CPU(s) used to support this layer?
<answer>
2. What is the total disk space and the amount of disk space available for the upgrade?
<answer>
Operating System [d.]

Document the operating system characteristics by providing the following information.
1. What operating system and version is in use? Is this version Century Data compliant?
<answer>
2. For UNIX operating systems, what Shell is in use (i.e., csh, ksh, or bsh)?
<answer>

3. Is an OS upgrade required for this Oracle Applications Upgrade? If so, what is the lead time and impacts? The latest compatibility
information can be found using the Oracle Worldwide Support MetaLink System.
Suggestion: For more information regarding MetaLink, contact your local Oracle Support representative.
<answer>
4. What text editor is in use to develop and maintain shell scripts? For example VI is used for UNIX and Notepad is used for
Windows/Intel based operating systems.
<answer>
Third-Party Software Installed [e.]

Third-party software may be installed on the CPU(s) in this layer which may require upgrades in order to be compatible with the new
Oracle Applications release.
1. Identify the third-party software package(s) and release(s) installed on each CPU that comprise the Applications Server Layer.
<answer>
2. If third-party software is being used, what are the dependencies between it and Oracle software that should be considered during the
Oracle Applications upgrade?
<answer>
Custom Extensions [f.]

Custom forms may exist at the Applications Server Layer for NCA installs while the custom tables or views would exist on the Master
Database Layer. Answer the following questions to obtain key characteristics of such customizations.
1. Identify the type and number of custom objects that have been developed.
Custom Object Type Total Client Preliminary Century Date Compliance Complexity Note
Assessment (VE, E, M, C)
Forms
2. Identify whether the Oracle Applications source code has been modified and where this source code is located.

<answer>
Custom Applications [g.]

Custom Oracle Applications may have been developed to meet business requirements that were not met by the Oracle Applications that
were initially implemented. Only the Forms of these applications would reside on the Applications Server Layer.
1. Identify if there are any custom applications that have been developed using Oracle tools.
Application Brief Built Development Migrate Century Access Standard Uses Oracle Doc Note
Name Description Using Tools Used (Y or N) Date Oracle Application Status
Oracle Compliant Applications API’s (List
Tools (Y (Y or N) Tables (C - API)
or N) Create, R - Read,
U - Update, D -
Delete or N - No)
2. Identify what the plans are to achieve Century Date compliance for these custom applications.
<answer>

Client Device Layer [E.]
The Client Device Layer is involved in a SmartClient install where client side Oracle Applications software is loaded on the PC. The
Client Device Layer is also the third tier in an NCA or Web Deployed Applications install where a browser, such as Netscape , is installed ™
to access the Oracle Applications that reside on the Applications Server Layer.
In this section, the questions relate to the Client Device Layer. The diagram below shows the Client Device Layer and each of the system
components by user interface. There are three user interfaces for Oracle Applications. The following list shows the system components
for each user interface:
• Character User Interface - No system components reside at the Client Device Layer. This tier does not exist for Character
installations.
• SmartClient User Interface - Client Side Oracle Applications software resides at the Client Device Layer. Client side Oracle
Applications software is loaded on each client device (PC). For SmartClient installations, the Client Device Layer contains the
Oracle Applications forms.
• NCA User Interface - a browser, such as Netscape , is installed at the Client Device Layer to access the Oracle Applications which
™
are running on the Applications Server Layer.
Client Device Layer

PC/Terminal Oracle PC
Applications PC w/
Char Mode Oracle Apps
Software Browser
(Client Side) (Client Side)
Terminal Emulation (Character mode Only) [a.]

1. What terminal emulation package is being used?
<answer>

Browser Version (NCA and Web Deployed Applications Only) [b.]
A browser is required at this layer for each client device. Although at this time the Oracle Applications are not certified to run any
specific browser, the applications can use them, provided they use a certified Java Development Kit (JDK).
1. What browser and version is installed on each client device?
<answer>
2. What JDK is currently being used?
<answer>
JVM Environment (NCA and Web Deployed Applications Only) [c.]

A Java Virtual Machine environment must exist on each client device.
1. What Java Virtual Machine and version is installed on each client device?
<answer>
Hardware [d.]
For either NCA or SmartClient installations, the number of PCs used at this layer depends on the number of seats the client has.
Character installations can use either a terminal or a PC with terminal emulation software. Capture the general hardware information in
use at the Client Device Layer.
1. Identify the general hardware configurations that comprise the Client Device Layer, such as the make, model, memory and options
for the CPUs employed.
<answer>
2. Generally speaking, what is the total disk space and the amount of disk space available for the upgrade on these devices?
<answer>
Operating System [e.]

The operating system and version installed on client devices should be determined.
1. What operating system and version is being run? Is this version Century Date compliant?
<answer>
2. Is an operating system upgrade required for this Oracle Applications Upgrade? If so, what is the lead time and impact?

<answer>
Third-party Software Installed [f.]

Third-party software may be installed on the client devices which could have an impact on the Oracle Application upgrade. Items that
could impact the Oracle Applications upgrade are related to software compatibility, memory space, and system performance.
1. In general terms, identify the third-party software and releases that have been installed on the CPUs that comprise this layer.
<answer>
2. Identify the dependencies between any third-party software products and Oracle software products that should be considered during
the Oracle Applications upgrade.
<answer>
Custom Extensions - (Smart Client only) [g.]

Customizations to Oracle Applications software can only occur at the Client Device Layer for SmartClient installs.
1. If modification to standard (Oracle shipped) Forms have been made, provide the Oracle Application module name, form name, a
brief summary of the changes, intent to migrate the extension, whether date logic was added or changed and its Century Date
compliance status, file location, as well as a reference to documentation if available.
Oracle Form Name Summary of Changes Intent to Date Logic C/Date Compliance Documentation Reference
Application Migrate Added or Status
Module Changed
2. If custom Forms have been made, provide the Oracle Application module name, form name, a brief summary of the changes, intent
to migrate the extension, whether date logic was added and its Century Date compliance status, file location, as well as a reference to
documentation if available.
Module Changed

Module Changed
3. Identify the most often used variable names for the date fields in the customizations.
<answer>
Custom Applications (Smart Client only) [h.]

In addition to customizations to Oracle Applications, an entire new custom application module may have been developed and interfaced
with Oracle Applications.
1. Identify if there are any custom application modules that have been developed using Oracle tools.
Application Brief Built Development Migrate Century Access Standard Uses Oracle Doc Note
Name Description Using Tools Used (Y or N) Date Oracle Application Status
Oracle Compliant Applications API’s (List
Tools (Y (Y or N) Tables (C - API)
or N) Create, R - Read,
U - Update, D -
Delete or N - No)
2. Identify what the plans are to achieve Century Date compliance for these custom applications.
<answer>

Issues
General
Open Issues
Issue Responsibility Identification Resolution Comments
Date Target Date
Closed Issues
Issue Responsibility Identification Resolution Comments
Date Target Date

11i Assessment Questionnaire

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

11i Assessment Questionnaire

Uploaded by

Copyright:

Available Formats

ORACLE APPLICATIONS

Author: AGSL - Methods/Tools

Copy Number _____

Date Author Version Change Reference

Copy No. Name Location

1 Library Master Project Library

Common for All Environments [A.]........................................................................................23

t ion Assessment & Test

Later during the Migration

Year 2000 and EMM

To conduct a Migration Discovery, follow the six steps listed below:

• Complete as much of the questionnaire by client personnel in advance of the arrival of

Use this document to:

• Help facilitate the Migration Discovery activity.

How This Document Is Structured

Overall Upgrade Project Information

Common For All Environments

Oracle Applications Environment

• explanations of why topics should be addressed

• Base Software Upgrade

Upgrade Project Constraints [a.]

1. When should the production upgrade be completed?

High-Level Project Scope [B.]

High-Level Upgrade Project Scope [a.]

Retrofit Misaligned Customizations

Base Software Upgrade

Remove Customizations Eclipsed by

Retrofit Misaligned Customizations

Base Software Upgrade

Re-Engineer Business Processes to take Advantage

Retrofit Misaligned Customizations

Base Software Upgrade

Upgrade Project Objectives [a.]

1. What are the key objectives for this upgrade project?

2. How will success be measured?

• In-house, no external (Migration Discovery only)

Project Management [e.]

1. Who is responsible for creating and updating the project plan?

2. What method will the project plan be based upon?

Suggestion: Oracle recommends using the EasiPath Migration Method.

4. How will the project library be managed?

Business Process Change [f.]

Implementation of New Features [g.]

1. Generally, implementation of new features:

• will occur if required as part of the upgrade

Implementation of New Modules [h.]

Oracle Applications Oracle Applications

BOM INV GL BOM INV GL

Technical Architecture Changes [i.]

• will occur if required as part of the upgrade

• A single set of books environment will be upgraded to a Multi-Org environment.

Oracle Apps Release 10.4 Oracle Apps Release 10.7

• Multiple install environment will be upgraded to a Multi-Org environment.

Oracle Apps (Release 10.4 ) Oracle Apps (Release 11)

ENG OE-2 AR-2 ENG

SOB2 IO2 SOB2

• Multiple install environment will be upgraded to a Multiple install environment.

Oracle Apps (Release 10.4) Oracle Apps (Release 10.7)

ENG ENG OE-2 AR-2

• Multiple production environments will converge into a single Multi-Org production

Oracle Apps (Release 10.4 )

Oracle Apps (Release 11)

WIP PO AP IO1 SOB1