SAP Basis Certification Sample Questions

When creating a logon group for Logon Load Balancing, which of the following CANNOT be specified?

A. Maximum allowable response time. B. Maximum number of users who may be logged on to the instance. C. Name of the instance defined for the logon group. D. Maximum number of sessions per user. E. Name of the logon group

Which R/3 System user is used for starting external programs using SAP background jobs?

A. DDIC B. SAP* C. SAPR3 D. SAPCPIC E. adm

Name the R/3 System transaction used for mointoring a spool requests.

A. SM50 B. SM51 C. SPAD D. SP01 E. SM37

Which of the following is authorized to maintain R/3 user id parameters?

A. Only the R/3 system administrator. B. All R/3 users having an account in the same R/3 client. C. Only the user himself. D. Only the R/3 system administrator and the user.

Given a LAN with an R/3 Central Instance with database (Node: host1, Instance Name:DVEBMGS01, SAPSID:C11), and R/3 Dialog Instance (Node: host2), and several R/3 Frontend PC's what is the name of the profile where the SAPDBHOST parameter is defined?

A. C11_DVEBMGS00_host1 B. The SAPDBHOST parameter is defined in the database startup profile. C. TEMU.PFL D. DEFAULT.PFL E. START_DVEBMGS01_host1

Given and R/3 Central Instance with all services installed, using Instance ID01, and having the SAP ID of C11. What is the name of the directory where the work process trace files are written (for Windows NT replace the "/" with "\")?

A. /usr/sap/C11/DVEBMGS01/data B. /usr/sap/C11/DVEBMGS01/log C. /usr/sap/C11/DVEBMGS01/work D. The trace files are written in internal database tables. E. The trace files are written in the home directory of the database.

Which of the following functions is NOT possible using the SAP Online Service System (OSS)?

Answer: (All is possible) A. Execute online searches for R/3 Notes. B. Register problems with the SAP Hotline. C. Lookup SAP training dates and course offerings. D. Register changes to SAP objects. E. Apply for official Internet address from SAP.

How can you automatically logged out users after a certain period of time?

As to save precious SAP resources, it is good to automatically logged users out whose sessions have been idle after a period of time (for example, no activity after 30 minutes or 1 hour).

You can do that in transaction RZ10.

Use the Instance Profile and tick Extended maintenance

The Parameter is : rdisp/gui_auto_logout

If no entry is made for rdisp/gui_auto_logout (in seconds), the frontend is automatically logged off.

If the parameter has the value 0, no automatic logoff.

Save your entries and ensure that the profile is activated.

You need to re-start your SAP instance before the paramaters settings becomes active.

The paramaters applied to all the SAP users that have login to the system.

Currently, there are no parameters where you can exclude a list of SAP users that are subject to this auto logged out by the system.

For those who are using two R/3 instance, you can separate them into two groups, one with the automatic logged out and the other group that will not be subject to automatic logged out.

Adding text to the SAP logon/login screen

Writing text to the SAP logon screen. This is very handy for identifying which SAP system the user is about to log onto, especially non production boxes. You can also warn them here of pending changes, updates or outages. Because it is up while they are typing in their user id and password, users can't claim they missed the system message.

SAP icons like the stop sign and warning signs can also be displayed.

Details can be found in OSS note #205487.

Here are the details :-

Go to Transaction SE61 and select the document 'General text' (selection via F4 help), and create a text with the name ZLOGIN_SCREEN_INFO in the language defined with profile parameter zcsa/system_language.

If the text does not exist in the system language, no output is made.

Note that there is space for 16 lines with 45 fixed-font characters each or for approximately 60 proportional space font characters on the logon screen.

Title lines (can be recognized by means of format keys starting with a 'U') are highlighted in the display.

You may also output icons at the beginning of lines by using an icon code (for example, @1D@ for the STOP icon). You can get a list of icon codes from Report RSTXICON. Pay attention to the codes with two '@' symbols displayed by the report. You cannot include text symbols. The 'include indicator' cannot be used for this function. SUBHINT here.

These can be used on system messages as well.

Changing the SAPGUI Logo on the Right Hand Side

Thanks to the webmaster for :- SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips

Steps to change the default SAP IMAGE on the right hand column of the screen :-

Transaction code - SMW0

X - Binary data for WebRFC application

Hit Enter

Click Execute

Click Settings -> Maintain MIME types

Click the Create button

Fill in :- TYPE : image/gif EXTENSION : .GIF

Click Save

Click Back to the Binary data for WebRFC

Click Create

Fill in :- Obj. name : ZXXXX.GIF Description :

Company Logo

Click Import and specify the filename where your

GIF file is

located.File type is BIN. Finish press the

Transfer button.

If successful, your logo will be shown in the

Binary data for

WebRFC.

Transaction code SM30 - Table/View - SSM_CUST

Click Maintain

Click New Entries

Name Value to be set

START_IMAGE ZXXXX.GIF

RESIZE_IMAGE NO

Logoff and Login again

Receive an ABAP dump with "CNTL_ERROR"

The message "CNTL_ERROR" appear when you are using some ot the SAP enjoy transaction code like ME21N / ME22N / ME23N.

This are bugs cause by the earlier version of the SAPGUI.

To solve it, goto OSS and apply the SAPGUI's latest front end patch to your PC/Laptop.

Black Icon in SAPGUI 6.10

This happened when you did not remove the old SAPGUI before installing the new SAPGUI.

Always used the SAP Remove Frontend and restart your PC before installing the latest version of the SAPGUI.

Spelling Check in SAP

This function is valid for SAPGUI 6.10, and will even work on 3.x versions of SAP in the backend..

Anytime you want to a spell check, just click on the three color circle customizing button and Spelling Check.

The spelling check itself is done by Microsoft Word and SAP Frontend displays the result of it on the status line.

You must install Microsoft Word (at least Office 97) in order to used this features.

Clashing with the display drivers

When your installation is completed normally but the sapgui clashes with the display drivers when you start the SAP R/3.

You double-click on SAP Log-on and after a minute, it automatically (bounces) and re-starts the machine.

Take a look at SAP note 170770 - Blue screen after starting 4.6 GUI

Automatically logged off the frontend SAPGUI

You can set Parameter : rdisp/gui_auto_logout in transaction RZ11.

If no entry is made for rdisp/gui_auto_logout (in seconds), the frontend is automatically logged off.

If the parameter has the value 0, there will be no automatic logoff.

To change the parameter value,

First, display the parameter value with transaction RZ11.

Once in the display screen, you will be able to click the Change Value button to modify your desired value.

Maximum No. Of SAP Session Per User

You set this Parameter : rdisp/max_alt_modes in transaction RZ10.

Add in the above parameter in the Instance Profile - Options Extended Maintenance.

Restart the R/3 instance.

The default maximum no. of sessions in 4.6x is set as 6 session per user.

Most company will reduced the number of session per user but not increase it.

History in SAP front end

The history tab appears in the options tab under LocalData.

If it didn't work, find the .mdb file like SAP_local*.mdb, the path of which should be available in the options tab under LocalData (Directory of local data).

It is always possible to delete the file, so that when the SAP frontend is restarted, it creates the file again and history is back again.

Please make sure to uncheck the enable low speed connection as the history won't work if this was enabled.

Pros and Cons of using SAPGUI with Citrix

I must install SAP client on a Terminal Server (with Citrix). I haven't got any problem with this because it is very easy. Now the clients connect without problems, but on his window has a button that for me is an important problem: Local Configuration Tuning (sorry if is incorrectly translate from spanish).

With this button, the users can change options that can cause problems in this environment. I need a way to eliminate this button and all things that could be important to get a best performance and eliminate errors.

In any kind of IT installation, there will be its pros and cons.

Citrix does work well, although it isn't perfect (but is any man-made application perfect?).

There are good cost savings as well. I mean before Citrix we had laptops issued to each and every one of our 200 IT staff, so that they could work from home. Along with the laptops there was the usual costs from support, maintenance etc.

Now all of them have a basic spec PC at home that has an ADSL connection right to the Citrix server farm. These cost savings are impressive in themselves but when coupled with the other advantages of Citrix - one upgrade point, dynamic load balancing , access to all information (including word documents, powerpoint presentations, pdfs) anywhere in Europe (just read the marketing blurb) etc.

Of course if the Citrix farm goes down or gets corrupted, we're.....well, let's not talk about that...

In summary, the following are the pros and cons of using SAPGUI with Citrix Metaframe:

Pros of Citrix

You only need to load one copy of SAPGUI into the Citrix server.

It save time and manpower during any SAPGUI upgrade as only one copy of SAPGUI need to be loaded on the Citrix server rather than having to un-install and install on every PC again and again.

The Citrix client will be loaded once on the PC of every user.

The PC resources required for using a Citrix SAPGUI is much lower than using the SAPGUI directly.

Cons of Citrix

You cannot control the Display options of the SAPGUI. This means that if one user changes the SAPGUI display options, for e.g. the fonts or color, it will affect all the Citrix SAPGUI users.

Users will not be able to access SAP if either the Citrix or SAP server is down, instead of just SAP if you are not using Citrix. This should not be able major concern as most companies that deploy Citrix have a fall back Citrix server. If one Citrix Server is down, it will auto switch to the other Citrix Server.

Additional cost for purchasing the Citrix Server.

Therefore, whether to use a Citrix server for your SAPGUI will depends on the cost savings on manpower and time against loading the SAPGUI (or upgrading) one at at time.

Disable SAP USERS to logon multiple times

Set the parameter in RZ10.

login/multi_login_users = set to 1 to activate

login/disable_multi_gui_login = you can put a list of users that should be allow to logon multiple times

List the user IDs separated by commas ",".

Do not leave space characters between user IDs.

Restart the R/3 instance to see the changes.

Suppress SAP Multi Login Message

You can suppress the multi login message by setting the parameter in the instance profile.

It is necessary if your company allows a single users to have multiple login and there tends to be cases where users will choose Options 1 which terminates the rest with the same user IDs. This can result in loss of data as the users may have not click the save button.

Use transaction code 'RZ10'.

Parameter name : login/multi_login_users

In this parameter, enter the name of all the users separated by "," comma for which you want to suppress the message while multi login with the same user IDs.

Take note that the multi login counter still counts even though you have suppress the message.

Proper way to delete a SAP client

Here goes:

1. log into the client to delete 2. go into SCC5 and delete client 3. log into another client and delete entry with SCC4 4. reorg database to recover database space.

Actually, if you check "on" the little "Delete Entry from T000" checkbox, you can skip step 3.

One other way of deleting a client which could give significant performance gain and save time is at OS level using - R3trans

To delete a client 200, you have to create a command file "del200" with following entries

Clientremove Client = 200 Select *

Place the command file in /usr/sap/trans/bin

$ cd /usr/sap/trans/bin

$ R3trans w -u 1

e.g $ R3trans -w del200.log -u 1 del200

To check the progress...

$ tail -f del200

Reorg the database post client delete

What is the best way to refresh QA from PRD?

How to make a system copy:

1. Take offline backup of both the server (source and target servers)

2. Verify the backup is successfully done.

3. Run the following command on source system. a. Login as adm b. svrmgrl c. connect internal d. alter database backup controlfile to trace; e. exit; f. Above command will generate a .trc file in /oracle/P01/saptrance/usertrace directory. g. Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file. h. Copy the controlfile.sql to target system. i. Edit the file and replace the entire source SID to target SID. j. Edit the reuse database command with the set database command

4. Copy the aft generated during the backup file from the source system to target system. (/oracle//sapbackup) a. Change all the source to target . b. Only don't change the backup volume name it must be target system . c. Copy the above aft file name line from the source back.log to target.log file.

5. Shutdown the target server instance.

6. From this onwards all the command on the target system only. a. Login as adm b. run the SAPDBA c. select J (Restore/Recovery) d. select B (Full restore and recovery) e. select A (Select backup of type) f. Select the offline backup which you want to restore. g. It will take some time to restore. h. Once the database is restored login as adm and run the i. svrmgrl j. connect internal; k. startup nomount (if the database is already mounted shutdown it using the shutdown command) l. run the following command m. @controlfile.sql (file name of the control file contains the CREATE CONTROLFILE statement) n. After the run the above command it should give the "Statement Processed) o. alter database open resetlogs p. shutdown q. Start the database and SAP services using startup.

7. After this you have to reconfigure the STMS.

8. All the jobs also you have to reconfigure and reschedule.

9. Reconfigure all the printers.

10. If you want to change the Client number then use the local copy tool and remove the original client after successfully import to new client.

Problems with Multi-clients in one SAP Production instance

You are working on group of companies. They don't want to share any data between companies, simply no integration required, therefore mgt wants to have one client for one company that end up having multi-clients in prod instance. However, one of the SAP local guy told you not to continue with this landscape.

Some of the potential problem of using multi-clients in one prod instance are:

1. problems affecting one client immediately affect all other clients. an eg.: 1 client runs a job that fills up a tablespace or file-system.

2. a system problem (system crash) affects all clients immediately. e.g. an Oracle archive stuck will affect all clients.

3. programs/tables are client independent. Individual customers cannot make changes to common programs/client without affecting the others.

4. Poorly written ABAP's will cause bad response throughout the SAP system, affecting all clients. I shudder to think of a situation where the programmer for 1 customer stuffs up and the other customers demand blood!

5. Taking all of this into account, your change management will turn into a NIGHTMARE! especially considering that each customer probably does no care about the other customers, so EVERY change of theirs is the most important one.

The above are some of the problems if you have multi-client in one SAP instance and there are many more arguments.

Problems in Heterogeneous Setup

We Planning to go for hetrogenius setup. Development server - HP-UX11i,oracle9.2,sap47. Production server - SUN Solaris with same oracle and sap version My issue is that, will I face any problems in this setup? Because right now developments are going on HP-UX.

I am not in a hetro-geneous setup. But a similar installation I have already visited, which one of the big installation in Bangalore, they used Sun solaris as dev and HP UX as PRD. But no problems. Logically SAP system just looks for where the data is stored and works on TCP/IP. It just does not matter where the database resides for development and production. The transport mechanism just transports from the development client to productive client. So I assure you 100% you can plan this. This is supported by SAP. You can even plan NT as development machine. It just works fine. But some advantages are available if you have similar systems. 1. When updating patches for a particular os/db combination , you have a chance to see how it works, before trying it on productive system. 2. You learn a lot on installation, sizing, many other related issues at the time of development, so that you can easily sort it our at the time of installation of prd system. The above cannot be told as advantageous, but take a note of these. After all it is a matter of cost + convenience! I am on NT + SQL Server with SAP 4.7 Ent. and its works fantastic without any problems. Post Installation Task after successful R/3 46c

Generally you need to :-

1. import profiles (default, instance, start) into SAP R3 1.1 add/modify instance parameters such as rdisp/max_wp_run, abap/timeout, zcsa/system_languages, and so on...

2. update the R3trans and tp tools with the last ones available on sapnet

3. configure TMS (systems,layer and routes). You can do it with virtual systems if you have only one SAP system

4. update SPAM/SAINT

5. check via Tcde db02 (with refresh option) the available space for TS other than SYSTEM TS.( for the others %used must be less than 90) 5.1 check to see critical objects (table/index) 5.2 extend (via sapdba tools -> option TS administration) all TS which shown critical objectsfor example: PSAPPOOLD + 200M PSAPPOOLI + 100M ... You can get necessary via Note 195446 (for language import) and Note 118823 (for client copy) 5.3 refresh again in db02 and check the %used space

6. import language other than the default (DE & EN) if necessary

7. Client copy

8. configure printer (SPAD)

9. create user

10. change system user password such as SAP* , DDIC, and so on ...

Error you might encounter at the end of client copy :-

"there is a window "change and transport system not configured" Status is cancelled.

To rectify the errors :-

You need to configure CTS via tcde STMS for your SAP system.

If it's your only sap system, then: - configure it as domain controller: run Tcde STMS and accept the default proposed domain controller which is your system - define one or two virtual system (Menu overview-->system then Menu SAP system-->create-->virtual system) - Menu Environment --> transport routes then press F5 and Menu Edit Transport layer to create a "Z" layer for example "ZDEV" Create a transport route between your real sap system and the virtual system by using the two layers: "Z" layer and "SAP" standard layer - save and distribute the TMS configuration

That is the main action you have to do to setup CTS.

SAP Client Copy

Before doing a client copy, you need to prepare the following :-

1. Find the source client space with the client size custom program which can be implemented using the rel. note: Find the space of the client - '0118823'. This will give you the size of the source client.

2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV client based on space requirements also.

3. You can do the client copy by remote or export/import client. Remote method is not preferred if you are doing a large client copy. Do a client export/import.

4. To speed up the export/import, use R3trans export/import for the clustered tables. Please find the rel. notes related to performance improvements for cluster tables in OSS.

5. Do import and post processing. Note: Export may take 10 to 20 hr. for 50gb of data import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on your system performance.

Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process.

Note :-

If it is a fresh installation, do this --

1. SCC4 --> Create client no. and fill other details. 2. Logon to the newly created client with SAP* and PASS as password. 3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client . 4. Preferably do a test run initially to check if it can go well. 5. As a care check space in databases.

Copy users from DEV to PRD

1. Login to the client in your DEV system from where you want to copy.

2. Execute scc8. Select the profile sap_user. Specify the target system. Click on 'schedule as background job'.

3. Specify the background server name i.e. the server name where your DEV system is available.

4. Click on 'schedule job' button. Verify the things and click on 'continue' button.

5. You will have options to specify the start time. Specify to suit your convenience. You can see the log in scc3.

6. Login to the destination client and execute scc6. Specify the request number which was created during scc8. You need to specify only one request number. Other(s) will be taken automatically. Click on 'Prepare import'.

7. Specify the target client and click on 'Import'. Log can be checked in scc3.

SAP Client lock

-----Original Message----- Subject: Client lock

I have two questions :

1. How to lock the client from logon

2. How to see the all the users connected per day (with the activities they have done and resource utilization)

Subject: RE: Client lock

I cannot answer the first straight away, but the second questions, there are many available SAP transactions

use STAT very useful and many options available if you use them correctly.

Subject: RE: Client lock

1. I don't know how how to lock the client, but you can lock the system with "tp locksys " and unlock it with "tp unlocksys ". You can also stop the service, but then no one can login including yourself. However, I had problems with tp locksys when applying some Hot Packages and exporting client. It wouldn't work with system locked. I didn't try, but a simple ABAP that locks and unlocks all the users in table usr02 (with exceptions of yourself, SAP*, DDIC... - of course) might be an interesting idea.

2. STAT transaction

Subject: RE: Client lock

U can lock the system thro "tp locksys" (Transport Utility).

Check the other options of "tp" command for locking the specific client under the system thro "tp help".

Subject: RE: Client lock

With this solution I can lock the whole system, but not specified by client.

Send me in more detail....

Subject: RE: Client lock

There's no way to lock a client. You have to lock all users from loging in of this specified client. The way you do is by user administration setting the lock.

Subject: RE: Client lock

We can lock a client using SCCR_LOCK_CLIENT and unlock SCCR_UNLOCK_CLIENT functions.

Once we run this functions with a client as input , that client will be locked/unlocked. Actually this function set flag '' Client is locked temporarily for client copy" in client maintenance menu. And the client will be available for users other than DDIC and SAP*. If you try to login in that client as any user , system gives message that ' Client locked temporarily'..

SAP Maintenance transport requests work flow

An example of a basic principle and flow is:-

1. A request for a change is submitted to support team

2. Change is done in DEV (if approved) and tested by support team (limited testing only due to lack of productive data)

3. Change is transported to TST

4. User testing takes place

5. User approves or rejects (giving reasons)

6. System manager approves the change to go into PRD

7. Change is transported to PRD

All transports are done by the support team.

If a change is urgent it is transported straight away, if not they are batched up and done once a week.

The Workflow can be controlled by a software like a Lotus Notes database so you can have a record of approval at every step.

Note :-

The system manager is the manager of the support team. The system "belongs" to him i.e. it is his responsibility and he has the final say on what goes into the PRD system. 99.999% of the time he will approves the change, this is mainly a way of keeping him informed of what changes are happening in the system.

Many companies uses the core modules MM, PP, FI, CO. The problem with transporting single transports is that if it is a program, the complete program buffer is reloaded therefore giving a performance hit. Therefore you tend to leave them and just have one performance hit per week (although most weeks there are no program changes). When you are in production the number of transports will settle down to a reasonable figure. Maybe about 10 transports a week, and most of those are material groups (which, although they are user data, they are classed as customising). This rises if you are doing any modifications or changing business processes etc, but 10 is about quite normal for most.

What is a Logical system?

Does anybody know what "logical system" is ??? I have read help in = transaction SCC4 already, but I'm confused more than before ... :-))) = What it is good for ? What is the reason for defining it ?

'logical system' is used to identify an individual client in a system, for ALE communication between SAP systems. That's why you see a field for 'logical system' in the client master data in SCC4 (table T000). You use logical systems in ALE config - this should be documented further in the IMG guide, or SALE and BALE transactions.

Just a note of warning regarding choosing the Logical System name.

I know of one site where it was chosen such that it depended on the actual system name and, therefore, had to be changed after copying production back to acceptance. The process ran for two to three days! I have not examined how the logical system name is used but it would appear that selection should be made carefully to avoid the need for this if the architecture can support it.

Perhaps someone with more experience of this object could comment on its usage and name selection.

yes - you should use a naming convention for the logical system names which includes distinct IDs depending on: System ID (SID), and client number, and maybe also system number if you have more than one instance per host machine. Hostname would be useful too, but I think there's only 10 characters in v3.1x (maybe more with long name functionality in 4.x ??).

eg., in DEV box , sys no 00, client 100, choose something like 'DEV00_100'.

You state that a logical system appears to be nothing more than another label for a client. I think (certainly cannot say I know!) that it is a little more than that: I think it is an externally visible label for a client within a system.

I had interpreted the term "logical" as meaning it had no relationship to a specific instance. That's how I would use the term anyway. I take it from your remarks and others on this thread that it is, in fact, a very instance and client specific label - really very physical and not at all virtual/logical.

I know from experience that the logical system must be defined or you get error messages all over the place during order processing stating the logical system has not been defined. The logical system is defined in the IMG. Don't know the transaction identifier, but in 4.* it is found in the IMG > Cross Application Components > Distribution ALE > Basic settings > Logical systems > Define logical systems. Here the entry is just an identifier and a text entry. As you stated, it is assigned to the Client in Tx SCC4. (The next step in the IMG) I went to the IMG for help. Here is the extract at "Logical systems" level: "Logical Systems. The distribution of systems ( ALE ) makes it necessary to be able to identify every system individually within a network. The "logical system" is used to do this. A logical system is an application system within which the applications are coordinated to work in one database. In the SAP sense of the word, a logical system corresponds to a client. In the following steps, you must define every client as a logical system by first of all defining logical systems and then assigning the clients in question to the corresponding logical systems. Note: Assignments must be unique (that is, a client may only be assigned to one logical system. Several clients must never be assigned to the same logical system."

Reading this it does seem that it is nothing more than another identifier for a "Client".

Running Unix Shell Script within SAP

A short simple FTP script looks like this :-

You see, SAP looks at EXIT STATUS of shell script at the end. EXIT STATUS of 1 leads to batchjob failure (irrespective whether it was a EXTERNAL COMMAND or EXTERNAL PROGRAM). As not much shell-control is available after a FTP session is established till command "BYE", the only option is to redirect stdout (before connection, to a file) and after the session (BYE) perfom grep for certain strings (back to shell). This particular action is good reason to exit with a EXIT STATUS of non-zero.

A short simple script looks like this

#!/bin/sh ftp -n foo > success mount (to check NFS mount is OK)

- Unix > df -k (as above)

Shutdown

- Login as 'root'

- Unix > ps -ef | more

- Unix > sync

- Unix > init 0

- Power down the machine

SAP Database Startup and Shutdown

Startup

- Login as 'adm'

- To interrupt Open Windows 'Shift Control-C'

- Unix > startsap all (this will startup the SAP and database system)

Note :- startsap R3 - will startup SAP only startsap DB - will startup database only

SAP Startup Profile resides in /sapmnt//profile/_DVEBMGS00

Shutdown

- Check if there are any users or processes executing in the SAP System (use transaction code SM50 and SM04 - delete their session before shutdown)

- Login as 'adm'

- To interrupt Open Windows 'Shift Control-C'

- Unix > stopsap all (this will shutdown the SAP and database system)

Note :- stopsap R3 - will shutdown SAP only stopsap DB - will shutdown database only

What is SAP IDES and System Requirement for installations?

System Requirement to install IDES

For installing IDES 46C on a Laptop, you need :-

Pentium 3/Pentium 4 with any CPU

2*40 GB HDD

512 MB RAM

DVD Drive

What is SAP IDES (Internet Demonstration and Evaluation System)?

SAP IDES is a normal R/3 but with lots of DEMO data.

The system that contains several sample companies typifying relevant business processes. It is simple to use and has a variety of master and transaction data, and is used for demos, online/classroom training, and presentations. Potential customers use IDES to trial and test software via Internet.

SAP IDES the "Internet Demonstration and Evaluation System" in the R/3 System, represents a model company. It consists of an international group with subsidiaries in several countries. IDES contains application data for various business scenarios that can be run in the SAP System. The business processes in the IDES system are designed to reflect real-life business requirements, and have access to many realistic characteristics. IDES uses easy-to-follow business scenarios to show you the comprehensive functions of the R/3 System. The focal point of IDES, however, is not the functionality itself, but the business processes and their integration.

IDES not only covers the Logistics area, but also Financials, and Human Resources. It demonstrates how the R/3 System is able to support practically all types of industries, from discrete production through to process industries, from engineering-to-order to repetitive manufacturing. However, IDES is not a sector-oriented model company. The individual processes are based on practice-oriented data for sectors such as Retailing or Banking. The IDES group manufactures products as diverse as elevators, motorcycles, and paints.

IDES is managed by SAP just as any regular business enterprise. SAP regularly updates the IDES data (master data, transaction data, and customizing). IDES also carry out period-end closing and plan with different time-horizons. Transaction data are generated to ensure that the information systems in all areas have access to realistic evaluation data. IDES are constantly implementing new, interesting business scenarios to highlight the very latest functions available in the R/3 System. New functions are represented and documented by IDES scenarios.

Above all, IDES shows you the possibilities of the integrated applications in the SAP System. IDEScover all aspects of a business enterprise, including Human Resources, Financial Accounting, Product Cost Planning, Overhead Management, Profitability Analysis, Planning, Sales and Distribution, Materials Management, Production, and much, much more. IDEShave also integrated document administration and third-party CAD systems within the IDES system. This means that you can call up and display external documents, or access CAD drawings.

IDES shows you how the R/3 System supports production processes, the supply chain, and the efficient usage of global resources. Or perhaps you would like to increase your understanding of just-in-time-production or the integration of the electronic KANBAN system in an MRP II environment? IDES provides the ideal way to learn about areas such as Product Cost Controlling, Activity-Based Costing, or integrated Service Management and Plant Maintenance. How to manage high inflation is just one of the ever-growing number of IDES business scenarios that you can choose from.

SAP IDES Installation Procedure for SAP Install on W2k server

Procedure for installation on W2k server with sp3.

Installation Of SAP 4.6b

System Requirements.

P-III System 1024 MB or 512 MB RAM Minimum 60GB HDD 40 GB Hdd (2GB for WinNT & 38 GB for oracle & SAP) 10 GB Hdd for CD dumps. CDROM drive. Network Card

C:\ - 10GB - Windows 2000 Server - NTFS D:\ - 40GB - Oracle & SAP - NTFS E:\ - 10GB - CD Dumps - NTFS F:\ - CDROM Drive

Install Windows 2000 server in first 10GB partition Computer Name - SAPSRV IP Address - 192.168.1.2 Subnet Mask - 255.255.255.0 Work Group - TEKSOFT Complete the installation & Restart.

Install Service Pack 3 Install All the Drivers Install IE6 SP1

Create two Users as mentioned bellow

Start -> Programs -> Administrative Tools -> Computer Management -> Local Usersand Groups -> Users -> New User

a. First user name TEKADM Give password, disable the already enabled option & enable "Password Never Expires & user cannot change the password option "

b. Second user name SAPServiceTEK Give password, disable the already enabled option & enable "Password Never Expires & user cannot change the password option "

Add the two Users to Administrators Group

Change hostfile

Open C:\Winnt\System32\driver\ect\host file in Notepad & add IP Address and Computer Name in The bottom of file. Save & Exit.

Change the Virtual Memory

C: Min - 512MB Max - 1024MB

D: Min - 2048MB Max - 2560MB

Change the File and Printer sharing properties to Maximize through

Logon as TEKADM Insert SAP-Oracle CD & Select F:\NT\i386\setup & click enter Location of oracle D:\orant & click enter Accept path change & click enter Oracle 8 enterprise edition & click enter (Oracle 8.1.7 will not be supported by SAP Kernel 4.6B) (Oracle 8.1.7 will be supported by SAP Kernel 4.6C only)

After completion of oracle Stop the service "Oracle TNSlistner 80" Select F:\NT\i386\Patchs\8.0.5.2.2\setup & click enter Accept the defaults & complete the installation. Restart the system.

Dump all the export CDs (6 CDs) into E:\dump\db1 - export CD 1 E:\dump\db2 - export CD 2 E:\dump\db3 - export CD 3 (To dump type as E:\dump\db1>Xcopy /e f: & enter) E:\dump\db4 - export CD 4 E:\dump\db5 - export CD 5 E:\dump\db6 - export CD 6

Insert Kernel CD

Select F:\46bker\NT\i386\NTPATCH\R3dllins & click enter This will install patch for NT.

Restart the system. Logon as TEKADM From kernel CD F:\NT\common\r3setup & enter Enter the following

System Name - TEK (must be 3 Letters Capital) Location - C:\users\Tekadm\install (it comes by default) Accept to restart the machine.

Logon on as TEKADM Copy the file "db_ides.r3s" from DB1\IDES\NT\ORA\DB_IDES.R3S (18KB files size) to C:\users\tekadm\install

Start r3setup from C:\users\tekadm\install\r3setup & enter Select "central.r3s" file & enter & Follow as mentioned bellow

System Name - TEK Instance no. - 00 Accept Defaults Directory of SAP system -change to D: RAM of the sys. - Accept the default Location of the KERNEL CD - F: Port no. - 3600 Enter the password of TEKADM two times Enter the password of SAPServiceTEK two times Start the installation. This will come upto

Select C:\users\tekadm\install\r3setup & enter Select "db_ides.r3s" & enter System Name - TEK Instance no. - 00 Accept Defaults Select WE8DEC (default for r/3 4.x system) & enter Oracle dir. - D:

Location of SAP Database specific files

SAP Database Drive

SAPARCH D SAPBACKUP D SAPCHECK D SAPREORG D SAPTRACE D & enter

Location of Oracle Data files

Oracle Data directory drive

SAPDATA1 D SAPDATA2 D SAPDATA3 D SAPDATA4 D SAPDATA5 D SAPDATA6 D & enter

Location Database LOG files

Dir. for LOG files Drive

ORIGLOGA D ORIGLOGB D & enter

Location Mirrored Database LOG files (Change from D to C)

Dir. for LOG files Drive

MIRRLOGA C MIRRLOGB C & enter

Accept the default RAM & enter

Location of export CDs dump

CD name Location Copy destination

KERNEL F:\46bker EXPORT1 E:\dump\db1\1 EXPORT2 E:\dump\db2\2 EXPORT3 E:\dump\db3\3 EXPORT4 E:\dump\db4\4 (Clear this field) EXPORT5 E:\dump\db5\5 EXPORT6 E:\dump\db6\6 & enter

Enter the Password of TEKADM No. of parallel process - 1 Start installation.

Wait for 14 to 15 Hrs & installation will come Upto 91% & will ask for SAPr3 password. Enter the password of TEKADM & enter

This will come upto 95% Open SAP Management Console from desktop & Right click "TEK" & start the service. Wait for the service to start & will change from yellow to green. Come to the r3setup screen & click next. This will bring upto 100% & the installation is over. Exit the r3setup & stop the "TEK"service & Restart the system.

POST INSTALLATION TASKS

After SAP installation, install SAPGUI in the server. (CD 9) Restart the system

Open SAP Management Console & start the sap service.

Start the Sap Frontend from the start\programs\sap frontend\sapsrv.

Logon as Client 000 User name DDIC

Password 19920706 Language en

* Note : Clear this field This means if you already have the CD's copied on the the harddrive you don't need to copy them again..

CD Title------CD Location-----------CD copy to this location kernel--------Dump location1-------clear , don't re copy cd1-----------Dump2--------- -------clear, this field cd2-----------........3-----------------clear cd3-----------.........4----------------clear

How SAP Router Works?

SAProuter examines any incoming data packets, checks the route and authorization and then sends them to their specified targets. The partner that sets up the connection specifies the route (from SAProuter to SAProuter and to the target). This procedure is known as source routing.

If you want a connection, from a SAPgui to an R/3 System for example, to run through a SAProuter, then you need to enter the route in the SAPgui command line.

You can use SAProuter if there is no direct IP connection between the communication partners. SAProuter must be running on a host that is connected to both IP networks. It can then receive data from the SAPgui in one IP network and relay it to the R/3 server in another IP network, and vice versa. Normal IP routing is used between the application programs and the SAProuters.

Connections established using SAProuter have the additional advantage that no end-to-end connections between the participating system are necessary on network level. For example, if accessing a frontend PC on an R/3 server with an intermediate SAProuter, it is not necessary to define the complete path between the two systems at TCP/IP level. It is sufficient if both parties can reach the SAProuter. From an SAP communication viewpoint, this represents a point of concentration in your network that serves as a starting point for each subconnection.

Each subnetwork stored logically behind a SAProuter is therefore reduced to the network address of the SAProuter.

Without SAProuter, the Internet Protocol (IP) addresses must be unique, which cannot always be guaranteed, particularly on international networks.

With SAProuter it is possible to connect two points that have unofficial,or even identical, IP addresses. Therefore, it is rarely necessary to adapt existing address topologies using official IP addresses.

SAP Online Service & Support now only supports SAProuter connections due to these advantages. Because SAP routes all accesses to internal systems (such as SAPNet - R/3 Frontend) and all service connections via SAProuter, the connection between SAP and the customer is reduced to a single SAProuter - SAProuter connection.

Changing the IP address of your SAP Server

Where do you need to change the IP address on the oss site, and how can you configure the saprouter?

You need to check your RFC connections in SM59 and your hosts file.

If you have set up any external ftp connections to your system, you also need to check if they use IP address or hostname.

If the SAProuter runs on the server you are changing the IP address, you must create a customer message for SAP and ask them to change the IP at their site. The IP address of a SAProuter must be from an official range. You must also update your SAProuter data and change the IP on SAPNet (system-data).

In saprouttab you need to adjust the IP as well.

Understanding SAP ITS - Internet Transaction Server

The SAP Internet Transaction Server (ITS) is the essential link between the SAP R/3 system and the Internet. It enables Internet (and Intranet) users to communicate directly between R/3 system to run R/e transactions, remote enabled function modules and reports as Internet applications components. The ITS is one of the cornerstones of SAP's mySAP.com offerings and strategy and integrated into the SAP 6.10 Web Application Server release. The ITS is the key technology behind the following products: Workplace, Employee Self-Service (ESS), Enterprise Buyer Professional (EBP), BW 2.0 Interface, Online Store and Retail Store, and the APO Interface. There are many other SAP products and applications that are based on ITS technology to interface from the Web to SAP R/3.

SAP ITS can handle complementary Web technologies to access data from SAP R/3:

- SAP GUI for Html: SAP transaction screens are dynamically converted to HTML pages

- Web transactions: SAP transactions that can be called from an HTML page (template based mode)

- Web remote function call (RFC): SAP R/3 function module that can be called from an HTML page

- Web reporting: Mechanism for linking to SAP reports and regenerated lists from an HTML page. Web reporting is implemented as a special-case RFC.

- ITS Flow Logic: Events, statuses, and modes used to model the dialog logic of a Web application in "flow files" on the SAP ITS.

SAP R/3 data is accessed via BAPI or RFC. Access to external data providers is also possible.

SAP's Internet applications are known as Internet Application Components (IAC) or Easy Web Transactions (EWT). Both are complete business solutions that allow Internet and Intranet users to access business information in the SAP R/3 system by starting transactions, function modules, and reports from a Web browser. All IACs or EWTs are based on a common infrastructure consisting of two essential components.

SAP Internet Transaction Server (ITS) - The ITS is the interface between the Internet and R/3 and is the runtime engine that links Web server to the R/3 Application server.

ABAP workbench tool - Web Application Builder and/or SAP@Web Studio - WAB is an R/3 ABAP workbench tool and SAP@Web Studio is a PC tool for creating, modifying and managing all ITS objects on which IACs or EWTs are based. These objects include service files, HTML Templates and HTRC language resource files.

The ITS solution to developing Internet applications is based on the premise that there is already a suitable business application solution, which has a stock of transactions, function modules and reports, as well as its own integrated development environment. All that is needed to enable Internet users to access and run these applications is an interface to the Internet. Apart from the general advantages derived from making SAP R/3 business information available over the internet, the ITS solution has many benefits.

These include:

Ease of development - Programmers can develop IACsEWTs using a business application system (R/3), development environment (ABAP Workbench) and a programming language (ABAP), with which they are already familiar. There is also integrated data dictionary support from the ABAP Dictionary and appropriate transaction handling.

Ease of deployment - The ITS solution supports internationalization of applications.

Ease of use - ITS based IACs and EWTs have the same look and feel as any other Web site.

The separation of programming tasks from the visual design aspects is desirable, because both require different skills. In the ITS scenario, the ABAP programmer develops the application in ABAP using the ABAP Workbench in the SAP R/3 system and the user interface specialist handles the design and navigation aspects of the application with design languages like HTML and SAP's HTML Business in either the SAP@Web studio or ABAP Workbench tool, Web Application Builder.

The aim is to create applications that send documents back to the Web browser client in plain HTML format, since this format can be handled by all major browsers. This is important in an environment like the Internet where there is often little control you can exert over client software such as Web browsers. Fit can be controlled; you can also use Dynamic HTML, Java applets, JavaScript, and VBScript in you HTML templates, because the script language is transparent to the ITS.

How does the SAP ITS work?

When an Internet user requests an ITS service by clicking on a URL hyperlink or keying in a URL address in a Web browser to run a IACEWT, the request is processed as follows:

1. The Web browser passes the request to the Web server.

2. The Web server calls the server-specific ITS extension WGate - WGate is the link between the ITS and the Web server. WGate is a Web server extension that encapsulates the various supported HTTP server interfaces such as: CGI (Common Gateway Interface), NSAPI (Netscape Server Application Programming Interface), ISAPI (Internet Server Application Programming Interface) in a transparent manner that passes the requested data to the ITS AGate component.

3. WGate forwards the request to the ITS server process called AGate (which may or may not reside on the same machine.)

4. AGate is the link between the ITS and the SAP R3 application server. AGate is the core processing component of the ITS. It receives Web browser request from WGate and communicates with the SAP R3 application server via the DIAG or RFC protocol.

5. AGate then processes the requests, and sends all relevant details (including logon information) to the SAP R3 system, which either starts the first dialog step of a new transaction of submits further data for the next dialog step of a transaction already started.

6. SAP R3 starts the transaction for the service requested and sends the screen output to AGate.

7. When the dialog step has finished, AGate retrieves the result from SAP R3, and is responsible for session management, including mapping of SAP R3 screen or function modules to HTML, web session timeout handling, SAP R3 connection management and generation of HTML documents that are sent back to the Web browser client.

8. AGate forwards the formatted HTML page to WGate.

9. WGate forwards the formatted HTML page to the Web server.

10. The Web server sends the formatted HTML page to the Web browser, where it can be viewed by the user.

The ITS is downward compatible, therefore the ITS release must be the same or higher than the SAP R/3 kernel release.

There are three restrictions to this approach:

1. The SAP R3 release must be at least version 3.1I or higher.

2. You can only use those Internet Application Components that were shipped with the SAP R3 release you are using.

3. ITS 6.10 should only be installed in front of an SAP E3 kernel release 6.10 (e.g. CRM 3.0)

*** ITS 4.6D Server Platforms ***

>>Wgate Microsoft NT 4.0 Server Microsoft Web Server (ISAPI) Netscape Web Server (NASPI) Apache HTTP Server (Apache Module) Any CGI Web Server (CGI) Microsoft windows 2000 Server Microsoft Web Server (ISAPI) Linux/Intel Apache HTTP Server (Apache Module)

>>Agate Microsoft NT4.0 Server Microsoft Windows 2000 Server SAP@Web Studio Microsoft NT 4.0 Workstation Microsoft Windows 2000 Workstation

*** ITS 6.10 Server Platforms ***

>>Wgate Microsoft NT 4.0 Server Microsoft Web Server (ISAPI) Netscape Web Server (NASPI) Apache HTTP Server (Apache Module) Any CGI Web Server (CGI) Microsoft windows 2000 Server Microsoft Web Server (ISAPI) Microsoft XP Server Linux/Intel Apache HTTP Server (Apache Module)

>>Agate Microsoft NT4.0 Server Microsoft Windows 2000 Server Microsoft XP Server SAP@Web Studio Microsoft NT 4.0 Workstation Microsoft Windows 2000 Workstation Microsoft XP Server

SAP Profile Generator tables

We maintain profiles in a Development system using Profile Generator, but only transport the authorisation profile and not the activity group to Staging/Production.

We are about to refresh the Development system with a copy of Production. What tables do I need to export from Development prior to the refresh, and later re-import, to ensure that Profile Generator is able to maintain the activity groups created in Development?

oh, and maybe these tables for profile generator stuff...... (from top include for PFCG) 000010 function-pool rhum. 000020 000030 tables: hrv1220, hrp1001, hrp1000. 000040 tables: pchdy, pphdx, p1000, 000050 pt1220, t77fc, t77fd. 000060 tables: *objec, objec, *p1000. 000070 tables: pdrhum, t77aw, t777o. 000080 tables: xu213. 000090 tables: t777e, usr05, tprprof.

and you may need to do the same with menu tables - I'm not sure which ones - (from top include from SSM1) 000010 function-pool smnu. "MESSAGE-ID ... 000020 * 000030 tables: indx, tstct, dsyax, 000040 smenca_new, smen_obnew, smen_conew, 000050 smenusenew, smenentnew, 000060 smen_dates, ssm_stat, ssm_start, ssm_langu, 000070 smensapt, smencust, smenentt, 000080 smensapnew, smencusnew, 000090 smenselect, t002t, 000100 ssm_rele, smenintnew, smenintt.

user masters: USR01 to 09, UST04, profiles: USR10, USR11, UST10S, UST10C, authorisations: USR12, USR13, UST12. password exceptions USR40. History tables(may not be applicable but FYI): users: USH02, USH04, profiles: USH10, auths USH12.

activity groups are stored in table PLOGI along with loads of other object types. the activity groups are object type T. You could export the table data with a manual transport request via SE01, using R3TR TABU and specify the keys to use for all objects of type T(ie all activity groups). Remember to include all clients in the selection.

OR, if you are using the client copy functions to refresh you DEV from PROD, then you could use the RSCCEXCT (see OSS note 70290) to list all these tables and exclude them from the copy, hence the corresponding original DEV tables should not be overwritten in DEV. I suggest you export a transport request with with all these tables from DEV just in case, so you can re-import them again if it goes pear shaped. In 3.x I don't think the activity group names involve client number or SID, but I've heard some differences in 4.6 - Guy Holchester has sent many notes to the list about it - have a look at the archives, but I think as long as you aren't copying between different versions (eg from Prod 4.6 to Dev 3.x, or vice versa) then it should be OK.

If you choose to re-import the tables from transport requests, you might want to run the sync tool in the target client (DEV) afterwards - ie run function module SUSR_SYNC_USER_TABLES, or run SU30, just to check for any dodgy links or inconsistencies.

Also, if you are re-importing user masters too, run RSSODELT and RSSOUSER to recreate all SAPOffice mailboxes and link them to the new user IDs in the target client.

I would use RHMOVE30 and create a transport of your activity groups. To be safe test import the activity groups to QAS prior to refreshing DEV with PRD. Then once you have completed the refresh import the transport you created. For more info on this look at the Authorization is made easy guide available online on page 11-6 release 4.0b.

Remember to run SUPC after you import to regenerate the profiles.

An example of a DB Backup Strategy

Our SAP DB Backup strategy:

Full Online Backup on 00:00 from Tuesday to Saturday.

Redolog on 06:00 from Monday to Saturday

And Once a month full offline backup

Is this good enough or need improvement?

An example of a DB Strategy is as follows:-

Full online SAP backup every day at 20:00 (including weekends)

Full OS filesystem (minus SAP data) every weekday.

Continuous archive logging from 15:00 to 11:00 next day (weekdays) and 15:00 to 14:30 (weekends).

Archive log deletion at 14:45 every day.

We perform a parallel backup on 2 tapes using 3 x 5 DLT tape autoloaders using a 7 day rotating tape cycle. OS backup onto single DAT.

The tapes are stored offsite and brought in every weekday. On Friday the Friday,

Saturday and Sunday tapes are brought in.

The only problem I can see with the strategy is if the system crashes at 05:55 on Monday and needs a restore, you could lose a lot of data as you are missing backups on Sunday and Monday, and archive logs from Sunday.

With this strategy if this happens you will be restoring the data from 00:00 Saturday and the logs from 06:00 Saturday. This means you could lose 48 hours worth of data.

Is your operation 24 x 7 or 24 x 5? If 24 x 5 it shouldn't be too bad unless you run weekly jobs over the weekend.

Do you have single tape drives or multiple autoloaders?

Is there anyone there to change the tapes over the weekend?

My own personal suggestion would be to forget the offline backup as you do not really want to restore data which could be a month old so why bother shutting the system down every month to back it up. I would perform a daily online backup every possible day and continually archive the redo logs with a window for changing the tapes. If nobody is there over the weekend to change the tapes, run your archiving continually through the weekend i.e. start on Friday and finish on Monday.

Evaluating Online Re-Organization Tools

We are evaluating online reorg tools for an Oracle SAP database which is soon to be of 1 Terra Bite size. I would like some guidance for online reorg.tools and experiences of using some of them.

I use SAP 4.6C under Oracle 9.2 under AIX 5.1 on Risc6000 medium-performance machines.

I experienced some reorganizations SAP online, due to the PRD system that must always be up.

Fisrt, consider that the entire reorg is not possible when SAP is online, because of permanent tables (system tables and so on) that could not be exported/imported while running.

An entire TABLESPACE reorganization is no more suitable because of the long runtime between 2 offline backups.

So you can reorg only some tables/indexes or single objects. Be sure that the objects should not be accessed during the reorg, so it will fail. For a particular case, for example a BIG table, I experienced serious perf problems :

JVTLFZUO table : 10 Gb data + 17 GB indexes = 37 GB to be reorganized.

When SAP is online, it took about 13 hours (4 procs, 8 GB RAM) When SAP is not available for users, it took less than 5 hours !!!

So my advice is : - don't reorg too big tables with SAP online. - don't reorg system tables with SAP online. - you'd better to perform a reorg by night or in a lower user activity. - you'd rather to reorg with SAP down for perfs point of views. - always perform an OFFLINE backup before reorg, because the reorg is not always successful.

Difference Between EDI and IDOC

EDI (Electronic Document interchange) - Edi is the electronic exchange of business documents between the computer systems of business partners,using a standard format over a communication network.

Edi is also called paperless exchange.

Advantages: Reduced Data entry errors Reduced processing time Availabilty of data in electonic form Reduced paperwork Reduced Cost Reduced inventories and better planning Standard means of communications Better business process

EDI has two process 1. Outbound process 2. Inbound process

OP: 1.Application document is created. 2.IDOC is generated 3.IDoc is transferred from SAP to Operating system layer 4.Idoc is converted into EDI standards 5.Edi document is transmitted to the business partner 6.The Edi Subsystem report status to SAP

IP: 1.EDI transmission received 2.EDI document is converted into an IDOC 3.IDOC is transferred to the SAP layer 4.The application document is created 5.The application document can be viewed.

IDOC: IDOC is a container that can be used to exchange data between any two process. Each iDoc is assigned a unique number for tracking and future reference. iDoc Consist of several segments,and segments contain several fields. iDoc contains the following three type of records... 1.One Control Record. 2.One or many Data Record 3.One or many Status record.

PORT: Port is used in the outbound process to determine the name of the EDI subsystem program,the directory path where the idoc file will be created at the operating system level,the idoc file names and the rfc desinations.

RFC Destination: Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.

Partner Profile: Partner profile specified the various componets used in an outbound process ( Partner number,IDoc type,message type,Port,Process code),the mode in which it communicates with the subsystem(batch or immediate) and the person to be notified in case of errors.

Message Control Used in pricing,account determination,material determination,and output determination.The message control component enables you to encapsulate business rules with out having to write abap programs.

Process: Setup RFC destinations SM59 Port Destinations WE21 Partner Profile WE20 Message control NACE Purchase Order ME21 Check IDOCs WE02,WE05

Fast Logon to an SAP ServerYou can log on to an SAP server quickly using the "SAPGUI" executable.This way, you do not even need SAPLogon.

At the command prompt type:

sapgui hostname instnumberExample:

sapgui myprd 00The example above lets you log on to the server "myprd" with instance number 00.

The SAPGUI.exe is located under the "SAPgui" directory. You either need to put this directory in your system's path or change to the directory to be able to log on as indicated above.

Saving Passwords for SAP shortcutsPasswords are not saved in shortcuts created within SAPGUI. In fact, when you edit a shortcut the password field is grayed out.Why? Because you need to first register the SAPshortcuts using:

sapshcut -register

SAPSHCUT.exe is located under the SAPpcsapgui directory. In SAPGUI 4.0 it was called SAPSH.exe.Once you do the registration you need to open the registry (regedit or regedt32) and change the value data of "EnablePassword" to "1" under:

HKCU\Software\SAP\SAPShortcut\SecurityThen, you will be able to type and save your passwords.

Getting technical info at the OS level

It is very easy to obtain the patch level of some core R/3 executables such as: disp+work, tp and r3trans.Many people would like to know how to do this. Here, I will show you how to do it for R/3 systems running on Windows and SQL Server environments.

1. Go to the command prompt. 2. Change to the "run" directory of your SAP instance (cd \usr\sap\\sys\exe\run). 3. Run the following three commands:

dsp+work -V | find "patch number"

tp -V | find "patch number"

r3trans -V | find "patch number" If you want to see all the release information, then do not filter for the patch number. Now that you know how to do this, you can get creative and write a little script that reads the names of all your SAP servers from a text file and then it runs the three commands listed above. This way, you can get the patch level of all your systems by just running a script. This becomes in handy when you're consulting or putting reports together.

Controlling the SAPGUI New Visual DesignSAPGUI 4.6x introduced the "new visual design" or "enjoySAP" look and feel.

As you know, users can switch back and forth the new visual design or the "light" look and feel. They simply use the "SAP Configuration" applet in Control Panel. However, you the administrator might need to control what they set up on their PCs in order to have a uniform platform.

The Windows registry controls this setting:

HKEY_LOCAL_MACHINE\Software\SAP\General\Enjoy\ActiveBy the default, it is set to "On". When the user changes it to the light version using the SAP Configuration icon that is on the desktop or Control Panel, then the registry value changes to "Off".

You can hide the SAP Configuration applet. You can even do this when setting up SAPGUI. You can edit the file SAPSETUP.NID and comment out these two lines:

!InstallFileList('%WINSYSDIR%')%SAPsourceDir%\sapgui\sapfcpl.cplEndProc/U/TSIn SAPGUI 4.6D the line above is number 1,459.

!CreateIconOrLink('SAP Configuration','%WINSYSDIR%\sapfcpl.cpl','%SAPworkDir%','sapfcpl.cpl,0','Desktop\',' ',cgAsCommon)/TSIn SAPGUI 4.6D the line above is number 1,645.

Locking/Unlocking accounts - Behind the scenesUser accounts can be locked/unlocked via SU01 (User Maintenance.)But, what goes on behind the scenes? What does the system do to actually set this?

The table USR02 gets updated. The field UFLAG determines if the user account is locked or unlocked. The value "64" indicates that the user account is locked. The value "0" that the user account is unlocked.

Knowing this, you can then issue an update statement at the database level that locks all users in mass.

Don't lock yourself out, though! Use exceptions for super user accounts in your update statement.

Notice that 4.6b and above have made improvements to this kind of task, making the locking/unlocking a bit easier. However, changing at the database level is much faster and it is just one simple query.

SAP table with Version and Instance nameUSAP R/3 stores its version, instance name and OS platform in tables!This is excellent as you can then query the database to get the R/3 version, Instance Name and OS platform as follows:

select * from SVERSselect * from TSLE4You don't even have to log on to the application to get this info. The above query gives it to you in less than 1 second.

Logging on to SAPNet directly (bypass OSS1)You can logon to SAPNet -R/3 FrontEnd without using transaction OSS1.This way you don't have to open an SAP session just to log on to SAPNet.

Here is how to do it:

1. Create the file "saproute.ini" under the %winnt% directory and add the following two entries:

[Router]sapservX=/H/your-SAProuter-internal-IP-address/H/SAPServX-IP-address/H/

Example:sapserv4=/H/200.10.10.24/H/204.79.199.2/H/

200.10.10.24 is my SAP router's IP address.204.79.199.2 is SAPServ4's IP address.

2. Create the file "sapmsg.ini" under the %winnt% directory and add the following two entries:

[Message Server]O01=oss001.wdf.sap-ag.de

3. Open the SAPLogon program (it is part of the SAP FrontEnd software -SAPGUI, on your PC).

4. Click on the "Groups" button.

5. Click on the down arrow for "SAP Router for" and select your SAPServX from the list.

6. Click on the "Generate list" button.

7. Select "1_PUBLIC" from the list of groups.

8. Click on the "Add and Logon" button.

You're done! You can change the name of the SAPNet session in SAPLogon if you want to.No more typing OSS1!

Check if your SAP servers are alive from the Command PromptThis is a very useful tip that can help you check if an SAP R/3 server is up and running. This way, you don't have to log on to the system just to find out.Additionally, you can create another script that uses the FOR command to check ALL your servers so you don't have to check one by one. Have the script do the job for you.

The key to this script is the command SAPINFO.exe, which comes on the SAPFrontEnd CD (SAPGUI). It's part of the SDK. If you don't have the file, e-mail me and I'll send it to you.

The syntax of SAPINFO is:sapinfo ashost=host sysnr=nn

When used in a batch file (.bat or .cmd) you can check the errorlevel returned by the program. If it is 1 then the system is not up and running.

My script below first checks if the system is on the network by 'pinging' it and expecting a reply.

If you want to check all your systems, then create another script (example: checkallrfcs.bat) and use this command:

FOR /F %%i in (SAPsystems.txt) do call checkrfc %%i 00

The command above reads the file SAPsystems.txt, which should have a list of all the servers (one server name per line) and then it invokes the script 'checkrfc' passing the server name as a parameter. The 00 indicates the instance number.

I believe you will find it extremely useful and it will save you tons of time.Now, you can just run the script, sit back and watch it report the status of the systems.

Script code:@echo offrem ======================================================================rem Script: CheckRFC.BATrem It uses SAPINFO from the RFC-SDK (SAPGUI) to check an RFC destination.rem It needs two parameters: 1. Hostname 2. Instance Numberrem A ping is sent to the host. If successful an RFC check is carried out.rem By: Giovanni Davilarem ======================================================================

if "%2"=="" goto NoParameterecho Pinging %1 ...ping %1 -n 2 | find /i "reply" >nul && goto CheckRFCecho System does not exist on the network! & goto Bye

:CheckRFCsapinfo ashost=%1 sysnr=%2 & if errorlevel 1 goto System_Downecho ----------------------------echo System is up. RFC checks OK!echo ----------------------------goto Bye

:System_Downecho ---------------echo System is down!echo ---------------goto Bye

:NoParameterecho ----------------------------------------------echo You did not specify at least one parameter!echo Syntax: checkrfc "hostname" "instance number"echo Example: checkrfc mydev 00echo ----------------------------------------------

:ByeLock a Client to Prevent LogonsDo you need to do maintenance on a system and want to make sure nobody logs on to it while you're working on it?

You can lock a system at the OS level by running: tp locksys pf=tpprofile

Example: To lock your DEV system enter this command: tp locksys DEV pf=saptranshostsapmnttransbintp_domain_dev.pflUsers will get this message if they attempt to log on: "Upgrade still running. Logon not possible".

Notice that the message is not exactly accurate. TP locksys is mainly used during release upgrades so the message is kind of generic. But, it works!

To unlock the system, run: tp unlocksys pf=tpprofileNow you can tell your boss that you know how to keep the users off the system!

Only SAP* and DDIC can log on to any of the clients in the system that has been locked.

How to know the kernel version of a SAP R3 system?

Could someone tell me how can I find the Kernel version of a SAP R3 system ? example, for those releases SAP R3 4.0B, 4.5B, 4.6B, 4.6D and so on ....

From any screen choose System-->Status then click the 'other kernel info' icon (between Navigate and Cancel). The same information can be found at OS level in the dispatcher trace file: /usr/sap///work/dev_disp. Regards,

Goto transaction sm51, and click (not double click) on the the Database server and then click on release notes. there you will see the SAP R/3 kernel and patch level etc.

You can use the System ==> Status and then Other Kernel Info button to get the details about the Kernel Release, Patch levels etc.

I think an even more convenient way to do this is to use SM51. Highlight the server you are interested in and click on "Release Information". This provides you a location to view all servers with out logging on to each one. The answer below will give you information about the server you are connected to only.

Also try "disp+work -v" on server.

go to transaction SM51 -->release information

How to apply OSS notes to my R/3 system?

In order to fix one of the problem in R/3 system, SAP will asked you to download an OSS notes which is a ".car" file.

To work with a CAR File do the following at OS Level:

Get into OS as adm

Copy the .CAR file to a Temporary Directory.

Uncompress the file with SAPCAR

Copy the the data file generated in the data transport directory ( ej: = /usr/Sap/trans/data).

Copy the the cofile file generated in the cofiles transport directory ( = ej: /usr/Sap/trans/cofiles).

Run transaction STMS

Upload the support package with SPAM transaction and the support package will show "New support packages".

**********

Examples of CAR command :-

1) UNIX only:

Log on as user adm. cd /usr/sap/trans CAR -xvf tmp/.CAR -V

2) Windows NT only:

Log on as user ADM. cd \USR\SAP\TRANS CAR -xvf TMP\.CAR

This Will create two(2) FILES

After you run SPAM you MUST run STMS and check the transport queues

**********

As per 315963 note you can direct made the changes in the program or you can apply the support pack.

a) If you want to apply correction then first you need to register the object in SAP, so that you will get the Access key and then you can make the changes.

b) If you want to import the support pack then you need to down load from SAP market-place. and this is in CAR file. and then you need extract the same using CAR utility. ex: CAR -xvf abc.car

or

you can directly apply the patch from SAPGUI, login to 000 client and then you can load the patch from Presentation server.

Also check what is your current basis patch level?

For example if you want to apply patch 07 and you are having 05 then you need to apply 06 and then apply 07.

Things to take note of:It would definitely be better to apply the latest spam/saint spam manager, tp, R3trans and possibly a new kernel patch.

This is not a simple task to complete on the fly. By applying SAP support packs, you may run into problems with SPDD and SPAU adjustments. Also include the fact that the support packages may break one of your transactions. You may want to test this in your sandbox environment, if you have one, before tackling it.

In most situation when you apply support packages, it can takes about 3 weeks to fully test the support packages before you can apply them to the production system.

Do test your "golden" transactions to make sure that they are not broken. If you are not familiar with SPDD and/or SPAU adjustments than do not attempt to load support packages.

You may be better off just to modify the SAP object in question via OSS note.

Manually Applying OSS note on SAP Standard Program

In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.

For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.

Follow this step to obtain the Program Access key:

Menu Path: System -> Services -> SAP Service (Transaction code OSS1)

Login in with your OSS ID and Password

Click the Registration button

Click Register Object

Double click R/3 Value Contract

Fill in the Object Registration for Installation:

For e.g. PGMID/Object/Name: R3TR FUGR MIGO SAP release: 46C

Finished, click the Register button

Select the Key number and use the Copy and Paste short key to copy the Access key

You are now able to modify the SAP standard program.

Finished the modification, do remember to transport it to the production system after all the necessary testing.

Upgrading the SAP Kernel and SAP Hotpatches

Kernel upgrade is an easy process.

Go to the SAP OSS Site :-

http://service.sap.com/SWCenter-Main SAP R/3 SAP R/3 4.6C Binary Patches SAP KERNEL 4.6D

Download the kernel programs in a temporary folder.

Create a folder and copy the executables /exe/run/ then uncar the downloaded files and replace the executables.

It is recommended to shutdown the R/3 database and all services including saposcol.

Then restart your system.

A couple of important points to remember are :-.

a) Always make a copy of the files you're going to replace. For e.g. Create a directory (oldkern) and copy all the old files before replacing them (this helps when sometimes the new Kernel has problems, and you can revert it)

b) You have to shutdown SAP and the Database using the OLD kernel file. Again it is good practice to shutdown everything first.

Refer to this OSS note which is pretty useful :-

102461 - Installation of 4.0B/40B_COM kernel with 4.0A/40B

Applying SP4 to Windows 2000 Server

You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use.

Once you are at the patches website, you will need to click in the navigation tree: R/3 -> R/3 + ?Release number? -> Binary patches -> SAP Kernel + ?Release number? + 32-Bit -> NT/I386.

Download everything from the database section and everything from the database independent section.

One of the files you downloaded should start with SAPCAR and end with a *.exe. Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory. Go to \usr\sap\\SYS\exe\run and backup the entire directory to some other directory - I usually create a \usr\sap\\SYS\exe\backup_run directory. Make sure SAP is down, the database is down, the TNS listener is down, and the SAPOSCOL is down before you do this.

Uncompress all the files you downloaded by opening a DOS box and typing:

SAPCAR -xvf .CAR

All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\\SYS\exe\run AFTER that directory has been completely backed up.

Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup.

If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.

Suspending batch jobs

During rollouts or support packages or any other time when you don't want the batch jobs running, use programs BTCTRNS1 and BTCTRNS2. BTCTRNS1 suspends all batch jobs EXCEPT the import jobs. It puts them in a unique state. When you're done, use BTCTRNS2 to re-release the jobs and restore you backup schedule.

SPAU and SPDD

When you apply a package, a large number of objects are changed.

If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.

SPDD is used to identify dictionary objects

and

SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.

You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.

If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.

If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.

If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.

You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.

How to know the kernel version of a SAP R3 system?

Could someone tell me how can I find the Kernel version of a SAP R3 system ? example, for those releases SAP R3 4.0B, 4.5B, 4.6B, 4.6D and so on ....

From any screen choose System-->Status then click the 'other kernel info' icon (between Navigate and Cancel). The same information can be found at OS level in the dispatcher trace file: /usr/sap///work/dev_disp.

Goto transaction sm51, and click (not double click) on the the Database server and then click on release notes. there you will see the SAP R/3 kernel and patch level etc.

You can use the System ==> Status and then Other Kernel Info button to get the details about the Kernel Release, Patch levels etc.

I think an even more convenient way to do this is to use SM51. Highlight the server you are interested in and click on "Release Information". This provides you a location to view all servers with out logging on to each one. The answer below will give you information about the server you are connected to only.

Also try "disp+work -v" on server.

-----Reply Message----- Subject: RE: How to know the kernel version of a SAP R3 system

go to transaction SM51 -->release information

SAP Transaction code to pre-compile all system program

Make use of the transaction 'SGEN' to re-generate all the SAP programs after an SAP upgrade or a kernel patch.

Do take care of the table spaces and use SAPDBA to observe them.

Do it during a weekend which is the best or a period of time with very very low users activity.

It will takes about 5 to 8 hours depending on the type of hardware configuration you are using.

Different methods to Lock or unlock SAP users

Is there a way in SAP to unlock a locked user for a limited time, then automatically after x time set the user back to lock status?

You can fill in "valid from" and "valid until", but you cannot say from Monday to Friday from 8 - 12:00 for part time workers.

Can we schedule to lock all users?

If users get locked, from SU01 you can unlock them.

Use SU10 to mass lock/unlock the users.

Use address data or authorisation data to get a list of users - select the ones you want and

click transfer.

Once this is done click on lock or unlock.

You can also use transaction code EWZ5 to mass lock/unlock the users

or

Execute program EWULKUSR in SE38

or

Set a profile parameter (login/failed_user_auto_unlock) to unlock at midnight the locked users.

or

Here's an ABAP code, short and simple, isn't it?

REPORT zreusrlock.

DATA: time_limit TYPE sy-datum. DATA: days TYPE i VALUE 40.

time_limit = sy-datum - days. UPDATE usr02 SET uflag = 64 WHERE trdat < time_limit.

If you don't want to specify the time in the program, you can use SE38 to schedule it as a daily background job with the date and time.

or

Probably the easiest way would be to write a sqlplus SQL script that sets all the UFLAG fields in table USR02 to 64 EXCEPT for the BNAMEs you don't want locked. When you are done, you can do the same again but change the UFLAG field to 0.

The SQL statement would look like:

update SAPR3.USR02 set UFLAG = 64 where MANDT = and BNAME != ;

You can replace != with if you want. To run this from an OS command line, you would type:

Unix/Oracle 8---> sqlplus internal @ NT/Oracle 8.0---> plus80 internal @ NT/Oracle 8.1---> sqlplus internal @s Unix/Oracle 9:--> sqlplus /nolog @ NT/Oracle 9-----> sqlplus /nolog @

In UNIX you can cron the script to schedule it. In NT you can schedule it as a task.

or

This is another method to UNLOCK ALL users.

Start Oracle Server manager (I assume you are on Oracle) connect internal update sapr3.usr02 set uflag='0' where mandt='399';

When users are locked, the uflag is set to 64.

Finish, just query to check.

select bname, uflag from sapr3.usr02 where mandt='399';

Please note that unlocking users from low level (like Oracle sqlplus) should be used as last resort. Frequent use of low level access may tempt you to use on other things. Highly dangerous and your IS auditors will not be too happy.

Is there a way to set a list of users that cannot be locked, even if we try to lock them manually, and even if they fail connection ( wrong password )?

Increase this parameter in SAP Instance profile:

login/fails_to_user_lock = 6 (max is 99 wrong attempts, i.e, value 99). Currently you have a value of 3.

login/failed_user_auto_unlock (for your midnight unlocking).

Ask users to remember passwords!! If someone is deliberately login-in with different username/password (thereby blocking legitimate access of that user), check hostname from SM21.

This is considered as DoS (Denial of Service).

Changing the default password for sap* user

You are trying to change the password for sap* user, however when you go into su01 and enter sap* as the user name, the following message is displayed, user sap* does not exist.

You can delete the SAP* user using ABAP code :- Delete from usr02 where bname = 'SAP*' and mandt = '***';

Where '***' means your client no.

Then login to your client using password SAP* and password PASS

However, if you delete it, then it will automatically created once again with password PASS

The userid, SAP*, is delivered with SAP and is available in clients 000 and 001 after the initial installation. In these 2 clients, the default password is 07061992 (which is, by the way, the initial date when R/3 came into being...). It is given the SAP_ALL user profile and is assigned to the Super user group. When I say it is "delivered" with SAP, I mean that the userid resides in the SAP database; there are actually rows in the user tables used to define userids.

If you delete the userid, SAP*, from the database, SAP has this userid defined in its kernel (the SAP executable code that sits at the operating system level, i.e., disp+work). When this situation exists, the password defined in the SAP code for SAP* is PASS. This is necessary when you are performing client copies for example, as the user information is copied at the end of the process. You can sign into the client you are creating while a client copy is processing using SAP* with password PASS (but you should have a good reason to do this - don't change anything while it's running).

Anyway, if the SAP* userid is missing, you can sign in to the client you want and simply define it using transaction SU01 and, as I stated above, assign it to the SUPER user group and give it the SAP_ALL profile. You define its initial password at this point. If you've forgotten its password and don't have a userid with sufficient authorization to create/change/delete userid, then you can use the SQL statements to delete it from the database and then you can use SAP* with PASS to sign back into the client you want to define it in and recreate it.

There is also a profile parameter which can override the use of SAP* with PASS to close this security hole in SAP (login/no_automatic_user_sapstar). When this parameter is defined either in your DEFAULT.PFL profile or the instance-specific profile and is set to a value of '1', then the automatic use of SAP* is deactivated. The only way to reactivate the kernel-defined SAP* userid at this point would be to stop SAP, change this parameter to a value of 0 (zero), and then restart SAP.

The default password for SAP* is 06071992. (DDIC has 19920706)

Mass Maintenance of Users Profiles

Goto transaction code SU10

Select your SAP User by Address data or Authorization data.

With the users you want to change selected, click :-

User -> Change -> Profiles

Filled in the Profiles and click save.

What are user groups and how can we use them?

Your auditer asked you to implement user groups in SAP, but you have no idea what are user group.

Transaction SUGR - have a look. Purpose for example is to give certain system admin rights to unlock / change password only to a given user group. You assign user group to an user id via SU01.

User group can be used for differ