Roles & Responsibilities of BASIS Consultant
Ø SAP application server monitoring, ABAP dump and system log
analysis.
Ø Performance tuning
Ø Database maintenance , Database backup schedule and restore
Ø R/3 solution manager installation, etc.
Ø SAP license maintenance.
Ø SAP landscape, transport management system installations, etc.
Ø Client creating, client copying, client deletion, etc.
Ø Creating user, assigning roles , locking and unlocking users,etc
Ø Background jobs scheduling, job monitoring, job deletion, etc.
Ø Profile and operation mode maintenance
Ø Applying support patches, upgrading and installing add-ons
Ø SNOTE applying and removing errors.
Ø System copy, System refresh, etc.
SAP SYSTEM LANDSCAPE
Clients & Their Role
Ø A client is
organizational and legal entity in the sap system. All the business management
data is protected here because other clients cannot access them.
Ø The main
objective of the client is to keep the data isolated.
Ø The data in a
client can be only visible within that client.
Ø A client has
its own separate master records and own set of "tables"
v Each system has a specific role within the system landscape and
there is a configuration for each role. As well, each client in a system has
its own settings.
System Settings in a Two-System
Landscape
Ø Development
system(DEV)
Ø Production
System(PRD)
v The client settings define the Customizing and development
functions in the SAP System
Description of Clients
in the Development System DEV (Two-System Landscape)
Ø 000:
SAP standard
This
client is used to set up new "neutral" clients by client copy.
Do not change or delete this client.
Ø 001: SAP standard
This
client is used to set up new "neutral” clients by client copy. Do not change or delete client 000 or client 001.
Ø 066: Early Watch
This
client is purely a service client that enables SAP to access remotely the
customer system with regard to analyzing errors and performance. You must not
change or delete this client.
Do not change or delete this client.
Ø 100 : sandbox
Changes
and transport for client specific object is set for option 4 which restrict
this client to make
Changes
without automatic recording and no transport allowed.
Ø 110 : ABAP
Ø The best practice while creating
ABAP client is to assign option 2 which is cross client object –allowed to make
changes.
Ø 120 : Golden client
Ø The best practices while
creating Golden client is to set option 2 for client specific object and that’s
automatic recording of changes. This client is considered as neat and clean client
and only well configured objects are kept into this client.
Client Roles
This attribute indicates the role of the
client in your R/3 system.
Possible roles are:
1.
Production
client
2.
Test
client
3.
Training
client
4.
Demo
client
5.
Customizing
client
6.
SAP
reference client
This field should be maintained by the
customer for documentary
Purposes. It is particularly important for the
production client.
Production clients and SAP reference clients
are protected from the
Client copy tools, including "Copy by
Transport Request"
(Transaction SCC1).
There is corresponding protection from the
automatic Customizing
Distribution and other tools.
In a production client, customizing settings
that can be maintained
As "current settings" are excluded
from a client lock or transport
Connection; this means current settings (e.g.
exchange rates,
Posting periods) can always be maintained in a
productive client
Without recording changes. Other clients
usually require a transport
Request.
No comments:
Post a Comment