Oracle Business Accelerators

PROJECT IMPLEMENTATION GUIDELINES

OCTOBER 15, 2008
2

Copyright 2004, 2009, Oracle. All rights reserved.

Contents

Overview.................................................................................................................................. 1 What is the Role of Oracle Business Accelerators? ..................................................... 1 Leading and Participating in an Oracle Business Accelerator Project............................. 2 Choosing a Project Team ................................................................................................ 2 Training Requirements ................................................................................................... 2 Implementer Workshop.................................................................................................. 2 Project Risk Mitigation with OBA ................................................................................. 3 Support and Assistance.......................................................................................................... 5 Key Concepts........................................................................................................................... 6 Setup Mechanics of the Oracle Business Accelerator ................................................. 6 Setup Template ................................................................................................................ 6 Setup Loader .................................................................................................................... 7 Configured Applications Environment ........................................................................ 7 Project Workspace ........................................................................................................... 7 Accelerator Implementation Project Lifecycle ............................................................. 9 Accelerator 12 Step Implementation Method .............................................................. 9 Sales Cycle ............................................................................................................................. 11 1.0 Scoping ...................................................................................................................... 11 2.0 Bid Development ..................................................................................................... 12 3.0 Acceptance................................................................................................................ 12 Project Preparation ............................................................................................................... 14 4.0 Request & Install Software ..................................................................................... 14 5.0 Request & Prepare Project Workspace.................................................................. 15 6.0 Project Initiation....................................................................................................... 17 Execution................................................................................................................................ 19 7.0 Enter Setup Data ...................................................................................................... 19 8.0 Configure Applications........................................................................................... 24 9.0 Validation and Acceptance Testing....................................................................... 28 Post Accelerator Activities................................................................................................... 29 10.0 Additional Functionality ...................................................................................... 29 11.0 Conversions and Customizations........................................................................ 30 12.0 Transitioning to Production ................................................................................. 30 Accelerator Implementation Plan and Checklist .............................................................. 32 OBA 12 Step Implementation Method............................................................................... 35 Oracle Business Accelerator Discovery Questionnaire and Worksheet........................ 36

Project Implementation Guidelines

Overview ii

Overview
This document provides an explanation of the Oracle Business Accelerator implementation methodology. Our goal is to encourage the most effective and efficient implementation practices when using the Oracle Business Accelerators. Project Managers and their teams must understand how Oracle Business Accelerators change and streamline the implementation process. Along with the Project Implementation Guidelines, the OBA provides a project plan starter template matched to the OBA Implementation method. This template is a starting point for planning your OBA implementation project. Another key document provided to guide managers and project teams, the Setup Guide document discusses the details of how to log Accelerator service requests, how to use the Project Workspace, how to use the Setup Loader, and how to resolve setup errors.

What is the Role of Oracle Business Accelerators?

Oracle Business Accelerators are a rapid implementation approach based on standard business flows and leading industry practices. Accelerators provide an online Project Workspace, an automated Setup Loader and associated collateral targeted a specific industry and country. Oracle Business Accelerators empower project teams to rapidly configure a master instance (Baseline) with standard business flows matched to customer requirements in a highly structured manner. The instance is ready for transition to production when the standard flows satisfy the customer requirements. Alternatively, prior to go-live, the project team can use the master instance as a baseline to configure additional flows and applications, develop reports and customizations, and integrate with 3rd party applications. These activities are performed outside of the Accelerator scope.

Project Implementation Guidelines

Overview 1 of 37

Leading and Participating in an Oracle Business Accelerator Project

Proper preparation and planning is a critical determinant of an implementers ultimate success with Oracle Business Accelerators (OBAs). Success begins with choosing and training a project team. The nature of project management is the same in an OBA implementation project but the approach and project tasks differ significantly. Project Managers and their team must be trained and prepared to implement using a new approach. In this section we discuss the most important considerations regarding the Leadership and Participation in OBA Implementation projects.

Choosing a Project Team

The Accelerator approach assumes only experienced implementers who have completed the mandatory training may utilize an Oracle Business Accelerator. Implementers with little or no Oracle E-Business Suite implementation experience are at a disadvantage with the lack of knowledge concerning Oracle EBusiness Suite configuration details. Each implementation team member must have a basic understanding of the underlying setup relationships and requisite data for their functional area. Recommended minimum staffing and experience for project resources: At least one experienced Oracle Financials implementation consultant. Minimum level of experience of at least 3 or more implementations. At least one experienced consultant for each major functional area being implemented e.g. Supply Chain, Manufacturing, Project Accounting, Sales and Service etc. At least one experienced Oracle Applications Database Administrator trained on Accelerator installation.

Project Managers must use their experience when staffing any implementation project. While Oracle Business Accelerators may ease the initial effort for an implementation project and may provide a certain amount of leverage in staffing your project, the number of resources required will vary according to project complexity, schedule, budget, and other factors. References: Leading Practice: Staffing an OBA Project (ID 456202.1) How do I Qualify for Accelerator Access (ID 409133.1)

Training Requirements
Proper training is required to effectively utilize the Oracle Business Accelerators. The Project Manager must ensure that all project members complete the required training for their project role before the beginning of the project and requesting a project workspace. Additionally, all project team members must successfully complete an Implementer Workshop. Oracle Business Accelerators Training Requirements are available online: Release 12: OBA Training Requirements

Implementer Workshop
The Implementer Workshop is a mandatory requirement for first time OBA implementation teams. Before using Oracle Business Accelerators for a client engagement, prospective OBA implementers gain handson experience through participation in a practice implementation exercise. This exercise is intended to serve as the final component of a complete learning experience which complements the online training discussed above. After completion of this requirement, implementers become eligible for Project Workspace access and are prepared for Accelerator delivery at a client engagement. Additional details on the Implementer Workshop requirements are available here: Oracle Business Accelerator Implementer Workshop (ID 421948.1)

Project Implementation Guidelines

Leading and Participating in an Oracle Business Accelerator Project 2 of 37

Implementer Workshop Training

Project Risk Mitigation with OBA

Listed below are potential sources of Project Risk for an OBA implementation and suggested mitigation.
Risk Description Mitigation

Accelerator Fit Assessment

Picking the appropriate Accelerator is critical to reducing project implementation time.

Sales team should have a clear understanding of Accelerator key assumptions and functionality. Ensure that all team members have completed the appropriate on-line training. Scoping teams should clearly understand the business requirements that fall outside the scope of the Accelerator; Bids and timelines should be adjusted accordingly. Expectations should be set with the client on what the Accelerator baseline includes, and what features and functions will be addressed once the baseline is approved. The project team must have prior implementation experience. The functional area experts will be able to provide effective leadership on an Accelerator project. Each partner should have a strategic training plan in place to ensure certified resources are available to staff projects before project start up.

Business Flow Fit

Some required business processes might not be addressed in the scope of the Accelerators business flows.

Implementation Experience

Accelerators are no substitute for experienced implementers and project management.

Availability of Accelerator Trained Resources

All partner resources must complete mandatory training that includes a hands-on implementer workshop. Successful completion of the training is a prerequisite for access and privileges in their project workspace. Success is dependent on the willingness to adopt leading practice business processes.

Change Management

Clear expectations should be set in the sales cycle with the executive team that their participation might be required to mandate change.

Accelerator and Business Flow Fit Assessment Trained sales and delivery partner resources need to be involved in scoping the work effort for a potential Accelerator project. The bid and project teams should review the Business Flow Models and the Functionality Overview with their clients to determine whether the Oracle Business Accelerator functionality and configurations is appropriate for the clients business requirements. The overall fit to the clients requirements should be expressed as a percentage indicating how appropriate the business flow is for the client. Clear expectations should be set with the client regarding how much functionality is provided via the Accelerators Configuration Tool and how much additional effort will be required to configure additional functional requirements. The estimate should be aligned with the project scope of services. The contract should clearly differentiate Accelerator solution functionality that is implemented versus any additional functionality outside the scope of Accelerator functionality.

Project Implementation Guidelines

Leading and Participating in an Oracle Business Accelerator Project 3 of 37

The bid and project teams must proactively manage client expectations throughout the sales and delivery cycle. Resources from Oracles Channel Sales organization should be leveraged as necessary to assist the bid teams. Any proposal or contract that will leverage Oracle Business Accelerator materials should include an assumption that states the following:

The client will adopt the standard processes and application functionality as defined by the Oracle Business Accelerator materials. Any deviation from the standard processes and functionality will be addressed through the projects change control process.

Oracle Applications Implementation Experience The need to staff an Oracle Business Accelerator project with experienced resources cannot be overemphasized. Setup questions reflect the setups for a particular application. The default values are provided to speed the implementation process, based on leading practice, and familiar to experienced implementers. These experienced resources will have a superior understanding of what can and should be modified, added or removed versus what defaults are acceptable. The Accelerator allows for a certain amount of leverage when staffing a project, assuming that the staff is experienced with Oracle E-Business Suite implementation. Accelerators cannot substitute for experience, but they do allow experienced implementers to accomplish more than in a traditional manual implementation. If experienced Oracle Applications implementers are not available -- particularly for the key roles such as Financials and Procurement -- the bid team should consider positioning the implementation project without the Oracle Business Accelerator. Change Management and Scope Control The ability for the clients organization to absorb all of the anticipated changes during and after an accelerated implementation, and to provide resources to accomplish the client-side responsibilities of the implementation is a crucial determinant of implementation success. Project managers must clearly assess the clients ability to absorb changes providing appropriate resources during the implementation. This may be done as part of the sales cycle or as part of an assessment workshop with the clients executives. Clearly document the project scope in the contract. Set and manage the appropriate expectations with the client before and during the execution of the project. Complex Requirements Accelerators may be leveraged on global and complex implementations. The extent to which an Accelerator may be used is a critical decision point that must be evaluated to ensure that they are leveraged in a reasonable manner. Many Accelerators are constrained to a single HR Business Group. In those Accelerators, additional HR Business Groups can be configured manually after the Accelerator setups are complete. Oracle Business Accelerators are specific to an industry within a country. The fit needs to be evaluated against the entire scope of the clients requirements to ensure selection of the most appropriate Accelerator solution. The Accelerators are not intended for upgrade or add-on situations; the Configuration Tool needs to be run on a fresh install only. Select the industry solution with the closest fit to the clients requirements. Solicit input from the Global Oracle Consulting resources from the other countries that are part of the global scope. Involve the Accelerate Program Management Office to help plan, estimate, and determine the reasonable approach options for implementing multiple countries. Leverage a phased implementation approach. Allocate additional contingency as appropriate (See Accelerator and Business Flow Fit Assessment, above).

Project Implementation Guidelines

Leading and Participating in an Oracle Business Accelerator Project 4 of 37

Support and Assistance

The Oracle Business Accelerators for E-Business Suite are designed to be self-supporting with all required information and learning aids available online. They are provided free of charge and are intended for use "As-Is" by trained, qualified implementers. English-language assistance is available from the Accelerators Online helpdesk through service requests logged via My Oracle Support. You may search for solutions and answers to Accelerator questions via the Oracle Business Accelerator Knowledge Base on My Oracle Support (formerly Metalink). This assistance is for Accelerator-related issues only. Help for E-Business Suite application issues -- unrelated to Oracle Business Accelerators should be sought through Oracle Support, not the Oracle Business Accelerator helpdesk. It is important to note that the Oracle Business Accelerator helpdesk helps to resolve all issues during India business hours only. All issues will be responded to within 3 India business days. Service Requests for Accelerator-related issues cannot be escalated. If you need further assistance, please contact your Oracle Alliances representative. It is the sole responsibility of the implementer to understand the ramifications of their implementation decisions. Where necessary, obtain support for any applications issues under a valid support contract or via fee for service. Any changes to data in the Project Workspace made by an implementer should be made with appropriate consideration of the ramifications and dependencies. Configuration Tool failures resulting from incorrect and inconsistent data are the sole responsibility of the implementer. Support information for Oracle Applications and other Oracle products may be obtained at http://www.oracle.com/support/index.html.

Project Implementation Guidelines

Support and Assistance 5 of 37

Key Concepts
In this section we discuss the key Oracle Business Accelerator concepts and components. A thorough understanding of the key components, purpose and their appropriate use is a critical factor leading to an OBA implementation success. The Project Workspace, the Setup Template and the Setup Loader are the mechanical components of the Oracle Business Accelerator used in the configuration of the E-Business Suite.

Setup Mechanics of the Oracle Business Accelerator

Shown below is a graphical representation of Oracle E-Business Suite using the Oracle Business Accelerator. These steps occur after the Setup Loader Utility software has been installed. 1. 2. 3. 4. Implementer Team enters setup responses in the Project Workspace on the Configuration Tool tab. Implementer Team member requests and imports Setup template into the applications instance. Implementer Team members execute the Setup Loader. The Accelerator Configured Applications Environment or Baseline is complete and the DBA executes a database backup.

Setup Template
The Configuration Tool Template refers to the electronic generation of setup data and instructions from the Project Workspace. The Setup Template provides the inputs to the automated Setup Loader for the setup of the Oracle E-Business Suite. The Setup Template is requested by the implementer from the installed applications instance after the implementation team has completed data entry/modification and validation in the Project Workspace. The Oracle Business Accelerators for Oracle E-Business Suite instance contains the Oracle EBusiness Suite and the Setup Loader. However, when the software is initially delivered, it comes without the Configuration Tool Template. The Configuration Tool Template consists of the business questions and setup data entered in the Project Workspace by the implementation team. The Configuration Tool Template is required in order to run the Setup Loader and configure the instance. Once the implementer has completed the responses to the Configuration Tool questions in the Project Workspace, they can login to the E-Business Suite environment and request the Configuration Tool Template. As Configuration Tool Templates are instance-specific, you need to obtain a new template each time you install a different Oracle Business Accelerators for Oracle EBusiness Suite instance.

Project Implementation Guidelines

Key Concepts 6 of 37

Setup Loader
The Oracle Business Accelerator software provides installation of the Oracle E-Business Suite and the Accelerator Setup Loader. Accelerator users access the Setup Loader by selecting the Oracle Business Accelerators responsibility and choosing the Configuration Tool menu item. The interface provides a step-by-step approach to request and import the Configuration Tool Template. After the template has been imported, the Setup Loader executes the configuration automatically based on the instructions provided by the Configuration Tool Template. Upon completion of the setups, the Setup Loader can no longer be executed. Information about the Setup Load run, however, is still available such as ability to view responses to the questions, view failed setups, view statistics, and generate the Manual Setups document.

Configured Applications Environment

Now you have a configured E-Business Suite environment. However there may be manual setups required. Follow the instructions provided and complete these setups. Once these are completed, the instance is ready for testing.

Project Workspace
The Project Workspace

The Project Workspace functions as the interface between the implementer and the automated configuration tool. Workspaces are hosted online at https://accelerators.oracle.com. A project workspace (Workspace) provides a simple structured interface composed of setup questions and default data that may be modified to meet client requirements. The workspace represents a starting point for an implementation project using a flexible and repeatable method for configuring Oracle E-Business Suite applications business flows. The automated Configuration Tool utilizes the data entered on the workspace to configure an applications instance. Setup Questionnaire Questions presented in the Project Workspace are organized under two main nodes: Common Key Business Questions includes common questions related to financial and organizational architecture, such as Chart of Accounts, Calendars, Locations, Business Group, Operating Units, Legal Entities and others.

Project Implementation Guidelines

Key Concepts 7 of 37

Specific Business Flow Questions includes questions grouped by application and address the additional setups required by each product for the business flows.

To complete the entry of setup data in a project workspace, first answer Common Key Business Questions. Then answer the Specific Business Flow Questions. All questions in the Configuration Tool should be answered in the order presented, unless instructed otherwise by the question hints. Types of Questions Three types of questions may appear in the Configuration Tool, depending on the Accelerator solution selected. Automated Questions account for most of the questions. The Configuration Tool automatically performs the corresponding setups for these questions in the required sequence. Manual Questions pause during Configuration Tool run-time. After performing the manual setups the Configuration Tool can be resumed. Post-Setup Questions appear as a sub-node under the relevant product nodes. A document is provided instructing the implementation team to perform the corresponding setups manually after the Configuration Tool has been run and before any transactions are posted.

Default Data Default data is provided in the Configuration Tool questionnaire where appropriate. This default data represents the most common settings based on leading implementation practices and is an important feature of the Accelerator-based rapid implementation. You can use this data as-is, or you can use it as a starting point adding, updating or deleting data as required. However to minimize effort, we recommend that you change only what is essential. Default data doesnt include any transactional master data items such as Items, Customers or Suppliers. Data can be deleted if it is not relevant to the implementation. The preferred approach to default data in the Configuration Tool is to modify data where necessary to match implementation requirements. The Configuration Tool automatically reflects data deletion in other questions that refer to that value. However, Flexfield structure changes for instance, adding segments or changing segment length are not automatically reflected elsewhere in the Configuration Tool because code combinations are captured through use of a text box. These changes can be made manually in each question where code combinations appear. Data (beyond the default data provided) may be added to the Configuration Tool when required. Caution: Deletion of default data must be considered carefully with an understanding the included data dependencies. Deletion of default data without due consideration may decelerate your accelerator. Spreadsheet Upload/Multi Record Delete Spreadsheet upload is helpful for answering setup questions with high volume responses such as accounting segment values and accounting periods. The Upload process is additive; if there are values you no longer need, it is best to delete them prior to upload. When you select to use Spreadsheet Upload, a spreadsheet may be downloaded which includes a list of values for each field, or the appropriate data format to use. Click Spreadsheet Upload button to begin the process. The Spreadsheet Upload window appears for the selected question. Click the Flashlight to download a spreadsheet template for collecting data. Complete the spreadsheet with data for the implementation. When ready, find the file and upload it to the Configuration Tool. The spreadsheet features datatype validation based on what the Configuration Tool requires. It also includes lists of values to minimize data entry errors. In some cases where the field refers to responses from a previous question, the list of values will reflect these. You may also delete setup values en masse where Spreadsheet Upload is enabled. You simply choose Select All, then click Go for Delete. .

Project Implementation Guidelines

Key Concepts 8 of 37

Accelerators can be used in implementation for any organization regardless of size, including those having complex requirements. Specific exceptions can be determined by thoroughly reviewing the Constraints and Defaults tab in the Accelerator or Key Assumptions document for the target solution.

Accelerator Implementation Project Lifecycle

The Oracle Business Accelerator project lifecycle is divided into 4 stages. Each stage represents a major classification of activities necessary for an implementation project using Oracle Business Accelerators. The first three stages of the implementation life cycle are directly impacted by your decision to Implement E-Business Suite using Oracle Business Accelerators. Sales Cycle: Business Development and Pre-Project activities. Project Preparation: Project Start through Data Collection and Preparation activities. Accelerator Execution: Configuration of E-Business Suite using the Setup Loader. Additional Activities: Post Accelerator Configuration Activities to Production.

Accelerator 12 Step Implementation Method

The Accelerator Project Lifecycle is further divided into 12 high level processes comprising the Oracle Business Accelerator Method. The Oracle Business Accelerator Method is a completely new and revolutionary implementation method that encourages movement toward global standard business processes configured in a rapid timeline. The remainder of this document will focus on the detail of each process step in the Method.

Project Implementation Guidelines

Key Concepts 9 of 37

Project Implementation Guidelines

Key Concepts 10 of 37

Sales Cycle
The ultimate success of an Oracle Business Accelerator project begins during the sales cycle. The Sales Cycle stage of the OBA Implementation Method includes Scoping, Bid Development and Acceptance. During the Sales Cycle the sales team: Educates the customer on the Accelerator implementation approach. Determines high-level requirements. Assesses the applicability of an Accelerator solution. Prepares a scope and submits a proposal. Provides a setup questionnaire to jump-start the discovery process.

1.0 Scoping
1.1 Identifying an Accelerator and Assessing Accelerator Fit The Oracle Business Accelerator must be run against a fresh install of the applications. Consequently, they can only be utilized during the first phase of a phased implementation approach. The Oracle Business Accelerator cannot be used to upgrade or add functionality to an existing Oracle E-Business Suite installation. The Oracle Business Accelerators are available in various industries and countries. Selecting an Accelerator that is closely aligned with the customer profile allows more customer requirements to be covered by standard Accelerator business flows. Below is a list of client information you need to collect in order to select an Accelerator best fit for the client implementation: 1. 2. Country of operation Each Accelerator is built to address country and region localization requirements. Hence, implementers should only utilize the Accelerators in the countries where they are available. Company industry - While the Oracle Business Accelerator for General Business covers requirements for a typical discrete manufacturing company, other industry-specific Accelerators provides flows and

Project Implementation Guidelines

Sales Cycle 11 of 37

features tailored for those industries. An appropriate industry Accelerator should be used if it is available in the country. 3. Functional area to implement This determines the flow family selection. Choose the flow families in the Accelerator that cover the functional area to implement. You might need to weigh between an industryspecific Accelerator and General Business, based on the covered functional area for the client. The features and flows in the selected Accelerator may not cover all the client requirements. Additional products and flows are to be configured after the Accelerator creates the project master instance. 1.2 Key Accelerator Assets Used for Fit Assessment Datasheets: Provides a snapshot description including key features and benefits as well as business functions and applications included. Solution Footprint: Provides a list of business flows, functions, and product applications included. Functionality Overview: Provides a list of implemented functionality by business flow. Constraints and Defaults : Describes important Accelerator settings and limitations.

These documents are available for each Accelerator solution at https://accelerators.oracle.com/.

2.0 Bid Development

2.1 Staffing an Accelerator Project The staff required for a project varies according to the project complexity, schedule, budgets, and the level of skill. The Oracle Business Accelerator facilitates the implementation of the Oracle E-Business Suite but does not replace the experience and the competency of the consultants. A typical Accelerator project with simple organization structure should consist of: 1. 2. 3. An experienced Oracle Financials consultant (at least three implementation projects) A functional consultant for each functional area such as Supply Chain, Manufacturing, etc. An experienced Oracle Applications Database Administrator (on part-time basis) trained on Accelerator installation and administration.

Refer My Oracle Support article Leading Practice: Staffing an OBA Project (ID 456202.1). Accelerators can also handle complex organization situations. The project consideration in complex project situations should be : 1. 2. More effort is needed to gather the responses if the seeded values do not satisfy the project requirements. The implementer also needs to collect more setup responses from the client organizations. The effort to communicate and coordinate with different organizations increases dramatically as well as the effort to enter the setup responses onto the online questionnaire and the time to run the Setup Loader.

The project will require additional resources for activities such as custom reports, integration, and go-live training/support.

3.0 Acceptance
Typical Sales Close activities are the same for an Accelerator implementation project as with any implementation project. After the client has accepted the bids, evaluated and awarded the contract to the chosen implementer, the implementer sales team transmits the scope to the client as part of the contract. Preliminary plans are communicated as to the proposed project schedule. One activity that is unique to Accelerator deals and is absolutely critical to moving quickly in an Accelerator implementation scenario is the handoff of the Setup Questionnaire to the client. The sales team should attempt to introduce the Project Manager to the client and handoff to the client at that time the Setup Questionnaire.

Project Implementation Guidelines

Sales Cycle 12 of 37

The Intent of the Setup Questionnaire is to serve as a preliminary discovery tool for the client to complete with all of the information necessary for the delivery team to begin the first week of the implementation. This questionnaire should represent the key implementation setup decisions. During the initial days of the implementation, the delivery team (implementation team) will review the clients responses and use these as a basis for conversation and planning of the setups with the client key personnel. For Further Reference: Oracle Business Accelerator Setup Questionnaire and Worksheet

Project Implementation Guidelines

Sales Cycle 13 of 37

Project Preparation
The Project Preparation stage begins prior to the arrival of implementation consultants at the client site. The DBA must request the Accelerator software and the project team must request a project workspace, participate in a pre-project review and prepare for the upcoming project. During the first week of the project, initial meetings are held with the key client decision makers to review and approve all project planning materials. Additional meetings with client key business process owners are conducted to review the Oracle Business Flows and to review and plan for the accounting and organizational aspects of the implementation project. The implementation steps covered in this section are: Request & Install Software Request & Prepare Project Workspace Project Initiation

4.0 Request & Install Software

4.1 My Oracle Support: DBA Requests Setup Loader Utility An Applications Database Administrator (DBA) assigned to the Accelerator implementation project must request the Setup Loader Utility (SLU) software from Oracle via a Service Request (SR) in My Oracle Support assigned to the product Oracle Accelerators. The SLU includes all of the software required for an OBA installation. When the request is approved, the SR will be updated a with a Request Identification Number that valid for 5 business days from the day of the approval along with instructions for the DBA to obtain the SLU. The DBA should request the SLU in advance of the project start date. The lead-time for approval and delivery of the SLU is 3 Business Days excluding any time required to download the software. By requesting the software before the project team arrives at the client, the DBA will have the Setup Loader Utility ready and available before you need to create your instance. The DBA must download the SLU prior to the Project Managers requesting of a pre-project review. For Further Reference: OBA Implementation Plan and Checklist

Project Implementation Guidelines

Project Preparation 14 of 37

4.2 Download and Install Software After the Service Request is updated with a Request Identification number, the DBA may log on to Oracle Accelerators Online to download the setup loader utility. The DBA will click on the Release button under the E-Delivery section specific to the Release of software that has been requested. After reviewing the download instructions and accepting the Terms and Conditions, the DBA enters the Request Identification Number provided in the Service Request and proceeds with download of all the CDs. Before installation of the SLU, the DBA should confirm that the Linux server is ready for installation of the SLU. The DBA should refer to the Technical Installation Guide document to gather details on preparing the Linux server prior to installing the Accelerator SLU software. This document also provides details on all required Operating System patches that need to be applied by the Linux System Administrator. After preparation of the Linux environment, the DBA may then commence with the installation of the SLU software on the target Linux hardware following the Technical Installation Guide. For Further Reference: Frequently Asked Questions - Release 12 Installation (ID 430777.1) Hardware and patchset requirements for installation of Oracle Accelerator (ID 419684.1) Leading Practice: Setup Loader Utility Install (ID 456200.1) OBA Diagnostic Utility for e-Business Suite Available (ID 549683.1) Accelerator Implementation Plan and Checklist Technical Installation Guide (Contained in the downloaded SLU software). 4.3 Applications Database Backup Initial Environment After a successful installation, the Database Administrator must take a complete applications database backup of the Oracle E-Business Suite Instance. This backup may be used for multiple projects using the same Accelerator. The DBA can use the Accelerator Diagnostic Utility to identify any anticipated installation issues and resolve them accordingly. The DBA should not apply any patches on this instance until after the Accelerator setups and post setup steps are complete, and no transactions have been posted. 4.4 Milestone: Installed Applications Environment The initial Oracle E-Business Suite applications environment is ready for configuration. The functional implementation/delivery team will enter setups in an assigned Accelerator Project Workspace and verify the entries. Once completed, the functional team may request the Configuration Tool Template download from this installed applications environment and begin the configuration process.

5.0 Request & Prepare Project Workspace

5.1 Request Pre-Project Review To request a pre-project review, the project manager must log a Service Request on My Oracle Support against 'Oracle Accelerators' product (ID: 1690) with the Request Category Request Pre-Project Review. The Accelerator Helpdesk team will update the Service Request with conference call details. The Project Manager and entire project team, including the DBA should participate on the call. This review is designed to be completed in a conference call and should take no longer than 30 minutes to complete. Project Managers: You must include all members of the project team using the Accelerators in the request for a project workspace at the time of the original request. Details should include: Consultant Name Oracle Single Sign-On ID Corporate E-mail ID Area of expertise, years of Oracle Applications experience

5.2 Request Project Workspace Every project is associated with a unique Project Workspace. To request a Project Workspace, the project manager must log a Service Request on My Oracle Support against 'Oracle Accelerators' product (ID:

Project Implementation Guidelines

Project Preparation 15 of 37

1690) with the Request Category Request Project Workspace. In this request, the Project Manager must specify the accelerator build requested, Release of the application and other details. The project manager must update the SR with the list of consultants who will participate in the project. A Pre-Project Review is conducted to qualify the project team to receive the project workspace. Project Managers must include all members of the project team using the Accelerators in the request for a project workspace at the time of the original request so that the project team members will be provided access to the workspace. Details should include: Consultant Name Oracle Single Sign On ID Corporate E-mail ID Area of expertise, years of Oracle Applications experience

To qualify for Project Workspace access, either for an Implementer Workshop or Internal Training, consultants must have completed Level 3 training. Consultants can be part of project workspace for client implementation as long as they have completed the Implementer Workshop for the same release of Oracle E-Business Suite as the one being implemented by the client. The request for the project workspace should be made only when ready to begin the configuration of the E-Business Suite using the Configuration Tool. The project workspace is active for 21 calendar days only, so implementers must use their time wisely. Much of the business requirements and data gathering process can be completed in BROWSE Mode at https://accelerators.oracle.com, and should be complete before you raise your request (see My Oracle Support Note 456205.1). Schedule Your Requests: Ask for the workspace to be available when you believe you will have the customer data and setups ready. The implementer may request a Configuration Tool Template from the Project Workspace as many times as is required prior to expiration of the Project Workspace. For example, you may input responses, download the template and run the Setup Loader, fine tune responses in the Project Workspace, then download the template and run the Setup Loader again. This process can be repeated as often as required during the life of the Project Workspace. Project Workspace Expiration Accelerator Project Workspaces are available for 21 Days 5.3 Pre-Project Review The pre-project review is to ensure the project team is familiar with the Accelerator assets and are ready to use the Accelerator on the client implementation. Some of the topics covered during this review are: 1. 2. 3. 4. 5. Project Team size, training levels and application skills Understanding of the key Accelerator implementation issues Understanding of the critical OBA assets such as Key Assumptions, Project Implementation Guidelines, and Technical Installation Guide. Knowledge of the issue resolution process and requesting assistance from the Accelerator team Key project information such as Org structure, flow families to implement, and data volumes.

Before this review, the team members must review the My Oracle Support article Oracle Business Accelerators Keys to a Successful Implementation Experience and also read the articles posted in the My Oracle Support Oracle Business Accelerator Knowledge Browser Product Page. The project manager must decide on the ownership of the workspace during the pre-project review. The manager must also provide the list of members who need to be added to the workspace during the review, after ensuring that they have completed the requisite training (more members can be added if required at a later stage). Continuity of ownership is important. Project teams should ensure that the project manager assigned to the workspace is available for the entire duration of the workspace. After the Pre-Project Review meeting, the Accelerator team will grant the project team access to the requested Project Workspace. Access to a Production Project Workspace is good for 21 business days. 5.4 Project Workspace Granted

Project Implementation Guidelines

Project Preparation 16 of 37

Project Workspace access will be granted ONLY after completion of the Pre-Project Review. Once approved and completion of training and pre-project review requirements have been verified, a project workspace will be allocated on the date requested by the implementer.

6.0 Project Initiation

6.1 Review Final Scope The implementation team confirms the Accelerator and flow families to implement for the client, walks through the major implementation stages, and shares project materials such as Functionality Overview and Key Assumption documents, and sample flow scripts. The objective of the Accelerator is to create an instance with selected business flows enabled. Any additional features and functions should discuss and handled separately. The client Project Manager and the Implementation Team Project Manager review the work plan and obtain the approval from the client Executive Sponsors. 6.2 Conduct Flow Review Begin by conducting a brief overview of Business Flows using the What are Business Flows? presentation included with the Oracle Accelerator. The client Business Process Owners must understand what is meant by business flows and the intent for beginning with predetermined business processes. Next, Implementer SMEs review specific Flow Models with the client Business Process owners. At this point implementers are laying a foundation for common understanding of the standard business processes and use this review with the client as a starting point in the discussion to determine if there are any high-level gaps. The Business Flows tab contains links to the flow-specific assets that you should use as part of your Business Flow Review process with the client: Flow Model Flow Video

A Flow Model depicts the show the sequence in which business processes are typically completed by the end user in an end-to-end business transaction. Oracle Business Accelerators use the Flow Models to show how Oracle can solve specific business problems. A process flow with this easy-to-recognize content, customers come to agreement on the requirements more quickly, thereby reducing implementation effort and time. Process flows allow the implementer to quickly establish credibility and rapport with customers and accelerates your discovery because the implementation focus is on the business processes and not the minutiae of setup details in a setup document. Flow Videos demonstrate how the flows are performed in Oracle E-Business Suite and are useful to help the client visualize how the business processes can be addressed in Oracle. 6.3 Gap Analysis When gaps are identified, the implementer must strive to determine if the gaps raised are a result of a general misunderstanding of the flow model, the result of a clients processes, requirements that are believed to be needed but serve only to provide some link to or function of a legacy system that is not needed or no longer in use. Oracle Business Accelerators also accomplish business process realignment to a standardized process. Implementers should be moving clients toward a standard or leading and more efficient practices and away from needless customizations. You should therefore eliminate all customizations that are not the result of truly unique business requirements. Key Assets used in Gap Analysis Flow Models Flow Videos Functionality Overview

Project Implementation Guidelines

Project Preparation 17 of 37

These documents are available at https://accelerators.oracle.com/. 6.4 Accounting and Organization Planning The client functional leads provide feedback on the proposed organization and accounting structure during the initial discussions with the project team. The implementation team needs to ensure the client functional leads understand the impact of organization structure in the product configuration. The project team should arrive an organization and accounting structure accepted by the client team. For Further Reference: Discovery Questionnaire and Worksheet OBA Implementation Plan and Checklist

Project Implementation Guidelines

Project Preparation 18 of 37

Execution
The Accelerator Execution phase constitutes the core of the Oracle Business Accelerator implementation project. The implementation steps covered in this section are: Enter Setup Data Applications Configuration Validation and Acceptance Testing

7.0 Enter Setup Data

7.1 Review Setup Questionnaire The Implementation Team should review the setup questionnaire completed prior to the commencement of the project by the client. The information in this document will form the basis for conversation with the client regarding the organizational and accounting structure. The implementers who are understood to be the expert in Oracle E-Business Suite must consider the responses provided by the client and assist the client with the development of the most appropriate structure for the implementation. The Implementer should use the Setup Questions Worksheet provided in the Project Workspace as a guide to gather and document data for the setups. Although the Setup Questions Worksheet covers only some key questions implementers may modify the spreadsheet to include other relevant questions and relevant data required for configuration. 7.2 Enter Setup Data in Project Workspace 7.2.1 Access the Project Workspace Navigate to the Project Workspace tab. The Project Workspace tab lists all previously requested Accelerators. For each Accelerator the project information status and the expiration date is displayed. The expiration date reflects when the Project Workspace will become inactive. Click on the Accelerator name in the left column to access it.

Project Implementation Guidelines

Execution 19 of 37

7.2.2 Select Flow Families The Project Workspace will determine the collection of setup questions required to support the corresponding flows based on the flow families selected. Each Accelerator solution has its own combination of flow families available for selection. Consult the Functionality Overview document to determine the flow families available for a particular accelerator solution. After choosing flow families, click on Proceed to Setup Questionnaire button.

7.2.3 Answer Common Key Business Questions The Common Key Business Questions include the key configurations for the Accounting and Organizational structure. These setups include the Accounting Key Flexfield, Calendar, Currency, Ledgers, Business Group, Legal Entity, Operating Unit and Inventory Organization. These questions must be answered prior any other questions in the Project Workspace. All questions in this section are provided with default responses that may be modified to match client requirements. Questions in this section must be answered in the order of appearance in the hierarchy.

Project Implementation Guidelines

Execution 20 of 37

7.2.4 Answer Specific Business Flow Questions Specific Business Flow questions are hierarchies of questions organized by application. Most of the answers to questions in this section will also come with default values that may be updated to match client requirements. You may also add or delete client specific values where appropriate. You may add multiple rows of data. The tool will generally allow deletion or modification of records in this section.

Generally speaking, product nodes under Specific Business Flow Questions may be answered in parallel. However keep in mind that some questions have data dependencies across product nodes. Fields with data dependencies indicate through the field hint where the source question is for that data. Respond to all questions presented. When you are finished answering the questions click on Proceed to Review and Verify, located at the bottom of the questionnaire, to review and validate the status of the questions.

Project Implementation Guidelines

Execution 21 of 37

7.3 Review and Confirm Setups To minimize the number of Setup Loader iterations and stops, the project manager and the business area leads MUST review the data on the workspace and ensure accuracy and completeness before requesting for template download. Most of the issues encountered during Setup Loader run are due to data input errors. The typical conditions that cause the Setup loader execution to stop during the configuration process are: 1. 2. 3. 4. 5. Invalid Flexfield code combinations. Data of an inappropriate length or type. Duplicate records. Incorrect data for the record being entered. Mandatory data missing.

All of the conditions above will cause Setup Loader stops. These conditions can be avoided by careful entry and validation of data in the Project Workspace. Review and Confirm Setups page

Review your list of Questions report indicates whether a questions responses have been modified. A check mark ( ) next to the questions entered or modified.

Project Implementation Guidelines

Execution 22 of 37

Verify your Responses report allows you to browse each of the questions, and by clicking the flashlight icon for a question you can see the values entered. Click on the flashlight icon to see the data entered for a particular question.

Questions With No Responses report indicates the questions that have no responses, and includes the Configuration Tool tree navigation so you can navigate to and enter data for the missing setup.

Project Implementation Guidelines

Execution 23 of 37

Once all setup values have been entered and validated, and you are ready to proceed to setup the EBusiness Suite. Close any Oracle Accelerators Online screens and log in to the locally installed environment to request and import the Configuration Tool Template.

8.0 Configure Applications

8.1 Request Setup Data File The Project Workspace owner must login to the applications environment as user OA_IMPLEMENTER with password welcome to request the Configuration Tool Template (setup data file). Choose the Oracle Business Accelerators responsibility and click the Setup hyperlink. Step 1: Provide Customer Information for Configuration Tool Template

Provide the relevant project information such as the Project Workspace Owner username and password, Customer Name, Customer CSI#, Partner Company Name, Contact Name and Phone Number. After entering this data, click the Proceed to Step 2 Button. Step 2: Review Project Information & Submit Request

Review the entered project information and click the Go Back to Step 1 button to correct any discrepancies. After confirming the entered data, launch the request for the template download by clicking the hyperlink Click here to request Configuration Tool Template Download. The request is

Project Implementation Guidelines

Execution 24 of 37

automatically fulfilled electronically within 1-2 hours. Once the request is fulfilled, the requester is sent a workflow email notification via email confirming that the template is available for download.

8.2 Import Setup Data File Step 3: Load Configuration Tool Template

Once the workflow email is received, click the link Click here for Direct Delivery of the Configuration Tool Template. This will generate a process to load the setup data file. While the import/load is in process you will see a message at the bottom of the screen indicating that the Configuration tool Template load is in Progress. When this process completes, a popup window will confirm the successful completion of the setup load. Attention: The import process will overwrite any previously imported Configuration Tool Template. Use this feature carefully. 8.3 Execute Setup Loader and Perform Any Manual Runtime Setups After successful import of the setup data file, the configuration tool is ready to perform the configuration of an Oracle Business Accelerator instance. Step 4: Start Setup Load

Before starting the Setup run, click on View Your Responses. Here implementers may review and verify setup responses imported into the Configuration Tool. Manual and Post Setup Steps Most Oracle Business Accelerators have some manual and post setup steps that must be performed. The implementer must monitor the setup load and be prepared to perform manual steps when prompted for a manual setup by the setup loader. These manual steps must not be skipped and should be performed immediately to prevent delaying the setup process. The manual steps and post setup steps are provided via the following hyperlinks on the Step 4 page.

Project Implementation Guidelines

Execution 25 of 37

Manual Steps link The first link opens the Manual Setups document. During the automated setup process the Setup Loader will prompt you to perform certain manual setups. Once you perform the prompted manual setup, you can resume the automated setup process. The Manual Setups document included a list and details of these setups. Post Setup Steps and Additional Post Setup Steps links The links open the Post Setup Steps and Additional Post Setup Steps documents. These documents contain the details of manual steps that are to be performed after the automated setup process has completed. These steps are mandatory to complete a successful instance setup. The Configuration Tool generates the contents of this document based on flow families that were selected previously. As a final check before executing the run, do the following: Verify that your browser is supported by the Oracle Business Accelerators. Ensure that the Display variable is set appropriately. Check the client machine running the configuration tool and verify that it has at least 1 GB memory, although higher memory is strongly recommended Ensure that the server hosting your instance does not have any other instances running at this time. Also, insure that the server has enough memory. Confirm that your DBA has performed ALL required post-setups as documented in Technical Install Guide BEFORE commencing the Setup Loader Ensure the E-Business Suite Forms-based application window has been opened once on the system. To test this, login to the E-Business Suite as Sysadmin with the password provided by your DBA and open an Oracle Forms-based application window. Refer to the Technical Installation Guide for complete client configuration requirements. Download and print the following key documents. Manual Setups, Post Setup Steps, and Additional Post Setup Steps

Begin Execution of the Setup Loader Finally to begin execution of the configuration tool, click the Start Setup button. The Setup Loader will begin from this point and at least one member of the project team should monitor the run and intervene with manual steps as required.

Configuration/Setup Monitor

Project Implementation Guidelines

Execution 26 of 37

The Setup Loader opens a Setup Monitor window while running. This window indicates progress towards instance configuration. The number of steps varies, depending on the Accelerator solution and the volume of data entered. The Setup Loader will run from this computer, so be sure to select the right clientfor example, dont start it on a laptop at 5:00p unless the intent is to leave it there. Or, dont run it from a computer that does not have the jInitiator installed. Once you execute the Setup Loader, it is very important that you closely monitor the instance configuration since the Setup Loader will pause at various intervals for you to perform manual setups. If the Setup Load process is interrupted, you can resume by navigating to the Setup tab. By clicking Resume Setup, the process will continue where it left off. In certain cases, the application window opened by the Setup Loader might freeze. The Setup Monitor detects these errors and pauses, providing an option to proceed when ready. If this happens, login to the application through a separate browser and enter the correct data in the application. Verify the error, fix manually the setup and proceed. Further information regarding error scenarios and the resolutions for these cases can be found on note 412485.1. When the Setup Load is complete, the following page is displayed:

In addition to Post Setup Steps and Manual Setups, this page shows other helpful links. View Errored Setups This is a report of any errored setups that did not complete successfully during the automated setup process. View Setup Load Run Statistics

Click on Statistics to view information about how much time was spent responding to the questions, and how much time was required to complete the setup load. 8.4 Perform Post Configuration Steps The Post Setup Steps and Additional Post Setup Steps documents contain the details of manual steps that are to be performed after the automated setup process has completed. These steps are mandatory to

Project Implementation Guidelines

Execution 27 of 37

complete a successful instance setup. The Accelerator generates the contents of this document based on flow families that were selected previously. 8.5 Configured Applications Environment After completion of the automated Setup Loader and the manual Post Setup Steps, the implementation team may configure any additional applications or functionality required to satisfy client requirements or may be in scope. 8.6 Backup Configured Applications Environment The Applications DBA should perform a complete Applications database backup prior to execution of flow scripts. This backup will be used to develop additional environments for development of customizations, data conversions, and for refresh of the environment.

9.0 Validation and Acceptance Testing

9.1 Execute Flow Scripts After the completion of the Setup Loader execution, client functional leads and key system users should perform extensive and detailed flow and transaction testing to confirm the baseline configuration. Every flow script (and included functionality) should be tested end to end with client data to match as closely as possible the operational environment as it will be upon production cutover. Most importantly, the monthly close cycle should be executed with the key accounting staff and attention of Financial Management. 9.2 Identify Changes and Integrate (As Required) Execution of the flow scripts may uncover setup changes required. If changes are required, they frequently can be accomplished directly in the instance without rerunning the Automated Configuration Tool. These changes should be added to a refresh of the database from the recent backup (Step 5.6). However, some changes have such impact that they cannot be changed once they have been entered. In these cases, the changes can be made directly to the Project Workspace while the instance is being refreshed to its Pre- Configuration state from the prior backup. 9.3 Post Project Review with the OBA Team A Post Project Review provides an opportunity to debrief the Oracle Business Accelerator team on use of the Accelerator for the client. Implementers provide valuable feedback during this conference with Oracle. This feedback is critical to continuous improvement of the Accelerator solutions. Implementers may also pose questions and make requests for enhancements during this session. The project manager must initiate the review by contacting the Oracle Accelerator Helpdesk via Service Request 'Oracle Accelerators' product (ID: 1690) with the Request Category Request Post Project Review. This should be logged immediately upon completion of the Validation and Acceptance of the Pre Production configuration, signaling that the production workspace is no longer needed. The Oracle Business Accelerator Project Review Team will arrange for a teleconference with the Implementation team and the Project Manager. Contact details like cell phone number, availability, time zone, etc must be mentioned in the SR. The post project reviews are usually conducted during India business hours. 9.4 Client Approves Baseline Configuration The client functional area leads should prepare a status briefing to key decision makers along with a recommendation to either approve or revision of the configuration. The client functional leads should work with the implementation team to develop a roadmap to Production for approval of client management. The client management and executive sponsors should review the reports from the project team and approve as appropriate.

Project Implementation Guidelines

Execution 28 of 37

Post Accelerator Activities

Planning and development of additional functionality, conversions and customizations may begin as early as the first week of an Accelerator implementation project. Upon completion of the Execution stage of the project, any additional functionality, applications, patches, and/or localizations not included in the Oracle Business Accelerator may be applied. Integration with 3rd party applications, interfaces, data conversions, custom reports and custom applications may also be applied after the Execution stage to satisfy client requirements.

10.0 Additional Functionality

10.1 Localizations The flows included with the Oracle Business Accelerators are designed to comply with the regulations and leading business practices of a designated country. If the client has organizations outside of the designated country for which an Accelerator was intended, additional manual configuration and the addition of localizations may be required. The project scope should dictate what applications and functionality will be implemented for the client during the project, whether configured by the Oracle Business Accelerator or manually by the implementation team. Enabling localizations may require: additional setups, localization patches, additional applications license and potentially some integration with 3rd party software packages. Localization activities must be incorporated into the overall project plan. The design and development of localizations may be performed in parallel to the Project Preparation and Execution activities but the final setup and testing may only be permitted after configuring the baseline applications instance. Depending upon the number of iterations during the Execution stage, you may be able to begin early testing of localizations. 10.2 Patches Additional patches may be required to incorporate select features not included in the Applications configured using the Accelerator or as part of an ongoing maintenance and improvement plan. It is common practice to bring the applications instance to the latest major maintenance pack to minimize patching activities later in an implementation project. However, the Accelerator comes packaged with the patches required for the functionality included with the business flows. Any additional patching or technology stack upgrade must be performed only after the Execution stage of the project on the baseline instance. After patching is complete, the project team should perform complete testing of the applications flows to re-validate the instance and to identify any problem areas.

Project Implementation Guidelines

Post Accelerator Activities 29 of 37

10.3 Products and Advanced Functionality The Accelerator includes typical applications functionality utilized across Oracle E-Business Suite applications. The business flows should not be construed to encompass all of the rich and varied functionality available within Oracle E-Business Suite applications as this solution is intended to satisfy requirements for the broadest segment of the target market. The implementer is not limited to the setups provided by the Oracle Business Accelerator. Additional functionality is available in the E-Business Suite and may be utilized at the implementers discretion to satisfy client requirements provided that the additional functionality is included in the clients E-Business Suite software license agreement and is in the scope of the project. Configuration of additional applications or application functionality not included in the Accelerator should be performed manually after the completion of the Oracle Business Accelerator Setup Loader and manual setups. Implementers may choose to configure the business flows from any one or all of the included business functions packaged with the Accelerator. There is no requirement to implement all of the functions or flows included in the footprint for this solution using the Accelerator Configuration Tool. However, any setups related to flows not chosen by the implementer may not be configured by the Accelerator and therefore must be configured manually after the Configuration Tool has been executed and manual steps completed.

11.0 Conversions and Customizations

11.1 Data Conversions The Oracle Business Accelerator does not impact the design of data conversion programs since the Accelerator does not change E-Business Suite database schema. The design, preparation, and development of data conversion programs should be done in parallel to the Accelerator activities. Installation and testing of data conversions may begin on a baseline instance configured during the Execution stage of the project. However, final data conversion testing and certification must be done only after the Execution stage has been completed and the baseline instance has been approved. 11.2 Application Interfaces The planning, design and development of application interfaces and 3rd party applications integration programs should be performed in parallel to the accelerator activities. Installation and testing of these components may begin on a baseline instance configured during the Execution stage of the project. However, final testing and certification must be done only after the Execution stage has been completed and the baseline instance has been approved. 11.3 Reports and Customizations The development of customization components such as reports and forms should be performed in parallel to the accelerator activities. Installation and testing of these components may begin on a baseline instance configured during the Execution stage of the project. However, final testing and certification must be done only after the Execution stage has been completed and the baseline instance has been approved.

12.0 Transitioning to Production

Execution of the final phase of an Oracle Business Accelerator implementation, the Transition to Production stage is the sole responsibility of the implementation team and the client decision makers. After the configuration of the Pre Production Baseline, the Accelerator does not provide any additional tools, resources, or guidance. Implementers should pursue their traditional implementation approach as relates to the tasks during this final stage. The typical implementation steps to be accomplished by the implementer and client during this stage include: 12.1 Modify/Develop Policies and Procedures 12.2 User Training

Project Implementation Guidelines

Post Accelerator Activities 30 of 37

12.3 Final Acceptance Testing 12.4 Disaster Recovery Plan 12.5 Production Cutover 12.6 Performance Tuning 12.7 Periodic Maintenance and Backups

Project Implementation Guidelines

Post Accelerator Activities 31 of 37

Accelerator Implementation Plan and Checklist

# Implementation Step Status Completion Date Responsibility Approvals Required/Reference

Sales Cycle
1.0 2.0 3.0 Scoping Bid Development Acceptance Complete Complete Complete Pre Project Pre Project Pre Project Sales Team Sales Team Sales Team Discovery Questionnaire Scope

Project Preparation
4.0 4.1 4.3 4.4 4.5 5.0 5.1 5.2 5.3 5.4 6.0 6.1 6.2 6.3 Request & Install Software My Oracle Support: OBA Requests Setup Loader Utility (SLU) Software Download and Install Software Applications Database Backup Initial Environment Milestone: Installed Applications Environment Request & Prepare Project Workspace Request Pre-Project Review Request Project Workspace Pre-Project Review Project Workspace Granted Project Initiation Review Final Scope Conduct Flow Review Gap Analysis Not Started Not Started Not Started DD/MON? DD/MON? DD/MON? Client Functional Lead Implementer Functional Lead Client Functional Lead Implementer Functional Lead Client Functional Lead Implementer Functional Lead Client Functional Lead Implementer Functional Lead Client Functional Lead Implementer Functional Lead Client Functional Lead Implementer Functional Lead Not Started Not Started Not Started Not Started DD/MON? DD/MON? DD/MON? DD/MON? Project Manager Project Manager Project Manager/Implementer Functional Leads Oracle Business Accelerators Oracle Business Accelerators Complete Not Started Not Started Not Started Pre Project DD/MON? DD/MON? DD/MON? Database Administrator Database Administrator Database Administrator Database Administrator

Project Implementation Guidelines

Accelerator Implementation Plan and Checklist 32 of 37

# 6.4

Implementation Step Accounting and Organization Planning

Status Not Started

Completion Date DD/MON?

Responsibility Client Functional Lead Implementer Functional Lead

Approvals Required/Reference Client Functional Lead Implementer Functional Lead

Accelerator Execution
7.0 7.1 6.2 6.3 6.4 8.0 8.1 8.2 8.3 8.4 8.5 8.6 9.0 9.1 9.2 9.3 9.4 Enter Setup Data Review Setup Questionnaire Enter Setup Responses in Project Workspace Review and Confirm Setup Responses Iterate from Step 4.0 through Step 6.3 as Required. Configure Pre Production Applications Request Configuration Tool Template Download Import Configuration Tool Template Execute Setup Loader & Perform Any Runtime Manual Setups Perform Post Setup Steps Backup Configured Pre Production Environment Milestone: Completed Pre Production Baseline Validation and Acceptance Testing Client Executes Flow Scripts Identify Changes and Integrate (As Required) Post Project Review with OBA Team Client Approves Baseline Configuration Not Started Not Started Not Started Not Started DD/MON? DD/MON? DD/MON? DD/MON? Client Functional Leads Implementer Functional Leads Client Functional Leads Implementer Functional Leads Project Team, Project Manager, OBA PPR Team Client Functional Leads Client Functional Leads Not Started Not Started Not Started Not Started Not Started Not Started DD/MON? DD/MON? DD/MON? DD/MON? DD/MON? DD/MON? Project Manager/Implementer Functional Lead Project Manager/Implementer Functional Lead Project Manager/Implementer Functional Lead Project Manager/Implementer Functional Lead Database Administrator Not Started Not Started Not Started DD/MON? DD/MON? DD/MON? Project Lead Project Lead Project Lead Project Lead Project Lead Project Lead

Post Accelerator Activities

10.0 Additional Functionality

Project Implementation Guidelines

Accelerator Implementation Plan and Checklist 33 of 37

# 10.1 10.2 10.3 11.0 11.1 11.2 11.3 12.0 12.1 12.2 12.3 12.4 12.5 12.6 12.7

Implementation Step Localizations Patches Products and Advanced Functionality Conversion and Custom Data Conversions Application Interfaces Reports and Customizations Production Modify/Develop Policies and Procedures User Training Final Acceptance Testing Disaster Recovery Plan Production Cutover Performance Tuning Periodic Maintenance and Backups

Status Not Started Not Started Not Started

Completion Date DD/MON? DD/MON? DD/MON?

Responsibility

Approvals Required/Reference

Not Started Not Started Not Started

DD/MON? DD/MON? DD/MON?

Not Started Not Started Not Started Not Started Not Started Not Started Not Started

DD/MON? DD/MON? DD/MON? DD/MON? DD/MON? DD/MON? DD/MON?

Project Implementation Guidelines

Accelerator Implementation Plan and Checklist 34 of 37

OBA 12 Step Implementation Method

Project Implementation Guidelines

OBA 12 Step Implementation Method 35 of 37

Oracle Business Accelerator Discovery Questionnaire and Worksheet

Question Count Details Guidance

Organizational Geography
How many business locations do have (Offices, Manufacturing, Sales, Distribution, et cetera)? List your Organizational Locations. Record each location to be assigned to an Organizational unit (Office, Warehouse, Service Center, et cetera). . Locations outside the home/default country of the accelerator may or may not be defined within the Configuration questions depending upon the version. A Business Group is typically required for each country jurisdiction where you have employees. The default Business Group reflects the Country for which the accelerator has been based.

Business Groups
In what Countries do you conduct business? List All Of the Countries listed above, how many will be subject to this implementation?

Accounting Legal Entities/Legal Entity

What are the Various Currencies (Functional and Transactional) do you require to conduct business. What organizations are your legally registered entities? Identify any legal and reporting requirements that may vary locally by country? Discuss any Tax reporting requirements. Will you need the Oracle MRC functionality? For unstable currency fluctuations? Do you have the need to operate with the Euro as a functional currency? What data within your organization is regarded as sensitive? Discuss Financial Data, HR/Employee Data, Sales, Customer, Supplier, etc Additional Functional and Transaction Currencies may be defined within the Configuration questionnaire. Each legally registered entity for tax, legal and an Accounting Legal Entity and LE Government Reporting Entity should represent reporting purposes.

Ledgers/Sets of Books
Are you involved with a fair number of acquisitions/divestitures on a regular basis? Are there any joint ventures involved with your company? What are your period close procedures, schedules and requirements for different organizations/divisions within your company? What kind of inter-company movements, reporting, and tracking do you require? Do you use Encumbrance Accounting? Project Implementation Guidelines Oracle Business Accelerator Discovery Questionnaire and Worksheet 36 of 37

Question What are your reporting requirements? Ie Subledger reporting? Do you have any divisional or country document sequencing requirements? What data within your organization is regarded as sensitive? Discuss Financial Data, HR/Employee Data, Sales, Customer, Supplier, etc Asset Corporate Books Asset Tax Books

Count

Details

Guidance

Same as Number of Ledgers Number of Asset Corporate Books x Applicable Tax Treatments

Typically you should have no more than one Fixed Asset Book for GAAP accounting purposes per Ledger. Every Organization should have at least a FEDERAL tax depreciation book but may also require ACE and/or AMT. Tax departments are typically small and very specialized. To most effectively manage assets for tax treatment, you should minimize the number of Corporate Books, one for each Ledger/Set of Books. Excessive Corporate books will require the same or more tax books.

Operating Units
How is your Business Organized? Divisional? Product? Service Oriented? Geographic? What is your distribution model? How are goods sourced?

Inventory Organizations
What are your Distribution Points? How Many Warehouses do you operate? What are your Manufacturing Sites Do you Maintenance Requirements? How do you Organize for your Maintenance requirements? What are the requirements for your Accounting Code Structure? If a Global firm, are you striving for a common accounting code or chart of accounts?

Project Implementation Guidelines

Oracle Business Accelerator Discovery Questionnaire and Worksheet 37 of 37