Question { Wipro, 7147 }

Hi,

Could you please explain the ASAP methodology?

Thanks in Advance,
PRS

Answer

ASAP Methodology
Accelerated SAP [ASAP] is SAP’s standard implementation methodology. It contains the roadmap, a step-by-step
guide that incorporates experience from many years of implementing R/3. The road map defines control
points/milestones and also specifies the major deliverables within each milestone. In road map we follo0w the
identities the activities within each phase and assign dates to these milestones. At the end of the each phase we
come up with deliverables/work packages. At the end of the each phase we perform quality check.
5 phases in ASAP Road Map:
• Project preparation
• Blue print
• Realization
• Final preparation
• Go live and support
Phase 1: Project preparation: In this phase of the ASAP roadmap, decision makers define clear project objectives
and an efficient decision making process. We define our project goals and identify scope of project
Scope of the project: Identifying the business process that we want to map into SAP, which modules we
are going to use and what functionality we are going to use for each modules. Then we decide whether we
are going to go live by big bang implementation or phased implementation, which can be described in
EASD [Enterprise Area Scope Development].
• We develop the structure of the project organization and identify the members to be included in the
steering committee for the project.
• Assigning the resources to work on the project.
• Identify the proper hardware to be able to support development work on SAP R/3.
• Preparing the development server.
• Planni9ng for giving training for project people.
• Identifying the business and project measurements.
• Establishing standards [For proper documentation, reporting frequency and hierarchy, communication
between team members].
• Identifying the persons to give authorization to access OSS note, early watch and going live check.
• Having a assistance from independent party to conduct Audit/Quality checks.
• Developing landscape, that is defining client instance strategy.
• Defining our system upgrade strategy.
• Defining procedures to manage transport requests.
• Organizing kick off meetings in which we declare the structure, roles and responsibilities.
• Perform quality checks and sign off.
• Concept check tool can be used in theses project.
Phase 2: Blue print: It’s a document that specifies all requirements of our company within identified scope of the
ASAP project.
• Conceptual design phase of the project in which project team defines current business process or the AS –
IS process first.
• Based on this AS – IS business processes, project team develops SHOULD – BE processes by using
business re – engineering techniques.
• Mainly in this phase where we identify the requirements, perform re – engineering and record what our
SAP system to deliver.
• In this phase we identify the BASELINE scope.
• In order to determine business requirements we integrate with end users. We use SAP tool that is Q & A
database that is generated from the EASD. Q & A database includes issue database where issues relating
project can be logged and get the resolutions from project management. By Q & A database we can
generate reports.
• When answering the Q & A database we also identify the base line scope [80% of requirements].
• The entire realization phase can be divided baseline scope period, one to four unit test cycles and two
integration test cycles.
• We could use two of the four unit test cycles to complete our 20% configurations.
362
• Based on the transactions that we identify in scope, we can specify which transactions are applicable to
which cycle. This input is trigger point for generation of the business process master list [MS Excel file].
• Based on the questions that we entered, team SAP members enter answers in the form of analysis of
requirements, and then we can generate business blue print itself.
• Implementing the initial stages of the system landscape and development environment.
• System administration work starts here. So that development environment is ready with necessary logins.
• Finalize the technical design of hardware archi8techture.
• Establishing transport request management and release strategy.
• Remote connection to SAP, installing SAP GUI’s.
• Deciding the two/three tire architecture and setting up database and application layers accordingly.
• Establishing SAP clients and their purposes.
• Develop and finalize the training strategy.
Phase 3: Realization: Purpose of this phase is to implement all documented requirements in the business blue
print.
• Performing integration testing.
• Getting ready of SAP system to productive operation.
• This phase is subdivided into:
(A) Base line phase [Configuration]
(B) Final configuration and
(C) Integration test
Base line phase [Configuration]: By considering business process transactions identified in the business
process master prints, team SAP members perform configuration. While they doing the system
configuration, developing necessary programs and interfaces, we can send project members to get the
training. In this configuration minor critical processes are implemented in R/3. They demonstrate the
functionality of system to team.
Final configuration: In this step team SAP will go back a little bit and allow the project team to complete
20% project.
• The work that is done at base line configuration can be refined in this phase.
• Unit/Cycle tests are developed processes.
• Problems are fixed if they found any errors, before moving to realization phase.
• The business master list contains the lists of transactions that need to be tested and that serve as a guideline
for unit tests.
• These two phases can be used to develop customer-designed reports and transactions, test interfaces, test
and develop all forms and data conversion programs.
• Developing quality assurance system where all integration tests would be performed.
Integration test: Performing tests on cross module processes or phase processes that involve more than
one module of SAP to complete.
Integration test phase 1 constraints on transactions, which involve a data flow from one module to another
module.
Integration test phase 2 is to execute back-to-back processes as if the entire process was entirely within one
module.
• If any error finds that should be fixed and documented.
• Technical team defines authorizations for end users.
• Functional team creates user specific menus
• Technical team procure/plan for productive environment and archiving strategy also should be defined.
• Identifying the end users and impart training.
363
Phase 4: Final preparation: This phase is to finalize our entire system configuration and environment, including
tests, user training, productive system setup.
• Developing a cut over plan.
• Scheduling the going live check. It is a service provided by SAP in which SAP employed experts logon
into SAP and check for factors that could affect system performance by doing test on the scope of the
project, and they give advices in a report to improve fine tune system configuration.
• Setting up the helpdesk facility [Single level/Two level].
• Finally start the conversion of data from legacy system to R/3 productive system. This requires
downloading the data from legacy to proper format and then uploading the data into R/3. Data can be
uploaded by manually or data conversion programmes.
Phase 5: Go live and support: The purpose of this phase is to go productive with production system, dismantle
existing system.
• End user starts their transactions in R/3.

Question { Wipro, 4348 }

what are functional specifications, give a right examples.

Answer

Function Specs is a document which a functional consultant prepares to be given to Abaper. This Document contains details like Tables & fields name, Table joints, Logic for development, along with test case in sand box / test server to verify the development.