1* SAP Landscape: - A landscape is an arrangement of servers.

In landscape in project preparation phase

decided how many server to be purchased, sizing of server, where to purchase server. Any client if they
want to implement SAP they need to purchase servers. All in one server. But client are different server.
SAP Suggest to go for minimum 3 Server:-

Development Server
Quality Server
Production Server

2* Development Server: - it will be used to configure the client business process into SAP. Development
server will be used by consultants only. For development server further classified into three client technical
client, configuration client, and internal testing client.

Can I create master data in configuration client – no.

Can I create master data in internal testing client – yes.
What is purpose of internal testing – concept wise testing.
What is cross client – if you do configuration in one client it will update other client server called cross
client.

3* Quality Server: - it will be used to test the scenarios whatever developed in development server. Quality
server will be used by consultants and core users.
Core User is the employee of the client company who has good experience & exposure in client business
process.

4* Production Server: - It is the live server, where end user will do day to day transactions in SAP.
Production server will be used by end users and core users. Consultants will not have access to production
server. Users will not have access to development server.

5* Roles & Responsibility of consultant

As a consultant we will be placed into either implementation project, support project, Rollout Project,
Upgrade Project.

6* Implementation Project
Configuring client business process newly into SAP.
Whenever implementation partner receives the order from client to implement SAP, then they start using
ASAP methodology (ASAP stands for accelerated SAP).

ASAP methodology consists of step by step implementing of SAP. That is the guidelines to implement SAP.
Its purpose is to help, design SAP implementation in most efficient manner. Its goals are to effectively
optimise time, people, quality & other resources.
It’s also providing full life cycle support.
ASAP methodology integrates the following components
ASAP road map
Tools(questionnaires)
R/3 service & training.

7* ASAP Methodology consists 5 Road map:-

1. Project Preparation
2. Business blue print (BBP)
3. Realization
4. Final Preparation
5. Go-Live & Support

8* As a consultant we will be involved from business blue print phase onwards. ( KDS – key data structure)
Daily stand up meeting, scrum meeting, sprinting meeting.

9* Project Preparation Phase: -

In project preparation phase the management from implementation partner and management from client
will involve.
As a consultant we don’t involve in project preparation phase.

10* Project Preparation Phase Activities:

User Licenses: - Any client if they want to implement SAP they need to purchase user licenses from SAP.
Based on number of end users they decide on how many user licenses to be purchased from SAP.

Landscape: - A landscape is an arrangement of servers.

Any client if they want to implement SAP they need to purchase servers.
SAP Suggest to go for 3 Servers:-

Development Server
Quality Server
Production Server
If landscape is 4th server then the extra server is SANDBOX. It is used for rough work & R & D department
will handle.

After deciding how many servers to purchase, then they decide on sizing of the
Server.
Ex - Hard disk, RAM etc. On the basis of number of Pc‟s
Where to purchases the servers? Popular Manufacturers of servers in the market are HP, IBM, HCL, DELL .
Infrastructure – they decide how many new computers to be purchased for no. of licence. In server
environment they decide where keep the server & security. In VPN connectivity, it will help to connect the
server kepted some other location.

Implementation Partner: - will list out all the consultants who are going to involve in this implementation
Project. Client will list out all the core users who are going to involved in this project. Core user role in
implementation project is they have to explain the client’s business process to clients. And consultants
configuring the SAP.

Implementation partner are BDM, PM, DELIVERY HEAD, TECHNICAL HEAD.

Consultant Facilities: - If it is domestic project all the consultants will go to client place for implementing
SAP.
If it is foreign project, from each module one consultant will go to client place to implement SAP (On-Site)
and rest of the team will work from Off- shore (it means Implementation Partner office).
Ex- Accommodation, food expenses, travel expenses, work environment etc.
The Average project tenure for domestic project is 9 months.
For foreign project 18 months
Go-Live Date: - It is a date from which client (Galaxy Parma) will start using SAP or the date the client will
start entering day to day transactions in SAP.

After completion of project preparation phase, the implementation partner management will come back to
office and conduct kick-off meeting.
Kick-off: - A kick of meeting is a first meeting with the project team & client of the project.
The purpose of kick of meeting is to formally notify, all the team members, client, & stake holder (together
all vendor, customer, share holder etc.) that the project has begun & make sure everyone has a common
understanding of the project & their rules.
Also they will invite all the consultants across all the modules that who are going to involve in this
implementation project.
Here discussed

Introduction about client

Rules & regulations of client
Role & Responsibility’s of consultant
Core users list.
Go live date.
Starting date.
After kick –off meeting all the consultants will move to client’s place for implementing SAP (Domestic).
When all the consultants move to client place to implement SAP then we start 2nd phase of ASAP
methodology that is Business Blue Print (BBP).
10* Business Blue Print Phase (3 Months)

As a FI consultant we involve from Business blue print phase onwards.

BBP phase is most critical phase because the success of the project is totally depended on that how
accurate we gather the requirements from core user.
In BBP phase we prepare two documents:-
Requirement gathering document
BBP document & sign off
GAP analysis document.(if require)

Generally the 1St day of client visit, we will have introduction with core user and core user will take us for
site visit (Mfg plant visit).on 2ndday, the first activity in BBP is

Requirement Gathering: - Everyday consultant has to go to core user place, ask the questions and whatever
core user will explain note it down as-it is.

Every day after completion of requirement gathering (time allot 10am to 3pm) consultant has to prepare a
document which is called AS-IS document. (In excel sheet)

AS-IS document consist the present business process of client, whatever core user explain as it is we
mentioning in this document.
- Based on questionnaires provided by the implement partner we gather requirement from core user.

BBP document and sign-off: - After completion of requirement gathering, we need to prepare
BBPdocument.BBP document consist of AS-IS and TO-BE document.

Example of AS-IS – TO BE
TO-BE document consist of, how the present business of the client is going to be implement in SAP system.
While preparing TO-BE document we may find some GAP’s.
GAP: - For client business process, if there is no solution in standard SAP then we call it as a GAP. Whenever
we find GAP we will prepare GAP analysis document.

11* GAP analysis document

Gap analysis document consist Clear description of client process, which is a GAP in SAP. Also find
alternative solution.

After preparing BBP document, we will send this document to core user for sign-off.

Now core user has to check & go through the BBP document. If everything is fine then he will send
confirmation mail to consultant.
 After getting confirmation mail we take the signature of core user and PM in sign-off form and one copy
will be with Implementation Partner and one copy we will submitted to client.

Without sign off, we are not supposed to move next phase of ASAP methodology.

* Common Problems we face in BBP phase:-

Most of the core users they don’t support for gathering requirement, and also they don’t come on time. (If
it happens continuous then after 4 or 5 days we need to inform our PM and our PM will inform to client
PM).
They don’t want change. (They don’t want to implement SAP; they may have threat to their job).
Core user having knowledge on SAP configuration (They will join some institute & they will ask some error
and check our knowledge or waste time for gaining their knowledge).

After receiving BBP sign-off from core user then we move to the next phase of ASAP methodology that is
realization.

BPD - in this phase we join in BPD with client (blue print discussion) in that our role & responsibilities are we saying
that what are works we do in this phase, in SAP we fulfil this requirement. We told these are type configuration
(Baseline & final) we doing as per your business & also showing any other company data to knowing purpose your
current client & we can configure this field. It is a one type of discussion part. In that phase both side of suggestion
are showing & one document are prepared which is called BBP document, means AS-IS TO-BE document. And if
any GAP analysis is there means verify the AS-IS & TO- BE if not do/no possible anything in this document
mentioned in end of the BPD & also mentioned what we will do in end of BPD.

We told in BBP phase disused that are only. My role is in this phase I was taking KT & create format in excel sheet
like list of vendor, customer, and asset everything.

12* Realization Phase

Realization: - Configuring the client business process into SAP or mapping TO-BE process in SAP. When we
enter into realisation phase we will get credentials from BASIS people. (Client no, user ID, password, server
ID etc).In this phase we Login into development server, to configure the client business process into SAP.

We have two types of configurations:-

Base Line configuration
Final configuration

Base line configuration: - It is the configuration for which, we don’t want to depend on other module
consultant (it is a configuration which is specific to one module).
Final configuration (Integration between Modules): - it is the configuration for which we need to depend
on other module consultants (MM, PP, FI). This configuration we can’t do on our own.

13* In SAP whenever we are saving the configuration, we need to save it in a particular REQUESTNUMBER.
Request number will help to transport the configuration from one server to another server.
Ex. - Transport request number will help to transfer the configuration from development server to
quality server for testing purpose.
After completion of base line configuration and final configuration we transport the entire requests
from development server to quality server for testing purpose.

14* Functional consultant role in transporting request

Transport requests nothing, but it is a transport object which is transfer the data from one Clint to another
client by transport organiser.
We need to release the entire request. Each request consist of parent & child, first release the child
request then release parent request. Child request will help to carry the data & parent request will help to
transport the data.
List out all the request number in excel file along with the description & sequence order, and send this
excel file to basic consultant, basic consultant will transport the entire request from one server to another
server.
Transport request is of two types:-
Customizing request
Workbench request
Customizing request (Client Dependent): - Whatever configurations, functional consultant will do, that will
save in customizing request.
Workbench request (Client In-Dependent): - Whatever developments, technical consultant will do, that will
store in workbench request.

After transporting the request from development server to quality server then we do internal testing in
quality server.

15* Testing
Unit testing.
Integration testing
Unit testing: - It is the testing which is specific to one module and no need to depend on other module.
Integration testing: - It is the testing for which we need to depend on other module.

16* Before testing we need to prepare test case document or test scenario document. Based on this test
case we will do unit and integration testing
Test Case
What to test.
How to test
Expecte0d result
Actual result
Status
Tested document number

After completion of testing, we prepare user manual document.

17* User Manual document:-It is a guideline to end users, this document consist of step by step process of
creating master data and transaction data along with the screen shots. After preparing user manual
document, we will give it to core user.

18* Configuration document: - This document consists of the entire configurations made for that particular
client along with the screenshots. Configuration document will be used for KT (knowledge Transfer)
purpose. This document will be given to core users.
In realisation phase mostly prepare 4 document FS document, test case document, user manual document,
configuration document.

18* Final Preparation Phase .

Final Preparation Activities:-

Training to core users (Train-the-Trainer): - We give training to core user for 15 days. After that core user
will give training to (15 days) their end User.
UAT Sign-off: - After training we will ask core user to test the scenarios and confirm. Core user has to (10
days) test all the scenarios; if everything is fine they will give UAT sign-off (User acceptance test).
Transfer request number Quality to production: - After getting UAT sign-off we transport all the requests
(configurations) from quality to production Server through ABAP people.
Cutover activities: - Uploading of master data and open transactions data from legacy to SAP. Legacy
means Non-SAP.
19* Consultant role in cutover activities
We list out in excel sheet what master data and what open transaction data should be uploaded from
legacy to SAP
Master data consist:-
Customer master
Material master
Vendor master
Asset master
Open transaction data: - Open Order (The order which created but yet not delivered or pending)
We do recording (maintain record the all document) and send this recording to ABAPER while doing
recording simultaneously prepare excel sheet with the same sequence of recording and send this excel
sheet to core user.
Basis on the recording ABAPER will develop BDC (batch data communication) and give it to consultant.
Core user will fill all the excel sheet and give it to consultant.

As consultant we first go to quality server and do MOCK run (testing) if everything is fine then we go to
production server and upload the data from legacy or excel sheet.
20* Cutover Strategy: - It is a planning for uploading data from legacy to SAP. During this strategy we
decide when exactly to upload the data from legacy to SAP. Whenever we plan to upload the data from
legacy to SAP, in that time we request to client stop the business transactions.

21* Cutover Period: - Generally we take 2 days to upload the data from legacy to SAP. The 2 days period is
called cutover period.
After cutover period we go to the next phase of ASAP methodology that is GO-LIVE & Support.

22* GO-LIVE & SUPPORT PHASE

Handing over SAP to client/end user, from that date onwards end users will start entering day to day
transaction in SAP.
After implementation we provide 1 months of post production support, which is called hyper care support.

What was your role – did you work in onsite or offshore – first of all I was working in onsite this is
Indian project. What was your team size – our FI team size was 2 persons. There was a senior
consultant & me. I worked as Associate consultant. My responsibility was like requirement
gathering from the beginning but mostly prepared ASIS document in BBP phase. BBP means
combination document of ASIS & TOBE document. I prepared all the ASIS documents along with
my senior & conducting meetings & workshop with the client & business people then prepared
BBP. I also part of BBP phase my senior play key role in BBP phase & I was also part of project end
to end implementation then after sign off from take sign from PM & Client. I did configuration like
baseline configuration & unit testing after I did the integration testing after integration testing we
did UAT testing with core user/business people of client & then GO live. What was your duration
of project - it was 8 to 9 month taken.
Basically we used ASAP methodology to complete the project – first of all there 5 phases in ASAP
like project preparation, BBP, realization, final preparation, Go live Support. In project preparation
phases we conducted some business workshops, questionnaires & meetings with client & core
user & we gathered all the information like what is the business, how it operates, what are
manufacturing & all those things & then we prepared as per business requirement ASIS
document. In the ASIS document me & my senior both prepared the ASIS document& I helped to
my senior for ASIS documentation how it operates & flow diagram & business model. So after that
we prepared the BBP document. BBP document means combination of ASIS & TOBE document
you know. ASIS means the existing business process of client & TOBE means its how the existing
business mapping to the SAP. In this phase my senior written the document & me associate him to
complete the BBP phase. You written BBP or not – yeah prepare BBP but my key person
responsible I do that. In BBP prepared nomenclature, business process, flow diagram & list out the
all data in excel sheet whatever information collected. Then in realization phase I did baseline
configuration. What is configuration you did that in implementation. What you did after
configuration. – after realization phase Within the module we test unit testing we successfully
posted the document in unit testing after did the integration testing after we move to realization
phase to final preparation phase & all developments copy to the quality client from development
clients. Once tastings are successfully then transport the document help transfer request to BASIS
people they transport the entire request development server to quality server for testing purpose.
Once it moves to quality server tester user ID created then user manual document. After user
manual document need to UAT testing then decided cutover period & migrated data from non
SAP to SAP after that we did the LSMW & all the transfer request from move to production system
then move to GO live after GO live we hyper support for 1 month its means immediately complete
of implementation its happened (one type of bond) then we give regular support. After I gave to
KT to other people project handle to support team & I joined in another project.

In unit testing means what are the business process of the company we check the master data &
transaction data whatever already created. What are integration testing you did with other
modules – these are the integration in this project (project name/client) they manufacturing
cartoon & products & packaging products & tetra packs in that machines & labor all are available
(story) from Google.

Difference between test case & test script - The test case is a sequence of steps that help us
perform a certain test on the application. The test script is the same thing. Now, there is one
school of thought that test case is a term used in the manual testing environment and test script
is used in an automation environment.
Test suite - test cases that are intended to be used to test a software program to show that it has
some specified set of behaviors. It is also we can say one type of folder.