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

407231.doc

Copy No.

Name

Location

1 2 3

Library Master

Project Library Project Manager

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 Migration Assessment. Migration Discovery then provides enough information to support the detailed project planning and project estimating activities.

Relationship Between Assessment Tools

ccu

d/A

ils

ta De

ere ath

EasiPath Migration Method

f yo

t ma

ion

Migration Assessment

Update & Test

Transition

Production

for

In

c ra

Migration Discovery

G

Preliminary Migration Later during the 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 Applications Server Layer Client Device Layer

(Repeated for each environment)

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 consultantfacilitated 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?

2.

Are there any other projects underway, or planned, that will have an impact on the completion of the Oracle Applications upgrade project?

3.

Are there any hardware, software, or business constraints that will affect the timing of the upgrade?

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

Minimal

At a minimum, you need to undertake the Base Software Upgrade and Retrofit. Misaligned

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

Basic

Normally, a migration also includes the objective to remove prior customizations that have been

Remove Customizations Eclipsed by New Features Retrofit Misaligned Customizations Base Software Upgrade 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

Comprehensive

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

Remove Customizations Eclipsed by New Features Retrofit Misaligned Customizations Base Software Upgrade

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?

2.

How will success be measured?

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.

2.

Identify any software issues requiring Oracle Application environment upgrades to occur at different times.

3.

Identify any hardware factors requiring Oracle Application environment upgrades to occur at different times.

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?

3.

What are normal business hours for the client staff? Are overtime hours allowed, and if so are they willing to work them?

4.

Are there any specific client staffing issues, such as a mandatory shutdown for inventory counting or maternity leave?

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?

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?

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?

2.

Are there any existing site documented test scenarios that should be used, or will the upgrade team need to create them?

3.

How many test upgrade cycles would the client like performed prior to the production upgrade?

4.

Will it be necessary to perform a User Acceptance Test of the production environment before using/accepting the system?

5.

Is there sufficient hardware capacity to perform test upgrades, such as disk space for test environments and CPU capacity for executing tests?

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?

7.

Will testing software be used to automate portions of the testing process? If yes, which software tool will be used?

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?

2.

What method will the project plan be based upon? Suggestion: Oracle recommends using the EasiPath Migration Method.

3.

How will project management report to executive management? For example, will there be an executive steering committee and a project sponsor?

4.

How will the project library be managed?

5.

How will custom software be controlled? What configuration management system is used?

6.

What existing custom coding standards are to be followed for custom extensions?

7.

How will project acceptance occur? Who will officially accept the upgrade?

8.

What requirements are there for project personnel time recording, including both internal and external resources?

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. Nondiscretionary 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?

2.

Have these changes been scrutinized to ensure they cannot be postponed until after the upgrade?

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:

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

BOM

OE

AR GL

INV

MRP

BOM

AR GL

INV PA

MRP

WIP

AP

PO

COST

WIP PO

AP

COST

Legacy Project Accounting

1.

Are there any plans to implement additional Oracle Applications modules as part of the upgrade?

2.

If so, which application products are considered, and what are the business reasons for wanting to implement those applications? 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?

3.

What technical architecture changes should be made as part of the upgrade project?

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. Current Release Environment

New Release Environment

Oracle Apps Release 10.4

Oracle Apps Release 10.7

ENG OE BOM

MRP

WIP

COST

ENG

AR

INV

IO

SOB

PO

AP

AR

OE GL

BOM

INV

MRP

IO

WIP

GL

SOB

PO

AP

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.

Current Release Environment

New Release Environment Oracle Apps (Release 10.4 )

ENG

OE-2 OE-1

INV-2 BOM

Oracle Apps (Release 11) ENG

AR-2

OE

AR-1 GL

INV-1

BOM

SOB1

MRP

AR GL

INV

SOB1

IO1

MRP PO-2

WIP

PO-1

AP-2

SOB2

AP-1

SOB2

IO2

WIP

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. Current Release Environment

New Release Environment Oracle Apps (Release 10.4)

ENG

OE-2

INV-2 BOM

OE-1

Oracle Apps (Release 10.7) ENG

AR-2 GL

INV-1

SOB1

MRP

WIP

COST

PO-2 PO-1

AP-2

OE-2

INV-2

AR-1

SOB2

BOM

OE-1

AR-2 AR-1 GL

INV-1

SOB1

MRP

WIP

AP-1

PO-2 PO-1

AP-2

SOB2

AP-1

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.

New Release Environment

Current Release Environments Oracle Apps (Release 10.4 )

Oracle Apps (Release 11) ENG

OE

AR

INV

BOM

IO1

MRP WIP

GL

SOB1

PO

ENG OE BOM

AP

AR GL

INV IO1

SOB1

MRP

COST

WIP

SOB2

IO2

PO Oracle Apps (Release 10.5)

ENG

OE

AR

INV

BOM

IO2

MRP WIP

AP

COST

GL SOB2

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?

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?

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?



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?

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?

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 [email protected].

2.

When will language translations be available in your language for the new release?

3.

Is the Oracle Consulting MLS solution installed in this environment?

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?

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?

Network Considerations [s.] 1. 1.

If a client/server environment is being employed, is there a stable network to allow continuation of work during brown outages?

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: •

407231.doc

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

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 Environment Name

Physical Location

Primary Contact Name, Phone and Email Address

Release

User Interface: (Character, SC, or Browser)

Technical Architecture (2-tier character, 2-tier SC, 3-tier NCA)

Dependencies on Other Application Environments

EURO-PROD

DB-Paris, Clients-Europe DB-Paris Clients-Europe DB-UK Clients-World Wide

Jar Dehooeekn

10.7

2-tier SC

EURO-TEST is a mirror on EURO-PROD, EURO-TRAIN

Jar Dehooeekn

10.7

Jar Dehooeekn

10.7

Character and Smart Client Character and Smart Client Character and Smart Client

EURO-TEST EURO-TRAIN

2-tier SC 2-tier SC

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 Name

407231.doc

LAN/WAN

Geographical Area Covered

Bandwidth

Copyright © 1998, Oracle Corporation

Protocols

Latency

Contact Name, Phone, Email Address

Oracle Application Environment Supported

Note

Oracle Applications Environment - [B.]

23

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?

1.

Is there a help desk where users can call with questions concerning Oracle Applications, networks, or other technical questions?

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?

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?

4.

Does the customer use Oracle MetaLink and if so, to what extent?

5.

How does the customer receive patches?

6.

How does the customer manage the application of patches to the environments?

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

24

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:

407231.doc

•

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.

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

25

3 Architecture Layers For Oracle Applications

Character User Interface

SmartClient User Interface

Oracle Database

Oracle Applications Software

Master Database Layer

NCA User Interface

Oracle Applications (Server Side)

CPU

CPU

Oracle Database

Oracle Database

CPU

CPU

CPU

CPU

Oracle Applications Server

Applications Server Layer

CPU

CPU

Client Device Layer

Oracle Applications Software

Terminal or PC

PC Oracle Apps (Client Side)

PC w/ Browser

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

Prior to 10.6 10.6 10.7 11 407231.doc

Character

Yes Yes Yes No

SmartClient

No Yes Yes No

Copyright © 1998, Oracle Corporation

NCA

No No Yes Yes

Character

Charter

& SmartClient

SmartClient & NCA

No Yes Yes No

No No Yes (GL NCA only) No Oracle Applications Environment - [B.]

26

The table above shows the various user interface options that are available. An explanation of these options for each release is listed below:

407231.doc

•

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/ Sequence

Oracle Application Module

Major Release

Module Version

Prod Number

Patch Status

# of Named Users

# of Concurrent Users

Sample-1 Sample-2

AOL GL

10.7 10.7

6.1.1 9.0.9

16.1 16.1

Current Current

114 114

35 6

Identifier/ Sequence

Oracle Application Module

User Interface: (Character, SC, or Browser)

Tier: (Database Layer, Application Server Layer, Client Device Layer)

Share Status - pre10.7: (Fully Installed or Shared)

Data Segregation Approach (None, Multiple Installs, Multi-Org Feature)

Sample-1 Sample-2

AOL GL

Char, SC Char, SC

DB, Client DB, Client

Installed Installed

None None

Identifier/ Sequence

Oracle Application Module

Planned Major Release

Planned Module Version

Planned Prod Number (SC only)

Patch Level Goal

# of Named Users

# of Concurrent Users

Sample-1 Sample-2

AOL GL

11.1 11.1

TBD TBD

N/A N/A

Current Current

114 114

35 6

(SC only)

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

27

Identifier/ Sequence

Oracle Application Module

User Interface: (Character, SC, or Browser)

Tier: (Database Layer, Application Server Layer, Client Device Layer)

Multi-Org Plans

Comments

Sample-1 Sample-2

AOL GL

Browser Browser

DB, AS, Client DB, AS, Client

None None

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?

3.

What globalizations/localizations are installed?

4.

How many Sets of Books are in use?

5.

What languages are installed?

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.

407231.doc

What high-level customizations currently exist for this environment?

Identifier / Sequence

Name/Function of extension

Master Database Layer

Application Server Layer

Client Device Layer

Specification/ Documentation

EXT-02

Work Order Validation

YES

NO

NO

$CPO_TOP/install/do c/EXT-02.doc

EXT-09

Auto-Pay/Pay on Receipt

YES

NO

N/NO

$CPO_TOP/install/do c/EXT-09.doc

Copyright © 1998, Oracle Corporation

Is the documentation current?

Comments

Supports on-line validation of maintenance work order numbers on PO lines and associated AP Invoice Lines Supports auto generation of invoices for payment processing for vendors that have the ‘Auto-Pay’ attribute. Likely eclipsed by new Oracle Applications Environment - [B.] 28

Identifier / Sequence

Name/Function of extension

Master Database Layer

Application Server Layer

Client Device Layer

Specification/ Documentation

EXT-04

Performance Variance Calculator

YES

NO

NO

$CPO_TOP/install/do c/EXT-04.doc

Is the documentation current?

Comments

application functionality Supports vendor commit to 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?

2.

Should current production data be analyzed to ensure accuracy before the production upgrade? If so, will this be within the upgrade project scope?

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?

2.

Is there procedure level documentation for the user? If so, what does it include?

3.

Does current customization documentation exist? What does it include?

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

29

4.

Are test scripts (specific to existing customizations, interfaces), which could be used for testing modified customizations to be migrated, available? What is included? •

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?

2.

If necessary, is it acceptable to create an environment which does not meet your non-OFA compliant standards during the applications upgrade?

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?

2.

When was the last time a recovery was successfully done?

3.

When was the last cold backup taken?

4.

When was the last hot backup taken?

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

30

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?

2.

Will the Oracle Applications upgrade require an Oracle database upgrade? If so, to what release?

3.

Will any third party application software require upgrades due to the Oracle Applications upgrade? If so, to what release?

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)?

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?

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?

2. 407231.doc

Have changes been made to the standard print definitions? Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

31

3.

Do any printers directly attach to Oracle Application client devices?

4.

If modified printer description files exist, where are they being used by the Oracle Applications?

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:

407231.doc

•

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.

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

32

Master Database Layer

Character User Interface

SmartClient User Interface

Oracle Database

Oracle Applications Software

Oracle Applications (Server Side)

CPU

CPU

NCA User Interface

Oracle Database

Oracle Database

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?

2.

What is the total disk space and the amount of disk space available for the upgrade?

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

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?

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

33

2.

For UNIX operating systems, what Shell is in use for the Oracle Database account owner?

3.

What text editor is in use to develop and maintain shell scripts?

4.

Does the site use raw or file system organized disks?

5.

Are there any optimization techniques in place? (i.e. stripping, mirroring)

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?

2.

What is the Oracle Server patch status?

3.

Is the Oracle Parallel Server option being used?

4.

Is replication being used? If so, how many distributed replication databases are in use?

5.

Is the National Language option being used? If so, what languages are in use?

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

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

34

• Between 30 and 50 GB • Over 50 GB 1.

Where are the database log files stored?

2.

Is Multiple Language System Support being used? If so, what languages are being used?

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?

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?

3.

What server management tools are in use at this time? Are they compatible with planned upgrades to the Oracle Server environment?

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.

407231.doc

What interfaces between Oracle Applications and other applications exist?

Identifier / Sequence

Source System/Applications

Destination System/ Application

Content

Hot or Batch

Frequency (e.g., Daily, Monthly)

Volume (Ave # of records or transactions

Standard Oracle Interface API

Technical Environment

INT-01 INT-02

Lease Management (MVS/TSO) Costing (ISIS)

Oracle-AP Oracle-GL

AP Invoices GL Journals

Batch Batch

Nightly Nightly

300/night 45,000/night

No Yes, GLJE

SQL*Loader, SQL/Plus SQL*Loader

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

35

Identifier / Sequence

Source System/Applications

Destination System/ Application

Content

Hot or Batch

Frequency (e.g., Daily, Monthly)

Volume (Ave # of records or transactions

Standard Oracle Interface API

Identifier / Sequence

DDL Code (Location and Name)

Execution Code (Location and Name)

Century Date Destination

Century Date Source

Migration

INT-01

$CAP_TOP/install/sql/int01a.sql, $CAP_TOP/install/sql/int01b.sql

$CAP_TOP/sql/int01.sql, $CAP_TOP/bin/int01.ldr

Reviewed, OK

Reviewed, OK

INT-02

N/A

$CAP_TOP/bin/int02.ldr

Reviewed, needs YYYY

Reviewed, needs YYYY

Technical Environment

Migration Complexity

Notes

Migrate

VE

Migrate

VE

Check to see if tables have changed Code rework for C/Date

Plan

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.

407231.doc

What custom database server objects exist at the Master Database Layer?

Identifier / Sequence

Object Name

Type - Schema, Table - Synonym, View - Grants, Profile - Sequences

Schema

DDL Code

Description

EXT-02/ DSO.001

CUST

SCHEMA

CUST

Schema for customer’s custom extensions and database objects

EXT-02/ DSO.002

MAINTENANCE_WORK_ORDERS

TABLE

CUST

EXT-02/ DSO.003

MAINTENANCE_WORK_ORDERS

GRANT (Select)

to PO, FND

$CFND_TOP/inst all/sql/cust_schem .sql $CPO_TOP/instal l/sql/mwo.sql $CPO_TOP/instal l/sql/mwo.sql

Copyright © 1998, Oracle Corporation

Create Script for Maintenance Work Orders Table Create Script for Maintenance Work Orders Table

Oracle Applications Environment - [B.]

36

Identifier / Sequence

Century Date

Migration Complexity (VE, E, M, C)

EXT-02/ DSO.001 EXT-02/ DSO.002 EXT-02/ DSO.003

N/A To be reviewed N/A

VE VE VE

2.

Oracle Standards Used

Notes

Check format of any date columns during project Strip out grants portion of $CPO_TOP/install/sql/mwo.sql into new script so that it can be rerun anytime grants are lost

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.

407231.doc

Identifier / Sequence

Object Name

Type - Schema, Table - Synonym, View - Grants, Profile - Sequences

Schema

EXT-09/ DSSO.001

PO_VENDORS

TABLE

CUST

EXT-09/ DSSO.002

PO_VENDORS

GRANT (Select)

to CUST

DDL Code (Alter Object Script)

$CPO_TOP/install/sql/m wo.sql $CPO_TOP/install/sql/m wo.sql

Description of change from what was installed as shipped

Additional column added ‘AUTO_PAY’ char(1) to support auto invoice generation on receipt Grant script

Identifier / Sequence

Century Date

Migration Complexity (VE, E, M, C)

Notes/Plan

EXT-09/ DSSO.001

Reviewed, OK

C

EXT-09/ DSSO.002

N/A

VE

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. Review/Migration to new functionality in this area and retire extension and modification to standard table. Oracle Applications Environment - [B.] 37

Copyright © 1998, Oracle Corporation

Identifier / Sequence

Century Date

Migration Complexity (VE, E, M, C)

Notes/Plan

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 / Sequence

Name/Function of extension

Schema

Type - Package - Trigger

Table(s) (Triggers)

On-Action (Triggers)

DDL Code

EXT-02/ TRG.001

Work Order Validation Trigger

PO

Trigger

PO_LINES

$CPO_TOP/install/sql/ext01.sql

EXT-02/ PKG.004

Work Order Validation Package

PO

Package

N/A

Insert, Update N/A

Identifier / Sequence

Century Date

Migration Plan

Migration Complexity

Notes

EXT-02/ TRG.001 EXT-02/ PKG.004

Reviewed, OK Reviewed, OK

Migrate Migrate

Low Low

Check to see if tables have changed Check to see if tables have changed

4.

$CPO_TOP/install/sql/ext02.sql

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).

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

38

Identifier / Sequence

Name/Function of extension

Schema

Type - Package - Trigger

Table(s) (Triggers)

On-Action (Triggers)

DDL Code

EXT-07/ TRG.002

POP_CMERGE_REQ Customer Merge Package for PO

PO

Package

PO_REQUSITI ON_LINES, PO_LOCATIO N_ASSOCIATI ONS,

N/A

Orig:$PO_TOP/install/sql/pocmerge.pkb Cust: $CPO_TOP/install/sql/pocmerge.pkb

Identifier / Sequence

Century Date

Migratio n Plan

Migration Complexity

Notes

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? 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.

407231.doc

Identifier / Sequence

Name/Function of extension

Libraries Used

‘C’ Source Code

Make file

EXT-04/ VARCAL

Performance Variance Calculator

lib.a, onx, varc

$CPO_TOP/install/bin/ EXT04.src

$CPO_TOP/install/bin/VARCAL.mk

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

39

Identifier / Sequence

‘C’ Executable

EXT-04/ VARCAL

$CPO_TOP/bin/VARCAL

Century Date

Migration

Not Compliant

Migrate

Plan

Migration Complexity

Notes

High

Check to see if tables have changed

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 / Sequence

Name/Function of extension

libraries used

‘C’ Source Code

Make file

EXT-05/ RTP

Online RCV Transaction Manager (Online Advise for high-priority receipt of maintenance materials)

rcvoltm.o, $(APPL_LIBS), ${LFNDLIB)

Orig: $PO_TOP/lib/rcvoltm.c Cust: $CPO_TOP/lib/ccvoltm. c

$CPO_TOP/PO/lib/CPO.mk

Identifier / Sequence

‘C’ Executable

Century Date

Migration

EXT-05/ RTP

$CPO_TOP/bin/CCVOLTM linked to $PO_TOP/bin/RCVOLTM

Compliant

Migrate

8.

407231.doc

Plan

Migration Complexity

Notes

Medium

Check to see if ‘c’ source has changed

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.

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

40

Identifier / Sequence

Form Long Name

Ship Form Name, Code Path

Modified Form Name, Code Path

Comments

EXT-02/APXINMSI EXT-02/POXPIMSI EXT-09/ APXVDMVD

Enter Invoices Enter Purchase Orders Enter Vendors

$AP_TOP/forms/APXINMSI.inp $PO_TOP/forms/POXPIMSI.inp $AP_TOP/forms/APXVDMVD.inp

$CAP_TOP/forms/APCXINMSI.inp $PO_TOP/forms/POXPIMSI.inp $CAP_TOP/forms/APXVDMVD.inp

Identifier / Sequence

Century Date

Migration Plan

Migration Complexity

Notes

EXT-02/APXINMSI

Reviewed custom code, OK

Very Complex

Check to see if tables have changed

EXT-02/POXPIMSI

Reviewed custom code, OK

Very Complex

Check to see if tables have changed, Also .. this form is in the wrong code path. Should be in the CPO_TOP code path and executed from there. Will need to download the current non-customized (‘as-shipped) source for final Century date review through Ravel tool.

EXT-09/ APXVDMVD

To be Reviewed

Migrate to NCA, Reapply customizations to latest version of form Migrate to NCA, Reapply customizations to latest version of form May eliminate as eclipsed

TBD

May no longer be required due to new feature introduced in latest release

Detailed Century date review statistics from the Unravel/2000 tool: Identifier / Sequence

# of Base Table Blocks

# of Control Blocks

# of Fields

# of Triggers

# of Triggers with Date Ref.

# of SQL Lines

# of Date Variables

# of Related Date Variables

# LOC with Date Ref

EXT-02/APXINMSI EXT-02/POXPIMSI EXT-09/ APXVDMVD

3 4 6

1 1 1

132 145 167

37 56 54

22 12 34

345 735 105

35 53 24

23 22 34

17 33 23

9.

Notes

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 / Sequence

407231.doc

Total LOC

Form Long Name

New Form Name, Code Path

Copyright © 1998, Oracle Corporation

Comments

Oracle Applications Environment - [B.]

41

Identifier / Sequence

Form Long Name

Identifier / Sequence

Century Date

New Form Name, Code Path

Migration Plan

Migration Complexity

Comments

Notes

Detailed Century date review statistics from the Unravel/2000 tool: Identifier / Sequence

# of Base Table Blocks

# of Control Blocks

# of Fields

# of Triggers

# of Triggers with Date Ref.

# of SQL Lines

# of Date Variables

# of Related Date Variables

# LOC with Date Ref

Total LOC

Notes

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 Name

407231.doc

File Name

Path

Description of Report

Copyright © 1998, Oracle Corporation

Migrate (Y or N)

# of SQL Lines

# of Date Variables

# of Related Date Variables

# of LOC with Date Ref.

Total LOC

Note

Oracle Applications Environment - [B.]

42

15. If RPT new reports have been created, please complete the information below: 16. Report Name

File Name

Path

Description of Report

Migrate (Y or N)

# of SQL Lines

# of Date Variables

# of Related Date Variables

# of LOC with Date Ref.

Total LOC

Note

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 Name

Path

Description of Module

Migrate (Y or N)

Date Code Present (Y or N)

Century Date Compliance (Y or N)

Doc Ref.

Note

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.

Module Name

407231.doc

File Name

Path

Description of Module

Copyright © 1998, Oracle Corporation

Migrate (Y or N)

Date Code Present (Y or N)

Century Date Compliance (Y or N)

Doc Ref.

Note

Oracle Applications Environment - [B.]

43

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.

Module Name

File Name

Path

Description of Module

Migrate (Y or N)

Date Code Present (Y or N)

Century Date Compliance (Y or N)

Doc Ref.

Note

Doc Ref.

Note

15. If Reports2.0 programs have been developed, please complete the information below:

Module Name

File Name

Path

Description of Module

Migrate (Y or N)

Date Code Present (Y or N)

Century Date Compliance (Y or N)

17. If Reports 2.5/3.0 reports have been modified, please complete the information below: 18. Report Name

File Name

Path

Description of Report

Migrate (Y or N)

# of SQL Lines

# of Date Variables

# of Related Date Variables

# of LOC with Date Ref.

Total LOC

Note

19. If new Reports 2.5/3.0 reports have been created, please complete the information below: 20. 407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

44

Report Name

File Name

Path

Description of Report

Migrate (Y or N)

# of SQL Lines

# of Date Variables

# of Related Date Variables

# of LOC with Date Ref.

Total LOC

Note

# of Date Variables

# of Related Date Variables

# of LOC with Date Ref.

Total LOC

Note

21. If Reports 4.0 are in use, please complete the information below: 22. Report Name

File Name

Path

Description of Report

Migrate (Y or N)

# of SQL Lines

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 Name

Body Name(s)

Path

Description

Migrate (Y or N)

# of SQL Lines

# of Date Variables

# of Related Date Variables

# of LOC with Date Ref.

Total LOC

Note

25. Have any operating system Shell scripts been developed? 26.

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

45

Script Name

407231.doc

File Name

Path

Description of Script

File Type

Copyright © 1998, Oracle Corporation

LOC

LOC with Date Ref

# of Date Fields

Migrate (Y or N)

Doc Ref.

Note

Oracle Applications Environment - [B.]

46

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

Character User Interface

SmartClient User Interface

NCA User Interface Oracle Applications Software

Oracle Applications 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. 407231.doc

What Oracle Applications Server software release is in use? Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

47

2.

What is the Oracle Application Server patch status?

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?

2.

What is the Forms Listener patch status?

3.

What options, if any, are installed?

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?

2.

What is the total disk space and the amount of disk space available for the upgrade?

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?

2.

For UNIX operating systems, what Shell is in use (i.e., csh, ksh, or bsh)?

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

48

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.

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.

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.

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?

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 Assessment

Complexity (VE, E, M, C)

Note

Forms

2. 407231.doc

Identify whether the Oracle Applications source code has been modified and where this source code is located. Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

49

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 Name

2.

Brief Description

Built Using Oracle Tools (Y or N)

Development Tools Used

Migrate (Y or N)

Century Date Compliant (Y or N)

Access Standard Oracle Applications Tables (C Create, R - Read, U - Update, D Delete or N - No)

Uses Oracle Application API’s (List API)

Doc Status

Note

Identify what the plans are to achieve Century Date compliance for these custom applications.

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

50

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

Character User Interface

PC/Terminal Char Mode (Client Side)

SmartClient User Interface

Oracle Applications Software

NCA User Interface

PC Oracle Apps (Client Side)

PC w/ Browser

Terminal Emulation (Character mode Only) [a.] 1.

What terminal emulation package is being used?

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

51

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?

2.

What JDK is currently being used?

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?

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.

2.

Generally speaking, what is the total disk space and the amount of disk space available for the upgrade on these devices?

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?

2. 407231.doc

Is an operating system upgrade required for this Oracle Applications Upgrade? If so, what is the lead time and impact? Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

52

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.

2.

Identify the dependencies between any third-party software products and Oracle software products that should be considered during the Oracle Applications upgrade.

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 Application Module

2.

Summary of Changes

Intent to Migrate

Date Logic Added or Changed

C/Date Compliance Status

Documentation Reference

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.

Oracle Application Module

407231.doc

Form Name

Form Name

Summary of Changes

Copyright © 1998, Oracle Corporation

Intent to Migrate

Date Logic Added or Changed

C/Date Compliance Status

Documentation Reference

Oracle Applications Environment - [B.]

53

Oracle Application Module

3.

Form Name

Summary of Changes

Intent to Migrate

Date Logic Added or Changed

C/Date Compliance Status

Documentation Reference

Identify the most often used variable names for the date fields in the customizations.

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 Name

2.

Brief Description

Built Using Oracle Tools (Y or N)

Development Tools Used

Migrate (Y or N)

Century Date Compliant (Y or N)

Access Standard Oracle Applications Tables (C Create, R - Read, U - Update, D Delete or N - No)

Uses Oracle Application API’s (List API)

Doc Status

Note

Identify what the plans are to achieve Century Date compliance for these custom applications.

407231.doc

Copyright © 1998, Oracle Corporation

Oracle Applications Environment - [B.]

54

Issues

General Open Issues Issue

Responsibility

Identification Date

Resolution Target Date

Comments

Responsibility

Identification Date

Resolution Target Date

Comments

Closed Issues Issue