SAP

MM S4
HANA
SAP is an enterprise resource planning software that was
basically designed to manage resources, information and
activities that are required to complete business processes such
as procurement and managing orders, billing of orders and
management of human resources, INVENTORY MANAGEMENT.
SAP applications work with real-time data. It has the ability to be
configured according to the needs of the business. It allows a
business to make rapid changes in its requirements through a
common set of programs. This tutorial adopts a step-by-step
approach to acquaint the readers with the SAP MM environment
and how to make good use of its features. It will also help
learners to perform procurement of stock materials in SAP.
Audience
This tutorial has been designed for beginners without prior
exposure to materials management. With the customer demands
changing rapidly, this tutorial will be especially useful for those
who want to learn how to manage the supply chain management
side of the business using SAP so that market demands can be
met in the shortest possible time.
Prerequisites
A basic knowledge of ERP concepts will help you in
understanding the concepts of SAP Material Management
System described in this tutorial.
 SAP MM OVERVIEW
SAP -ERP
Module-MM,HR,PP,QA,EWM,FI,CO,BI,
Version-S4 Data base previous ECC - On Server
Data Base- HANA (Cloud)

SAP ERP (Enterprise Resource Planning) is a commercial

software that integrates all the information in a single software,
considering various factors such as time and cost. Organizations
can easily meet their business demands with the help of SAP.

SAP Business Process

SAP MM (Material Management) system. The roles of SAP MM
in a business process are as follows −
 SAP MM is a part of logistics functions and it helps in
managing the procurement activities of an organization.
 It supports all aspects of material management (planning,
control, Inventory Management etc.).
 It is the backbone of logistics that incorporates modules such
as Sales and Distribution, Production Planning, Plant
Maintenance, Project Systems, Warehouse Management,
Finance, Controlling etc

Features of SAP MM
The features of a SAP MM system are as follows −
 SAP MM is one of the modules of SAP that deals with
material management and inventory management.
 Material Management as a process ensures no shortage of
materials or any gaps in the supply chain process of the
organization. SAP MM speeds up the procurement and
material management activities, making the business run
smoothly with complete time and cost efficiency.
  It deals with managing the materials (products and/or
services) and resources of an organization with the aim of
accelerating productivity and reducing costs.
 It deals with the Procurement Process, Master Data (Material
& Vendor Master), Account Determination & Valuation of
Material, Inventory Management, Invoice Verification,
Material Requirement Planning, etc.

What is SAP HANA? ORACLE ERP,

SAP HANA (High-Performance Analytic Appliance) is an

In-Memory Database that uses technology based on
column-based, row-based, and object-based database
technology. It can be deployed on-premise and cloud.
SAP Hana uses In-Memory computing to write, read and
store the data in RAM, rather than processing on normal disk
drives. When compared to normal databases on disk drives,
Hana can process the data 10,000 faster. For example – the
generation of reports with 1 billion files on a traditional
database, took more than 60+ minutes. Where In-memory
computing SAP Hana database, it will take just 10-20
seconds to generate the reports with 1 Billion files.
In Simple terms, SAP Hana is a Digital core with –
 Combination of Hardware and Software Technology

 In Memory Computing Database

 Application Development Platform.

Why SAP Hana.

 SAP Hana Database keeps all the data in the main

system memory (RAM) and improves query performance

faster than other databases as both OLTP and OLAP use
the same database i.e. SAP Hana database.
 SAP Hana Database is the heart of SAP’s In-Memory
technology that helps customers to improve their
operational efficiency with speed and flexibility.
 In-Memory computing is referred to as data that is loaded

and stored in main memory or RAM during booting itself.

 Real-time data replication.

 Includes tools for data modeling, data and life cycle

management, security, operation, etc.

Technology Used in SAP Hana
1.TREX Engine – TREX (Text Retrieval and Extraction) is
responsible for the In-Memory computing capabilities of
SAP Hana. TREX engine enables read capability in the
Hana system.

2.RDBMS Functionality – RDBMS Relational Database

Management System functionality has the ability to store,
write and retrieve data. P*Time is a lightweight, Online
Transaction Processing in-memory RDBMS system that
provides an In-Memory backbone to the SAP Hana
software. RDBMS enables write capability in the Hana
system.
3.MaxDB – MaxDB has the capability of Backup from In
memory constantly. It helps as backup layers to SAP
Hana.
By using these three technologies, SAP company has
developed a high-speed technology memory database
system that is called as HANA System.
Components of SAP Hana
The important components of SAP Hana that offered
by SAP are as follows
1.Hana DB
2.Hana Studio
3.Hana Appliance
4.Hana Application Cloud
Advantages of SAP Hana
 Using the SAP Hana platform, enable to make a smarter

decision faster with real-time data reports

 Process high volumes of transactional data on a real-time

basis.
 Accelerates key business processes with rapid analysis

and reporting
 Invent new business models and processes by leveraging

innovative solutions
 Hana uses column-oriented storage

 SAP Hana uses massively parallel processing

 Uses Push down mechanism.

Industry coverage
SAP S/4HANA Enterprise Management contains core
functions for the industries listed below. Extended industry
functions you will find in chapter SAP S/4HANA Industry-
Specific LoB Functions.

Industry Cluster Industry

Consumer • Consumer Products
 • Wholesale
• Life Science
• Retail including fashion and
Vertical business

Discrete • Aerospace & Defence

• High Tech
• Industrial Machinery and
Components
• Automotive

Energy & Resources • Chemicals

• Mining
• Mill Products
• Utilities

Financial Services • Banking

• Insurance

Public Services • PS & Postal

Services • Engineering, Construction,

and Operations
• Professional Services
• Telecommunications

Sports & Entertainment • Sports & Entertainment

Transportation & Logistics • Transportation & Logistics

What is the difference between ECC and S4 Hana in
SAP MM ?
The main difference between SAP ECC and SAP HANA is
that ECC is the core ERP product within the SAP Business Suite,
whereas HANA is a cloud-friendly, in-memory database designed
to handle transactions and analytics on one system.

What is Client in SAP.

A Client is the highest organizational element of SAP
system’s organizational structure that contains User
Master Data, Customizing data and Application Data. An
SAP S4Hana system can contain or more clients in logical
systems and you can log on to SAP S4 Hana system in a
specific client.
 In SAP system, a client is identified with 3 digits unique

code
 Standard SAP system delivers with clients 000, 001,

066
As per SAP System’s Landscape, you can have 3 or more
clients {Systems}

1. Development – Dev client can be used for

configuration , customization and development of new
components and functionalities.

2. Quality Assurance System – QAS client is used for

testing. upgrades and transports prior to
implementation in production system.
 3. Production Client – PROD client is with live data
used for Productive activities and business data

Additional an SAP system can have the following

clients

4. Sandbox – Sandbox client is used for sampling of

customizing transactions and settings.

5. Test – Test client is used for testing of configuration

settings with data

6. Training – Training client is used for end user

customer training environment

7. Pr-Production – All the pre production activities are

done before the live production activities.

The configuration of SAP system is done in the

development client -> Transported to Quality Assurance
System for testing ->

Final configuration transported to production system which

is final and live system to the production activities.
Sandbox and golden client?
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 development 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".

Differences between SAP HANA and SAP

S/4 HANA
It’s easy to be confused about SAP HANA vs S4 HANA–
the two sound very similar. To put it simply, SAP HANA is
the in-memory database technology that runs the SAP
landscape. S4 HANA is the business suite launched as the
next-generation ERP designed to run exclusively on the
HANA database. The differences between HANA vs S4
HANA are that one is a database, and the other is an ERP
suite that runs on said database.

Differences between SAP ECC vs

S/4HANA
 ECC (ERP) S/4 HANA
Third-party
databases
Database SAP HANA
(Oracle,
IBM, etc)
FI GL
A merger of accounts
controlling are mapped Universal journal stores both GL acco
(CO) and to CO element
finance (FI) primary cost
elements
Choice of
"classic" GL
New general
structure or Uses only the new GL
ledger (GL)
the "new"
GL structure
Customer vs. Separate
Vendor to customer
Business Partner record
business and vendor
partner files
SD rebate
Rebates Settlement management through con
processing

With many companies now having to plan the

transformation to S/4HANA, what are the
main differences between S4/HANA vs
ECC?
1.Database: ECC supports databases from other
providers such as Db2, Oracle, or Informix, however,
S/4HANA only runs on SAP HANA. As a result,
S/4HANA has much faster reaction times thanks to its
in-memory database.
2.A merger of controlling (CO) and finance
(FI): When it comes to the merger of controlling (CO)
and finance (FI), SAP S4 HANA’s structure of the
universal journal stores both the GL account and the
cost element, vs ECC where the FI GL accounts are
mapped to CO primary cost elements.
3.New general ledger: S/4HANA also only uses the
new general ledger (GI), while ECC ran both "new"
and "classic" versions. (In S/4 HANA there many
changes in GL master compare to ECC environment.
Now General Ledger and Cost Element got merged.
Transaction code such as KA01, KA02, KA03, KA06
have been removed. If you try to use them, you will be
redirected to FS00)
4.Customer vs. Vendor to business partner: In ECC,
customer and vendor files were separate, while
S/4HANA combines the common data structure
elements of both into a Business Partner record.
5.Rebates: S/4 HANA has replaced the SD rebate
processing in ECC with settlement management
through condition contracts. (Condition Contract
Management” within Settlements Management which
is the replacement for traditional “Rebates
Management”)
How is SAP S/4HANA Different From SAP
ECC?
SAP S/4HANA streamlines features and processes from
SAP ECC to reduce costs and boost business efficiency.
This means some features have changed, while others
have been replaced or combined into new features.

Some of the key changes in SAP S/4HANA are listed

below.

Default Account-Based CO-PA

In SAP ECC, costing-based CO-PA (CO-Profitability
Analysis) is the default option. But in SAP S/4HANA, the
default option is account-based CO-PA, though you can
run both options together.

FI and CO Merger
Businesses manage their financial data in SAP ECC with
both FI (Finance) and CO (Controlling). In SAP S/4HANA,
FI and CO are part of a single table in ACDOCA,
the Universal Journal. This means you no longer have to
reconcile them with the General Ledger at each period-
end. ACDOCA reconciles them automatically in real-time,
so period-end closings are simpler in SAP S/4HANA.

Material Number Extension

SAP S/4HANA gives you the option of extending the
material number from 18 characters to 40 characters. Bear
in mind, though, if you turn on the extension you will have
to adjust your custom code to the new material length of
CHAR40.

Integrated Business Partners

In SAP ECC, customers and vendors are separate data
objects. SAP S/4HANA integrates customers and vendors
into a unified master data object called business partners.
Customer-vendor integration has several benefits, such as:
 One business partner can have multiple roles and
addresses
 General data is shared across roles, which reduces
your database footprint
 There's less redundancy since unused data is deleted
after a certain time-period
Real-time MRP Totally Change In S4HANA From SAP
ECC
To process material requirements planning (MRP) in SAP
ECC, you must wait until non-peak hours and run a batch
job. In SAP S/4HANA, you can run MRP in real-time. SAP
has also simplified subcontracting in SAP S/4HANA. The
downside? You can no longer run MRP at the storage level
like in SAP ECC, but only at plant and area level.

Integrated SAP APO

For SAP S/4HANA, SAP integrated the main SAP
Advanced Planning Optimizer (APO) sub modules into two
new configurations:
1.Demand planning and supply network planning are
now integrated in the new SAP Integrated Business
Planning (SAP IBP) module.
2.Production planning and detail scheduling, and global
ATP have partly merged in the SAP S/4HANA digital
core. Account,Purchasing,Invoicing,
These changes mean you can’t automatically migrate from
SAP APO to the new configurations.
Mandatory Material Ledger
The Material Ledger (ML) is another feature that's optional
in SAP ECC but mandatory in SAP S/4HANA. Most
companies don't activate the ML in SAP ECC due to
frustration with the many aggregate and index tables. But
in SAP S/4HANA, the ML is part of ACDOCA, so this
frustration is now a thing of the past.

New Features in SAP S/4HANA

SAP S/4HANA includes a ton of new features to help you
manage your data more effectively. Key features include
the following.

ACDOCA: The Universal Journal

As mentioned before, SAP S/4HANA combines several
data modules into a single table called ACDOCA (the
Universal Journal). This includes asset accounting (AA),
GL, ML, management accounting (MA), FI, and CO-PA.
ACDOCA removes many aggregate and index tables,
which greatly reduces your data footprint. It's also a much
more efficient system.

MATDOC Inventory Management

SAP S/4HANA introduces MATDOC, a new inventory
management system that eliminates over 26 tables
present in SAP ECC. Now, material documents are stored
in MATDOC instead of MKPF or MSEG tables. This
removes redundancy and improves stock reporting
efficiency.

The SAP HANA Database

As we discussed earlier, SAP S/4HANA can only run on
the SAP HANA database. But, thanks to the SAP HANA
Cloud database, SAP S/4HANA is faster and more efficient
than SAP ECC. Why? There are several reasons. Firstly,
SAP S/4HANA reads data from the main memory instead
of the hard disk, so there are fewer data movements. Next,
the tables in SAP S/4HANA are column-based instead of
row-based, so it only reads the relevant column in a query.
It can also process different columns in parallel. There are
no aggregate, index, or history tables since applications
can access the original data. Lastly, SAP S/4HANA
combines the online transactional processing (OLTP) and
online analytical processing (OLAP) tables. You no longer
need to reconcile them.

Advanced ATP(Available to Promise)

In SAP ECC, you can check product availability, product
allocation, and backorders with available-to-promise
(ATP). With SAP S/4HANA, you can do all this and more
with advanced ATP (aATP). aATP uses automation for
functions like: 100,500 Stock available 100 Issue 400
available PO Release automatically stock regain 500
  Releasing items for delivery
 Checking stock availability in alternative plants
 Performing mass availability checks

Global Trade Services

SAP S/4HANA has global trade services (GTS), which
replaces the foreign trade functions in SAP ECC. SAP
GTS uses automation to speed up processes that were
manual in SAP ECC. This includes embargo checking,
license checks, and import and export
declarations.Logi.,Finance curr.Trans.

FSCM Credit Management (Financial Supply Chain

Management)
FI-AR-CR was the credit management system in SAP
ECC. In SAP S/4HANA, credit management falls under
financial supply chain management (FSCM). Automated
workflows in FSCM-CR remove manual processes for
tasks like credit limit approval and risk scoring. Also, its
distributed architecture means it can interface with external
credit agencies directly.

Extended Warehouse Management

In SAP ECC, warehouse management takes place in the
Warehouse Management (WM) module. But this is
replaced by the extended warehouse management (EWM)
module in SAP S/4HANA. SAP EWM helps you manage
complex warehouse processes such as labor management
and goods distribution with ease.

Revenue Accounting and Reporting (RAR)

The SAP S/4HANA Revenue Accounting and
Reporting (RAR) module replaces SAP ECC’s SD
Revenue Recognition module. RAR is an add-on that’s
based on the new, five-step revenue recognition model
found in International Financial Reporting Standard 15
(IFRS 15). RAR comes with new optimized contract
management capabilities to comply with IFRS 15. At the
same time, it simplifies revenue recognition.

SAP Fiori User Interface

SAP S/4HANA introduces a new user interface, SAP Fiori.
SAP Fiori gives users a consistent, intuitive, and integrated
experience. With SAP Fiori, you can get work done faster
and more accurately. This speeds up onboarding and
training, and provides a better user experience. You can
also create custom enterprise apps that work consistently
across devices.

Benefits of Moving to SAP S/4HANA

In 2021, 72% of businesses said the biggest benefit of
SAP S/4HANA was improved efficiency, followed by
greater satisfaction (61%). Other benefits of moving to
SAP S/4HANA include:

Conclusion
Understanding the key differences between SAP releases
makes it easy to see why transformation to S/4 HANA is
beneficial, and how with the right SAP migration scenario,
the transition can be a smooth process.
SAP S/4HANA transformation is now less of a choice and
more of a necessity. This is because SAP is planning to
end all support for older versions of their product by 2025.

BENEFITS
 Better integration with other SAP products
 Lower costs, such as lower operational and ownership
costs
 A smaller database footprint due to simplified data
models
 Automated processes improving productivity and
performance
 Faster, more intelligent decision-making
 Higher overall profit
SAP S4HANA Activate Method For Migration from
ECC to S4HANA
SAP recommends that project teams follow the
methodology when they implement S/4HANA or SAP cloud
applications, whether these projects are new
implementations, upgrades or migrations. The
methodology is designed to handle cloud, on-premises or
hybrid projects.

Each SAP application is associated with its own version of

Activate. Although the core design is the same, the
activities and deliverables within work streams vary.

Here's a look at SAP Activate methodology's main

components, phases, work streams and iterations.

Components
The SAP Activate methodology consists of three core
components:

 SAP Best Practices is a set of standard-delivered best

practice processes and configurations that provide a
baseline for getting started with the implementation. The
Best Practices content lists and describes the project's
scope. The project team can use it to explore and
understand the out-of-the-box scope. The Best Practices
also provides a downloadable set of accelerators, such
as a list of scope items, an overview of the sample
master data and overviews of delivered configurations.
 The SAP Best Practices content for all available SAP
applications are included in the SAP Best Practices
Explorer.
 Guided Configuration consists of tools and
accelerators. It also refers to the process of applying
updates and changes to the SAP Best Practices
configuration during the implementation. The team can
use the Guided Configuration to make changes to the
project landscape.
 Methodology contains the principles, practices,
workstreams, content, deliverables and responsibilities
that work together as a complete process for delivering a
project. SAP Best Practices and Guided Configuration
are both managed under the methodology.
Phases
The SAP Activate methodology is split into a pre-project
phase, followed by four core phases and a post-project
phase. Each phase contains a specific set of related
activities and deliverables that drive the project forward.

The discover phase is the pre-project phase. In this

phase, the project team prepares for implementation by
building a business case. Specific team members work to
understand the scope of the SAP Best Practices content
library, review the standard-delivered content and identify
any potential items that aren't included in the scope of Best
Practices. The project team also begins to look at
implementation partners to help with the implementation
journey.

The prepare phase is the first core phase. In this phase,

the organization begins preparing for the project. Once the
project plan and change management strategy is created,
the organization defines the project goals and high-level
scope. The organization then defines, prepares and
enables the project team. Once the team is assembled and
the project's goals and scope are defined, the project
officially begins.

The explore phase is the second core phase. During this

phase, the project team validates the baseline processes
and configuration provided as part of the SAP Best
Practices content library. The team identifies any gaps and
changes and defines configuration values for items such
as drop-down lists and selection criteria. The team also
prepares for data loading and any software extensions.

The realize phase is the third core phase. The team

configures any gaps and changes that were identified in
the explore phase, executes the software walkthrough for
each iteration, launches data migration activities and tests
and trains. Preparation of the production instance, cutover
plan and post-go-live support plan also happens in this
phase.

The deploy phase is the fourth and final core phase. The
project team conducts any and all final change
management activities. The team completes preparation
for the cutover and executes the post-go-live support plan.
The project then goes live.

The run phase is the post-project phase, and is focused

on the ongoing operation, optimization, upgrades and
release management and maintenance of the implemented
software as a productive environment. This is not really a
bona fide phase of the project itself, but rather exists to
ensure that these activities are included as part of the
implementation.

The SAP Roadmap Viewer describes each phase of the

methodology and provides a list of the main phase
activities. A content repository provides information,
activities and accelerators -- including documents such as
project plans, templates, configuration workbooks and
guides -- for the activities and deliverables within each
phase. The team can filter activities and deliverables by
workstream.

Benefits of SAP HANA Migration Cockpit

1.Preconfigured content and mapping for each migration
object. Examples are Cost center, Profit center,
Material, Customer etc.
2.Predefined template files and staging tables for each
migration object
3.Automated mapping between the template and target
structure
4.Migration programs are automatically generated- no
programing required
5.Available for SAP S/4 HANA and SAP S/4 HANA cloud
SAP HANA Migration Tools
We have some important SAP HANA migration tools that
we need to do the SAP ECC to HANA data migration.
Understand them in detail and how they work.
 Maintenance Planner
 SI Check (simplification items)
 Custom Code
 Sizing Report
Some Supporting SAP HANA Migration tools are:-
 SUM Tool (Software Update Manager)
 DMO (Database Migration Option)
Maintenance Optimizer

ASAP METHOLODOGY
This document will help in getting basic understanding on ASAP
Methodology.ASCILERATED SAP
 We’ll discuss below points:
1- What is ASAP Methodology?
2- Phases of ASAP Methodology
3- Brief explanation of each phase
What is ASAP Methodology?

ASAP stands for Accelerated SAP.

Its purpose to help design SAP implementation in the most
efficient manner possible.
Its goal is to effectively optimize time, people, quality and other
resources, using a proven methodology to implementation.
1- Phase of ASAP Methodology
ASAP focuses on tools and training, wrapped up in a five-phase
process oriented road map for guiding implementation.

The road map is composed of five well-known consecutive

phases,POJECT IT MEANS PLAN
• Phase 1 Project Preparation
• Phase 2 Business Blueprint
• Phase 3 Realization
• Phase 4 Final Preparation
• Phase 5 Go-Live and support
Support 6
Brief explanation of each phase
ASAP Methodology – Phase 1 : Project Preparation
Phase-1 initiates with a retrieval of information and resources. It
is an important time to assemble the necessary components for
 the implementation. Some important milestones that need to be
accomplished for phase 1 include
• Obtaining senior-level management/stakeholder support
• Identifying clear project objectives
• Architect an efficient decision-making process
• Creating an environment suitable for change and re-
engineering
• Building a qualified and capable project team.
ASAP Methodology – Phase 2- Business Blueprint
SAP has defined a business blueprint phase to help extract
pertinent information about your company that is necessary for
implementation. These blueprints are in the form of
questionnaires that are designed to probe for information that
uncovers how your company does business. As such, they also
serve to document the implementation.
Each business blueprint document essentially outlines your future
business processes and business requirements. The kinds of
questions asked are
germane to the particular business function, as seen in the
following sample questions:
1) What information do you capture on a purchase order?
2) What information is required to complete a purchase order?
ASAP Methodology – Phase- 3 – Realization
With the completion of the business in phase 2, “functional”
experts are now ready to begin configuring SAP.
The Realization phase is broken in to two parts.
1) Your SAP consulting team helps you configure your baseline
system, called the baseline configuration.
1) Your implementation project team fine-tunes that system to meet
all your business and process requirements as part of the fine
tuning configuration.
The initial configuration completed during the base line
configuration is based on the information that you provided in
your blueprint document. The remaining approximately 20% of
your configuration that was not tackled during the baseline
configuration is completed during the fine tuning configuration.
Fine tuning usually deals with the exceptions that are not covered
in baseline configuration. This final bit of tweaking represents the
work necessary to fit your special needs.
Configuration Testing-
With the help of your SAP consulting team, you segregate your
business processes into cycles of related business flows. The
cycles serve as independent units that enable you to test specific
parts of the business process. You can also work through
configuring the SAP implementation guide (IMG). A tool used to
assist you in configuring your SAP system in a step by step
manner.
Knowledge Transfer-
As the configuration phase comes to a close, it becomes
necessary for the Project team to be self-sufficient in their
knowledge of the configuration of your SAP system.
Knowledge transfer to the configuration team tasked with system
maintenance (that is, maintenance of the business processes
after Go-live) needs to be completed at this time. In addition, the
end users tasked with actually using the system for day-to-day
business purposes must be trained.
ASAP Methodology – Phase 4 – Final Preparation
As phase 3 merges into phase 4, you should find yourselves not
only in the midst of SAP training, but also in the midst of rigorous
functional and stress testing.
Phase 4 also concentrates on the fine tuning of your configuration
before Go-live and more importantly, the migration of data from
your old system or systems to SAP.
Workload testing (including peak volume, daily load, and other
forms of stress testing), and integration or functional testing are
conducted to ensure the accuracy of your data and the stability of
your SAP system. Because you should have begun testing back
in phase 2, you do not have too far to go until Go-live.
Now is an important time to perform preventative maintenance
checks to ensure optimal performance at your SAP system. At
the conclusion of phase 4, take time to plan and document a Go-
live strategy. Preparation for Go-live means preparing for your
end-users questions as they start actively working on the new
SAP system.
ASAP Methodology – Phase 5 – Go-live and Support
The Go-live milestone is itself is easy to achieve; a smooth and
uneventful Go-live is another matter altogether. Preparation is the
key, including attention to what-if scenarios related not only to the
individual business processes deployed but also to the
functioning of technology underpinning these business processes
and preparation for ongoing support, including maintenance
contracts and documented processes and procedures are
essential. Support Team provide training on sap to all employees.
support team will help onsite or off site support to clint by solving
error tickets.tickets will be sorted by levels of deficulty.

SAP MM NAVIGATION
The first step to understand SAP is to have a basic knowledge of its various screens. The
following sections describe how to navigate through the screens available in SAP and how to use
the functionalities of the standard toolbar.

Login Screen
Log on to the SAP ERP server. The SAP login screen will prompt you for the User ID and the
Password. Provide a valid user ID and password and press enter. The user id and password are
provided by the system administrator. The login screen appears as follows −

Standard Toolbar Icon

The following screenshot shows the toolbars available on the SAP screen. −
Given below is a brief description of the available toolbars −
 Menu Bar − Menu bar is the top line of the dialog window in the SAP system.
 Standard Toolbar − This toolbar includes standard functions such as save, top of page,
end of page, page up, page down, print, etc.
 Title Bar − Title bar displays the name of the application/business process you are currently
in.
 Application Toolbar − Application-specific menu options are available on this toolbar.
 Command Field − to start a business application without navigating through menu
transactions, some logical codes are assigned to the business processes. Transaction
codes are entered in the command field to start an application directly.

Standard Exit Keys

Exit keys are used to exit the module or to log off. They are used to go back to the last accessed
screen. The following screenshot highlights the standard exit keys used in SAP −
New Session Icon
For creating a new session, we use the following keys shown in the screenshot below −

Log Off
It is a good practice to log off from the SAP system when you finish your work. There are several
ways to log off from the system, but it can be done using the following instructions as shown in the
screenshot below −