cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Methodology

Former Member
0 Kudos

Hi guru

I am new to SAP after passing the certification in scm. I wanted to know the SAP methodology and the step by step incident occured in one full life cycle implementation.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hello, friend.

these are the general phases in SAP Methodology.

1. Project Preparation

2. Blueprint

3. Realization

4. Final Preparation

5. Go Live

will supply more details if needed.

regards.

Former Member
0 Kudos

>

> hello, friend.

>

> these are the general phases in SAP Methodology.

>

> 1. Project Preparation

> 2. Blueprint

> 3. Realization

> 4. Final Preparation

> 5. Go Live

>

> will supply more details if needed.

>

> regards.

Hi

Thanks for providing the methods.

Can u give me the details of each phase.

Thanks

ranjeetrajendra_jain
Active Contributor
0 Kudos

Hiya

1. Project Preparation

In this phase fact gathering is done. the existing sytem is checked and the compatibility with SAP is studied. Its here that a quotaion for implemntation id derived depending upon the complexity of the project

2. Blueprint.

In this phase a business blue print is prepared with AS IS and TO BE documentations. These documents form the basic structure and scope of the implementation

3. Realization

In realization phase configuration takes place.

4. Final Preparation.

Here the configuration is uploaded with data and tested for consistencey. Also end user training is taken for all the process in the company.

5. Go Live.

This is the last and the most crutial stage of the project.

From this Date/Phase the Legacy system would be replaced by SAP and production would start.

Keep Sapping

Former Member
0 Kudos

hello again.

actually, you don't have methods within the phases. and there is a great degree of variation among projects, on how the methodology actually proceeds. but here are some general data...

1. Project Preparation

during this phase, your project manager will be doing a lot of conferring with your client's IT chief. they will define the general scope and what functional/technical modules will be included in the project. some of the deliverables in this phase are: project charter, notes from the contract, the project plan and the project schedule.

your project manager will also be sourcing consultants and procuring resources while the client side will be assembling its delegates as members of the project team.

this phase can last anywhere from 2 weeks (best) up. there have been cases where this phase reaches several months to a year!

2. Blueprinting

this is when the consultants map the business requirements and document these. they meet with the client side and identify gaps and formulate plans for enhancements. some training and demos will be done here, maybe some testing in the sandbox to confirm theories. deliverables: blueprint, gap analysis, FRICE, etc.

this should take one to two months.

3. Realization

this is when the consultants do the actual configuration. the team members start to test the configuration in several stages of testing (e.g. unit, integration, stress testing). this is usually the longest stage of the project.

4. Final Preparation

the intensity of training and testing increases. everybody prepares for the Go Live.

master data is uploaded and settings are finalized.

deliverables during the Realization and Final Preparation may include: configuration manual, the BPP and instruction manuals, test scripts, document sign-offs, etc.

5. Go-Live

the client now enters transactions in the systems (although some could have been done during the 4th phase).

the consultants normally provide on-site support during this phase.

hope you found this helpful.

regards and good luck!

Former Member
0 Kudos

Dear Friend,

ASAP: Accelerated Systems Application and Products in Data Processing

All implementation projects have the the following phases:

Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.

As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.

Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.

To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you

will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.

Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.

Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.

Integration testing:

Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.

Go live preparation

Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.

and go through following link

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/501c66ff-c31c-2a10-62ad-9588691d...

Reward points if this is helpful.

Dhananjay

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi sap gurus,

can any body help me out regarding

01) what is fit gap analysis

02) how to add new fields at field catalog( pricing)

Thanks and Regards

ram

Former Member
0 Kudos

Five Phases of ASAP methodlogy.

Phase 1: Project Preparation - The purpose of this phase is to provide initial planning and preparation for your SAP project.

Phase 2: Business Blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run its business within the SAP System. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. The Business Blueprint document represents the business process requirements of the company. It is the agreed statement of how the company intends to run its business within the SAP System.

Phase 3: Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope).

Phase 4: Final Preparation - The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.

Phase 5: Go Live & Support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.

Additionally:

Some additional Infomation on ASAP methodology:

Phase 1 - Project Preparation

Change Charter - Goals and objectives of Organizational Change Management

Project Plan - This is a first cut focusing on milestones and Work Packages; details to come.

Scope - Sets the initial definition of the project; input from sales cycle.

Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities

Cutover Plan - The details of how to move to the production environment and go live

Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

Reward points if helpful.

Regards,

Rajesh Banka

Former Member
0 Kudos

hi,

pl check this link for detailed documentation on ASAP methodology :

[ASAP|http://www.sapfans.com/sapfans/asap/be_02_e.htm]

I hope you can also close the thread, since lot of information is already covered with the above threads along with this.

regards

sadhu kishore

former_member184555
Active Contributor
0 Kudos

Hi

Please go through this link to have a better idea on the activities in ASAP methodology.

http://help.sap.com/printdocu/core/Print46c/en/Data/htm/frame_sv.htm

Thanks,

Ravi