SAP ABAP real-time

scenarios
1.What is a functional specification? examples of
Functional Specification.
What is a Functional Specification?
Functional Specification is the official document for a developer which
describes the features and design of expected functionality, it contains the
technical expectations and required data for the design and development.
This Functional Specification document is the functional document, which
explains in detail how software will be designed.
Functions Of Functional Specifications:

Requirement.

Design Summary.

Desired Functionality.

Finished product.

Test Cases.

Functional Specification format/contents may differ from company to

company, every company follow their own formatting style.
Who prepares Functional Specifications?
As per standard Organizational structure, functional consultants will prepare
functional specifications, in some cases Techno-Functional consultants will
prepare them.(In some companies Senior-Technical Consultants may
prepare ).
What is the next step after Functional Specifications?
Once Functional Specification is prepared, the document will be sent for
approval to functional head or project manager, once approved, it will send to
technical lead. The technical lead will distribute the Functional Specification
to any developer.
How do you receive Functional Specifications?
In general a functional specification will be sent to a consultant through
organizational email like : Outlook, IBM Lotus etc.

2. ASAP methodology SAP

ASAP, accelerated SAP implementation methodology is a proven and
successful methodology in implementation of SAP projects.

Steps and phases involved in ASAP implementation methodology

1.

Project Preparation

2.

Business Blueprint

3.

Realization

4.

Final Preparation

5.

Go Live & Support

Phase1: Project Preparation

This is the first phase on any project under ASAP methodology, this will begin
building up a core project team to go through whole implementation process.
In this phase the team goes through initial planning and preparation for SAP
project implementation, this phase includes:

Defining project goals and objectives.

Clarifying the scope of implementation.

Defining project schedule, budget plan, and implementation sequence.

Establishing the project organization and relevant committees, and

assigning resources.

Phase2: Business blue print

This is the second of a project under ASAP methodology, this is the detailed
formula of the implementation of the project. The main objective of this
phase is to achieve common understanding of how the company intend to
run SAP software.
The project goals and objectives will be set in this phase.
This phase also involves man power, training needs etc.

Phase3: Realization
This is the third phase in ASAP, the purpose of this phase is to implement all
the business process requirements based on blue print.
In this level, the project team should have activities as follow, unit test;
integration test; RICEF(Reports, Interfaces, Conversions, Enhancements and
Forms) developments, data cleaning, preparation, collection, validation and
testing; train the trainer, such as process owner and super users. The project
should develop end user training in accordance with the end user training
strategy.

Phase4: Final Preparation

In the forth phase in ASAP, Final Preparation, it will complete the final
preparation which include testing, end user testing, system management and
cut over activities, to finalize the readiness to go live. In addition, this step
will resolve all critical open issues, on successful completion in the live SAP
system.

Phase5: Go Live & Support

The purpose of this phase is to move from a project-oriented, pre-production
environment(Development environment) to live production operation. The
most important elements include setting up production support, monitoring
system transactions, and optimizing overall system performance.
The project team will integrate new organizational chart and job profile
information performance management system. In addition, the help
desk(support desk) will support end user. The important issue after
implementation is to review system processes and continuous improvement
which means the core team will design high level structure, job hierarchy,
role, responsibilities and performance metrics for post implementation
support personal.

3. ABAP Development end to end process in

Companies
Typically ABAP Developers involved in Realization, Final Preparation and Go
live & Support phases in ASAP methodologies of SAP .

ABAP Consultant role in Realization phase

ABAP consultants plays main role in Realization phase as real development
starts here, in this phase along with ABAP consultants Functional Consultants,
Data Migration consultants and Basis Consultants are involved.

ABAP Development flow in project implementation

Step1 : Functional consultants gather business requirements from business
users.
Step2 : With the gathered requirement, functional consultants do some
functionality analysis and prepare Functional Specification.
Step3 : Functional Consultant send the designed functional specification to
Project Manager (generally in small projects, where project manager acts as
lead) or Team Lead .
Step4 : PM/Teal Lead will assign the requirement to ABAP consultant by
sending the Functional Specification.
Step5 : ABAP consultants designs Technical Specification(Each
company/project has their own template) based on the Functional
Specification .
Step6 : ABAP consultant sends(explains) the Technical Specification to Team
Lead/Review Team to get approval.

Step7 : Once get approval ABAP consultant starts developing ABAP/Web

Dynpro/BSP application.
Step8 : Once development is completed, ABAP consultant will do some Unit
Testing(Testing the application by ABAP consultant) and send it to Functional
Consultants and they will send it to Testing Team.
Step9 : Testers will test the application, if found any issues/bugs send them
to ABAP consultants, ABAP consultant fixes the bugs, this process continues
till no bugs found.
Step10 : Once testing is completed, Functional consultants will send
application to End Users (Actual business users), they will test the
application, if any issues found raise CR(Change Request)/Bugs, ABAP
consultant will fix them.
Step11 : Once End User testing is completed, they will give UAT(User
Acceptance Testing) sign off (means application can be moved to
production ).
Step12 : The entire development moved to production on specific planned
day.
Step13 : ABAP consultant provides production support for the application for
some time (ex: 3 months )
Note: The above is the standard process followed in Companies, the process
may vary from Company to Company