Client Administratrion

CLIENT ADMINISTRATION

A client is an independent business unit with in R/3 system. It could be different independent branches with in company. Client is the highest organizational unit. Data belonging to one client may not be shared or viewed by another client. Client is represented by digit number from 000 to 999 which hold some data with authorization in which users will work.

Data in the R/3 are classified as Client Dependent and client independent. 

Client Independent data: - The data on client is accessible by all other client in SAP R/3. 

Client dependant data : It is the copy of client independent with the difference being that the data is client dependant. The data on this belongs to client only.

After successful installation of SAP R/3, the system will have three clients 000, 001 and 066.

Client 000 contains the client independent data of the R/3 system and a test company with standard customizations and environment setting. The data on client 000 is accessible by all other clients in the system. Special administrative task such as language supplement are done in client 000 as user SAP* or DDIC.

Client 001 is a copy of client 000 with the difference being that the data is client dependant. Data in this client will belongs only to client 001. 

SAP comes with some pre configure clients. They are 000, 001 and 066 in non IDES (Real time) and in IDES (version for Training) also have client 800, 810, 811, and 812 which contain the IDES data.

Client 066 is the SAP remote support client. Members of the early watch team use this client to log on to your system and to gather the statistics they need to write the preventive performance reports they send their appreciative customer.

Along with the standard clients SAP also come with some standard users. Users and their configuration such as password, master record etc is client independent.

Client 000 and 001 come with standard user SAP* and DDIC with standard passwords 06071992 and 19920706 respectively.

When ever you create a new client in the SAP system, the standard user comes with standard password as “pass”.

A client without data needs approximately 150-200 Mb space in the database

LIST  OF TRANSECTION CODES FOR CIENT ADMINSTRATION

SCC1          CLIENT COPY WITH SPECIAL FUNCTION

SCC3 CLIENT COPY LOG

SCC4 CLIENT ADMINISTRATION 

SCC5 CLIENT DELETION

SCC7 CLIENT IMPORT POST PROCESSING

SCC8 CLIENT EXPORT

SCC9 REMOTE CLIENT COPY

SCCL LOCAL CLIENT COPY.

CREATION OF CLIENT

TRANSECTION CODE  SCC4

SCC4 transaction is used to create client. When you give the transaction code SCC4 the screen will show like this

Click on display change option you get the screen 

Click on new entries

Enter the Details

In above screen fill the displayed form the details are as under:

Client   <500> <name of company for which you are creating this new client in system>

City      <enter the city where the company is located>

Logical system   <        > leave it blank

                (Information contained in SAP R/3 can be distributed to other system all over the world functioning independently from each other. SAP developed a technology called ALE (Application Link Enabling) which allows remote system to communicate and exchange data if they were integrated to logical system. This field pertaining to ALE only).

Std Currency <give the currency of company in which they work>

Clint role        < option are             1. Customizing

                                                             2. demo

                                                             3. production

                                                             4. training/education

                                                             5. test client

                                                             6. SAP reference

BASIS Roles and Responsibility

OVERVIEW FOR SYSTEM ADMINISTRATOR


This chapter is about the roles that a system administrator plays. These roles cross all Functional areas, and the number and intensity of the tasks depends on the size of the Company. In a small company, one person can be the entire system administration Department. In a larger company, however, this person is probably part of a team. The purpose of this “definition” is to help clarify the roles of a system administrator. This chapter is a list of commonly used system administration terms and their definitions. At the end of this chapter is a list of 14 R/3 System guidelines, which a system administrator must be aware of while working with the system. Sample guidelines include:


* Keep it short and simple (KISS)
* Use checklists
* Do not allow direct database access


ROLES OF R/3 BASIS ADMINISTRATOR


Depending on the size of the company and available resources, R/3 administrator(s) may range from one person to several specialized people in several departments. Factors that affect an R/3 system administrator’s tasks, staffing, and roles:

* Company size
* Available resources (the size of the Basis group)
* Availability of infrastructure support for:
* Desktop support.
* Database
* Network
* Facilities

The R/3 system administrator may wear many hats both in or directly related to, R/3 and indirectly or external to R/3.

WITH IN R/3 SYSTEM
* User administrator
* Set up and maintain user accounts
* Security administrator
* Create and maintain SAP security profiles
* Monitor and manage security access and violations
* Maintain the system’s health
* Monitor system performance and logs
* Transport administrator
* Transport changes between systems
* Manage change requests
* Batch scheduler
* Create and manage the scheduling of batch  jobs
* Backup operator
* Schedule, run, and monitor backup jobs of the SAP  database and any required operating system level files
* Disaster recovery technical manager
* Create, test, and execute the SAP disaster recovery plan
* Apply SAPNet R/3 note fixes to programs
* Data Dictionary (DDIC) manager
* Change the Data Dictionary (when applicable)
*  Data Base Administrator (DBA)

EXTERNAL SUPPORT TO R/3

* DBA for the specific database on which the system is running
* Manage database specific tasks
* Maintain the database’s health and integrity
* Operating system administrator
* Manage the operating system access and user IDs
* Manage operating system specific tasks
* Network administrator
* Manage network access and user IDs
* Manage network support and maintenance
* Server administrator
* Manage the servers
* Desktop support
* Supports the user’s desktop PC
* Printers
* Facilities
* Manages facilities-related support issues, such as:
   . Power/utilities
   . Air conditioning (cooling)
* Physical server access

QUALITY OF BASIS ADMINISTRATOR

An R/3 system administrator should:

* Have a proper attitude
* Protect and safeguard the system.
The system administrator is the guardian of the system.
* Know when to call for help
* The ability to know when you need to get help is a strength.
* The weakness is not knowing when to get help and getting      into trouble.
* Be willing to work the hours required to support the system
*Certain tasks must be done after hours or on weekends to  avoid disrupting normal business operations.
* Be technically competent
* When necessary, the company must invest in training for  the Basis staff.
* You must also take responsibility for your own training and  education, whether your company pays for it or not.
* Be a team-player
* The system administrator will have to work with various  functional groups, users, the IS staff, and others to  successfully complete the necessary tasks.

Tips while work

When working on an R/3 System:

* Protect the system
* Do not be afraid to ask for help
* Network with other customers and consultants
* Keep it short and simple (KISS)
* Keep proper documentation
* Use checklists
* Use the appropriate tool for the job
* Perform preventive maintenance
* Do not change what you do not have to
* Do not make changes to the system during critical periods
* Do not allow direct database access
* Keep all non-SAP activity off the SAP servers
* Minimize single points of failure 
* Everything you do as a system administrator should be  focused on protecting and maintaining the system’s  integrity. 

* If the system’s integrity is compromised, incorrect decisions   could be made based on invalid data.
* If the system cannot be recovered after a disaster, your  company could be out of business.
* The system administrator must have a positive,  professional  attitude.
* If the system administrator has less than this attitude,    critical tasks may not be properly completed (for example,    backups may not be taken as scheduled and backup logs  may not be checked, which reduces the chances for a  successful recovery).  

* System administrators should maintain a “my job is on the  line” attitude. This attitude helps to ensure that  administrators focus on maintaining the integrity of the  system. The company may not survive if the system crashes  and cannot be recovered.
* The system must be protected from internal and external  sources.
* R/3 is so large and complex that one person cannot be  expected to know everything. If you are unsure which task to  complete or how to complete it, you could make a mistake    and cause a larger problem. 

* Mistakes within the system can be expensive. Certain things  cannot be “undone,” and once set, are set forever.
* The only way to learn is to ask. There are no dumb questions —only dumb reasons for not asking them.