SAP SDSAP SD

SYSTEM APPLICATION AND PRODUCTSYSTEM APPLICATION AND PRODUCT

SAP IS AN ERP PACKAGESAP IS AN ERP PACKAGE

SAP IS THREE TIER ARCHITECTURESAP IS THREE TIER ARCHITECTURE

SAP IS AN ERP PACKAGESAP IS AN ERP PACKAGE

ITS SPECIFIES THE PLANNING IN ALL ITS SPECIFIES THE PLANNING IN ALL DEPARTMENT IN AN ORGANISATIONDEPARTMENT IN AN ORGANISATION

ITS SPECIFIES HOW TO UTILISED THE ITS SPECIFIES HOW TO UTILISED THE 4’MS 4’MS

MENMEN

MONEYMONEY

MATERIALMATERIAL

MACHINERYMACHINERY

SAP IS THREE TIER SAP IS THREE TIER ARCHITECTUREARCHITECTURE

PRESENTATION LAYERPRESENTATION LAYER

APPLICATION LAYERAPPLICATION LAYER

DATABASE LAYERDATABASE LAYER

PRESENTATION LAYERPRESENTATION LAYER

SYSTEM USED BY END USER THIS IS SYSTEM USED BY END USER THIS IS THE PRESENTATION LAYERTHE PRESENTATION LAYER

ITS LIVE DAY TO DAY TRANSECTION ITS LIVE DAY TO DAY TRANSECTION DONE ON THISDONE ON THIS

APPLICATION LAYERAPPLICATION LAYER

ANY REQUEST SEND BY ANY REQUEST SEND BY PRESENTATION LAYER FIRST TAKEN PRESENTATION LAYER FIRST TAKEN BY APPLICATION LAYER .BY APPLICATION LAYER .TAKE THE DATA AND SEND TO DATA TAKE THE DATA AND SEND TO DATA BASE LAYER FURTHER TAKE THE BASE LAYER FURTHER TAKE THE PROCESSED DATA FROM DATA BASE PROCESSED DATA FROM DATA BASE AND SEND IT TO PRESENTATION AND SEND IT TO PRESENTATION LAYERLAYERITS ACT AS MEDIATORITS ACT AS MEDIATOR

DATABASE LAYER DATABASE LAYER

ITS CONSIST OF DATA ONLYITS CONSIST OF DATA ONLY

ROLES AND RESPONCIBILITY ROLES AND RESPONCIBILITY OF CONSULTANT IN OF CONSULTANT IN

IMPLIMENTATION OF PROJECTIMPLIMENTATION OF PROJECT

COMFIGUIRING THE CLIENTS BUSINESS COMFIGUIRING THE CLIENTS BUSINESS PROCESS INTO SAP WHO MIGHT USING PROCESS INTO SAP WHO MIGHT USING SOME LEGACY SYSTEM .SOME LEGACY SYSTEM . LEGACY SYSTEM IS THE THE SYSTEM LEGACY SYSTEM IS THE THE SYSTEM OTHER THAN SAP . OTHER THAN SAP . ANY CLIENT WHO WANT TO IMPLIMENT SAP ANY CLIENT WHO WANT TO IMPLIMENT SAP THEN CONSULTANT HAS TO GO WITH THEN CONSULTANT HAS TO GO WITH SPECIFIC METHODOLOGY CALLED ASAP SPECIFIC METHODOLOGY CALLED ASAP METHODOLOGY.METHODOLOGY.

ASAPASAP

ACCELERATED SAP IS CALLED ASAPACCELERATED SAP IS CALLED ASAP

ITS CONSIST OF THE GUIDELINES TO ITS CONSIST OF THE GUIDELINES TO IMPLEMENT THE SAP.IMPLEMENT THE SAP.

ITS STEP BY STEP PROCESS OF ITS STEP BY STEP PROCESS OF IMLPEMENTING SAP.IMLPEMENTING SAP.

ITS CONSIST OF FIVE PHASEITS CONSIST OF FIVE PHASE

ASAP FIVE PHASESASAP FIVE PHASES

PROJECT PREPERATION PHASEPROJECT PREPERATION PHASE

BUSINESS BLUE PRINT PHASEBUSINESS BLUE PRINT PHASE

REALISATIONREALISATION

FINAL PREPERATIONFINAL PREPERATION

GO LIVE AND SUPPORTGO LIVE AND SUPPORT

PROJECT PREPERATION PHASEPROJECT PREPERATION PHASE

AS CONSULTANT WE DO NOT NEED AS CONSULTANT WE DO NOT NEED TO INVOLVED IN THE PROJECT TO INVOLVED IN THE PROJECT PREPERATION PHASE.PREPERATION PHASE.

ONLY THE MANAGEMENT FROM THE ONLY THE MANAGEMENT FROM THE IMPLIMENTATION PARTENER AND IMPLIMENTATION PARTENER AND CLIENT MANAGEMENT INVOLVE INTO CLIENT MANAGEMENT INVOLVE INTO PROJECT PREPERATION.PROJECT PREPERATION.

PHASESES OF PROJECT PHASESES OF PROJECT PREPERATION PREPERATION

USER LICENSESUSER LICENSES

LANDSCAPELANDSCAPE

INFRASTRUCTUREINFRASTRUCTURE

IMPLIMENTATION PARTENERIMPLIMENTATION PARTENER

CONSULTANT FACILITYCONSULTANT FACILITY

GO LIVE DATEGO LIVE DATE

USER LICENSESUSER LICENSES

ANY CLIENT IF THEY WANT TO ANY CLIENT IF THEY WANT TO IMPLEMENT SAP THEY NEED TO IMPLEMENT SAP THEY NEED TO PURCHASE USER LICENSES FROM PURCHASE USER LICENSES FROM SAP.SAP.

BASED ON NO. OF END USERS THEY BASED ON NO. OF END USERS THEY DECIDE HOW MANY USER LICENSES DECIDE HOW MANY USER LICENSES NEED TO PURCHASE FROM SAP.NEED TO PURCHASE FROM SAP.

EACH USER LICENSES COST GOING EACH USER LICENSES COST GOING TO BE APROXIMATELY RS 18000 /-.TO BE APROXIMATELY RS 18000 /-.

AN EVERY YEAR CLINT HAS TO PAY AN EVERY YEAR CLINT HAS TO PAY 22% OF LICENSE COST TO SAP IN THE 22% OF LICENSE COST TO SAP IN THE FORM AMC.FORM AMC.

AMC =ANNUAL MAINTAINENCE COSTAMC =ANNUAL MAINTAINENCE COST

LANDSCAPELANDSCAPE

ITS ARRANGEMENT OF SERVERS.ITS ARRANGEMENT OF SERVERS.IN LANDSCAPE PHASE WE DECIDE ON IN LANDSCAPE PHASE WE DECIDE ON HOW MANY SERVER TO BE HOW MANY SERVER TO BE PYRCHASE.PYRCHASE.WE DECIDE ON SIZING THE SERVER, WE DECIDE ON SIZING THE SERVER, SIZING MEANS HARD DISK RAM , SIZING MEANS HARD DISK RAM , PROCESSER.PROCESSER.DECIDE ON WHERE FROM PURCHASE DECIDE ON WHERE FROM PURCHASE THE SERVER, IBM, HP, HCL, DELL. THE SERVER, IBM, HP, HCL, DELL.

LANSCAPE THREE SERVER LANSCAPE THREE SERVER ARRANGEMENT ARRANGEMENT

DEVELOPMENT SERVERDEVELOPMENT SERVER

QUALITY SERVERQUALITY SERVER

PRODUCTION SERVERPRODUCTION SERVER

DEVELOPMENT SERVERDEVELOPMENT SERVER

DEVELOPMENT SERVER USED BY DEVELOPMENT SERVER USED BY CONSULTANT.CONSULTANT.

IN THIS SERVER CONSULTANT WORK IN THIS SERVER CONSULTANT WORK ON THE COMFIGURATION THE ON THE COMFIGURATION THE BUSINESS PROCESS OF CLIENT INTO BUSINESS PROCESS OF CLIENT INTO SAP.SAP.

QUALITY SERVERQUALITY SERVER

ITS USED BY CONSULTANT AND CORE ITS USED BY CONSULTANT AND CORE USERS.USERS.

ITS USED TO TEST THE SCENARIO.ITS USED TO TEST THE SCENARIO.

PRODUCTION SERVERPRODUCTION SERVER

ITS WILL BE USED BY END USER AND ITS WILL BE USED BY END USER AND CORE USER.CORE USER.

ITS USED TO ENTER DAY TO DAY ITS USED TO ENTER DAY TO DAY TRANSECTION INTO SAP.TRANSECTION INTO SAP.

INFRASTRUCTUREINFRASTRUCTURE

ITS DECIDE REGARDING IMFRASTRUCTURE NEED TO ITS DECIDE REGARDING IMFRASTRUCTURE NEED TO IMPLEMATATION.IMPLEMATATION.

HOW MANY PC’S PURCHASE TO MATE THE NO. OF USER HOW MANY PC’S PURCHASE TO MATE THE NO. OF USER LICENSE.LICENSE.

SERVER ENVIROMENTSERVER ENVIROMENTWHERE TO KEEP THE SERVER I.E. HO OR AT PLANT LOCATION.WHERE TO KEEP THE SERVER I.E. HO OR AT PLANT LOCATION.SECURITY OF SERVERSECURITY OF SERVERTEMPERATURE REQUIREMENTTEMPERATURE REQUIREMENT

VPN CONNECTIVITYVPN CONNECTIVITYVIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THE VIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THE

SERVER FROM REMOTE LOCATION.SERVER FROM REMOTE LOCATION.

IMPLIMENTATION PARTENERIMPLIMENTATION PARTENERWILL LIST OUT ALL THE CONSULTANT WHO ARE GOING TO WILL LIST OUT ALL THE CONSULTANT WHO ARE GOING TO INVOLVE IN THIS PROJECT.INVOLVE IN THIS PROJECT.

AND CLIENT WILL LIST OUT ALL THE CORE USER WHO ARE AND CLIENT WILL LIST OUT ALL THE CORE USER WHO ARE GOING TO INVOLVE IN THIS PROJECT.GOING TO INVOLVE IN THIS PROJECT.

THE NORMAL TEAM SIZE TO IMPLEMENT YHE SAP FOR THE NORMAL TEAM SIZE TO IMPLEMENT YHE SAP FOR UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3 UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3 CONSULTANT.CONSULTANT.

TEAM SIZE TO IMPLEMENT SAP FOR MNC CLIENT OR WELL TEAM SIZE TO IMPLEMENT SAP FOR MNC CLIENT OR WELL KNOWN CLIENT IS 60 OUT OF THAT SD HAS 10 CONSULTANT.KNOWN CLIENT IS 60 OUT OF THAT SD HAS 10 CONSULTANT.

FOR IMPLEMENTATION OF PROJECT FOR EACH MODULE FOR IMPLEMENTATION OF PROJECT FOR EACH MODULE CLIENT WILL PICK UP ONE CORE USER .CLIENT WILL PICK UP ONE CORE USER .

IF THEY ARE IMPLEMENTED SD,MM,PP FICO MODULE THEN IF THEY ARE IMPLEMENTED SD,MM,PP FICO MODULE THEN CLIENT WILL PICK UP FIVE CORE USER . CLIENT WILL PICK UP FIVE CORE USER .

MAIN ROLE OF CORE USER IS HE WILL SHARE CLIENT MAIN ROLE OF CORE USER IS HE WILL SHARE CLIENT BUSINESS PROCESS TO RESPECTIVE CONSULTANTBUSINESS PROCESS TO RESPECTIVE CONSULTANT

CONSULTANT FACILITYCONSULTANT FACILITYTHE NORMAL PROJECT TENEURE FOR THE NORMAL PROJECT TENEURE FOR UNKNOWN DOMESTIC CLIENT IS SIX UNKNOWN DOMESTIC CLIENT IS SIX MONTH . THE NORMAL TENEURE FOR MNC MONTH . THE NORMAL TENEURE FOR MNC CLIENT IS 10 MONTH.CLIENT IS 10 MONTH.IF ITS DOMESTIC CLINT ALL CONSULTANT IF ITS DOMESTIC CLINT ALL CONSULTANT WILL GO TO CLIENT TO IMPLEMENT THE WILL GO TO CLIENT TO IMPLEMENT THE SAP , IF IT’S A FOREIGN CLIENT THEN EACH SAP , IF IT’S A FOREIGN CLIENT THEN EACH MODULE ONE PERSON GO TO CLIENT MODULE ONE PERSON GO TO CLIENT PLACE AND REMAINING PEOPLE FROM PLACE AND REMAINING PEOPLE FROM OFFSHORE WORKING.OFFSHORE WORKING.IN THIS PHASE THEY DECIDE WHO WILL IN THIS PHASE THEY DECIDE WHO WILL TAKE CARE OF FOOD EXPENCES , TAKE CARE OF FOOD EXPENCES , ACCOMODATION LOCAL TRAVELLING ACCOMODATION LOCAL TRAVELLING EXPENCES , WORK ENVIROMENT, EXPENCES , WORK ENVIROMENT, LAPTOPS. LAPTOPS.

GO LIVE DATEGO LIVE DATE

IT’S A DATE FROM WHICH CLIENT IT’S A DATE FROM WHICH CLIENT WILL START USING SAP .WILL START USING SAP .GO LIVE DATE MEANS HANDELING GO LIVE DATE MEANS HANDELING OVER SAP TO CLIENT.OVER SAP TO CLIENT.AFTER COMPLICATION OF PROJECT AFTER COMPLICATION OF PROJECT PREPERATION PHASE THE PREPERATION PHASE THE IMPLEMENTATION PARTERNER IMPLEMENTATION PARTERNER MANAGEMENT WILL COME BACK AND MANAGEMENT WILL COME BACK AND CONDUCT KICK OFF MEETING .CONDUCT KICK OFF MEETING .

KICK OFF MEETINGKICK OFF MEETING

ITS MEANS STARTING OF.ITS MEANS STARTING OF.

IN THIS THEY WILL INVITE ALL THE IN THIS THEY WILL INVITE ALL THE CONSULTANT WHO GOING TO INVOLVE IN CONSULTANT WHO GOING TO INVOLVE IN THE IMPLEMENTATION PROJECT.THE IMPLEMENTATION PROJECT.

AFTER KICK OFF MEETING CONSULTANT AFTER KICK OFF MEETING CONSULTANT MOVES TO CLIENT PLACE TO START THE MOVES TO CLIENT PLACE TO START THE IMPLEMENTATION PROJECT.IMPLEMENTATION PROJECT.

KICK OFF MEETING KICK OFF MEETING DISCUSSION TOPIC DISCUSSION TOPIC

THEY MENTION RULES AND THEY MENTION RULES AND REGULATION OF CLIENTS.REGULATION OF CLIENTS.ROLES AND RESPONCIBILITY OFF ROLES AND RESPONCIBILITY OFF CONSULTANT.CONSULTANT.INTRODUCTION ABOUT CLIENT.INTRODUCTION ABOUT CLIENT.THEY WILL SHARE THE CORE USER THEY WILL SHARE THE CORE USER IMFORMATION .IMFORMATION .GO LIVE DATE SHARE.GO LIVE DATE SHARE.STARTING DATE.STARTING DATE.

BUSINESS BLUE PRINTBUSINESS BLUE PRINT

AS CONSULTANT WE WILL INVOLVE FROM AS CONSULTANT WE WILL INVOLVE FROM BUSINESS BLUE PRINT PHASE.BUSINESS BLUE PRINT PHASE.IN THIS PHASE WE WILL GATHERD THE IN THIS PHASE WE WILL GATHERD THE INFORMATION OF CLIENT BUSINESS INFORMATION OF CLIENT BUSINESS PROCESS. PROCESS. ON THE BASIS OF THE DATA WE WILL ON THE BASIS OF THE DATA WE WILL PLANE TO CONVERT LEGACY SYSTEM TO PLANE TO CONVERT LEGACY SYSTEM TO SAP.SAP.THERE ARE VARIOUS STEPES FOR BBP THERE ARE VARIOUS STEPES FOR BBP PHASE.PHASE.

BBP PHASE STEPES BBP PHASE STEPES

REQUIREMENT GATHERING REQUIREMENT GATHERING

BBP DOCUMENTBBP DOCUMENT

REQUIREMENT GATHERING REQUIREMENT GATHERING EVERY DAY CONSULTANT WILL GO TO EVERY DAY CONSULTANT WILL GO TO CORE USER PLACE AND ASK THE CORE USER PLACE AND ASK THE QUESTION AND WHATEVER CORE USER QUESTION AND WHATEVER CORE USER EXPLAIN WILL BE NOTE DOWN.EXPLAIN WILL BE NOTE DOWN.ON THE BASIS OF QUESTIONARY WE WILL ON THE BASIS OF QUESTIONARY WE WILL GATHERED THE REQUIREMENT FROM GATHERED THE REQUIREMENT FROM CORE USER AND QUESTIONARY WILL BE CORE USER AND QUESTIONARY WILL BE PROVIDED BY IMPLIMENTATION PARTENER.PROVIDED BY IMPLIMENTATION PARTENER.EVERY DAY AFTER COMPLETION OF EVERY DAY AFTER COMPLETION OF REQUIREMENT GATHERING WE WILL COME REQUIREMENT GATHERING WE WILL COME BACK AND PREPAIR DOCUMENT CALLED AS BACK AND PREPAIR DOCUMENT CALLED AS ---IS DOC.---IS DOC.THIS ACTIVITY WILL TAKE A APROXIMATELY THIS ACTIVITY WILL TAKE A APROXIMATELY TWO MONTH.TWO MONTH.

BBP DOCUMENTBBP DOCUMENT

AFTER REQUIREMENT GATHERING AFTER REQUIREMENT GATHERING WE WILL PREPAIR BBP DOCUMENT WE WILL PREPAIR BBP DOCUMENT AND WE WILL TAKE BBP DOCUMENT AND WE WILL TAKE BBP DOCUMENT SIGN OFF FROM CORE USER.SIGN OFF FROM CORE USER.

AS----IS TO----BE

BBP DOCUMENT CONSIST OF AS---IS AND TO---BE.BBP DOCUMENT CONSIST OF AS---IS AND TO---BE.AS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT AND AS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT AND TO---BE CONSIST OF HOW THE PRESENT BUSINESS PROCESS OF THE TO---BE CONSIST OF HOW THE PRESENT BUSINESS PROCESS OF THE CLIENT IS GOING TO SAP.CLIENT IS GOING TO SAP.WHILE PREPARING A TO----BE DOCUMENT WILL FIND SOME GAP .WHILE PREPARING A TO----BE DOCUMENT WILL FIND SOME GAP .THE PRESENT BUSINESS PROCESS OF CLIENT FOR WHICH THERE IS THE PRESENT BUSINESS PROCESS OF CLIENT FOR WHICH THERE IS NO SOLUTION FROM SAP IS CALLED GAP.NO SOLUTION FROM SAP IS CALLED GAP.WHEN EVER WE FIND GAP WE PREPARE GAP ANALYSIS DOCUMENT.WHEN EVER WE FIND GAP WE PREPARE GAP ANALYSIS DOCUMENT.ITS CONSIST OF CLEARE DECSRIPTION OF GAP , ESTIMATED EFFORTS ITS CONSIST OF CLEARE DECSRIPTION OF GAP , ESTIMATED EFFORTS REGARDING FUNCTIONAL MANDAYS AND TECHNICAL MAN DAYS.REGARDING FUNCTIONAL MANDAYS AND TECHNICAL MAN DAYS.AFTER PREPARING A BBP DOCUMENT WE WILL SEND THE DOCUMENT AFTER PREPARING A BBP DOCUMENT WE WILL SEND THE DOCUMENT TO CORE USER FOR COMFIRMATION.TO CORE USER FOR COMFIRMATION.CORE USER HAS GO THROUGH DOCUMENT AND EVERY THINGS ARE CORE USER HAS GO THROUGH DOCUMENT AND EVERY THINGS ARE OK THEN , CORE USER WILL SEND A COMFIRMATION MAIL.OK THEN , CORE USER WILL SEND A COMFIRMATION MAIL.AFTER COMFIRMATION MAIL WE WILL TAKE A SIGNATURE ON SIGN AFTER COMFIRMATION MAIL WE WILL TAKE A SIGNATURE ON SIGN OFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECT OFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECT IMPLEMENTATION. IMPLEMENTATION. WE WILL TAKE THE SIGNATURE OF CORE USER , CLIENT PM , OUR WE WILL TAKE THE SIGNATURE OF CORE USER , CLIENT PM , OUR PM ,AND CONSULTANT SIGNATURE.PM ,AND CONSULTANT SIGNATURE.SUBMIT ONE COPY TO CLIENT OFFICE AND ANATHER ONE TO SUBMIT ONE COPY TO CLIENT OFFICE AND ANATHER ONE TO IMPLEMENTATION PARTENER.IMPLEMENTATION PARTENER.WITH OUT SIGNOUT WE CAN’T GO FURTHER.WITH OUT SIGNOUT WE CAN’T GO FURTHER.THIS PHASE TAKE A TWO MONTH .THIS PHASE TAKE A TWO MONTH .THIS PHASE IS MOST CRITICAL PHASE BECAUSE HOW TO GATHERED THIS PHASE IS MOST CRITICAL PHASE BECAUSE HOW TO GATHERED THE ACCURATE INFORMATION TO MAKE SUCCESS OF PROJECTTHE ACCURATE INFORMATION TO MAKE SUCCESS OF PROJECT..

REALISATION PHASEREALISATION PHASEIN REALISATION PHASE WE WILL ENTER INTO IN REALISATION PHASE WE WILL ENTER INTO DEVELOPMENT SERVER TO CONFIGURE THE DEVELOPMENT SERVER TO CONFIGURE THE CLIENT BUSINESS PROCESS INTO SAP.CLIENT BUSINESS PROCESS INTO SAP.ITS MEANS MAPING TO---BE PROCESS INTO SAP.ITS MEANS MAPING TO---BE PROCESS INTO SAP.CONFIGURATION DEVIDED INTO TWO TYPE. CONFIGURATION DEVIDED INTO TWO TYPE. BASELINE BASELINE COMFIGURATION FINAL COMFIGURATION FINAL COMFIGURATIONCOMFIGURATIONBASELINE COMFIGURATION IS THE SPECIFIC FOR BASELINE COMFIGURATION IS THE SPECIFIC FOR ONE MODULE FOR WHICH NO NEED TO DEPEND ON ONE MODULE FOR WHICH NO NEED TO DEPEND ON OTHER MODULECONSULTANT.OTHER MODULECONSULTANT.FINAL COMFIGURATION HAS TO DEPEND ON OTHER FINAL COMFIGURATION HAS TO DEPEND ON OTHER MODULE.MODULE.FIRST WE COMPLETE THE BASELINE FIRST WE COMPLETE THE BASELINE COMFIGURATION AND THEN GO FOR FINAL COMFIGURATION AND THEN GO FOR FINAL COMFIGURATION.COMFIGURATION.

FUNCTIONAL SPECIFICATION FUNCTIONAL SPECIFICATION DOCUMENT DOCUMENT

IN THIS PHASE DURING FINAL IN THIS PHASE DURING FINAL COMFIGURATION WE WILL PREPARE COMFIGURATION WE WILL PREPARE FUNCTIONAL SPECIFICATION DOCUMENT.FUNCTIONAL SPECIFICATION DOCUMENT.

ANY CLIENT REQUIREMENT FOR WHICH IF ANY CLIENT REQUIREMENT FOR WHICH IF YOU REQUIRED THE HELP OF ABAP YOU YOU REQUIRED THE HELP OF ABAP YOU HAVE TO PREPARE F. S. DOC.HAVE TO PREPARE F. S. DOC.

REQUEST NUMBERREQUEST NUMBER

IN REALISATION IN REALISATION PHASE WHEN PHASE WHEN WE SAVE THE WE SAVE THE COMFIGURATION COMFIGURATION IN PERTICULAR IN PERTICULAR REQUEST REQUEST NUMBER.NUMBER.REQUEST REQUEST NO.WILL HELP NO.WILL HELP TO TRNSPORT TO TRNSPORT THE THE COMFIGURATION COMFIGURATION FROM ONE FROM ONE SERVER TO SERVER TO ANATHER ANATHER SERVER.SERVER.

TYPE OF REQUEST TYPE OF REQUEST

WE HAVE TWO TYPE OF REQUEST.WE HAVE TWO TYPE OF REQUEST.

WORKBENCH REQUESTWORKBENCH REQUEST

CUSTOMISING REQUESTCUSTOMISING REQUEST

WORK BENCH REQUESTWORK BENCH REQUEST

WHAT EVER ABAPER WILL DO WHAT EVER ABAPER WILL DO CHANGES THAT WILL SAVED INTO CHANGES THAT WILL SAVED INTO WORK BWNCH REQUEST.WORK BWNCH REQUEST.ALL WORK BENCH REQUEST ARE ALL WORK BENCH REQUEST ARE CROSSED CLIENT.CROSSED CLIENT.IF WE DO COMFIGUERATION IN ONE IF WE DO COMFIGUERATION IN ONE CLINT THEN ITS AUTOMATICALLY CLINT THEN ITS AUTOMATICALLY UPDATES INTO OTHER CLIENT WITHIN UPDATES INTO OTHER CLIENT WITHIN SERVER.SERVER.

CUSTOMISING REQUESTCUSTOMISING REQUEST

WHAT EVER FUNCTIONAL WHAT EVER FUNCTIONAL CONSULTANT WILL DO THE CHANGES CONSULTANT WILL DO THE CHANGES WILL SAVED INTO CUSTOMISING WILL SAVED INTO CUSTOMISING REQUEST.REQUEST.

ELEMENT OF THE REQUEST ELEMENT OF THE REQUEST

EACH REQUEST CONSIST OF TWO EACH REQUEST CONSIST OF TWO SUB REQUEST SUB REQUEST

PARENT REQUEST & CHILD REQUEST.PARENT REQUEST & CHILD REQUEST.

PARENT REQUEST WILL HELP TO PARENT REQUEST WILL HELP TO TRANSFER THE COMFIGUERATION TRANSFER THE COMFIGUERATION FROM ONE SERVER TO ANATHER.FROM ONE SERVER TO ANATHER.

CHILD REQUEST WILL HELP TO CHILD REQUEST WILL HELP TO CARRY THE DATA.CARRY THE DATA.

BASIS CONSULTANT WILL BASIS CONSULTANT WILL TRANSPORT THE REQUEST FROM TRANSPORT THE REQUEST FROM

ONE SERVER TO ANATHER .ONE SERVER TO ANATHER .

CONSULTANT ROLE CONSULTANT ROLE INTRANSPORTING THE INTRANSPORTING THE

REQUESTREQUEST

WE HAVE TO REALIESE ALL THE WE HAVE TO REALIESE ALL THE REQUEST.REQUEST.

AND TAKE THE LIST OF ALL THE AND TAKE THE LIST OF ALL THE REQUEST NO. IN EXCEL FILE AND REQUEST NO. IN EXCEL FILE AND SEND IT TO BASIS CONSULTANT.SEND IT TO BASIS CONSULTANT.

BASIS CONSULTANT WILL BASIS CONSULTANT WILL TRANSPORT ALL THE REQUEST FROM TRANSPORT ALL THE REQUEST FROM ONE SERVER TO ANATHER SERVER. ONE SERVER TO ANATHER SERVER.

AFTER COMPLITION OF ALL THE AFTER COMPLITION OF ALL THE COMFIGUIRATION BASIS COMFIGUIRATION BASIS

CONSULTANT WILL TRANSPORT CONSULTANT WILL TRANSPORT ALL COMFIGUERATION FROM ALL COMFIGUERATION FROM DEVELOPMENT SERVER TO DEVELOPMENT SERVER TO

QUALITY SERVER.THEN WE DO QUALITY SERVER.THEN WE DO A TESTING IN QUALITY SERVER.A TESTING IN QUALITY SERVER.

TYPE OF TESTING IN QUALITY TYPE OF TESTING IN QUALITY SERVERSERVER

UNIT TESTINGUNIT TESTING , IN WHICH ITESTING IS , IN WHICH ITESTING IS SPECIFIC TO ONE MODULE.SPECIFIC TO ONE MODULE.

INTEGRATION TESTING ,INTEGRATION TESTING , FOR WHICH FOR WHICH YOU HAVE TO DEPEND UPON OTHER YOU HAVE TO DEPEND UPON OTHER MODULE CONSULTANT.MODULE CONSULTANT.

TEST CASE DOCUMENTTEST CASE DOCUMENT

ON THE BASIS OF ON THE BASIS OF TEST CASE TEST CASE DOCUMENTWE DOCUMENTWE WILL DO THE WILL DO THE TESTING.TESTING.

TEST CASE TEST CASE DOCUMENT IS DOCUMENT IS CONSIST OF CONSIST OF SHOWN FIG.SHOWN FIG.

WHAT TO TEST WHAT TO TEST

HOW TO TEST HOW TO TEST

EXPECTED RESULTEXPECTED RESULT

ACTUAL RESULT ACTUAL RESULT

STATUSSTATUS

TESTADE TESTADE DOCUMENTDOCUMENT

USER MANUAL DOCUMENTUSER MANUAL DOCUMENTAFTER COMPLETION OF TESTING WE WILL AFTER COMPLETION OF TESTING WE WILL PREPARE A USER MANUAL DOCUMENT IS A PREPARE A USER MANUAL DOCUMENT IS A GUADELINE TO USER.GUADELINE TO USER.

ITS CONSIST OF STEP BY STEP PROCESS ITS CONSIST OF STEP BY STEP PROCESS OF CREATING MASTER DATA AND OF CREATING MASTER DATA AND TRANSACTION DATA ALONG WITH SCREEN TRANSACTION DATA ALONG WITH SCREEN SHOTS.SHOTS.

EX- MASTER DATA CUSTOMER MASTER EX- MASTER DATA CUSTOMER MASTER MATERIAL MASTER, TRANSACTION DATA MATERIAL MASTER, TRANSACTION DATA ENQUARY, QUASTIONARY ORDER TO ENQUARY, QUASTIONARY ORDER TO DELIVEY, INVOLIA.DELIVEY, INVOLIA.

AFTER PREPARING A USER MANUAL DOC AFTER PREPARING A USER MANUAL DOC WE WILL SEND THIS DOC TO CORE USER.WE WILL SEND THIS DOC TO CORE USER.

CONFIGUERATION DOCUMENT CONFIGUERATION DOCUMENT

COMFIGUERATION DOC CONSIST THE COMFIGUERATION DOC CONSIST THE SCREEN SHOTS OF ALL THE SCREEN SHOTS OF ALL THE COMFIGUERATION MADE FOR THIS COMFIGUERATION MADE FOR THIS PERTICULAR CLIENT.PERTICULAR CLIENT.

PURPOSE OF COMFIGUERATION DOC PURPOSE OF COMFIGUERATION DOC IS KNOWLEDGE TRANSFER. (K. T.) IS KNOWLEDGE TRANSFER. (K. T.)

IN REALISATION WE WILL IN REALISATION WE WILL PREPARE A FOUR DOCUMENTPREPARE A FOUR DOCUMENTFUNCTIONAL SPECIFICATION DOCFUNCTIONAL SPECIFICATION DOCTEST CASE DOCTEST CASE DOCUSER MSNUAL DOC USER MSNUAL DOC COMFIGUERATION DOCCOMFIGUERATION DOC

AFTER PREPARING A DOCUMENT WE WILL AFTER PREPARING A DOCUMENT WE WILL GO TO FINAL PREPERATION PHASE.GO TO FINAL PREPERATION PHASE.

PERIOD OF REALISATION PHASE IS PERIOD OF REALISATION PHASE IS TWO TWO MONTHS.MONTHS.

FINAL PREPERATION PHASE FINAL PREPERATION PHASE TRAINING TO CORE USER – 10 DAYS TRAINING TO CORE USER – 10 DAYS WE GIVEN A TRAINING TO CORE USER WE GIVEN A TRAINING TO CORE USER

HOW TO CREAT A MASTER DATA &HOW TO CREAT A MASTER DATA &HOW TO CREAT ATRASANCTACTION DATAHOW TO CREAT ATRASANCTACTION DATA

WE WILL ASK THE CORE USER TO TEST WE WILL ASK THE CORE USER TO TEST THE SCENARIO AND COMFERM IT . CORE THE SCENARIO AND COMFERM IT . CORE USER HAS TO TEST ALL THE SCENAREO USER HAS TO TEST ALL THE SCENAREO AND IF EVERY THINGS ARE OK THEN USER AND IF EVERY THINGS ARE OK THEN USER WILL GIVE SIGN OFF WE CALL IT AS WILL GIVE SIGN OFF WE CALL IT AS UAT UAT SIGN OFF .SIGN OFF .AFTER GETTING A UAT SIGN OFF WE WILL AFTER GETTING A UAT SIGN OFF WE WILL TRANSPORT ALL THE REQUEST FROM TRANSPORT ALL THE REQUEST FROM QUALITY SERVER TO PRODUCTION SERVER QUALITY SERVER TO PRODUCTION SERVER . .

CUT OVER ACTIVITY CUT OVER ACTIVITY

AFTER TRANSFERING A ALL REQUEST AFTER TRANSFERING A ALL REQUEST FROM QUALITY SERVER TO PRODUCTION FROM QUALITY SERVER TO PRODUCTION SERVER WE WILL DO THE CUT OVER SERVER WE WILL DO THE CUT OVER ACTIVITY .ACTIVITY .CUT OVER ACTIVITY IS THE UPLOADING OF CUT OVER ACTIVITY IS THE UPLOADING OF MASTER DATA FROM ONE LEGACY TO SAP MASTER DATA FROM ONE LEGACY TO SAP WHILE UPLOADING THE DATA FROM WHILE UPLOADING THE DATA FROM LEGACY TO SAP .LEGACY TO SAP .DURING THIS ACTIVITY CLIENT HAS TO DURING THIS ACTIVITY CLIENT HAS TO STOP THE BUSINESS TO AVOID DATA STOP THE BUSINESS TO AVOID DATA DESCREPENCY.DESCREPENCY.

CUT OVER STRATEGIES CUT OVER STRATEGIES

PLANNING ON WENT TO UPLOAD THE PLANNING ON WENT TO UPLOAD THE DATA AND REQUESTING THE CLIENT DATA AND REQUESTING THE CLIENT TO STOP BUSINESS.TO STOP BUSINESS.

CUT OVER PERIOD CUT OVER PERIOD

ACTUAL NO. OF DAYS TAKEN TO ACTUAL NO. OF DAYS TAKEN TO UPLOAD THE DATA FROM LEGACY TO UPLOAD THE DATA FROM LEGACY TO SAP.SAP.

AFTER UPLOADING THE DATA AFTER UPLOADING THE DATA FROM LEGACY TO SAP THEN FROM LEGACY TO SAP THEN WE DECLARE GO LIVE . GO WE DECLARE GO LIVE . GO LIVE MEANS HANDOVER SAP LIVE MEANS HANDOVER SAP TO CLIENT I.E. FROM THAT TO CLIENT I.E. FROM THAT DAY ONWARD USER WILL DAY ONWARD USER WILL STAND USING SAP.STAND USING SAP.AFTER GO LIVE WE WILL GIVE AFTER GO LIVE WE WILL GIVE 3 MONTH FIRST PRODUCTION 3 MONTH FIRST PRODUCTION SUPPORT.SUPPORT.

SUPPORTSUPPORT

SUPPORT PARTENER SOLVING THE ISSUE SUPPORT PARTENER SOLVING THE ISSUE RAISED BY THE CLIENT WHO ALREADY RAISED BY THE CLIENT WHO ALREADY IMPLEMENTED SAP.IMPLEMENTED SAP.WHEN EVER SUPPORT PARTENER GETS A NEW WHEN EVER SUPPORT PARTENER GETS A NEW PROJECT THE SUPPORT PARTENER AND THE PROJECT THE SUPPORT PARTENER AND THE CLIENT HAS TO ENTER INTO AN AGREEMENT CLIENT HAS TO ENTER INTO AN AGREEMENT CALLED AS SERVICE LEVEL AGREEMENT.CALLED AS SERVICE LEVEL AGREEMENT.IBM ALKEM CLIENT IBM ALKEM CLIENT

TCSTCS

SLA

AS CONSULTANTAS CONSULTANT

CONSULTANT SHOULD HAVE KNOW FROM CONSULTANT SHOULD HAVE KNOW FROM SOME IMFORMATION FROM SLASOME IMFORMATION FROM SLAPRIORITY ISSUE OR KICKETS .PRIORITY ISSUE OR KICKETS .GENERALLY TICKETS ARE CLASSIFIDE INTO GENERALLY TICKETS ARE CLASSIFIDE INTO THREE TYPE.THREE TYPE.HIGH PRIORITY ISSUE WIILSOLVE IN 4 HRSHIGH PRIORITY ISSUE WIILSOLVE IN 4 HRSMEDIAN PRIORITY ISSUE WIIL SOLVED IN 24 MEDIAN PRIORITY ISSUE WIIL SOLVED IN 24 HRS.HRS.LOW PRIORITY ISSUE WILL SOLVED IN 48HRSLOW PRIORITY ISSUE WILL SOLVED IN 48HRS

ANY ISSUE IF ITS STOPING ANY ISSUE IF ITS STOPING THE CLIENT BUSSINESS THE CLIENT BUSSINESS PROCESS THEN WE PROCESS THEN WE TREATED AS HIGH PRIORITY TREATED AS HIGH PRIORITY ISSUE. IT WILL SOLVED IN 4 ISSUE. IT WILL SOLVED IN 4 HRS.HRS.

CHANGE REQUESTCHANGE REQUEST

ANY THING THINGS ANY THING THINGS CLIENT HAS ASKING CLIENT HAS ASKING FOR NEW , BUT THERE FOR NEW , BUT THERE IS NO PRESENT IS NO PRESENT COMFIGUERATIONTHECOMFIGUERATIONTHEN WE TREATED AS N WE TREATED AS CHANGE REQUEST.CHANGE REQUEST.WHEN EVER WE GET WHEN EVER WE GET CHANGE REQUEST CHANGE REQUEST NEED CREATE NEED CREATE CHANGE REQUEST CHANGE REQUEST DOC .DOC .

CLEAR DESCREPTION CLEAR DESCREPTION OF ISSUE OF ISSUE

EXPECTED SOLUTIONEXPECTED SOLUTION

APROXIMATE APROXIMATE EFFORTS EFFORTS

FUNCTIONAL MAN FUNCTIONAL MAN DAYSDAYS

TECHNICAL MAN TECHNICAL MAN DAYSDAYS

AFTER PREPARING CHANGES REQUEST AFTER PREPARING CHANGES REQUEST DOC WE WILL SEND THIS DOC TO DOC WE WILL SEND THIS DOC TO SUPERIOR FOR REVIEW .SUPERIOR FOR REVIEW .AFTER REVIEW WE WILL SEND THIS DOC AFTER REVIEW WE WILL SEND THIS DOC TO CORE USER FOR APPROVAL FROM TO CORE USER FOR APPROVAL FROM CORE USER THEN WE START WORKING ON CORE USER THEN WE START WORKING ON ISSUE.ISSUE.WHEN EVER SUPPORT PARTNER GETS A WHEN EVER SUPPORT PARTNER GETS A NEW PROJECT THEN SUPPORT PARTENER NEW PROJECT THEN SUPPORT PARTENER WILL CONDUCT KICK OFF MEETING .WILL CONDUCT KICK OFF MEETING .THEY WILL INVITE ALL THE CONSULTANT THEY WILL INVITE ALL THE CONSULTANT WHO ARE GOING TO INVOLVE IN THE WHO ARE GOING TO INVOLVE IN THE SUPPORT PROJECT.SUPPORT PROJECT.APROXIMATE TEAM SIZE FOR UNKNOWN APROXIMATE TEAM SIZE FOR UNKNOWN DOMESTIC CLIENT IS 12 MEMBERS OUT OF DOMESTIC CLIENT IS 12 MEMBERS OUT OF THAT SD HAS 2 & IN MNC 50 & 12 RESP. THAT SD HAS 2 & IN MNC 50 & 12 RESP.

SUPPORT PROJECT KICK OFF SUPPORT PROJECT KICK OFF MEETINGMEETING

GIVES THE IMFORMATION ABOUT CLIENT GIVES THE IMFORMATION ABOUT CLIENT BUSSINESS PROCESS .BUSSINESS PROCESS .RULES AND REGULATION OF CLIENT.RULES AND REGULATION OF CLIENT.ROLES AND RESPONCIBILITY OF ROLES AND RESPONCIBILITY OF CONSULTANT.CONSULTANT.CORE USER INFORNATION.CORE USER INFORNATION.STARTING DATE.STARTING DATE.

AFTER KICK OFF MEETING ALL THE AFTER KICK OFF MEETING ALL THE CONSULTANT WILL MOOV TO CLIENT CONSULTANT WILL MOOV TO CLIENT PLACE FOR KT PROCESS . PLACE FOR KT PROCESS .

K. T. PROCESSK. T. PROCESS

CORE SUER WILL HAND OVER CORE SUER WILL HAND OVER COMFIGUERATION DOCUMENT TO COMFIGUERATION DOCUMENT TO CONSULTANT HAS TO GO THROUGH THE CONSULTANT HAS TO GO THROUGH THE DOC & SIMULTANEOUSLYDO THE SYSTEM DOC & SIMULTANEOUSLYDO THE SYSTEM STUDY .STUDY .AFTER SYSTEM STUDY CONSULTANT HAS AFTER SYSTEM STUDY CONSULTANT HAS TO PREPARE UNDERSTANDING DOC AND TO PREPARE UNDERSTANDING DOC AND GIVE REVERS-KT TO CORE USER . GIVE REVERS-KT TO CORE USER . AFTER REVERS KT CONSULTANT WILL AFTER REVERS KT CONSULTANT WILL COME BACK AND START HANDELING THE COME BACK AND START HANDELING THE ISSUE. ISSUE.

TICKET PROCESSTICKET PROCESS

TICKETS PROCESS TICKETS PROCESS

WHEN END USER FACE ANY PROBLEM WHEN END USER FACE ANY PROBLEM RAISES AN ISSUE WHICH IS CALLED RAISES AN ISSUE WHICH IS CALLED TICKETING ISSUE .TICKETING ISSUE .END USER THE ISSUE TO HELP DESK .END USER THE ISSUE TO HELP DESK .AT THE HELP DESK CORE USER RECEIVED AT THE HELP DESK CORE USER RECEIVED THE ISSUE .THE ISSUE .THE CORE USER TRIES TO SOLVE FIRST IF THE CORE USER TRIES TO SOLVE FIRST IF HE NOT ABLE TO SOLVE THE ISSUE THEN HE NOT ABLE TO SOLVE THE ISSUE THEN HE RAISE THE ISSUE TOWARDS THE ISSUE HE RAISE THE ISSUE TOWARDS THE ISSUE IN TICKETING TOOLS.IN TICKETING TOOLS.IN TICKETING TOOL CORE USER RAISES IN TICKETING TOOL CORE USER RAISES THE ISSUE WITH PRIORITY AS HIGH THE ISSUE WITH PRIORITY AS HIGH MEDIUM , LOW.MEDIUM , LOW.

THE SUPPORT CONSULTANT THE SUPPORT CONSULTANT COORDINATOR RECEIVES THE MAILS COORDINATOR RECEIVES THE MAILS FROM TICKETING TOOL WITH PRIORITY.FROM TICKETING TOOL WITH PRIORITY.

THE CORDINATORS ANALYSE AND THE CORDINATORS ANALYSE AND ALLOCATE THE ISSUES TO RESPECTIVE ALLOCATE THE ISSUES TO RESPECTIVE CONSULTANT.CONSULTANT.

THE CONSULTANT RECEVED THE MAIL THE CONSULTANT RECEVED THE MAIL AND REPLY TO CORE USER END USER AND REPLY TO CORE USER END USER AND COORDINATOR .AND COORDINATOR .

THE CONSULTANT HAS TO MAIL AND THE CONSULTANT HAS TO MAIL AND REPLY TO CORE USER END USER , CC REPLY TO CORE USER END USER , CC COORDINATOR. COORDINATOR.

THE STATUS OF ISSUE ARE AS FOLLOWS .THE STATUS OF ISSUE ARE AS FOLLOWS .

OPEN OPEN

BEING PROCESSBEING PROCESS

WAITAING FOR INFORMTIONWAITAING FOR INFORMTION

WAITAING FOR CONFIRMATIONWAITAING FOR CONFIRMATION

CLOSEDCLOSED

IF THE STATUS IS BEING PROCESS THEN IF THE STATUS IS BEING PROCESS THEN ONLY THE TIME START OTHER THAN BEING ONLY THE TIME START OTHER THAN BEING PROCESS THEN TIME STOP.PROCESS THEN TIME STOP.

AFTER SENDING THE ACCKOLEDGEMENT AFTER SENDING THE ACCKOLEDGEMENT CONSULTANT HAS TO ANALYSE THE CONSULTANT HAS TO ANALYSE THE TICKET SIZE.TICKET SIZE.

IN SUPPORT WE WILL HAVE PRE IN SUPPORT WE WILL HAVE PRE PRODUCTION SERVER .PRODUCTION SERVER .

PRE PRODUCTION SERVER IS MIRROR PRE PRODUCTION SERVER IS MIRROR IMAGE OFF PRODUCTION SERVER . WE IMAGE OFF PRODUCTION SERVER . WE ALSO CALLED AS SLAGING SERVER .ALSO CALLED AS SLAGING SERVER .

WE TIMES TO DO THE SMALL WHAT END WE TIMES TO DO THE SMALL WHAT END USER IS DOING IT IN PRODUCTION SERVER.USER IS DOING IT IN PRODUCTION SERVER.

IF THE END USER IS GETTING ERROR IN IF THE END USER IS GETTING ERROR IN PRODUCTION SERVER THEN WE SHOULD PRODUCTION SERVER THEN WE SHOULD ALSO GET THE SAME ERROR IN PRE ALSO GET THE SAME ERROR IN PRE PRODUCTION SERVER. PRODUCTION SERVER.

AFTER GETTING THE ERROR WE GO TO AFTER GETTING THE ERROR WE GO TO DEVELOPMENT ERROR AND DO DEVELOPMENT ERROR AND DO NECESSARY COMFIGUERATIONS.NECESSARY COMFIGUERATIONS.THEN WE TRANSPORT FROM THEN WE TRANSPORT FROM DEVELOPMENT TO QUALITY SERVER AND DEVELOPMENT TO QUALITY SERVER AND ASK THE CORE USER TO TEST IT ASK THE CORE USER TO TEST IT COMFIRM .COMFIRM .AFTER CONFIRMATION WE WILL AFTER CONFIRMATION WE WILL TRANSPORT THE CONFIGUERATION FROM TRANSPORT THE CONFIGUERATION FROM QUALITY SERVER TO PRODUCTION QUALITY SERVER TO PRODUCTION SERVER.SERVER.AFTER TRANSPORTING COMFIGUERATION AFTER TRANSPORTING COMFIGUERATION TO PRODUCTION SERVER WE WILL PUT TO PRODUCTION SERVER WE WILL PUT THE STATUS AS CLOSED.THE STATUS AS CLOSED.

LEVEL IN SUPPORTS LEVEL IN SUPPORTS

GENERALLY THE LEVEL IN THE GENERALLY THE LEVEL IN THE SUPPORTS WE WILL BE CLASSIFIED SUPPORTS WE WILL BE CLASSIFIED IN 3 LEVEL IN 3 LEVEL

LEVEL 1 – HIGH PRIORITY ISSUE LEVEL 1 – HIGH PRIORITY ISSUE

LEVEL 2 _ MEDIUM PRIORITY ISSUES LEVEL 2 _ MEDIUM PRIORITY ISSUES

LEVEL 3_ CHANGE REQUEST & LEVEL 3_ CHANGE REQUEST & ENHANCEMENT ENHANCEMENT