You are on page 1of 7

what is full bw life cycle implementation

Hi guys I am new BW job seeker, showing some experience...


The interviewers asking ' you have any full life cycle bw implementation
experiece'. Pls anyone tell me what is full life cycle be implementation,
what topics it covers. I have knowledge from Infooject creation, cube, ods,
Extraction, reporitn. with these topics knowledge if I say yes I have full
life cycle implementation experiece will it work. Pls help me.

Can any one tell me what are the major steps invloved in a sap end-to-end implementation. I mean the in
the complete life cycle. I do not want the details just need to know the major steps invloved.

Also, I would like to know what is the difference between SAP and mysap.
Implementation steps:
1. AS IS process
2. To be process mapping
3. customizaiton in SAP + devepment
4. Unit testing
5. Full testing
6. End-user training
7. Go-live
8. Support for initial month-ends.
9. Ongoing support....

1. AS IS process - Study of the existing process.


2. To be process mapping - What will be the new process.
3. customizaiton in SAP + devepment - Customization like company codes, plants etc based on the To be
process. And master data upload.
4. Unit testing - Testing of each and every module separatly
5. Full testing - Full system testing. In this step all steps are integrated so, it is also known as Integration
testing.
6. End-user training - Training for the Power user (first line users) by the SAP Consultants. They will in turn
train to other users.
7. Go-live - Creation of first PO or Invoice
8. Support for initial month-ends. - First month-end closing, this is very much critical as FI/CO point of view.
9. Ongoing support....

SAP follows ASAP methodology to make the project implementation.

a)Project Preparation
b)Blue-print
c)Realization / Fit-gap analysis
d)Pre-producton
e)Go-live / Production

Generally in project preparation top management / PM will discuss with the client regarding the
business integration n pros n cons of implementation.

Blue print contains all the functional specs related to the project.

Realization is the place where u actually implement and provide solutions , like activation of Business
content objects etc.

Pre-production is the place where u will test the project .

Go-live means actual production and u will support the issues hereafter.

Normally u will involve in the realization phase .

When u r working on the bw implementation depends upon u r experience task will be assigned to you.

Generally any sap implementation have same phases above what kalyan mention but it will vary from client
to client.

Before going to u r task u need to understand the application(business process) of u r client according to
that u need to configure or create or activate the objects.

once these objects completed in the development server u need to transport into quality server then u need
to send into production server there u need to check whether objects r working according to u r client
requirement.

Entire process will take some more time

can u plz explain me these.


1. how do you convert tech spec to functional spec?

2. any toughest scenario in implementation proj?( plz for interview purpose}

1. how do you convert tech spec to functional spec?

First of all we cant convert using either one document to another document. Instead of that we have to
create both documents in different time. You can understand by reading the following definitions:

Technical Specification:

Here we will mention all the BW objects (info objects, data sources, info sources and info providers). Then
we are going to say the data flow and behaviour of the data load (either delta or full) also we can tell the
duration of the cube activation or creation. Pure BW technical things are available in this document. This is
not for End users document.

Functional Specification:

Here we will describe the business requirements. That means here we are going to say which are all
business we are implementing like SD, MM and FI etc., then we are going to tell the KPI and deliverable
reports detail to the users. This document is going to mingle with both Function Consultants and Business
Users. This document is applicable for end users also.

2. any toughest scenario in implementation proj?

That is depending on the implementing procedure. For example you are going to implement the project with
full of customizing objects even data source also then that will be tough compare with activate the business
content.

If your implementation is based on only activation of the business content, then there will not be taking more
risks. Only thing we have to take care of the enhancements. For this you have lot of best practices are there.

Following are the different phases of implementation,

1. Initial Preparation
2. Blue Print
3. Realization
4. Final Preparation
5. Go live & support,

Here are the phases of SAP Life Cycle-

Phase 1 Project Preparation


- review BW Methodology
- assign Roles based on project member's skills
- Project Charter
- Project Plan

Phase 2 Business Blueprint


- Information Requirements Analysis

- Multidimensional Data Modeling


- Templates Business Blueprint
- Sizing, Hardware Sizing
- review BW System Lanscape & Transport
- Authorizations

Phase 3 Realization
- modeling, create infocube, ods, query, aggregate, etc
- Issue log database

Phase 4 Final Preparation


- BW Performance / Tuning

Phase 5 Going Live


- user training
- Operational Support

You can even have a look at these good links-

http://help.sap.com/bp_biv335/BI_EN/documentation/BWProjectPlan_EN.mpp

http://help.sap.com/bp_biv235/BI_EN/documentation/BW_ROLES_SKILLS.doc

Re: Lifecycle Implementation