際際滷

際際滷Share a Scribd company logo

Sap sd implementation by niteen vaidya

Download as PPT, PDF
N
Niteen Vaidya

The document discusses SAP SD (Sales and Distribution) and the SAP implementation process. It describes SAP SD as an ERP package that specifies planning across departments and utilizes the 4Ms (Men, Money, Material, Machinery). It notes that SAP uses a three-tier architecture with presentation, application, and database layers. It then outlines the roles of consultants in implementing SAP projects using the ASAP (Accelerated SAP) methodology and its five phases: project preparation, business blueprints, realization, final preparation, and go-live support.

1 of 64
Downloaded 18 times
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 ALLITS SPECIFIES THE PLANNING IN ALL DEPARTMENT IN AN ORGANISATIONDEPARTMENT IN AN ORGANISATION ITS SPECIFIES HOW TO UTILISED THEITS SPECIFIES HOW TO UTILISED THE 4MS4MS MENMEN MONEYMONEY MATERIALMATERIAL MACHINERYMACHINERY
SAP IS THREE TIERSAP IS THREE TIER ARCHITECTUREARCHITECTURE PRESENTATION LAYERPRESENTATION LAYER APPLICATION LAYERAPPLICATION LAYER DATABASE LAYERDATABASE LAYER
PRESENTATION LAYERPRESENTATION LAYER SYSTEM USED BY END USER THIS ISSYSTEM USED BY END USER THIS IS THE PRESENTATION LAYERTHE PRESENTATION LAYER ITS LIVE DAY TO DAY TRANSECTIONITS LIVE DAY TO DAY TRANSECTION DONE ON THISDONE ON THIS
APPLICATION LAYERAPPLICATION LAYER ANY REQUEST SEND BYANY REQUEST SEND BY PRESENTATION LAYER FIRST TAKENPRESENTATION LAYER FIRST TAKEN BY APPLICATION LAYER .BY APPLICATION LAYER . TAKE THE DATA AND SEND TO DATATAKE THE DATA AND SEND TO DATA BASE LAYER FURTHER TAKE THEBASE LAYER FURTHER TAKE THE PROCESSED DATA FROM DATA BASEPROCESSED DATA FROM DATA BASE AND SEND IT TO PRESENTATIONAND SEND IT TO PRESENTATION LAYERLAYER ITS ACT AS MEDIATORITS ACT AS MEDIATOR
DATABASE LAYERDATABASE LAYER ITS CONSIST OF DATA ONLYITS CONSIST OF DATA ONLY
ROLES AND RESPONCIBILITYROLES AND RESPONCIBILITY OF CONSULTANT INOF CONSULTANT IN IMPLIMENTATION OF PROJECTIMPLIMENTATION OF PROJECT COMFIGUIRING THE CLIENTS BUSINESSCOMFIGUIRING THE CLIENTS BUSINESS PROCESS INTO SAP WHO MIGHT USINGPROCESS INTO SAP WHO MIGHT USING SOME LEGACY SYSTEM .SOME LEGACY SYSTEM . LEGACY SYSTEM IS THE THE SYSTEMLEGACY SYSTEM IS THE THE SYSTEM OTHER THAN SAP .OTHER THAN SAP . ANY CLIENT WHO WANT TO IMPLIMENT SAPANY CLIENT WHO WANT TO IMPLIMENT SAP THEN CONSULTANT HAS TO GO WITHTHEN CONSULTANT HAS TO GO WITH SPECIFIC METHODOLOGY CALLED ASAPSPECIFIC METHODOLOGY CALLED ASAP METHODOLOGY.METHODOLOGY.
ASAPASAP ACCELERATED SAP IS CALLED ASAPACCELERATED SAP IS CALLED ASAP ITS CONSIST OF THE GUIDELINES TOITS CONSIST OF THE GUIDELINES TO IMPLEMENT THE SAP.IMPLEMENT THE SAP. ITS STEP BY STEP PROCESS OFITS 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 NEEDAS CONSULTANT WE DO NOT NEED TO INVOLVED IN THE PROJECTTO INVOLVED IN THE PROJECT PREPERATION PHASE.PREPERATION PHASE. ONLY THE MANAGEMENT FROM THEONLY THE MANAGEMENT FROM THE IMPLIMENTATION PARTENER ANDIMPLIMENTATION PARTENER AND CLIENT MANAGEMENT INVOLVE INTOCLIENT MANAGEMENT INVOLVE INTO PROJECT PREPERATION.PROJECT PREPERATION.
PHASESES OF PROJECTPHASESES OF PROJECT PREPERATIONPREPERATION USER LICENSESUSER LICENSES LANDSCAPELANDSCAPE INFRASTRUCTUREINFRASTRUCTURE IMPLIMENTATION PARTENERIMPLIMENTATION PARTENER CONSULTANT FACILITYCONSULTANT FACILITY GO LIVE DATEGO LIVE DATE
USER LICENSESUSER LICENSES ANY CLIENT IF THEY WANT TOANY CLIENT IF THEY WANT TO IMPLEMENT SAP THEY NEED TOIMPLEMENT SAP THEY NEED TO PURCHASE USER LICENSES FROMPURCHASE USER LICENSES FROM SAP.SAP. BASED ON NO. OF END USERS THEYBASED ON NO. OF END USERS THEY DECIDE HOW MANY USER LICENSESDECIDE HOW MANY USER LICENSES NEED TO PURCHASE FROM SAP.NEED TO PURCHASE FROM SAP. EACH USER LICENSES COST GOINGEACH USER LICENSES COST GOING TO BE APROXIMATELY RS 18000 /-.TO BE APROXIMATELY RS 18000 /-.
AN EVERY YEAR CLINT HAS TO PAYAN EVERY YEAR CLINT HAS TO PAY 22% OF LICENSE COST TO SAP IN THE22% 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 ONIN LANDSCAPE PHASE WE DECIDE ON HOW MANY SERVER TO BEHOW 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 PURCHASEDECIDE ON WHERE FROM PURCHASE THE SERVER, IBM, HP, HCL, DELL.THE SERVER, IBM, HP, HCL, DELL.
LANSCAPE THREE SERVERLANSCAPE THREE SERVER ARRANGEMENTARRANGEMENT DEVELOPMENT SERVERDEVELOPMENT SERVER QUALITY SERVERQUALITY SERVER PRODUCTION SERVERPRODUCTION SERVER
DEVELOPMENT SERVERDEVELOPMENT SERVER DEVELOPMENT SERVER USED BYDEVELOPMENT SERVER USED BY CONSULTANT.CONSULTANT. IN THIS SERVER CONSULTANT WORKIN THIS SERVER CONSULTANT WORK ON THE COMFIGURATION THEON THE COMFIGURATION THE BUSINESS PROCESS OF CLIENT INTOBUSINESS PROCESS OF CLIENT INTO SAP.SAP.
QUALITY SERVERQUALITY SERVER ITS USED BY CONSULTANT AND COREITS 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 ANDITS WILL BE USED BY END USER AND CORE USER.CORE USER. ITS USED TO ENTER DAY TO DAYITS USED TO ENTER DAY TO DAY TRANSECTION INTO SAP.TRANSECTION INTO SAP.
INFRASTRUCTUREINFRASTRUCTURE ITS DECIDE REGARDING IMFRASTRUCTURE NEED TOITS DECIDE REGARDING IMFRASTRUCTURE NEED TO IMPLEMATATION.IMPLEMATATION. HOW MANY PCS PURCHASE TO MATE THE NO. OF USERHOW MANY PCS PURCHASE TO MATE THE NO. OF USER LICENSE.LICENSE. SERVER ENVIROMENTSERVER ENVIROMENT WHERE 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 SERVER TEMPERATURE REQUIREMENTTEMPERATURE REQUIREMENT VPN CONNECTIVITYVPN CONNECTIVITY VIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THEVIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THE SERVER FROM REMOTE LOCATION.SERVER FROM REMOTE LOCATION.
IMPLIMENTATION PARTENERIMPLIMENTATION PARTENER WILL LIST OUT ALL THE CONSULTANT WHO ARE GOING TOWILL 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 AREAND 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 FORTHE NORMAL TEAM SIZE TO IMPLEMENT YHE SAP FOR UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3 CONSULTANT.CONSULTANT. TEAM SIZE TO IMPLEMENT SAP FOR MNC CLIENT OR WELLTEAM 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 MODULEFOR 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 THENIF 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 CLIENTMAIN ROLE OF CORE USER IS HE WILL SHARE CLIENT
CONSULTANT FACILITYCONSULTANT FACILITY THE NORMAL PROJECT TENEURE FORTHE NORMAL PROJECT TENEURE FOR UNKNOWN DOMESTIC CLIENT IS SIXUNKNOWN DOMESTIC CLIENT IS SIX MONTH . THE NORMAL TENEURE FOR MNCMONTH . THE NORMAL TENEURE FOR MNC CLIENT IS 10 MONTH.CLIENT IS 10 MONTH. IF ITS DOMESTIC CLINT ALL CONSULTANTIF ITS DOMESTIC CLINT ALL CONSULTANT WILL GO TO CLIENT TO IMPLEMENT THEWILL GO TO CLIENT TO IMPLEMENT THE SAP , IF ITS A FOREIGN CLIENT THEN EACHSAP , IF ITS A FOREIGN CLIENT THEN EACH MODULE ONE PERSON GO TO CLIENTMODULE ONE PERSON GO TO CLIENT PLACE AND REMAINING PEOPLE FROMPLACE AND REMAINING PEOPLE FROM OFFSHORE WORKING.OFFSHORE WORKING. IN THIS PHASE THEY DECIDE WHO WILLIN THIS PHASE THEY DECIDE WHO WILL TAKE CARE OF FOOD EXPENCES ,TAKE CARE OF FOOD EXPENCES , ACCOMODATION LOCAL TRAVELLINGACCOMODATION LOCAL TRAVELLING EXPENCES , WORK ENVIROMENT,EXPENCES , WORK ENVIROMENT, LAPTOPS.LAPTOPS.
GO LIVE DATEGO LIVE DATE ITS A DATE FROM WHICH CLIENTITS A DATE FROM WHICH CLIENT WILL START USING SAP .WILL START USING SAP . GO LIVE DATE MEANS HANDELINGGO LIVE DATE MEANS HANDELING OVER SAP TO CLIENT.OVER SAP TO CLIENT. AFTER COMPLICATION OF PROJECTAFTER COMPLICATION OF PROJECT PREPERATION PHASE THEPREPERATION PHASE THE IMPLEMENTATION PARTERNERIMPLEMENTATION PARTERNER MANAGEMENT WILL COME BACK ANDMANAGEMENT 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 THEIN THIS THEY WILL INVITE ALL THE CONSULTANT WHO GOING TO INVOLVE INCONSULTANT WHO GOING TO INVOLVE IN THE IMPLEMENTATION PROJECT.THE IMPLEMENTATION PROJECT. AFTER KICK OFF MEETING CONSULTANTAFTER KICK OFF MEETING CONSULTANT MOVES TO CLIENT PLACE TO START THEMOVES TO CLIENT PLACE TO START THE IMPLEMENTATION PROJECT.IMPLEMENTATION PROJECT.
KICK OFF MEETINGKICK OFF MEETING DISCUSSION TOPICDISCUSSION TOPIC THEY MENTION RULES ANDTHEY MENTION RULES AND REGULATION OF CLIENTS.REGULATION OF CLIENTS. ROLES AND RESPONCIBILITY OFFROLES AND RESPONCIBILITY OFF CONSULTANT.CONSULTANT. INTRODUCTION ABOUT CLIENT.INTRODUCTION ABOUT CLIENT. THEY WILL SHARE THE CORE USERTHEY 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 FROMAS CONSULTANT WE WILL INVOLVE FROM BUSINESS BLUE PRINT PHASE.BUSINESS BLUE PRINT PHASE. IN THIS PHASE WE WILL GATHERD THEIN THIS PHASE WE WILL GATHERD THE INFORMATION OF CLIENT BUSINESSINFORMATION OF CLIENT BUSINESS PROCESS.PROCESS. ON THE BASIS OF THE DATA WE WILLON THE BASIS OF THE DATA WE WILL PLANE TO CONVERT LEGACY SYSTEM TOPLANE TO CONVERT LEGACY SYSTEM TO SAP.SAP. THERE ARE VARIOUS STEPES FOR BBPTHERE ARE VARIOUS STEPES FOR BBP PHASE.PHASE.
BBP PHASE STEPESBBP PHASE STEPES REQUIREMENT GATHERINGREQUIREMENT GATHERING BBP DOCUMENTBBP DOCUMENT
REQUIREMENT GATHERINGREQUIREMENT GATHERING EVERY DAY CONSULTANT WILL GO TOEVERY DAY CONSULTANT WILL GO TO CORE USER PLACE AND ASK THECORE USER PLACE AND ASK THE QUESTION AND WHATEVER CORE USERQUESTION AND WHATEVER CORE USER EXPLAIN WILL BE NOTE DOWN.EXPLAIN WILL BE NOTE DOWN. ON THE BASIS OF QUESTIONARY WE WILLON THE BASIS OF QUESTIONARY WE WILL GATHERED THE REQUIREMENT FROMGATHERED THE REQUIREMENT FROM CORE USER AND QUESTIONARY WILL BECORE USER AND QUESTIONARY WILL BE PROVIDED BY IMPLIMENTATION PARTENER.PROVIDED BY IMPLIMENTATION PARTENER. EVERY DAY AFTER COMPLETION OFEVERY DAY AFTER COMPLETION OF REQUIREMENT GATHERING WE WILL COMEREQUIREMENT GATHERING WE WILL COME BACK AND PREPAIR DOCUMENT CALLED ASBACK AND PREPAIR DOCUMENT CALLED AS ---IS DOC.---IS DOC. THIS ACTIVITY WILL TAKE A APROXIMATELYTHIS ACTIVITY WILL TAKE A APROXIMATELY TWO MONTH.TWO MONTH.
BBP DOCUMENTBBP DOCUMENT AFTER REQUIREMENT GATHERINGAFTER REQUIREMENT GATHERING WE WILL PREPAIR BBP DOCUMENTWE WILL PREPAIR BBP DOCUMENT AND WE WILL TAKE BBP DOCUMENTAND WE WILL TAKE BBP DOCUMENT SIGN OFF FROM CORE USER.SIGN OFF FROM CORE USER. AS----IS TO----BE
AS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT ANAS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT AN TO---BE CONSIST OF HOW THE PRESENT BUSINESS PROCESS OF THETO---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 ISTHE 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 EFFORTSITS 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 DOCUMENTAFTER 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 ARECORE 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 SIGNAFTER COMFIRMATION MAIL WE WILL TAKE A SIGNATURE ON SIGN OFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECTOFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECT IMPLEMENTATION.IMPLEMENTATION. WE WILL TAKE THE SIGNATURE OF CORE USER , CLIENT PM , OURWE 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 TOSUBMIT ONE COPY TO CLIENT OFFICE AND ANATHER ONE TO IMPLEMENTATION PARTENER.IMPLEMENTATION PARTENER. WITH OUT SIGNOUT WE CANT GO FURTHER.WITH OUT SIGNOUT WE CANT GO FURTHER. THIS PHASE TAKE A TWO MONTH .THIS PHASE TAKE A TWO MONTH . THIS PHASE IS MOST CRITICAL PHASE BECAUSE HOW TO GATHEREDTHIS 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 PHASE IN REALISATION PHASE WE WILL ENTER INTOIN REALISATION PHASE WE WILL ENTER INTO DEVELOPMENT SERVER TO CONFIGURE THEDEVELOPMENT 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. BASELINEBASELINE COMFIGURATIONCOMFIGURATION FINAL COMFIGURATIONFINAL COMFIGURATION BASELINE COMFIGURATION IS THE SPECIFIC FORBASELINE COMFIGURATION IS THE SPECIFIC FOR ONE MODULE FOR WHICH NO NEED TO DEPENDONE MODULE FOR WHICH NO NEED TO DEPEND ON OTHER MODULECONSULTANT.ON OTHER MODULECONSULTANT. FINAL COMFIGURATION HAS TO DEPEND ONFINAL COMFIGURATION HAS TO DEPEND ON OTHER MODULE.OTHER MODULE. FIRST WE COMPLETE THE BASELINEFIRST WE COMPLETE THE BASELINE COMFIGURATION AND THEN GO FOR FINALCOMFIGURATION AND THEN GO FOR FINAL COMFIGURATION.COMFIGURATION.
FUNCTIONAL SPECIFICATIONFUNCTIONAL SPECIFICATION DOCUMENTDOCUMENT IN THIS PHASE DURING FINALIN THIS PHASE DURING FINAL COMFIGURATION WE WILL PREPARECOMFIGURATION WE WILL PREPARE FUNCTIONAL SPECIFICATION DOCUMENT.FUNCTIONAL SPECIFICATION DOCUMENT. ANY CLIENT REQUIREMENT FOR WHICH IFANY CLIENT REQUIREMENT FOR WHICH IF YOU REQUIRED THE HELP OF ABAP YOUYOU REQUIRED THE HELP OF ABAP YOU HAVE TO PREPARE F. S. DOC.HAVE TO PREPARE F. S. DOC.
REQUEST NUMBERREQUEST NUMBER IN REALISATIONIN REALISATION PHASE WHENPHASE WHEN WE SAVE THEWE SAVE THE COMFIGURATIONCOMFIGURATION IN PERTICULARIN PERTICULAR REQUESTREQUEST NUMBER.NUMBER. REQUESTREQUEST NO.WILL HELPNO.WILL HELP TO TRNSPORTTO TRNSPORT THETHE COMFIGURATIONCOMFIGURATION FROM ONEFROM ONE SERVER TOSERVER TO ANATHERANATHER SERVER.SERVER.
TYPE OF REQUESTTYPE 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 DOWHAT EVER ABAPER WILL DO CHANGES THAT WILL SAVED INTOCHANGES THAT WILL SAVED INTO WORK BWNCH REQUEST.WORK BWNCH REQUEST. ALL WORK BENCH REQUEST AREALL WORK BENCH REQUEST ARE CROSSED CLIENT.CROSSED CLIENT. IF WE DO COMFIGUERATION IN ONEIF WE DO COMFIGUERATION IN ONE CLINT THEN ITS AUTOMATICALLYCLINT THEN ITS AUTOMATICALLY UPDATES INTO OTHER CLIENT WITHINUPDATES INTO OTHER CLIENT WITHIN SERVER.SERVER.
Sap sd implementation by niteen vaidya
CUSTOMISING REQUESTCUSTOMISING REQUEST WHAT EVER FUNCTIONALWHAT EVER FUNCTIONAL CONSULTANT WILL DO THE CHANGESCONSULTANT WILL DO THE CHANGES WILL SAVED INTO CUSTOMISINGWILL SAVED INTO CUSTOMISING REQUEST.REQUEST.
ELEMENT OF THE REQUESTELEMENT OF THE REQUEST EACH REQUEST CONSIST OF TWOEACH REQUEST CONSIST OF TWO SUB REQUESTSUB REQUEST PARENT REQUEST & CHILD REQUEST.PARENT REQUEST & CHILD REQUEST. PARENT REQUEST WILL HELP TOPARENT REQUEST WILL HELP TO TRANSFER THE COMFIGUERATIONTRANSFER THE COMFIGUERATION FROM ONE SERVER TO ANATHER.FROM ONE SERVER TO ANATHER. CHILD REQUEST WILL HELP TOCHILD REQUEST WILL HELP TO CARRY THE DATA.CARRY THE DATA.
BASIS CONSULTANT WILLBASIS CONSULTANT WILL TRANSPORT THE REQUEST FROMTRANSPORT THE REQUEST FROM ONE SERVER TO ANATHER .ONE SERVER TO ANATHER .
CONSULTANT ROLECONSULTANT ROLE INTRANSPORTING THEINTRANSPORTING THE REQUESTREQUEST WE HAVE TO REALIESE ALL THEWE HAVE TO REALIESE ALL THE REQUEST.REQUEST. AND TAKE THE LIST OF ALL THEAND TAKE THE LIST OF ALL THE REQUEST NO. IN EXCEL FILE ANDREQUEST NO. IN EXCEL FILE AND SEND IT TO BASIS CONSULTANT.SEND IT TO BASIS CONSULTANT. BASIS CONSULTANT WILLBASIS CONSULTANT WILL TRANSPORT ALL THE REQUEST FROMTRANSPORT ALL THE REQUEST FROM ONE SERVER TO ANATHER SERVER.ONE SERVER TO ANATHER SERVER.
AFTER COMPLITION OF ALL THEAFTER COMPLITION OF ALL THE COMFIGUIRATION BASISCOMFIGUIRATION BASIS CONSULTANT WILL TRANSPORTCONSULTANT WILL TRANSPORT ALL COMFIGUERATION FROMALL COMFIGUERATION FROM DEVELOPMENT SERVER TODEVELOPMENT SERVER TO QUALITY SERVER.THEN WE DOQUALITY SERVER.THEN WE DO A TESTING IN QUALITY SERVER.A TESTING IN QUALITY SERVER.
TYPE OF TESTING IN QUALITYTYPE 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 WHICHFOR WHICH YOU HAVE TO DEPEND UPON OTHERYOU HAVE TO DEPEND UPON OTHER MODULE CONSULTANT.MODULE CONSULTANT.
TEST CASE DOCUMENTTEST CASE DOCUMENT ON THE BASIS OFON THE BASIS OF TEST CASETEST CASE DOCUMENTWEDOCUMENTWE WILL DO THEWILL DO THE TESTING.TESTING. TEST CASETEST CASE DOCUMENT ISDOCUMENT IS CONSIST OFCONSIST OF SHOWN FIG.SHOWN FIG. WHAT TO TESTWHAT TO TEST HOW TO TESTHOW TO TEST EXPECTED RESULTEXPECTED RESULT ACTUAL RESULTACTUAL RESULT STATUSSTATUS TESTADETESTADE DOCUMENTDOCUMENT
USER MANUAL DOCUMENTUSER MANUAL DOCUMENT AFTER COMPLETION OF TESTING WE WILLAFTER COMPLETION OF TESTING WE WILL PREPARE A USER MANUAL DOCUMENT IS APREPARE A USER MANUAL DOCUMENT IS A GUADELINE TO USER.GUADELINE TO USER. ITS CONSIST OF STEP BY STEP PROCESSITS CONSIST OF STEP BY STEP PROCESS OF CREATING MASTER DATA ANDOF CREATING MASTER DATA AND TRANSACTION DATA ALONG WITH SCREENTRANSACTION DATA ALONG WITH SCREEN SHOTS.SHOTS. EX- MASTER DATA CUSTOMER MASTEREX- MASTER DATA CUSTOMER MASTER MATERIAL MASTER, TRANSACTION DATAMATERIAL MASTER, TRANSACTION DATA ENQUARY, QUASTIONARY ORDER TOENQUARY, QUASTIONARY ORDER TO DELIVEY, INVOLIA.DELIVEY, INVOLIA. AFTER PREPARING A USER MANUAL DOCAFTER PREPARING A USER MANUAL DOC
CONFIGUERATION DOCUMENTCONFIGUERATION DOCUMENT COMFIGUERATION DOC CONSIST THECOMFIGUERATION DOC CONSIST THE SCREEN SHOTS OF ALL THESCREEN SHOTS OF ALL THE COMFIGUERATION MADE FOR THISCOMFIGUERATION MADE FOR THIS PERTICULAR CLIENT.PERTICULAR CLIENT. PURPOSE OF COMFIGUERATION DOCPURPOSE OF COMFIGUERATION DOC IS KNOWLEDGE TRANSFER. (K. T.)IS KNOWLEDGE TRANSFER. (K. T.)
IN REALISATION WE WILLIN REALISATION WE WILL PREPARE A FOUR DOCUMENTPREPARE A FOUR DOCUMENT FUNCTIONAL SPECIFICATION DOCFUNCTIONAL SPECIFICATION DOC TEST CASE DOCTEST CASE DOC USER MSNUAL DOCUSER MSNUAL DOC COMFIGUERATION DOCCOMFIGUERATION DOC AFTER PREPARING A DOCUMENT WEAFTER PREPARING A DOCUMENT WE WILL GO TO FINAL PREPERATIONWILL GO TO FINAL PREPERATION PHASE.PHASE. PERIOD OF REALISATION PHASE ISPERIOD OF REALISATION PHASE IS TWOTWO MONTHS.MONTHS.
FINAL PREPERATION PHASEFINAL PREPERATION PHASE TRAINING TO CORE USER 10 DAYSTRAINING TO CORE USER 10 DAYS WE GIVEN A TRAINING TO CORE USERWE 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 TESTWE WILL ASK THE CORE USER TO TEST THE SCENARIO AND COMFERM IT . CORETHE SCENARIO AND COMFERM IT . CORE USER HAS TO TEST ALL THE SCENAREOUSER HAS TO TEST ALL THE SCENAREO AND IF EVERY THINGS ARE OK THEN USERAND IF EVERY THINGS ARE OK THEN USER WILL GIVE SIGN OFF WE CALL IT ASWILL GIVE SIGN OFF WE CALL IT AS UATUAT SIGN OFF .SIGN OFF . AFTER GETTING A UAT SIGN OFF WE WILLAFTER GETTING A UAT SIGN OFF WE WILL TRANSPORT ALL THE REQUEST FROMTRANSPORT ALL THE REQUEST FROM QUALITY SERVER TO PRODUCTION SERVERQUALITY SERVER TO PRODUCTION SERVER ..
CUT OVER ACTIVITYCUT OVER ACTIVITY AFTER TRANSFERING A ALL REQUESTAFTER TRANSFERING A ALL REQUEST FROM QUALITY SERVER TO PRODUCTIONFROM QUALITY SERVER TO PRODUCTION SERVER WE WILL DO THE CUT OVERSERVER WE WILL DO THE CUT OVER ACTIVITY .ACTIVITY . CUT OVER ACTIVITY IS THE UPLOADING OFCUT OVER ACTIVITY IS THE UPLOADING OF MASTER DATA FROM ONE LEGACY TO SAPMASTER DATA FROM ONE LEGACY TO SAP WHILE UPLOADING THE DATA FROMWHILE UPLOADING THE DATA FROM LEGACY TO SAP .LEGACY TO SAP . DURING THIS ACTIVITY CLIENT HAS TODURING THIS ACTIVITY CLIENT HAS TO STOP THE BUSINESS TO AVOID DATASTOP THE BUSINESS TO AVOID DATA DESCREPENCY.DESCREPENCY.
CUT OVER STRATEGIESCUT OVER STRATEGIES PLANNING ON WENT TO UPLOAD THEPLANNING ON WENT TO UPLOAD THE DATA AND REQUESTING THE CLIENTDATA AND REQUESTING THE CLIENT TO STOP BUSINESS.TO STOP BUSINESS.
CUT OVER PERIODCUT OVER PERIOD ACTUAL NO. OF DAYS TAKEN TOACTUAL NO. OF DAYS TAKEN TO UPLOAD THE DATA FROM LEGACY TOUPLOAD THE DATA FROM LEGACY TO SAP.SAP.
AFTER UPLOADING THE DATAAFTER UPLOADING THE DATA FROM LEGACY TO SAP THENFROM LEGACY TO SAP THEN WE DECLARE GO LIVE . GOWE DECLARE GO LIVE . GO LIVE MEANS HANDOVER SAPLIVE MEANS HANDOVER SAP TO CLIENT I.E. FROM THATTO CLIENT I.E. FROM THAT DAY ONWARD USER WILLDAY ONWARD USER WILL STAND USING SAP.STAND USING SAP. AFTER GO LIVE WE WILL GIVEAFTER GO LIVE WE WILL GIVE 3 MONTH FIRST PRODUCTION3 MONTH FIRST PRODUCTION SUPPORT.SUPPORT.
SUPPORTSUPPORT SUPPORT PARTENER SOLVING THE ISSUESUPPORT PARTENER SOLVING THE ISSUE RAISED BY THE CLIENT WHO ALREADYRAISED BY THE CLIENT WHO ALREADY IMPLEMENTED SAP.IMPLEMENTED SAP. WHEN EVER SUPPORT PARTENER GETS A NEWWHEN EVER SUPPORT PARTENER GETS A NEW PROJECT THE SUPPORT PARTENER AND THEPROJECT THE SUPPORT PARTENER AND THE CLIENT HAS TO ENTER INTO AN AGREEMENTCLIENT HAS TO ENTER INTO AN AGREEMENT CALLED AS SERVICE LEVEL AGREEMENT.CALLED AS SERVICE LEVEL AGREEMENT. IBM ALKEM CLIENTIBM ALKEM CLIENT TCSTCS SLA
AS CONSULTANTAS CONSULTANT CONSULTANT SHOULD HAVE KNOW FROMCONSULTANT SHOULD HAVE KNOW FROM SOME IMFORMATION FROM SLASOME IMFORMATION FROM SLA PRIORITY ISSUE OR KICKETS .PRIORITY ISSUE OR KICKETS . GENERALLY TICKETS ARE CLASSIFIDE INTOGENERALLY TICKETS ARE CLASSIFIDE INTO THREE TYPE.THREE TYPE. HIGH PRIORITY ISSUE WIILSOLVE IN 4 HRSHIGH PRIORITY ISSUE WIILSOLVE IN 4 HRS MEDIAN PRIORITY ISSUE WIIL SOLVED IN 24MEDIAN PRIORITY ISSUE WIIL SOLVED IN 24 HRS.HRS. LOW PRIORITY ISSUE WILL SOLVED INLOW PRIORITY ISSUE WILL SOLVED IN 48HRS48HRS
ANY ISSUE IF ITS STOPINGANY ISSUE IF ITS STOPING THE CLIENT BUSSINESSTHE CLIENT BUSSINESS PROCESS THEN WEPROCESS THEN WE TREATED AS HIGH PRIORITYTREATED AS HIGH PRIORITY ISSUE. IT WILL SOLVED IN 4ISSUE. IT WILL SOLVED IN 4 HRS.HRS.
CHANGE REQUESTCHANGE REQUEST ANY THING THINGSANY THING THINGS CLIENT HAS ASKINGCLIENT HAS ASKING FOR NEW , BUT THEREFOR NEW , BUT THERE IS NO PRESENTIS NO PRESENT COMFIGUERATIONTHECOMFIGUERATIONTHE N WE TREATED ASN WE TREATED AS CHANGE REQUEST.CHANGE REQUEST. WHEN EVER WE GETWHEN EVER WE GET CHANGE REQUESTCHANGE REQUEST NEED CREATENEED CREATE CHANGE REQUESTCHANGE REQUEST DOC .DOC . CLEAR DESCREPTIONCLEAR DESCREPTION OF ISSUEOF ISSUE EXPECTED SOLUTIONEXPECTED SOLUTION APROXIMATEAPROXIMATE EFFORTSEFFORTS FUNCTIONAL MANFUNCTIONAL MAN DAYSDAYS TECHNICAL MANTECHNICAL MAN DAYSDAYS
AFTER PREPARING CHANGES REQUESTAFTER PREPARING CHANGES REQUEST DOC WE WILL SEND THIS DOC TODOC WE WILL SEND THIS DOC TO SUPERIOR FOR REVIEW .SUPERIOR FOR REVIEW . AFTER REVIEW WE WILL SEND THIS DOCAFTER REVIEW WE WILL SEND THIS DOC TO CORE USER FOR APPROVAL FROMTO CORE USER FOR APPROVAL FROM CORE USER THEN WE START WORKING ONCORE USER THEN WE START WORKING ON ISSUE.ISSUE. WHEN EVER SUPPORT PARTNER GETS AWHEN EVER SUPPORT PARTNER GETS A NEW PROJECT THEN SUPPORT PARTENERNEW PROJECT THEN SUPPORT PARTENER WILL CONDUCT KICK OFF MEETING .WILL CONDUCT KICK OFF MEETING . THEY WILL INVITE ALL THE CONSULTANTTHEY WILL INVITE ALL THE CONSULTANT WHO ARE GOING TO INVOLVE IN THEWHO ARE GOING TO INVOLVE IN THE SUPPORT PROJECT.SUPPORT PROJECT. APROXIMATE TEAM SIZE FOR UNKNOWNAPROXIMATE TEAM SIZE FOR UNKNOWN DOMESTIC CLIENT IS 12 MEMBERS OUT OFDOMESTIC 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 OFFSUPPORT PROJECT KICK OFF MEETINGMEETING GIVES THE IMFORMATION ABOUT CLIENTGIVES THE IMFORMATION ABOUT CLIENT BUSSINESS PROCESS .BUSSINESS PROCESS . RULES AND REGULATION OF CLIENT.RULES AND REGULATION OF CLIENT. ROLES AND RESPONCIBILITY OFROLES AND RESPONCIBILITY OF CONSULTANT.CONSULTANT. CORE USER INFORNATION.CORE USER INFORNATION. STARTING DATE.STARTING DATE. AFTER KICK OFF MEETING ALL THEAFTER KICK OFF MEETING ALL THE CONSULTANT WILL MOOV TO CLIENTCONSULTANT WILL MOOV TO CLIENT PLACE FOR KT PROCESS .PLACE FOR KT PROCESS .
K. T. PROCESSK. T. PROCESS CORE SUER WILL HAND OVERCORE SUER WILL HAND OVER COMFIGUERATION DOCUMENT TOCOMFIGUERATION DOCUMENT TO CONSULTANT HAS TO GO THROUGH THECONSULTANT HAS TO GO THROUGH THE DOC & SIMULTANEOUSLYDO THE SYSTEMDOC & SIMULTANEOUSLYDO THE SYSTEM STUDY .STUDY . AFTER SYSTEM STUDY CONSULTANT HASAFTER SYSTEM STUDY CONSULTANT HAS TO PREPARE UNDERSTANDING DOC ANDTO PREPARE UNDERSTANDING DOC AND GIVE REVERS-KT TO CORE USER .GIVE REVERS-KT TO CORE USER . AFTER REVERS KT CONSULTANT WILLAFTER REVERS KT CONSULTANT WILL COME BACK AND START HANDELING THECOME BACK AND START HANDELING THE ISSUE.ISSUE.
TICKET PROCESSTICKET PROCESS
TICKETS PROCESSTICKETS PROCESS WHEN END USER FACE ANY PROBLEMWHEN END USER FACE ANY PROBLEM RAISES AN ISSUE WHICH IS CALLEDRAISES 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 RECEIVEDAT THE HELP DESK CORE USER RECEIVED THE ISSUE .THE ISSUE . THE CORE USER TRIES TO SOLVE FIRST IFTHE CORE USER TRIES TO SOLVE FIRST IF HE NOT ABLE TO SOLVE THE ISSUE THENHE NOT ABLE TO SOLVE THE ISSUE THEN HE RAISE THE ISSUE TOWARDS THE ISSUEHE RAISE THE ISSUE TOWARDS THE ISSUE IN TICKETING TOOLS.IN TICKETING TOOLS. IN TICKETING TOOL CORE USER RAISESIN TICKETING TOOL CORE USER RAISES THE ISSUE WITH PRIORITY AS HIGHTHE ISSUE WITH PRIORITY AS HIGH MEDIUM , LOW.MEDIUM , LOW.
THE SUPPORT CONSULTANTTHE SUPPORT CONSULTANT COORDINATOR RECEIVES THE MAILSCOORDINATOR RECEIVES THE MAILS FROM TICKETING TOOL WITH PRIORITY.FROM TICKETING TOOL WITH PRIORITY. THE CORDINATORS ANALYSE ANDTHE CORDINATORS ANALYSE AND ALLOCATE THE ISSUES TO RESPECTIVEALLOCATE THE ISSUES TO RESPECTIVE CONSULTANT.CONSULTANT. THE CONSULTANT RECEVED THE MAILTHE CONSULTANT RECEVED THE MAIL AND REPLY TO CORE USER END USERAND REPLY TO CORE USER END USER AND COORDINATOR .AND COORDINATOR . THE CONSULTANT HAS TO MAIL ANDTHE CONSULTANT HAS TO MAIL AND REPLY TO CORE USER END USER , CCREPLY TO CORE USER END USER , CC COORDINATOR.COORDINATOR.
THE STATUS OF ISSUE ARE AS FOLLOWS .THE STATUS OF ISSUE ARE AS FOLLOWS . OPENOPEN BEING PROCESSBEING PROCESS WAITAING FOR INFORMTIONWAITAING FOR INFORMTION WAITAING FOR CONFIRMATIONWAITAING FOR CONFIRMATION CLOSEDCLOSED
ONLY THE TIME START OTHER THAN BEINGONLY THE TIME START OTHER THAN BEING PROCESS THEN TIME STOP.PROCESS THEN TIME STOP. AFTER SENDING THE ACCKOLEDGEMENTAFTER SENDING THE ACCKOLEDGEMENT CONSULTANT HAS TO ANALYSE THECONSULTANT HAS TO ANALYSE THE TICKET SIZE.TICKET SIZE. IN SUPPORT WE WILL HAVE PREIN SUPPORT WE WILL HAVE PRE PRODUCTION SERVER .PRODUCTION SERVER . PRE PRODUCTION SERVER IS MIRRORPRE PRODUCTION SERVER IS MIRROR IMAGE OFF PRODUCTION SERVER . WEIMAGE OFF PRODUCTION SERVER . WE ALSO CALLED AS SLAGING SERVER .ALSO CALLED AS SLAGING SERVER . WE TIMES TO DO THE SMALL WHAT ENDWE 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 INIF THE END USER IS GETTING ERROR IN
AFTER GETTING THE ERROR WE GO TOAFTER GETTING THE ERROR WE GO TO DEVELOPMENT ERROR AND DODEVELOPMENT ERROR AND DO NECESSARY COMFIGUERATIONS.NECESSARY COMFIGUERATIONS. THEN WE TRANSPORT FROMTHEN WE TRANSPORT FROM DEVELOPMENT TO QUALITY SERVER ANDDEVELOPMENT TO QUALITY SERVER AND ASK THE CORE USER TO TEST ITASK THE CORE USER TO TEST IT COMFIRM .COMFIRM . AFTER CONFIRMATION WE WILLAFTER CONFIRMATION WE WILL TRANSPORT THE CONFIGUERATION FROMTRANSPORT THE CONFIGUERATION FROM QUALITY SERVER TO PRODUCTIONQUALITY SERVER TO PRODUCTION SERVER.SERVER. AFTER TRANSPORTING COMFIGUERATIONAFTER TRANSPORTING COMFIGUERATION TO PRODUCTION SERVER WE WILL PUTTO PRODUCTION SERVER WE WILL PUT THE STATUS AS CLOSED.THE STATUS AS CLOSED.
LEVEL IN SUPPORTSLEVEL IN SUPPORTS GENERALLY THE LEVEL IN THEGENERALLY THE LEVEL IN THE SUPPORTS WE WILL BE CLASSIFIEDSUPPORTS WE WILL BE CLASSIFIED IN 3 LEVELIN 3 LEVEL LEVEL 1 HIGH PRIORITY ISSUELEVEL 1 HIGH PRIORITY ISSUE LEVEL 2 _ MEDIUM PRIORITY ISSUESLEVEL 2 _ MEDIUM PRIORITY ISSUES LEVEL 3_ CHANGE REQUEST &LEVEL 3_ CHANGE REQUEST & ENHANCEMENTENHANCEMENT

More Related Content

Sap sd implementation by niteen vaidya

  • 1. 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
  • 2. SAP IS AN ERP PACKAGESAP IS AN ERP PACKAGE ITS SPECIFIES THE PLANNING IN ALLITS SPECIFIES THE PLANNING IN ALL DEPARTMENT IN AN ORGANISATIONDEPARTMENT IN AN ORGANISATION ITS SPECIFIES HOW TO UTILISED THEITS SPECIFIES HOW TO UTILISED THE 4MS4MS MENMEN MONEYMONEY MATERIALMATERIAL MACHINERYMACHINERY
  • 3. SAP IS THREE TIERSAP IS THREE TIER ARCHITECTUREARCHITECTURE PRESENTATION LAYERPRESENTATION LAYER APPLICATION LAYERAPPLICATION LAYER DATABASE LAYERDATABASE LAYER
  • 4. PRESENTATION LAYERPRESENTATION LAYER SYSTEM USED BY END USER THIS ISSYSTEM USED BY END USER THIS IS THE PRESENTATION LAYERTHE PRESENTATION LAYER ITS LIVE DAY TO DAY TRANSECTIONITS LIVE DAY TO DAY TRANSECTION DONE ON THISDONE ON THIS
  • 5. APPLICATION LAYERAPPLICATION LAYER ANY REQUEST SEND BYANY REQUEST SEND BY PRESENTATION LAYER FIRST TAKENPRESENTATION LAYER FIRST TAKEN BY APPLICATION LAYER .BY APPLICATION LAYER . TAKE THE DATA AND SEND TO DATATAKE THE DATA AND SEND TO DATA BASE LAYER FURTHER TAKE THEBASE LAYER FURTHER TAKE THE PROCESSED DATA FROM DATA BASEPROCESSED DATA FROM DATA BASE AND SEND IT TO PRESENTATIONAND SEND IT TO PRESENTATION LAYERLAYER ITS ACT AS MEDIATORITS ACT AS MEDIATOR
  • 6. DATABASE LAYERDATABASE LAYER ITS CONSIST OF DATA ONLYITS CONSIST OF DATA ONLY
  • 7. ROLES AND RESPONCIBILITYROLES AND RESPONCIBILITY OF CONSULTANT INOF CONSULTANT IN IMPLIMENTATION OF PROJECTIMPLIMENTATION OF PROJECT COMFIGUIRING THE CLIENTS BUSINESSCOMFIGUIRING THE CLIENTS BUSINESS PROCESS INTO SAP WHO MIGHT USINGPROCESS INTO SAP WHO MIGHT USING SOME LEGACY SYSTEM .SOME LEGACY SYSTEM . LEGACY SYSTEM IS THE THE SYSTEMLEGACY SYSTEM IS THE THE SYSTEM OTHER THAN SAP .OTHER THAN SAP . ANY CLIENT WHO WANT TO IMPLIMENT SAPANY CLIENT WHO WANT TO IMPLIMENT SAP THEN CONSULTANT HAS TO GO WITHTHEN CONSULTANT HAS TO GO WITH SPECIFIC METHODOLOGY CALLED ASAPSPECIFIC METHODOLOGY CALLED ASAP METHODOLOGY.METHODOLOGY.
  • 8. ASAPASAP ACCELERATED SAP IS CALLED ASAPACCELERATED SAP IS CALLED ASAP ITS CONSIST OF THE GUIDELINES TOITS CONSIST OF THE GUIDELINES TO IMPLEMENT THE SAP.IMPLEMENT THE SAP. ITS STEP BY STEP PROCESS OFITS STEP BY STEP PROCESS OF IMLPEMENTING SAP.IMLPEMENTING SAP. ITS CONSIST OF FIVE PHASEITS CONSIST OF FIVE PHASE
  • 9. 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
  • 10. PROJECT PREPERATION PHASEPROJECT PREPERATION PHASE AS CONSULTANT WE DO NOT NEEDAS CONSULTANT WE DO NOT NEED TO INVOLVED IN THE PROJECTTO INVOLVED IN THE PROJECT PREPERATION PHASE.PREPERATION PHASE. ONLY THE MANAGEMENT FROM THEONLY THE MANAGEMENT FROM THE IMPLIMENTATION PARTENER ANDIMPLIMENTATION PARTENER AND CLIENT MANAGEMENT INVOLVE INTOCLIENT MANAGEMENT INVOLVE INTO PROJECT PREPERATION.PROJECT PREPERATION.
  • 11. PHASESES OF PROJECTPHASESES OF PROJECT PREPERATIONPREPERATION USER LICENSESUSER LICENSES LANDSCAPELANDSCAPE INFRASTRUCTUREINFRASTRUCTURE IMPLIMENTATION PARTENERIMPLIMENTATION PARTENER CONSULTANT FACILITYCONSULTANT FACILITY GO LIVE DATEGO LIVE DATE
  • 12. USER LICENSESUSER LICENSES ANY CLIENT IF THEY WANT TOANY CLIENT IF THEY WANT TO IMPLEMENT SAP THEY NEED TOIMPLEMENT SAP THEY NEED TO PURCHASE USER LICENSES FROMPURCHASE USER LICENSES FROM SAP.SAP. BASED ON NO. OF END USERS THEYBASED ON NO. OF END USERS THEY DECIDE HOW MANY USER LICENSESDECIDE HOW MANY USER LICENSES NEED TO PURCHASE FROM SAP.NEED TO PURCHASE FROM SAP. EACH USER LICENSES COST GOINGEACH USER LICENSES COST GOING TO BE APROXIMATELY RS 18000 /-.TO BE APROXIMATELY RS 18000 /-.
  • 13. AN EVERY YEAR CLINT HAS TO PAYAN EVERY YEAR CLINT HAS TO PAY 22% OF LICENSE COST TO SAP IN THE22% OF LICENSE COST TO SAP IN THE FORM AMC.FORM AMC. AMC =ANNUAL MAINTAINENCE COSTAMC =ANNUAL MAINTAINENCE COST
  • 14. LANDSCAPELANDSCAPE ITS ARRANGEMENT OF SERVERS.ITS ARRANGEMENT OF SERVERS. IN LANDSCAPE PHASE WE DECIDE ONIN LANDSCAPE PHASE WE DECIDE ON HOW MANY SERVER TO BEHOW 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 PURCHASEDECIDE ON WHERE FROM PURCHASE THE SERVER, IBM, HP, HCL, DELL.THE SERVER, IBM, HP, HCL, DELL.
  • 15. LANSCAPE THREE SERVERLANSCAPE THREE SERVER ARRANGEMENTARRANGEMENT DEVELOPMENT SERVERDEVELOPMENT SERVER QUALITY SERVERQUALITY SERVER PRODUCTION SERVERPRODUCTION SERVER
  • 16. DEVELOPMENT SERVERDEVELOPMENT SERVER DEVELOPMENT SERVER USED BYDEVELOPMENT SERVER USED BY CONSULTANT.CONSULTANT. IN THIS SERVER CONSULTANT WORKIN THIS SERVER CONSULTANT WORK ON THE COMFIGURATION THEON THE COMFIGURATION THE BUSINESS PROCESS OF CLIENT INTOBUSINESS PROCESS OF CLIENT INTO SAP.SAP.
  • 17. QUALITY SERVERQUALITY SERVER ITS USED BY CONSULTANT AND COREITS USED BY CONSULTANT AND CORE USERS.USERS. ITS USED TO TEST THE SCENARIO.ITS USED TO TEST THE SCENARIO.
  • 18. PRODUCTION SERVERPRODUCTION SERVER ITS WILL BE USED BY END USER ANDITS WILL BE USED BY END USER AND CORE USER.CORE USER. ITS USED TO ENTER DAY TO DAYITS USED TO ENTER DAY TO DAY TRANSECTION INTO SAP.TRANSECTION INTO SAP.
  • 19. INFRASTRUCTUREINFRASTRUCTURE ITS DECIDE REGARDING IMFRASTRUCTURE NEED TOITS DECIDE REGARDING IMFRASTRUCTURE NEED TO IMPLEMATATION.IMPLEMATATION. HOW MANY PCS PURCHASE TO MATE THE NO. OF USERHOW MANY PCS PURCHASE TO MATE THE NO. OF USER LICENSE.LICENSE. SERVER ENVIROMENTSERVER ENVIROMENT WHERE 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 SERVER TEMPERATURE REQUIREMENTTEMPERATURE REQUIREMENT VPN CONNECTIVITYVPN CONNECTIVITY VIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THEVIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THE SERVER FROM REMOTE LOCATION.SERVER FROM REMOTE LOCATION.
  • 20. IMPLIMENTATION PARTENERIMPLIMENTATION PARTENER WILL LIST OUT ALL THE CONSULTANT WHO ARE GOING TOWILL 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 AREAND 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 FORTHE NORMAL TEAM SIZE TO IMPLEMENT YHE SAP FOR UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3 CONSULTANT.CONSULTANT. TEAM SIZE TO IMPLEMENT SAP FOR MNC CLIENT OR WELLTEAM 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 MODULEFOR 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 THENIF 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 CLIENTMAIN ROLE OF CORE USER IS HE WILL SHARE CLIENT
  • 21. CONSULTANT FACILITYCONSULTANT FACILITY THE NORMAL PROJECT TENEURE FORTHE NORMAL PROJECT TENEURE FOR UNKNOWN DOMESTIC CLIENT IS SIXUNKNOWN DOMESTIC CLIENT IS SIX MONTH . THE NORMAL TENEURE FOR MNCMONTH . THE NORMAL TENEURE FOR MNC CLIENT IS 10 MONTH.CLIENT IS 10 MONTH. IF ITS DOMESTIC CLINT ALL CONSULTANTIF ITS DOMESTIC CLINT ALL CONSULTANT WILL GO TO CLIENT TO IMPLEMENT THEWILL GO TO CLIENT TO IMPLEMENT THE SAP , IF ITS A FOREIGN CLIENT THEN EACHSAP , IF ITS A FOREIGN CLIENT THEN EACH MODULE ONE PERSON GO TO CLIENTMODULE ONE PERSON GO TO CLIENT PLACE AND REMAINING PEOPLE FROMPLACE AND REMAINING PEOPLE FROM OFFSHORE WORKING.OFFSHORE WORKING. IN THIS PHASE THEY DECIDE WHO WILLIN THIS PHASE THEY DECIDE WHO WILL TAKE CARE OF FOOD EXPENCES ,TAKE CARE OF FOOD EXPENCES , ACCOMODATION LOCAL TRAVELLINGACCOMODATION LOCAL TRAVELLING EXPENCES , WORK ENVIROMENT,EXPENCES , WORK ENVIROMENT, LAPTOPS.LAPTOPS.
  • 22. GO LIVE DATEGO LIVE DATE ITS A DATE FROM WHICH CLIENTITS A DATE FROM WHICH CLIENT WILL START USING SAP .WILL START USING SAP . GO LIVE DATE MEANS HANDELINGGO LIVE DATE MEANS HANDELING OVER SAP TO CLIENT.OVER SAP TO CLIENT. AFTER COMPLICATION OF PROJECTAFTER COMPLICATION OF PROJECT PREPERATION PHASE THEPREPERATION PHASE THE IMPLEMENTATION PARTERNERIMPLEMENTATION PARTERNER MANAGEMENT WILL COME BACK ANDMANAGEMENT WILL COME BACK AND CONDUCT KICK OFF MEETING .CONDUCT KICK OFF MEETING .
  • 23. KICK OFF MEETINGKICK OFF MEETING ITS MEANS STARTING OF.ITS MEANS STARTING OF. IN THIS THEY WILL INVITE ALL THEIN THIS THEY WILL INVITE ALL THE CONSULTANT WHO GOING TO INVOLVE INCONSULTANT WHO GOING TO INVOLVE IN THE IMPLEMENTATION PROJECT.THE IMPLEMENTATION PROJECT. AFTER KICK OFF MEETING CONSULTANTAFTER KICK OFF MEETING CONSULTANT MOVES TO CLIENT PLACE TO START THEMOVES TO CLIENT PLACE TO START THE IMPLEMENTATION PROJECT.IMPLEMENTATION PROJECT.
  • 24. KICK OFF MEETINGKICK OFF MEETING DISCUSSION TOPICDISCUSSION TOPIC THEY MENTION RULES ANDTHEY MENTION RULES AND REGULATION OF CLIENTS.REGULATION OF CLIENTS. ROLES AND RESPONCIBILITY OFFROLES AND RESPONCIBILITY OFF CONSULTANT.CONSULTANT. INTRODUCTION ABOUT CLIENT.INTRODUCTION ABOUT CLIENT. THEY WILL SHARE THE CORE USERTHEY WILL SHARE THE CORE USER IMFORMATION .IMFORMATION . GO LIVE DATE SHARE.GO LIVE DATE SHARE. STARTING DATE.STARTING DATE.
  • 25. BUSINESS BLUE PRINTBUSINESS BLUE PRINT AS CONSULTANT WE WILL INVOLVE FROMAS CONSULTANT WE WILL INVOLVE FROM BUSINESS BLUE PRINT PHASE.BUSINESS BLUE PRINT PHASE. IN THIS PHASE WE WILL GATHERD THEIN THIS PHASE WE WILL GATHERD THE INFORMATION OF CLIENT BUSINESSINFORMATION OF CLIENT BUSINESS PROCESS.PROCESS. ON THE BASIS OF THE DATA WE WILLON THE BASIS OF THE DATA WE WILL PLANE TO CONVERT LEGACY SYSTEM TOPLANE TO CONVERT LEGACY SYSTEM TO SAP.SAP. THERE ARE VARIOUS STEPES FOR BBPTHERE ARE VARIOUS STEPES FOR BBP PHASE.PHASE.
  • 26. BBP PHASE STEPESBBP PHASE STEPES REQUIREMENT GATHERINGREQUIREMENT GATHERING BBP DOCUMENTBBP DOCUMENT
  • 27. REQUIREMENT GATHERINGREQUIREMENT GATHERING EVERY DAY CONSULTANT WILL GO TOEVERY DAY CONSULTANT WILL GO TO CORE USER PLACE AND ASK THECORE USER PLACE AND ASK THE QUESTION AND WHATEVER CORE USERQUESTION AND WHATEVER CORE USER EXPLAIN WILL BE NOTE DOWN.EXPLAIN WILL BE NOTE DOWN. ON THE BASIS OF QUESTIONARY WE WILLON THE BASIS OF QUESTIONARY WE WILL GATHERED THE REQUIREMENT FROMGATHERED THE REQUIREMENT FROM CORE USER AND QUESTIONARY WILL BECORE USER AND QUESTIONARY WILL BE PROVIDED BY IMPLIMENTATION PARTENER.PROVIDED BY IMPLIMENTATION PARTENER. EVERY DAY AFTER COMPLETION OFEVERY DAY AFTER COMPLETION OF REQUIREMENT GATHERING WE WILL COMEREQUIREMENT GATHERING WE WILL COME BACK AND PREPAIR DOCUMENT CALLED ASBACK AND PREPAIR DOCUMENT CALLED AS ---IS DOC.---IS DOC. THIS ACTIVITY WILL TAKE A APROXIMATELYTHIS ACTIVITY WILL TAKE A APROXIMATELY TWO MONTH.TWO MONTH.
  • 28. BBP DOCUMENTBBP DOCUMENT AFTER REQUIREMENT GATHERINGAFTER REQUIREMENT GATHERING WE WILL PREPAIR BBP DOCUMENTWE WILL PREPAIR BBP DOCUMENT AND WE WILL TAKE BBP DOCUMENTAND WE WILL TAKE BBP DOCUMENT SIGN OFF FROM CORE USER.SIGN OFF FROM CORE USER. AS----IS TO----BE
  • 29. AS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT ANAS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT AN TO---BE CONSIST OF HOW THE PRESENT BUSINESS PROCESS OF THETO---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 ISTHE 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 EFFORTSITS 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 DOCUMENTAFTER 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 ARECORE 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 SIGNAFTER COMFIRMATION MAIL WE WILL TAKE A SIGNATURE ON SIGN OFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECTOFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECT IMPLEMENTATION.IMPLEMENTATION. WE WILL TAKE THE SIGNATURE OF CORE USER , CLIENT PM , OURWE 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 TOSUBMIT ONE COPY TO CLIENT OFFICE AND ANATHER ONE TO IMPLEMENTATION PARTENER.IMPLEMENTATION PARTENER. WITH OUT SIGNOUT WE CANT GO FURTHER.WITH OUT SIGNOUT WE CANT GO FURTHER. THIS PHASE TAKE A TWO MONTH .THIS PHASE TAKE A TWO MONTH . THIS PHASE IS MOST CRITICAL PHASE BECAUSE HOW TO GATHEREDTHIS PHASE IS MOST CRITICAL PHASE BECAUSE HOW TO GATHERED THE ACCURATE INFORMATION TO MAKE SUCCESS OF PROJECTTHE ACCURATE INFORMATION TO MAKE SUCCESS OF PROJECT..
  • 30. REALISATION PHASEREALISATION PHASE IN REALISATION PHASE WE WILL ENTER INTOIN REALISATION PHASE WE WILL ENTER INTO DEVELOPMENT SERVER TO CONFIGURE THEDEVELOPMENT 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. BASELINEBASELINE COMFIGURATIONCOMFIGURATION FINAL COMFIGURATIONFINAL COMFIGURATION BASELINE COMFIGURATION IS THE SPECIFIC FORBASELINE COMFIGURATION IS THE SPECIFIC FOR ONE MODULE FOR WHICH NO NEED TO DEPENDONE MODULE FOR WHICH NO NEED TO DEPEND ON OTHER MODULECONSULTANT.ON OTHER MODULECONSULTANT. FINAL COMFIGURATION HAS TO DEPEND ONFINAL COMFIGURATION HAS TO DEPEND ON OTHER MODULE.OTHER MODULE. FIRST WE COMPLETE THE BASELINEFIRST WE COMPLETE THE BASELINE COMFIGURATION AND THEN GO FOR FINALCOMFIGURATION AND THEN GO FOR FINAL COMFIGURATION.COMFIGURATION.
  • 31. FUNCTIONAL SPECIFICATIONFUNCTIONAL SPECIFICATION DOCUMENTDOCUMENT IN THIS PHASE DURING FINALIN THIS PHASE DURING FINAL COMFIGURATION WE WILL PREPARECOMFIGURATION WE WILL PREPARE FUNCTIONAL SPECIFICATION DOCUMENT.FUNCTIONAL SPECIFICATION DOCUMENT. ANY CLIENT REQUIREMENT FOR WHICH IFANY CLIENT REQUIREMENT FOR WHICH IF YOU REQUIRED THE HELP OF ABAP YOUYOU REQUIRED THE HELP OF ABAP YOU HAVE TO PREPARE F. S. DOC.HAVE TO PREPARE F. S. DOC.
  • 32. REQUEST NUMBERREQUEST NUMBER IN REALISATIONIN REALISATION PHASE WHENPHASE WHEN WE SAVE THEWE SAVE THE COMFIGURATIONCOMFIGURATION IN PERTICULARIN PERTICULAR REQUESTREQUEST NUMBER.NUMBER. REQUESTREQUEST NO.WILL HELPNO.WILL HELP TO TRNSPORTTO TRNSPORT THETHE COMFIGURATIONCOMFIGURATION FROM ONEFROM ONE SERVER TOSERVER TO ANATHERANATHER SERVER.SERVER.
  • 33. TYPE OF REQUESTTYPE OF REQUEST WE HAVE TWO TYPE OF REQUEST.WE HAVE TWO TYPE OF REQUEST. WORKBENCH REQUESTWORKBENCH REQUEST CUSTOMISING REQUESTCUSTOMISING REQUEST
  • 34. WORK BENCH REQUESTWORK BENCH REQUEST WHAT EVER ABAPER WILL DOWHAT EVER ABAPER WILL DO CHANGES THAT WILL SAVED INTOCHANGES THAT WILL SAVED INTO WORK BWNCH REQUEST.WORK BWNCH REQUEST. ALL WORK BENCH REQUEST AREALL WORK BENCH REQUEST ARE CROSSED CLIENT.CROSSED CLIENT. IF WE DO COMFIGUERATION IN ONEIF WE DO COMFIGUERATION IN ONE CLINT THEN ITS AUTOMATICALLYCLINT THEN ITS AUTOMATICALLY UPDATES INTO OTHER CLIENT WITHINUPDATES INTO OTHER CLIENT WITHIN SERVER.SERVER.
  • 36. CUSTOMISING REQUESTCUSTOMISING REQUEST WHAT EVER FUNCTIONALWHAT EVER FUNCTIONAL CONSULTANT WILL DO THE CHANGESCONSULTANT WILL DO THE CHANGES WILL SAVED INTO CUSTOMISINGWILL SAVED INTO CUSTOMISING REQUEST.REQUEST.
  • 37. ELEMENT OF THE REQUESTELEMENT OF THE REQUEST EACH REQUEST CONSIST OF TWOEACH REQUEST CONSIST OF TWO SUB REQUESTSUB REQUEST PARENT REQUEST & CHILD REQUEST.PARENT REQUEST & CHILD REQUEST. PARENT REQUEST WILL HELP TOPARENT REQUEST WILL HELP TO TRANSFER THE COMFIGUERATIONTRANSFER THE COMFIGUERATION FROM ONE SERVER TO ANATHER.FROM ONE SERVER TO ANATHER. CHILD REQUEST WILL HELP TOCHILD REQUEST WILL HELP TO CARRY THE DATA.CARRY THE DATA.
  • 38. BASIS CONSULTANT WILLBASIS CONSULTANT WILL TRANSPORT THE REQUEST FROMTRANSPORT THE REQUEST FROM ONE SERVER TO ANATHER .ONE SERVER TO ANATHER .
  • 39. CONSULTANT ROLECONSULTANT ROLE INTRANSPORTING THEINTRANSPORTING THE REQUESTREQUEST WE HAVE TO REALIESE ALL THEWE HAVE TO REALIESE ALL THE REQUEST.REQUEST. AND TAKE THE LIST OF ALL THEAND TAKE THE LIST OF ALL THE REQUEST NO. IN EXCEL FILE ANDREQUEST NO. IN EXCEL FILE AND SEND IT TO BASIS CONSULTANT.SEND IT TO BASIS CONSULTANT. BASIS CONSULTANT WILLBASIS CONSULTANT WILL TRANSPORT ALL THE REQUEST FROMTRANSPORT ALL THE REQUEST FROM ONE SERVER TO ANATHER SERVER.ONE SERVER TO ANATHER SERVER.
  • 40. AFTER COMPLITION OF ALL THEAFTER COMPLITION OF ALL THE COMFIGUIRATION BASISCOMFIGUIRATION BASIS CONSULTANT WILL TRANSPORTCONSULTANT WILL TRANSPORT ALL COMFIGUERATION FROMALL COMFIGUERATION FROM DEVELOPMENT SERVER TODEVELOPMENT SERVER TO QUALITY SERVER.THEN WE DOQUALITY SERVER.THEN WE DO A TESTING IN QUALITY SERVER.A TESTING IN QUALITY SERVER.
  • 41. TYPE OF TESTING IN QUALITYTYPE 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 WHICHFOR WHICH YOU HAVE TO DEPEND UPON OTHERYOU HAVE TO DEPEND UPON OTHER MODULE CONSULTANT.MODULE CONSULTANT.
  • 42. TEST CASE DOCUMENTTEST CASE DOCUMENT ON THE BASIS OFON THE BASIS OF TEST CASETEST CASE DOCUMENTWEDOCUMENTWE WILL DO THEWILL DO THE TESTING.TESTING. TEST CASETEST CASE DOCUMENT ISDOCUMENT IS CONSIST OFCONSIST OF SHOWN FIG.SHOWN FIG. WHAT TO TESTWHAT TO TEST HOW TO TESTHOW TO TEST EXPECTED RESULTEXPECTED RESULT ACTUAL RESULTACTUAL RESULT STATUSSTATUS TESTADETESTADE DOCUMENTDOCUMENT
  • 43. USER MANUAL DOCUMENTUSER MANUAL DOCUMENT AFTER COMPLETION OF TESTING WE WILLAFTER COMPLETION OF TESTING WE WILL PREPARE A USER MANUAL DOCUMENT IS APREPARE A USER MANUAL DOCUMENT IS A GUADELINE TO USER.GUADELINE TO USER. ITS CONSIST OF STEP BY STEP PROCESSITS CONSIST OF STEP BY STEP PROCESS OF CREATING MASTER DATA ANDOF CREATING MASTER DATA AND TRANSACTION DATA ALONG WITH SCREENTRANSACTION DATA ALONG WITH SCREEN SHOTS.SHOTS. EX- MASTER DATA CUSTOMER MASTEREX- MASTER DATA CUSTOMER MASTER MATERIAL MASTER, TRANSACTION DATAMATERIAL MASTER, TRANSACTION DATA ENQUARY, QUASTIONARY ORDER TOENQUARY, QUASTIONARY ORDER TO DELIVEY, INVOLIA.DELIVEY, INVOLIA. AFTER PREPARING A USER MANUAL DOCAFTER PREPARING A USER MANUAL DOC
  • 44. CONFIGUERATION DOCUMENTCONFIGUERATION DOCUMENT COMFIGUERATION DOC CONSIST THECOMFIGUERATION DOC CONSIST THE SCREEN SHOTS OF ALL THESCREEN SHOTS OF ALL THE COMFIGUERATION MADE FOR THISCOMFIGUERATION MADE FOR THIS PERTICULAR CLIENT.PERTICULAR CLIENT. PURPOSE OF COMFIGUERATION DOCPURPOSE OF COMFIGUERATION DOC IS KNOWLEDGE TRANSFER. (K. T.)IS KNOWLEDGE TRANSFER. (K. T.)
  • 45. IN REALISATION WE WILLIN REALISATION WE WILL PREPARE A FOUR DOCUMENTPREPARE A FOUR DOCUMENT FUNCTIONAL SPECIFICATION DOCFUNCTIONAL SPECIFICATION DOC TEST CASE DOCTEST CASE DOC USER MSNUAL DOCUSER MSNUAL DOC COMFIGUERATION DOCCOMFIGUERATION DOC AFTER PREPARING A DOCUMENT WEAFTER PREPARING A DOCUMENT WE WILL GO TO FINAL PREPERATIONWILL GO TO FINAL PREPERATION PHASE.PHASE. PERIOD OF REALISATION PHASE ISPERIOD OF REALISATION PHASE IS TWOTWO MONTHS.MONTHS.
  • 46. FINAL PREPERATION PHASEFINAL PREPERATION PHASE TRAINING TO CORE USER 10 DAYSTRAINING TO CORE USER 10 DAYS WE GIVEN A TRAINING TO CORE USERWE 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 TESTWE WILL ASK THE CORE USER TO TEST THE SCENARIO AND COMFERM IT . CORETHE SCENARIO AND COMFERM IT . CORE USER HAS TO TEST ALL THE SCENAREOUSER HAS TO TEST ALL THE SCENAREO AND IF EVERY THINGS ARE OK THEN USERAND IF EVERY THINGS ARE OK THEN USER WILL GIVE SIGN OFF WE CALL IT ASWILL GIVE SIGN OFF WE CALL IT AS UATUAT SIGN OFF .SIGN OFF . AFTER GETTING A UAT SIGN OFF WE WILLAFTER GETTING A UAT SIGN OFF WE WILL TRANSPORT ALL THE REQUEST FROMTRANSPORT ALL THE REQUEST FROM QUALITY SERVER TO PRODUCTION SERVERQUALITY SERVER TO PRODUCTION SERVER ..
  • 47. CUT OVER ACTIVITYCUT OVER ACTIVITY AFTER TRANSFERING A ALL REQUESTAFTER TRANSFERING A ALL REQUEST FROM QUALITY SERVER TO PRODUCTIONFROM QUALITY SERVER TO PRODUCTION SERVER WE WILL DO THE CUT OVERSERVER WE WILL DO THE CUT OVER ACTIVITY .ACTIVITY . CUT OVER ACTIVITY IS THE UPLOADING OFCUT OVER ACTIVITY IS THE UPLOADING OF MASTER DATA FROM ONE LEGACY TO SAPMASTER DATA FROM ONE LEGACY TO SAP WHILE UPLOADING THE DATA FROMWHILE UPLOADING THE DATA FROM LEGACY TO SAP .LEGACY TO SAP . DURING THIS ACTIVITY CLIENT HAS TODURING THIS ACTIVITY CLIENT HAS TO STOP THE BUSINESS TO AVOID DATASTOP THE BUSINESS TO AVOID DATA DESCREPENCY.DESCREPENCY.
  • 48. CUT OVER STRATEGIESCUT OVER STRATEGIES PLANNING ON WENT TO UPLOAD THEPLANNING ON WENT TO UPLOAD THE DATA AND REQUESTING THE CLIENTDATA AND REQUESTING THE CLIENT TO STOP BUSINESS.TO STOP BUSINESS.
  • 49. CUT OVER PERIODCUT OVER PERIOD ACTUAL NO. OF DAYS TAKEN TOACTUAL NO. OF DAYS TAKEN TO UPLOAD THE DATA FROM LEGACY TOUPLOAD THE DATA FROM LEGACY TO SAP.SAP.
  • 50. AFTER UPLOADING THE DATAAFTER UPLOADING THE DATA FROM LEGACY TO SAP THENFROM LEGACY TO SAP THEN WE DECLARE GO LIVE . GOWE DECLARE GO LIVE . GO LIVE MEANS HANDOVER SAPLIVE MEANS HANDOVER SAP TO CLIENT I.E. FROM THATTO CLIENT I.E. FROM THAT DAY ONWARD USER WILLDAY ONWARD USER WILL STAND USING SAP.STAND USING SAP. AFTER GO LIVE WE WILL GIVEAFTER GO LIVE WE WILL GIVE 3 MONTH FIRST PRODUCTION3 MONTH FIRST PRODUCTION SUPPORT.SUPPORT.
  • 51. SUPPORTSUPPORT SUPPORT PARTENER SOLVING THE ISSUESUPPORT PARTENER SOLVING THE ISSUE RAISED BY THE CLIENT WHO ALREADYRAISED BY THE CLIENT WHO ALREADY IMPLEMENTED SAP.IMPLEMENTED SAP. WHEN EVER SUPPORT PARTENER GETS A NEWWHEN EVER SUPPORT PARTENER GETS A NEW PROJECT THE SUPPORT PARTENER AND THEPROJECT THE SUPPORT PARTENER AND THE CLIENT HAS TO ENTER INTO AN AGREEMENTCLIENT HAS TO ENTER INTO AN AGREEMENT CALLED AS SERVICE LEVEL AGREEMENT.CALLED AS SERVICE LEVEL AGREEMENT. IBM ALKEM CLIENTIBM ALKEM CLIENT TCSTCS SLA
  • 52. AS CONSULTANTAS CONSULTANT CONSULTANT SHOULD HAVE KNOW FROMCONSULTANT SHOULD HAVE KNOW FROM SOME IMFORMATION FROM SLASOME IMFORMATION FROM SLA PRIORITY ISSUE OR KICKETS .PRIORITY ISSUE OR KICKETS . GENERALLY TICKETS ARE CLASSIFIDE INTOGENERALLY TICKETS ARE CLASSIFIDE INTO THREE TYPE.THREE TYPE. HIGH PRIORITY ISSUE WIILSOLVE IN 4 HRSHIGH PRIORITY ISSUE WIILSOLVE IN 4 HRS MEDIAN PRIORITY ISSUE WIIL SOLVED IN 24MEDIAN PRIORITY ISSUE WIIL SOLVED IN 24 HRS.HRS. LOW PRIORITY ISSUE WILL SOLVED INLOW PRIORITY ISSUE WILL SOLVED IN 48HRS48HRS
  • 53. ANY ISSUE IF ITS STOPINGANY ISSUE IF ITS STOPING THE CLIENT BUSSINESSTHE CLIENT BUSSINESS PROCESS THEN WEPROCESS THEN WE TREATED AS HIGH PRIORITYTREATED AS HIGH PRIORITY ISSUE. IT WILL SOLVED IN 4ISSUE. IT WILL SOLVED IN 4 HRS.HRS.
  • 54. CHANGE REQUESTCHANGE REQUEST ANY THING THINGSANY THING THINGS CLIENT HAS ASKINGCLIENT HAS ASKING FOR NEW , BUT THEREFOR NEW , BUT THERE IS NO PRESENTIS NO PRESENT COMFIGUERATIONTHECOMFIGUERATIONTHE N WE TREATED ASN WE TREATED AS CHANGE REQUEST.CHANGE REQUEST. WHEN EVER WE GETWHEN EVER WE GET CHANGE REQUESTCHANGE REQUEST NEED CREATENEED CREATE CHANGE REQUESTCHANGE REQUEST DOC .DOC . CLEAR DESCREPTIONCLEAR DESCREPTION OF ISSUEOF ISSUE EXPECTED SOLUTIONEXPECTED SOLUTION APROXIMATEAPROXIMATE EFFORTSEFFORTS FUNCTIONAL MANFUNCTIONAL MAN DAYSDAYS TECHNICAL MANTECHNICAL MAN DAYSDAYS
  • 55. AFTER PREPARING CHANGES REQUESTAFTER PREPARING CHANGES REQUEST DOC WE WILL SEND THIS DOC TODOC WE WILL SEND THIS DOC TO SUPERIOR FOR REVIEW .SUPERIOR FOR REVIEW . AFTER REVIEW WE WILL SEND THIS DOCAFTER REVIEW WE WILL SEND THIS DOC TO CORE USER FOR APPROVAL FROMTO CORE USER FOR APPROVAL FROM CORE USER THEN WE START WORKING ONCORE USER THEN WE START WORKING ON ISSUE.ISSUE. WHEN EVER SUPPORT PARTNER GETS AWHEN EVER SUPPORT PARTNER GETS A NEW PROJECT THEN SUPPORT PARTENERNEW PROJECT THEN SUPPORT PARTENER WILL CONDUCT KICK OFF MEETING .WILL CONDUCT KICK OFF MEETING . THEY WILL INVITE ALL THE CONSULTANTTHEY WILL INVITE ALL THE CONSULTANT WHO ARE GOING TO INVOLVE IN THEWHO ARE GOING TO INVOLVE IN THE SUPPORT PROJECT.SUPPORT PROJECT. APROXIMATE TEAM SIZE FOR UNKNOWNAPROXIMATE TEAM SIZE FOR UNKNOWN DOMESTIC CLIENT IS 12 MEMBERS OUT OFDOMESTIC CLIENT IS 12 MEMBERS OUT OF THAT SD HAS 2 & IN MNC 50 & 12 RESP.THAT SD HAS 2 & IN MNC 50 & 12 RESP.
  • 56. SUPPORT PROJECT KICK OFFSUPPORT PROJECT KICK OFF MEETINGMEETING GIVES THE IMFORMATION ABOUT CLIENTGIVES THE IMFORMATION ABOUT CLIENT BUSSINESS PROCESS .BUSSINESS PROCESS . RULES AND REGULATION OF CLIENT.RULES AND REGULATION OF CLIENT. ROLES AND RESPONCIBILITY OFROLES AND RESPONCIBILITY OF CONSULTANT.CONSULTANT. CORE USER INFORNATION.CORE USER INFORNATION. STARTING DATE.STARTING DATE. AFTER KICK OFF MEETING ALL THEAFTER KICK OFF MEETING ALL THE CONSULTANT WILL MOOV TO CLIENTCONSULTANT WILL MOOV TO CLIENT PLACE FOR KT PROCESS .PLACE FOR KT PROCESS .
  • 57. K. T. PROCESSK. T. PROCESS CORE SUER WILL HAND OVERCORE SUER WILL HAND OVER COMFIGUERATION DOCUMENT TOCOMFIGUERATION DOCUMENT TO CONSULTANT HAS TO GO THROUGH THECONSULTANT HAS TO GO THROUGH THE DOC & SIMULTANEOUSLYDO THE SYSTEMDOC & SIMULTANEOUSLYDO THE SYSTEM STUDY .STUDY . AFTER SYSTEM STUDY CONSULTANT HASAFTER SYSTEM STUDY CONSULTANT HAS TO PREPARE UNDERSTANDING DOC ANDTO PREPARE UNDERSTANDING DOC AND GIVE REVERS-KT TO CORE USER .GIVE REVERS-KT TO CORE USER . AFTER REVERS KT CONSULTANT WILLAFTER REVERS KT CONSULTANT WILL COME BACK AND START HANDELING THECOME BACK AND START HANDELING THE ISSUE.ISSUE.
  • 59. TICKETS PROCESSTICKETS PROCESS WHEN END USER FACE ANY PROBLEMWHEN END USER FACE ANY PROBLEM RAISES AN ISSUE WHICH IS CALLEDRAISES 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 RECEIVEDAT THE HELP DESK CORE USER RECEIVED THE ISSUE .THE ISSUE . THE CORE USER TRIES TO SOLVE FIRST IFTHE CORE USER TRIES TO SOLVE FIRST IF HE NOT ABLE TO SOLVE THE ISSUE THENHE NOT ABLE TO SOLVE THE ISSUE THEN HE RAISE THE ISSUE TOWARDS THE ISSUEHE RAISE THE ISSUE TOWARDS THE ISSUE IN TICKETING TOOLS.IN TICKETING TOOLS. IN TICKETING TOOL CORE USER RAISESIN TICKETING TOOL CORE USER RAISES THE ISSUE WITH PRIORITY AS HIGHTHE ISSUE WITH PRIORITY AS HIGH MEDIUM , LOW.MEDIUM , LOW.
  • 60. THE SUPPORT CONSULTANTTHE SUPPORT CONSULTANT COORDINATOR RECEIVES THE MAILSCOORDINATOR RECEIVES THE MAILS FROM TICKETING TOOL WITH PRIORITY.FROM TICKETING TOOL WITH PRIORITY. THE CORDINATORS ANALYSE ANDTHE CORDINATORS ANALYSE AND ALLOCATE THE ISSUES TO RESPECTIVEALLOCATE THE ISSUES TO RESPECTIVE CONSULTANT.CONSULTANT. THE CONSULTANT RECEVED THE MAILTHE CONSULTANT RECEVED THE MAIL AND REPLY TO CORE USER END USERAND REPLY TO CORE USER END USER AND COORDINATOR .AND COORDINATOR . THE CONSULTANT HAS TO MAIL ANDTHE CONSULTANT HAS TO MAIL AND REPLY TO CORE USER END USER , CCREPLY TO CORE USER END USER , CC COORDINATOR.COORDINATOR.
  • 61. THE STATUS OF ISSUE ARE AS FOLLOWS .THE STATUS OF ISSUE ARE AS FOLLOWS . OPENOPEN BEING PROCESSBEING PROCESS WAITAING FOR INFORMTIONWAITAING FOR INFORMTION WAITAING FOR CONFIRMATIONWAITAING FOR CONFIRMATION CLOSEDCLOSED
  • 62. ONLY THE TIME START OTHER THAN BEINGONLY THE TIME START OTHER THAN BEING PROCESS THEN TIME STOP.PROCESS THEN TIME STOP. AFTER SENDING THE ACCKOLEDGEMENTAFTER SENDING THE ACCKOLEDGEMENT CONSULTANT HAS TO ANALYSE THECONSULTANT HAS TO ANALYSE THE TICKET SIZE.TICKET SIZE. IN SUPPORT WE WILL HAVE PREIN SUPPORT WE WILL HAVE PRE PRODUCTION SERVER .PRODUCTION SERVER . PRE PRODUCTION SERVER IS MIRRORPRE PRODUCTION SERVER IS MIRROR IMAGE OFF PRODUCTION SERVER . WEIMAGE OFF PRODUCTION SERVER . WE ALSO CALLED AS SLAGING SERVER .ALSO CALLED AS SLAGING SERVER . WE TIMES TO DO THE SMALL WHAT ENDWE 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 INIF THE END USER IS GETTING ERROR IN
  • 63. AFTER GETTING THE ERROR WE GO TOAFTER GETTING THE ERROR WE GO TO DEVELOPMENT ERROR AND DODEVELOPMENT ERROR AND DO NECESSARY COMFIGUERATIONS.NECESSARY COMFIGUERATIONS. THEN WE TRANSPORT FROMTHEN WE TRANSPORT FROM DEVELOPMENT TO QUALITY SERVER ANDDEVELOPMENT TO QUALITY SERVER AND ASK THE CORE USER TO TEST ITASK THE CORE USER TO TEST IT COMFIRM .COMFIRM . AFTER CONFIRMATION WE WILLAFTER CONFIRMATION WE WILL TRANSPORT THE CONFIGUERATION FROMTRANSPORT THE CONFIGUERATION FROM QUALITY SERVER TO PRODUCTIONQUALITY SERVER TO PRODUCTION SERVER.SERVER. AFTER TRANSPORTING COMFIGUERATIONAFTER TRANSPORTING COMFIGUERATION TO PRODUCTION SERVER WE WILL PUTTO PRODUCTION SERVER WE WILL PUT THE STATUS AS CLOSED.THE STATUS AS CLOSED.
  • 64. LEVEL IN SUPPORTSLEVEL IN SUPPORTS GENERALLY THE LEVEL IN THEGENERALLY THE LEVEL IN THE SUPPORTS WE WILL BE CLASSIFIEDSUPPORTS WE WILL BE CLASSIFIED IN 3 LEVELIN 3 LEVEL LEVEL 1 HIGH PRIORITY ISSUELEVEL 1 HIGH PRIORITY ISSUE LEVEL 2 _ MEDIUM PRIORITY ISSUESLEVEL 2 _ MEDIUM PRIORITY ISSUES LEVEL 3_ CHANGE REQUEST &LEVEL 3_ CHANGE REQUEST & ENHANCEMENTENHANCEMENT