The transport process basically consists of exporting of objects out of the source SAP system and importing them into the target SAP system/s. TMS Stands for Transport Management System The CTS components play an important role in the overall development and customization environment. Get help for your Basis problems Do you have a SAP Basis Question? SAP Basis Admin Books SAP System Administration, Security, Authorization, ALE, Performance Tuning Reference Books. SAP Basis Tips SAP BC Tips and Basis Components Discussion Forum. Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES.
In this topic, we described about the below sections -
- Client Administration
- Data Classification
- Default Clients
Client is defined as a self-contained business entities or independent accountable business units in commercial, organizational and technical terms.
One Client is normally referring to one user/customer in SAP system. Client is generally used for multiple logins on one instance in the SAP system. Once customer maps to only one client at a time. Multiple/number of clients can be created on single instance.
One user/customer with one client can't able to see the data of another user/customer on the other client which provides isolated and security. There is no need to install separate software’s for each user/customer.
Clients can be created from 000-999 in SAP system. Multiple clients can be created by managing SAP system landscape for DEV, QA and PROD team.
SAP system and resources can share to many users like we can have client for dev team, client for testing team and client for PROD.
Client Contains -
Transport Issues In Sap Basis Accounting
- Application Data- Data that are stored in the database tables.
- Customizing Data- Data created by customers when customizing their systems.
- User Master Record- Defines the authorizations assigned to a user.
Data Classification -
Data in the database are classified as two types.
- Client Independent Data/Cross client data
- Client Dependent Data
Based on the below two types, client have differentiation about the data accessing and displaying.
Client independent data / Cross client data -
Data created on any client within the system. Data can be accessible from any client. Data is not specific to any client and it is belonging to all the clients.
Ex: screen data, transaction data, repository data and dictionary data.
Client dependent data / Client specific data -
Data created on the specific client and can be accessible through same client.
Ex: user data, authorization data, application data.
Client Roles -
| Role | Description |
|---|---|
| C | Customizing |
| D | Demo |
| E | Education / Training |
| P | Production |
| S | SAP reference |
| T | Test |
Default Clients -
SAP System comes up with three standard default clients.
- 000 - Master Client
- 001- Copy of the Master Client
- 066- Early watch client
000 – Master Client -
000 clients are available immediately after installing R/3 System. Client is called as a master client. This client has client independent settings.
This client contains test company’s simple organizational structure and includes all applications parameters, settings, configurations and transactions etc. This client is normally used in business environment.
001 – Copy of Master Client -
Client 001 is called as Copy of Master client including the test company. Client 001 used to create new clients normally. Client 001 settings are client independent if they are customized or configured.
Client 001 can be customized to move it to the PROD environment. In general, users mostly use 001 clients to create a new client. If the client 001 is customized, it won’t behave like master client.
066 – Early Watch Client -
Client 066 is called as early watch client. Client 066 used to perform early watch service for customer systems. Early watch service is diagnosis and monitoring service for solution monitoring of SAP and non-SAP systems.
Early watch service triggers alerts and the alert may contain performance issue, database administration related issues etc.
Client Management Transactions -
| TCODE | Description |
|---|---|
| SCC1 | Client Copy-Special Selections |
| SCC2 | Client transport |
| SCC3 | Client copy log |
| SCC4 | Client Administration (Create/ Change / Display / Edit clients) |
| SCC5 | Delete Client copy |
| SCC6 | Import Client |
| SCC7 | Post Client Import |
| SCC8 | Export Client |
| SCC9 | Remote Client Copy |
| SCCL | Local Client Copy |
Sap Basis Tutorial
Q1) In SP01 what is the difference between print directly & print with changed parameters?
1) The setting that uses spool with “Print directly to the printer.” You might choose this setting if you have a lot of jobs waiting in the spool and want to print something else in a hurry, and is defined for the user-id
For Print a Spool Request with changing its Parameters.
To change the request before printing it, for example, to send the request to a different printer or change the number of copies to print, choose Print with changed parameters. You can change the following settings before printing:
a) Output Device: If possible, only send the output to an output device that uses the same device type as the output device for which the request was originally created. The device type indicates the printer type used, such as PCL.
b) Start Time: To set a later time for printing, choose this button
Q2) If a spool request is in waiting status for a long time, what does it mean?
2) Status Waiting may also indicate that there is a problem with the spool work process that is assigned to a printer. Check the following:
a) Find out which printer an output request has been sent to. To do this, select the relevant spool request in the Output Controller and choose. You can find the printer name in the Output device field.
b) Find out which spool work process is responsible for the printer. Enter the name of the printer to which the output request was sent in the Output Device field on the Devices/serverstab and choose enter. Display the definition and note the SAP application server name that appears in the Print server field. If you have only a single spool server in your SAP system, then you can omit this step.
c) Use the CCMS System Monitor or in transaction SM51 to display the application servers in your SAP system. Check that the application server that you noted from the Print server field is running and that the server offers the service Spool. If the server is not running or if the Spool service is not active, then you have found the source of the problem.
d) If the print server is running and the spool service is active, then check the activity in the spool work process.
In transaction SM51, mark the print server in question and click on Processes. In the process display, look for the spool work process and note the name of the active user. If User SAPSYS is active, this indicates that the spool work process is busy with internal spool activities or is requesting the status of a print request from a host spool system. Choose CPU repeatedly to check the CPU time that the spool work process requires. If the same CPU time is always displayed, then it is likely that the spool work process is waiting for a status query to time out. It is likely that you have to then find the reason for the delay in output request processing.
Q3): If a user wants to reprint his document again what should to do ?
3) The user needs to give the spool request number in sp01 and then print it or Users should have Tx SP02 for their own spool requests (not SP01 which is a BASIS Tx). User can browse & reissue an output request for a particular spool (unless they deleted it, or it time expired and got reorg’d).
Q4): What I have done to use users OS level printer as SAP printer. I mean if a user has given a print if SAP couldn’t able to find printer it will be in error status. In this case I want to reprint that document from users OS level default printer.
4) There are two things for this:
a) You have to define the local printer same as for your OS in SAP and maintain that as local in spad.
b) The user needs to give the spool request number in sp01 and then print it going forward.
or
You could configure a front-end printer (host spool method G) in SPAD. Printer name is generally LOCL. Understand now that you will have more problems by introducing front-end printing, and not fewer. Users will become accustomed to using it and will insist you fix it when some desktop patch or network change breaks it. I know it SEEMs like a good idea; remember I tried to warn you. Host spool method M is a more easily supported alternative (print-to-email and they can use the resulting attachment as they like).
Q5): What are the regular spool problems and resolutions?
5) Many and varied. Users do not typically distinguish between ‘spool problems’ and ‘printing problems’. Make sure the housekeeping j
obs run: https://service.sap.com/sap/support/notes/1411877
When you schedule standard jobs using transaction SM36 and choosing 'Standard jobs', some jobs that are recommended in SAP Note 16083 are missing.
The following jobs are involved:
1. Job name: SAP_CHECK_ACTIVE_JOBS
Report: BTCAUX07
Description: Check Status of Active Jobs
SAP Note: 1169524
2. Job name: SAP_DELETE_ORPHANED_IVARIS
Report: BTC_DELETE_ORPHANED_IVARIS
Description: Delete 'Orphaned' Temporary Variants
SAP Note: 1021775
3. Job name: SAP_REORG_ORPHANED_TEMSE_FILES
Report: RSTS0043
Description: Consistency Check: File System-TemSe, Table TST01 (with Deletion)
SAP Note: 936049
4. Job name: SAP_REORG_PRIPARAMS
Report: RSBTCPRIDEL
Description: Delete obsolete print parameters
SAP Note: 999951
5. Job name: SAP_SPOOL_CONSISTENCY_CHECK
Report: RSPO1043
Description: Consistency check spool/TemSe
SAP Note: 98065
Q6): In my project I had faced a prob in SOLMAN. The system was giving short dump “SPOOL_INTERNAL_ERROR” and while checking it, system was issuing message “SPOOL OVERFLOW”.
6) As the solution I applied resolution provided in SNote no. 48284, which asked me to raise the upper limit for spool requests using TC=SNRO. The complete procedure is:
1. Log on to the system in client 000 and call transaction SNRO.
2. Select the object SPO_NUM and choose the button: Number ranges.
3. On the next screen, choose: Change Intervals.
4. In the “To number” column, change the upper limit of interval 01 to 999,999, for example.
Q7): Sometime printing is working perfectly & then suddenly all printing get stop. We have seen in SAP spool error log is:
“Unable to open file /usr/sap/<SID>/DVEBMGS40/data/009v1WwD.<SID> for writing (error 28)
Errors occurred processing this print request
There may be no printout”.
After restarting it works fine for some time but again printing got stuck.
7) There are 2 things for this:
a) Do TemSe reorganization; remove inconsistencies & Restart SPO processes in SM50.
b) Error in UNIX Index Nodes (Inode stores basic information about a regular file, directory, or other file system object.)
We were facing out of index nodes issue. The directory where all the batch logs were getting accumulated had run out of number of files it could accommodate even though space was available. When we moved the batch logs to another directory issue was resolved.