Introduction - Done

Journey -

13 May - 20 June

13 May - 17 May - Delivery practice - Self paced learning - Portal

20th May - 20th June - Stream training (SAP BASIS) - Virtual

Timing - 8:30 AM to 5:30 PM

everybody will report at 8:30AM

come back by 9:00 AM
by 9:15 AM or 9:30 AM - Attendance
9:30 to 10:15 AM or 10:30 AM - Training session
10:30 AM - 10:45 AM - Short break
10:45AM - 1:00 PM - Training session
1:00 PM - 2:00 PM - Lunch
2:00 PM - 3:30 or 4:00 - Training session
4:00 PM - 4:15/4:20 PM - Short break
4:20 till EoD - training session

Nomination of CR - [email protected] / [email protected]

===================================================================================
=================================================

MCQ1 {40 Qus} (1st 50% syllabus) + MCQ2 {40 Qus} (2nd 50% syllabus) + ASA (Case
based question {MCQ - 10} + Viva)

MCQ1 {40 Qus} (1st 50% syllabus)

MCQ2 {40 Qus} (2nd 50% syllabus)
ASA (Case based question {MCQ - 10} + Viva)

Minimum Avg marks required to get permanent seat - 60% (Primers + MCQ1 + MCQ2)

Total - 0/2

Criteria 1/2
Primers (20) + MCQ1 (20) + MCQ2 (20) >= 60% -> 36
if not then
RT1 >= 60%
if not then
RT2 >= 60%
if not then
OUT!!

Criteria 2/2

ASA (Case based question {MCQ - 10} + Viva) -> 20 Marks (10 MCQ + 10 Viva) >= 60%
if not then
RT1 >= 60%
if not then
RT2 >= 60%
if not then
OUT!!

===================================================================================
=================================================

Memory - RAM, Volatile Memory

Storage - Data gets stored, permanent
OS - Software
Database - Software

Cloud - Avail Services

Cloud Streaming services - Sounds cloud, youtube, Amazon Prime, Netflix, Dis----
Computer resources shared or sell like a utility
Virtual Storage - GDrive
Network
Instances - VM
Accessible through internet
Model - Pay as you go/ Subscription

Powerful computer -> Mumbai -> 2min

Cloud Player - Azure (Microsoft), AWS (Amazon), GCloud, Ali baba.........., SAP

Deployment option
Public Cloud -
Private Cloud -
Hybrid Cloud -

Services

IaaS - Infra as a service - AWS, Azure

PaaS - Platform -----
SaaS - Software -----
DaaS - Database ----- - SAP HANA Cloud
.
.
.

on-premise
Cloud

Datacenter - Place where your cloud resources/servers are kept

Virtual Machine - Shared resource of a physical computer, Running an OS inside an

OS - Hypervisor

Server - A Computer which provides services

===================================================================================
==========================================

Introduction of SAP

What is ERP -

What is SAP -
SAP Architecture - 3 Layers (Presentation, Application {ERP Soft}, Database (DB
soft))

Tier - 1 Tier, 2 Tier, 3 Tier

SAP Solution & Portfolio - Small/Medium/Large enterprises

SAP Core Modules - Logistics, Accounts, HR

SAP Teams: -
(1) Technical Consultants - Technical side of things (Installation, upgrade,
performance, Coding and debugging, Integration etc.)
Ex. SAP BASIS, SAP ABAP, SAP PI/PO etc.

(2) Functional Consultants - Functional consultants works on business/functional

area side of things.
Ex. SAP MM, SAP SD, SAP FICO, SAP PS, SAP PP, SAP PM, SAP QM etc.
===================================================================================
=============================================================

Prerequisite: -

Software - SAP GUI 8.00/SAP HANA Studio

software.accenture.com

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

Pre-installation

1. Change Hostname
2. Set Swap space/Paging file
3. Check Disk space
4. Add hostfile entry
5. Disable the firewall
6. Check installation media
7. Restart

List of software

(1.) Database - Oracle 12c - Database software file (Oracle12)

(2.) SAP Application - SAP Netweaver 7.5 - Kernel file, SAP NW, Oracle Client,
SWPM.

Kernel file - These are set of executable files which are needed for proper
functioning of SAP system. These files are also called heart of SAP application.

SWPM - Software provisioning manager - Installer

Oracle Client - Software which enables communication between oracle database and
SAP application.

Client Software - Any software which communicates with other application/system

Application (SAP)->Oracle Client <---> Oracle Client<-Database (Oracle)

===================================================================================
===============================
Installation

OS User during installation using SWPM

1. <SID>adm
2. SAPService<SID>
3. sapadm

Oracle DB user created during installation

1. sys
2. system

Default SAP users created after installation: -

1. DDIC
2. SAP* (need to activate it manually)

Default client which gets created after installation: -

SAP Netweaver 7.4 and before - 000 (Golden client), 001(Configuration client), 066
(Earlywatch client)

SAP Netweaver 7.5 - 000, 001

SAP S/4 HANA - 000

SAP MMC (Windows) - SAP application server instance management (start, stop,
monitoring, checking logs etc.)

Start-Stop Sequence

Start Sequence: -
1. Server/VM
2. Database services (Oracle services)
3. SAP Application instances
a. ASCS Instance (01)
b. DB Instance
c. PAS Instance (00)
d. AAS Instance (Optional if any)
Stop Sequence: - Opposite of Start sequence.

Tcodes - Transaction codes - Shortcuts - To perform your activities in SAP system.

SGEN - Load Generator

SAP - ABAP reports/Programs - Compilation of programs -> Speed up in the day to day
operation and execution.

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

SAP Application/Product Stack: -

1. SAP ABAP Stack

2. SAP JAVA Stack
3. SAP Dual Stack (ABAP+JAVA)

SAP ECC - ABAP

SAP BW - ABAP
SAP EP - JAVA
SAP Solution manager - Dual
SAP PI/PO - Dual

ABAP Based System: -

1. ASCS - Central instance

a. Message server
b. Enqueue server
2. DB instance

3. PAS - Dialog instance

a. Workprocess (D/B/V/S)
b. ABAP Dispatcher
c. Gateway
d. IGS
e. ICM

4. AAS - Add. dialog instance

a. Workprocess (D/B/V/S)
b. ABAP Dispatcher
c. Gateway
d. IGS
e. ICM

Java Based System: -

1. SCS
2. DB instance
3. PAS
-----------------------------------------------------------------------------------
-------------------------------------------------------------------

Software maintenance lifecycle management

Download | Installation | maintenance | Troubleshooting | Upgrade/updates

SAP Support portal - SAP Marketplace -> https://support.sap.com/

PAM - Product availability matrix - for checking the compatibility of certain SAP
product with supported OS (& its versions), DB (& its versions), SAP Kernel (&
versions).

Installation - SWPM (Software Provisioning Manager) -> SL Toolsets

SWPM - Install, Uninstall, Rename, Dual stack Split, Database copy

SUM (Soft update manager) - Update/Upgrade
DMO with SUM (Database Migration Option) - SWPM + SUM (Migration + Conversion)

Example: -
ECC 6.0 EHP8 -> S/4HANA 2023 -> (Upgrade/Conversion)
Oracle SAP HANA -> Data Migration

SPAM -Support package manager - If any software component is already present and is
at certain release version, for release upgrade (version upgrade), we use SPAM.
SAINT - SAP Add-on installation - If any software component is not present of SAP
product, you can install it using SAINT.

Note: - SPAM & SAINT should be launched from Golden client (000) only.

SNOTE - SAP Notes - 1. Correction 2. Correction instruction/KBA (Knowledge based

Articles)
These are files which have single correction codes which resolves issue faced in
sap system.
SP - Support Packages - Collection of SAP Notes + New features or upgrade.
SPS - Support Package stack - Collection of Support packages or when multiple SAP
components are involved in SAP upgrade.
EHP - Enhancement Packages - New Features

SSCR Keys: -
Object Key - Standards object in SAP are protected (locked) against any changes, in
order to perform any customization in standards objects/tables, you need unlock
those objects/tables using object key.
Developer Key - Developer (Who works in ABAP Workbench) needs to be register in SAP
portal and get a developer key, in order to register himself as a developer in the
sap system.

SAP License - License key for SAP, by default, you get 90 days of temp license.

User ID in SAP Portal

P-User ID - Training/Learning purpose
S-User ID - Project/Client account management

===================================================================================
============================================================
E: usr/sap/-><SID>/trans

/sapmnt/trans/

/usr/sap/ -> /sapmnt/

/usr/sap/trans/ ->
1} /usr/sap/trans/EPS/in/ = Upgrade files will be stored here - Add-on
installation/SP upgrade
2} /usr/sap/trans/data/ - Stores data file
3} /usr/sap/trans/cofiles/ - stores Cofiles (info about respective data file)
4} /usr/sap/trans/bin/ - TP profile and domain CFG file information
5} /usr/sap/trans/buffer/ - It has import buffer related file.

/usr/sap/DEV/ ->
2 types of folder
1. Instance Directory - ASCS<nr>, D<nr>. <nr> -> Instance number
2. Global directory - SYS

Instance Directory
/usr/sap/DEV/ASCS01|D00/ ->
1} /usr/sap/DEV/ASCS01|D00/work/ - all logs (system error, system diagnostic,
component specific logs etc.)
2} /usr/sap/DEV/ASCS01|D00/exe/ - kernel files will be stored
3} /usr/sap/DEV/ASCS01|D00/sec/ - SAP Security cerficiates stored

Global directory - SYS

/usr/sap/DEV/SYS/ ->

1} /usr/sap/DEV/SYS/exe/uc/NTAMD64/ - kernel files will be stored - sapcpe.exe

2} /usr/sap/DEV/SYS/profile/ - This directory has sap profile stored (Default and
instance profile)
3} /usr/sap/DEV/SYS/global/ - Global settings are stored

===================================================================================
==================================================
**User Administration -> control the access to applications by creating users,
maintaining the same users.
SU01 - Managing the user (create/delete/edit/customize/password set/copy user etc.)
-> Done
SU10 - Mass user operation (create/delete/lock/unlock/assign roles etc.) -> Done
SU01D - View only purpose -> Done
SUIM - Select/List out users using various filters -> Done
SUGR - User Group creation -> Done
SUCOMP - Company code -> Done
SU53 - Checking Missing auth. objects -> Done
SU3 - Managing user's own data

Tables for User management: -

USR02 - List of users
USR40 - List of illegal passwords/Restricted password

Types of Users: -

1) Dialog user -
=>This user is used for interactive system access from GUI.A regular dialogue
user is used for all logon types by precisely one person.
=>This is used to logon using the SAP GUI. During a dialog logon, the system
checks for expired/initial passwords.
=>The user can change his or her password. Multiple dialog logons are checked
and, if appropriate, logged.
=>These users are used for carrying out standard transactions. This is an
interactive type of logon. The initial multiple logins are 6. They are set
according to company policy.

2) System user -
=>This user is used for background processing, communication within a system.
=>These are non-interactive users. They are used for background processing
and internal communication in the system (such as RFC users for ALE, Workflow, TMS,
and CUA).
=>The end users cannot change their passwords. Only the user administrator
can change their passwords.
=>Multiple logins is permitted in this type of user. Dialog logon is not
possible for this type of user.

3) Communication user -
=>This user is used for external RFC calls.Used for dialog-free communication
between systems.
=>It is not possible to use this type of user for a dialog logon.
=>Their passwords are valid for a certain period, so they expire. The users
have the option to change their passwords.

4) Service user -
=>This user is created for a larger and anonymous group of users
=>Dialog user is available to a larger, anonymous group of users. The system
does not check for expired/initial passwords during login.
 =>Only the user administrator can change the passwords. Generally, highly
restricted authorizations are given to this type of user.

5)Reference user -
=>A reference user is, like the service user, a general non-person-related
user. Dialog logon is not possible with this kind of user.
=> A reference user is used only to assign additional authorizations. To
attach a reference user to a dialog user, specify it when maintaining the dialog
user on the Roles tab page.

Role Management: -

Role - PFCG

Authorization Object -> Role (BASIS) -> Profile -> Assigment

Single role -
Composite role
Derived role

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

R3 Client Administration

Total No. of Client possible - 1000 -> {000 - 999}

By default, how many clients are available -

NW 7.3 or 7.4 - 000, 001, 066

NW 7.5 - 000,001
S4HANA - 000

How many client we can create - 997/998/999

Logical System - each client acts as an independent system, to identify that

individual client, apart from client number, we use logical system name.

Client - 100 - <SID>CLNT<Client No.> -> DEVCLNT100

Client - 200 - DEVCLNT200

BD54/SALE - Creation of Logical system

SCC4 - Client Creation
SCCL - Local client copy (RFC) - Both of your client (Source & Target) should be in
same system
SCC9 - Remote client copy (RFC) - Your source and target client are in different
system (DEV (100) -> Source, QA (250)-> Target) - RFC connection between source and
target.
SCC8 - Export client data using TR
SCC7 + STMS_import - Import of client data + post processing
SCC1 - Copy transport across different clients of same system
SCC3 - Checking the logs for client copy
SCC5 - Client deletion

Creation of client: -

SCC4 - Pre-requisite - You should have logical system name defined in BD54
When you create a new client - SAP* - pass

Client Copy - Local

Pre-requisites -

1. Target client should be available

2. Background jobs should be suspended in source client
3. Users in source client should be locked

SCCL - Local client copy

You should login to the target client (200), and select the source client (100) in
Tcode - SCCL

Private mode (PRIV)-> kill wp

Memory assigned to individual wp - Local memory

shared memory for workprocesses - Extended memory
Heap memory

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

Transport Management System

**3 System Landscape (Dev->QA->Prod)

Production - Business is running - Live system

Scenario - Some requirement came from the client - I want to change the view of the
specific screen - ABAPer - He coded and made those changes.

Never a good idea to perform any changes directly into Production system.

Development System (Development/ Changes are introduced)

All coding, Patching, Soft upgrade

Quality System/UAT System (Testing of the functionality/changes/Development)

Testing of the introduced functionality/Changes which made in the development

Production System
Here the final deployment will be done. Business runs here.

Changes -> Captured in a Transport request

1. You're facing issue in a specific tcode - SAP Note - which will fix the issue -
Capture the data/sap notes - In a Transport request
2. You've created a SAP Role - Which grants you access to delete any user in the
system - Captured new role - In a Transport request
3. Some ABAP dump was coming due to inactive object - Activated object in the
system - Captured that activation - In a transport Request
**Changes are moved in SAP System through Transports - Dev->QA->Prod

**(Refer PPT) Types of Data in SAP: -

1. Customizing Data: - When SAP Delivers soft, it is mostly Standard software (not
customized for client entirely). When standard SAP soft (Product/System) is not
sufficient to meet with the client's requirement, We introduce few/some changes in
those SAP components/objects/SAP software. These changes gets stored in a
customizing table and that data is known as customizing data.
Usually customizing data are client specific and not globally applied throughtout
the system.
The transport request which captures the customizing data is known as customizing
request.

2. Repository Data: - in SAP System, it comes with an added advantage that you can
create few changes for specific requirement of the client. These changes can be
done using ABAP workbench, ABAP editor. ABAP'er can introduce new
interface/objects/tables/screen using workbench functionality. These data gets
stored in repository table. This data is known as Repository data.
These are independent from the SAP Standard Objects & This thing gets applied
globally (It applies in the system level).
The transport request which captured the Workbench data is known as workbench
request.

Customizing data - SAP has provided a standard soft component/object/table ->

changing/altering those standard things, client specific data (does not apply
globally)
Repository Data - We are completely creating new changes/ we are introducing
changes which are globally applicable (to all clients)

3. Application Data: - Application data (Transactional Data) is a client

(Business/organization) specific data in which all business specific record
financial data, material management related data. procurement related data, supply
chain/payroll related data etc gets stored. These data can not be transfer to other
system using TMS (Transport management system). This can be done using special tool
ALE,CATT etc.

***two types transport request

One which captured data which will apply globally - Workbench TR

One which captured data which will apply client specific - Customizing TR

Define a change (Requirement) -> Work on those changes -> Capture the activity
(change) in a Transport request -> Release the Transport from Development system->
Available in QA system import queue -> Import the Transport in QA system -> Testing
in QA system -> Import the request in prod after successful testing and approval.

**Steps to configure Transport: -

SE06 - Reset the TMS configuration

STMS - Created Transport domain, Created TMSADM, created transport group
STMS -> System Overview -> Virtual system
STMS -> Transport routes -> Defined the transport route (mapping of the systems)
***CTO - Used for creation of transports and releasing the transports
{administration, monitor and analysis} - SE01/SE03/SE09/SE10
Transport Tool: - tp and R3trans
STMS - Tcode - STMS & STMS_Import

***Transport Route - It is used to connect 2 sap systems in a SAP domain

there are 2 types sap routes" -

1. Consolidation Route -> Dev->QA

2. Delivery Route -> QA->Prod

*Transport Domain - All the system which are connected through transport routes are
known to be in a Transport domain (Group of sap systems connected through Transport
routes).

***Domain Controller - This system is responsible for the adminstration and

management of the transport domain (Including system, approving system, changing TP
profile parameters, creation of transport routes etc.)

Transport Directory Structure and folder usage.

Transport Group - TMS supports multiple transport directories within a transport

domain. All systems which shares common transport directory forms a transport
group.

Transport Layer - All development projects developed in a same SAP system &
transported on the same transport route are grouped together to form a transport
layer.

***TMS Configuration - Perform in client 000 only

SE06 - Standard installation -> perform post installation actions
STMS - Create transport Domain and create transport group.

***Return Code -

RC=0 - Successfully imported without any error

RC=4 - Imported with warnings
RC=8 - Import canceled with errors
RC=12
RC=16

***Naming convention
Data file - R9<TR no.>.<SID>
Co-files - K9<TR no.>.<SID>
Transport number - <SID>K9<TR no.>
Example: - of a company {Accenture} bus (transport service bus) which carries
employees: -

Traveller (BUS) - Facilitator - Transport Layer

Conductor - Intructs the driver - tp tool
Driver - Who actually drives - R3trans
Employees - Who are getting transported - Changes/ Development objects
ID card - Identification (make sure you belong a certain group/company) - Transport
Package
Road (Highway) - The way, the path where the bus will travel - Transport route
-----------------------------------------------------------------------------------
-------------------------------------------------------------------

SAP Profile - These stores the SAP profile parameter values.

Profile parameters - Are varibles, which defines how your system will behave. Using
profile parameter, you decide how your system will work, show outputs etc.

**login/no_automatic_user_sapstar = 0 -> To activate SAP* user

***SAP Profile types: -

1. Default profile - When you define any sap profile parameter in the default
profile, the parameter will be applicable/activated in all of the sap application
server instance.
example - Any user, who is idle for 60 seconds should be kicked out from the SAP
system.

2. Instance Profile - When you define any sap profile parameter in any of the
Instance profile, the parameter will be applicable/activated in the specific sap
application server instance.

Application server instance -> During the installation, individual soft components
(application server instance) gets created. these are known as Application server
instance. These have specific set of processess and uses specific set of resources
from OS/server.
Instance no. - OS level funda ->

Server - Instance no. -> This isolates/divides the resources to individual

applications (xx - instance no. 00 to 99)

SAP ECC (00) - 3600, 3200, 3300

SAP GRC (10) - 3610, 3210, 3310

SAP app or external non sap app

172.240.10.78:3600
172.240.10.78:3610

ASCS01 - ABAP central services (message server enqueue server)

PAS00 - Primary application server (dispatcher, gateway, IGS, ICM, Workprocess)
AAS02 -Additional application server (extra hand you need -> extra resource ->
similar to PAS)
Kernel Values (1)
|
Default profile (0)

**Kernel values (300) --> Default profile (200) ---> Instance profile {PAS} (500)

Kernel -> Set of executable files, which performs Very foundational activities
(Basic activities) in the backend.

***Based on nature - 2 Types

RZ10 - Static parameter - To activate a static parameter, you need to take restart
of the system.
RZ11 - Dynamic parameter - This parameter can be activated instantaneously, the
moment you will assign a value against a specific dynamic parameter, that value
will be activated. The assigned value will be revert to its original value upon
restarting the system.

===================================================================================
==============================================================

***OS Commands: -

disp+work = checking kernel release version

R3trans -d = Checking Database connectivity with application (0000 means connected,
0012 means not connected)
SAPSTART.EXE name=<SID> nr=<SYSNR> SAPDIAHOST=<host> = start sap application
instance
STOPSAP.EXE name=<SID> nr=<SYSNR> SAPDIAHOST=<host> = stop sap application
instances

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

Transport Management System

**3 System Landscape (Dev->QA->Prod)

Production - Business is running - Live system

Scenario - Some requirement came from the client - I want to change the view of the
specific screen - ABAPer - He coded and made those changes.

Never a good idea to perform any changes directly into Production system.

Development System (Development/ Changes are introduced)

All coding, Patching, Soft upgrade

Quality System/UAT System (Testing of the functionality/changes/Development)

Testing of the introduced functionality/Changes which made in the development
Production System
Here the final deployment will be done. Business runs here.

Changes -> Captured in a Transport request

1. You're facing issue in a specific tcode - SAP Note - which will fix the issue -
Capture the data/sap notes - In a Transport request
2. You've created a SAP Role - Which grants you access to delete any user in the
system - Captured new role - In a Transport request
3. Some ABAP dump was coming due to inactive object - Activated object in the
system - Captured that activation - In a transport Request

**Changes are moved in SAP System through Transports - Dev->QA->Prod

**(Refer PPT) Types of Data in SAP: -

1. Customizing Data: - When SAP Delivers soft, it is mostly Standard software (not
customized for client entirely). When standard SAP soft (Product/System) is not
sufficient to meet with the client's requirement, We introduce few/some changes in
those SAP components/objects/SAP software. These changes gets stored in a
customizing table and that data is known as customizing data.
Usually customizing data are client specific and not globally applied throughtout
the system.
The transport request which captures the customizing data is known as customizing
request.

2. Repository Data: - in SAP System, it comes with an added advantage that you can
create few changes for specific requirement of the client. These changes can be
done using ABAP workbench, ABAP editor. ABAP'er can introduce new
interface/objects/tables/screen using workbench functionality. These data gets
stored in repository table. This data is known as Repository data.
These are independent from the SAP Standard Objects & This thing gets applied
globally (It applies in the system level).
The transport request which captured the Workbench data is known as workbench
request.

Customizing data - SAP has provided a standard soft component/object/table ->

changing/altering those standard things, client specific data (does not apply
globally)
Repository Data - We are completely creating new changes/ we are introducing
changes which are globally applicable (to all clients)

3. Application Data: - Application data (Transactional Data) is a client

(Business/organization) specific data in which all business specific record
financial data, material management related data. procurement related data, supply
chain/payroll related data etc gets stored. These data can not be transfer to other
system using TMS (Transport management system). This can be done using special tool
ALE,CATT etc.

***two types transport request

One which captured data which will apply globally - Workbench TR

One which captured data which will apply client specific - Customizing TR
Define a change (Requirement) -> Work on those changes -> Capture the activity
(change) in a Transport request -> Release the Transport from Development system->
Available in QA system import queue -> Import the Transport in QA system -> Testing
in QA system -> Import the request in prod after successful testing and approval.

**Steps to configure Transport: -

SE06 - Reset the TMS configuration

STMS - Created Transport domain, Created TMSADM, created transport group
STMS -> System Overview -> Virtual system
STMS -> Transport routes -> Defined the transport route (mapping of the systems)

***CTO - Used for creation of transports and releasing the transports

{administration, monitor and analysis} - SE01/SE03/SE09/SE10
Transport Tool: - tp and R3trans
STMS - Tcode - STMS & STMS_Import

***Transport Route - It is used to connect 2 sap systems in a SAP domain

there are 2 types sap routes" -

1. Consolidation Route -> Dev->QA

2. Delivery Route -> QA->Prod

*Transport Domain - All the system which are connected through transport routes are
known to be in a Transport domain (Group of sap systems connected through Transport
routes).

***Domain Controller - This system is responsible for the adminstration and

management of the transport domain (Including system, approving system, changing TP
profile parameters, creation of transport routes etc.)

Transport Directory Structure and folder usage.

Transport Group - TMS supports multiple transport directories within a transport

domain. All systems which shares common transport directory forms a transport
group.

Transport Layer - All development projects developed in a same SAP system &
transported on the same transport route are grouped together to form a transport
layer.

***TMS Configuration - Perform in client 000 only

SE06 - Standard installation -> perform post installation actions
STMS - Create transport Domain and create transport group.

***Return Code -

RC=0 - Successfully imported without any error

RC=4 - Imported with warnings
RC=8 - Import canceled with errors
RC=12
RC=16

***Naming convention
Data file - R9<TR no.>.<SID>
Co-files - K9<TR no.>.<SID>
Transport number - <SID>K9<TR no.>

Example: - of a company {Accenture} bus (transport service bus) which carries

employees: -

Traveller (BUS) - Facilitator - Transport Layer

Conductor - Intructs the driver - tp tool
Driver - Who actually drives - R3trans
Employees - Who are getting transported - Changes/ Development objects
ID card - Identification (make sure you belong a certain group/company) - Transport
Package
Road (Highway) - The way, the path where the bus will travel - Transport route

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

Spool Adminstration (Output request management)

Spool work process ->

User request (print) -> Spool request & Spool Data => Output request -> Spool WP ->
Printing server/OS of server -> Printer

When you request a print -> 1. You specify output printer name - SAP Spool only for
now
2. You specify output printer name - Immediate/date & time
printing

***SPAD - Spool adminstration - *Access Method* -

C/F/G - Local & Front end printing - Windows
L - Local printing - Linux
S - Print using SAP Protocol (remote printing) - Windows
U - Using Berkeley Protocol (remote Printing) - unix/Linux

***SP01/SP02 - Montioring of Spool request

SP02 -> Request created by the user, who executed the Tcode, in the existing
client.
SP01 -> browse the request created by any user in any client.

***Temse - Temp sequencial storage table - TST03 (Table name)

***SP11 - Spool data/Temse Data

***SP12 - Administration - Deletion + Consistency check

SPOV - Overview of the spool request

***ABAP Program/reports (Tcode - SE38): -

RSPO1041 - Delete old spool request
RSPO1043 - Consistency check of spool data

===================================================================================
===============================================================
***System Monitoring/Daily Monitoring: -

1. SM51 - Check the availability of the application server

2. SM50/SM66 - Checking the work process status (Local/Global)
3. SM21 - System Logs
4. SM37 - Background job monitoring
5. ST06 - OS level monitoring (RAM/CPU/SWAP SPACE/FILE DIRECTORY/SAPOSCOL)
6. ST02 - MEMORY TUNING
7. ST22 - ABAP DUMPS
8. ST03/STO3N - WORKLOAD Analysis
9. SM12 - SAP Locks
10. SM13 - Checking the update entries
11. SMQ1 - Outbound qRFC
12. SMQ2 - Inbound qRFC
13. SM58 - tRFC monitoring
14. SCOT - Mail Node configuration
15. SOST - Mail output monitoring
16. STRUST/STRUSTSSO2 - SAP Security certificate(SE38 -> SSF_ALERT_CERTEXPIRE)
17. AL11 - SAP Directory
18. SM04/AL08 - Checking SAP User sessions (Local/Global)
19. SCC4 - client checking/administration
20. DB01/DB02/DB12/DB13/DBACOCKPIT/ST04 - DB Administration related tcodes
DB12 - backup catelog
DB13 - DBA planning calender (schedule backup)
DB02 - Space overview
DB01 - Oracle lock monitor
ST04 - DB performance overview
21. ST01 - System Trace
22. ST05 - Performance Trace
23. RZ20 - CCMS Monitoring

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

Background Job administration - SM37 -> Monitor and analyze the job

Why Background jobs are needed?

1. When the job is of repetitive nature.
2. No frequent dialog user intervention/input required.
3. When there is requirement to run an expensive/intensive/heavy job.

SM36 -> Scheduling custom and standard jobs

SAP Standard Jobs - These are also called house-keeping job. These are scheduled to
make sure your system health remain in good condition without storing redundant
data which is no longer needed.
You scheduled Standard jobs using SM36.

ABAP Program/External command/External Program - Which is required to run under

certain circumstances, repetitive or non-repetitive way, usually run using
background work process.

***1. Name of the job - Z or Y - Z_SD_AUS_CreatePO

***2. Job Class - Priority of Job - A/B/C - 10 AM - 2 jobs are schedule to run - 1
BG available - A will have more priority than B & C -> A>B>C
3. Spool list recipient - Mail list
4. Step of the Job
a. User - Step user - It runs the job. Assign a user which is long lived,
doesn't expire, has sufficient authorization to run the job.
***b. Program values - Define what job will do. (1. ABAP Program, 2. External
commands, 3. External Program)
***5. Start condition - How your job will run, when it will run. (1. Immediate, 2.
Date/time, 3. After Job, 4. After Event, 5. Operation Mode, 6. Workday/Time)
***6. Define the period values (Reoccurrence of the Job) - {1. Months, 2. Weeks, 3.
Days, 4. Hours, 5. Minutes}

10 AM - BG available - engaged in some other job - Job will go to queue.

***Status of the job -

Scheduled -> You haven't defined the start time/start conditions & haven't released
the job (Saved the job).
Released -> The moment you'll assign start time/conditions, job will be in
released. Your job will start running/will be assigned BG work-process, once start
conditions are met (subjected to availability of BG work-process).
Ready -> The job is ready to be assigned a BG work process.
Active -> When job starts to run.
Finished -> Job executed successfully.
Canceled -> Job failed

Some important Background job related ABAP programs: -

BTCTRNS1 - Suspend background jobs due to upgrade

BTCTRNS2 - Release background jobs
RSBTCDEL2 - Deletion of Background jobs

===================================================================================
==================================================

SAP Operation mode - RZ03/RZ04/SM63

Office Hours - There will be more number of active sap user - Dialog work process
(More), background work process (Less).
Non-office Hours - There will be less number of active sap user - Dialog work
process (Less), background work process (More)

Day time (8 AM to 5 PM) or (6 AM to 8 PM)

Diag - 10
BG - 4

Night Time (6 PM to 8 AM) or (9 PM to 6 AM)

Diag - 6
BG - 8

RZ03 - CCMS Monitoring - Checking the Operation mode status

RZ04 - Create Operation mode and define number of workprocess
SM63 - Define timings for the operation modes - Normal, exception

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

SAP SECURITY
***PFCG -> Create SAP Roles

***Roles -> Profile (Generate automatically) -> Auth Objects (Foundation of auth
check)

***Roles -> There are 3 types of Role

1. Single Role -> Normal/basic role that you can create

2. Composite Role -> Collection of Single Roles
3. Derived Role -> You derive certain auth and access from role

**How to check missing auth objects of a user -> Tcode - SU53

**Menu Items in PFCG t-code - during Single role creation

(1) Description (2) Menu (3) Workflow (4) Authorization (5)User (6) Miniapps
(7)Personalization

**Menu Items in PFCG t-code - during Composite role creation

(1) Description (2) Role (3) Menu (4) User (5)Personalization

Authorization objects -> SAP Security Profile => Users

Authorization objects -> SAP Security Role -> SAP Security Profile => Users

SAP AUDIT Management

SM18 - Deletion of Old Audit logs

SM19 - Audit creation T-code
SM20 - Export of Audit Logs

Location of Audit Files - /usr/sap/<SID>/D<NR>/log/

===================================================================================
===================================================================

SAP Memory Management: -

1. Virtual Memory -> Local Memory (RAM) + Swap Space (Defined in OS Level) {Works
as RAM which is the part of your storage}

2 parts - 1. Used by Work process (Local memory)

2. Shared Memory (Used as per requirement)

Local Memory - L1 | L2 | L3 | L4.... - Dedicated part of local memory which will be

used by individual work process without sharing it with others because they're
cheap guys.

SAP Buffer: - It stores frequently used SAP ABAP executable in compiled form, Data
table, Repository buffer etc. to improve the system performance.

Ex: - R/3 Buffer, Extended memory, R/3 Paging file, Roll buffer.

User Context - It means all data which characterize user for example -
authorization, administrative information & data for screen processing. It must be
shared to all workprocesses that's why it is stored in Extended memory (Part of
shared memory).

Heap memory: - This is part of the local memory

Flow of How Workprocess utilize memory from different part of virtual memory
(Diaglog WP): -

User --> Task---> Workprocess 1 -----> Use Local memory 1 (Roll area initial)----->
Extended memory (Shared memory)------> Local Memory 1 (Roll area leftover)---->
Heap memory (Workprocess status will become private, It is also known as PRIV mode
& WP will stop working)

===================================================================================
===================================================================================
=============

SPDD - Data dictionary adjustment - Keeping the customized table data and making
sure that the standard table data doesn't replace the old table data of your
system. This adjustment needs to be done immediately, cannot be skipped or go ahead
without making adjustment.

SPAU - Repository objects (SAP Notes, function groups, function modules etc.). This
can be skipped as there is 14 days of window to perform the changes/adjustment.

SPDD SPAU are Tcodes. SPDD SPAU modification are phases as well which comes during
the upgrade (SPAM/SAINT/SUM). These phases offers you opportunity to keep your
customized changes in your system and let you decided whether you want to overwrite
the change in the system.

Who performs SPDD and SPAU Adjustment - ABAP consultant - Will capture these
changes in Development system in TR for further landscape (QA/Prod).

===================================================================================
=======================================
RFC

***RFC - Remote function calls - SM59

RFC - Gateway Component

Type of Connections which can be created in SM59

**1. ABAP <-> ABAP - Type 3

**2. ABAP <-> JAVA/ABAP (HTTP connection) - Type H
**3. ABAP <-> External (HTTP Connection using RFC technology) - SAP service market
place - SAP Note implementation - Type G
4. Internal connection - SAP Standard communication (Internal communication - Abap
systems connected to the SAME DATBASE as the Current system) - Type I
**5. ABAP <-> Certain executable programs (SAPGUI, Spooler) - TCP/IP - Type T
6. Connections via ABAP driver - Type X

#Application in Client copy: -

Local client copy: client copy within same system
Remote client copy: client copy(client data) b/w two system
source(sender)system----Target(receiver)system

For creation:
1) Enter SM59
i)RFC destination( target system ID)
ii)connection type
 iii)description
2)Technical tab:
Setting:
Target Host(IP)
System number(Instance Number)
3)Logon/security tab:
i)language
ii)Client
iii) User (communication user)
iv) Password

***Types of RFC:
1) Synchronous sRFC - Active<->Active - source and target must available, Here
acknowledgement is needed. It requires both system to be available
2) Asynchronous aRFC - No need of acknowledgement. It doesn't require other system
to be available during the time of execution.
3) Transactional tRFC (SM58) - Combination sRFC & aRFC - Each of the RFC request
will be assign a transaction ID, once the other system is available, that will get
executed + It also records failures so that you can process. In tRFC, the
functional modules are bundled in small packets which we call LUW (Logical units of
work) which gets executed in the target system.
4) Queued qRFC (SMQ1/SMQ2)- First come, first serve - Follows sequence - Unique ID
1)Inbound Queue(Inbox)- SMQ2
The request that you're receiving from other system.
To monitor inbound queue-SMQ2/Tcode
To view the list of inbound queue-SMQR/Tcode
2)Outbound Queue(outbox)- SMQ1
The request that you're sending to other system.
To monitor outbound queue-SMQ1/Tcode
To view the list of outbound queue-SMQS/Tcode

Error what we need to check:

1) connection type
2) Authorization test
3) unicode/non-Unicode

===================================================================================
===================================================================

SAP HANA Introduction: -

HANA Stands for High performance analytical appliance.

HANA is nothing more than a database. but how it's different than oracle, sql etc.

So first we need to check what is a traditional database is & how it works in

general.

Why HANA: -
See the diagram & example of walmart

OLTP – Online Transactional processing system - System which is purely built to

store the transactional data
OLAP – Online Transactional Analytical system - System which is purely built to
read data & perform analytical tasks.

Using OLAP system, we perform: -

Predictive analysis
Trend analysis
forecast analysis

2003 - 2004 - SAP BWA - SAP Business Warehouse Accelerator

HANA Replaced the BW warehouse part used for analytical reporting.

What is HANA system (IMCE - In memory computing engine): -

HANA is backed 3 different type of technologies: -

1. Trex technology - Text Retrievel & extraction engine (improve the read
performance of in-memory database)
2. P* Time - (light weight RDBMS system for better write performance)
3. MAXDB - Persistence layer for backup & restore operation only.

Why HANA is called in Appliance - Appliance - Software + Hardware

Software Advancement -
1. In- memory DB
2. Column Storage + Row Storage
3. Computational capability (Push Down Mechanism)
4. Significant Compression factor

Hardware Advancement -
1. MPP - Massive Parallel Processing - Multi Motherboard -> Multi CPU -> Multi Core
(Divide a table in several parts & perform parallel process)

Bring data from a source system to target system is known as ETL--> Extraction
Transform Load
But in HANA, It is known as DATA provisioning - SLT, BODS, SDA etc.

Few of the challenges: -

1. Traditional DB were mechanical device - I/O, Maintenance, Read & write

capabilities
2. Cost moderated
3. There were too many competitors with same technology

HANA DB - In-memory, Column based (supports row based store), OLTP+OLAP = OLTAP

Oracle - Soft or storage capability

Appliance - Hardware capability + Software capability

===================================================================================
===================================================================

Installation of Database (SAP HANA): - Linux (SuSE & RHEL)

***1. How we install - HDBLCM - HANA Database Lifecycle management
***a. hdblcm (terminal based installer) - Install using input commands
***b. hdblcmgui (GUI based installer) - Extra tools (MobaXterm)
***c. hdblcmweb (URL based installer) - open url in browser for installation steps.

You'll use ROOT user for the installation of your SAP HANA DB.

***During the Installation HANA DB: -

What are the OS level users gets created - sapadm, <SID>adm

What are the database users gets created - SYSTEM (super user of DB)
What are the Parameters that you supply during the installation -
System ID name -
instance number -
Hostname -
Default installation directory and HANA specific locations

/hana/shared/ - Installation directory

/hana/data/ - directory for storing data units
/hana/log/ - directory for storing logs
/usr/sap/ - home directory of SID

***What are the mandatory components which is required to be selected during the
installation of SAP HANA - 1. hana server, 2. hana client

***HANA License - 2 types of License - 1. Enforced 2. Unenforced

HANA used memory - 512 GB + Tolerance

***Validity of temp license - 90 days

***once your newly installed license (permanent license) gets expired, what is the
grace period for the renewal of the license - 45 Days

===================================================================================
==

SAP HANA Architecture

Architecture of SAP HANA DB

Single Container DB - HANA 1.0 SP08 - System DB

Multi Container DB - HANA 1.0 SP09 & onwards

SAP HANA - SAP HANA 1.0 & SAP HANA 2.0

SID - PDA
System DB (1) - This will have all information about the tenants, system
configuration, parameters, data location, system db specific user and roles etc.
System DB have the topology information about the database.

Tenant DB (20) - Will have actual business data, user schema, tenant specific
parameter information, Tenant user and roles, table information of own tenant.

During the installation, A System DB and one Tenant DB will be created. The name of
the Tenant DB which gets created by default during the installation is same as the
SID of the database

House owner - Tenant

House owner (System DB) - Remove tenants, adding tenant, map (dimensions) of the
apartment, legal documents, ID cards of tenants

Tenants (Tenant DB) - Their own stuffs (bed, bag, table etc.), owner of their own
stuffs, is there a possibility of multiple tenant - Yes

***Core Processes of SAP HANA DB: -

Name server - Runs of system DB, and works as a index server for the system DB
Index server - Runs on Tenant DB, and stores are processes all DB objects belongs
to the particular Tenant DB container.
Preprocessor - TREX engine - Structured and unstructured data is processed
Compile server - Compilation of SQL programs
XS Engine - Native application development using web based workbench
Daemon - starting of services (monitors)
sapstarsrv - Trigger service
webdispatcher - web dispatcher (HTTP/HTTPS request)

**How to Check running services in SAP HANA from OS: -

Login to <SID>adm
use command : - HDB info or sapcontrol -nr <instance no.> -function GetProcessList

**How to start or stop DB

Login to <SID>adm
HDB start
HDB stop

You can also use ROOT user and use sapcontrol command to start your database (refer
to slides for command)

**How to get Database version

Login to <SID>adm
HDB version

===================================================================================
===================================================================

***Backup and recovery: -

2 Types of Backup available in SAP HANA

1. Complete DB backup or Full backup

2. Delta Backup
A. Incremental Backup
B. Differential Backup

1. Complete DB backup or Full backup - It backs up the complete database. You don't
need any extra backup for restoration of the database (unless you want to restore
to a certain point which is not captured by the full backup).

Example - You've taken a Full backup 10:00 AM & your DB gets corrupt 1:00 PM.

2. Delta Backup - This backs up the database from a last checkpoint (Full backup)
till the point of execution. This doesn't captures the complete database backup,
rather only captures the delta part (change in data) post a Full backup.

Example - You've taken a Full backup 10:00 AM & you've initiated a delta backup
(either incremental or differential) at 12:00 PM. Your DB gets corrupt 1:00 PM.
A.) Differential Backup - For differential backup, the checkpoint is always Full
backup.

Example -
1) You've taken a Full backup 10:00 AM & you've initiated a differential backup at
12:00 PM. Differential backup is going to capture data between 10:00 AM and 12:00
PM

2) You've taken a Full backup 10:00 AM & you've initiated first differential backup
at 11:00 PM. First Differential backup is going to capture data between 10:00 AM
and 11:00 PM. Now you've initiated second differential backup at 1:00 PM, Second
Differential backup is going to capture data between 10:00 AM and 01:00 PM.

B.) Incremental Backup - For Incremental backup, the checkpoint is either a Full
backup or a Delta (differential or incremental) backup.

Example -
1) You've taken a Full backup 10:00 AM & you've initiated a Incremental backup at
12:00 PM. Incremental backup is going to capture data between 10:00 AM and 12:00 PM

2) You've taken a Full backup 10:00 AM & you've initiated first differential backup
at 11:00 AM. First Differential backup is going to capture data between 10:00 AM
and 11:00 AM. Now you've initiated an Incremental backup at 1:00 PM, Incremental
backup is going to capture data between 11:00 AM and 01:00 PM.

3) You've taken a Full backup 10:00 AM & you've initiated first Incremental backup
at 11:00 AM. First Incremental backup is going to capture data between 10:00 AM and
11:00 AM. Now you've initiated second Incremental backup at 1:00 PM, Second
Incremental backup is going to capture data between 11:00 AM and 01:00 PM.

**Terminologies: -

Undo Logs: - Whenever any data gets change or edit operation takes place in any DB
table, Database captures the old state of the table to ensure a fallback mechanism.
These data which stores old state of the table are known as undo logs. This is
stored in Data volume.

Redo logs: - The data which is changed is captured in redo log files. These changed
data will be used for restoring your database to the most recent state after any
commit transaction. This is stored in Log volumes.

Save point - Default mechanism in database which ships data and log from DB level
to persistent level. Usually it is at 5 min interval.

***System privileges required for scheduling a backup: -

Backup_admin
Catalog Read
===================================================================================
==================
SAP Security

***User Administration: -

Standard users available in SAP HANA: - SYSTEM, SYS, SYS_BI, SYS_BIC,

_SYS_STATISTICS etc.
(Refer the list given in the slide).

***Types of Users: -
1. Standard user: - It has public role assigned.
2. Restricted user : - It doesn't have public role assigned which prevents some of
the action that can be performed using a restricted user.

***Command for creating user: -

Standard user: - Create user <user name>;

Restricted user: - Create Restricted user <user name>;

***Roles: - SAP HANA Roles are collection of privileges which can be directly
granted to users or can be assigned to other roles. There are some standard roles
given and new roles can be created by referring to the standard ones.
It is always best practice to assign custom roles to users rather than directly
assign the standard roles or privileges directly to users.
Two types of HANA roles: -
1. Catalog roles 2. Design time repository roles

Command for creating a role: -> Create role <role name>;

***Privileges: - There are 6 privileges in SAP HANA: -

1. System, 2. Object, 3. Application, 4. Package, 5. Analytic, 6. Privileges on
user