Different Stages in an Oracle Application Implementation

Project.... !

Hi All,
today we will be seeing the different stages that are available in an implementation project. A
Project is not a short term activity to be completed in matter of days, it requires intensive
analysis, thoughtful thinking and serious decision making in core and critical business activities.
There decisions taken at every stage is critical and irreversible, there is no going back after
performing final step. We have to understand how a long term project is broken up in to phases
and completed smoothly. We will see what are the different stages in an Oracle Application
Implementation project in real time. i have taken AIM standards as the base for further
explanations.

Application Implementation Methodology has laid out various stages available in a project.

Stage 1 - Definition of Project Management

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Description
========
The success to any project is a well thought of PROJECT PLAN at the very beginning
considering the requirements and available resources. A Normal Contention of many people is
that Project Plan should normally stage the Start Date and End Date and the Consideration, but in
real time it is actually many more that, the whole project is broken in to different phases and
for each phase a detailed plan is laid out which in turns account for the overall project plan.
Project Plan must be revised whenever there is a Change in the contract or requirement of the
client

Documentation to be Prepared
======================
Project Plan (Finalized or Draft)
Write up about the Client and the Consultant.
Stage 2 - Operational Analysis
~~~~~~~~~~~~~~~~~~~~~~

Description
========
This is the very very Critical stage of the Project. One must devote the maximum possible time
to this stage. Any compromise on this stage may prove critical at later stage of the project. In this
stage a Consultant, who is a total stranger to the client so far is going to make an effort to
become an expert in understanding the client business every inch. Only when he masters the
clients business, he will be in a position to think beyond it and provide solutions considering the
impact it can have on overall business. In this stage a consultant must carryout following
activities:
-- Clearly understand the contractual obligations made between the client and the consultant with
respect to the work to be performed.
-- Detailed study on the Client business and Organisation Structure
-- Capture the current business process as they are following ( Also known as AS IS
documentation)
-- Collect the requirements from the client, managers, end users as to what they expect from the
Oracle Product
-- Requirements with respect to Functional Side as well as Technical Side is collected
-- Document the bottlenecks faced with the existing system in place
-- Most important point is that get the document signed from the client
( Note: Normally speaking once a requirement is expressed at this stage , it will be taken care by
the consultant, however in real time, requirements gathering becomes a day to day activity in
many clients place, which is highly unprofessional way of working )

Documentation to be Prepared
======================

RD 10 --> Current Financial and Operating Structure

RD 20 --> Current Business Baseline
RD 50 --> Business Requirements Scenario
Stage 3 - Solution Design
~~~~~~~~~~~~~~~~~~~

Description
========

After making serious understanding and analysis on clients current business practices and future
requirements, consultant must begin the process of providing solutions to each and every aspect.
If an straight forward solution is not possible , think about the possibility of workaround. Enough
analysis has to be one in drafting the new business process of the client which is going to be
followed here after, it is also known as To Be Process.Once the solution is decided on, the same
must be communicated to the client seeking acceptance. when the client is satisfied with the
solution, consultant can put an end to his research work on providing alternate solutions.

Documentation to be Prepared
======================
BP 80 --> Business Process Design ( To be process )
BR 10 --> High Level Gap Analysis
BR 30 --> Business Requirements Mapping
MD 50 --> Application Extension Functional Design
MD 70 --> Application Extension Technical Design

Stage 4 - Building Stage

~~~~~~~~~~~~~~~~~~

Description
========

Only at this stage the work of performing setups and access to the instance begins. Based on the
Solutions and new business process ( To Be) designed at the previous stage, the consultant starts
performing setting up of the Application. In case of a functional requirement, it will be setups
from the front end, in case of technical requirements, sql scripts, customizations will be
performed. Document all the setups that has been carried out at this stage, since it will be useful
when the production Instance is configured or when there is a system crash or corruption of data
or any hardware failure. After performing all required setups, the system has to be tested for its
readiness to carry out operations

Documentation to be Prepared
======================

BR 100 --> Application Setup

TE 20 --> Unit Test Script
TE 40 --> System Test Script
TE 50 --> System Integration Test Script
TE 120 --> System Integration Test Plan

Stage 5 - Transition Stage

~~~~~~~~~~~~~~~~~~

Description
========

In this stage, client is exposed to the Applications for the first time to get the comfort level. In
order to make the client to get a feel of the system, user guides, training manuals and training
may be given in understanding how thier business is completly taken care by the product. Once
the client is exposed to the Applications, they normally tend to show some interest in learning
new things, which can be used for testing the system. Once the client is satisfied with the
Solutions and the way in which the system performs, he can express his willings to accept the
system. In real time, acceptance will be taken up at two levels,
First Level - CRP - Conferance Room Piloting - Where the consultant gives a preview of the new
system to the selected members of the client and get thier feedback.
Second Level - UAT - User Acceptance Testing - Here the consultant gives detailed
demonstration on the new system to the users ( Super and End ), and get the acceptance from the
users that the new system meet thier expectations.
Documentation to be Prepared
======================

TE 130 - User Acceptance Test Report

Stage 6 - Production Stage

~~~~~~~~~~~~~~~~~~

Description
========

Once CRP and UAT is approved, it is the duty of the consultant to replicate the same in a new
environment which will be used solely and exclusively for the Production purposes only. After
making the production server ready with all setups, it is advised to clone the production server to
an development or test server, so that any value addition or future testing can be carried out
separately in future. Once the production server is ready, it is given to the client to begin their
operations, which is termed as GO LIVE. In order to assist the client in adapting to the new
system, consultant will provide them with User Manuals and also a support consultant for a short
period of time if needed.
Once the production server is ready and used, the implementation gets over, and the client should
give it in writing that he is satisfied with the implementation taken place, which is termed as sign
off ( A Big Good Bye ) !!

Documentation to be Prepared
======================

User Manuals
Client's sign off on the Acceptance Certificate

NOTE:
=====
Documentations suggested in this post is recommended when AIM is adopted. Instead of the
recommended documents, users can prepare documents based on thier methodology.
Nothing stated above is mandatory, every aspect is recommendatory in nature.
Posted by Karthikeyanat 12:48 PM

Data Migration

Hi All,

today we will discuss on an important area in any implementation, which is migration of data in to Oracle

Applications Database. First data migration means moving of data from one place to another. Moving of data

does not mean a mere copy paste work, it means moving of Clean data (uncorrupted) in to proper database

tables.

Which data is going to be migrated?

When we are going to implement a new ERP like Oracle Financials, setups are carried out based on the

current business processes and policies, after setting up, we need access to past data in the application.

Why we need access to past data?

It may be a statutory requirement or companies requirement. Apart from which , it could be a normal

business requirement. Assume that you have customer who bought goods or services from you on March

2007 and he need to pay you 1000 USD by end of June 2007. And if we have implemented Oracle

Applications by May 2007, without past data, we will certainly loose the track of that customer, since the

new system will not say that how much needs to be received due to previous transactions. So in order to

account for Outstandings and Accruals one need to have access to past data. Apart from that , your opening

balances are a resultant figure of Past data.

At which stage of the project this data migration will come in to picture?

It happens before Go Live or one could say after User Acceptance Testing.

Who has to decide on what data should be migrated ?

It is the client who needs to decide what are the data that needs to be migrated since he is the one who is

going to access it. Client must also decide on how many years of data needs to be migrated. Assume that if

a company is doing manual accounting for 20 years and now they are moving in to Oracle Apps, they need

to decide whether they want access to all 20 years of data or they can decide a cut off date beyond which all

data will be migrated.

How data will be migrated ?

Depending on the volume of the data, the consultant will decide on the suitable methodology. He can go in

for data load or SQL scripts.

How data will be presented ?

Client must provide the consultant will the data in the prescribed format. It is the responsibility of the client

to authenticate the data which he gives to the consultant for migration, consultant is more interested on

how to move the data in to Applications, he is not expected to audit the data which you are giving. So client

must take effort to provide a Clean data.

How it will be ensured, that data migration is successful ?

After data migration, enough testing will be carried out to find the accuracy and completeness. After

migrating data, reports will be drawn out of the Oracle Applicaitons system and matched with the existing

figures based on the current system followed by the client. Only after 100% satisfaction, of both the client

and the consultant, data migration will come to an end.

How long this data migration will take to get complete?

It depends on the volume of data, if its going to be a newly started company the volume of data will be less,

hence migration may take only months, where as for companies wanting years of data to be migrated,

requires years including testing.

Who will migrate the data ?

Normally it will be a role of a Technical Consultant, if the data is very less, then a Functional consultant can

perform it by using dataload. Also it can be outsourced to any other firm apart from the consulting company

which implements oracle apps. There will be many companies which specialize in this area alone, one can

make use of them to perform this job.

What is CRP?. when do we go for it? and What kind of document we prepare for it?

What is the difference between CRP1, CRP2 and CRP3?

CRP Stands for Conference Room Piloting

The CRP Sessions are conducted to transform Oracle Applications knowledge to the customer before
conducting UAT (User Acceptance Test) and End User Training

The No.of CRP you need to have and when it needs to be conducted depends on Client Industry, Size of
Implementation and client knowledge in general about ERP applications.

I have implemented ERP solutions where customer migrate from one ERP to another. In those cases two
CRP sessions are enough.

If client does not have any idea about ERP, then it is better to have it three

CRP 1: Generally it is conduted at initial phase after you finish RD010 and RD020 - Basically to provide
an overview of Oracle ERP after understanding client Business

CRP2: Conducted after BP080 (Future Business Model) - Configure the system as per client Future
Business Model and Demonstrate. This will help you to identify the client expectation and prepare
BR010 Gap Analysis Document

CRP3: Develop workaround or customization for the Gaps identified in the CRP2 and fix them and
demonstrate a full fledged solution suitable to Client Business