1

SAP Basis
What is sap:

 SAP stands for Systems, Applications, and Products in data processing

 It is a ERP package, which integrates all sap systems to get real time data.
 SAP system consist of a number of fully integrated modules which covers
virtually every Aspect of business management.
 SAP is a software as well as name of the company.

ERP:

 ERP stands for Enterprise resource planning.

 ERP is a business management software.
 An ERP is the best option for demonstrating value by providing real time
information to all employees of a corporation across departments.

SAP PRODUCTS: NON-SAP ERP PRODUCTS:

1. APPLE WORKDAY
2. BENZ ZOHO
3. BMW ORACLE NET SUITE
4. NESTLE MICROSOFT DYNAMICS
5. INDIAN OIL

SAP Versions

1. SAP R/1 (1972)

 SAP's first version with a single-tier architecture for real-time processing.

 Focused on basic financial accounting and materials management.

SAP BASIS RAJESH

2

2. SAP R/2 (1979)

 Introduced multi-tier architecture and was designed for mainframe

computers.
 Expanded functionalities for finance and materials management.

3. SAP R/3 (1992)

 Shifted to a client-server model, enabling more scalability and flexibility.

 Introduced modular structure for integrating various business processes.

4. SAP ERP 6.0 (2006)

 A modernized version of R/3 with enhanced usability and new features.

 Integrated with SAP NetWeaver, offering improved web-based
applications.

5. SAP S/4HANA (2015)

 Built on the in-memory SAP HANA database for real-time data

processing.
 Simplified data models and a modern user interface (Fiori).

6. SAP S/4HANA Cloud (2017)

 Cloud-based version of S/4HANA for faster updates and scalability.

 Focused on continuous innovation with flexible cloud deployment.

7. SAP Business Technology Platform (BTP) (2020)

 A unified platform for data management, analytics, and application

integration.
 Supports digital transformation with AI, machine learning, and
automation.

SAP BASIS RAJESH

3

8. SAP S/4HANA 2020 (2020)

 Enhanced with industry-specific solutions and advanced automation.

 Improved cloud integration and intelligent capabilities for business
processes.

9. SAP S/4HANA 2021 (2021)

 Focused on deeper AI capabilities, predictive analytics, and

sustainability.
 Advanced user experiences and enhanced business functions.

10. SAP S/4HANA 2022 (2022)

 Latest release with more robust cloud-native solutions and automation.

 Focused on real-time insights, automation, and greater integration with
cloud technologies.

SAP MODULES:

SAP (Systems, Applications, and Products in Data Processing) ERP consists of

multiple modules designed to manage various business processes. These
modules are categorized into functional and technical types.

1. Functional Modules (Business Process-Oriented)

These modules focus on different business areas and are widely used in
industries.

SAP BASIS RAJESH

4

Core SAP ERP Modules:

 SAP FI (Financial Accounting) – Manages financial transactions,

reporting, and accounting.
 SAP CO (Controlling) – Focuses on cost control, planning, and
budgeting.
 SAP MM (Materials Management) – Handles procurement, inventory,
and supply chain.
 SAP SD (Sales and Distribution) – Manages sales orders, billing, and
shipping.
 SAP PP (Production Planning) – Handles manufacturing, planning, and
production.
 SAP QM (Quality Management) – Ensures product quality and
compliance.
 SAP PM (Plant Maintenance) – Manages maintenance activities and
equipment.
 SAP HCM (Human Capital Management) – Manages HR functions like
payroll, recruitment, and performance.

2. Technical Modules (Development & Administration)

These modules are used for customization, integration, and system

administration.

 SAP ABAP (Advanced Business Application Programming) –

Programming language for SAP customization.
 SAP Basis – Manages system administration, security, and performance.
 SAP NetWeaver – Integration platform for SAP and non-SAP systems.
 SAP HANA (High-Performance Analytic Appliance) – In-memory
database for fast processing.

SAP BASIS RAJESH

5

SAP R/3 Architecture :

SAP R/3 is a three-tier architecture that consists of three main layers:

1. Presentation Layer
2. Application Layer
3. Database Layer

This architecture provides scalability, flexibility, and security for business

processes.

1. Presentation Layer (User Interface)

 The front-end of the SAP system where users interact.

 It sends user requests to the Application Layer and displays the results.

2. Application Layer (Processing Layer)

 This is the heart of SAP R/3, where all business logic and processes are
executed.
 It consists of one or multiple application servers that handle requests
from the Presentation Layer.
 Contains various SAP Work Processes, such as:
o Dialog – Handles user input and transactions.
o Update – Manages database updates.
o Enqueue – Handles lock mechanisms to prevent data conflicts.
o Background – Executes scheduled jobs.
o Spool – Manages print requests.
 Dispatcher: Manages work processes and distributes user requests.
 Message Server: Handles communication between multiple application
servers.

3. Database Layer (Data Storage)

 Stores all business data, configurations, and transactions.

SAP BASIS RAJESH
6

 Uses relational databases like SAP HANA, Oracle, SQL Server, IBM
DB2, etc.
 The Database Server communicates with the Application Layer for
read/write operations.

SAP Landscape

SAP Landscape refers to the arrangement of SAP servers in an organization

for development, testing, and production purposes. It ensures a smooth
transition of changes from development to live production while maintaining
stability.

Typical SAP Landscape (3-System Architecture)

The most common SAP landscape consists of three environments:

1. Development System (DEV)

a. Used for coding, customization, and initial configuration.
b. Developers write and test the code.
c. Includes multiple clients for different purposes:
i. Sandbox Client – For experimenting and testing.
ii. Customization Client – For configurations.
iii. Development Client – For actual coding.
2. Quality Assurance System (QAS)
a. Used for testing and validation.
b. Ensures that developments work correctly before moving to
production.

3. Includes:

SAP BASIS RAJESH

7

a. Functional Testing – Checking if business processes work.

b. Performance Testing – Checking system speed and load handling.
c. User Acceptance Testing (UAT) – End users test and approve
changes.
4. Production System (PRD)
a. Live system used by end users for daily business operations.
b. No direct development or testing is done here.
c. Only approved and tested changes are transported from QAS to PRD.

Extended SAP Landscape (4-System or 5-System Architecture)

Larger organizations may have additional systems to further separate

development, testing, and production:

4-System Landscape

 DEV → TST (Testing System) → QAS → PRD

 Testing is done in TST, and quality checks in QAS before going live.

5-System Landscape

 SANDBOX → DEV → QAS→ PRE-PROD → PRD

 SANDBOX --- It’s like playground
 Pre-Production (PRE-PROD) is used to mimic real-world scenarios
before moving to PRD

FIXES IN SAP: In SAP, fixes are applied to resolve bugs, improve system stability,
and enhance functionality. Fixes are also called snotes.
 Number of fixes is called patch
 Number of patches is called support packs
 The number of support packs is called enhancement packs.
SAP BASIS RAJESH
8

Drawbacks of HDD (Hard Disk Drive)

HDDs have been widely used for data storage, but they come with several
limitations compared to modern SSDs (Solid State Drives). Here are the key
drawbacks:

 No encryption, data is not encrypted in HDD.

 It will take more time.
 Data is not stored in ordered form it is stored in scattered way.

1. Slower Speed

 HDDs have moving mechanical parts, which makes them significantly

slower than SSDs.

2. High Power Consumption

 Requires more power to spin the platters and move the read/write head.
 This results in shorter battery life for laptops compared to SSDs

3. Larger and Heavier

 HDDs are bulkier and heavier than SSDs.

 Not ideal for ultra-thin laptops and compact devices.

4. More Heat Generation

 The spinning disk and motor generate more heat, affecting overall
system cooling.
 SSDs produce much less heat in comparison.

SAP BASIS RAJESH

9

Importance of a Database

1.Efficient Data Management

 Organizes large amounts of data in a structured manner.

 Reduces data redundancy and improves efficiency.

2.Fast Data Access & Retrieval

 Allows quick search and retrieval of information using queries (e.g.,

SQL).
 Improves business decision-making by providing real-time insights.

3.Security & Integrity

 Protects sensitive data with authentication, authorization, and

encryption.
 Ensures accuracy and consistency through constraints and validation
rules.

4. Multi-User Access & Scalability

 Supports multiple users accessing data simultaneously.

 Scales to handle large volumes of data as businesses grow.

5. Backup & Recovery

 Prevents data loss with automated backups and recovery options.

 Ensures business continuity in case of system failures.

SAP BASIS RAJESH

10

Starting and stopping Sequence of an SAP System

Step-by-Step SAP Start Process:

Step 1: Start the Database Server (SAP HANA, Oracle, etc.)

 Begin by starting the database server (e.g., SAP HANA, Oracle, or SQL
Server).
 Ensure that the database starts without any errors before proceeding to
the next step.

Step 2: Start the SAP Central Services (SCS/ASCS) Instance

 Next, start the SAP Central Services (SCS) or ABAP/Java Central Services (ASCS)
instance.
 This instance manages the message server and enqueue server, which
are crucial for the SAP system’s operation.

Step 3: Start the SAP Primary Application Servers (PAS)

 After the central services are running, start the Primary Application
Server (PAS).
 This will allow the core SAP application processes to run and handle user
requests.

Step 4: Start the SAP Additional Application Servers (AAS)

 Finally, start any Additional Application Servers (AAS) in the SAP

landscape.

SAP BASIS RAJESH

11

 These servers can be started after the primary application server is up,
and they will support additional workload distribution.

Step-by-Step SAP Shutdown Process:

Step 1: Stop SAP Additional Application Servers (AAS)

 First, shut down all the Additional Application Servers (AAS) that are part
of the SAP landscape.
 This can be done through the SAP management interface or command
line (disp+work process).

Step 2: Stop SAP Primary Application Servers (PAS)

 Next, stop the Primary Application Server (PAS), which handles the main
SAP application processes.
 The shutdown can be initiated using the same interface or command line
commands.

Step 3: Stop the SAP Central Services (SCS/ASCS) Instance

 Stop the SAP Central Services (SCS) or ABAP/Java Central Services

(ASCS) instance.
 This instance manages message and enqueue services for the system
and should be stopped after the application servers.

SAP BASIS RAJESH

12

Step 4: Stop the Database Server (SAP HANA, Oracle, etc.)

 Finally, shut down the database server (e.g., SAP HANA, Oracle, or SQL
Server).
 The database should be properly stopped to avoid data corruption and
ensure consistency.

What is High Availability (HA) in SAP?

1. High Availability for SAP Application Server

SAP Central Services (SCS/ASCS) Redundancy

 ASCS (ABAP Central Services) and SCS (SAP Central Services) manage
locks and message communication.
 Instead of a single application server, run multiple instances.
 If one fails, the other handles user requests automatically. SAP Web
Dispatcher for Load Balancing
 Distributes user requests between multiple application servers,
preventing overload.

2. High Availability for SAP Database

Database Clustering (Active-Passive / Active-Active)

 SAP HANA System Replication allows a standby database to take over in

case of failure.

Automated Failover Mechanism

 If the primary database goes down, SAP automatically switches to the
secondary database.

Backup and Restore Strategy

 Regular database backups and replication ensure data safety.

SAP BASIS RAJESH
13

ABAP System Architecture (3-Tier Architecture)

FIG. ABAP Architecture

ASCS – ABAP SAP Central Services

MS – Message Server ES – Enqueue Server

SAP BASIS RAJESH

14

Step-by-Step Process Flow in SAP ABAP Architecture (Based on

the Diagram)

Scenario: Creating and Saving a Sales Order in SAP (Transaction VA01)

Step 1: User Interaction via SAP GUI

 A sales representative opens the SAP GUI and starts transaction VA01
(Create Sales Order).

 The request is sent to the Queue Buffer, which temporarily holds the
request before further processing.

Step 2: Request Handling by Dispatcher

 The Dispatcher receives the request and determines which work

process should handle it.

 It assigns the request to a Dialog Work Process (D), as this is an

interactive user transaction.

Step 3: Processing in Work Processes

 The Dialog Work Process checks the User Buffer for any existing
cached data related to the sales order or user session.

 If required, the work process accesses the Public Buffer for shared data
(e.g., customer master data, material pricing).

SAP BASIS RAJESH

15

Step 4: Database Query Execution

 If the requested data is not in the buffer, the system forwards the request
to the ABAP/SQL Interpreter.

 The interpreter translates the ABAP request into an SQL query.

 The DB Client sends this query to the underlying Database.

 The database retrieves relevant sales order data and sends it back to the
DB Client, which forwards it to the Public Buffer and the Work Process.

Step 5: Data Display and User Actions

 The processed data is sent back through the Dispatcher to the SAP GUI,
displaying order details.

 The user fills in the required sales order details (customer, products,
pricing, delivery details).

 After verifying the details, the user clicks Save to finalize the order.

Step 6: Database Update

 The Update Work Process (V) is triggered to store the order permanently
in the database.

 The system ensures data consistency by locking certain tables during the
update.

 Once the update is complete, the lock is released.

SAP BASIS RAJESH

16

Step 7: Output Processing (Optional: Printing the Sales Order)

 If the user chooses to print the sales order confirmation, the request is
forwarded to the Spool Work Process (S).

 The spool process queues the print job and sends it to the designated
printer.

Step 8: Completion and User Notification

 The system confirms successful sales order creation and displays an

order number in SAP GUI.

 The transaction is completed, and the SAP GUI is ready for the next
request.

SAP ABAP systems are based on a 3-tier architecture, consisting of:

1. Presentation Layer (User Interface)

 Handles user interactions via SAP GUI

 Communicates with the Application Server to process user requests.

2. Application Layer (Processing Layer)

 The core of SAP ABAP where business logic is executed.

 Consists of SAP NetWeaver Application Server (AS ABAP).
 Handles work processes (Dialog, Update, Background, Enqueue,
Spool, Gateway, etc.).

SAP BASIS RAJESH

17

 Uses Dispatcher to assign user requests to available Work Processes.

3. Database Layer (Data Storage)

 Stores business data, programs, and configuration settings.

 Uses databases like SAP HANA, Oracle, or MS SQL Server.

Dispatcher:

The Dispatcher in SAP plays a crucial role in ensuring that user requests are
efficiently processed and distributed to the appropriate work processes. It
manages the system's workload by balancing tasks across available resources
and queuing requests when necessary. Proper configuration, monitoring, and
tuning of the dispatcher are vital for ensuring smooth performance, particularly
in large SAP systems with high transaction volumes

Message server:

In SAP, the Message Server is a critical component that acts as a

communication hub between different SAP instances (application servers) in a
distributed SAP landscape. It facilitates internal communication and provides
a connection point for the different components of an SAP system, including
the SAP GUI, background jobs, and other services.

Enqueue server:

In SAP, the Enqueue Server is a critical component responsible for managing

locks on data objects to maintain consistency and prevent data corruption in
a multi-user environment. It ensures that concurrent transactions do not
modify the same data simultaneously, which could lead to inconsistent results.
The Enqueue Server handles the locking mechanism for all applications within
the SAP system.

SAP BASIS RAJESH

18

Work Processes (WPs):

SAP uses different types of work processes for handling different tasks

Dialogue work processes:

In SAP, Dialogue Work Processes (WP) are responsible for handling

interactive user requests, also known as dialog steps, in a system. These work
processes are part of the AS (Application Server) and are essential for
managing user interactions with the SAP system, like logging in, executing
transactions, and processing other interactive tasks.

Background work processes:

In SAP, Background Work Processes (WP) are responsible for handling tasks
that do not require user interaction. These tasks are typically long-running
processes that are executed in the background, such as batch jobs, report
generation, data processing, or updates. Background work processes are
important for efficiently managing system resources and ensuring that system
activities, which do not involve direct user interaction, are executed properly.

Update work processes:

In SAP, Update Work Processes (WP) are responsible for handling update
tasks that are crucial for maintaining the consistency of the database during
transaction processing. These work processes manage the execution of
database updates, including data modifications, insertions, and deletions,
ensuring that changes made during a transaction are properly reflected in the
database.

Spool work processes:

In SAP, Spool Work Processes (WP) are responsible for managing the creation
and management of output requests, such as print jobs, PDF documents, or
other types of outputs. When a user or system generates output (e.g., printing
SAP BASIS RAJESH
19

a report or generating a document), the Spool Work Process handles the task
of processing the output request, formatting it, and sending it to the
appropriate destination (e.g., printer, file, or email).

Gateway work processes:

In SAP, the Gateway Work Process (WP) is a type of work process responsible
for handling communication between the SAP system and external systems,
particularly when using Remote Function Calls (RFC). The Gateway WP plays
a key role in enabling SAP systems to interact with other systems, such as other
SAP systems, third-party applications, or external web services.

Task Handler: In SAP's system architecture, the Task Handler plays a

crucial role within the work process framework. It coordinates various
activities during a user's interaction with the system, ensuring efficient
processing and management of user sessions.

Database Client:

In the context of SAP systems, a Database (DB) Client refers to software

components that facilitate communication between applications and
databases, enabling data exchange and management. These clients provide
the necessary drivers and utilities to connect to various databases, such as
SAP HANA, MaxDB, or other relational database management systems
(RDBMS).

SYSTEM MONITORING:

SAP system monitoring is crucial for maintaining system performance, stability,

and security. It involves tracking system health, checking logs, and
troubleshooting issues.

A. System Performance Monitoring

Monitors CPU, memory, and workload.

SAP BASIS RAJESH
20

 ST06 – OS Monitoring (CPU, RAM, disk usage)

 ST02 – Buffer and Memory Monitoring
 ST03N – Workload Analysis (Performance statistics)
 AL12 – Shared Memory Monitoring

B. Database Monitoring

Checks database performance and space usage.

 DB02 – Database Performance & Tablespace

 DB12 – Backup Logs
 DB13 – Database Job Scheduling
 ST04 – Database Performance Overview

C. Work Process & Job Monitoring

Tracks SAP background jobs and processes.

 SM50 – Work Process Overview (ABAP Instance)

 SM66 – Global Work Process Overview
 SM37 – Background Job Monitoring
 SM21 – System Log Analysis

D. User & Security Monitoring

Manages users, authorizations, and security logs.

 SU01 – User Management

 SUIM – User Information System (Roles & Authorizations)
 RSAUDITC_LOG_DISPLAY – Security Audit Log
 SM19 / SM20 – Security Audit Logs

E. Transport & Change Monitoring

Handles SAP system changes and transports.

SAP BASIS RAJESH
21

 STMS – Transport Management System

 SE09 / SE10 – Transport Organizer

F. Application Server Monitoring

Monitors SAP instances and application health.

 SM51 – Active SAP Instances

 SMMS – Message Server Monitoring

G. ABAP Dump & Update Monitoring

Checks for ABAP errors and updates.

 ST22 – ABAP Dump Analysis

 SM13 – Update Requests Monitoring

BACKGROUND JOBS

Creating & Scheduling a Background Job (SM36)

Steps:

1. Open Transaction SM36

2. Enter Job Name (e.g., Z_MY_JOB)
3. Define Job Class:
a. A (High Priority)
b. B (Medium Priority)
c. C (Low Priority – Default)
4. Assign Step (Program to Execute)
5. Choose Start Condition:
a. Immediate – Runs as soon as possible
b. Date/Time – Schedules job for later
c. After Event – Triggers job based on an event
d. After Job – Runs after another job completes
SAP BASIS RAJESH
22

6. Save and Activate the Job

3. Monitoring Background Jobs (SM37)

Steps:

1. Open Transaction SM37

2. Enter Job Name (or use * for all jobs)
3. Select Job Status:
a. Scheduled – Job is planned but not started
b. Released – Job is ready for execution
c. Ready – Job is waiting for a free work process
d. Active – Job is currently running
e. Finished – Job completed successfully
f. Canceled – Job failed (Needs investigation)
4. Click Execute (F8)
5. Check Job Logs and Spool Requests for results

What is Unicode in SAP?

 Unicode is a universal character encoding standard that supports

multiple languages and scripts.
 In SAP, Unicode ensures that all characters, including special symbols
and different language scripts, are correctly processed and displayed
across systems.
 SAP introduced Unicode-compliant systems to replace older non-
Unicode systems, allowing global businesses to handle multilingual
data efficiently.

SAP BASIS RAJESH

23

USER CREATION:

How to Create a User in SAP (SU01)

Steps to Create a New User:

1. Open SU01 (User Maintenance).

2. Enter the User ID (e.g., TESTUSER1).
3. Click Create (F8).
4. Fill in the required details under the "Address" tab:
a. Last Name (mandatory)
b. First Name (optional)
c. Email Address (if needed)
5. Go to the "Logon Data" tab:
a. Set User Type (Dialog, System, Communication, etc.)
b. Define Initial Password (ensure it meets policy requirements)
c. Select Default Language (EN for English, DE for German, etc.)
6. Assign Roles & Authorizations in the "Roles" tab:
a. Click Add (F4) and assign the required roles (e.g., SAP_ALL,
FI_USER, etc.).
7. Set Profiles (optional) in the "Profiles" tab (e.g., SAP_NEW, SAP_ALL).
8. Click Save (Ctrl+S) to create the user.

Mass User Creation (SU10)

To create multiple users at once:

1. Open T-Code SU10.

2. Click Users → New Entries.
3. Enter multiple user IDs.
4. Assign roles, passwords, and user types.
5. Save and activate users.

SAP BASIS RAJESH

24

SAP NETWEAVER

 A user logs in to SAP Portal (Java-based UI).

 The request was received by the Web Dispatcher.
 The Web Dispatcher forwards the request to the Message Server, which
assigns the best available Java Server Node.
 The assigned Server Node executes the request using Java Work
Processes.
 The work process retrieves necessary data from the Database.
 The Enqueue Server ensures that data is locked correctly to prevent
inconsistencies
 Once processing is complete, the Server Node sends the response back
through the Dispatcher → Message Server → Web Dispatcher → User
Browser or SAP GUI.

SCS (SAP Central Services)

SAP Central Services (SCS) is a core component in SAP NetWeaver Java,

responsible for managing locks, messaging, and synchronization across
multiple Java application servers.

1. Enqueue server - H0andles locking mechanisms to prevent data

inconsistencies in multi-user
2. Message Server - Facilitates communication between application
servers and handles load balancing for incoming requests.

SAP BASIS RAJESH

25

PAS (Primary Application Server)

The Primary Application Server (PAS) is the main instance in an SAP
NetWeaver Java system where applications run.
In java system the PAS have Two main Services

 Jstart.exe - is a core process responsible for starting and managing Java

server nodes within the Primary Application Server (PAS) and Additional
Application Servers (AAS).
 Igswd.exe - It is a monitoring and control process for the SAP Internet
Graphics Server (IGS), which is used to generate graphical content such
as charts, maps, and other visual elements in SAP applications.

Important AS Java Directories

 /usr/sap/<SID>/<Instance>/work/ - If any error occurs, we see the log

here
 /usr/sap/<SID>/<Instance>/j2ee/cluster/server0/log / - Stores Java-
specific logs, including defaultTrace.trc
 DefaultTrace.trc - if processor stops, we see the detailed log

SAP Central Services (SCS)

 Ensures system synchronization.

Java Dispatcher

 Distributes requests to server nodes.

Server Nodes

 Executes Java applications.

SAP BASIS RAJESH
26

Database Server

 Stores system and application data.



Clients in SAP

A client in SAP is an independent business entity within an SAP system. It

allows multiple organizations to use the same SAP system while maintaining
data separation. Each client has its own master data, transactional data, and
user authorizations, making it a logical partition within the SAP system.

Client 000 in SAP

 Client 000 is the default SAP client that comes pre-installed when you
install an SAP system.
 It is the base reference client containing the original SAP standard
configuration, settings, and master templates.

Client 001 in SAP

 Client 001 is a predefined client that comes with a new SAP

installation.
 It is a copy of Client 000 but allows minor modifications.
 It is used as a reference client and sometimes as a starting point
for system configuration.

Client dependent data

 Client-Dependent data is specific to a single client and is not

shared across other clients.
 Each client in an SAP system has its own version of this data.
 Stored with a Client Number (MANDT) in database tables.

SAP BASIS RAJESH

27

Client independent data

 Client-Independent data is shared across all clients in the SAP

system.
 Any change made in one client automatically applies to all
clients.
 Stored without a client number (MANDT) in the database.

Steps to Create a New Client:

1. Open T-Code SCC4.

2. Click New Entries (F5).
3. Enter the Client Number (e.g., 800).
4. Fill in Client Name & Description.
5. Set Client Role (e.g., Production, Development, etc.).
6. Choose Logical System Name (must be unique for client).
7. Assign Currency and Authorization Control.
8. Save and activate the new client.

Client T-CODES:

SCC3 is used to monitor and analyze logs of client copies (SCCL, SCC9) and
client deletions (SCC5) in SAP. It helps administrators track progress, detect
errors, and troubleshoot issues during client operations.

SCC4 is the Client Administration transaction in SAP. It is used to view, create,

modify, and control clients within an SAP system.

SAP BASIS RAJESH

28

SCC5 is used to delete an entire client from an SAP system. This transaction
permanently removes all client-related data, including customizing, master
data, and transactional data.

SCCL (Local Client Copy) is used to copy client data within the same SAP
system. It allows administrators to create a new client by copying data from an
existing one.

The SCC7 transaction code in SAP is used for Client Import in SAP systems.
It's part of the SAP System Landscape and is primarily used to import data from
one SAP client to another.

The SCC8 transaction code in SAP is used for Client Export in the SAP system.
It allows you to export data from one client in an SAP system to create a copy
that can later be imported into another system or client. This is typically done
for system migrations, client copies, or backups.

SCC9 is used to delete a client from the SAP system completely. This includes
removing all associated data, customizing, master data, and transactional
data from the client.

SYSTEM REFRESH

A System Refresh in SAP is the process of copying a production client’s data

into a non-production system (such as a development or testing system). This
is done to make sure that the non-production environment has the most up-to-
date data, configurations, and business processes, so it can closely mirror the
live environment for testing, development, or training purposes.

Why Perform a System Refresh?

1. Test with Real Data: Non-production systems (like test or development

environments) get updated with real data from the live system. This

SAP BASIS RAJESH

29

makes testing more accurate because you're working with actual, up-to-
date data.
2. Reduce Downtime: Testing or developing with real data helps avoid
issues when changes are pushed to the production environment.
3. Training: It's useful for training purposes, as trainees can work with real,
up-to-date business data.

1. Pre-Refresh (Before You Start)

 Backup: Always create a backup of both the source (production) and

target (non-production) systems. This ensures that if anything goes
wrong, you can restore the system.
 Plan Downtime: A system refresh requires downtime because the
system will be unavailable while the refresh is happening. Schedule this
downtime to avoid disrupting business activities.
 Prepare the Target System: Make sure the target system (e.g.,
development or test system) has enough space to handle the data you're
copying. If needed, delete old data from the target system to make room
for the new data.

2. Refresh Process (Copying Data)

 Export Data from Production: You use a tool (like SCC8) to export the
data from the production system. This data includes configurations,
master data, transactional data, etc.
 Import Data into the Non-Production System: After exporting, the data
is imported into the non-production system using a tool (like SCC7). This
makes the target system's data mirror the live system's data.

SAP BASIS RAJESH

30

3. Post-Refresh (After You Finish)

 Check Data Consistency: Make sure all the data has been correctly
transferred and that there are no errors.
 Adjust System Configurations: You may need to adjust some settings
in the target system, such as user roles and authorizations, as well as
any client-specific customizations.
 Test the System: Run tests to ensure everything works properly in the
refreshed environment. This includes checking business processes to
make sure they're functioning as expected.
 Backup the Target System: Once everything is working correctly, make
a backup of the refreshed target system to have a restore point in case of
future issues.

SAP BASIS RAJESH