There is no way to actually hide a client but there is a workaround: delete the entry in table T000
via SCC4. This way, nobody will able to log on to it. To “unhide” it, simply re-create the entry via
SCC4.
8.How can I lock a client?
You can use one of these two: 1) delete the entry in table T000 via SCC4; 2) run tp
locksys/unlocksys at the OS level.
9.How can I determine the size of a client?
You can run a local client copy in “test” mode.
10.How can I see all the available icons in SAP?
Execute transaction BIBS and select Elements -> Icon Overview.
You can use the code that appears on the last column in order to put icons in system messages
(SM02).
11.What happens if I start a dialog instance but the database and SAP services are down on the
central instance?
The SAP_xx and SAPOSCOL services will start.
However, the work processes will end soon after being started.
12.What happens if I start a dialog instance but only the database services are up on the central
instance?
The SAP services will start and so will the work processes. However, because the message server
is down on the central instance users will get the message “No logon possible (no hardware ID
received by message server) when trying to log on. No user logins will work. The “Process List”
in the SAP MMC will stay in yellow.
13.Can I import transports between different R/3 releases?
Read the technical and logical problems SAP reports when doing transports between different R/3
releases.
SAP Notes 126776 and 330267.
14.I lost the password for SAP*. What can I do?
You can delete the record for SAP* in table USR02 as follows:
delete USR02 where BNAME=”SAP*” and MANDT=’XXX’;
commit;
Replace ‘XXX’ for a valid client number.
15.Can SAP be installed on FAT or FAT32 partitions?
No. SAP needs to be installed on NTFS partitions only.
16.How can I quickly check if the passwords for the accounts SAP*, DDIC, SAPCPIC and
EarlyWatch are not the default ones?