VIDEO
HIGHLIGHT
Log InSign up
Day 2 - SAP Client Administration
SummaryTranscriptChat

Day 2 - SAP Client Administration

Introduction to Client Administration

In this section, we will learn about client administration in SAP systems. We will define what a client is and why the SAP system is divided into clients.

What is a Client?

  • A client is represented by a 3-digit number from triple 0 to triple line.
  • A client refers to an independent space within an SAP system.
  • The maximum number of clients that can be created within an SAP system is 1000.

Purpose of Dividing SAP System into Clients

  • Dividing the SAP system into clients helps organize data and makes it easier to retrieve data.
  • Segregating data clearly and storing it becomes possible with dividing the SAP system into spaces.

Benefits of Using Clients

  • Each space or client is independent of others, which means that any changes made in one client do not affect other clients.
  • Organizing data becomes easier with clients, making it easy to retrieve specific information when needed.

Conclusion

In conclusion, understanding what a client is and how it works in an SAP system is essential for effective client administration. By dividing the system into smaller spaces or clients, organizing and retrieving data become more manageable.

IDS and Client Data

In this section, the instructor explains the concept of IDS (International Demonstration and Education System) and non-IDS systems. The instructor also discusses client data, which is divided into two types: client-independent (standard data) and client-dependent (customized data).

IDS vs Non-IDS Systems

  • IDS stands for International Demonstration and Education System.
  • IDS is a training system, while non-IDS systems are used for business purposes.
  • IDS systems have more clients than non-IDS systems because they require sample or official data for training purposes.

Client Data

  • Client data is divided into two types: client-independent (standard data) and client-dependent (customized data).
  • Standard data refers to pre-existing commands in SAP, while customized data is created based on customer requirements.
  • Examples of standard data include T-codes and map codes that come with SAP installation. Examples of customized data include user-created transactional data.
  • To determine whether the data is standard or customized, ask how it was created. If SAP created it by default, it's standard; if you created it based on customer requirements, it's customized.

Conclusion

This section provides an overview of IDS and non-IDS systems as well as client-independent and client-dependent (customized) data. Understanding these concepts will be important throughout the course.

SAP Client Administration

In this section, the speaker discusses the standard system of client administration in SAP and how to create custom clients. The speaker also explains why it is not recommended to store customized data in the standard clients.

Standard System of Client Administration

  • The standard system of client administration in SAP consists of three clients named triple zero double zero one and double zero double six.
  • It is not recommended to store customized data into these three clients as they contain all the standard data that may get disturbed.
  • Instead, create a new client by copying the custom standard data from triple zero to 100 and then store all your data into 100.

Custom Clients

  • Custom clients can be created by naming them any number between triple zero to triple line, but it should be unique because all it triple zero is there.
  • Do not create another triple zero.

Local and Remote Client Copy

  • Local client copy means within the same system you are copying from one client to another, especially from triple zero to 100.
  • Remote client copy means from some other system you are copying into the 100 of my local client.
  • SCC5 is for client deletion, SCCL is for local client copy, and SCC9 is called remote client copy.

SAP Landscape

In this section, the speaker discusses what an SAP landscape is and why it's important.

What Is an SAP Landscape?

  • An SAP landscape refers to a collection of systems that work together to support business processes.
  • It includes development systems, testing systems, quality assurance systems, production systems, etc.

Importance of Understanding SAP Landscape

  • Understanding an SAP landscape is essential for interview purposes as it's a mandatory question asked during interviews.
  • It helps in understanding how different systems work together to support business processes.

Introduction to SAP Security

In this section, the speaker introduces the three areas of SAP security and explains what user administration is.

Three Areas of SAP Security

  • The three areas of SAP security are user administration, role administration, and authorization administration.

User Administration

  • User administration is a daily activity job that involves creating, modifying, and deleting users.
  • It's important to understand user administration as it's one of the major topics in SAP security.

User Maintenance

In this section, the speaker discusses user maintenance and its different activities. The process involved in user administration is also explained.

User Maintenance Activities

  • User maintenance includes user creation, modification, deletion, lock and unlock, copy, and password reset.
  • T-code SU01 is used for user administration to perform all these activities.

Process Involved in User Administration

  • The process involved in user administration requires filling out an SAP access form by the user providing all their details.
  • The form needs to be approved by the reporting manager and role owner before it goes to the security team for creating a new user ID.
  • Manager approval and role owner approval are required in some companies while only manager approval is needed in others.
  • Security team creates the user ID after approvals are obtained from managers and role owners.

SAP Access Form Details

  • The SAP access form requires details such as name, email ID, phone number, department name, supervisor name, employee site etc.
  • It also requires specifying which systems are required such as ECC BW Solman PI Bob etc., along with approvals taken for transactions or roles required.
  • A brief description of business need for the role or transaction is also needed along with obtaining manager approval along with completed form initiation service certificate.

User Administration Process

In this section, the speaker explains the process involved in user administration and how to create a user ID.

User Administration Process

  • The form is filled out and sent for approval through email and role owner approval. Then it is scanned if it was filled manually or attached in an email with all the approval mail trails and sent to the security team.
  • The security team creates the user ID, provides the password to the user, and closes the request.

Creating a User ID

  • Use command SU01 to create a new user ID.
  • Enter the user's first name and last name as per naming convention standards. For example, combining Balataran Murali's name would result in BA LA MU as their user ID.
  • Remember that maximum length of a user ID is 12 characters and follow naming conventions while creating one.
  • Fill out all details such as first name, last name, academic title, format, function, department, room number, floor building from SAP access form when creating a new user ID.

Tabs in User Administration Screen

  • There are several tabs visible on screen which are important to remember since you will see this screen daily at least 10 times a day or more depending on your job experience level.

SAP User Creation

In this section, the speaker explains the symbols used in SAP and provides an overview of the tabs available when creating a user. They then go on to explain each tab in detail, starting with the Address tab and moving on to Login Data and S&C.

Symbols Used in SAP

  • Symbols are self-explanatory in SAP.
  • A blank sheet indicates "here".
  • A pencil symbol indicates change or modify.
  • Goggles indicate display.
  • Dustbin symbol is for delete.
  • Xerox copy, lock, and unlock symbols are for password reset.

Tabs Available When Creating a User

  • There are 10 tabs available when creating a user.
  • The tabs are Address, Login Data, S&C, Defaults, Parameters, Roles, Profiles, Groups, Personalization and License Data.

Address Tab

  • The Address tab contains details such as first name, last name, department function etc.
  • Only last name is mandatory to fill out.

Login Data Tab

  • The Login Data tab contains four important fields - user type, password initial password (mandatory), user group and validity period.
  • User type will be dialogue by default under login data tab
  • Initial password is the first password set for any user and is mandatory.
  • Only last name and initial password are mandatory fields in SAP while creating a user.

S&C Tab

  • The S&C tab stands for Secure Network Communication and is used if you enable this feature.

User Administration

In this section, the instructor explains how to manage user administration in SAP.

SNC and Password Management

  • If SNC is activated, the system will not ask for a password during login.
  • With SNC enabled, you can skip the password status without skipping the password itself.
  • SNC is inactive by default on application servers but can be activated to skip passwords.

Defaults and Parameters

  • Login language, decimal notation, date format, time format, output device (printer), and time zone are all defaults that can be defined.
  • Parameters control user behavior and allow for customization of screen color.

Roles and Profiles

  • Roles and profiles reveal what authorizations a user has.
  • Validity from and validity to periods are automatically filled when assigning roles.
  • User validity is different from role validity.

Security Measures

  • When logging in for the first time, users must change their password to prevent misuse of their ID.
  • Users are only authorized to perform tasks assigned to them based on their role.

Conclusion

  • The basics of user administration were covered in this session with more details to follow in future sessions.

Logging into the System

In this section, the speaker explains the steps to log in to the system and how password asking screen will be skipped if S&C is activated.

Steps to Log in

  • Click on system name
  • Enter user ID and password
  • Log in to the system

Password Asking Screen Skipped with S&C Activation

  • Password asking screen will be skipped if S&C is activated

Meeting Schedule and Doubts

In this section, the speaker discusses meeting schedules and asks for doubts.

Meeting Schedule

  • Discusses meeting schedule for tomorrow
  • Asks about availability in morning sessions
  • Proposes 10 or 11 am as a possible time for meeting

Doubts

  • Asks if there are any doubts
  • No doubts from Vashanthi
  • Nilu has no doubts

[#](no timestamp available) Conclusion

The transcript ends without any further discussion.

Playlists: SAP Security by Sridhar Gajulapalli
Video description

SAP Client Administration