VALUE ASAP METHODOLOGY

WHY SAP TO COMPANY

1. INTEGRATON
2. MULTI LANGUAGE – MORE THAN 26 LANGUAGES
3. MULTI CURRENCY
4. TRANSPARENCY - CHINA YEN, REPORT IN EURO

DATA TYPES
1. MASTER DATA - END USER
2. TRANSACTION DATA - END USER
3. CONFIGURATION DATA - CONSULTANT

SAP MODULE MORE THAN 67

IMP - SHIFTING LEGACY SYSTEM TO SAP
ENHANCEMENT : EXPANDING THE BUSINESS IS CALLED ENHANCEMENT.
1. ENTERING IN TO A NEW VENTURE
2. NEW LAUNCH PRODUCT
3. MEGRING WITH BIG COMPANIES

VISION – WHAT I AM GOING TO ACHIEVE

MISSION – HOW I M GOING TO ACHIEVE MY VISION

I – PHASE / PROJECT PREPARATION

1. INTRODUCTION
2. PROJECT VISION
3. PROJECT LOGO
4. PROJECT OBJECTIVES
5. PROJECT SUCCESS INDICATORS
6. PROJECT SCOPE
7. PARTNER SCOPE OF WORK
8. PROJECT IMPLEMENTATION STRATEGY
9. CLIENT DEPLOYMENT STRATEGY
10. SAP CONFIGURATION STATUS
11. TESTING STANDARD & STRATEGY
12. TRAINING METHODOLOGY
13. PROJECT PLAN
14. PROJECT DELIVERABLES
15. RESOURCE PLANNING & ALLOCATION
16. SIGNOFF
4-PROJECT OBJECTIVES
ERROR FREE FINANCIAL STATEMENT
LESS PRODUCT SHORTAGE
ACCURATE PROMISING TO CUSTOMER
OPTIMUM STOCK LEVEL

5-PROJECT SUCCESS INDICATORS

IF I ACHIEVE THE ABOVE IT WILL BE SUCESSFUL

6-PROJECT SCOPE
ECC 6.0 SD / MM / FI CO / HR / ABAP / BASIS

7-PARTNER SCOPE OF WORK

1. TRADING PARTNER - WIPRO
2. TESTING PARTNER - INFOTECH
3. AUDIT - DELOITTEE / SAP

8-PROJECT IMPLEMENTATION STRATEGY

VALUE ASAP METHODOLOGY

9-CLIENT DEPLOYMENT STRATGEY

10-SAP CONFIGURATION STATUS

Y & Z – TO SUPPORT UPGRADED VERSION
ABAP STANDARDS = THERE ARE 840 STANDARDS

11-TESTING STRATEGY AND STANDARD

1. UNIT TESTING - INDIVIDUAL MODEL WISE
2. INTEGRATION TESTING - FI MM / FI SD
3. USER ACCEPTANCE TESTING - END USER ACCEPTANCE TEST
APART FROM THAT
1. POSITIVE -
2. NEGATIVE - PURPOSEFULLY GIVE WRONG VALUE, SHD NOT ACCEPT
3. RANDUM - PICKUP SOME VENDOR WISE / MATERIAL OUT OF 100 VENDORS.
4. REGRESSION - IN SUPPORT PROJECT
5. STRESS - AFTER GOLIVE FROM CRM, SRM, SCM TO ECC 6.0
6. PERFORMANCE - “ - AT A TIME LOT OF USER LOGIN OR ISSUE SO AT A TIME
7. VOLUME - “
12-TRAINING METHODOLOGY
WHICH METHODOLOGY USED FOR TRAINING THE ENDER USER –
TTT – TRAINING THE TRAINER OR
TAT – TRAIN A TRAINER

SR. CONSULTANT WILL GIVE THE TRAINING TO JUNIOR CONSULTANT

JUNIOR CONSULTANT TO CORE TEAM MEMBER
CORE TEAM MEMBER TO SUPER USER OR POWER USER
POWER USER TO END USER

13-PROJECT PLAN
EACH AND EVERY ACTIVITY IN THE IMPLEMENTATION WITH THE DATE AND RESPONSIBLE PERSON
NAME.

14-PROJECT DELIVERABLES
FOR THE ABOVE ACTIVITIES ARE ALL MY DELIVERABLES.
TRAINING, TESTING & UPLOADING WILL BE GIVEN ELABORATELY IN THIS.
PROJECT PREPARATION, BUSINESS BLUE PRINT PHASE (ALL THE PHASES),
PREPARE A DOCUMENT, THIS WILL BE CALLED DELIVERABLES.

15-RESOURCE PLANNING & ALLOCATION

RESPONSIBILITIES OF :-
FI / MM / SD CONSULTANTS

16-SIGNOFF
PROJECT MANAGER
WIPRO DELIVERY MANAGER
ITC PROJECT MANAGER
15 ACTIVITIES WILL BE MENTIONED. THE ABOVE 4 PERSON WILL BE SINGOFF MEANS THIS PROJECT
PREPARATION PHASE IS OVER. THIS DOCUMENT WILL BE CALLED PROJECT CHARTER.

PROJECT PREPARATION
1 TEAM LEADER
1 SR CONSULTANT
2 ASSOCIATE CONSULTANT (IF IT IS REQUIRED)
1 JUNIOR CONSULTANT
 STEERING COMMITTEE
WIPRO
CEO  VP  CIO  SAP DELIVERY MANAGER (INDIA SAP MANAGER)  PROGRAM MANAGER  PMGR
PROJECT MANAGER
|
TEAM LEADER
|
SENIOR CONSULTANT
(FI / CO / MM / SD / HR / BASIS / ABAP)
|
JUNIOR CONSULTANT

MEETING – MONTHLY ONCE –

JOINEE : SAP DELIVERY MANAGER
PROGRAM MANAGER
PROJECT MANAGER

ITC – SIDE
CEO 
VP 
CIO 
SAP PROJECT MANAGER 
CORE TEAM 

SUPER USER 
END USER

STEERING COMMITTEE WILL INCHARGE FOR :-

1. BUDGET CONSTRAINT
2. MORE IMPLEMENTATION
3. EXTENSION OF PROJECT

CORE TEAM MEMBER WILL COLLECT INFORMATION FROM THEIR SIDE (EXISTING BUSINESS PROCESS –
RELEASING OF AS IS TEMPLATE), WHEN THE PROJECT PREPARATION PHASE STARTS AND AT THE
BEGINNING OF BUSINESS BLUE PRINT PHASE THEY WILL HAND OVER TO PREPARE A TO BE DOCUMENT.

SOME COMPANIES CALLED

AS IS - CURRENT STATE BUSINESS PROCESS
TO BE - FUTURE STATE BUSINESS PROCESS
II – PHASE / BUSINESS BLUE PRINT

GAP:-
1. NOT POSSIBLE BY SAP AT ALL
2. POSSIBLE BY SAP BUT NOT POSSIBLE BECAUSE OF SCOPE, TIME AND MONEY

A. WORK AROUND SOLUTION

B. DEVELOP A PROGRAM
C. WE GO DEVELOPMENT – IDENTIFY THE WRICEF IN BLUE PRINT LEVEL
D. INTEGRATION PROCESS
E. FINALISE ORGANIZATION STRUCTURE (DISCUSS WITH ALL MODULE CONSULTANTS BECAS ONCE
WILL SAY 1 PLANT 2 CO. CODES, TO AVOID THIS).

BUSINESS BLUE PRINT CONSISTS OF :

1. AS IS (DOC WILL BE MORE THAN 500)
2. TO BE (IT BECOMES 20 TO 40)
3. IDENTIFY GAP
4. IDENTIFY WRICEF
5. FINALISE INTEGRATION PROCESS
6. FINALISE ORGANIZATION STRUCTURE

SENIOR CONSULTANT WILL PREPARE TO BE DOCUMENT FOR THE PARTICULAR SUB MODULE LIKE AP
AND GL.

EXISTING PROCESS = INPUT

SUGGESTED SOLUTION = OUTPUT

BLUE PRINT DOCUMENT CONTAINS THE FOLLOWING :-

1. ORGANIZATION STRUCTURE
2. MASTER DATA
3. BUSINESS PROCESS
4. STANDARD INFORMATION SYSTEM
5. MODULE INTEGRATION
6. REPORTS
7. FORMS
8. GAPS
9. DEVELOPMENT LIST
10. PROCESS CHANGES

THIS WILL BE SINGOFF AND GOES TO NEXT PHASE

III – PHASE / REALISATION

SAND BOX IS NOT CONNECTED TO OTHER SERVER

WE HAVE FULL ACCESS
THIS IS FOR TRAINING AND R&D PURPOSE THAT IS EXPERIMENTAL PURPOSE
DATA ALREADY AVAILABLE

DEV – QTY – PRODUCTION = CONNECTED (BUT NO DATA AVAILABLE)

RESTRICTION TO USE THE ABOVE 3 SYSTEM

DEV – NO DATA
SAND BOX – ALL MASTERS DATA AVAILABLE, READY TO USE. WE CAN MOULD AS YOU WISH.
NO TR WILL MOVE FROM SAND BOX TO DEV. BASIS TEAM WILL MOVE.

IN BLUE PRINT PHASE – ONLY SAND BOX AVAILABLE, NOT OTHER SERVER
IN REALIZATION PHASE – DEV – QTY – PROD

IN REALISATION PHASE WE USE SAND BOX THEN TR WILL BE MOVED FROM SAND BOX TO DEV.

200 – FUNCTIONAL DEV

210 – TECHNICAL OR ABAP DEV
220 – UNIT TESTING - POSITIVE TESTING AND DOC PRE - BY JR. CONS
- NEGATIVE TESTING AND DOC PRE - BY JR. CONS
- RANDOM TESTING AND DOC PRE - BY JR. CONS
CONFIGURATION WILL BE DONE BY SR. CONSULTANT AND FINALISE THE BLUE PRINT.

ONCE DONE IN 200 BY FUNCTIONAL CONSULTANT (CONSULTNAT WILL CHK HERE ONLY) FOR TESTING
PURPOSE (MODULE WISE) TR WILL BE MOVED FROM 200 TO 220.

LIKE WISE 210 TO 220 (TECHNICAL CONSULTANT)

IN 220 – CORE TEAM WILL DO THE MODULE WISE UNIT TESTING.

HOW TO TEST

FI TEST SUIT CONTAINS :-

1. TEST CASE – GL POSTING WITH FILEDS, CONTAINS (TEST CASE MEANS FILE)
2. TEST SCRIPTS – THAT IS STEPS, HOW TO DO THE PATH (TEST C=

AFTER UNIT TESTING CLIENT WILL SIGN OFF.

THEN IT WILL BE MOVED TO QUALITY SYSTEM - MOVE TR DEV TO QTY SYSTEM
300 - INTEGRATION TEST FI-MM & FI-SD - POSITIVE – TEST SUIT, TEST CASE, TEST SCRIPT
- NEGATIVE – - DO -
- RANDOM – - DO -

310 - GOLDEN CLIENT, PRE-PRODUCTION OR MIRROR IMAGE OF PRODUCTION SERVER ALSO CALLED
BACK UP SERVER

300 - HERE IF TEST CASES IS FAILED THEN GO BACK TO 200 AND CHANGE THE CONFIGURATION AND
MOVE TR TO 220 THEN QUALITY 300 THEN ALL THE TR FROM 300 TO 310.

FINALLY 310 TO 500 PRODUCTION SERVER

NOTE- APO = 4 SERVER - LINKED TO SAND BOX - ECC 6.0

CRM = 4 SERVER - LINKED TO SAND BOX - ECC 6.0
BI = 4 SERVER - LINKED TO SAND BOX - ECC 6.0

IV – PHASE / FINAL PREPARATION

1. CUTOVER ACTIVITIES
2. TRAINING - END USER TRNG, END USER MANUAL (STEP WISE PROCEEDURES)
3. UPLOAD DATA - MDM OR FUNCTIONAL CONSULTANT
4. UAT
5. AUTHORIZATION MATRIX

TRAINING - 01 CONSULTANT = 10 CORE TEAM MEMBER

- 10 CORE TEAM = 100 SUPER USER
- 100 SUPER USER = 100 END USER

TRAINING METHOD – TAT = TRAIN A TRAINER

TRAINING WILL BE DONE IN SAND BOX ONLY. IF CLIENT AGREES USE DEV SERVER.
DURATION = 2 WEEKS (FIX THE DATE, VENUE AND SCHEDULE)

AUTHORIZATION MATRIX :-GIVING ACCESS TO END USER BY BASIS TEAM

FUNCTIONAL CONSULTANT WILL PREPARE A EXCEL SHEET :-
NAME AND TCODE

CLIENT - ROLES OF END USER NAME AND THE EMP ID

BACIS TEAM WILL GIVE ACCESS TO THE ENDER USER AFTER WE SUBMIT IN EXCEL SHEET.
UAT
END USER ACCEPTANCE TEST. ANY CHANGES GIVEN BY END USER IN THIS TIME WILL BE DONE IN
SUPPORT AFTER GO LIVE.

CUT OVER ACTIVITIES

OPEN ORDER
OPEN DELIVERY - DLY DONE BUT NOT PAID
OPEN PO - INV PAID BUT NOT PAID
OPEN PR
OPEN GL ACCOUNT

FUNCTIONAL PEOPLE WILL ASK CLIENT AND PREPARE FS AND HAND OVER TO ABAPER, THEY WILL
PREPARE TS

4 MONTHS PERIOD IN FINAL CONFIGURATION TIME, 9 HRS THEY WILL PREPARE FOR EXA 30 PROG.
1000 OEPN ORDER WILL CREATE IN SAP IN DEV SERVER ONLY, TEST IT.

MOVE IT TO PRODUCTION AT THE TIME OF CUT OVER ACTIVITIES PERIOD.

CUTTING OVER LEGACY SYSTEM AND MOVING ALL OPEN TRANSACTIONS TO SAP SYSTEM BY USING BDC
PROGRAM.

V – PHASE / GOLIVE