cancel
Showing results for 
Search instead for 
Did you mean: 

hai experts

Former Member
0 Kudos

hello sd gurus

may i get some data from you reg the actual end to end imp of a project in brief, step by step (steps in each phase of asap)

Functional specs - an example

Documentation - how you do in an imp project

thanks

early responders will be definitely rewarded

kishore

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

<u><b>Five Phases of ASAP methodlogy.</b></u>

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

<b>Phase 2: Business Blueprint</b> - 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.

<b>Phase 3: Realization</b> - 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).

<b>Phase 4: Final Preparation</b> - 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.

<b>Phase 5: Go Live & Support</b> - 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:

<b>Phase 1 - Project Preparation</b>

Change Charter - Goals and objectives of Organizational Change&#61550; Management

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

Scope - Sets the initial definition of the&#61550; project; input from sales cycle.

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

<b>Phase 2 - Business Blueprint</b> - 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

<b>Phase 3 - Realization</b> - 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.

<b>Phase 4 - Final Preparation</b> 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

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

<u><b>Functional Specs Format:</b></u>

Document Control

Change History

Issue No

Date

Name

Change

#

Initial Draft

Authorizations

Role

Name

Signed

Date

Business Process Lead (customer)

Functional Analyst (specification author)

Technical Lead

Developer (if known)

Select program type below and then use menu option tools > unprotect to

open other fields for input

Type

Table of Contents

Document Control 1

Overview. 3

1.1 Short Description. 3

1.2 Business Process. 3

1.3 Terminology. 3

1.4 New Custom Objects Required. 3

1.5 Impacted SAP Transactions/Tables. 4

Process Decomposition. 5

2.1 Process Flow. 5

2.2 New Tables/Structures Required. 5

2.3 Sub-Process Description. 5

2.4 Error Handling. 5

2.5 Security Considerations. 5

2.6 Database Considerations. 5

2.7 Conversion Implications. 5

2.8 Batch Processing. 6

2.9 Functional Test Requirements. 6

Overview

1.1 Short Description

1.2 Business Process

1.3 Terminology

1.4 New Custom Objects Required

Include all new tables, key new fields/domains, new lock objects, new

match-codes, new transaction codes, new authorization objects, new

function groups, reports and module pools (transaction programs). Don't

specify all includes, function modules, routines etc. here.

Type (table, transaction etc.)

Description

Naming convention

1.5 Impacted SAP Transactions/Tables

List SAP objects updated/impacted by this specification (do not include

read only impacts)

Object(s)

Type (table, transaction etc.)

Description of Impact

Process Decomposition

2.1 Process Flow

2.2 New Tables/Structures Required

Specify new tables and structures required. If appropriate, you may

defer detailed field list/specification to the technical specification

(e.g. for secondary tables and structures).

Table id

Description

Type

Master, transaction, customizing, staging

Expected size

Maint. dialog

None, SM30, custom

Fields

Key

Domain/data element names

Domain format (if new)

Description

2.3 Sub-Process Description

.

2.4 Error Handling

Specify what to do if a condition passes AND fails (e.g. - what happens

if a customer record is found, or is not found). Specify messages and

type.

Specify any special error logging or table storage, including use of

standard application log where appropriate.

Field

Validation

Message type/no.

Message text

2.5 Security Considerations

2.6 Database Considerations

2.7 Conversion Implications

2.8 Batch Processing

2.9 Functional Test Requirements

Consider all the conditions that need testing for this enhancement and

document below. For each logic branch in theory both (or more)

conditions of the branch should be tested. For each scenario that could

impact program execution, all situations must be tested.

No.

Test condition

Expected result

Data set-up reqt.

Dependencies

- - - - - - - - - - - - - - - - - - - - - -

<b>AS-IS</b> Document describes current process.

<b>TO-BE</b> Document describes proposed process in SAP.

<b>Gap Analysis</b> Document describes the gap between expected process from SAP & TO-BE process (Some gaps may be met through development, based on the scope of the project).

Regards,

Rajesh Banka

Reward points if helpful

Reward Points if helpful

Former Member
0 Kudos

hi kishore,

<a href="http://www.wipro.com/webpages/itservices/eas/sap/implement.htm">info link 1 - wipro</a>

<a href="http://www.hclinfosystems.com/sol_enterp.htm">info link 2 - hcl</a>

<a href="http://www.emeraldinsight.com/Insight/viewContentItem.do?contentType=Article&hdAction=lnkhtml&contentId=1510083&dType=SUB">implementation</a>

<a href="http://www.sap.com/industries/chemicals/midsize/pdf/BWP_SB_Accelerate_Implementation.pdf">ASAP</a>

hope it helps.

Thanks,

Sadhu Kishore

Former Member
0 Kudos