Phase 3

http://www.sap-img.
com/
Phase 3: Realization
The purpose of Phase 3 is to configure the R/3 System, in order to have
an integrated and documented solution which fulfills your business
process requirements.
In this phase, configuration of your system is carried out in two steps:
Baseline and Final Configuration. The Baseline configuration is
designed to configure about 80% of your daily business transactions
and all of your master data, and organizational structure. The
remaining configuration is done in process-oriented cycles. The
Business Blueprint is used as the guide for the system configuration,
done using the Implementation Guide, which will be described in detail
in this chapter. After this, data transfer programs, as well as interfaces,
need to be tested.
Fig. 3-1: Main work packages of Phase 3
Business Process Master List (BPML)
The Business Process Master List (BPML) is initially created in Phase 2
as a report from the Q&Adb. It is used to identify, plan, schedule, and
monitor the configuration and testing of all R/3 business scenarios and
processes within the scope of an implementation. The Business
Process Master List is comprised of Excel worksheets that collectively
facilitate the configuration and testing of R/3.
The Business Process Master List is a representation of the R/3
business processes and transactions that are contained within the
scope of the project. These are refined during the Realization Phase
into the project’s applicable business scenarios and R/3 transactions.
The Master List is the central data repository that feeds all business
process information to all subsequent worksheets. It contains the
baseline scope, the cycle plans (you can define up to four configuration
cycles), integration testing plans, and further templates.
A business process procedure (BPP) is a filled-out template that
provides the initial definition for developing User Procedures and
Case/Test Procedures. The results of the business definition meetings
held with the customer provide an input for the initial business process
procedures.
Fig. : Business Process Master List (BPML)
Business process procedures provide the most detailed level in the
BPML and form the basis for defining the scope of your configuration
cycles. They also represent a filled-out template attached to the
structure you see in the BPML. This template gives you a head start on
end user training and documentation.
http://www.sap-img.com/
Baseline configuration is performed by the application consultant while

the business process team is attending Level 3 training. This will allow
the team to get a firm understanding of processes within R/3 and of
how the IMG is used to carry out actual configuration. The team will be
able to test the Baseline configuration and validate that all the
requirements have been met by developing and performing Baseline
Scenarios.
Baseline Scenarios replicate your key business processes in the R/3
System to check that the Baseline provides the required configuration
and business solution platform for the final business solution. The
number and detail of Baseline Scenarios depends on the confidence
level you want from the confirmation. The goal must be to define
scenarios for your key business flows.
Final configuration will build upon the Baseline. This configuration is
performed by the business process teams. Each configuration core
business process is divided into cycles of related business process
flows. These can be configured in parallel, for which reports, user
procedures, testing scenarios and security profiles need to be
developed. The cycles not only provide milestones for the project
team, but also provide points at which the business processes can be
demonstrated to the user community. This approach provides
immediate feedback as well as involves the entire organization in the
project.
The BPML enables you to manage all the integration testing necessary
to validate the system configuration. Integration testing is planned for
all the scenarios within the implementation. Multiple cases should be
defined and tested to duplicate real business examples across areas.
Fig. XX Baseline configuration and testing
From the BPML, it is possible to call up an R/3 System, provided you
have installed a local GUI. In this way, you can branch to the
transaction you want to implement to see its functionality. Also, there
is an "outline" icon that allows you to expand and suppress the
business process detail, at the enterprise, scenario, case, business
process, or BPP level, in order to best facilitate the work that you’re
doing.
You can also view linked documents, such as the BPP document or the
CI template from the BPML. Furthermore, when you need to add the
same information to multiple cells in a column, you can use the "Fill
Cells of Child Records" icon. This copies the information in the current
cell to all its subordinate cells.
Lastly, the Business Process Master List has a hypertext
documentation linked to it, which guides you through all creation and
maintenance steps.
Uploading the BPML Scope to R/3

Provided you have created a Customizing project in the R/3 System –
without however generating the Project IMG for it – you can upload the
scope of your BPML to R/3. The prerequisite for this is the use of at
least R/3 Release 4.0 and the maintenance of the corresponding R/3
login information in the BMPL User Profile.
You then generate the BPML, and enter the number of the project you
have created in the R/3 System.
Fig. Xx: Generating a Business Process Master List
After the generation run, the system has loaded the scope into the R/3
System. However, in order for the scope to be included in the project,
it is now necessary to generate the Project IMG in the R/3 System
itself.
The advantage of this method is that you can access the R/3 IMG from
the BPML, and branch to precisely the activities relevant to a particular
process.
The project managers have to plan the work in this phase early enough
to involve all those affected. For example, as part of the planning of
the integration tests, organizational matters such as the equipment
required, invitations to employees at other sites, and the testing
procedure should not be overlooked.
The project manager also has to ensure that the project standards are
adhered to, discuss the progress of the project with the Steering
Committee, and to ensure that the activities are correctly integrated,
especially user documentation and training.
On the technical side, the interfaces and enhancements are developed,
data is transferred from the legacy systems, and the archiving system
is set up.
At the end of the Realization phase, you will have an application
system tailored to your business needs that has been approved by
each department and by management. How this is done in detail is
explained further on in this chapter.
Customizing R/3 with the Implementation Guide
The Implementation Guide (IMG) is the main tool for setting the
parameters to configure or "customize" R/3 during this phase. R/3 is
configured by the business process teams and/or consultants by
following the steps in the IMG. The Implementation Guide is used for:
θ Initial implementation of the R/3 System
θ System enhancement and modifications
 System maintenance and release upgrades
Fig. xx: Component-oriented or process-oriented configuration

Using the Implementation Guide, you can:
• Manage, process and analyze implementation or enhancement
projects
• Configure R/3 functions in your company quickly, safely, and
cost-effectively.
• Tailor standard functions to meet your company's specific
business needs.
• Document and monitor the implementation phases in an easy-to-
use project management tool.
θ Automatically transfer of configuration data from the quality
assurance system to the productive system, thereby ensuring
consistency
Configuring the Implementation Guide
The IMG contains all configuration tasks necessary to adapt R/3 to your
business needs. Therefore, it is important for the speed of your
implementation project that the IMG only contains implementation
tasks that are really necessary. In order to do this, SAP allows you to
configure the IMG and hereby cut down the number of configuraton
tasks to a reasonable minimum:
1. An Enterprise IMG is created from the R/3 Reference IMG,
which contains the whole range of activities. This defines which
R/3 components are to be implemented in which countries.
2. A Project IMG is created for the individual project by selecting
countries and application components from the Enterprise IMG.
3. Views are created for every Project IMG. Selecting attributes
reduces the number of activities to be processed again. Of
particular interest is the mandatory activity view. It only shows
the activities that must be carried out.
This configuration process, shown in the following graphic, together
with sample navigation paths, considerably reduces the size of the
IMG.
Fig. 27 (2-10) Reducing the implementation scope
All the Customizing activities have attributes that are used to specify
the IMG. Each IMG activity has the following attributes:
• Key and status
• Assignment to R/3 application components
• Assignment to countries
• Assignment to a work package in the ASAP Roadmap
• Assignment to transport type (transport of all change requests,

transport of original activities, transport of copied activities)
• Client dependency
• Language dependency
• Classification as optional or mandatory
• Classification as critical or not
• Selection fields allocated, for example, for indicating a Global
Template
Structure of the Implementation Guide
The structure of the IMG reflects the chronological order in which the
Customizing activities are to be carried out.
Fig. 14 (3-4): From the Reference IMG to the customer-specific

Project IMG
You can execute all activities directly from the IMG. In addition, the
following functions can be called:
 IMG documentation
The documentation function tells you what the activity is needed
for, what effects a change in the configuration will have and what
to do. Since the documentation is displayed in a separate
window, you can view it while you carry out the instruction steps.
θ Activities
This function calls the Customizing activity where you can make
the settings you need, for example, for payment conditions.
 Project management
This function enables you to document the project status,
schedule and resources.
• Project documentation
This function enables you to create project documentation for
each Customizing activity.
Once you have created your IMG, some of the evaluation possibilities
are:
• Display of all planned Customizing activities
• Display of all Customizing activities necessitating completion
• Display of all finished Customizing activities
• User-defined evaluations of Customizing activities
Fig 29 (10): Changing Customizing for a sales order so that
export check is carried out
The R/3 Customizing tables have been bundled into different views in
order to make it easier to understand the business concepts behind
them. Each change to a Customizing object is automatically recorded
in a transport request and can be planned for export to the productive
system. This procedure guarantees that the productive system is
consistent with the quality assurance system and is easy to maintain.
IMG Project Documentation
Project documentation, which mostly concerns decisions made about
IMG activities, is stored in the Project IMG itself. You can also plan and
confirm your schedule and overhead for activities using project
documentation.
Fig. 28 (2-8) The IMG menu with IMG activities and HTML-based
documentation
Comprehensive, standardized project documentation enables you to
log all implementation plans and changes. There are three types of
project documentation:
• Organizational structure and process documentation
This sort of documentation, which is based on the R/3 Reference
Model, describes the business functionality and the integrated
processes in the R/3 System separately from the technical
aspects.
θ Project work documentation
This documentation is written in SAPoffice, in which you can also
store and manage the documents in folders automatically
generated by R/3 to match the Reference Model.
θ Customizing documentation
Notes are entered and stored in the IMG for each Customizing
activity. This ensures that the configuration is easy to
understand even after the project has finished.
Using the Business Navigator, you can move directly from the
processes or functions you want to implement to the corresponding
SAPoffice folder. You can also navigate straight from the application
components, to which the processes and functions are assigned, to the
configuration activities and notes in the IMG.
SAPoffice allows you to edit and store all the documents and
information that you need during your implementation project. It has
interfaces to various PC-based editing tools, for example,
Microsoft® Word, Microsoft® Excel, Microsoft® PowerPoint, and
Lotus® ScreenCam. Also at your disposal is SAPoffice’s entire mail
functionality, which enables you to store your documents in structured
folders and exchange them with other members of the project team
using distribution lists. This way, you can ensure that the entire project
team is kept up-to-date.
The methodical recording of all activities and information during the

implementation builds a solid basis for the user documentation that is
written in the next phase. Together with the Business Process
Procedures, the application system documentation and the conceptual
design drawn up at the beginning of the project form a considerable
part of the user documentation and training materials.
Customizing Functionality
Among the basic functions that you can carry out in using the
Implementation Guide is how to carry out your system installation
(setting up system logs, defining logical systems, communication
servers, etc.) setting up clients, maintaining users, making individual
Customizing settings, and setting up the transport functionality.
The management of Customizing transport requests for transferring
settings from the quality assurance to the productive system has an
important role to play. The R/3 transport system transfers all the
settings and parameters you make in the quality assurance system to
the productive system. These are activated in the quality assurance
system, meaning that a Customizing request is maintained for every
setting made, which can then be transported.
This way of working not only guarantees consistency between the
quality assurance and productive systems, it also makes it much easier
to change processes and carry out release upgrades. You can use
the Transport Organizer for cross-client transports and the Workbench
Organizer for cross-system transports. Project IMGs and the related
documentation can also be transported.
Global settings include such objects as currencies, countries, units of
measurement, and factory calendars. These settings can be configured
centrally, as they function independently of the individual business
processes. These are the first steps the IMG guides you through when
you start configuration.
Data and reports required for strategic and for operational purposes
are also configured in this phase. R/3 offers many typical reports which
you can tailor to your individual business needs. In Phase 3, you have
to check that the reports meet the enterprise’s needs, making any
adjustments that may be required.
The Report Navigator is a comprehensive catalog of approximately
1,500 reports which makes it easier for users to find standard reports.
Most reports listed contain comprehensive documentation.
In Phase 3 you define and create all the reports that you will be using,
and this tool helps with this process. The Report Navigator is located in
the Knowledge Corner of AcceleratedSAP.
Customizing Wizards
Customizing wizards are similar to wizards found in Windows software

that assist the user by using a series of simple dialog boxes. These
easy-to-understand wizards "converse" with the user to collect
information. Upon completion, the wizard automatically updates the
corresponding R/3 Customizing tables with the appropriate settings.
Each wizard focuses on a specific R/3 Customizing topic, which can
then carry out the Customizing of multiple IMG transactions.
Fig. Xx: Customizing wizard for MM account determination
The wizards can be used for initial configuration settings as well as for
subsequent changes. This means that the wizards must first read the
existing R/3 Customizing table settings. This also implies that the
"classic" IMG can still be used interchangeably with the wizards. The
following wizards are available:
• MM Account Determination
• SD Output Determination
• SD Revenue Account Determination
Preconfiguration Tools
For Release 4.5A, so called Business Configuration sets (BC sets for
short) have been developed to save Customizing parameter values
from a business point of view, that is, a part of the Reference Model. In
order to save the parameters of one Customizing activity for a model
element, individual Customizing profiles can be used. These can then
be grouped to form Business Configuration Sets.
Fig. Xx: BC Sets and compare tool (Customizing Cross-System

Viewer)
In a further step of the Business Engineer functionality, it will be
possible to load BC sets assigned to model elements into the system.
This means that they can be taken over automatically in the
corresponding Customizing views. BC sets can have as many
hierarchies as needed, down to the individual profile level. On the
other hand, you can have a BC set with a direct value assignment,
which is transferred to the quality assurance or productive system via
a transport order.
The Customizing Cross-System Viewer is a tool that enables you to see
at a glance what Customizing data has been transported to another
system and compare the two systems with respect to this data.
This is a tool for checking the consistency of client-specific Customizing
changes. In a typical R/3 System infrastructure, changes made in the
development system are transported to the quality assurance system
and then to the production system.
To check the consistency of changes in the quality assurance system

before transporting them to the production system, you transfer them
to an intermediate import client first. You then start the Customizing
Transfer Assistant in the quality assistant client, and log on to the
import client via Remote Function Call. Normally, you use the
Customizing Transfer Assistant together with other cross-system tools
such as the Customizing Cross-System Viewer.
Further Aspects of the Realization Phase
The following aspects of configuration need to be taken into account
during the steps carried out for the Realization Phase:
• Defining authorizations in the R/3 System
• Defining your workflows
• Creating your user documentation
Authorizations (Profile Generator)
As well as the configuration of an enterprise’s organizational structure
and business processes, one important task in Phase 3 is setting up the
authorization profiles for the users.
For this, the employees’ tasks are matched with the authorization
profiles supplied by R/3 in the form of pre-defined activity groups.
These profiles can be adjusted using the Profile Generator. This often
used to be the job of the technical team, who had to quiz the staff as
to the details of their business processes. It is now so easy that the
members of the project team responsible for the business processes
can take care of it themselves.
R/3’s flexible authorization concept has several strengths:
• It protects applications and data from unauthorized access
• It provides users with the necessary authorization for individual
applications
The administrator no longer has to define authorizations directly from
the authorization objects; instead, the tasks that are to be performed
using R/3 are simply selected. The Profile Generator creates the
authorizations automatically and bundles them in a new authorization
profile. The administrator is not required to intervene again until the
end of the process when the organizational units, for example, for
plant or company code have to be specified. However, it is the Profile
Generator that then transfers the organizational information to the
authorization fields.
There are several advantages to defining authorization profiles in this
way:
• The configuration process is considerably simplified.
• Profiles are more precise and easier to understand.

• Communication between the administrator and the users is
simplified by the use of terms the user is familiar with.
You can adapt the transactions of each application to the business
requirements of your company and of different groups of users. Typical
work centers are defined by assigning standard transactions or
customized transactions to a user group. End users are only offered
the transactions that fit their respective work centers, and unnecessary
navigation in the SAP applications is eliminated. In the process, the
appropriate authorization profiles for the employees are defined, fields
are prefilled, hidden/locked and an individual user menu can be
generated.
SAP Business Workflow
In Phase 3, SAP Business Workflow is typically used to define such
business processes as invoice approval, availability checks, trip cost
accounting and purchase requisition approval. It offers further
optimization potential in automatic handling of exceptional situations
and missed deadlines, for example.
With SAP Business Workflow, the user is at the heart of the business
process. An intuitive electronic inbox receives all messages and
documents for each employee. Employees are kept informed about the
tasks that they are involved with and supplied with all the information
they need. A range of filter functions makes it possible to configure the
inbox to meet the needs of your enterprise or of the individual
employees. You can set up folders, manage documents and set
resubmission dates.
The implementation process is accelerated by using preconfigured
workflow templates on a number of different levels. SAP offers a library
of templates that contain ready-to-run application scenarios. They can
be used as they are or adapted to meet your own individual
requirements. The templates harmonize perfectly with the application
components. The graphical workflow editor makes it easy to change
the workflow definitions at any time without any programming effort.
The changes do not have to be made to the applications themselves,
so that the adjustments can be made during productive operation.
Analyses of completed processes and observations of trends can offer
invaluable information about the cost and effectiveness of individual
processes. Those that are too costly or too time-consuming can easily
be pinpointed for reengineering.
ABAP Workbench
The ABAP Workbench is a complete development environment
integrated into the R/3 System that enables you to make modifications
to the standard R/3 applications. It is used by innumerable R/3
customers and by SAP’s own developers. A sophisticated enhancement

concept ensures that all such changes are consistent and easy to
maintain. The ABAP Workbench is also used for defining interfaces and
transferring data.
ALE – Distributed Business Processes
Business processes are subject to continual change and typically
evolve from a sequence of worksteps to a network of processes. The
prime consideration in process design is the enterprise’s business; the
IT infrastructure is of secondary importance. Sometimes, in order to
keep intercompany processes consistent, information systems have to
be separated or distributed. Both the implementation and development
of such scenarios have to be flexible enough to support changes in
requirements.
The Application Link Enabling (ALE) initiative opens up new
perspectives in this context, facilitating the loose coupling of
distributed R/3 and third-party applications alike. Because
communication between applications is based on business object
technology, all settings are easy to access and consistency between
different application systems is guaranteed.
One example of a distributed scenario is centralized accounting and
customer master maintenance combined with local sales operations.
Creating User Documentation
Once you know the number of users and tasks for R/3, you can plan
the structure, contents, and format of the user documentation. Before
you create the documentation, you have to define how you want to
have documentation changes managed.
One accelerator that is available to help your documentation and
training become successful is to use the Business Process Procedures
that are contained in the Business Process Master List. The BPPs,
created for most R/3 business processes and scripts, are like step-by-
step procedures of how to carry out a process. Adapting these scripts
to your implementation by taking screenshots and filling in field
information allows you to easily create documentation for every
business process.
System Management Procedures
In the Realization phase, procedures for system management also
need to be defined, in order to prepare the system for productive
operation. This includes monitoring productive infrastructure needs,
and determining which system administration activities are necessary.
The following steps are carried out in this work package of the
Realization phase:
1. Developing of system test plans
2. Defining the service level commitment

3. Establishing system administration functions
4. Setting up a Quality Assurance environment
5. Defining the design of the productive system
6. Defining system management procedures for the productive system
7. Setting up the productive environment
Quality Checks in the Realization Phase
At the end of Phase 3, the status of deliverables must be checked for
completeness and accuracy. The Project Manager performs this
internal quality check, which should not be confused with the external,
independent Quality Assurance Audits after each phase.
The Quick Sizing Tool, or Quick Sizer helps you in reviewing the sizing
you have determined in the Project Preparation phase.
Some of the things validated are the configuration of the Baseline
scope, the global settings made for the R/3 System, and the
organizational structure. Furthermore, it's necessary to confirm the
creation of archiving management, verify the existence of a finalized
system, and ensure the creation of user documentation and training
materials.
Lastly, the preparation for end user training needs to be gone through
and approved.
hat is ASAP Methodology

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.
Thirumallasetty
ASAP methodoligy means nothing but standard process for
implementation of SAP, It consists of 5 phases.
1. Project preperation - consists of identifying team members and
developing strategy as how to go.
2. Business Blue print - consists of identifying the client current

process, reqeirement and how SAP provides solution.
Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the
business and process requirements based on the
Business Blueprint.
4. Final Preparation - The purpose of this phase is to complete testing,
end-user training,
5. Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from
uploading of legacy data, devoloping customised reports, BDC's, Forms
etc, here functinal consultatns need to give guidence as to get the
requried data for reports and all.. like the table name, fields etc
Kittu Kittu
What is baseline configuration in sap?
Base line and Final config is the third phase in ASAP methadology. The
purpose of this phase is to implement all the business & process
requirements based on business blue print. You customize the system
step by step in 2 work packages: Base Line Configuration & Final
Configuration.
- Base Line Configuration: this phase comprises the priority
requirements of the enterprise, ensuring that they can be implemented
quickly. This phase can be completed without programming or
enhancements to SAP systems.
- Final Configuration: in this phase you confirm that all your
requirements are met in the R/3 system. Final configuration is a
transportation process that expands that base line solution.
The ASAP Roadmap provides the methodology for implementing and

continuously optimizing your SAP System. It divides the
implementation process into five phases and offers detailed Project
Plans to assist you (in Microsoft Project format). The documentation
stored at each level of the Roadmap tree structure contains
recommendations on implementing your SAP System and links to
helpful tools and accelerators.
The implementation of your SAP System covers the following phases:
Project Preparation
In this phase you plan your project and lay the foundations for
successful implementation. It is at this stage that you make the
strategic decisions crucial to your project:
Define your project goals and objectives
Clarify the scope of your implementation
Define your project schedule, budget plan, and implementation
sequence
Establish the project organization and relevant committees and assign
resources
Business Blueprint
In this phase you create a blueprint using the Question & Answer
database (Q&Adb), which documents your enterprise’s requirements
and establishes how your business processes and organizational
structure are to be represented in the SAP System. You also refine the
original project goals and objectives and revise the overall project
schedule in this phase.
Realization
In this phase, you configure the requirements contained in the
Business Blueprint. Baseline configuration (major scope) is followed by
final configuration (remaining scope), which can consist of up to four
cycles. Other key focal areas of this phase are conducting integration
tests and drawing up end user documentation.
Final Preparation
In this phase you complete your preparations, including testing, end
user training, system management, and cutover activities. You also
need to resolve all open issues in this phase. At this stage you need to
ensure that all the prerequisites for your system to go live have been
fulfilled.
Go Live & Support

In this phase you move from a pre-production environment to the live
system. The most important elements include setting up production
support, monitoring system trans
Parent Categories: SAP / Project Management / SAP R/3
SAP Implementation Phases (8,366 views)
Edit / Discuss / History / Invite Peers / Connect (18 connections)

Major Editors: Vinay Kuma…/ All
Introduction
SAP Project Implementation is one of the components of Project
Management and required a great degree of project related Knowledge
such as Project Management, Change Management,Risk Analysis and
Review Programs.
Accelerated SAP (ASAP) is not only a SAP implementation solution but
it also supports a comprehensive project plan. Like Project
Management, ASAP Methodology also integrates several components
and comprises of MS Project templates providing complete work
breakdown structures and resource assignments.
SAP Implementation Phases
Project Preparation Phase – As per Accelerated SAP (ASAP)

methodology it is the First Phase of SAP Implementation. During this
phase, following components are discussed and documented:
• Initial Project Planning
• Project Procedures
• Project Team Members & their Training
• Project Kickoff
• Technical Requirements
• Quality Check
Business Blueprint Phase - In this phase, a detailed study of
business processes and business requirements are undertaken by the
Project Team members. This is the phase where Project Team
Members interact with respective Core Team Members or Process
Owners. The entire requirements gathered during this phase are
documented as Business Blueprint. During this phase, following
components are discussed and documented:
• Project Management
• Organizational Change Management
• Training
• Develop System Environment
• Organizational Structure Definition
• Business Process Analysis
• Business Process Definition
• Quality Check
Realization Phase - In this phase, all the business and process
requirements are implemented as documented in Business Blueprint.
SAP R/3 system is configured step by step in two work packages,
Baseline and Final configuration. How these configurations will be done

and how it will be tested.
• Baseline Configuration and Confirmation
• System Management
• Final Configuration and Confirmation
• Development of external Programs & Interfaces
• Unit Testing & Documentation
• Final Integration Test
• Business Scenarios & Process Documentation
• End User Training & Documentation
• Quality Check
Final Preparation Phase - During this phase, following activities are
discussed, completed and documented, successful completion of these
activities leads to transition of all configurations settings to live R/3
System
• System Management
• Stress & Volume Tests
• Cutover Strategies & Plans
• End User Training
• Quality Check
Go Live and Support Phase – This is phase where all

configurations/customizations are transported to live production
operation and business starts all its activities in the SAP R/3.
During this phase, all the problems/issues related to hardware,
network, operating system, database, training, and application system
are addressed by the project team members and they help the end
users in achieving their day to day task/assignments. This phase is
further divided as:
• Application Production Support and Maintenance
• Project Implementation End
Continuous Improvement Phase – Towards continuous
improvement and to overcome the organizational, business &
technology changes the followings are covered under this phase:
• Post go-Live Support
• Improve System performance
The lifecycle of an ERP implementation begins with the understanding

of the critical goals and objectives of the business enterprises in
running of the businesses and focussing on the process of streamlining

the business processes which are being planned to get integrated
technologically.
To start with, while building the Business Case or the Business
blueprint, the first focus that is needed, before the initiation of the ERP
project is to analyze what the project will be trying to accomplish and
at what cost, using what resource in time, money and man efforts,
besides also working on the ROI (Return on Investment) details and a
communication plan for all strata of the users involved in the
implementation that include the Top management , operational
management, all the staff members at all levels in an organization who
would be the users , stakeholders, sponsors etc.An other very
important initial activity involved in the ERP implementations is the
designing of the information system for a business, which is an
important role of an System Enterprise Architect because unless the
requirements are not defined in advance and well understood, the
result could be fiasco because the goal of the ERP is application of the
technology to what is right for the business and not what are the
technology tools that are involved in designing an ERP.
Another salient aspect to be considered in ERP project lifecycle is the
protoype based training session with the users which ought to involve
the actual business enterprise data in a test environment to simulate
the ERP package software running the business. This implies the
loading of actual operational data such as bills-of-materials, routings,
business partners, customers, suppliers, etc. into a test environment
for simulation with the ERP software. This approach provides the
business user with an exact look and feel of the information as well as
the user interfaces that is used in the business operations and system
design respectively, and also faciltates to trace the gaps in the
business processes. The testing of business processes along with the
ERP implementation can plug lot of gaps simultaneously in the
development phase.
Normally, a popular approach before ERP implementation is to have a
trial run of the existing business processes or pre defined business
processes through the new system in a simulated environment using
the actual data of the business enterprise. This process is often
referred to as the Conference Room Pilot (CRP) and is normally is
designed to be the final verification that the new system is set-up
correctly to function in the live business environment.
The normal lifecycle of an ERP Implementation Project shall
consist of the following milestones:
1. Business Process Study: Regular interactions with the client grow
in order to understand the various business processes and the way
they are presently carried out.
2. Setting the objectives of ERP implementation; setting the

expectation of the client
2. Pre-Implementation Training: A pre-implementation training,
detailing the concepts and features, shall be given to all the end-users
at the client site. This shall improve the lead time in collecting the
inputs for the preparation of specifications. I don't think this activity
will take place in normal ERP implementation life cycle stages.
3. Requirement Analysis: The requirements of the client are
collected, using the SRS (Software Requirements Specification) form,
to further the process study.
4. GAP Analysis: In relation to Information Technology, this analysis
points out the differences or gaps that exist between the standard
capabilities of the desired system & the expectations of the client. The
deliverable is a GAP Report.
5. In order to get maximum benefit out of the ERP processes must be
re-engineered and then mapped with the redesigned processes
5. BMR (Business Mapping Report): This follow-up of the GAP
Analysis should address the identified solution(s) for the gap areas.
5a. Master Data preparation and managment: This is perhaps
most illtreated activitiy which ultimately leads to delays if not
addressed at early stages of the project planning. A team must look
after these before and after the project to ensure accurracy in master
data as this may lead to erroneous results causing panics after Go
Live.
6. Project Plan: This milestone shall set the actual plan for execution
and roll out for the roles and task allocations.
7. Installation of Software: The Vanilla installation of the complete
software should now be carried out to ascertain the infrastructure
preparedness at the client site.
8. Customization of Forms & Reports: The Client's requirement as
to the customization of forms (user interfaces) and reports (existing as
well as new requirements) are addressed here.
9. The system must be tested for complete processes and each type of
transactions so as to check its robustness.
9. Migration of Historical Data: Beyond the opening balance
incorporation, if the client desires to bring the historical data, this step
will be required to plan the conversion and clean up - prepare the data
for the new environment.
10. Design of Routines & Workarounds: Though this is not a
milestone, the additional routine and workaround requirements (as
identified in the GAP & BMR) shall be addressed through this step.
11. Setup & Configuration: The new environment shall be setup

based on the SRS and the software shall be configured (on different
deployment methods) fully.
12. Testing Environment: A testing environment (a simulation of the
live environment) shall be created in the new software to enable the
end-users to acquaint and equip themselves for beginning in the live
environment.
13. End-User Training: The next milestone shall be giving training to
the end-users on the setup, configuration, transaction processing and
report generation. This shall be the post-implementation training
phase.
14. System Walk-Through: This milestone requires entry of sample
transactions by the end-users in the testing environment.
15. Go Live: This is the Sign-Off phase where the project gets
implemented. Checklist: [1]
16. Post Implementation Support: An immediate support
commitment, subsequent to the implementation, and the detailed
modes of support, etc., are given to the client.
[edit]
Links
SMI210 - IMPLEMENTATION METHODOLOGY OVERVIEW
Course Course Schedule &

Description Locations
Course Version: 084
Duration: 1 day
Delivery Type
• Instructor-led Classroom
Audience
• Managers, Project Managers, Project Team Leaders and Project
Team Members responsible for managing, documenting and
implementing SAP solutions
Prerequisites:
Essential
• SAP01 SAP Overview

• Basic knowledge of SAP systems and Windows operating
environment
Recommended
• SAP Implementation Experience
Goals
• Introduce the ASAP Methodology and the ASAP
Implementation Roadmap.
• Understand how to use this standard implementation
methodology with SAP Solutions
• Introduce the SAP Solution Manager and the use of the
Implementation Roadmap in Projects.
Course Based on Software Release
• SAP Solution Manager 7.0
Content
• Introduce and explain how the ASAP Implementation Roadmap
can aid in the implementation of SAP Solutions.
• Navigate through the ASAP Implementation Roadmap
following the ASAP methodology through each successive
phase of an implementation project :
○ Project Preparation
○ Business Blueprint
○ Realization
○ Final Preparation
○ Go Live & Support
• Provide an understanding of the SAP Solution Manager and it
relationship to the ASAP Roadmap,
• Introduce other Roadmaps including the Run SAP Roadmap.
Reply
Re: Badi
Implementatio
n Step by Step
Needed.
Posted: Aug 19,
2007 8:01 AM
in response
to: SriRam
Hello Sudha
Implementing a BAdi is a piece of cake. The main problem is to find

the right BAdI for your requirement.
Five simple steps are required to implement, e.g. BAdI

ME_PROCESS_PO_CUST:
1. Call transaction SE18 -> enter ME_PROCESS_PO_CUST -> display

2. Choose menu: Implementation -> Create -> enter implementation
name (e.g. ZME_PROCESS_PO_CUST) -> push ENTER/OK button in the
popup
3. Enter description -> switch to tabstrip Interface
4. Accept the name of the implementing class or change it (e.g.
ZCL_ME_PROCESS_PO_CUST)
5. Double-click on the name of the implementing class -> (class
builder opens) implement your coding in the required methods
Finally, call transaction SE19 and activate your BAdI implementation.
Regards
Uwe
Re: Badi Implementation Step Reply

by Step Needed.
Posted: Aug 20, 2007 7:08 AM in
response to: SriRam
Hi Sudha,
Please go though the following links which will help you understand
BADI(1 & 2) and then shows you how to Implement a simple BADI with
screenshots(3):
1. http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf4940e11d2
95df0000e82de14a/frameset.htm
2.
http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf4940e11d295
df0000e82de14a/frameset.htm
3.
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3430
4.
https://weblogs.sdn.sap.com/pub/wlg/3506
Please reward the helpful entries.

Regards,
Raman.
Re: Badi Implementation Step by Reply

Step Needed.
Posted: Aug 29, 2007 7:21 AM in
response to: SriRam
Hi,
Implementing Business Add-Ins (BADI)
The use of object orientated code within SAP has lead to new method
of enhancing standard SAP code called
Business Add-Ins or BADI's for short. Although the implementation
concept is based on classes, methods and
inheritance you do not really have to understand this fully to
implement a BADI. Simply think of methods
as a function module with the same import and export parameters
and follow the simple instructions below.
Steps:
1. Execute Business Add-In(BADI) transaction SE18
2. Enter BADI name i.e. HRPBSGB_HESA_NISR and press the display
button
3. Select menu option Implementation->Create
4. Give implementation a name such as Z_HRPBSGB_HESA_NISR

5. You can now make any changes you require to the BADI within this
implementation, for example choose the Interface tab
6. Double click on the method you want to change, you can now enter
any code you require.
7. Please note to find out what import and export parameters a
method has got return the original BADI definition
(i.e. HRPBSGB_HESA_NISR) and double click on the method name
for example within HRPBSGB_HESA_NISR contract is a method
8. When changes have been made activate the implementation
See below link for more info:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0
456c54-0901-0010-f0b3-cd765fb99702
Step by step proc
http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
Reward points
Regards
BADI http://www.esnips.com/doc/e06e4171-29df-462f-b857-
54fac19a9d8e/ppt-on-badis.ppt http://www.esnips.com/doc/10016c34-
55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-
de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-
5f04d8f87839/badi.doc
www.sapgenie.com/publications/saptips/022006%20-%20Zaidi
%20BADI.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10
000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10
000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b6303
1e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e6/63ee7f486cc143a56
0799d8803ce29/content.htm https://www.sdn.sap.com/irj/sdn/wiki?
path=/display/SRM/BAdI+-+general+information&
http://www.esnips.com/doc/e06e4171-29df-462f-b857-
54fac19a9d8e/ppt-on-badis.ppt http://www.esnips.com/doc/10016c34-
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-
de05e9faac0d/Business-Addin.doc
5f04d8f87839/badi.doc
www.sapgenie.com/publications/saptips/022006%20-%20Zaidi
%20BADI.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10
000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b6303
1e10000000a155106/frameset.htm
https://forums.sdn.sap.com/thread.jspa?
forumID=50&threadID=84658&messageID=916759#916759
http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09
e10000000a155106/frameset.htm
http://support.sas.com/rnd/papers/sugi30/SAP.ppt http://www.sts.tu-
harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://members.aol.com/_ht_a/skarkada/sap/ http://www.ct-
software.com/reportpool_frame.htm
http://www.saphelp.com/SAP_Technical.htm
http://www.kabai.com/abaps/q.htm
http://www.guidancetech.com/people/holland/sap/abap/
http://www.planetsap.com/download_abap_programs.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d189
6f0000e8322d00/content.htm http://www.allsaplinks.com/badi.html
https://www.sdn.sap.com/irj/sdn/weblogs?
blog=/pub/wlg/3430https://www.sdn.sap.com/irj/sdn/weblogs?
blog=/pub/wlg/3480 https://www.sdn.sap.com/irj/sdn/weblogs?
blog=/pub/wlg/3506 https://www.sdn.sap.com/irj/sdn/weblogs?
blog=/pub/wlg/3595 http://www.esnips.com/doc/e06e4171-29df-462f-
b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-
bf720422d265/BADIs.pdf http://www.esnips.com/doc/43a58f51-5d92-
4213-913a-de05e9faac0d/Business-Addin.doc
5f04d8f87839/badi.doc http://www.esnips.com/doc/3b7bbc09-c095-
45a0-9e89-91f2f86ee8e9/BADI-Introduction.ppt
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/409
21dd7-d5cf-2910-1894-bb62316afbd1
http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09
e10000000a155106/frameset.htm
http://support.sas.com/rnd/papers/sugi30/SAP.ppt http://www.sts.tu-
harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://members.aol.com/_ht_a/skarkada/sap/ http://www.ct-
software.com/reportpool_frame.htm
http://www.saphelp.com/SAP_Technical.htm
http://www.kabai.com/abaps/q.htm
http://www.guidancetech.com/people/holland/sap/abap/
http://www.planetsap.com/download_abap_programs.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d189
6f0000e8322d00/content.htm
http://esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-
badis.ppt http://esnips.com/doc/43a58f51-5d92-4213-913a-
de05e9faac0d/Business-Addin.doc http://esnips.com/doc/10016c34-
http://esnips.com/doc/1e10392e-64d8-4181-b2a5-
5f04d8f87839/badi.doc http://esnips.com/doc/365d4c4d-9fcb-4189-
85fd-866b7bf25257/customer-exits--badi.zip
http://esnips.com/doc/3b7bbc09-c095-45a0-9e89-91f2f86ee8e9/BADI-
Introduction.ppt
http://help.sap.com//saphelp_470/helpdata/EN/eb/3e7cee940e11d295d
f0000e82de14a/frameset.htm Rewards if useful......... Min
SAP Tickets - What Is That?

Handling tickets is called Issue Tracking system. The errors or bugs
forwarded by the end user to the support team are prioritized under
three seviority High, Medium and Low. Each and every seviority as got
its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on
line to the customer or the organisation where SAP is already
implemented for which the person should be very strong in the subject
and the process which are implemented in SAP at the client side to
understand,to analyse,to actuate and to give the right solution in right
time.This is the job of the support consultant.
The issues or the tickets(problems) which are arised is taken care of on
priority basis by the support team consultants.
The work process in support projects are given below for your
reference.
1. The customer or the end user logs a call through any tool or by
mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which

work group (by name).
4. Once the calls came to the work group the support consultant or
the team need to send an IR (Initial Response) to the user depending
upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the
team. Then after testing properly by generating TR(Transport Request
through the basis admin)
6. Then it is informed to the end user/customer/super user about the
changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any
configuration or customization is required to solve the issue, then the
consultant have to work on DEV Client, then the end user will test it in
the QA client and after approval the BASIS consultant has to transport
it to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or
the employee in the company face while working on R/3. Tickets
usually occur during the implementation or after theimplementation of
the project. There can be numerous problem which can occur in the
production support and a person who is working in the support has to
resolve those tickets in the limited duration, every ticket has the
particular deadline alert so your responsibility is to finish it before that
deadline.
To begin with , we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant , since shipping
point determination is not happened . ( Without Shipping point the
document becomes INCOMPLETE and he will not be able to proceed
further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and
identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the
change and Request one more Transport to BASIS for QA client. The
End user will test the same by creating a sales order for the new plant
and approve it.
Finally, you request a transport to move the changes to PRODUCTION.
Once the change is deployed in production the TICKET is closed. What
I have given is a small example. You would get some real issues with
severity HIGH in your day-day support.
Tips by: Sourav, Om Prakash, Prabbath, Biswajit Sarangi
e: Badi Implementation Step by Reply

Step Needed.
Posted: Nov 12, 2007 12:49 PM in
response to: SriRam
Hi Sudhakar P , These steps should enable you to find any BADI
related to any transaction in a matter of minutes. Procedure 1: 1) Go
to the transaction SE37 to find your function module. 2) Locate the
function SXV_GET_CLIF_BY_NAME. 3) Put a breakpoint there. 4) Now
open a new session. 5) Go to your transaction. 6) At that time, it will
stop this function. 7) Double click on the function field EXIT_NAME. 8)
That will give you name of the BADI that is provided in your
transaction. Business Add-Ins Procedure 2: 1) Goto se24 (Display class
cl_exithandler) 2) Double click on the method GET_INSTANCE. 3) Put a
break point at Line no.25 (CASE sy-subrc). 4) Now Execute SAP
standard transaction 5) Press the required button for which you need
to write an exit logic, the execution will stop at the break point. 6)
Check the values of variable 'exit_name', it will give you the BADI
name called at that time. 7) This way you will find all the BADIs called
on click of any button in any transaction SAP Business Add-Ins (BAdIs)
are one of the most important technologies used to adapt SAP
software to specific requirements. BAdIs were introduced with Release
4.6 and replace function module exits. This technology is not limited
to SAP applications. BAdI calls can be integrated in customer
applications. These can then be enhanced by other customer
applications. In the various SAP applications, BAdI calls are
implemented at places where enhancements are appropriate.Business
add-ins are enhancements to the standard version of the system.
They can be inserted into the SAP System to accommodate user
requirements too specific to be included in the standard delivery.
Since specific industries often require special functions, SAP allows
you to predefine these points in your software. As with customer exits,
two different views are available: · In the definition view, an

application programmer defines exit points in a source that allow
specific industry sectors, partners, and customers to attach additional
coding to standard SAP source code, without having to modify the
original object. · In the implementation view, the users of Business
Add-Ins can customize the logic they need or use a standard solution,
if one is available. In contrast to customer exits, Business Add-Ins no
longer assume a two-level infrastructure (SAP and customer
solutions), but instead allow for a multi-level system landscape (SAP,
country-specific versions, industry solutions, partner, customer, and
so on). You can create definitions and implementations of Business
Add-Ins at any level of the system landscape.SAP guarantees the
upward compatibility of all Business Add-In interfaces. Release
upgrades do not affect enhancement calls from within the standard
software nor do they affect the validity of call interfaces. You do not
have to register Business Add-Ins in SSCR. The Business Add-In
enhancement technique differentiates between enhancements that
can only be implemented once and enhancements that can be used
actively by any number of customers at the same time. In addition,
Business Add-Ins can be defined according to filter values. This allows
you to differentiate between Add-In implementations using the filter
Country or other criteria. The enhancement technique is set up in
such a way that it is possible to define interfaces for ABAP soure code,
screens, GUI interfaces, and tables. These allow customers to include
their own enhancements in the standard. A single Business Add-In
contains all of the interfaces necessary to implement a specific task.
BADI is just an object-oriented version of user-exit. Instead of entering
program code into some function module (as in customer-exit), you
define some class which has to implement predefined methods and
those methods are fired at predefined points just like an old user-exit.
Some BADI can have multiple independent implementations which is
much better for software deployment as several developers can
implement the same BADI independently. BADI/UserExists are used to
enhance R/3 For customer Needs. Actually there is no transaction to
find when and where the BADI is called. 1. You can see the BADI
description to find why it is called. 2. Once you implemented and
activated the BADI, put some break points in the BADI and see "where
else used" option to check in what all programs this BADI is called. In
the ITS debug, when you are doing the operation what exactly the
BADI description tells, it will take to the break points and you have to
do manually debug the whole thing. I know its bit difficult to do
manual debug the whole thing, it takes lot of time, but you have to be
very patience when you are dealing with BADI's. Transaction SE18 is
the BADI equivalent of transaction SMOD Transaction SE19 is the BADI
equivalent of transaction CMOD . To find the BADI to be implemented
and then implement this via SE19. Check this blogs 2 find a BADI:
https://www.sdn.sap.com/irj/sdn/message?messageID=3343735
https://www.sdn.sap.com/irj/sdn/thread?
messageID=3370270#3370270
https://www.sdn.sap.com/irj/sdn/thread?
messageID=3399488#3399488 How To Define a New BAdI Within the
Enhancement Framework (Some Basics About the BAdI,BAdI
Commands in ABAP, When to Use a BAdI?)
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3430 How to
implement a BAdI And How to Use a Filter
Introducing Business Add-Ins
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f32
02186-0601-0010-6591-b832b1a0d0de How to implement BAdi in
Enhancement Framework
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0
456c54-0901-0010-f0b3-cd765fb99702 Business Add-Ins
http://help.sap.com/saphelp_47x200/helpdata/en/ee/a1d548892b11d2
95d60000e82de14a/frameset.htm BAdI: Customer-Defined Functions
in the Formula Builder
0000000a114084/content.htm Difference Between BADI and User
Exits http://www.sap-img.com/abap/difference-between-badi-and-user-
exits.htm To Use BADI - Business Add In you need to Understand ABAP
OO Interface Concept http://www.sap-img.com/abap/business-add-in-
you-need-to-understand-abap-oo-interface-concept.htm cheers!
gyanaraj ****Pls reward points if u find this helpful
oles and Responsibilities of End Users

What is the Difference between Consultant & End users?
SAP consultant role is to build the system, changes &
modification/updation in currently installed SAP system for the end
users.
SAP End user only use the SAP system just to fetch some info, or to
create new thing. So a end user is just using the final product which it
is meant for and consultnat design the product/updation and
modification.
The roles and responsibilities of end users is working in easy access
menu they will not have authorizations of using img settings if they get
doubt they will send query to the implemented company and just
entering day to day transactions.
Roles and Responsibilities of End User:
Using the software at the end or after the implementation is an End
User.
In sap HR , we do come across entire Org Management creation by an
end user after the Personnel strucutre is created. OM objects like
creation of Org Unit means functional area or dpt , creation Job and
Position and its occupancy is with in the limits of an enduser. Initiallly
the OM is created by sap consultant . In course of time a new
department has appeared in the company of the client .. this has to be
created by the enduser rather than depending up on the
implementor... similarly new job and position..like this small things are
always done by the enduser.
The entire work of OM is purely depends upon the enduser.
After from this running periodical payroll and Ensuring of the Time
schedules ( Work Schedules) of each employee is done from sap easy
access by an enduser and the show run of payroll everymonth is by the
enduser only. Like this lot of roles are there for an end user.
Whatever the problems come across during the enduser utilisation of
sap ...that will reach as ticket to the support team
Tips by: Pascal, Nitin, Sushil Pandey, Somasekhar
Explain what are the job responsibilities of END user & POWER
user.
One would need user id and password to access SAP be it a developer,
consultant, administrator, or end user.
End user is the one who performs transactions in SAP after it goes live.
Such as posting an invoice, goods receipt, creating purchase orders,
sales orders etc.
Power Users are users with advanced knowledge in certain applications
and with special permissions or roles. They work in the specialist
departments in the company and are available to other users as
contact persons.
hat Are SAP End User Manual

It is the same for every other modules although here I reference it mainly for
SAP HR.
1) You should understand which targeted group for the end-user training is for.
Do they have any computer background or not.
2) In what way they are going to make use of the manuals supplied to them
during the course of training.
Let us focus on how to prepare manuals:
In the client side , End Users are not permanent. If they get any better job
outside they will resign and go out. Even if you train them well, again the end-
user team disappears after some time. That is why implementing
company( Client ) expects SAP Consultants to prepare documents which are
self explanatory (even to a layman in SAP) and study themselves and use the
sap easy access very comfortably.
Hence we should prepare a document which explains the following things
comfortably:
A) All the buttons and Screens we have in sap and its importance for an end-
user.
B) All the transaction codes used by end user.
C) The STEP by STEP usage methodology with screen shots and explanatory
foot notes for each Transaction code.
D) Prepare a book a table and columns which should have the following
information:
- Sl.NO.
- Transaction Code
- Navigation path
- Use of the Code
- Expected Result
- Achieved Result
- Remarks/Any Comment
E) Highlight the common troubles during the usage of SAP by an enduser and
give the solutions (ready to use)
These problems you can come across while giving the in house training for the
end-users. You just place them at one place and publish it for their usage in
future for any of their new joinees as an end-user.
F) Every consultant is aware that the entire Organsiational Management is with
end user only. Means consultant should train the end user in entire OM.
G) We should inform the importance of info types and usage for our purposes
at expert mode, PA30, PA40 etc.,
H) Each field in the international infotypes should be explained very clearly
and ensure that they are comfortable with the fields of infotypes which have
been configured for their company.
For example : info type 0001 Org Assignment insists about the three structures
of the HR. We should explain each sub field like Emp Group, Emp Sub Group,
Personnel Area and Sub Area and its importance and relevance to their
company so as to understand while processing them from the enduser point of
view .
When an employee is hired into the company , now the end-user in a position to
understand which employee group and subgroup, Personnel Area And Sub
Area etc., should allotted..
Like this whatever comes across in SAP Easy Access should be insisted
through the training of end users.
I) Demo, exercises and solutions should be provided in the manuals.
J) Glossary of terms and expansion of Acronyms, Abbreviations should be
given. Like this each consultant should focus on end user training and prepare
the documents. *-- Somasekhar
What is SAP Landscape?

By: Kunal
Landscape is like a server system or like a layout of the servers or some may
even call it the architecture of the servers viz. SAP is divided into three
different lanscape DEV, QAS and PROD.
- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180-
Unit Test.
- QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710
Training.
- PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it
or they have been using in their previous implementations or how is the client's
business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients.
Whenever you think you are satisfied with your configuration and you think
you can use it moving forward, you RE-DO it in the golden client (remember,
this is a very neat and clean client and you cannot use it for rough usage). As
you re-do everything that you had thought was important and usable, you get a
transport request pop up upon saving everytime. You save it under a transport
request and give your description to it. Thus the configuration is transported to
the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the
100 (golden) client. This is a configuration only client. Now upon a successful
tranport by the Basis guy, you have all the configuration in the Testing client,
just as it is in the Golden client. The configuration remains in sync between
these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen.
It's a transaction only client where you perform the unit test. Upon a
satisfactory unit test, you move the good configuration to the next SERVER
(DEV). The incorrect or unsatisfactory configuration is corrected in Golden
(may again as well be practised in the sandbox prior to Golden) and
accordingly transported back to 180 (Unit Test) until the unit test affected by
that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may
rather call it the 'ultimate' reference client for all the good, complete and final
configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the
landscape.
DEVELOPMENT ---> QUALITY ----> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the
company's requirement.
QUALITY : is where the core team members and other members test the
customization.
PRODUCTION : is where the live data of the company is recorded.

A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are
given a sandbox server where you do all the configuration/customization as per
the companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is
done is development server and saved in workbench requests, to be transported
to Production server.
3. Production Server: This is the last/ most refined client where the user will
work after project GO LIVE. Any changes/ new develpoment is done is
development client and the request is transported to production.
These three are landscape of any Company. They organised their office in these
three way. Developer develop their program in Development server and then
transport it to test server. In testing server tester check/test the program and
then transport it to Production Server. Later it will deploy to client from
production server.
Presentaion Server- Where SAP GUI have.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
What is the meaning of "R" in R/3 systems?
R/3 stands for realtime three tier architecture. This is the kind of architrecture
SAP R/3 system has.
R/3 means three layers are installed in Different system/server and they are
connected with each other.
1) Presentation
2) Application
3) Database
Why do we call client 000 as golden client?
Golden client contains all the configuration data and master data so some
extent. All the configuration settings are done in golden clients and then moved
to other clients. Hence this client acts as a master record for all transaction
settings, hence the name "Golden Client".

Phase 3

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Phase 3

Diunggah oleh

Hak Cipta:

Format Tersedia

http://www.sap-img.

Baseline configuration is performed by the application consultant while

Uploading the BPML Scope to R/3

Fig. xx: Component-oriented or process-oriented configuration

• Assignment to transport type (transport of all change requests,

Fig. 14 (3-4): From the Reference IMG to the customer-specific

The methodical recording of all activities and information during the

Customizing wizards are similar to wizards found in Windows software

Fig. Xx: BC Sets and compare tool (Customizing Cross-System

To check the consistency of changes in the quality assurance system

• Profiles are more precise and easier to understand.

customers and by SAP’s own developers. A sophisticated enhancement

2. Defining the service level commitment

hat is ASAP Methodology

2. Business Blue print - consists of identifying the client current

The ASAP Roadmap provides the methodology for implementing and

The implementation of your SAP System covers the following phases:

Go Live & Support

Parent Categories: SAP / Project Management / SAP R/3

SAP Implementation Phases (8,366 views)

Edit / Discuss / History / Invite Peers / Connect (18 connections)

Major Editors: Vinay Kuma…/ All

Project Preparation Phase – As per Accelerated SAP (ASAP)

Baseline and Final configuration. How these configurations will be done

Go Live and Support Phase – This is phase where all

The lifecycle of an ERP implementation begins with the understanding

running of the businesses and focussing on the process of streamlining

2. Setting the objectives of ERP implementation; setting the

11. Setup & Configuration: The new environment shall be setup

SMI210 - IMPLEMENTATION METHODOLOGY OVERVIEW

Course Course Schedule &

Course Version: 084

• SAP01 SAP Overview

Implementing a BAdi is a piece of cake. The main problem is to find

Five simple steps are required to implement, e.g. BAdI

1. Call transaction SE18 -> enter ME_PROCESS_PO_CUST -> display

Finally, call transaction SE19 and activate your BAdI implementation.

Re: Badi Implementation Step Reply

Please reward the helpful entries.

Re: Badi Implementation Step by Reply

4. Give implementation a name such as Z_HRPBSGB_HESA_NISR

See below link for more info:

SAP Tickets - What Is That?

3. Whenever a customer logs a call he /she has to mention to which

e: Badi Implementation Step by Reply

two different views are available: · In the definition view, an

oles and Responsibilities of End Users

hat Are SAP End User Manual

What is SAP Landscape?

PRODUCTION : is where the live data of the company is recorded.

Anda mungkin juga menyukai