Sap Methodologies These are broadly divided into 5 parts 1. 2. 3. 4. 5.

Project Implementation Business Blue print phase Realization Final Preparation Go Live

1. Project preparation:Implementaion party Implementation company (business partner quip of meeting) technical infrastrucre planning (we need to plan the system landscape) Erp is a component dev quality production legecy (already implemented other s/w but wants to implement to sap) Hardware sizing: It will define the amount of h/w requried to implement our solution Discuss about the s/w Project Tools (scheduling a job(reports etc..,)) Members to be involved in the team Size of the team Role matrix: Tcodes corresponding (how much extent to be given for authorization ) Transport Management system : how the data should be moved, bulk,not modifable s tate, quality. project plan actual s/w project scope functional components (fico, hr) Modules

2. Business Blue print Phase:ABAP: Development (gap analysis) A, B, C, D if sap is not providing the sap so lutions then they will do something. Report designed, layouts Functional counsultants they will define that rules If they give high authorizations to an user what will be damage to the company. document is finalised we do the further process.

3. Realization:s-user id and credentials

option : sizing quick sizer tool we will measure the hardware how to measure the h/w to which system we need to do type of system: prod s/w : o/s and db and its version product availablity pane: this o/s and db says that no issues specify the high availabilty : if that application server goes down how to provi de solution. Online, offline, increment :(backups) offline database backup: we make the database down online database backup: we can take database even users are working. incremental backup:ex: 24 years 2 0r 5 tb data daily then in such case what will be solution 2 mb to 4 mb daily we will take for 2 days clustering disaster recovery servers Cluster: with in one location ex: 1 application server in hyd beside to that 2 application server same location if power off clustering will not be useful disaster recovery servers If one server is in various location and other in other location the recovery will be esay if power off no data will be deleted. network infrastrure: band width, connectivty( router,hub) ( This part having more stress when we discuss on network infrastructure) from realization part the core part has been started Types of users: low users medium users high users

User based sizing: Low user: every user will perform 480 dialog steps with in 40 hrs Ex: google user creation and submit it is called one dialog step for every 5 min Medium user: Can perform 480 steps to 4800 dialog steps wtih in 40 hrs for every 30 sec High user: He can perfomr 4800 steps 14400 dialog steps

for every 10 sec Based on this category we will prpeare the h/w sizing Object based through put sizing: Already implemented project (upgradation) It will give some result to implement we requrie 100 cpu small medium excel double excel simlary to measure sap cpus we measure in saps (like kg, ltrs) Hard disk required for storage purpose how much ram requried to our solution The first system to be installed in the landscape is the solution manager. What is the improtantce of solution mangaer we will upload the doucment of blue print phase Check out the doucments by the users, status of work, lagging (project status) This amount of work done this much of time takes to complete the remaing work.. We will install the dev, qual, they will create the hierachy( top level manageme nt, middle level) Functionsal consultant : give structures of the company hierachy Ex: Board of directors approval to the below level people. (They just defines) Tehnical people: Programed, testing uni testing integration testing whether the functinalty is suitable for the client requirement

4. Final Preparation:They will do the user acceptance testing ( whether it is providing the businee ss request ) validating the users, we need to check the autohorizations, final c ode freezing (no more developments) sap will check to ensure smooth operatins to the system In this production picture comes In this the other concept we discuss in final preparation is: Router: router is a s/w it will establish a connection b/w sap systems and landscape sys tems Router Configuration (very good)

Solution Manger( lagging with solution manager language) 5. Go live:One production server and the business starts putting data means (prod) Help for getting the sizing documentation http://service.sap.com/...../sizing

s0004886426