SAP SD

SYSTEM APPLICATION AND PRODUCT

SAP IS AN ERP PACKAGE

SAP IS THREE TIER ARCHITECTURE

 SAP IS AN ERP PACKAGE
ITS SPECIFIES THE PLANNING IN ALL
DEPARTMENT IN AN ORGANISATION
ITS SPECIFIES HOW TO UTILISED THE
4’MS
MEN
MONEY
MATERIAL
MACHINERY
 SAP IS THREE TIER
ARCHITECTURE
PRESENTATION LAYER

APPLICATION LAYER

DATABASE LAYER
 PRESENTATION LAYER
SYSTEM USED BY END USER THIS IS
THE PRESENTATION LAYER
ITS LIVE DAY TO DAY TRANSECTION
DONE ON THIS
 APPLICATION LAYER
ANY REQUEST SEND BY
PRESENTATION LAYER FIRST TAKEN
BY APPLICATION LAYER .
TAKE THE DATA AND SEND TO DATA
BASE LAYER FURTHER TAKE THE
PROCESSED DATA FROM DATA BASE
AND SEND IT TO PRESENTATION
LAYER
ITS ACT AS MEDIATOR
 DATABASE LAYER
ITS CONSIST OF DATA ONLY
 ROLES AND RESPONCIBILITY
OF CONSULTANT IN
IMPLIMENTATION OF PROJECT

COMFIGUIRING THE CLIENTS BUSINESS

PROCESS INTO SAP WHO MIGHT USING
SOME LEGACY SYSTEM .
LEGACY SYSTEM IS THE THE SYSTEM
OTHER THAN SAP .
ANY CLIENT WHO WANT TO IMPLIMENT SAP
THEN CONSULTANT HAS TO GO WITH
SPECIFIC METHODOLOGY CALLED ASAP
METHODOLOGY.
 ASAP
ACCELERATED SAP IS CALLED ASAP
ITS CONSIST OF THE GUIDELINES TO
IMPLEMENT THE SAP.
ITS STEP BY STEP PROCESS OF
IMLPEMENTING SAP.
ITS CONSIST OF FIVE PHASE
 ASAP FIVE PHASES
PROJECT PREPERATION PHASE
BUSINESS BLUE PRINT PHASE
REALISATION
FINAL PREPERATION
GO LIVE AND SUPPORT
PROJECT PREPERATION PHASE
AS CONSULTANT WE DO NOT NEED
TO INVOLVED IN THE PROJECT
PREPERATION PHASE.
ONLY THE MANAGEMENT FROM THE
IMPLIMENTATION PARTENER AND
CLIENT MANAGEMENT INVOLVE INTO
PROJECT PREPERATION.
 PHASESES OF PROJECT
PREPERATION
USER LICENSES
LANDSCAPE
INFRASTRUCTURE
IMPLIMENTATION PARTENER
CONSULTANT FACILITY
GO LIVE DATE
 USER LICENSES
ANY CLIENT IF THEY WANT TO
IMPLEMENT SAP THEY NEED TO
PURCHASE USER LICENSES FROM
SAP.
BASED ON NO. OF END USERS THEY
DECIDE HOW MANY USER LICENSES
NEED TO PURCHASE FROM SAP.
EACH USER LICENSES COST GOING
TO BE APROXIMATELY RS 18000 /-.
AN EVERY YEAR CLINT HAS TO PAY
22% OF LICENSE COST TO SAP IN THE
FORM AMC.
AMC =ANNUAL MAINTAINENCE COST
 LANDSCAPE
ITS ARRANGEMENT OF SERVERS.
IN LANDSCAPE PHASE WE DECIDE ON
HOW MANY SERVER TO BE
PYRCHASE.
WE DECIDE ON SIZING THE SERVER,
SIZING MEANS HARD DISK RAM ,
PROCESSER.
DECIDE ON WHERE FROM PURCHASE
THE SERVER, IBM, HP, HCL, DELL.
 LANSCAPE THREE SERVER
ARRANGEMENT
DEVELOPMENT SERVER
QUALITY SERVER
PRODUCTION SERVER
 DEVELOPMENT SERVER
DEVELOPMENT SERVER USED BY
CONSULTANT.
IN THIS SERVER CONSULTANT WORK
ON THE COMFIGURATION THE
BUSINESS PROCESS OF CLIENT INTO
SAP.
 QUALITY SERVER
ITS USED BY CONSULTANT AND CORE
USERS.
ITS USED TO TEST THE SCENARIO.
 PRODUCTION SERVER
ITS WILL BE USED BY END USER AND
CORE USER.
ITS USED TO ENTER DAY TO DAY
TRANSECTION INTO SAP.
 INFRASTRUCTURE
ITS DECIDE REGARDING IMFRASTRUCTURE NEED TO
IMPLEMATATION.

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

LICENSE.

SERVER ENVIROMENT
WHERE TO KEEP THE SERVER I.E. HO OR AT PLANT LOCATION.
SECURITY OF SERVER
TEMPERATURE REQUIREMENT

VPN CONNECTIVITY
VIRTUAL PRIVATE NETWORK. IT WILL HELP TO CONNECT THE
SERVER FROM REMOTE LOCATION.
IMPLIMENTATION PARTENER
WILL LIST OUT ALL THE CONSULTANT WHO ARE GOING TO
INVOLVE IN THIS PROJECT.

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

THE NORMAL TEAM SIZE TO IMPLEMENT YHE SAP FOR

UNKNOWN DOMESTIC CLIENT IA 15 OUT OF THAT SD HAS 3
CONSULTANT.

TEAM SIZE TO IMPLEMENT SAP FOR MNC CLIENT OR WELL

KNOWN CLIENT IS 60 OUT OF THAT SD HAS 10 CONSULTANT.

FOR IMPLEMENTATION OF PROJECT FOR EACH MODULE

CLIENT WILL PICK UP ONE CORE USER .

IF THEY ARE IMPLEMENTED SD,MM,PP FICO MODULE THEN

CLIENT WILL PICK UP FIVE CORE USER .

MAIN ROLE OF CORE USER IS HE WILL SHARE CLIENT

 CONSULTANT FACILITY
THE NORMAL PROJECT TENEURE FOR
UNKNOWN DOMESTIC CLIENT IS SIX
MONTH . THE NORMAL TENEURE FOR MNC
CLIENT IS 10 MONTH.
IF ITS DOMESTIC CLINT ALL CONSULTANT
WILL GO TO CLIENT TO IMPLEMENT THE
SAP , IF IT’S A FOREIGN CLIENT THEN EACH
MODULE ONE PERSON GO TO CLIENT
PLACE AND REMAINING PEOPLE FROM
OFFSHORE WORKING.
IN THIS PHASE THEY DECIDE WHO WILL
TAKE CARE OF FOOD EXPENCES ,
ACCOMODATION LOCAL TRAVELLING
EXPENCES , WORK ENVIROMENT,
LAPTOPS.
 GO LIVE DATE
IT’S A DATE FROM WHICH CLIENT
WILL START USING SAP .
GO LIVE DATE MEANS HANDELING
OVER SAP TO CLIENT.
AFTER COMPLICATION OF PROJECT
PREPERATION PHASE THE
IMPLEMENTATION PARTERNER
MANAGEMENT WILL COME BACK AND
CONDUCT KICK OFF MEETING .
 KICK OFF MEETING
ITS MEANS STARTING OF.
IN THIS THEY WILL INVITE ALL THE
CONSULTANT WHO GOING TO INVOLVE IN
THE IMPLEMENTATION PROJECT.
AFTER KICK OFF MEETING CONSULTANT
MOVES TO CLIENT PLACE TO START THE
IMPLEMENTATION PROJECT.
 KICK OFF MEETING
DISCUSSION TOPIC
THEY MENTION RULES AND
REGULATION OF CLIENTS.
ROLES AND RESPONCIBILITY OFF
CONSULTANT.
INTRODUCTION ABOUT CLIENT.
THEY WILL SHARE THE CORE USER
IMFORMATION .
GO LIVE DATE SHARE.
STARTING DATE.
 BUSINESS BLUE PRINT
AS CONSULTANT WE WILL INVOLVE FROM
BUSINESS BLUE PRINT PHASE.
IN THIS PHASE WE WILL GATHERD THE
INFORMATION OF CLIENT BUSINESS
PROCESS.
ON THE BASIS OF THE DATA WE WILL
PLANE TO CONVERT LEGACY SYSTEM TO
SAP.
THERE ARE VARIOUS STEPES FOR BBP
PHASE.
 BBP PHASE STEPES
REQUIREMENT GATHERING
BBP DOCUMENT
REQUIREMENT GATHERING
EVERY DAY CONSULTANT WILL GO TO
CORE USER PLACE AND ASK THE
QUESTION AND WHATEVER CORE USER
EXPLAIN WILL BE NOTE DOWN.
ON THE BASIS OF QUESTIONARY WE WILL
GATHERED THE REQUIREMENT FROM
CORE USER AND QUESTIONARY WILL BE
PROVIDED BY IMPLIMENTATION PARTENER.
EVERY DAY AFTER COMPLETION OF
REQUIREMENT GATHERING WE WILL COME
BACK AND PREPAIR DOCUMENT CALLED AS
---IS DOC.
THIS ACTIVITY WILL TAKE A APROXIMATELY
TWO MONTH.
 BBP DOCUMENT
AFTER REQUIREMENT GATHERING
WE WILL PREPAIR BBP DOCUMENT
AND WE WILL TAKE BBP DOCUMENT
SIGN OFF FROM CORE USER.
AS----IS TO----BE
AS---IS MEANS THE PRESENT BUSINESS PROCESS OF THE CLIENT AN
TO---BE CONSIST OF HOW THE PRESENT BUSINESS PROCESS OF THE
CLIENT IS GOING TO SAP.
WHILE PREPARING A TO----BE DOCUMENT WILL FIND SOME GAP .
THE PRESENT BUSINESS PROCESS OF CLIENT FOR WHICH THERE IS
NO SOLUTION FROM SAP IS CALLED GAP.
WHEN EVER WE FIND GAP WE PREPARE GAP ANALYSIS DOCUMENT.
ITS CONSIST OF CLEARE DECSRIPTION OF GAP , ESTIMATED EFFORTS
REGARDING FUNCTIONAL MANDAYS AND TECHNICAL MAN DAYS.
AFTER PREPARING A BBP DOCUMENT WE WILL SEND THE DOCUMENT
TO CORE USER FOR COMFIRMATION.
CORE USER HAS GO THROUGH DOCUMENT AND EVERY THINGS ARE
OK THEN , CORE USER WILL SEND A COMFIRMATION MAIL.
AFTER COMFIRMATION MAIL WE WILL TAKE A SIGNATURE ON SIGN
OFF FORM . SIGN OFF FORM IS THE LEGAL DOCUMENT IN PROJECT
IMPLEMENTATION.
WE WILL TAKE THE SIGNATURE OF CORE USER , CLIENT PM , OUR
PM ,AND CONSULTANT SIGNATURE.
SUBMIT ONE COPY TO CLIENT OFFICE AND ANATHER ONE TO
IMPLEMENTATION PARTENER.
WITH OUT SIGNOUT WE CAN’T GO FURTHER.
THIS PHASE TAKE A TWO MONTH .
THIS PHASE IS MOST CRITICAL PHASE BECAUSE HOW TO GATHERED
THE ACCURATE INFORMATION TO MAKE SUCCESS OF PROJECT.
 REALISATION PHASE
IN REALISATION PHASE WE WILL ENTER INTO
DEVELOPMENT SERVER TO CONFIGURE THE
CLIENT BUSINESS PROCESS INTO SAP.
ITS MEANS MAPING TO---BE PROCESS INTO SAP.
CONFIGURATION DEVIDED INTO TWO TYPE.
BASELINE
COMFIGURATION
FINAL COMFIGURATION
BASELINE COMFIGURATION IS THE SPECIFIC FOR
ONE MODULE FOR WHICH NO NEED TO DEPEND
ON OTHER MODULECONSULTANT.
FINAL COMFIGURATION HAS TO DEPEND ON
OTHER MODULE.
FIRST WE COMPLETE THE BASELINE
COMFIGURATION AND THEN GO FOR FINAL
COMFIGURATION.
 FUNCTIONAL SPECIFICATION
DOCUMENT
IN THIS PHASE DURING FINAL
COMFIGURATION WE WILL PREPARE
FUNCTIONAL SPECIFICATION DOCUMENT.
ANY CLIENT REQUIREMENT FOR WHICH IF
YOU REQUIRED THE HELP OF ABAP YOU
HAVE TO PREPARE F. S. DOC.
 REQUEST NUMBER
IN REALISATION
PHASE WHEN
WE SAVE THE
COMFIGURATION
IN PERTICULAR
REQUEST
NUMBER.
REQUEST
NO.WILL HELP
TO TRNSPORT
THE
COMFIGURATION
FROM ONE
SERVER TO
ANATHER
SERVER.
 TYPE OF REQUEST
WE HAVE TWO TYPE OF REQUEST.

WORKBENCH REQUEST

CUSTOMISING REQUEST
 WORK BENCH REQUEST
WHAT EVER ABAPER WILL DO
CHANGES THAT WILL SAVED INTO
WORK BWNCH REQUEST.
ALL WORK BENCH REQUEST ARE
CROSSED CLIENT.
IF WE DO COMFIGUERATION IN ONE
CLINT THEN ITS AUTOMATICALLY
UPDATES INTO OTHER CLIENT WITHIN
SERVER.
CUSTOMISING REQUEST
WHAT EVER FUNCTIONAL
CONSULTANT WILL DO THE CHANGES
WILL SAVED INTO CUSTOMISING
REQUEST.
ELEMENT OF THE REQUEST
EACH REQUEST CONSIST OF TWO
SUB REQUEST
PARENT REQUEST & CHILD REQUEST.
PARENT REQUEST WILL HELP TO
TRANSFER THE COMFIGUERATION
FROM ONE SERVER TO ANATHER.
CHILD REQUEST WILL HELP TO
CARRY THE DATA.
 BASIS CONSULTANT WILL
TRANSPORT THE REQUEST FROM
ONE SERVER TO ANATHER .
 CONSULTANT ROLE
INTRANSPORTING THE
REQUEST
WE HAVE TO REALIESE ALL THE
REQUEST.
AND TAKE THE LIST OF ALL THE
REQUEST NO. IN EXCEL FILE AND
SEND IT TO BASIS CONSULTANT.
BASIS CONSULTANT WILL
TRANSPORT ALL THE REQUEST FROM
ONE SERVER TO ANATHER SERVER.
AFTER COMPLITION OF ALL THE
COMFIGUIRATION BASIS
CONSULTANT WILL TRANSPORT
ALL COMFIGUERATION FROM
DEVELOPMENT SERVER TO
QUALITY SERVER.THEN WE DO
A TESTING IN QUALITY SERVER.
TYPE OF TESTING IN QUALITY
SERVER
UNIT TESTING , IN WHICH ITESTING IS
SPECIFIC TO ONE MODULE.
INTEGRATION TESTING , FOR WHICH
YOU HAVE TO DEPEND UPON OTHER
MODULE CONSULTANT.
 TEST CASE DOCUMENT
ON THE BASIS OF WHAT TO TEST
TEST CASE
DOCUMENTWE HOW TO TEST
WILL DO THE
EXPECTED RESULT
TESTING.
TEST CASE ACTUAL RESULT
DOCUMENT IS
CONSIST OF STATUS
SHOWN FIG.
TESTADE
DOCUMENT
USER MANUAL DOCUMENT
AFTER COMPLETION OF TESTING WE WILL
PREPARE A USER MANUAL DOCUMENT IS A
GUADELINE TO USER.
ITS CONSIST OF STEP BY STEP PROCESS
OF CREATING MASTER DATA AND
TRANSACTION DATA ALONG WITH SCREEN
SHOTS.
EX- MASTER DATA CUSTOMER MASTER
MATERIAL MASTER, TRANSACTION DATA
ENQUARY, QUASTIONARY ORDER TO
DELIVEY, INVOLIA.
AFTER PREPARING A USER MANUAL DOC
CONFIGUERATION DOCUMENT
COMFIGUERATION DOC CONSIST THE
SCREEN SHOTS OF ALL THE
COMFIGUERATION MADE FOR THIS
PERTICULAR CLIENT.
PURPOSE OF COMFIGUERATION DOC
IS KNOWLEDGE TRANSFER. (K. T.)
 IN REALISATION WE WILL
PREPARE A FOUR DOCUMENT
FUNCTIONAL SPECIFICATION DOC
TEST CASE DOC
USER MSNUAL DOC
COMFIGUERATION DOC

AFTER PREPARING A DOCUMENT WE

WILL GO TO FINAL PREPERATION
PHASE.
PERIOD OF REALISATION PHASE IS TWO
MONTHS.
FINAL PREPERATION PHASE
TRAINING TO CORE USER – 10 DAYS
WE GIVEN A TRAINING TO CORE USER
HOW TO CREAT A MASTER DATA &
HOW TO CREAT ATRASANCTACTION DATA
WE WILL ASK THE CORE USER TO TEST
THE SCENARIO AND COMFERM IT . CORE
USER HAS TO TEST ALL THE SCENAREO
AND IF EVERY THINGS ARE OK THEN USER
WILL GIVE SIGN OFF WE CALL IT AS UAT
SIGN OFF .
AFTER GETTING A UAT SIGN OFF WE WILL
TRANSPORT ALL THE REQUEST FROM
QUALITY SERVER TO PRODUCTION SERVER
.
 CUT OVER ACTIVITY
AFTER TRANSFERING A ALL REQUEST
FROM QUALITY SERVER TO PRODUCTION
SERVER WE WILL DO THE CUT OVER
ACTIVITY .
CUT OVER ACTIVITY IS THE UPLOADING OF
MASTER DATA FROM ONE LEGACY TO SAP
WHILE UPLOADING THE DATA FROM
LEGACY TO SAP .
DURING THIS ACTIVITY CLIENT HAS TO
STOP THE BUSINESS TO AVOID DATA
DESCREPENCY.
 CUT OVER STRATEGIES
PLANNING ON WENT TO UPLOAD THE
DATA AND REQUESTING THE CLIENT
TO STOP BUSINESS.
 CUT OVER PERIOD
ACTUAL NO. OF DAYS TAKEN TO
UPLOAD THE DATA FROM LEGACY TO
SAP.
AFTER UPLOADING THE DATA
FROM LEGACY TO SAP THEN
WE DECLARE GO LIVE . GO
LIVE MEANS HANDOVER SAP
TO CLIENT I.E. FROM THAT
DAY ONWARD USER WILL
STAND USING SAP.
AFTER GO LIVE WE WILL GIVE
3 MONTH FIRST PRODUCTION
SUPPORT.
 SUPPORT
SUPPORT PARTENER SOLVING THE ISSUE
RAISED BY THE CLIENT WHO ALREADY
IMPLEMENTED SAP.
WHEN EVER SUPPORT PARTENER GETS A NEW
PROJECT THE SUPPORT PARTENER AND THE
CLIENT HAS TO ENTER INTO AN AGREEMENT
CALLED AS SERVICE LEVEL AGREEMENT.
IBM ALKEM CLIENT

SLA

TCS
 AS CONSULTANT
CONSULTANT SHOULD HAVE KNOW FROM
SOME IMFORMATION FROM SLA
PRIORITY ISSUE OR KICKETS .
GENERALLY TICKETS ARE CLASSIFIDE INTO
THREE TYPE.
HIGH PRIORITY ISSUE WIILSOLVE IN 4 HRS
MEDIAN PRIORITY ISSUE WIIL SOLVED IN 24
HRS.
LOW PRIORITY ISSUE WILL SOLVED IN
48HRS
ANY ISSUE IF ITS STOPING
THE CLIENT BUSSINESS
PROCESS THEN WE
TREATED AS HIGH PRIORITY
ISSUE. IT WILL SOLVED IN 4
HRS.
 CHANGE REQUEST
ANY THING THINGS CLEAR DESCREPTION
CLIENT HAS ASKING OF ISSUE
FOR NEW , BUT THERE
IS NO PRESENT EXPECTED SOLUTION
COMFIGUERATIONTHE
N WE TREATED AS
CHANGE REQUEST. APROXIMATE
WHEN EVER WE GET EFFORTS
CHANGE REQUEST FUNCTIONAL MAN
NEED CREATE
CHANGE REQUEST DAYS
DOC . TECHNICAL MAN
DAYS
AFTER PREPARING CHANGES REQUEST
DOC WE WILL SEND THIS DOC TO
SUPERIOR FOR REVIEW .
AFTER REVIEW WE WILL SEND THIS DOC
TO CORE USER FOR APPROVAL FROM
CORE USER THEN WE START WORKING ON
ISSUE.
WHEN EVER SUPPORT PARTNER GETS A
NEW PROJECT THEN SUPPORT PARTENER
WILL CONDUCT KICK OFF MEETING .
THEY WILL INVITE ALL THE CONSULTANT
WHO ARE GOING TO INVOLVE IN THE
SUPPORT PROJECT.
APROXIMATE TEAM SIZE FOR UNKNOWN
DOMESTIC CLIENT IS 12 MEMBERS OUT OF
THAT SD HAS 2 & IN MNC 50 & 12 RESP.
 SUPPORT PROJECT KICK OFF
MEETING
GIVES THE IMFORMATION ABOUT CLIENT
BUSSINESS PROCESS .
RULES AND REGULATION OF CLIENT.
ROLES AND RESPONCIBILITY OF
CONSULTANT.
CORE USER INFORNATION.
STARTING DATE.
AFTER KICK OFF MEETING ALL THE
CONSULTANT WILL MOOV TO CLIENT
PLACE FOR KT PROCESS .
 K. T. PROCESS
CORE SUER WILL HAND OVER
COMFIGUERATION DOCUMENT TO
CONSULTANT HAS TO GO THROUGH THE
DOC & SIMULTANEOUSLYDO THE SYSTEM
STUDY .
AFTER SYSTEM STUDY CONSULTANT HAS
TO PREPARE UNDERSTANDING DOC AND
GIVE REVERS-KT TO CORE USER .
AFTER REVERS KT CONSULTANT WILL
COME BACK AND START HANDELING THE
ISSUE.
TICKET PROCESS
 TICKETS PROCESS
WHEN END USER FACE ANY PROBLEM
RAISES AN ISSUE WHICH IS CALLED
TICKETING ISSUE .
END USER THE ISSUE TO HELP DESK .
AT THE HELP DESK CORE USER RECEIVED
THE ISSUE .
THE CORE USER TRIES TO SOLVE FIRST IF
HE NOT ABLE TO SOLVE THE ISSUE THEN
HE RAISE THE ISSUE TOWARDS THE ISSUE
IN TICKETING TOOLS.
IN TICKETING TOOL CORE USER RAISES
THE ISSUE WITH PRIORITY AS HIGH
MEDIUM , LOW.
THE SUPPORT CONSULTANT
COORDINATOR RECEIVES THE MAILS
FROM TICKETING TOOL WITH PRIORITY.
THE CORDINATORS ANALYSE AND
ALLOCATE THE ISSUES TO RESPECTIVE
CONSULTANT.
THE CONSULTANT RECEVED THE MAIL
AND REPLY TO CORE USER END USER
AND COORDINATOR .
THE CONSULTANT HAS TO MAIL AND
REPLY TO CORE USER END USER , CC
COORDINATOR.
THE STATUS OF ISSUE ARE AS FOLLOWS .

OPEN
BEING PROCESS
WAITAING FOR INFORMTION
WAITAING FOR CONFIRMATION
CLOSED
ONLY THE TIME START OTHER THAN BEING
PROCESS THEN TIME STOP.
AFTER SENDING THE ACCKOLEDGEMENT
CONSULTANT HAS TO ANALYSE THE
TICKET SIZE.
IN SUPPORT WE WILL HAVE PRE
PRODUCTION SERVER .
PRE PRODUCTION SERVER IS MIRROR
IMAGE OFF PRODUCTION SERVER . WE
ALSO CALLED AS SLAGING SERVER .
WE TIMES TO DO THE SMALL WHAT END
USER IS DOING IT IN PRODUCTION SERVER.
IF THE END USER IS GETTING ERROR IN
AFTER GETTING THE ERROR WE GO TO
DEVELOPMENT ERROR AND DO
NECESSARY COMFIGUERATIONS.
THEN WE TRANSPORT FROM
DEVELOPMENT TO QUALITY SERVER AND
ASK THE CORE USER TO TEST IT
COMFIRM .
AFTER CONFIRMATION WE WILL
TRANSPORT THE CONFIGUERATION FROM
QUALITY SERVER TO PRODUCTION
SERVER.
AFTER TRANSPORTING COMFIGUERATION
TO PRODUCTION SERVER WE WILL PUT
THE STATUS AS CLOSED.
 LEVEL IN SUPPORTS
GENERALLY THE LEVEL IN THE
SUPPORTS WE WILL BE CLASSIFIED
IN 3 LEVEL
LEVEL 1 – HIGH PRIORITY ISSUE
LEVEL 2 _ MEDIUM PRIORITY ISSUES
LEVEL 3_ CHANGE REQUEST &
ENHANCEMENT