SAP

Fresco play course Id: 719

 (ERP) Enterprise Resource planning:

 Business Process: It is like a step by step plan that teams follow, using
different tools to get things done and achieve specific goals.

 Types of business process:

1. Core Process like (Purchasing, manufacturing, sales)

2. Support Process like (accounting, recruitment, administration)
provide assistance and keep everything running smoothly.

 End to End Business process: f

 Master Data: Core data that defines business such as customer

information, product information, employee data.
 Business process master list (BPML): It is a detailed roadmap for
businesses outlining all the steps and tasks needed crucial for setting up
 computer programs like ERP. It covers everything from daily tasks to
managing data and is essential for big projects.

 SAP S/4HANA:
1. It is an integrated ERP suite developed by SAP.
2. It is designed to provide simplified data model enhanced user
experience (UX) and improved analytical capabilities.
3. It’s uses:
i) Simplified data model.
ii) Modern UX.
iii) Cloud compatiblity.
iv) Integration with advance technology like A.I, ML and IoT.
v) End to End business processes
vi) Preparedness for future innovation

1. Order to Cash (O2C):

It is the process from a customer placing an order the company
preparing and shipping the product, sending an invoice to finally getting
paid.
Flow of O2C
Order Prepare pack and ship invoice payment

Different types of customer orders can affect how a company goes through
the "Order to Cash" process. Here are simple explanations:
1. Make to Stock (MTS Order):
 Example: Making things like pens, cars, or stationary that are
already available in stock.
 Explanation: Products are ready-made, and when a customer
orders, the company just picks from what's already there.
2. Make to Order (MTO Order):
 Example: Creating things like factory equipment based on a
specific order.
 Explanation: Products are assembled or made only when a
customer places an order, like custom-made items.
3. Engineer to Order (ETO Order):
  Example: Designing and making things like airplanes or power
plants based on unique customer requirements.
 Explanation: Products are designed and manufactured from
scratch based on what a customer needs.

2. Other processes team up with 'Order to Cash' (O2C) to make business

flow smoothly:
1. 'Opportunity to Order': Turns potential sales into confirmed orders.
2. 'Sustain and Retain': Deals with customer support after a sale.
3. 'Forecast to Stock': Plans and makes products needed for delivery.
4. 'Procure to Pay': Manages buying materials for order fulfillment.
5. 'Concept to Launch': Introduces new products, especially for engineered
ones.
6. 'Record to Report': Records all financial aspects of a customer order.
In simple terms, these processes work together with 'Order to Cash,' covering
everything from creating sales opportunities to customer support, planning,
buying, and recording finances.

3. Procure to pay (P2P):

"Procure to Pay" is the company's shopping journey:
1. Find Suppliers: Look for good options.
2. Get Requests: Employees say what they need.
3. Get Quotes: Ask for prices to find the best deal.
4. Make Deals: Negotiate terms and conditions.
5. Place Orders: Tell the supplier what's needed.
6. Get Stuff: Receive materials or services.
7. Quality Checks: Ensure things are good.
 8. Record and Pay: Keep track and settle the bill.
It's like the company's way of finding, buying, and paying for what it needs.

4. Different processes team up with "Procure to Pay" (P2P):

1. 'Order to Cash': Handles customer orders and provides input for buying
materials.
2. 'Forecast to Stock': Plans and makes materials, providing input for
procurement.
3. 'Concept to Launch': Introduces new products, giving input for material
procurement.
4. 'Record to Report': Records financial transactions during the buying
process.
In simple terms, these processes work together with 'Procure to Pay,' covering
customer orders, planning, introducing new products, and recording finances.

5. Forecast to Stock:
'Forecast to Stock' is like a company making a smart guess about what stuff it'll
need. They plan how to make it, check if they have enough tools and people,
and then follow through until the products are ready to be stored. It's like
arranging everything so that the right things are in the right place at the right
time in the company's storage.

In the 'Forecast to Stock' process, how a company plans and makes things
depends on the industry and order type:
1. Discrete Manufacturing:
 What it is: Making easily identified items. Like computer, cars
2. Repetitive Manufacturing:
 What it is: Continuously making the same product. Like cookies,
biscuits
 3. Lot-Based Manufacturing:
 What it is: Making products in batches. Like particular model of
smartphone.
4. Process Manufacturing:
 What it is: Continuously producing undifferentiated materials like
oil or chemicals.
In simple terms, companies decide how to make things based on what they're
producing and the type of industry they're in.

6. Processes which integrates with ‘Forecast to Stock’ process

In the 'Forecast to Stock' process:

1. 'Order to Cash': Manages customer orders, helps plan what to make.
2. 'Procure to Pay': Deals with buying materials. Guides what to buy for
manufacturing.
3. 'Concept to Launch': Introduces new products. Guides material
production during research.
4. 'Record to Report': Records financial transactions. Guides recording
costs during manufacturing.

In simple terms, these processes work together with 'Forecast to Stock,'

affecting customer orders, material buying, new product launches, and
financial records during manufacturing.

Link: https://chat.openai.com/share/a1aea555-f4bb-4e8a-8ff8-
84770297f19b

7. Definition of ‘Plan to Maintain’ process

'Plan to Maintain' is a process where a company plans, buys, and takes
care of its equipment and assets from acquisition to retirement. Key
activities include planning for assets, coordinating technical design for
acquisition, securing budgets, implementing preventive maintenance for
longer asset life, and handling complex retirement processes while
 following legal and environmental rules. It's about making sure
everything runs smoothly throughout an asset's lifecycle.
Scenarios in ‘Plan to Maintain’ process
The way a company takes care of its equipment varies based on the
industry and the type of assets. Here are some examples of assets that
require complex maintenance of both hardware and software in the
'Plan to Maintain' process:
 Oil rig
 Ship
 Rail line
 Manufacturing line for car, airplane
 Steel plants
 Real estate such as hotel, hospital
 Database servers hosted by a public cloud company.

Hire to Retire

Record to Report: 'Record to Report' is like keeping a detailed and accurate

diary of a company's money activities, and then using that diary to create
reports for legal requirements and management analysis.

(ERP) Enterprise Resource Planning:

Enterprise Resource Planning (ERP) is like a super app for businesses. Its main
job is to automate and manage lots of different tasks a company does, all in one
place. Instead of using many separate apps, an ERP brings everything together
in a single suite. It's like having a central command system to handle the
essential tasks of a business. SAP is a big company that makes one of the most
popular ERP systems used by many businesses.

 Enterprise Resource Planning (ERP) is a business application to

manage core processes of an enterprise such as record to report, order to
cash, procure to pay, forecast to stock, acquire to retire, hire to retire
  All these processes are integrated across multiple functions like sales,
manufacturing, procurement, supply chain, finance, asset management,
engineering, human capital management
 Management of an ERP requires process and functional processes. It also
requires multiple technical skills related to database and application
maintenance, analytics, programming, security.
 While each ERP can be customized to fit a company's needs, it's usually a
good idea to stick to standard processes.
 The size and complexity of a company's tasks are important factors in
choosing the right ERP. Think of it like picking the right tool for the job,
considering how big and complex your business is.

Key features of an ERP application:

i. Integration across business processes
ii. A common set of master data
iii. Records day-to-day transactions
iv. Periodic processing
v. Real time analytics
vi. A common database
vii. Consistent user experience and user interface
viii. Use of best practices and re-usable business process design
ix. Application maintenance and support by IT teams
x. Multi-country and multi-industry capabilities
xi. Audit trail and transparency
xii. Security and authorization

Benefits of an ERP application

 Recording of transactions in a software, financial and non-financial processes, in a
common database generates data and allow easy analysis.
 History of every data is retained and enables transparency
  Authorization concepts in an ERP system reduces possibility of unauthorized access
and fraud
 Integration across processes results into faster processing and optimization of
resources
 The very fundamental objective of implementing an ERP is to increase operational
efficiency of an enterprise along with resource optimization
 An ERP software provides the framework to run the business processes in multiple
ways and reduces the need of building a software from scratch for each enterprise.

SAP
 SAP is the world’s largest provider of enterprise application software
 SAP stands for Systems, Applications & Products in Data processing
 SAP serves more than 4,25,000 in more than 180 countries as of January 2019
 SAP has broadest portfolio of modular and suite applications, available on premise, in
the cloud and hybrid
 SAP has largest cloud portfolio with more than 100 applications
 SAP is a recognized database leader
 SAP applications include packaged solution for 25 industries

Roadmap for Industry, company and solution specific

https://www.sap.com/products/roadmaps.html

SAP product portfolio

In general there are eight types of project portfolio,
1. ERP and digital core
i. SAP S/4HANA is the latest solution from SAP in this portfolio category, also
known as digital core. Or SAP Intelligent ERP.
2. CRM and Customer Experience
i. SAP C/4HANA is the latest solution from SAP in this portfolio category
and available on cloud.
3. Network & Spend Management
i. Network and spend management involves handling how a company works
with its suppliers and manages its spending. It's all about organizing the
buying and supplying of goods and services for the organization.
ii. SAP ARIBA, SAP Fieldgalss and S4AP Concur are the key applications
from SAP in this portfolio category and hosted on cloud.

4. Digital Supply Chain

i. Supply chain is the journey of goods from suppliers to consumers. Using
digital tools like IoT, Blockchain, and Machine Learning makes it more
efficient and opens up new business possibilities.
ii. SAP Integrated Business Planning (IBP) is the key applications from SAP
in this portfolio category and hosted on cloud.

5. HR and People Engagement

i. It covers workforce management, including hiring, talent development,
and compensation.
ii. SAP SuccessFactors is the key applications from SAP in this portfolio
category.

6. Digital Platform

i. It is like a base for handling data and adapting business processes to fit
the organization's needs.
ii. It uses SAP HANA
iii. Digital platform consist of many applications from SAP for data
management, enterprise information management, cybersecurity,
risks and governance.

7. Analytics
i. SAP has many analytical suite of application on cloud and in premise
such as SAP BW/4HANA, SAP Analytics Cloud, Predictive Analytics.

8. Intelligent Technologies
i. SAP Leonardo is a tool by SAP for automating business processes within
SAP and its applications.
SAP Intelligent Enterprise: The Intelligent Enterprise is SAP's modern solution,
using various tools to automate processes, please customers, empower employees, and
support business.
 SAP intelligent enterprises has three key areas
1. Intelligent suite
2. Digital platform
3. Intelligent technologies

1. INTELLIGENT SUITE:
The Intelligent Suite from SAP manages key enterprise processes like customer
relations, employee management, supply chain, and core operations. It consists of five
components:

f
 2. Digital platform:
The Digital Platform by SAP helps companies handle data from any source and in any
format. It focuses on extending and integrating business applications and has two
parts:

3. Intelligent technologies:
Intelligent technologies, also called SAP Leonardo, are cutting-edge tools
concentrating on IoT, blockchain, big data, machine learning, and AI.

Some key points of SAP S/4HANA

i. It is also called as SAP digital Core
ii. It is based on SAP HANA
iii. SAP HANA combines database, data processing, and application
platform capabilities in a single in-memory platform.
 iv. The first release of ERP application by SAP was in 1979.

 SAP R/2 was the first version of SAP ERP in 1979 but had limited features.
 SAP R/3 improved things, connecting functions like Sales and Accounting.
 SAP ERP was the first to link all business functions using a centralized database.
 Now, SAP S/4HANA is the latest version, replacing SAP ERP by 2025, SAP plans to
shift all ERP systems to S/4HANA.
 S/4HANA brings many new features compared to SAP ERP.

SAP S/4HANA Architecture:

 SAP S/4HANA is deployed on HANA database

 Database can be hosted on premise or in cloud
 SAP S/4HANA has three tier architecture as shown in the picture here
o Database holds the structured set of data
o Application contains the software designed to perform certain functions and
for reporting
o Presentation layer is the user interface via which a person can access the
application and perform the required tasks

8. Key benefits of SAP S/4HANA:

i. Integrated business processes

ii. Offers next-gen user experience including digital assistant
iii. Include machine learning and predictive analytics capability for
actionable insights
iv. Real time data analytics
 v. Provides country specific and industry specific solutions
vi. Scalable architecture

Question 1: When SAP S/4HANA is released by SAP?

Answer: First version of SAP S/4HANA was released in year 2015.

Fresco Play Course Id: 725

System Landscape in SAP S/4HANA:

A system landscape for SAP S/4HANA is like a collection of various computer

setups, each designed for a specific purpose:
1. Production System: For real business operations.
2. Pre-production System: For testing changes before going live.
3. Quality System: For thorough testing to ensure quality.
4. Development System: Where new features are developed.
5. Sandbox System: A safe space for experimentation.
Each system can stand alone or be part of a group (same system ID), providing flexibility and
data segregation.

Client in SAP S/4HANA:

In SAP, a system can have different units called clients, each with its own data.
Some data is shared, but most is exclusive to each client. Users access the system by
specifying a client on the logon screen. Access is determined by the user's role in the
organization.

Front End in SAP S/4HANA:

1. The front end in SAP S/4HANA is the interface where business users or
applications interact with transactions.
 2. There are three types of front end for SAP S/4HANA
i. Fiori
ii. SAP classical GUI
iii. SAP WEBGUI

3. Each, like SAP GUI and Fiori, has distinct uses, meaning not all transactions
and configurations are accessible through both interfaces.

Fiori (Modern User Interface):

i. Accessed via web browser.
ii. No desktop or laptop installation needed.
iii. Developed using UI5 technology.
iv. Ideal for smartphones and tablets.
v. Primary front end for many new applications in SAP S/4HANA.
vi. Configuration in on-premise version still requires SAP GUI.

SAP GUI (Classical User Interface):

i. Accessed through SAP logon pad.
ii. Requires installation on desktop or laptop.
iii. Developed using ABAP programs.
iv. Not accessible on smartphones or tablets.
v. Used for specific business processes like master data and configuration in on-premise
SAP S/4HANA.

WebGUI in SAP S/4HANA:

i. Similar scope and processing as classical GUI.
ii. The only difference form classical UI is that it doesn’t require installation.

Accessing SAP S/4HANA with SAP Classical GUI:

i. Install SAP GUI on the system.
ii. Select a system by double-clicking.
iii. SAP logon screen appears.
iv. Enter client, user ID, and password.
v. Users have access only to systems relevant to their organizational role.
SAP Logon:
A GUI has two types of apps – SAP logon and SAP logon pad

1. SAP Logon:
 Allows users to add various SAP applications like ERP, CRM, SRM,
BI.
 Requires system IP and instance number, provided by the SAP
administration team.
2. SAP Logon Pad:
 Pre-loaded SAP systems.
 Users can't add systems.

10-01-2024 Meeting Notes

The division of Database is called Client.
Eg:- If there are two teams development and testing team and both of them having different
allocation of data so each team is called Client.

Important navigation functions in SAP GUI:

Implementation guide (IMG)

IMG helps set up SAP S/4HANA. It's a toolbox for configuring tasks. Access it with "SPRO"
in the command box. It's for tech, not regular business users. Changes here affect how things
run, so be careful. Each task has instructions to guide you.
Shortcuts in SAP GUI:
i. Function button (f1) is used for help
ii. Search function is used by (f4)
iii. (f8) is used for execution

SAP Fiori launch pad – Types of application:

1. Transactional: used for performing transactional tasks such as leave requests, travel
requests, and purchase orders. They can be deployed on any database that provides
adequate performance, including HANA.
2. Analytics: provide role-based real-time information about business operations. Runs
only SAP HANA DB.
 3. Factsheet: Factsheets are like information cards that show important details about
key things in a system. They work only on a specific type of database (SAP HANA)
and need a certain programming foundation (ABAP stack).

FRESCO COURSE ID: 726

SAP S/4HANA has different areas (like sandbox, development, quality, and production) for
specific jobs. When working on a customer's system, follow strict rules.

 Client: A client is an independent unit in each system which has its own data set.
 SCC4 shows clients in SAP.
 Logical system is a unique ID for sharing and distributing data. It helps locate
documents/resources in a system.
 Avoid changing logical system number in a productive system.
DATABASE IN SAP S/4HANA:
In SAP, data for applications is stored in database tables. Each data set can be in one or more
tables, meaning creating data may update multiple tables simultaneously. Conversely, a
single table can be updated by multiple tables. These tables store configuration data, master
data, transaction data, and transaction data. Types of tables include cluster and transparent
tables, and it's also possible to made custom tables. Updating custom tables requires

programming, either manually or through logic in a program. Configuration and

implementation guide (IMG) in SAP S/4HANA.

Configuration and implementation guide (IMG) in SAP S/4HANA:

In SAP, customization is done through tasks in the Implementation Guide (IMG) accessed
with SPRO. It's organized by modules in SAP S/4HANA. Understanding business processes
is key, and help documentation is available.
Customizations are in the development system, then moved to quality and production after
testing. They usually start with Z or Y. It's advised not to overwrite standard SAP objects;
instead, copy and modify if needed.

When people make customizations in SAP, there aren't strong safety checks. These changes
are usually done by experts (consultants), and if there's a mistake, it can mess up how the
business processes work in SAP. So, it's important to be careful when making these changes.

 Activation of Business function in IMG:

 1. There are certain business processes which are not a part of standard SAP system
delivered and is included in business function. Business function refers to extended
business process and needs activation
2. The enterprise extensions and business functions are activated using transaction
SFW5 or via IMG .
3. The business function controls additional customization and transactions. These
menus are available only after activation of business functions.
4. Activation of business function is normally a part of change request and should be
thoroughly tested in quality system
5. There are certain business functions which cannot be deactivated once activation is
done.

ABAP programming in SAP S/4HANA:

 Advance Business Application Programming (ABAP) is the programming language

used in SAP.
 All programs in SAP S/4HANA are created using ABAP. An ABAP objects can be a
transaction, report, workflow, form, interface.
 The list of ABAP objects which needs to be modified/ created during an SAP projects
is depicted as RICEFW
o R: reports
o I: Interface to integrate other applications with SAP S/4HANA
o C: Conversion for data migration from another system to SAP S/4HANA
o E: Enhancement in SAP standard programs
o F: Forms
o W: Workflow
 During a transaction processing, the program may be terminated by system due to
technical errors is known as ABAP dump. To resolve some issues, technical
consultants may need to debug the ABAP program some times.

ABAP workbench and SAP program is demonstrated in next section Before moving ahead go
through DEMO- SAPS4Foundation04 - 04

Demo steps to open ABAP program code and objects:

Step 1: Go to display customer master

Step 2:Go to system status and display program name

Step 3: Go to program display via SE38

Step 4:Display the program via object navigator SE80

Interfaces with SAP S/4HANA:

Enterprises often integrate applications for seamless processes. SAP S/4HANA, like other
systems, integrates with various applications (SAP/non-SAP). For example, finance sends
payment files to banks, and banks send transaction details back. This involves using multiple
middleware solutions and requires ABAP programming in SAP S/4HANA, as well as
programming in interfaced applications. The goal is to ensure smooth communication and
data flow across the complex IT landscape.

Creation of a message for use in custom program or task:

In SAP, messages play a crucial role in providing information, warnings, or errors during
transaction processing. They are organized into message classes based on the relevant module
or area. Each message within a class has a unique number for identification and explanation.

Messages can be self-explanatory or include long text with detailed information, such as
diagnosis, system response, and procedures. These messages are utilized in both SAP
standard programs and custom ABAP programs, often in specific configurations. Custom
messages can be created using transaction code SE91, and all messages are stored in table
T100.

TRANSPORT SYSTEM:

In SAP, a transport request is like a special box that holds all the changes you make in the
development area. When you finish working on something in the development system, you
put it in this box. Then, you can move this box to other places, like testing or the real working
system. This helps make sure that everything stays the same and works correctly in different
parts of SAP. It's like a careful way of taking your changes from one place to another, so
nothing gets messed up.

TRANSPORT MANAGEMENT:

In SAP systems, changes like settings and programs are moved from one system to another
using a transport request. This request holds all the details of what's changed. Everything is
first done in the development system and then sent to other systems. This keeps things
consistent across different parts of the system. Avoid making direct changes in the production
system for data consistency. The transport request travels from development to quality and
then to production systems.
There are two types of transport requests: workbench and customizing.

1. Workbench Request:
 Contains cross-client changes like ABAP objects and general customizing
tasks.
 Cross-client means it applies to the entire system.
2. Customizing Request:
 Includes client-specific changes made in the implementation guide.
 Client-specific means it applies to a particular client in the system.

Change requests follow a naming convention like XXXKnnnnnn, where:

 XXX is the system ID (e.g., DEV).

 K is a fixed alphabet.
 nnnnnn is a numerical range (e.g., DEVK000001).

Status of Transport Request:

 Transport request can have status as released or not released. A transport request is
released when all the changes are done and is ready to be moved to another system
 A transport request is modifiable until it is released. Once a transport request is
released, it can no more be modified.
 Modifiable – can be transported to another client is same system
 Released – can be transported to all systems and clients.

SEQUENCE OF TRANSPORT:

USER MENU:

The SAP Area Menu is a feature that allows users to customize their menu based on their
needs. It provides several advantages:

1. Streamlined Authorization:
2. User-Friendly Template
3. Faster Navigation
4. Access and Customization:
  Accessed through transaction code SE43.
 Hierarchy can mirror the SAP menu at various levels.
 Accessed by entering its name in the command box or added as a favorite.
 Can be set as a start menu in transaction code SU01.

However, for business users exclusively using Fiori, the SAP Area Menu in the classical
GUI may not be necessary. Fiori provides a modern and user-friendly interface that might
fulfill their needs without the use of the traditional area menu.

Security & roles in SAP S/4HANA:

Keeping the SAP system secure and handling sensitive data is crucial. We manage roles with
PFCG, creating and assigning roles to many users. User permissions are sorted with SU01,
where we create users, give them roles, and adjust as needed.

For keeping an eye on users, roles, and permissions, we use (SUIM) SAP User Information
Management. It helps us monitor and maintain a secure SAP system.

Background Jobs for SAP S/4HANA:

1. Background jobs in SAP can be set up for various tasks like processing, transactions,
or reports. The unique thing about background jobs is that once initiated, users can log
off, and the job continues running on the application server.

2. SM36 helps in creating jobs for transactions or reports, while SM37 is used to keep an
eye on jobs created through the original transaction or SM36.

3. The time it takes for a job to complete depends on the task. Typically, lengthy jobs are
scheduled after office hours or on weekends to avoid disruptions. Once a job finishes,
its log and system messages can be viewed through SM37, and it's crucial to check for
any errors.

4. Jobs can be scheduled for immediate processing, released for immediate action, or set
for later execution. There are six job statuses, each reflecting a different stage in the
job's execution, providing insights into its progress.
 In this SM stands for System Monitor
Background Job Status:

Stage of
Explanation
execution

Planned Job already been defined, but the start condition has not yet been defined

Released The job has been fully defined, including a start condition
 Stage of
Explanation
execution

The start condition of a released job has been met. A job scheduler has put
Ready
the job in line to wait for an available background work process.

The job is currently running. Active jobs can no longer be modified or

Active
deleted.

Finished All steps that make up this job have completed successfully.

The job has terminated :1. Intentional termination by user;2. Error code in
Canceled
job execution

SAP Inbox:

The SAP inbox serves as a tool for sending and receiving messages, especially for handling
system-related issues like job termination or ABAP dump errors during transactions.

Additionally, an express message feature allows administrators to send urgent messages with
a pop-up on users' screens. This is commonly used for critical announcements, such as
system downtime notices during important phases like go-live.

 General Settings for SAP S/4HANA:

SAP General settings customize the system based on norms and business needs. Split into
Client-Specific and Cross-Client, changes are impactful and must be defined cautiously
before production. Key settings cover Country, Currency, Language, and Calendar
configurations, essential for aligning SAP with organizational requirements.

Navigation to General setting via IMG:

IMG Path: SAP NetWeaver -> General settings contains configurations for Country,
Currency, and Calendar settings. Decimal places for currencies and calendar maintenance are
cross-client, affecting the entire system landscape with any changes made.

FRESCO COURSE ID: 727

Architecture and Data Model Overview:

  Architecture of SAP S/4HANA:

SAP S/4HANA is structured with a three-tier architecture, consisting of:

1. Database Layer:
 Holds a structured set of data.
 Data storage and retrieval happen at this layer.
2. Application Layer:
 Contains software designed for specific functions.
 Facilitates processing tasks and supports reporting functionalities.
3. Presentation Layer:
 User interface layer.
 Allows individuals to access the application and perform required tasks.

This three-tier architecture helps organize and optimize the functioning of SAP S/4HANA,
separating data storage, application processing, and user interaction for efficiency and
scalability.

How SAP S/4HANA works:

SAP S/4HANA works with:

1. Front End:
 Users input data through SAP Fiori (SAP UI5) or classical SAP ABAP
interfaces.
2. Data Processing:
 Software programs in the application layer process user-entered data.

3. Database:
 Processed data is updated in database tables, forming the data model structure.

 Data Model in SAP S/4HANA:

In SAP S/4HANA, the Data Model organizes data through logical relationships. It's like a
structure of tables where all SAP data is stored. When users add information, these tables get
updated. In S/4HANA, the data model has three parts: Configuration data, Master data,
and Transaction data. It helps organize and handle different types of information in the
system.

 Configuration data in SAP S/4HANA:

Configuration data in SAP S/4HANA is stored in pre-defined tables. When working with
data, the system reads these configurations from the tables. For example, there are tables for
company details, like legal entities, and plant details, such as manufacturing and sales
locations. It also includes information about currencies and units of measurement used in
transactions. These tables help set up and customize the system according to the
organization's needs.

 Master Data in SAP S/4HANA:

Master data in SAP S/4HANA, which includes information about key business entities, is
stored in predefined tables. When the system processes data, it reads these master data
elements from the tables. Examples of master data tables include:

1. Business Partner Tables:

 These cover information about customers, vendors, and banks.
2. Material Master Tables:
 Depict details about products sold or procured.
3. General Ledger Master Tables:
 Represent specific items like expenses, revenues, assets, or liabilities, such as
electricity expenses.

These tables hold essential information used in day-to-day business operations and
transactions.

 Transactional Data in SAP S/4HANA:

In SAP S/4HANA, everyday business activities are recorded as transaction data, and they're
kept in specific tables. For many transactions, the data is organized into headers and line
items.

When we do transactions, the system reads and uses information from master data,
configuration data, and existing transactions. In earlier versions of SAP S/4HANA,
transaction data was grouped for faster processing during regular tasks and reporting.
Examples of transaction tables are for things like financial documents, material movements,
and sales orders. These tables store details about specific business actions for us to check and
analyze.

 Update of database tables

 A record in a database table can be displayed, edited or a new record can be inserted.
 Each data set is saved in a single or in multiple tables. It implies that when a data is
created, it may be updating multiple tables at the same time.
 It is possible to define custom tables. Program needs to be written to update those
tables either manually or by way of some logic.
 All processing logic and validations are performed via ABAP programs during update
of data into tables.

 A view of database tables:

 SAP also provides structure or view. A structure or view does not store data but reads
the data from tables where the data is stored
 A view can be created to display data from multiple tables and can process data
related to configuration data, master data and transaction data.
 Examples of view
o Display material master list
o Aggregate of sales per product
o Aggregated of expense items for the year
o Display list of purchase orders

How to display database tables in SAP S/4HANA?

To look at tables in SAP S/4HANA:

1. Display Data:
 Use codes like SE16, SE16N, or SE16H.
 SE16 is older with fewer features, while SE16N and SE16H are newer and
better.
2. View Table Structure:
 For the structure of a table, try SE11.
 It shows all the fields and details about each field in a table.

Every table has one or more primary keys, ensuring no duplicate records. Also, all tables
have a "client" field, except for specific cross-client customizing objects. This "client" field
helps organize data for different users in the SAP system.

How to search for configuration transactions based on a configuration table?

To find configuration transactions related to a table in SAP:

 1. Open SM30:
 Go to the SM30 transaction in SAP.
2. Enter Table Name:
 Type in the name of the table you're interested in.
3. Check Transactions:
 Run the transaction, and SM30 will show you a list of configuration
transactions connected to that table.

If you have a custom table, be careful when using SM30 directly to update it. It's best to
follow guidelines and consider the impact on the system.

Fresco Play course Id: 728

Enterprise Structure Overview

 SAP S/4HANA Enterprise Structure overview:

The SAP S/4HANA Enterprise Structure is a blueprint of a company's organization
in the system, comprising units for accounting, product handling, sales, and human
resources. It's a crucial step in SAP setup, involving analysis of the company's
business structure and alignment with SAP's organizational units.

 About Enterprise Structure:

1. Enterprise Structure is made up of a combination of

configuration settings and master data
2. All transactions and processes within SAP S/4HANA always
belongs to the relevant organizational units
3. A sample of enterprise structure is depicted in the picture here.
Individual element is known as organizational
 unit. Combination of all organizational units is known
as Enterprise structure
4. Enterprise structure definition plays a critical role for process
management, reporting and managing security within SAP
S/4HANA
5.
 Key processes for Enterprise Structure in SAP S/4HANA:
1. Finance
2. Logistic Execution
3. Procurement
4. Sales and Distribution

 Client:
1. A client is an independent unit in each system which has its own data set.
2. System landscape of SAP S/4HANA includes multiple systems and
clients which are used for different purposes
3. All organizational units are created within a client except one element. All
configuration related to enterprise structure is client dependent
4. Operating concern is one of the organizational unit which is client independent. It is
a cross client object which means that changes done in one client is reflected in
other client also.

 Company and Company code:

1. Company and company code are two units which are created first while
defining the enterprise structure in SAP S/4HANA
2. Company represents agroup of legal entitieswithin an enterprise for which
SAP implementation is being done
3. For example if SAP S/4HANA is implemented for TATA Consultancy
Services (TCS), company would represent TCS. Company code will be
individual legal entities such as TCS India, TCS USA, TCS France
4. It is always possible to have more than one legal entity for a group company in
same country e.g. TATA Consultancy Services and TATA motors.

 Enterprise Structure for Finance:

In finance, the enterprise structure is crucial for recording all financial transactions,
both for legal and management accounting purposes. The finance processes involve
specific organizational units:
1. Company Code:
 Essential for legal reporting and financial statements.
2. Controlling Area:
 Needed for cost accounting and internal reporting.
3. Operating Concern:
  Plays a key role in profit and loss reporting, being a central organizational
unit.
4. Credit Control Area:
 Manages credit limits for customers, ensuring financial stability.

When designing these organizational units in finance, it's important to consider and
set up reporting parameters for effective financial reporting and analysis.

Company Code:

Company code is the smallest organizational unit of external accounting for which a
complete financial statements can be generated.

 All financial and logistic transactions are done within a legal entity. It means that all
organizational units will be directly or indirectly assigned to a legal entity or a
company code.
 Company code represents are registered legal entity within a company. When a
transaction is carried out between legal entities, financial records are captured in both
of entities as a cross company transaction.
 Company code is assigned to controlling area
 Multiple logistics related to organizational units are assigned to company code such as
plant, sales organization, purchasing organization.
 Definition of company code includes name, address & currency.

 Controlling Area:

Controlling Area is an organizational unit where cost accounting is carried out.

  A controlling area may contain one or more company codes, which can operate in
different currencies, if required.
 The company codes within a controlling area must use the same operational chart of
accounts and fiscal year variant.
 Account assignment objects where cost and revenue is collected are assigned to
controlling area such as cost center which normally represents a department, a sales
order which represents a customer contract or a manufacturing order which depicts a
specific manufacturing lot.

 Operating Concern:

Operating concern represents the entity for which profitability management is

required to be done.

 It is a cross client object which means that any changes done in any one client will be
visible in other clients too.
 Multiple controlling areas can be assigned to the operating concern.
 Definition of operating concern includes characteristics, GL accounts, value fields,
currency definition.

 Credit Control Area:

Credit Control Area is an organizational unit that represents the area where customer
credit is awarded and monitored.

 This organizational unit contains either asingle or several company codes,if credit
control is performed across several company codes.
 One credit control area contains credit control information for each customer.
 Customers can be created in different company codes – the credit control area is
responsible for a given customer depends on which credit control area the company
code is assigned to. Customers that are created in company codes with a common
credit control area are controlled by this one control area for all company codes.
 If the same customer needs a different credit limit if they are assigned to multiple
company codes then multiple credit control areas are required.

 Reporting Dimension (parameters) for Finance:

Reporting dimensions play a crucial role in both external and internal financial
reporting:

1. Legal Requirements:
  Driven by international standards like IFRS, IAS, and local GAAP.
 Involves standard financial statements for legal entities to comply with
regulations.
2. Industry-Specific Needs:
 Addresses requirements unique to industries, such as reporting revenue from a
specific retail store or in a tax-exempt facility.
3. Internal Control and Responsibility:
 Essential for internal controls and responsibility areas within the company.
 Tailored to meet specific needs and unique aspects of the company's
operations.

These reporting dimensions help create a comprehensive picture for both legal compliance
and internal management, accommodating standard practices and company-specific
requirements.

 Segments in SAP represent divisions of a company for external

financial reporting.
 Business area is an additional dimension which can be used for
financial reporting.
 Functional area is used for reporting financial statement based on
cost of sales accounting.

Finance Enterprise Structure:

Enterprise Structure for Logistic Execution:

In business logistics, there are important parts that help move things around, like when
selling, buying, or moving stuff inside the company. The main pieces are:

1. Plant
2. Storage location
3. Shipping point

 places where sales, buying, making things, or handling inventory happen are
called "plants."

Enterprise Structure for Sales:

A Sales Organization is the team that handles selling and distribution in a business. It
manages how products are sold, deals with customer matters, and negotiates sales terms.

 Sales organization is assigned to a company code

 Each Sales Organization has its own master data.
 Acts as the top-level unit in the sales structure.

 A Distribution Channel is the medium which is used to send goods and services to
the customer.

 Division is defined as a product line or grouping of services or materials.

 A product always belongs to only one division.

 Combination of Sales Organization, Distribution Channel and Division is also

known as Sales area.

 Sales office is an organizational unit responsible for sales and distribution within
geographical area.

Enterprise Structure for Purchasing:

  Purchasing organization is responsible for procurement of materials and services
for one or more plants.
 Purchasing group represents a team who is responsible for procurement of
materials and services for a specific category assigned to them.

Enterprise Structure for Human Resource:

Personnel Area: The personnel area is like a special team that takes care of things like
managing people, tracking time, and handling payroll in a company. It's in charge of a
specific area within the company where all these tasks happen.

Personnel Subarea: The personnel subarea is only used for handling employee matters. It
has specific details like pay scale area, pay scale type, and public holiday calendar defined for
it.

Fresco Play Id: 729

Master Data Concepts

There are various types of data which are created and stored in SAP applications

 Configuration data – Data required to customize SAP system as per business

requirement such as company code, currency, plant
 Master Data - Base data of different SAP objects which do not change frequently for
example company code of an employee
 Transaction Data – Data related to SAP objects which is changed very frequently for
example timesheet.

 Master Data:

Master data is a shared set of information crucial for business operations, spanning
applications, processes, and countries, including product lists, customers, and general
ledger accounts.

It serves as the core data necessary for various transactions and processes across
different teams, offering reusable objects for diverse types of transactional processing.

Master data is static, used for both transaction processing and reporting, and is
typically created once. It can be edited, with change history recorded for select master
data.

In complex IT landscapes, master data is usually created centrally and distributed to

multiple applications.

Each master data record has a defined number range, either internal by SAP or
external by the user. It is valid for a specific time and can be locked.

Certain master data can be grouped together for streamlined reporting purposes.

 Uses of Master Data:

Master data plays a crucial role in various transactions. Examples include:

1. Sales Order Entry:

 Customer master and material master are used.
2. Financial Document Entry:
 General ledger account is entered.
3. Purchase Order Creation:
 Vendor master and material master are utilized.
4. Payment to a Bank:
 A pre-defined bank master is used.
5. Production Process:
  Pre-defined bill of material is used.

 Master Data Governance

 Master data governance is a concept which requires central master data

maintenance to ensure data quality
 Data is maintained in a single application and distributed across business
applications used within the enterprise
 SAP provides master data governance (MDG) capabilities via SAP MDG
 Same can be deployed as standalone application which integrates with SAP
S/4HANA or it can be deployed as add-on SAP S/4HANA

Master Data Governance involves validating data using predefined business rules. Examples
include:

1. Credit Rating Assignment:

 Business rule assigns credit ratings based on customer profiles.
2. Material Codification:
 Distinguishes raw materials from finished products through material
codification.
3. GL Account Codification:
 Codifies GL accounts to differentiate between expenses and revenue items.

A centralized team often manages critical enterprise data.

 Business Partner as name indicates is a partner with whom company has certain
business relationship.

 What is Material Master:

Material Master is like a big database that holds all the important info about what a
company buys, makes, stores, and sells. It's a central hub that brings together details
from different parts of the company, like engineering, manufacturing, sales, and more.
Each product or material in this database has a special code to identify it, and in SAP
S/4HANA, this code can be up to 40 characters long.

Uses of Material Master:

Material Master is vital for various business functions:

1. Material Types:
 Represents raw materials, finished products, and more.
2. Procurement and Sales:
 Used in procurement cycles and sales orders.
3. Manufacturing:
 Used in creating finished or semi-finished products.
4. Logistics Module:
 Essential for logistics functions with key parameters.
5. Financial Analysis:
 Used for tasks like material valuation and quantity analysis.

Structure of Master Data:

 Material master information is organized hierarchically according to organizational

level.
 Organizing materials hierarchically allows easy management of information across an
enterprise and prevents redundant storage of material data.

"Redundant" refers to something that is unnecessarily repeated or duplicated.

Service Master:
A Service Master is important for organizations that need services like maintenance or
professional assistance, alongside buying materials for manufacturing and selling.

Procurement related master data:

 Procurement related master data includes all master data which is relevant for
procurement of materials and services from external vendor including inter-company
transactions.
 Following master data in SAP S/4HANA are required for procurement processes
o Purchasing info record – (relationship between material and vendor.)
o Source list – (list of available vendors from which would procure materials.)
o Condition record – (A condition record in procurement is a price record for
materials, showing how much it costs to buy or sell.)

 Sales related Master Data:

 Sales-related master data involves information essential for selling materials
and services, including inter-company transactions. In SAP S/4HANA, key master
data for sales processes includes condition records and credit master.

 Condition record or Pricing record is a master in sale which contains

price of the material at which it can be procured or sold.

 Credit Master:
The Credit Master helps organizations set credit limits for customers, reducing
credit risk. Limits can be managed centrally or at the legal entity level. Credit checks
during sales prevent orders exceeding the limit. If the limit is surpassed, sales
documents or deliveries can be blocked until the product is delivered.

 Manufacturing related Master data:

 Manufacturing related master data includes all master data which is relevant
for manufacturing of materials and services from external vendor including inter-
company transactions.
 Following master data in SAP S/4HANA are required for manufacturing
processes
o Work center
o Bill of material
o Routing & recipe
o Production version

 Finance related Master data:

 Finance related master data includes all master data which is relevant for
financial transactions processing of the organization.

 Following master data in SAP S/4HANA are required for finance processes
o GL account (General Ledger)
o Profit center
o Bank master
o Asset master
o Cost center
o Internal order
o Business process
o Activity type -Statistical key figure

 General Ledger:
 A General Ledger (GL) Account is like a master record for keeping track of
money stuff. It covers different types of accounts for things like profits, losses, and costs,
and when you put them all together, it's called a chart of accounts. This chart can be used
by multiple company codes. The GL account has two parts: one that's common for all
companies and another specific to each company. There's also a part for controlling costs
that's shared by all the companies.

 Human Resource related Master Data:

o Human resource related master data includes all master data which is relevant
for workforce management.
o Each employee of the organization is represented by an employee master.

Fresco Play Course Id: 730

SAP S/4HANA Authorization Concepts Overview

Basic security needs of an ERP application

 Prevention of unauthorized use of an application and the associated data is the

primary objective of the security layer of application.
 It could be the combination of hardware, software and procedural measures (manual
and automated)

Typical security software applications:

 Application Firewall
 Spyware Detectors
 Biometric Authentication

Typical security hardware

 Hubs and Routers

 Levels of an application security:

1. Application Access:
 Controls overall access to applications like S/4HANA.
2. Functionality Access:
 Restricts users to specific functionalities within an app (e.g., Purchasing in
S/4HANA).
3. Activity Access (e.g., Display, Write, Delete):
 Governs specific actions users can perform, such as reading but not
creating purchase orders.
 4. Data Object Access:
 Limits access to specific data objects (e.g., G/L accounts).
5. Regional/Organizational Access:
 Manages access based on regions or organizational units (e.g., users can
view US data but not Europe).

Overview of SAP Security & Authorization Concepts

 SAP Authorization Types:

 General Authorization (Task-based Approach):

 Involves granting permissions based on specific tasks or activities.
 Focuses on defining access according to the user's functional responsibilities.
 Structural Authorization (Job-based Approach):
 Involves setting up authorizations based on the user's role or position in the
organization.
 Defines access privileges according to the user's job functions.

Both authorization types can be configured to control system users' access to data and are
essential for effective SAP implementation.

 SAP User Types:

1. Dialog User (A):

 For interactive users, including Internet users.
 Can change passwords and supports multiple logons.
 Password expiration checks are performed.
2. System User (B):
 For background processing and internal RFC calls.
 No dialog logon allowed; password changes handled by the user
administrator.
 3. Communication User (C):
 For dialog-free communication between systems (e.g., RFC users for ALE,
Workflow).
 Dialog logon not allowed; password checks depend on logon method; no
password change requests.
4. Service User (S):
 A dialog user available for a larger, anonymous user group.
 Limited authorizations; used for anonymous system accesses (e.g., ITS
service).
 Allows continuation of an anonymous session as a person-related session
with a dialog user.
5. Reference User (L):
 For general, non-person-related users.
 Allows assignment of identical authorizations (e.g., for Internet users
created with transactions SU01).
 Cannot log on to the system directly.

 User Administration

SAP Systems Admin are responsible for monitoring and maintaining the ongoing
reliability, performance, management, and support of SAP application. They are also
responsible for User Administration.

Typical User Administration Activities :

 Create / Amend User Accounts in different SAP systems

 Lock / Unlock accounts
 Role Assignments and Role Removals to and from the users
 Password reset
 Maintenance of profiles

 User Information System – Transaction SUIM:

SUIM serves as a comprehensive tool for administrators to gather specific
information about users, roles, and authorizations within the SAP system.

 SAP HANA Security - Introduction

Fresco Play Course Id: 732

SAP S/4HANA Project Overview

 An overview of Project Management methodology:

 A project consists of tasks aimed at achieving a specific outcome or business

objective.
 Project Management is the process of creating, organizing, and executing a plan to
achieve these objectives.

 Project Methodology:
 A model for designing, planning, and implementing projects.
 Different methodologies for different projects.
 In SAP projects, popular ones include:
 Waterfall: Sequential and structured.
 Agile: Flexible and adaptive.
Choosing the right methodology depends on the project's nature and requirements.

 Release Management Overview:

Release Management:

 Objective: Safeguard the live environment while facilitating controlled

implementation of Business As Usual (BAU) changes and enhancements.

Business As Usual (BAU):

 Regular introduction of various operations into existing production environments

without disrupting current business processes.
 BAU ensures ongoing, routine operations to maintain and improve systems without
causing major disruptions.

 Service Transition Planning & Support

  SAP Project Management Methodology

SAP prescribes the use of following Project Management methodologies for projects
implementing its products.

 ASAP Methodology This is the most commonly used Project Management

methodology in SAP. This is based on the Waterfall Method that is described in the
previous unit.
 SAP Activate SAP is encouraging its partners and customers to adopt SAP Activate
Project Management methodology for all new projects, especially for SAP S/4 HANA
implementations. This method is based on the Agile Method of Project Management
that is described in the previous unit.

 Types of SAP Projects:

1. Implementation:
 Greenfield: Brand new installation of SAP modules.
 Transformation: Migration from a legacy IT system to SAP ERP.
 Roll Out: Re-installing SAP modules in other locations or business units.
2. Change Management:
 Enhancement Projects: Addressing new requirements to improve existing
solutions due to changes in business processes, automation needs, or legal
requirements.
3. Upgrade:
 Periodically implementing changes, bug fixes, and new capabilities in the
latest SAP versions.
 Upgrade Projects: Implementation of the latest SAP version for enhanced
functionality.
4. Application Maintenance Service:
 Production Support: Ongoing maintenance for SAP applications, including
incident management, backups, and monitoring for smooth operation.

SAP Project: Implementation (In this the we are applying SAP to an legacy environment)
Step 1
Landscape Architecture and Setup:

In SAP implementation, the system landscape is crucial and typically involves multiple
systems and clients serving different purposes. The standard landscape includes sandbox,
development, quality, and production systems. Strict adherence to rules is essential while
working on the customer landscape. Below is a sample SAP landscape:

System Description
Sandbox Testing and experimentation
Development System for application development
Quality Testing and quality assurance
Production Live operational environment

This structured landscape ensures a systematic and controlled approach throughout the
implementation process.

SAP Clients Overview:

In SAP, clients are independent units within a system, each with its own data set. Multiple
clients meet project needs, but considerations include resource usage (memory, database
space). Administration is vital for user access and authorizations.

Step 2 Core Enablement team:

The Core Enablement team has special access in SAP like super users and is crucial in
making things work. They help out, make things better, and are really important during big
SAP upgrades or projects. These guys write down how things should work and are like the
communication link between the business and tech teams. They have unique skills and are
super respected in the world of SAP.

Step 3 Solution workshop:

 Solution workshop is also known as "Fit-to-Standard" workshop
 Fit-to-Standard workshops are held with customer subject matter experts in an
efficient way to reduce backtracking later in the implementation and to enable the
customer on the execution of the scenarios.
 Project team is focused and have an open mind to understand how the preconfigured
and predefined processes offered in SAP Best practices can simplify the customer’s
existing processes
 Business processes aligning to the solution are standardized to eliminate major
process mapping and design so the team can focus on value added services.

Step 4 Fit-gap Analysis:

After the Solution Workshop, we dive into Fit-Gap Analysis. It's like figuring out how to
make the new solution fit with the way the customer already does things. We explore using
standard SAP practices or connecting different parts. If there are still gaps, we decide if it's
something upcoming, if there's already a solution, or if we need to do some extra work. This
whole process is called Fit-Gap Analysis.

Step 5 Delta Design:

After spotting and ranking gaps in the Fit-Gap Analysis, the project team, alongside the
customer:

1. Envisions how to fill those gaps in the design.

2. Collects needs based on feedback and seeks early approval.
3. Standardizes the solution design to keep modifications minimal.

This step is called Delta Design, ensuring a clear plan for addressing identified gaps while
maintaining simplicity.

Step 6 Configuration and Build:

Configuration is like customizing the SAP system to fit the organization's needs. It kicks off
by setting up the company structure. Different functional areas in SAP have their own parts
of the company structure, which need defining and linking.

After that, we define master data types and decide how they should look. Then, we configure
transactions to mirror business processes in the system. We can even tweak how each screen
looks and works. This whole process is known as Configuration and Build.

Step 7 : Cut over

 Cutover activities are carried out before Go-live of the project.

 After the project is implemented some data needs to be uploaded to the system.
 This activity involves- Master data upload for objects like customer masters including
partner function assignment, customer material info, pricing, outputs and credit
masters.

Step 8 : Data Migration

 If the customer is going to implement SAP by replacing the source (e.g Legacy)
system the is to load the relevant business data currently residing in the source
system into the appropriate SAP modules. This is called Data Migration.
 Data migration is the process of extraction, transformation & loading of data into SAP
system.
 This data loaded into SAP system needs to be validated with the source data.

Step 9: Testing

Testing in SAP implementation projects has three key steps:

1. Test Planning:
 Gather functional requirements for system and application testing.
 Develop test cases for both manual and automation testing.
2. Test System Setup:
 Prepare the test environment to execute the test cases.
3. Test Execution and Evaluation:
 Perform regression testing for critical processes.
 Conduct unit testing during this stage to ensure everything works smoothly.

These steps ensure a comprehensive and thorough testing process to validate the SAP
implementation.
Step 10: Training

The project team takes the lead in training, covering:

 Updating others on recent changes.

 Training new hires.
 Conducting one-on-one sessions and presenting in larger classrooms.

This step ensures everyone is well-prepared for the changes and additions made during the
SAP implementation.

Step 11: Business validation and user acceptance:

User Acceptance Testing is led by business end users to validate if the system aligns with
their functional needs. This ensures the system is user-friendly and meets expectations before
transitioning to the production environment. UAT is the final testing phase before the
software goes live.

Step 12: Documentation

Project documentation is crucial for project management, ensuring speed and stakeholder
awareness. Key documents in each phase include:

 Prepare Phase: Master Plan

 Explore Phase: Business Charter
 Realize Phase: Deployment Plan, Test, Technical, and Functional Documents
 Deploy Phase: User Manual, Transition/Rollout Plan, Handover Documents

These documents track progress and facilitate effective communication throughout the
project.

Step 13: Release and Go-live

In this phase, the goal is to shift the built solution from a project-oriented, pre-production
setting to the live production environment. The project team emphasizes supporting the
migration of master data and transaction data to ensure a successful transition.

Step 14: Transition to Support

After Go-Live, users often seek additional support and guidance, causing potential delays. In
this phase:
  Users log issues in an ITSM tool, categorized as User Awareness, Master Data,
Configuration, Hardware, etc.
 Running the tool a few days after Go-Live helps address reported issues under User
Awareness or Master Data categories, leading to timely resolutions. This ensures a
smooth transition to ongoing support.

Step 15: Closure

Ensuring end users are confident and comfortable with the new SAP solution is vital for
overall project success. Once high-quality post go-live support has been provided, the project
can be officially closed.

SAP Project: Change Management (Upgrades and Enhancements)

Change Management in SAP involves smaller projects for enhancing or upgrading existing
systems. While not as complex as implementations, the steps are similar. Depending on the
customer's setup, it might follow an 'Application Maintenance Service project' approach for
simplicity.

Most common steps for SAP Change Management projects

The major difference between implementation and change management projects is in the
initial steps - highlighted in picture.

Common Steps for SAP Change Management Projects

Step 1: Requirement Analysis

 For enhancement projects, analyze business needs.

  For upgrades, conduct a less detailed analysis for a technical system-level upgrade.
 Submit a feasibility report and establish high-level effort estimates.

Step 2: Impact Assessment

 Study the potential impact of the proposed solution on the existing system.
 Evaluate pros and cons before initiating the build.
 Ensure the proposed solution aligns with and doesn't disrupt existing processes.

Step 3: Design

 After thorough impact assessment, create high-level, mid-level, and low-level designs
as needed for the project.

SAP Application Maintenance Services (AMS) Overview

SAP AMS involves processes and methodologies for maintaining and managing
enterprise SAP environments. Key service components include:

1. Incident Management: Addressing and resolving issues promptly.

2. Change Management: Implementing changes efficiently and minimizing
disruptions.
3. Problem Management: Identifying and addressing root causes to prevent
recurring issues.
4. Release Management: Efficiently managing updates and new releases.
5. Knowledge Management: Building and sharing knowledge to enhance system
understanding.
6. Service Transition Planning & Support: Planning and supporting smooth
transitions for new services or changes.