What are the transaction codes related to client operations in SAP ?
Following Tcodes which are useful for various client operations in SAP.
SCC4 : This transaction is used to list all the clients that are present in the SAP system. This also includes details like :
- Last changed date of the client
- Last changed by
- Logical system name associated with the client
- Client role
All the client details that are available in SCC4 are present in the T000 table in the backend.
SCC5 : Tcode used to delete a client from an SAP system
SCCL : Tcode used to perform local client copy in SAP system
SCC9 : Tcode used to perform remote client copy in SAP system
SCC3 : Tcode used to monitor client copy progress
SCC8 : Tcode used for client export
SCC7 : Tcode used to perform client import post processing
activities
What is a Client in SAP
What is a client in SAP?
Client is self contained unit in commercial, organizational and technical terms.
It has its own user master data and set of table key ranges.
There are 2 types of data in SAP
- Client specific data
- Cross client data
What is the difference between client specific and cross-client data?
Client specific data means data such as user master and application data which belong to a specific client only.
Cross client data is not specific to any client. It is the data that belongs to all clients. It means data such as cross client customizing and all repository objects which affects the whole SAP system.
What are the different client roles?
Following are the different client roles :
C Customizing
D Demo
E Education / Training
P Production
S SAP reference
T Test
How to avoid TIME_OUT dumps in SAP system ?
These TIME_OUT dumps usually occur if the program has exceeded the maximum permitted runtime without interruption. After this program will get terminated and in ST22 a dump will get generated.
Usually SAP system will terminate the program after permitted runtime to make the work area available to other users who may waiting and to prevent a work area being blocked unnecessarily long time
In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted runtime without interruption. By default this value is set to 600 seconds. However, if you are frequently encountering more dumps in SAP system due to this, you can consider increasing this value to 3600 seconds to avoid this issue.
What is Change and Transport System(CTS) in SAP ?
Change and Transport System (CTS) is the tool provided by SAP for the creation, documentation and distribution of changes within a system landscape.
CTS comprises of Change and Transport Organiser (CTO) : This provides several functions to facilitate software development
Transport Management System (TMS) : This is used to setup transport routes in the landscape. This provides functions to perform organize, monitor and perform transports within the landscape
Transport Tools (R3trans and TP) : These are the tools that are used by SAP at operating system level to communicate with SAP, database and the files generated during the export process.
The transport control program (TP) is a utility for provided by SAP for managing transports and to handle release upgrades. This utility is inturn called by other programs like CTS, TMS and Upgrade control program (R3up)
R3trans is a transport program provided by SAP to handle transports between different SAP systems and for the release upgrades. R3trans is usually not called directly and it is called mostly by Transport control program(TP) and Upgrade control program(R3up)
How to schedule Basis standard jobs ?
How to schedule Basis standard jobs ?
Goto transaction SM36 and click on "standard jobs" pushbutton. This inturn displays standard jobs screen. Here select all the jobs and click on "default scheduling" push button to schedule all of them as per their default schedule.
What is the need of scheduling basis standard jobs ?
Standard jobs are the jobs that should run regularly in the SAP system. These jobs will perform housekeeping like deleting old spool requests (thus avoiding spool overflow), deleting old background jobs/logs/updates/batch input sessions/ABAP short dumps, collecting operating system/database level statistics (used for workload reporting) etc
What are the Standard jobs that should run in an SAP system & their significance ?
SAP_CCMS_MONI_BATCH_DP : Internally this job runs
RSAL_BATCH_TOOL_DISPATCHING report. This job dispatches monitoring architecture methods
SAP_COLLECTOR_FOR_JOBSTATISTIC : Internally this job runs RSBPCOLL report. This job generates run time statistics for background jobs
SAP_COLLECTOR_FOR_PERFMONITOR : Internally this job runs RSCOLL00 report. This job collects data for the performance monitor
SAP_COLLECTOR_FOR_NONE_R3_STAT : Internally this job runs RSN3_STAT_COLLECTOR report. This job will collect non-abap statistic data (Distributed Statistic Records - DSR)
SAP_REORG_ABAP_DUMPS : Internally this job runs RSSNAPDL report. This job cleans up old abap short dumps
SAP_REORG_BATCH_INPUT : Internally this job runs RSBDCREO report. This job cleans up old batch input sessions
SAP_REORG_JOBS : Internally this job runs RSBTCDEL report. This job cleans up old background jobs
SAP_REORG_JOBSTATIC : Internally this job runs RSBPSTDE report. This job cleans up old data from the run time statistics of the jobs
SAP_REORG_ORPHANED_JOBLOGS : Internally this job runs RSTS0024 report. This job cleans up orphaned job logs. The logs that cannot be deleted by RSBTCDEL report (i.e SAP_REORG_JOBS), remains as orphans which will be deleted by this job.
SAP_REORG_SPOOL : This job internally runs RSPO0041 report. This job deletes old spool data
SAP_REORG_XMILOG : This job internally runs RSXMILOGREORG. This job deletes XMI logs
SAP_SOAP_RUNTIME_MANAGEMENT : This job internally runs RSWSMANAGEMENT report. This job does the SOAP runtime monitoring
SAP_REORG_UPDATERECORDS : This job internally runs RSM13002 report and this deletes old update records
SAP_REORG_BATCH_INPUT : Internally this job runs RSBDCREO report. This job cleans up old batch input sessions
SAP_REORG_JOBS : Internally this job runs RSBTCDEL report. This job cleans up old background jobs
SAP_REORG_JOBSTATIC : Internally this job runs RSBPSTDE report. This job cleans up old data from the run time statistics of the jobs
SAP_REORG_ORPHANED_JOBLOGS : Internally this job runs RSTS0024 report. This job cleans up orphaned job logs. The logs that cannot be deleted by RSBTCDEL report (i.e SAP_REORG_JOBS), remains as orphans which will be deleted by this job.
SAP_REORG_SPOOL : This job internally runs RSPO0041 report. This job deletes old spool data
SAP_REORG_XMILOG : This job internally runs RSXMILOGREORG. This job deletes XMI logs
SAP_SOAP_RUNTIME_MANAGEMENT : This job internally runs RSWSMANAGEMENT report. This job does the SOAP runtime monitoring
SAP_REORG_UPDATERECORDS : This job internally runs RSM13002 report and this deletes old update records
What is the difference between Config Tool and Visual Administrator tools in SAP?
Config Tool and Visual Administrator(VA) are the administration and configuration tools in SAP Netweaver AS Java.
What are the prerequisites and uses of config tool ?
The prerequisite for the config tool is database must be running, as this tool is used to maintain the SAP Netweaver AS Java settings in the database. It is not necessary that Java should be running to use config tool.
Uses of config tool :
- The Java Virtual Memory(JVM) settings can only be maintained with the config tool.
- Configuration of services and managers can be done with config tool
Limitations of Config tool :
- Remote configuration cannot be done by Config tool
- Start or stop of java cannot be done through config tool
- Change of parameters at run time is not possible
What are the prerequisites and uses of Visual Administrator ?
With visual administrator, we can logon to the P4 port of the AS Java. Hence both database and java should be running. This is the prerequisite for VA.
Uses of Visual Administrator :
- Configuration of services and managers can be done
- Remote configuration can be done ( It means VA can be installed and used for configuration in any host on which SAP Netweaver AS JAVA is not installed
- Starting and stopping services can be done
- Stopping an SAP NW As java instance can be done
What is the difference between Config Tool and Visual Administrator tools in SAP?
- Java Virtual Machine parameter settings can only be done through Config tool. VA cannot be used for this
- To use VA, SAP Netweaver AS Java should be running but for config tool it is not required
- Changes to selected parameters can be done at run time through VA, which is not possible with Config tool.
- AS Java can be started/stopped by VA which is not possible by Config tool
- Remote configuration can be done by VA but not by config tool
Update got deactivated. What are the reasons for update deactivation. How to activate the update?
Update status check :
Update status can be checked in transaction SM13.
Reasons for update deactivation :
Update will get deactivated in cases of serious database problems.
Some of the examples of update deactivation and solutions for those are given below :
1) Update will get deactivated when oraarch is full
Solution : Trigger archivelog backup and ensure sufficient space is left in oraarch and then activate the update manually
2) When some critical tablespaces are 100% full and database is not able to perform some operations
Solution : Monitor the database and findout the tablespaces which are 100% full. Add necessary datafiles and ensure there is enough free space left out in them. Then activate the update manually
How to activate or deactivate an update in sap ?
Use transaction SM14 and goto update tab. There update status can be viewed with a push button. If it is in deactivated status, click it to activate and viceversa.
How to switch off automatic update deactivation ?
In RZ10, set the parameter rdisp/vb_stop_active to 1 and activate the profile to switch off automatic update deactivation incase of database problems.
How to troubleshoot, if update got deactivated ?
Please perform the following steps if udpate got deactivated :
- Check all the tablespaces and ensure figureout if any tablespace is 100% full. If so, add necessary space and activate the update as mentioned above
- Check if oraarch is full. Trigger archivelog backup and ensure there is enough space and activate the update again
- Check SM21 log and ST22 dumps
- Check workprocess trace for any other issues
What is the difference between dynamic and static parameter in SAP
In SAP, parameters are used to set the configuration and define the functionality of an sap system like number of workprocesses, buffer size, locktable size etc.
Basically there are 2 types of parameters :
- Static
- Dynamic
Static are the parameters those won't take effect immediately the value is set. Restart of an sap system is required for them to take effect.
Dynamic are the parameters those will take effect immediately in the run time. Restart of an sap system is not required for them to take effect.
Parameter can be differentiated whether it is dynamic or static by checking in RZ11 transaction of SAP.
In Rz11, type the parameter and display it. In the screen , there will be a check box with description as "Dynamically switchable". If that check box is ticked, it means that it is dynamic parameter and value can changed in run time without restart of the system. If it is not ticked, then it is static parameter and it needs restart of a sap system for the changes to take effect.
Subscribe to:
Posts
(
Atom
)
