SAP BASIS

BASIS MATERIAL

2010-03-15T10:13:00.000-07:00

1) Basis (BC)
2) Basis
3) Batch Management (LO-BM)
4) BC - ABAP Dictionary
5) BC ABAP Workbench Tools
6) BC ABAP Workbench Tutorial
7) ABAP Programming (BC-ABA)
8) BC Basis Programming Interfaces
9) BC - Business Workplace
10) BC - Central Maintenance and Transport Objects
11) BC Data Modeler
12) BC Documentation of System Objects
13) BC Extended Applications Function Library
14) BC - Namespaces and Naming Conventions (BC-CTS-NAM)
15) BC R/3 Database Guide:DB2/400
16) BC R/3 Database Guide: DB2 Universal Database for UNIX & Windows
17) BC R/3 Database Guide: Informix
18) BC SAPconnect
19) BC SAP Graphics: Programming Interfaces
20) BC SAP Graphics: User's Guide
21) BC - SAP Printing Guide
22) BC SAPscript Raw Data Interface
23) BC SAPscript: Printing with Forms
24) BC - SAP Style Guide
25) BC Style and Form Maintenance
26) BC System Services
27) BC The SAP Communications Server
28) BC - Word-Processing in the SAPscript Editor
29) Desktop Office Integration (BC-CI)
30) SQL Studio (BC)
31) Reference Manual 7.2 (BC)
32) Messages 6.2 (BC)
33) Messages 7.2 (BC)
34) Network Integration Guide (BC-NET)
35) Updates in the R/3 System (BC-CST-UP)
36) Users and Roles (BC-CCM-USR)
37) The SAP Lock Concept (BC-CST-EQ)
38) The Test Workbench in the SAP System (BC-CAT-PLN)
39) The Appointment Calendar (BC-SRV-GBT)
40) The BAPI Gateway Component (BC-FES-AIT)
41) Terminology and Glossary in SAPterm (BC-DOC-TER)
42) Business Configuration Sets (BC-CUS)
43) Business Document Service (BC-SRV-BDS)
44) Central Adress Management (BC-SRV-ADR)
45) Change and Transport System - Overview (BC-CST)
46) Changing the SAP Standard (BC)
47) Computing Center Management System (BC-CCM)
48) Controls Tutorial (BC-CI)
49) Repository Service Component (BC-FES-AIT)
50) Generic Object Service (BC-SRV-GBT)
51) Hypertext Structure Maintenance (BC-DOC-DTL)
52) Generic Business Tools for Application Developers (BC-SRV-GBT)

2007-11-23T13:03:00.001-08:00

Sending faxes from SAP

Some guidelines how to you can setup faxing from SAP :-

You will need an additional software to be installed.

The best way to do this is to get a standard desktop PC with a modem attached. Buy a
copy of Winfax 10 (its only about $100 to buy.)

When you have Winfax setup and working locally, install SAPLPD (put it in the startup group so its loads on startup).

WinFax will create a shared fax on the PC (For e.g. IFAX).

When this is done create a printer/Fax in transaction SPAD.

Device type = SAPWIN Rel.4.x/SAPlpd
Device class = Fax
Host Spool access method = S;print using SAP protocol
Dest. host = PC IP address
Host printer = Shared fax name on PC(i.e IFAX)

Make sure you have all the lasted SAPLPD + dll's

After that is done create the locations in transaction SCOM, they are self explainitory from there.

2007-11-23T13:00:00.001-08:00

Printing ABAP Report over LAN and WAN

For the LAN setup for local printer you can defined it as device LOCL

Device type: SAPWIN
Host printer: __DEFAULT
Host spool access method: F (Printing on front end computer)

This printer will works fine on your LAN.

For the WAN, assuming that you have 2 office connected over the internet and they work fine with the printer LOCL.

Now, you need to have a Print Server where you have installed many of the printer, some of them over WAN and they will work fine if you do this :-

The server must have SAPLPD installed.

Output device: LPFP
Device type: SAPWIN
Destination host: sapdev
Host printer: HP_HP1 (printer name on the Printer Server)
Host spool access method: S (Print on LPDHOST via SAP protocol)

2007-11-23T12:51:00.000-08:00

Auto convert SAP spool output to PDF file

As of Release 4.6D, PDF format (Adobe Acrobat data format) can be created via the SAP spooler by using the device type "PDF1".

As a workaround, a report (RSTXPDFT4) is made available for the missing "direct PDF printing", which can read spool requests, convert to PDF and perform a frontend download.

Read OSS Note 317851 - Printing PDF files in 4.6C/4.6B/4.5B

Note the restrictions specified in Note 323736 with the print output with PDF.

Caution when modifying device type ZPDF1, see Note 437696.

Version - 4.6D

If you are in version less than 4.6D, you can configure an output type to convert the spool automatically into a PDF format into your local harddisk but not do a "direct PDF printing".

When you print to this PDF output type, it will prompt you to enter the file name of your PDF file to be stored into your local harddisk.

First you have to add a printer using

Windows -> Start -> Settings -> Printers -> Generic / Text Only -> Port : Print to File

Next create a new device type e.g. ZPDF -> Select device type ZPDF1

Options for HostSpoolAccMethod

-> Host spool access method : F : Printing on Frontend Computer
Host Printer : __DEFAULT or Generic / Text Only

Save your entries.

When you print to the device type ZPDF, choose Generic / Text Only for the Frontend Computer if it is not the default type.

A user prompt Print to File will appear to let you specify the Output File Name.

2007-11-23T12:49:00.000-08:00

Delete multiple spool request

The program are RSPO0041 or RSPO1041.

This is handy whenever you encounter a user who managed to create a lot of spool requests which are choking your system.

Deleting them with SP01 will be too slow and you will get time out if it exceed the online time limit specify by your basis people.

2007-11-23T12:45:00.000-08:00

How can I print A3 format in SAP

My printer is HP LaserJet 5100

Note I can print ms word document in A3 format but I can't print A3 format in SAP

My output device setting are:

DeviceAttributes:
Device Type = THSAPWIN: MS-Windows-Printer via SAPLPD
Device Class = Standard printer
Access Method:
Host Spool Access Method = S: Print Using SAP Protocol

When I print SM50 output and select format X_65_255, it can print successfully but its format is A4.

What may I do wrong? Please help me how to set up for A3 printing in SAP.

Ps. Do I need to assign A3 format to be default format in that printer?

Is this task for BASIS or ABAP?

In printer settings - SPAD - tray info - you can give the Page format for that tray .
did you try setting that ? Try setting DINA3.

Go to START --> SETTINGS ---> Printers

Right click on HP LaserJet 5100 ... Properties..
General Tab --> Printing Preferences --> Advanced --> Paper Size -->
Change it to 14x11 or A3

and

hplaserjet 5100 --> Properties --> Advanced Tab
Printing Defaults --> Advanced --> Paper Size -> change it to 14x11
or A3

hplaserjet 5100 --> Properties --> Device Settings tab -> Autoselect -
-> A3 or 14x11...

Our ABAPer already changed some attributes(ex. font name & size) in print control of SPAD followed by SAP Notes 21738.

Like this ->

# THSAPWIN Z_65_255

# SAPWIN indicatior makes it possible to send via berkeley protocol
\e%SAPWIN%
# change WinCharSet to 222 (Thai)
\eW222;
# set orientation(LANDSCAPE)
#\ePL
# set font name
\eFAngsana New;
# set font size(5.5ponits)->8p->5.5
\eS220
# set vertical spacing(8.7LPI)
#\el3.0;
# set horizontal spacing(24.0CPI)->20->18 (255/11) ->23
#\ec5.0;
# set top/left margin(1.0cm=568.5)
#\eMT567;
#\eML567;

However, it take moderately time to change font size and test report printing for A3 format.

Thank you for your recommend.

I follow by your instruction. It's work well.

Note It doesn't need to setup these config at all.

Tab "Output Attributes"
Paper tray = "Paper tray 3"

Tab "Tray Info"
Tray 3 = "DINA3"

Key points of this solution, If the SAP spool server and the Microsoft Windows spool system are not on the same host, you must create a remote PC connection to the printer and force paper size to be A3 (Prakash's instruction)

By the way, I also adjust HP Laserjet 5100 from "EXEC" to "A3" in Tray 3 physically too. After that I can print ABAP List in A3 Format successfully.

Thank you again for the solution.

2007-11-23T12:42:00.000-08:00

Parallel printing to all the SAP device printers

If you have a situation where reports need to be send to multiple printers, you can configure a pool device type. A pool device type contain a list of SAP printers which the reports will be directed to.

Do this in transaction code SPAD for spool administration.

For example, in SPAD, type ZXXX next to the field 'Output devices',

Click the button Output devices.

In change mode, click the Create button.

Specify the Device type of your printer.

Click the tabstrips 'HostSpoolAccMethod'.

In the field "Host spool access method" set to "P: Device Pool".

Click the tabstrips 'DevicePool'

Click the options "Send to all devices in pool".

Type in the list of the SAP printers device you want the report to go to in this pool under the section 'Pool Device List'.

Now, when the users send a print to the new device for e.g. ZXXX, it will print to all the spool device you have specify.

The above step is done using SAP 4.6c

2007-11-23T12:38:00.000-08:00

Print to an USB printer from SAP

Is printing to a USB-printer using LOCL from SAP possible?

Yes, as long as this printer is defined on local workstation, it will work.

SAPLPD doesn't care on how the printer is connected, as long as Windows can print to it, SAPLPD will do its work.

Define one new device, also consider giving :

Device type as SAPWIN

Host Printer __default (yes, two underscores default)

Access Method : F

Make sure your desktop/PC Windows default printer is set to this USB printer.

2007-11-23T12:34:00.000-08:00

Mass Lock All Printers with SPAD

If you have lots of printers (50 or more) and need to lock them for maintenance, you can used this mass locked printers tips to locked or unlocked all the SAP printers at one go.

To mass Lock all the printer in SAP:

Go to transaction code SPAD

On top of the screen menu click Utilities -> For output devices -> Export devices

On the screen Import and Export of Device Descriptions:

Export/Import file name: c:\temp\printer.txt

Frontend computer: Tick

Export: Tick

Export Export: Tick

Output device: Choose the Selection options Pattern and type a *

(* for all or a* for all printers starting with a)

Click the Execute button

Open the text file do a replace all of PADISABLED = "" to PADISABLED = "X"

Then import the same file.

Another way is to go through each output device in SPAD and click on 'Lock Printer in SAP System' which is in the DeviceAttributes tab.

2007-11-23T12:20:00.000-08:00

Troubleshooting SAP Performance Issues

Is there a document that will help me troubleshoot system performance? What are the steps on how to troubleshoot?

Troubleshooting is a BIG task of itself, there is no single reference document because there are too many reasons why a system can appear "slow" to the user:

- Different Databases

Every database has its own mechanism for optimizing access, even more, each database has BOOKS on performance optimization. This can start from parameters to database layout to operating system configuration, used filesystems, mount parameters...

- Different Operating System

The same goes for operating systems, a standard Windows 2000 (or 2003) isn´t configured for optimal throughput, there is a LOT to tune, e. g. enable "background process priorities", stop non-needed services, network configurations (TCP window sizes) etc. Also the connection between application and database servers can be an issue

- SAP Itself

Almost for each and every long running program there are optimizations, be it on ABAP layer or on selection layer. Out of my experience, most self developed programs (Z*-programs) are the main issue, because developers program "quick-and-dirty"
doing "select *" and other things.

For e.g.:

If CPU is 100% Busy, what action should be taken to keep CPU idle?

This can't be answered generally. One need to check what process is using so much CPU - then one can start digging deeper. To add info regarding this issue, you may use:

st06->details analysis menu->snapshot analysis->top CPU from there, start to narrow down.

2007-11-23T12:12:00.000-08:00

Tuning Summary In Transaction ST02

My current system is SAP R/3 Enterprise 4.70. I have some questions about tuning summary in transaction ST02 :

To the best of my knowledge I am answering your questions. Ok

1. Do we have to increase every profile parameter value which is displayed in red alert in transaction ST02 ?

Ans: Of course it should be, since each buffer holds different values, wherever the red alert is there change the parameter value.

2. Why do the swapped objects always increase after a few days of tuning (in RZ10) & system restart?

Ans: Since more data had been fed into the server, it needs more space to hold in buffer while retrieving the data.

Since buffer is shot in space, swap memory will be used. It is not enough to increase the buffer and that does not mean tuning, tuning in the sense full analysis of the problem and working in that particular area to resolve the issue.

For example, creation of index, data archival, availability of statistics, aloting of no. of work process, etc.

3. Is there any standard in tuning ST02 to hold up the increasing value of swapped objects?

Ans: No. It depends on requirement.

4. After analysing ST02, how can we calculate the value of the parameter profile to be increased (in RZ10) ?

Ans: yes, use the command:

sappfpar check pf=\\usr\sap\trans\tpparam

(or)

sappfpar check pf=\\usr\sap\trans\tp_domain_sid

2007-11-23T12:04:00.000-08:00

SAP System Performance Issues

My server becomes slow when more users login.
What could be the reason? Is it because of less hardware resource?

Server configuration is 104GB HDD, 2GB Ram.
OS:Win 2003 server.
Database:Oracle.

I manage SAP R/3 4.6C systems on Risc 6000 machines, under Oracle 9.2.

The overall performance problem for me is to know if SAP response time is acceptable ; if not, do this :

- at AIX level : utilities are topas, to catch what's wrong : Disk I/O ? CPU bottleneck ? Too much swap ?

- at Oracle level : tkprof but don't know much about this.

- at SAP level : you can manage SAP memory, Oracle and OS too.

If SAP response time is acceptable, then try this :

Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.

Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.

Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads / logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo logging.

I use this kind of procedure to manage my systems.

It depends how much you allocated for SGA (database buffers, shared pool buffer, redo log buffers), how much you allocated for SAP buffers esp. Program buffers and whether the server have any other external processes/programs running.

How many Dialog Work Processes you allocated…I think your problem most likely is you don’t have enough of these Dialog processes. Also maybe users running inefficient reports/programs which are holding the Dialog processes, goto SM50 & check all DIA (Dialog) with status “waiting”…if ALL are “running” then you have wait time (problems !) for other users wanting to process transactions .

To troubleshoot performance, you need these tcode tools:-

ST04 – Database ß in here, check especially for Expensive SQLs (Detail Analysis à SQL Request)

ST02 – SAP buffers

ST06 – OS stats

ST05 – SQL trace

SE30 – Abap runtime analysis

A few step which you can exercise to sort/identify performance issues.

* ST03, ST02, ST04 are the tcode for workload, tuning and DB Performance Monitoring codes.

* ST06 FOR Operation System Monitoring.

** SM51 OR SM50 is process overview which tells you the workprocess sequence. ( Ideally 10-15 process with OLTP and batch process scheduled at peak and off peak times respectively) say 8-17 hrs and 17-8 hrs for Batch Process)

Operation Mode can be configured in RZ04 tcode.

** Check for top CPU in ST06 tcode. CPU should not exceed more than 60% for long time for any process.

** Based of No. of instances ( Application Servers ) should have adequately sized.

** Most resources intensive process have to be scheduled in Batch Process ( in Background in Non Peak Hours )

** Look for unnecessary Jobs Active During Prime Time
** Look for Parameters Set To Your Business Process.
( RZ10, RZ11 ) Check Snote:0124361

** Refer Early Watch Alert Periodically for Overall System Performance.. ( Tcode SDCC )

2007-11-23T11:57:00.002-08:00

SAP Load Balancing and Work Processes Troubleshoot

The benefit of segregating user groups by line-of-business (using logon groups) is related to the point that groups of users (like SD users or HR users, for example) tend to use the same sets of data. They (generally) work with the same groups of tables and hit the same indexes using the same programs (transactions).

So, if you can group all of the users hitting the same tables, onto (or one set of) App server(s), then you can tune the App server buffers to a much greater extent. If the FI users (generally) never hit against the HR tables then the App servers in the FI group don't (generally) have to buffer any HR data. That leaves you free to make memory and buffer adjustments to a more drastic extent, because you don't have to worry (as much) about screwing the HR users (as an example), when you're adjusting the FI server group.

So, (in opinion only) you should start with a buffer hit ratio analysis / DB table & index access analysis (by user group) to see where you would get the best benefit from this kind of setup. If you don't have this kind of info, then creating logon groups by line-of-business may have no benefit (or worst case, may make performance degrade for the group with the highest load %). You need some historical information to base your decision on, for how to best split the users up.

You may find that 50% of the load is from the SD users and so you may need one group for them (with 3 App servers in it) and one other group for everyone else (with the other 3).

The logon group(s) will have to be referenced by SAP GUI, so SAP GUI (or saplogon.ini + maybe the services file, only) will have to change to accomodate any new groups you create in SMLG. Also consider that there's variables for time-of-day (load varies by time-of-day) and op-mode switches (resources vary by op-mode).

All Work process are running? What will be our action?

Are all the work processes (dia,btc,enq,upd,up2,spo) running or just all the dialog work processes?

If all the work processes are running, then you may want to look at SM12 (or is SM13?) and see if updates are disabled. If they are, look at the alert log (if it's an Oracle database) and see if you have any space related errors (e.g. ORA-01653 or ORA-01654). If you do, add a datafile or raw device file to the applicable tablespace and then, re-enable updates in SM12.

If only all the dialog work processes are running, there are several possible causes. First, look to see if there's a number in the Semaphore column in SM50 or dpmon. If there is, click once on one of the numbers in the Semaphore column to select it and then, press F1 (help) to get a list of Semaphores. Then, search OSS notes and, hopefully, you'll find a note that will tell you how to fix the problem.

If it's not a semaphore (or sometimes if it is), use vmstat on UNIX or task manager on Windows to see if the operating system is running short on memory which would cause it to swap. In vmstat, the free column (which is in 4k pages on most UNIX derivatives) will be consistently 5MB or so and the pi and/or po columns will have a non- zero value. The %idle column in the cpu or proc section will be 0 or a very low single digit while the sys column will be a very high double-digit number because the operating system is having to swap programs out to disk and in from disk before it can execute them.

In task manager, look at free memory in the physical memory section under the performance tab. If it's 10MB or 15MB (I think), then the operating system will be swapping.

Usually, when all the dialog work processes are running, you won't be able to log in via SAPgui and will need to execute the dpmon utility at the commandline level. The procedure is basically the same on UNIX and Windows.

On UNIX:

telnet to server and login as sidadm user.
cd to /sapmnt/SID/profile directory
execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_hercules_DVEGMS00) select option "m" and then, option "l"

On Windows:

Click on START, then RUN
Type "cmd" and press enter
change to drive where profile directory resides (e.g. f:)
cd to \sapmnt\SID\profile
execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_zeus_DVEGMS00) select option "m" and then, option "l"

On both operating systems, you'll see a screen that looks like what you see in SM50. Depending on what you see here, will depend on what you do next, but checking the developer trace files (e.g. dev_disp) in the work directory (e.g. /usr/sap/SID/DVEGMS00/work) is never a bad idea.

2007-11-23T11:57:00.000-08:00

SAP Load Balancing and Work Processes Troubleshoot

You may find that 50% of the load is from the SD users and so you may need one group for them (with 3 App servers in it) and one other group for everyone else (with the other 3).

All Work process are running? What will be our action?

Are all the work processes (dia,btc,enq,upd,up2,spo) running or just all the dialog work processes?

In task manager, look at free memory in the physical memory section under the performance tab. If it's 10MB or 15MB (I think), then the operating system will be swapping.

On UNIX:

telnet to server and login as sidadm user.
cd to /sapmnt/SID/profile directory
execute "dpmon pf=SID_hostname_SYSNR" (e.g. PRD_hercules_DVEGMS00) select option "m" and then, option "l"

On Windows:

2007-10-13T14:27:00.000-07:00

Post Installation Steps For ECC 5.0

What are the post installation steps after I have installed the Central Instance and Database instance?

Initial Consistency Check

SM28

1. Logon to the newly refreshed SAP system and run transaction SM28

2. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.

Edit Batch Jobs

1. Set the fields as follows

Job name: RDDIMPDP*

User name: *

Job Status: Released and Ready checked off, all others unchecked

Fr: 01/01/0001

To: 12/31/9999

Or after event: *

2. Press F8 to execute the query

3. Highlight the first job in the list and press the CTRL+F11 to change the job.

4. Examine the Exec Target field.

a. If the box is empty, press F3 to exit

b. If the box is not empty, then clear out the contents so the field is blank and press CTRL+S to save

5. Repeat Steps 3 and 4 *for* each additonal job listed.

Workbench Organizer Reconfiguration

1. Logon on to client 000 of the newly refreshed system with DDIC.

SE06

1. Select the Database Copy or migration option

2. Press the Post-installation Processing button.

3. When prompted Do you want to re-install the CTS?, press the Yes button

4. When prompted *for* the Source System of Database Copy?, make sure that the SID of the production system is selected. Press the checkmark button to continue.

5. When prompted Change originals from PRD to QUA?, press the Yes button

6. When prompted Delete TMS Configuration?, press the Yes button

7. When prompted Delete old TMS configuration?, press the Yes button

8. When prompted Delete Old Versions of transport routes?, press the No button

TMS Configuration

1. Logon on to client 000 of the newly refreshed system.

STMS

1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed

2. The information on *this* screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description *for* the system and press CTRL+S to save. Otherwise, press the Other configuration button and manually configure.

3. From the Overview menu, select Transport Routes

4. From the Configuration menu, select Adjust with Controller

5. Press the Yes button when prompted *if* you want copy the transport routes from the controller.

Import Printers

1. Logon on to the production client of the newly refreshed system.

STMS

2. Press F5 to go to the *import* Overview.

3. Double click on the SID of the newly refresh system

4. From the Extras menu select Other Requests, then Add.

5. In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press Enter to save.

6. Select the transport that was just added to the queue and press CTRL+F11 to start the import.

7. In the Target client box, enter the productive client of the newly created system. Press Enter to save.

8. Press the Yes button to start the transport.

Client Configuration

SCC4

1. From the Table view menu, select Display -> Change

2. When warned that the table is cross-client, press the checkmark button.

3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)

4. Define client as follows:

Client role: Test

Changes and transports *for* client-specific object: Changes without automatic recording

Client-independent object changes: Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

5. Press CTRL+S to save.

6. Repeat steps 4 through 6 *for* any additional clients

Set System Change Option
SE06

1. Press the System Change Option button.

2. Set the global setting to Modifiable

3. From the Edit menu, select Software Components Modifiable

4. From the Edit menu, select Namespaces Modifiable

5. Press CTRL+S to save.

Import Users
STMS

1. Press F5 to go to the Import overview

2. Double click on the SID of the newly refreshed system.

3. Press F5 to refresh the list of transports

4. Locate the transport in the list containing the user exports done before the start of the refresh. If the transport is NOT in the list, then from the Extras menu, select Other requests then Add. Enter the transport number and press Enter. Then press the Yes button to add the transport.

5. Highlight the transport and press the Import request icon.

6. At the client *import* screen, enter the target client and then press the Import button.

7. Press Enter to confirm that the *import* will proceed.

SCC7

1. Run the Post Client Import Processing.

2. The transport number should be the same as that of the transport started in STMS.

3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.

4. Press CTRL+S to save.

SM37

1. Set the fields as follows

Job name: CLIENTIMPORT*

User name: *

Job Status: All options checked

Fr: 01/01/0001

To: 12/31/9999

Or after event: *

2. Highlight the job that was created by SCC7 and press CTRL+F11 to modify the job.

3. Press the Step button.

4. Select the RSCLXCOP line and press CTRL+SHIFT+F7 to modify that step.

5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).

6. Press CTRL+S to save the changes

7. Press F3 to go back to the main job screen.

8. Press the Start condition button.

9. Press the Immediate button.

10. Press CTRL+S to save the changes

11. Press CTRL+S again to save all the changes to the job.

12. Job will start immediately once saved. Press F8 to refresh the list of jobs

13. Continue to press F8 every once in a *while* to update the status of the job. Do not *continue* until the job is completed sucessfully.

SCC4

1. From the Table view menu, select Display -> Change

2. When warned that the table is cross-client, press the checkmark button.

3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)

4. Set the Protection to Protection level 1

5. Press CTRL+S to save.

6. Repeat steps 3 through 5 *for* any additional clients

Deleting Source System Profiles
RZ10

1. From the Utilities menu, select Import Profiles then Of Active Servers.

(Note: All application servers of the target system must be started)

2. If the Display Profile Check Log screen is displayed, press F3 to leave *this* screen.

3. Select the Profile field and press F4 to bring up a list of profiles.

4. From the list select one of the profiles associated with the source production system.

5. From the Profile menu, select Delete, then All versions, then of a profile.

6. When prompted, press the Yes button to delete all version of the profile

7. When prompted to delete the file at the operating system level, press the No button.

8. Repeat steps 3 through 7 *for* all additional profiles associated with the source system

Reconfigure Operation Modes
RZ04

1. From the Operation Mode menu, select Timetable

2. Select Normal Operation and press the Change button.

3. Highlight 00:00 in the left hand column and press the Delete Assignment button

4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.

5. Once all the assignments are deleted, press CTRL+S to save.

6. If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.

7. Press F3 to go back to the main RZ04 screen.

8. Right click on one of the listed Operation modes and select Delete

9. Press the Yes button to confirm the deletion.

10. Repeat steps 8 through 9 *for* any additional operation modes

11. Press F5 to create a *new* operation mode.

12. Enter a name and *short* description *for* the operation mode

13. Press CTRL+S to save.

14. Press F6 to create a *new* Instance

15. From the Settings menu, select Based on current settings, then New Instances, then Set

16. Press F3 to go back to the main RZ04 screen.

17. Press the Yes button to save

18. From the Operation Mode menu, select Timetable

19. Select Normal Operation and press the Change button.

20. Highlight the 00:00 at the top and press F2

21. Highlight the 00:00 at the bottom and press F2

22. Press the Assign button.

23. Press F4 to select the operation mode created above.

24. Press CTRL+S to save.

Delete Update Failures
SM13

1. Set the fields as follows

Client: *

User: *

From data: 01/01/0001

From time: 00:00:00

2. Press Enter to display the list of outstanding update requests

3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing F5 to select all records, then selecting the Update Records menu, then Delete.

4. Press the Continue button to confirm the deletion.

Delete Batch Input Sessions
SM35

1. From the Edit menu, select Select All

2. Press Shift+F2 to delete all the batch input sessions.

3. Press the checkmark button to confirm

4. Press the Yes button to start the delete.

Reorganize Spool
SPAD

1. From the Administration menu select Clean-up Spool

2. Check all check boxes and enter 0 *for* minimum age

3. Press the Execute button

4. Once complete, press F3 twice to get back to the main SPAD screen

5. From the Administration menu select Check Consistency

6. Press the Delete All button.

SP12

1. From the TemSe database menu, select Consistency check

2. When the check is complete, press the Delete All button.

Delete Invalid Background Control Objects
SM61

1. Press F8 to *switch* in to change mode

2. Press the Cleanup List button.

Restrict Outgoing Email and Faxes
SCOT

1. Double click on the green Fax entry

2. From the Supported Address Types area, press the Set button that is beside Fax

3. In the Address area, ADJUST AS NECESSARY

4. Double click on the green SMTP entry

5. From the Supported Address Types area, press the Set button that is beside Internet

6. In the Address area, ADJUST AS NECESSARY

Adjust RFC connections.
SM59

1. Expand the TCP/IP connections section

2. Double click on the first entry listed

3. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system. Make changes as necessary.

4. Press the Test Connection button to test the connection

5. Press CTRL+S and then F3 to save and *return* to the list of RFCs.

6. Repeat steps 1 through 5 *for* each additional RFC connection

Convert Logical Systems

Under no circumstances perform *this* procedure on a Production system

BDLS

1. When warned to read the documentation, press the checkmark button.

2. In the Old logical system name box, press F4

3. Select one of the production Logical System names that needs be changed (i.e.WIIPRD400)

4. In the New logical system name, enter what that logical system name should be called on *this* newly refreshed system (i.e.WIITRN400)

Note: Ignore Error/Warning about duplicate system by clicking on the check mark.

5. De-select the Test Run and Existence check on *new* names in tables options

6. From the Program menu, select Execute in background

7. Press the checkmark button when asked to select a spool device

8. Press the Immediate button when asked *for* the schedule

9. Press Ctrl+S to save

10. Use SM37 to monitor the job

11. When job is complete, repeat steps 2 through 10 *for* any additional logical system names that need to be changed.

Adjust Logical Systems names

SALE

1. Expand Sending and Receiving Systems, then Logical Systems

2. Click on the execute icon beside Define Logical System

3. Press the checkmark button to confirm that the change is cross client

4. …

Allow Certains Settings to be modifiable

(Refer to Note 356483 *for* more Details)

SM54

1. Enter V_T001B in the Table/View box.

2. Select the Generated Objects option.

3. Press the Create/Change button.

4. Enter any access keys *if* requested

5. Change the Recording routine to no, or user, recording routine.

6. Press Ctrl+S to save

7. Press Enter *if* warned that you are changing a function group that doesn't belong to you.

8. You are prompted *for* transport. Create a *new* local transport.

9. Repeat steps 1 through 8 *for* the following objects. You can specify the same transport you created above.

V_T001B_GL

V_T093B_01

V_T093B_02

BSI Configuration (R3 HR Systems only)

SM59

1. Expand TCP/IP Connections

2. Highlight BSI70-US-TAX and press the Change button

3. Change the program field to

\\<hostname>\sapmnt\<sid>\SYS\EXE\RUN\TF60SERVER.EXE

4. Double check the target host and gateway point to the correct server

5. Press CTRL+S to save

6. Press the Test connection button to test. If the connect is not successful, take the
necessary steps to resolve the issue.

SE38

1. In the Program field, enter RPUBTCU0

2. Press F8 to execute

3. Select option BSI version 7.0

4. Press F8 to execute

5. BSI should *return* tax calculations. If there are errors, take the necessary steps to
resolve.

Reconfigure DB13 schedule
DB13

1.Using the printout created before the refresh, recreate the DB13 calendar.

Client Configuration
SCC4

1. From the Table view menu, select Display -> Change

2. When warned that the table is cross-client, press the checkmark button.

3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)

4. Define clients as follows depending on client role

Development

Client role: Customizing

Changes and transports *for* client-specific object: Automatic recording of changes

Client-independent object changes: Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

Quality Assurance

Client role: Test

Changes and transports *for* client-specific object: No changes allowed

Client-independent object changes: No Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

Training

Client role: Education

Changes and transports *for* client-specific object: No changes allowed

Client-independent object changes: No Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

Sandbox

Client role: Test

Changes and transports *for* client-specific object: Changes without automatic recording

Client-independent object changes: Changes to repository and cross-client customizing allowed

Protection: Client copier and comparison tool: Protection level 0

Restrictions when starting CATT and eCATT: eCATT and CATT allowed

5. Press CTRL+S to save.

6. Repeat steps 4 through 6 *for* any additional clients

Set System Change Option

Skip *this* section of the system is a Development or Sandbox System.

SE06

1. Press the System Change Option button.

2. Set the global setting to Not Modifiable

3. Press +S to save.

Release Background Jobs

Currently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled).

2007-10-13T13:39:00.000-07:00

How To Do the TMS Configuration?

We have two systems with version ECC 5.0

The SID is

XY1 - Development & Quality

XY6 - Production

Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?

How can I make through it?

First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure

------------------

1. Login to the system with sap* in client 000

2. Goto SE06.

3. Click Post installation activities

4. Goto STMS

5. It will ask for Domain controller name.

6. Enter DOMAIN_ as domain controller name and enter the description.

7. Click Save button

Steps to add the other system with Domain controller

----------------------------------------------------

1. Login to system with sap* in client 000

2. Goto SE06

3. Click Post installation activities

4. Goto STMS

5. It will ask for Domain controller name.

6. Enter System ID of the Domain controller

7. Enter DOMAIN_ as domain controller name and enter the description.

8. Click Save button

9. Login to Domain controller system

10. Approve the added system.

2007-10-13T12:01:00.000-07:00

Information on how the OPS$ Users Work

Does anyone have information or a good understanding of how the OPS$ users work and operate under an Oracle SAP environment.

I would greatly appreciate some assistance as I have problems with my Brconnect and Brbackup within DB13 due to the OPS$ users.

I need info on how to permanently delete the OPS$ users and then recreate it, due to the fact that I have incorrect OPS$ users in some of the tables affected by the OPS$ users.

Below is the document I have prepared on recreating the OPS$ machanism. It helped me solve all my problem on DB13 and also on Schema owner connecting to database.

Hope this could help you.

Also refer to the following sapnotes:

1. 400241 : Problem withe ops$ or sapr3 connect to oracle

2. 134592 : Importing the SAPDBA role (sapdba_role.sql)

3. 361641 : Creating OPS$ users on UNIX

4. 50088 : Creating OPS$ users on Windows NT/Oracle

5. 437648 : DB13: External program terminated with exit code 1/2

----------

select owner from dba_tables where table_name='SAPUSER';

## If owner is not the sid you require, then drop the table SAPUSER

Drop table "".SAPUSER;

#or#

Drop table "domain\OPS$SIDadm".SAPUSER;

## IF THE ANSWER IS 0 ROWS SELECTED THEN CREATE THE TABLE SAPUSER

# Check whether OPS$adm user exist, if no then create it

create user OPS$SIDadm default tablespace psapuser1d temporary tablespace psaptemp identified

externally;

# if exist then drop it;

DROP USER OPS$SIDADM;

# Grant connect & resource roll to OPS$ADM;

grant connect, resource to OPS$SIDADM;

# Creat table SAPUSER

create table "OPS$SIDADM".SAPUSER ( USERID VARCHAR2(256), PASSWD VARCHAR2 (256));

# update "OPS$ADM.SAPUSER with the follwoing command

insert into "OPS$SIDADM".SAPUSER values ('SAPR3', 'sap'); #sap =

# Under NT it is required that user sapservice can also access the SAPUSER table. In order to avoid problems with the data consistency, it does not make sense to create an additional

SAPUSER table having the same contents. You should rather define a synonym. Check if a suitable

Synonym exists by using the following call:

SELECT OWNER, TABLE_OWNER, TABLE_NAME FROM DBA_SYNONYMS WHERE SYNONYM_NAME = 'SAPUSER';

# IF NOT THEN CREAT IT

create public synonym sapuser for OPS$SIDADM.SAPSUER;

# if synonym already exists drop the existing synonym by the following command

drop public synonym sapuser;

#If another name is returned as first value:

DROP SYNONYM "".SAPUSER;

# AND CREAT it again with above command

# To allow access to the synonym (or the associated table), a grant needs to be executed.

The authorization for this has only the ops$ user who is the owner of the actual table - that is ops$adm.

Therefore, you need to log on with the corresponding operating system user (adm) and execute the following commands:

CONNECT /
GRANT SELECT, UPDATE ON SAPUSER TO "OPS$SAPSERVICE";

# Now you can recreate the synonym (not PUBLIC, if possible):

CREATE SYNONYM "OPS$SAPSERVICESID".SAPUSER FOR "OPS$SIDADM".SAPUSER;

CREATE SYNONYM OPS$SAPSERVICESID.SAPUSER for OPS$SIDADM.SAPUSER;

# COMMIT AFTER COMPLETION of the activity & restart the DB

2007-10-13T11:48:00.000-07:00

SAP Language Error when logging in after Upgrade to 40B

we have recently upgraded our system from 3.1H/Oracle 7.3.3/HP-UX 10.20/CIN 2.1A to 4.0B/Oracle 8.0.4/HP-UX 10.20/CIN 2.2A.

Upgrade went fine without any major hassles.

After upgrade when I am logging in it is giving a message in an information dialogue box "Specified Language has not been installed completely".

How to correct the error ? Everything is fine other than this.

I also got the same error for the same situation.

Here is the solution:

The reason for this is that table TCPDB was not maintained in your system before the upgrade and the upgrade process was unable to import the special texts as it couldn/t find the correct codepage ( in TCPDB ).

This can be rectified by the following:

Logon to 000 client

1) Run program rscp0004 in transaction se38 and this will give u options to insert a codepage. Look for codepage 1100 in the list and press F2 on this line as suggested, to insert the codepage.

2) In transaction SMLT check the 'status' of the installed languages. You will probably find that its the 'special texts' that were not imported successfully ( because the codepage could not be found in TCPDB at the time of the upgrade )

3) Schedule a 'full' import of the 'special texts' for the languages that are affected. Plsease note that when scheduling these imports, the options for Customizing and Documentation are automatically ticked for selection. Please remove these to leave only the Special Text selected.

You can observe the progress of the imports with sm37. After successful completion, you can logon again and there should no longer be an error.

2007-10-13T11:39:00.000-07:00

Comparing two SAP clients

Compares Customizing objects in two logical systems with transaction SCU0.

(clients in either the same R/3 System or different ones).

To compare objects, start the Customizing Cross-System Viewer in the logon client (client of the system in which you are logged on) and then logon in the compare client (client to be compared).

The Customizing Cross-System Viewer compares Customizing objects by the following criteria:

- Project IMG

This option shows changes in your project.

- Application components

This option compares Customizing objects in specified application areas.

- Business Configuration Sets

This option concentrates on Customizing settings which are of particular importance for the processes in your company.

- Transport requests

This option shows the objects which would be overwritten by a transport.

- Manual selection

In this option, you specify which objects are compared.

The compare client security level must be:

0 (unrestricted), or 1 (no overwriting)

You can set this in the client maintenance SCC4.

You must also create a Remote Function Call link in SM59.

2007-10-13T11:13:00.000-07:00

Find Your SAP Transport Request Number Even If You Forgot

If you happend to be one of those who forgot the transport request number of your abap program.

You can easily find it via the Versions Management.

Steps :-

Transaction SE38

Filled in your ABAP program name.

Then click Utilities -> Versions -> Version Management

SAP system will display this sample list :-

Versions: Report source ZPROGRAM

Version Cat Fla SAP Rel. Arch Request Date Time Author

Version(s) in the development database:

activ

46X

01.08.9999

15:21:56

SAP

Version(s) in the version database:

00002

00001

46X

ABCD123456

01.08.9999

00.00.0000

15:52:43

00:00:00

SAP

2007-10-12T16:52:00.000-07:00

Find transports imported into system by search criteria

To find transports imported in a particlar system log into it,

1. Use transaction se16

2. Table name is E070

3. Table contents

4. Enter your search criteria, by Name, Date, Time, etc.

Good to use if you suspect a problem in your system and want to trace back transports that went in that possibly could have caused the fault.

Transporting a Request From OS

To import a transport request from OS .

2007-10-12T16:47:00.000-07:00

Basis - Changing Parameters for the Transport Control Program

Remove the import all request (big truck) button from STMS

To change the automatically generated profile parameters for the transport control program:

Log onto the SAP System functioning as the transport domain controller (the QA or PROD system).

Call Transaction STMS.

Choose Overview -> Systems.

The system overview appears.

Double click on the SAP System you want to change.

In the SAP System, click Configuration -> Change.

The screen Change TMS Configuration: System appears.

Choose the tab Transport tool.

First, all the global parameters are displayed and then all the local parameters.

The global parameters are identical for all SAP Systems in the domain.

To change a global parameter to a local parameter, you must delete the global parameter and enter the new local parameter.

The operating system is only displayed if values exist for this field.

Finally to remove the import all request (big truck) button from STMS

click the Insert Line (button)
Tick Global
Fill in Parameter = NO_IMPORT_ALL, Value = 1.

Save your entries.

If you enter a parameter unknown to the transport control program, or a value that is not permitted, the transport control program ignores this entry in the transport profile.

2007-10-12T16:41:00.000-07:00

Restrict The Transport Access In Production

How to restrict the transport access in Production?

You can control by 2 way :

1. Limit the authorization object that can limit your transport activity, please use authorization object S_TRANSP and remove the value 60 (import) at your production server

2. Remove the STMS from the role.

List of transports that have been transported over a period

I need to know how we can get a list of transports transported over a period of time. I tried SCC3 but I'm not able to pull up the data. Is there any other way?

Example: List of transport request that have beem transported during Jan, Feb 20xx to production.

System Landscape: Dev-->Test--> Production
DB:--Oracle Machine--SUN
Appln Servers: AIX
SAP version: 4.6C

Goto STMS --> Import overview --> select the system which you want to see the log of import queue --> select goto--> import history --> there select the data coloum and set the filter as per your requirement.

You can also execute SE03, Requests/Tasks, Find Requests, in the production system or use SE16 to query table E070.

How to import mass transport request using SCC1 in local client?

We have 3 clients in development system , we need to import multiple requests at a time using SCC1 in another client. Using SCC1 I am able to select mass request at a time but not able to see mass transport menu.

How to do mass transport steps using SCC1 in local clients.

You could try using SCCL and select "Customising" Profile.

What is Role Transportation from development server to Production server. I have also create New role, but how to bring out the role to production server. We have installed IDES 4.7 Server.

In Development:

Run TCD PFCG

- Enter the Role to be transported in the text box.

- Click on truck symbol left corner of options bar

- then series of screens will appear.

- In one of the screen don't select user assignment.

It will also ask you the change request no.

After that go to TCD SE10 and release the request.

NOW go to stms and select Quality system and import the request into it. After testing you can import the request in PRD system.

2007-10-12T16:40:00.000-07:00

Guideline to upgrade from 3.1 to 4.6 with HW upgrade at the same time

1. Do a system copy of the 3.1 instance to the new box.

2. Bring up 3.1 instance in new box.

3. Upgrade the Development/Staging instance and resolve all errors and issues. Create SPAU/SPDD modifications, if any.

4. Timing the upgrade processes - to determine how long the whole processes take.
Your managers will like to know how long it takes to complete the upgrade.

5. Do a system copy of the 3.1 instance to the new box again

6. Bring up 3.1 instance in new box.

7. Make the 3.1 instance in new box as the Production instance.

8. Make the 3.1 instance in the old box as the Development/Staging instance or a standby Production Box in case the upgrade fail.

9. Upgrade the Production instance as planned (i.e. 3 full working days).

10. Acceptance testing.

2007-10-12T16:38:00.000-07:00

SAP Message : TP_CANNOT_CONNECT_SYSTEM

Using spam, trying to import SPAM UPDATE, I get the above message together with TP_INTERFACE_FAILURE.

1. tp works fine when I am doing transports (tp import devk90000 qas client=400 u1 or addtobuffer).

2. niping -t SELFTEST works fine

I worked through notes 44946 and 96907, but could not resolve the issue.

The support packages have been uploaded from the DEV box into the QAS queue. The DEV and QAS boxes are in the same centre on the network, by fibre. I am working on QAS.

I get this message in QAS:-

"SAP system is waiting for the inclus. in transport domain"

When trying to update the config from DEV client 000, I get this message:-

System DEV is unknown in the Transport Management System

Diagnosis
An error occurred in the TMS communication layer.

System: QAS.DOMAIN_DEV(000)
Function: TMS_CI_CHECK_ACCESSTOKEN
Error: UNKNOWN_SYSTEM (DEV)

System Response
The function terminates.

Procedure
Log this system on to the Transport Management System.

If this error occurs in the function TMS_CI_CHECK_ACCESSTOKEN, then the TMS configuration was deleted in the R/3 System QAS.DOMAIN_DEV(000).

Configure the TMS in this R/3 System again.

You need to:

1. logon to the transport domain controller with admin user in client 000.

2. Run STMS

3. System overview

4. select QAS

5. Menu line option "SAP system" --> "Approve"

6. Distribute configuration

When you are logged on the transport domain server and run STMS --> System Overview. Is QAS listed? If so, select it and perform the checks under "SAP Systems" in menu line.

If they are not successful you might want to try the following to configure the TMS on QAS from scratch.

First delete QAS from system overview on the domain server.

Then do the following steps...

In your QAS system in client 000.

Run tcode SE06 --> Database copy or Database migration --> Perform post-installation actions.

Then confirm that you want to delete all old CTS/TMS config and type in QAS as source system for the database copy.

Then run STMS again and type in the correct data for the transport domain controller.

Logon to the transport domain controller in client 000. Run STMS. Open system overview.

Choose the SID of the QAS system and click on "SAP System" in the menu and choose Approve.

This will add the QAS system to your TMS config again.

Perform the checks from menu line "SAP Systems" again.

It seems like a lot maybe, but it only takes a couple of minutes to perform.

2007-10-12T16:35:00.000-07:00

Transport of ABAP Query

I am involved in this upgrade project to 4.7

The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.

I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.

You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.

You download the infosets, queries etc into a file and load them into whichever system you wish.

Just wanted to share my experience of transporting queries:

I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.

Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)

Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).

Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).

Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this
time specifying 'Copy Standard Area -> Global Area'.

(Now my queries etc were available in new system).

Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.

2007-10-12T16:34:00.001-07:00

Upgrade SAP or Installation of SAP R/3 and ECC

What is ECC? Where to find the installation steps of ECC 5/6.0 with SQL as database and on windows platform with the steps including Solution Manager installation?

http://service.sap.com/instguides

ECC means Enterprise Central Component.

There are all the relevant installation guides. You NEED SAPNet access because without a registered and licensed SolMan installation number you will not be able to generate the SolMan key for the ECC installation.

Upgrade to 4.7

Have you gone through an upgrade to 4.7?

What are the difference or changes associated with 4.7.

If you are currently on 4.6C and are inching forward to upgrading to 4.7 then this information might be useful to you.

There is very little difference between 4.6 and 4.7, the only "steps" you should need are steps in SU25 ( skip step 1) Then go through all your role and perform a merge old new to bring in the new authorization objects

Just to forewarn you of a potential problem which have been encounter at the point of writing.

After updating/ modifying roles in step 2C, when going back into 2C to make sure all roles are now green, 70% have gone back to red!

The maintenance done is ok, but there seems to be a problem while trying to go back into the roles again to re-generate.

SAP recognizes them as needing "adjustment", so you cannot pick them up in mass generate in PFCG as they do not come in, even though the authorizations tab is red.

This problem is currently with SAP and it is confirmed that nothing have been done wrongly.

Generally, the work is quite manageable in the upgrade, but don't be surprised at how big the upgrade is when compared to upgrading from 46b to 46c.

If we have full software of 46c and 47E is it possible to upgrade 46c to 47E or there is a seperate 47E upgrade software need to be requested from SAP?

Where I can get the document with upgrade steps on the service market place?

It is of course possible and supported:

http://service.sap.com/inguides

--> SAP Components

--> SAP R/3 Enterprise

--> (choose your version)

at the bottom there is an "Upgrade guide" for Windows and Unix.

For Upgrades it is recommended to read ALL the notes mentioned in the
upgrade guide and to make sure one is using

- the correct version of the "tp" program

- the correct version of the "R3trans" program

- the correct version of the "R3up" program

All that is explained in the upgrade guide and in the corresponding notes.

If this is your first upgrade you should take a person, that has some experience on doing that for the first time.

Installation of SAP R/3

Currently we are going to install SAP on a new IBM server from the existing COMPAQ server. Where can I get the steps for that.

Configuration is :

OS - windows 2003 server
DB - Oracle 9i
SAP 4.7

http://service.sap.com/instguides

--> SAP Components

--> SAP R/3 Enterprise

--> SAP R/3 Enterprise Core 4.70 / Ext. Set 2.00 (SR1)

--> Inst. Guide - R/3 Enterprise 4.7 x 2.00 SR1 on Win: Oracle

The above url is the SAP Service Marketplace with all the information you need to install, configure and run system. You need to be a valid licensed customer with a user ID and PASSWORD to use that.

Without access you won't be able to successfully run any SAP systems because it has notes, patches etc.

2007-10-12T16:30:00.000-07:00

Transport Request within same Server Different Clients

I have 3 clients under one SID (dev 130,140,150).
And we have more than 400+ transport requests in client 130. How can we transport these requests to other clients of 140 & 150. If I want to use tcode SCC1, that can be done only one tran. request at one time.

Do I need to write a script within unix?

SAP 4.6C
Oracle 9.2
AIX 5.2

Try STMS.

Click on the "import overview"

Double click on your target system

Click "refresh"

Click on "import all request" or ctrl+F9

Specify the target client

Execute the transport

Done...

But this will import all request.....thousands of them...

You can use Extended Transport Control.

Extended Transport Control is another way to set up the Transport Route so that the route is system and CLIENT specific.

In other words, when you release a change request in DEV Client 0XX it will not only automatically be added to the Import Queue for QAS but also 0X1, 0X2, of DEV.

To set this up requires the steps below:

1) Open the file TP_DOMAIN_DEV.PFL (located on your transport domain controller such as the DEV box. The file will be in usrsaptrans/bin)

Edit with notepad for each parameter on each system:

DEV/CTC = 0

Change to =1

2) Next you need to create Target Group before creating the transport route.

Create a Target Group:
Access the initial screen of the graphical or the hierarchical editor in change mode. STMS > Overview > Transport Routes (the default editor will appear, either Hierarchical or Graphical, to change the default editor : STMS > Extras > Settings > Transport Routes. You can also switch to one or the other from Goto > Graphical Editor.)

> Configuration > Display Change > (or change icon or F5)

Edit > Transport Target Groups > Create

In the dialog box, Create Target Group:
Enter a name for the target group /GR_QA/ (The name must begin and end with a forward slash /)

...and a description Targets for Consolidation route

Choose "Insert line"
Enter the required target system/client combinations
Use a separate line for each client.

Example:

Target System
Target Client
Client Name

DEV
0X1
Sandbox

DEV
0X2
Testing

QAS
0XX
Quality Assurance System

The idea is that we want to include the clients that will get an addition to their import queue when we release a change request from DEV.

Choose Transfer

Now you have to change the transport route to include the Target Group you created.
STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Delete

Now create a Transport Route with Extented Transport Control:

STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Create > Extended Transport Control icon at lower left of dialog box. > Consolidation route, enter integration system and transport layer. In Target system/client enter the SID of either an R/3 System and a client or an existing Target Group.

Each System must be specified by System and Client. The Target Group can be used for the consolidation system.

Distribute and activate the changes as usual by choosing Configuration > Distribute and activate

NOTE: After you set up Extended Transport Control there might be requests in an import queue that will show a red status in the CTL column. This is because these change requests need a client specified before they can be imported. These are old requests that were already in the queue.

From Import Queue Screen Mark the change request

Choose Request > Target Client > Set

Enter the Target Client ID and choose Enter.

To change a target client before starting an import:

Import Queue Screen > mark Change request > target client > change > enter target client id and choose enter.

Hope this helps.

2007-10-12T16:28:00.001-07:00

Transport guide Tips for Different SAP Objects

You may be wondering if you can transport certain SAP objects, and if possible, how?

Here are tips for different objects:

1 LSMW There are 2 ways for transporting LSMW data from a system to another.

1.1 Export/import This method gives you the opportunity to select the subprojects or objects you want to transfer. Hence you don't transfer the object a colleague might have created and that should stay in development system. LSMW -> Extras -> Export project

1.2 Transport request With this method, you can transport a LSMW project in full (you can not select the objects you want). With this method, the project will be transported as any other SAP object in a transport order.
LSMW -> Extras -> Create change request

2 Program variants

If you have several program variants in a development system that you want to transport, use the following method to transport them:
Execute program RSTRANSP (via se38) and inform the program and/or variant names (you can transport variant of several programs in one shot).

3 Layout In some transactions, one can save layout of the screen (sort, filter, ... criteria).

These layouts can be transported: In the required transaction, when your layouts have been saved, go to Settings -> Layout -> Layout Management. Select the desired layouts and go to Layout -> Transport… There you can add your layouts in existing TO or create a new one.

DB data

In some unusual cases, you might have to transport data of a SAP table.
Go to transaction SE16, select your entries and go to Table entry -> Transport entries. It's only possible for some tables...

If you cannot do it that way, you have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list.

Go in modification mode and add a new line with:

PgmID = R3TR
Obj = TABU
Object name = Name of your table

Double-click on the created line and, depending on your need, put '*' in the key field or double-click on it and select the key you need to transport.

4 Queries

Queries, datasets and user groups can be exported/imported between the systems thanks to the program RSAQR3TR.

5 Standard texts

Standard texts used in SAPScript (created with transaction SO10) can be included in transport orders. You have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list. Go in modification mode and add a new line with:

PgmID = R3TR
Obj = TEXT
Object name = TEXT,,ST,

Example :

R3TR / TEXT / TEXT,YMM_MEDRUCK_MAIN_16_EC,ST,F

You can also copy a Sapscript object (like standard text) with the program RSTXCPFS.

How to transfer a executable report from dev server to prd server? And that report contains one user defined view. I want to transfer *the report and the view* from dev to prd.

At the time of creating the report itself it will ask you to select the PACKAGE.

Here you should select the package instead of $TMP package, which for transporting the objects and create a new request and save it. If you want to give a TCode for the program that you have created just give SE93 in the GUI Window and give the TCode name there and enter the Create button. there you should give the name of the object or program that you have created and save it. After completing this go to SE09 TCode and select the MODIFIABLE Check box and press DISPLAY Button.

In the next screen you have to select the Request that you have created and click the check syntax icon. If no errors are there then you can press the Release Directy icon to transport the request to the Quality system. From there it has to be transported to the Production System. The latter part BASIS will take care.

2007-10-12T16:24:00.001-07:00

Meaning behind those unconditional tp command mode

Can anyone tell me what's the meaning behind all those unconditional mode U1 or U126 or U148 or anything?

tp import transportrequest ,,sid,,, clientxxx U1
tp import transportrequest,,sid,, clientxxx U126
tp import transportrequest ,,sid,,clientxxx U148

Note: here ,,= <>

The u stands for unconditional force ( how hard you want to force the request into the system - do you want to overwrite without warnings, or softly try to load the objects).

1: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.

2: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.

3: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.

4: When used with tp import, it overwrites the system-dependant objects.

5: During the import to the consolidation system it permits the source systems other than the integration system.

6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.

7: During import phase it ignores the limitations caused by the table classification.

8: During import it ignores that the system is locked for this kind of transport.

u128 is combination of 128 OF THE above points.

2007-10-12T16:19:00.000-07:00

Function and Role of User Types

In "USER MAINTENANCE- SU01" --> in the "logon tab" there are 5 different "user type"

1. dialog
2. system
3. communication
4. service
5. reference

Kindly mention the function and role of all the above mentioned user types specifically and hows is one user type different from another.

These are as follows:-

1. Dialogue:-

For this kind of users:-
GUI login is possible.
Initial password and expiration of passowrd are checked.
Multi GUI logins are checked.

Usage:- These are used for GUI logins.

2. System

For this kind of users:-
GUI login is not possible.
Initial password and expiration of passowrd are not checked.

Usage:- These are used for internal use in system like background jobs.

3. Communication

For this kind of users:-
GUI login is not possible.
Users are allowed to change password through some software in middle tier.

Usage:- These are used for login to system through external systems like web application

4. Service

For this kind of users:-
GUI login is possible.
Initial password and expiration of passowrd are not checked.
Multiple logins are allowed.
Users are not allowed to change the password. Only admin can change the password

Usage:- These are used for anonymous users. This type of users should be given minimum
authorization.

5. Reference

For this kind of users:-
GUI login is not ible.
Initial password and expiration of passowrd are not checked.

Usage:- These are special kind of users which are used to give authorization to other users.

2007-10-12T16:18:00.000-07:00

Hide the User Menu

Is there a way of masking or hiding the User Menus as we are using SAP Standard Menu instead of User Based Menus?

To put it simple, when the user logs on to the system he should have only the SAP Standard Menu.

You have two ways to control this :

1. Default hide for all the SAP users.

Goto SM30 and edit the table SSM_CUST and set ALL_USER_MENUS_OFF = YES and transport the same in production server.

2. Hide based on individual SAP users.

you can also try SM30 and maintain table USERS_SSM for individual users.

2007-10-12T16:16:00.000-07:00

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 different reasons and in different way.

In the latest versions of SAP, actually two types of usergroup exist, the authorization user group and the general user groups.

Naturally the main reason of user groups is to categorize user into a common denominator.

The authorization user group is used in conjunction with S_USER_GROUP authorization object. It allows to create security management authorization by user group. e.g. you can have a local security administrator only able to manage users in his groups, Help-Desk to reset password for all users except users in group SUPER, etc...

The general user group can be used in conjunction with SUIM and SU10, to select all the users in a specific group. User can only be member of one authorization user group but several general user group.

One of the Primary uses of user groups is to sort users into logical groups.

This allows users to be categorised in a method that is not dependent on roles/AG's/Responsibilities/Profiles etc.

User Groups also allow segregation of user maintenance, this is especially useful in a large organisation as you can control who your user admin team can maintain - an example would be giving a team leader the authority to change passwords for users in their team.

The most important factor identified is that the lack of user groups is an indication that there may be problems with the user build process. This is very "fuzzy" but is a bit of a warning flag.

The Auditors job is to provide assurance that SAP is set up and administered in a way that minimises risks to the financial data produced. If the only thing they have picked up on is the lack of usergroups then you will be fine.

If you are in any doubt whatsoever ASK THE AUDITOR. They would have produced a report listing why they feel there is a risk by not having User Groups implemented. If you feel that the risk is mitigated by other measures then let them know. It works best as a 2 way process and both parties can learn something.

2007-10-12T16:14:00.000-07:00

How to delete expired roles?

Here are 3 notes you may want to review to see if there is any helpful info, plus some documentation that may be helpful for others....we are going from 40B to 47 and have had a few issues with role deletion

Notes: 312943 504412 & 313587

Additional info

First, the report PFCG_TIME_DEPENDENCY is functioning as designed. It was not designed to remove activity groups.

Second, in transaction SU10 you must have the valid from and valid to fields filled in with the actual dates, 04/08/2002, in order to remove the invalid activity group. You need to be sure that the remove user radio button set in the role tab. But in the profile tab, the add user radio button is selected by default.

What you have to do is go to profile tab and select the remove user radio button. You have to make sure both role and profile has the same radio button selected, i.e. remove from users. Only then when you click save, it will allow you to delete the role from user.

In transaction SU10, you need to complete the following steps:

1. Click on the Authorization data button.

2. Entry the users name, latimerc

3. Click on the execute button.

4. Put a check in front of the users name.

5. Click on the transfer button.

6. Now highlight the user.

7. Click on the pencil button.

8. Click on the Activity Groups tab.

9. Enter the profile name (PM_NOTIFICATION_PROCESSOR).

10. Enter the valid from and valid to dates (04/08/2002).

11. Change the radio buttons to remove user from both the Activity Group and Profile Tabs.

12. Click on the trash can.

In another customer message the following was provided by developement:

We don't have a regular functionality for mass deletion of roles. But if you want to avoid the deletion by hand or with an own created report, I would suggest the following:

The attached note 324962 includes the report ZDELETE_RY_T_AGRS which could delete all roles with names like 'T_....' or 'RY....'. The report gives you a list of all these roles and deletes then the selected ones. You can modify the report to get all your roles in the selection list. Therefore you have to change the following:

SELECT * FROM AGR_FLAGS INTO TABLE L_AGR_FLAGS
WHERE FLAG_TYPE = 'COLL_AGR'
AND FLAG_VALUE = 'X'.
SORT L_AGR_FLAGS BY AGR_NAME.
LOOP AT SINGLE_ACTGROUPS WHERE AGR_NAME+11 <> SPACE AND <<<>
( AGR_NAME(2) = 'T_' OR AGR_NAME(2) = 'RY' ). <<<>
LOOP AT SINGLE_ACTGROUPS WHERE AGR_NAME+11 <> SPACE. <<<>

READ TABLE L_AGR_FLAGS WITH KEY AGR_NAME = SINGLE_ACTGROUPS-AGR_NAME
BINARY SEARCH.

Text from an additional customer message as further help:

- go on role tab

- select remove from user

- enter ZR.PRD.GENERIC and date : 06/04/2002 12/31/9999

- go to profile tab

- select remove from user

- save

- do the same for ZR:HR:ESS from 01/01/2002 to 12/31/9999 and worked
from date for testid was 01/01/2002 and testid2 02/01/2002 and the 2 assignement were deleted And the roles were removed from the 2 UMR.

So it works as designed.

2007-10-12T16:12:00.000-07:00

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.

How can I create multiple User Id at Random

We usually created Id though SU01, it only one by one.
Can I create multiple user id having same profile at once.

Yes you can, use tcode SCAT. First, make sure your client setting (SCC4) is enabled with ' X eCATT and CATT allowed'. Just in case your Production disabled this.

- Then, you need to create a simulation (test case) of creating new user id by calling tcode
SU01 later.

- Test case must start with Z, example ZCREATE_NEW_USER. Create this case, put title and
choose component as BC (basis components).

- Save and choose Local if you dont want to transport it or choose a dev. class (example ZDEV)
if you want to transport it later.

- Go back and click Change button. Then key -in Object as example SU01, and choose Record
button on top. When it prompts to enter Transaction code, key in SU01 (if for roles,
key-in PFCG) and begin recording. As usual in SU01 create 1 user id, dept field, password,
roles, group and so on.

- Make sure you press Enter on each field because we want to capture the value/object and
SCAT is a bit stupid if you become familiar later....but still useful...indeed.

- You will see a clock on the bottom which means the recording process is on going.
Once done, click Back button and press End button to end the recording.

Note - I noticed you said the profiles are all the same. Then this is much easier...no need to enter the roles/profiles, just duplicate this ID and change the name, dept and password only.

Okay..first stage has finished. Then double click the Object to begin inserting parameters. Then you will see an object for each fields that you run from SU01. Choose the right field example user id (BNAME) and choose button 'Insert Import Parameter (F6)' and you may click Next Screen to 'watch' what have been recorded and proceed to choose several other objects like password field (PASSWORD1, PASSWORD2), roles field (AGR_NAME), group field etc. If you happen to choose the wrong object, then you can reset back (Edit -> Reset Parameterization). You may see so many junk fields captured and this is because SCAT records every steps/dialogs.

Once done, choose Back and save this case. Then you need to click 'Goto -> Variant -> Export' and save it. After that use Ms Excel to open it and begin inserting all other user ids. Save and close. Remember to close this file because SCAT will use it.

Then last one, get back to SCAT and click button execute, processing mode chose Background, choose external file 'the one you created with Excel' and execute. At this moment don't use tcode SU01 bcoz you may interrupt the simulation. Wait for the logs. If you see reds then error was
happening.

Hoping this will help you. I have done (Sap 4.6C) this to create thousands of user ids and also thousands of roles/profiles (pfcg). I heard with Sap 4.7, the SCAT has so many extra features.....

Correct me if i'm wrong elsewhere.....just shared my experience.

2007-10-12T16:10:00.000-07:00

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)

2007-10-12T16:02:00.000-07:00

Different methods to Lock or unlock SAP users

I want to lock all the users in SAP during MTP. I know using SU10 we can do it. Any other alternative ways to lock the 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

Execute program EWULKUSR in SE38

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

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 <>

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.

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 !=
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.

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:

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).

2007-10-12T15:20:00.000-07:00

Apply Support Packs To My SAP SYSTEM

How can I apply support packs to my 4.7 IDES SYSTEM?
SAP"- SAP R3 4.7EE,

DATABASE : ORACLE 8.1.7

OS : WINDOWS 2003 SERVER

What is the step by step procedure and how to apply in r/3?

You have various issues with your setup:

- Oracle 8.1.7 is not supported under Windows 2003

- Oracle 8.1.7 is out of maintenance since three years

During SP application you will maybe run into problems that can't be
fixed since your installation is just too old and unsupported.

As mentioned, it's true that it won't get supported on Oracle 8. The best combination would be with 9i

Any How I have mentioned the steps below to apply for patches.

To Apply Support packs first up all you need to download the patches. When you have the downloaded the file i.e.. (*.car ) patch file then you can extract and apply it in two ways.

1. Go to command prompt through cmd (if you are using windows) and go to the folder where you have download these files ( could be in \downloaded folder\ ) type this command on command prompt without quotes "sapcar -xvf .sar".

Now it will create a folder called EPS and a folder called IN inside EPS. Go to this folder and it will show two extracted files with extension " .att " and " .pat ". Copy this two files into yours trans\eps\in folder which could be something like \usr\sap\trans\eps\in folder.

Then type spam on your session and navigate to Support Package\Load Package\From Application Server and it will ask for Path confirm it Say " YES"Select the patch imported and double click on it and then click on small truck Icon and it start Import.

2. Type Spam on session then navigate to Support Package\Load Package\From FrontEnd \ and Navigate to path where you have downloaded the *.SAR file of Support Pack.

Now it will open a popup window and then click on decompress button ( It is front-End process for extracting or decompressing .sar file in .pat and .att extension )

After that click on Display-Define button on right hand side.) Select the BASIS or ABAP patch ( whichever you are applying *) what ever you are after and import it in queue. After that click on Small truck Icon in menu i.e.. (import Queue) and it Starts importing.

* Note :- Basis patch starts with KBxxxx.sar and Abap Patch start with KAxxxx.sar likewise.

* Note :- If you are applying all support pack it may ask you to increase your spam level (SUPPORT PACK MANAGER).

2007-10-12T15:13:00.000-07:00

Reporting a Problem to SAP

When I tried to report a problem to SAP using

http://service.sap.com/message url it provided 4 steps to follow:

1) Choose system
2) Prepare Solution Search
3) Find Solution
4) Enter Message

I could do the step 1 but dont know what to do at steps 2, 3 and 4.

SAP changed the customer message screens so you now have to navigate through a search of the SAP Notes before being able to create a message.

We usually search the Notes extensively before we create a message, so we just enter a blank search and then go on to create the message.

Follow the steps, It may solve your problem:

1. Copy following url into web browser : http://service.sap.com/message

It will ask you for your OSS ID and password .
A Screen which contain a push Button Select System displayed .

2. Push the Button Select System .
It will open a sub screen in which there will be a hierarchical structue which looks like........

Your SAP Customer Number

-SAP Installation number for a specific product1
radio Button>System SID1 for which you have registered a license
radio Button>System SID2 for which you have registered a license

+SAP Installation number for a specific product2
+SAP Installation number for a specific product3

 add closing at end ie '>' on each tag.......

Here + indicate that you have a sub tree .
Specific product like SAP R/3 T for Services , SCM , CRM , ERP etc

3. Select the system for which you need to log a message
It will take you to message screen screen.

4. Select you domain for problem for example Basis problem with Database where dataBASE IS oracle then Message type will be BC-DB-ORA
* .

5 Select priority of Message

6 . Write Message and send it to SAP

2007-10-12T15:11:00.000-07:00

SAP Transaction code to pre-compile all system program

If I have to run SGEN and have to recycle the server as well for clearing out memory, does it make sense to run SGEN first and recycle afterwards, because SGEN will sort of litter the memory or is it inconsequential what runs first.

SGEN is ued to "compile" ABAP programs. Results are put in database.

So, if you restart SAP, compiled results will still be in the database, so, no need to run SGEN again.

Make use of the transaction 'SGEN' to re-generate all the SAP programs after you change version of your SAP kernel, upgrade SAP system or apply support packages.

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.

2007-10-12T15:08:00.000-07:00

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

2007-10-12T15:05:00.000-07:00

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.

2007-10-12T14:57:00.000-07:00

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.

2007-10-12T14:54:00.000-07:00

Upgrading SAP Kernel, Hotpatches and Database Startup

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

How do I find out the current patch level in SAP R/3 4.7

You can use either of these two methods:

1: Follow the path

System --> Status --> Component Information (The Magnifying glass button in the SAP System Data section)

2: Use the Transaction code ---- spam

spam(Support package manager) --> package level

Steps to Start Your Database After Kernel Upgrade

Do these steps to start your database:

1. Open command prompt

2. Give command: SQLPLUS "/as sysdba"

If its giving message connected to idle instance then proceed:

3. Give command: startup open

If its giving error that database is already open, shut it down first. Then first check what database process is up and running.

4. Try stopping the database: shutdown immediate.

5. Follow step 3 again after shut down the database.

6. Exit from SQLPLUS

7. Run command on command prompt: R3trans -d

Check the results whether its still giving error or if it completed with 000 return code, then try starting SAP.

Follow the above steps.

2007-10-12T14:43:00.000-07:00

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)

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.

What is mean by OSS how to work on that?

OSS are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.

2007-10-12T14:42:00.001-07:00

Apply OSS Notes On My SAP R/3 System

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

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.

SAP Basis Certification Sample Questions

2007-07-10T15:12:00.000-07:00

SAP Basis Certification Sample Questions

Caution: more than one answer may be correct.
Please mark ALL correct answers.

Question:

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

Question:

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

Question:

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

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

Question:

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.

Question:

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

Question:

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.

Question:

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

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

SAP Basis Certification

2007-07-10T15:10:00.000-07:00

SAP BC Certification - Is It Worth Getting Certified

Do you think it is worth getting certified? How many test are required for the basis certification? Is it required to take classes or can I study on my own?

Now days there's so many choices. Start at http://www.sap.com/services/education/index.epx, pick your country and select Certification Program.

If you've got enough years of experience I don't think certification would make much difference to a full time job.

But if you're a contractor, I could see it highly worthwhile. Upgrades / Migrations have to have certified Basis Consultant.

Do you require training to attend certification?

I have done certification in the month of FEB 2003. I took training also.

If you ask me the question - Do you require training to attend certification?

I will ask you following questions-

1. Do you have time to attend the course in the first place?

2. Do you want to inform outside world that you want to prove yourself? Coz, World listen you when you are certified. No matter how bad your skills are.

3. Do not want to take chances?

4. Invest money? Remember I am using word invest money? Investment is always linked with expectations of future higher returns?

5. Can keep job and other onhand tasks away for the training time? In otherwords have difficulty to free yourself and so the best choice is making yourself free by attending course would help?

6. Want to know in and out of SAP? Coz course would try to give you the behind picture in depth (practically may not be possible but may be true to some extent)

7. Conceptually weak in many of the aspects of basis?

If your answer is "YES" then better take course before writing exam?

Esp. in IT, you learn faster when someone guide you rather than you do self study. Of course with Basis certification you need both as time is limited. Also you may have to fight for best tutor (remember).

There are pros and cons. You are the better judge. If you can give more valid reasons for the choice you made. Go ahead. Sure you will win. Most important is committment.

Brief Description About SAP Basis Implementation

2007-07-10T15:03:00.000-07:00

There is no standard Implementation process, it purely depends on which methodology person have adopted for implementation. I will give you broad view of implementation project... I am just starting from sizing of the servers ...

1. Identify the no of users and type of users

2. Design the technical system landscape of servers

3. Do the sizing based on users, documents created.

4. Convert your sizing requirement in to Hardware requiremnet

5. Consider the backup procedure also

6. Then start with the setup of development landscape

7. Define client strategy, transport strategy, User management.

8. Fix the support package levels.

9. Tune the system for performence

10. set up the QA systems

11. Define client copy strategy

12. Setup the PROD systems

13. Apply for Pre Golive report

14. Monitor system of db load

15. Apply post golive report

Monitor and Administrate 4 SAP Systems

2007-07-10T15:01:00.002-07:00

If there are 4 systems installed SAP, how should I connect all of them in one network so that I can administrate the 4 systems with one among them as main server.

This should help you:

After installing an R/3 System, you can use transaction RZ20 to monitor the system. To monitor all systems of your system landscape centrally from one system, first customize the alert monitor by choosing Tools > CCMS > Configuration > Alert monitor or calling transaction RZ21.

Then, to specify the remote systems by System ID and RFC destination (which must have been created beforehand), choose Technical infrastructure > Create remote monitoring entry.

Next, to change your monitor definitions (you can only change your own monitors), choose Tools > CCMS > Control/Monitoring > Alert monitor or call transaction RZ20.

Activate the maintenance function by choosing Extras > Activate maintenance function.
Then, double click on the monitor and choose Monitoring change.
Parameter R3system defines which systems can be monitored by an alert monitor. Change parameter R3system from (only the current R/3 System can be monitored) to (all R/3 Systems defined in RZ21 can be monitored). Save the changes.

It will help you monitor & use spome other activities centrally.

Tcodes used for Daily System Monitoring

2007-07-10T15:01:00.001-07:00

After running daily system monitoring transaction, what should we check for:

In st22 look for the core dumps if any and report to the respective consultants and try to know why it happened.

In sm21 try to check for errors.

In sp01 try to see if any spool jobs have failed.

In st02 look if any swaps are happening, swaps are not good for performance.

In st04 look for Database alert logs and Performance.

In st03 look for ratio hits.

In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system

In db13 look if the jobs have run successfully.

In sm37 look for any cancelled scheduled job and take action appropriately.

In sm12 look for any pending locks from the previous days.

In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.

SAP Administrator Daily Activities

2007-07-10T14:59:00.000-07:00

SAP DAILY ACTIVITIES

1] Check that all the application servers are up:
sm51 SAP Servers
sm04/al08 Logon Users

2] Check that daily backup are executed without errors
db12 Backup logs: overview

3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.

4] Operating system Monitoring
st06

5] Extents monitoring
db02 Database monitoring--Check for max-extents reached

6] Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.

7] Check system log
sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events.

8] Review workload statistics
st03 Workload analysis of
sto2 tune summary instance

9] Look for any failed updates
sm13 update records

10] check for old locks
sm12 lock entry list

11] Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.

12] Review and resolve dumps
st22 ABAP Dump analysis

13] Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace

14] Archive backup
brarchive -f force -cds -c
Insert the archive backup tape

15] Review NT system logs for problem
-> NT system log- look 4 errors or failures
-> NT security log- failed logon 2 sap servers
-> NT Application log -look 4 errors or failures

Basis Administration Questions Answers

2007-07-10T14:53:00.000-07:00

What is th difference between Sap lock and database lock?

A "SAP lock" is named "enqueue lock", the enqueue is on a much higher level, e. g. a complete sales document is locked there whereas in the datbase usually only row locks exist. Since SAP runs on more database than Oracle (thanx god) one needed to have a mechanism, that is database independent and on a higher level.

What is the diff between clients 000 and 001?

Client 000 is the SAP source client, client 001 exists only on certain installations (e. g. solution Manager).

I would like to know is there anyway to transport roles from Production to Development or Sandbox.

Goto PFCG and enter the role which you want to transfer to other system. goto utilities->Mass download it will ask the path where to download/save that role on local desktop give the location and save it. Next logon to the system where you want that particular role.

PFCG-> Role -> upload.

Give the path where the role is saved. it accepts and generates successfully.

What is the need of having Development system?

To develop and custamize SAP to companies requirement. say if you dont have DEV, after go-live(started using SAP (PRD}) if you want to do some changes to application, you cannot do changes directly to PRD server, which may cause problem the PRD server live data. so you do the required changes on DEV first and test them on QAS, if it works fine then transport the same to PRD.

Difference between Application server and Central Instance?

AS: Is just a dialog instance.

CI: Is Dialog instance + Database Instance.

What is Transport domain and Domain controller?

TD: is the collection of transport controller, trans directory and all other systems in the group.

TC: A system which will have trans directory, and in which the total landscape is designed and maintained. in stms you can see all these.

What are SNOTES ? How to apply them in SAP ?

The name of the transaction is SNOTE. A "note" in general is a hint, documentation, error/bug description and may contain code corrections, that are applied with the transaction SNOTE.

What is OSS ?

OSS is the old name of the nowadays "sapnet" which contains everything you need to run SAP a program, patches, installation/upgrade documentation etc.

What are different modules used like EP, XI, CRM ,BW, etc?

Those are not different modules but different products.

EP = Enterprise Portal

XI = Exchange Infrastructure

CRM = Customer Relationship Management

BW = Business Warehouse (that is the old term), it's now call BI (Business Intelligence)

What is the correct use of SPAM, SAINT, SPAD and SPDD transactions. When should we use each?

SPAM is for installing support packages, SAINT is used to install new addons. SPAD is for creating printers (I assume you meant SPAU) and SPDD is for adjusting modification to dictionary objects.

Is it possible to update Support Release packages from OS level?

No - you can import them but the full process will require additional steps the tools "tp" and "R3trans" are not aware of. The way is to use SPAM - but SPAM has the possibility to schedule those imports in the background.

After doing any Support Package update in SPAM, are there any further steps to carry out for this update to take effect?

No, they are active immediately.

SAP Administration Questions Answers

2007-07-10T14:45:00.000-07:00

What is the use of profile paramater ztta/roll_area?

The value specifies the size of the roll area in bytes. The roll area is one of several memory areas, which satisfies the user requests of user programs. For technical reasons, however, the first 250 KB or so of a user context are always stored in the roll area, further data

- up to the roll area limit ztta/roll_first,

- in the extended memory, up to the limit ztta/roll_extension or if extended memory is exhausted, then

- again in the roll area, until the roll area is full, then

- in the local process area, up to the limit abap/heap_area_dia or abap/heap_area_total or until the address space or the swap space is exhausted.

Followed by termination with errors like STORAGE_PARAMETERS_WRONG_SET an error code, that points to memory bottleneck Minimum data transfer with context change; however, the increase helps to avoid problems (address space, swap space, operating system paging).

What is R/3? and what is basis version?

SAP Basis:

- Provides the runtime environment for all SAP applications

- Optimally embeds the application in the system environment

- Defines a stable architecture framework for system enhancements

- Contains the tools for administering the entire system

- Allows the distribution of resources and system components

- Provides interfaces for decentralized system parts and external products.

An R/3 instance is a group of R/3 services that are started and stopped as a unit (by an R/3 dispatcher) and have a common instance profile. The name of an R/3 instance is composed of letters standing for the relevant services, and an instance number which is unique for each computer. The services may be D, V, E, B, M, G, or S, which respectively stand for dialogue, update, enqueue, background, message, gateway, and spool services.

I would like to know the version or name of SAP that is implemented in real time?

This is a very generic question and really depends on what you are implementing (modules).

The history of the "R/3" is

3.0D Basis 300

3.0E Basis 300

3.0F Basis 300

3.1H Basis 310

3.1I Basis 310

4.0B Basis 400

4.5B Basis 450

4.6C Basis 460

4.71 Basis 6.20

4.72 Basis 6.20

5.00 Basis 6.40 (ECC 5.0 - Enterprise Core components)

6.00 Basis 7.00 (ECC 6.0) - actually in RampUp

All of those have increased business functionality and interfaces to other systems (CRM, BW etc.)

What is mysap?

It's a term for all the systems that in a contract (e. g. a MySAP business suite consist of ERP2005, CRM2005, SRM2005).
What is the systems configuration required to implement SAP.. i.e for production, development and QAS servers the hard disk space, RAM, Processor
This also depends on what your are implementing, how many users will work on the system, how many records in what area are created etc.
We need a BIG database system and an even bigger application server for ~ 900 users and 12 languages.

What is ASAP?

It's an old term for an implementation strategy. Blueprint -> prototype -> goLive (if you want to say it in one sentence).

How should I set priority for Printing say like user, teamlead, project manager?

There's nothing like "priority" settings for spool processes. Just define more (profile parameter rdisp/wp_no_spool) processes so people don't need to wait.

Using Tc SGEN I have generated 74% job and later I have terminated the job. I wish to start generating from where it stopped I have refreshed but to no chance nothing was done. How should I further proceed so as to complete the remaining job..

Start SGEN again and select the same you have selected before. It will popup and ask if you want to start from scratch or generate the just the remaining.

Interview Questions for SAP Basis

2007-07-10T14:43:00.000-07:00

What is private mode? When does user switch to user mode?

Private mode is a mode where the heap data is getting exclusively allocated by the user and is no more shared across the system. This happens when your extended memory is exhausted.

What is osp$ mean? What if user is given with this authorisation?

OPS$ is the mechanism the adm users uses to connect to the database .

Why do you use DDIC user not SAP* for Support Packs and SPam?
Do _NOT_ use neither DDIC nor SAP* for applying support packages. Copy DDIC to a separate user and use that user to apply them.
Can you kill a Job?
Yes - SM37 - select - kill

If you have a long running Job, how do you analyse?
Use transaction SE30.

How to uncar car/sar files in a single shot?
on Unix:
$ for i in *.SAR; do SAPCAR -xvf $i; done

When we should use Transactional RFC ?
A "transactional RFC" means, that either both parties agree that the data was correctly transfered - or not. There is no "half data transfer".
What is the use of Trusted system. I know that there is no need of UID and PWD to communicate with partner system. In what situation it is good to go for Trusted system ?

E. g. if you have an R/3 system and a BW system and don't want to maintain passwords. Same goes for CRM and a lot of other systems/applications.

Let me know if my understanding below is correct:

1) By default the RFC destination is synchronous

2) Asynchronous RFC is used incase if the system initiated the RFC call no need to wait for the response before it proceeds to something else.
Yes - that's right.

But keep in mind, that it's not only a technical issue whether to switch to asynchronous. The application must also be able to handle that correctly.

Which table contains the details related to Q defined in SPAM? Is there a way to revert back the Q defined? If yes, How?

There is a "delete" button when you define the queue. If you already started the import it's no more possible since the system will become inconsistent.

What is a developer key? and how to generate a developer key?

The developer key is a combination of you installation number, your license key (that you get from http://service.sap.com/licensekey) and the user name. You need this for each person that will make changes (Dictionary or programs) in the system.
What is XI3.0 ? EXPLAIN XI = Exchange Infrastructure - Part of Netweaver 2004.
SAP Exchange Infrastructure (SAP XI) is SAP's enterprise application integration (EAI) software, a component of the NetWeaver product group used to facilitate the exchange of information among a company's internal software and systems and those of external parties. Like other NetWeaver components, SAP XI is compatible with software products of other
companies.

SAP calls XI an integration broker because it mediates between entities with varying requirements in terms of connectivity, format, and protocols. According to SAP, XI reduces integration costs by providing a common repository for interfaces. The central component of SAP XI is the SAP Integration Server, which facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.

How to see when were the optimizer stats last time run? We are using win2k, oracle 9, sapr346c.
Assumed DB=Oracle
Select any table lets take MARA here but you should do the same for MSEG and few others to see whether the dates match or not.Run the following command on the command prompt:-

select last_analyzed from dba_tables where table_name like '%MARA%';
This gives you a straight answer .Else you can always fish around in DB14 for seeing when the optimzer stats were updated.

SAP Basis FAQ

2007-07-10T14:29:00.000-07:00

Automatic CTS

Even though SAP does not recommend automatic imports, it is the most practical way of moving transports from a development system to a QA environment or to a special development system (although I wouldn't recommend auto imports to a production system for obvious reasons).

There are various methods for doing this. The most effective and simple method is using an OS script (shell/perl etc.) scheduled using cron for user sidadm. There are a couple of steps you need to take before setting up automatic imports.

1.Your entire project team should agree upon the overall strategy, frequency of imports etc.

2.Resolve any issues with transport approvals (many shops don't care about traffic between DEV and QA)

3. Who is responsible for watching for errors and corrective actions (an email to the developer works in this case)

Configuring outbound SAP to Internet mail Gateway (R/3 4.0 and above)

Step 1 (UNIX SETUP)

Logon to your as sidadm

Change directory to /sapmnt/SID/global (or any directory globally available across all application servers)

Create the following entries in file SAP_EMAIL_GATEWAY.sh and save the file

#!/bin/sh
GWCONFIG=/sapmnt/SID/global/SAP_EMAIL_GATEWAY.cfg
export GWCONFIG
/sapmnt/SID/exe/mlunxsnd $*

Execute the command: mlosmadm SAP_EMAIL_GATEWAY.cfg (enter the following information)

System name : SID
Client : 200
Username : MAILADM
Password : initpass
Language : E
Loadbalancing : Y
Message Server :
Group name : LOGON GROUP1
Using SAPROUTER : N
Trace Level (inBoound) : 0
Sendmail Command :
Codepage :
Trace Level (Outbound) : 0
Update file : Y

Step 2 (SAP SETUP)

Logon to SAPSYSTEM (SID) via SAPGUI

Transaction SU01, create user MAILADM and password initpass, usertype CPIC

Transaction SM59, Click Create

RFC Destination : SAP 4.5 INTERNET MAIL GATEWAY

Connection Type : T

Description : INTERNET EMAIL GATEWAY

Hit RETURN

Click EXPLICIT HOST

Enter /sapmnt/P21/global/ SAP_EMAIL_GATEWAY.sh

Save your entries

Transaction SCOT, click Edit--> CREATE NODES

Node : EMAIL

Description : SAP CONNECT NODE FOR EMAIL (continue)

RFC DESTINATION: (choose SAP 4.5 INTERNET MAIL GATEWAY from the pull down menu)

Choose radio button Internet

Address area : *DOMAIN (your intranet domain)

Ccontinue

Format : DOC, DAT, R3F, TXT, RAW,PPT,XLS (continue)

Continue

Set further address types : N

Minimum waiting : 5 minutes

Check both Node is in use', Node can resolve path references

Continue

Choose Goto--> Schedule Background Job

Enter name for the job & save

Configuring outbound SAP to Internet mail Gateway (Upto R/3 3.1I)

SAP can be configured to send and receive emails from different sources. This section explains how to integrate SAPOffice with an external email system.

This is in no way supplementing the online documentation available on the online documentation CD supplied by SAP but simplyfies the process to the bare Internet email must be configured and running prior to this. Email from SAP is forwarded to the users external email client such as Eudora, Outlook etc.

You can configure inbound and outbound forwarding. Outbound flow forwards a SAP message (eg:update termination) via UNIX sendmail to the intended recepient. Inbound accepts a message from sendmail and places it in the users SAPOffice inbox. Many SAP shops prefer to configure outbound only.

Configuring outbound forwarding

SAP configuration

1) Create your RFC destination for outbound email using transaction SM59
RFC Destination         :  SAP_INTERNET_GATEWAY

Connection Type         : T

Description             : SAP internet mail gateway

Click on 'Explicit Host' if you want on demand gateway dameon invocation.

Program                 : /sapmnt/SID/exe/mlunxsnd

Target Host             : Enter hostname that runs your central instance.

Click 'Test Connection' and you should see a successfull message.
2) Choose menu Tools-->Administration-->Management-->Process Technology-->Office-->Office Settings

3) Click Internet Gateway
Gateway Destination             : SAP_INTERNET_GATEWAY
Path for configuration file     : /sapmnt/SID/exe/sap_mailSID.cfg
Return Address                      : .com
4)Click Internet Settings and fill in the following fields

5)Save the settings

6)Click Back

7)Choose menu Office-->Addresses-->Communication Types

8)Type in INT over the Comm. type and Internet Mail over description.

9)Check Maintain and Send checkboxes and Save your entries.,

UNIX configuration
10) cd /sapmnt/SID/exe
11) mlosadm sap_mailSID.cfg


Client :  000
Username : MAILADM
Password  : MAILADM
Language : ESystem
name : SID
System number
Hostname
Gateway hostname
Gateway server sapgw
Sendmail Command
Update file : Y   

Testing

1)Logon to SAP

2)Execute transaction SO01

3)Write a message and send it to

If you don't see the mail in your internet mailbox, go back and review steps 1-12

Write a message and send it to

FTP from ABAP

There are 2 ways of executing FTP from an ABAP (online or batch mode),


	Initiated from the operating system. A script is available in the utility repository that explains how to do this very easily.
	Initiated from the ABAP itself An example is given below.

1) Create a logical OS command 'zftp' using transaction SM69. Make sure that you enable 'comand line parameter allowed' checkbox

2) Create a shell script called 'zftp' with the following lines

RMTHOST=`echo $2 | tr '[A-Z]' '[a-z]'`
ftp -v $RMTHOST <<> /out/zftp.$$ 2>&1
lcd /out
put $1
bye
EOF

3)Use the SXPG_COMMAND_EXECUTE function module to call this script (zftp) with the filename you want to transfer as the parameter.

Eg:

call function 'SXPG_COMMAND_EXECUTE'
exporting
commandname =
tables
exec_protocol =
exceptions
no_permission = 1
command_not_found = 2
parameters_too_long = 3
...

Enable web based online documentaion (R/3 4.0 or above)

1)Install Netscape webserver or use an existing web server (requires administrators privelege)

2)Create a directory called SAPDOCS4 under your web server document root.

3)Mount the CDROM containing online documentation on your PC or your UNIX server.

4)Recursively copy all files under /cdrom/docs/ to the SAPDOC4 directory under the web server root.

5)Create the following entries in your /usr/sap/SID/SYS/profile/DEFAULT.PFL

eu/iwb/installed_languages = EN

eu/iwb/help_type=2

eu/iwb/server_win32=webserver.domain.com

eu/iwb/path_win32=saphelp/helpdata

6)Restart your SAP system

How to access an external database from ABAP via DBLINK (ORACLE)

1)Using transaction SE11, create a table (ZTABLE) with the same fields as the table in the external database, make sure that the type and lengths of the fields are identical.

2)Using transaction SE11, create a view (ZTABLE_VIEW, projection view) using BASIS table ZTABLE

3)Using SVRMGRL>

create dblink REMOTE_DB as connect to remote_user identified by password; (database link created)

drop table ZTABLE; (table dropped)

create synonym ZTABLE for ZTABLE@REMOTE_DB; (synonym created)

4)Using transaction SE16 , type in ZTABLE_VIEW and hit RETURN

5)Enter value in key fields and hit execute. (displays rows from the remote table)

Tips and Tricks

1)To see the complete text of an error/warning message on the SAPGUI status bar, right click on the message and drag left.

2)To prevent your spool requests getting deleted from the BASIS cleanup jobs, you need to uncheck the Delete after print checkbox in the print control screen, execute transaction SP01, find your spool#, click on Attributes and change the Delete After date

3)Short cuts using the OK-code box.
%sc                       
 Search in page                     
%pc                       
 Download do local file              
p+                        
 Page up                     
p-                        
 Page down                     
p++                       
 Top of page                     
p--                       
 End of page                                 
4)Use transaction AL11 to browse the application servers directory structure

2007-07-10T14:22:00.000-07:00

2007-07-10T14:19:00.000-07:00

Changing the Title of SAP Transaction

Sometimes, internal user or customer might request you to change the Title of the SAP Transaction code to a more meaningful one and SAP allows this to be done painlessly.

The steps to change the Title of any SAP transaction code are as follows:

First, goto tcode SE63

On the top left Menu of the screen - Click Translation - Short texts - Transactions

For example, assuming you want to change the title of the tcode FB01 from Post Document to Post Document for G/L. On the first screen, fill in the following information:

Transaction code - FB01

Source Language - English
Target Languate - English

To change the Title, click the Edit button

On the second line, type in the Title (For e.g. Post Document for G/L) you want for the transaction code

Click the Save button

Now, called up the transaction code /nFB01 again and you should be able to view the new Title.

Please note that it works for most of the Transaction code except for those new Enjoy transaction code in 4.6x.

2007-07-10T14:14:00.000-07:00

Useful SAP System Administration Transactions

AL01 SAP Alert Monitor
AL02 Database alert monitor
AL03 Operating system alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL06 Performance: Upload/Download
AL07 EarlyWatch Report
AL08 Users Logged On
AL09 Data for database expertise
AL10 Download to Early Watch
AL11 Display SAP Directories
AL12 Display table buffer (Exp. session)
AL13 Display Shared Memory (Expert mode)
AL15 Customize SAPOSCOL destination
AL16 Local Alert Monitor for Operat.Syst.
AL17 Remote Alert Monitor for Operat. Syst.
AL18 Local File System Monitor
AL19 Remote File System Monitor
AL20 EarlyWatch Data Collector List
AL21 ABAP Program analysis
AL22 Dependent objects display
CREF Cross-reference
BD64
BSVW Linkage Status Update-Workflow Event
CMOD Enhancements
DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes
DB03 Parameter changes in database
DB11 Early Watch Profile Maintenance
DB12 Overview of Backup Logs
DB13 Database administration calendar
DB14 Show SAPDBA Action Logs
DB15 Data Archiving: Database Tables
DB16 DB System Check: Monitor
DB17 DB System Check: Configuration
DMIG Start Transaction for Data Migration
DB2 Select Database Activities
DB20 DB Cost-Based Optimizer: Tab. Stats
DB21 DB Cost-Based Optimizer: Config.
DB24 Database Operations Monitor
DB26 DB Profile:Monitor and Configuration
DB2J Manage JCL jobs for OS/390
DBCO Database Connection Maintenance
FILE Cross-Client File Names/Paths
NACE WFMC: Initial Customizing Screen
OAA1 SAP ArchiveLink: Maint.user st.syst
OAA3 SAP ArchiveLink protocols
OAA4 SAP ArchiveLink applic.maintenance
OAAD ArchiveLink Administration Documents
OAC2 SAP ArchiveLink: Globaldoc. types
OAC5 SAP ArchiveLink: Bar code entry
OACA SAP ArchiveLink workflow parameters
OAD0 SAP ArchiveLink: Objectlinks
OAD2 SAP ArchiveLink document classes
OAD3 SAP ArchiveLink: Link tables
OAD4 SAP ArchiveLink: Bar code types
OAD5 SAP ArchiveLink: Customizing Wizard
OADR SAP ArchiveLink: Print list search
OAM1 SAP ArchiveLink: Monitoring
OAOR SAP ArchiveLink: Storeddocuments
OARE SAP ArchiveLink:St.syst.return codes
OS01 LAN check with ping
OS03 O/S Parameter changes
OS04 Local System Configuration
OS05 Remote System Cconfiguration
OS06 Local Operating System Activity
OS07 Remote Operating SystemActivity
OSS1 Logon to Online ServiceSystem
OY18 Table history
OY08 Development Class Overview
PFCG Activity Group
PFUD Authorization Profile comparison
RLOG Data migration logging
RZ01 Job Scheduling Monitor
RZ02 Network Graphics for SAP Instances
RZ03 Presentation, Control SAP Instances
RZ04 Maintain SAP Instances
RZ06 Alerts Thresholds Maintenance
RZ08 SAP Alert Monitor
RZ10 Maintenance of profile parameters
RZ11 Profile parameter maintenance
RZ12 Maintain RFC Server Group Assignment
RZ20 CCMS Monitoring
RZ21 Customize CCMS Alert Monitor
SA38 ABAP/4 Reporting
SAD0 Address Management call
SADC Address: Maint. communication types
SALE Display ALE Customizing
SAINT Plug-in Installation
SARI Archive Information System
SAR3 Customizing Archiving
SAR4 Define Archiving Class
SAR5 Assign Archiving Class
SAR6 Archiving Time Generator
SARA Archive management
SARL Call of ArchiveLink Monitor
SARP Reporting (Tree Structure): Execute
SART Display Reporting Tree
SB01 Business Navigator - Component View
SB02 Business Navigator - Process flow vw
SBAS Assignments to Process Model Elemts
SC38 Start Report Immediately
SCAT Computer Aided Test Tool
SCC0 Client Copy
SCC1 Client Copy - Special Selections
SCC2 Client transport
SCC3 Client Copy Log
SCC4 Client administration
SCC5 Client Delete
SCC6 Client Import
SCC7 Client Import – Post Processing
SCC8 Client Export
SCC9 Remote Client Copy
SCCL Local Client Copy
SCDO Display Change DocumentObjects
SCMP View / Table Comparison
SCOM SAPcomm: Configuration
SCON SAPconnect - Administration
SCPF Generate enterprise IMG
SCPR1 Customizing Profiles : Maintenance Tool
SCPR2 Comparing Customizing profiles
SCUA Central User Administration : Distribution Model Assigment
SCUG Central User Administration Structure Display
SCUL
SCUM Central User Administration Field Selection
SCU0 Table Analyses And Comparison
SCU1 Table Comparison - Export to Tape
SCU2 Table Comparison Against Tape
SCU3 Table History
SD11 Data Modeler
SDBE Explain an SQL Statement
SECR Audit Information System
SE01 Transport and Correction System
SE02 Environment Analyzer
SE03 Transport Utilities
SE06 Set up Workbench Organizer
SE07 Transport System Status Display
SE09 Workbench Organizer (Initial Screen)
SE10 Customizing Organizer
SE11 Data Dictionary Maintenance
SE12 Data Dictionary Display
SE13 Maintain Technical Settings (Tables)
SE14 Convert Data Dictionary tables on Database Level
SE15 Repository Info System
SE16 Display Table Content
SE17 Generate Table Display
SE30 ABAP Objects Runtime Analysis
SE32 ABAP Text Element Maintenance
SE33 Context Builder
SE35 ABAP/4 Dialog Modules
SE36 Logical databases
SE37 ABAP Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE40 MP: Standards Maint. and Translation
SE41 Menu Painter
SE43 Maintain Area Menu
SE51 Screen Painter
SE52 Parameterized screenpainter call
SE54 Generate table view
SE55 Internal table view maintenance call
SE56 internal call: display table view
SE57 internal delete table view call
SE61 R/3 Documentation
SE62 Industry Utilities
SE63 Translation: Initial Screen
SE71 SAPscript form
SE72 SAPscript Styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript: Form Translation
SE77 SAPscript Translation Styles
SE78 SAPscript: Graphics administration
SE80 Object Navigator
SE81 Application Hierarchy
SE82 Application Hierarchy
SE84 R/3 Repository Information System
SE85 ABAP/4 Repository Information System
SE86 ABAP Repository Information System
SE88 Development Coordination Info System
SE89 Maintain Trees in Information System
SE91 Maintain Messages
SE92 New SysLog Msg Maintenance as of 46A
SE93 Maintain Transaction Codes
SE94 Customer enhancement simulation
SE95 Modification Browser
SEPS SAP Electronic Parcel Service
SERP Reporting: Change Tree Structure
SEU Repository Browser
SF01 Client-Specific File Names
SFAW Field Selection Maintenance
SIAC1 Web Object Administration
SHDB Record Batch Input
SICK Installation Check
SIN1 SAPBPT: Inbox
SINA SAPBPT: Maintain Standard Config.
SLG0 Application Log: ObjectMaintenance
SLIN ABAP: Extended Program Check
SM01 Lock Transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM14 Update Program Administration
SM21 System log
SM23 System Log Analysis
SM28 Installation Check
SM29 Model Transfer for Tables
SM30 Call Up View Maintenance
SM31 Table maintenance
SM31_OLD Old Table Maintenance
SM32 Maintain Table Parameter ID TAB
SM33 Display Table ParameterID TAB
SM34 Viewcluster maintenancecall
SM35 Batch Input Monitoring
SM36 Batch request
SM37 Background job overview
SM38 Queue Maintenance Transaction
SM39 Job analysis
SM49 Execute Logical Commands
SM50 Work Process Overview
SM51 List of SAP Servers
SM54 TXCOM maintenance
SM55 THOST maintenance
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM60 Borrow/Return Objects
SM61
SM62
SM63 Display/Maintain Operating Mode Sets
SM64 Release of an event
SM65 Background Processing Analysis Tool
SM66 System-wide Work Process Overview
SM67 Job scheduling
SM68 Job administration
SM69 Display/Maintain Logical Commands
SMEN Dynamic menu
SMGW Gateway Monitor
SMLG Maintain Logon Group
SMLI Language import utility
SMLT Language transport utility
SMOD SAP Enhancement Management
SMT1 Trusted Systems (Display <-> Maint.)
SMT2 Trusting systems (Display <->Maint.)
SMW0 SAP Web Repository
SMX Display Own Jobs
SNRO Number Range Objects
SO02 SAPoffice: Outbox
SO03 SAPoffice: Private Folders
SO04 SAPoffice: Shared Folders
SO05 SAPoffice: Private Trash
SO06 SAPoffice: Substitutionon/off
SO07 SAPoffice: Resubmission
SO10 SAPscript: Standard Texts
SO12 SAPoffice: User Master
SO13 SAPoffice: Substitute
SO15 SAPoffice: DistributionLists
SO16 SAPoffice: Profile
SO17 SAPoffice: Delete Shared Trash
SO18 SAPoffice: Shared Trash
SO19 SAPoffice: Default Documents
SO21 Maintain PC Work Directory
SO22 SAPoffice: Delete PC Temp. Files
SO23 SAPoffice: DistributionLists
SO24 SAPoffice: Maintenance of default PC
SO28 Maintain SOGR
SO30 SAPoffice: Reorg.
SO31 Reorganization (daily)
SO36 Create Automatic Forwarding
SO38 SAPoffice: Synchr. of Folder Auths.
SO40 SAPoffice: Cust. LayoutSet MAIL
SO41 SAPoffice: Cust. LayoutSet TELEFAX
SO42 SAPoffice: Cust.Layout Set TELEFAX_K
SO43 SAPoffice: Cust.Layout Set TELEFAX_M
SO44 SAPoffice: Cust. LayoutSet TELEX
SO70 Hypertext: Display/Maint. Structure
SO71 Test plan management
SO72 Maintain Hypertext Module
SO73 Import graphic into SAPfind
SO80 SAPfind: Free Text Retrieval Dialog
SO81 SAPfind: Free Text Indexing (Test)
SO82 SAPfind: Free Text Retrieval Batch
SO95 Pregenerated Search Queries - Selec.
SO99 Put Information System
SOA0 ArchiveLink Workflow document types
SOBJ Attribute Maintenance Objects
SOLE OLE Applications
SOLI Load OLE type info
SOPE Exclude Document Classes
SOTD SAPoffice: Maintain Object Types
SOY1 SAPoffice: Mass Maint. Users
SOY2 SAPoffice: Statistics data collect.
SOY3 SAPoffice: Statistics Evaluation
SOY4 SAPoffice: Access overview
SOY5 SAPoffice: Inbox overview
SOY6 SAPoffice: Document overview
SOY7 SAPoffice: Folder overview
SOY8 SAPoffice: Mass Archiving
SOY9 SAPoffice: Inbox Reorg.
SOYA SAPoffice: Change folder owner
SP00 Spool and Relate Area
SP01 Spool Control
SP02 Display output Requests
SP03 Spool: Load Formats
SP11 TemSe Contents
SP12 TemSe Administration
SPAD Spool Management
SPAM SAP Patch Manager (SPAM)
SPAU Display Modified DE Objects
SPCC Spool Consistency check
SPDD Display Modified DDIC objects
SPHA Telephony administration
SPIC Spool : Installation Check
SPRM Current Customizing
SPRO Customizing
SQ01 SAP Query: Maintain queries
SQ02 SAP Query: Maintain funct. areas
SQ03 SAP Query: Maintain user groups
SQ07 SAP Query: Language comparison
SQVI QuickViewer
SSAA System Administration Assistant
SSCA Appointment Diary: Administration
SRZL CCMS
SSM1 Session Manager generation call
SSM5 Create Activity Group
ST01 System Trace
ST02 Setups/Tune Buffers
ST03 Performance, SAP Statistics, Workload
ST04 Select activity of the databases
ST05 SQL Trace
ST06 Operating System Monitor
ST07 Application monitor
ST08 Network Monitor
ST09 Network Alert Monitor
ST10 Table Call Statistics
ST11 Display Developer Traces
ST12 Application Monitor
ST14 Application Analysis
ST22 ABAP Runtime Error Analysis
ST22 ABAP/4 Runtime Error Analysis
ST62 Create industry short texts
STAT Local transaction statistics
STMS Transport Management System
STUN Performance Monitoring
STW1 Test Workbench: Test catalog
STW2 Test workbench: Test plan
STW3 Test workbench: Test package
STW4 Test Workbench: Edit test package
STW5 C maintenance table TTPLA
STZAC Maintain time zone act.in client
STZAD Disp .time zone activat.in client
SUMM Global User Manager
SU01 Maintain User
SU01D Display users
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet Users
SU10 Mass changes to User Master
SU11 Maintain Authorizations
SU12 Mass Changes to User Master Records
SU2 Maintain User Parameter
SU20 Maintain Authorization Fields
SU21 Maintain Authorization Objects
SU22 Auth. object usage in transactions
SU24 Disables Authorization Checks
SU25 Imports SAP Check Indicators defaults
SU26 Adjust Authorization checks
SU30 Total checks in the area of auth.
SU52 Maintain own user parameters
SU53 Display check values
SU54 List for Session Manager
SU56 Analyze User Buffer
SUPC Profiles for activity groups
SUPF Integrated User Maintenance
SUPO Maintain Organization Levels
SUIM Repository Info System
SWDC Workflow Definition
SXDA Data Transfer Workbench
TU02 Display Active Parameters
USMM Customer measurement

SAP BASIS

2007-06-19T11:28:00.000-07:00

1.0 Introduction
SAP has done nothing less than change the entire systems landscape for enterprises. The benefits it can bring have led to widespread adoption across the globe. One of the key benefits SAP brings to an enterprise is the ability to integrate the data both within the enterprise, and between it and it’s partners / competitors. In many cases organizations today are both partners and competitors at the same time. Think of wholesalers and distributors, SAP and Oracle, AT&T and BT, or two oil giants who have an upstream joint venture. These companies use SAP to integrate process between themselves for their mutual benefit. This ability to integrate, however, brings with it a particular risk – that of exposing their data to the un-authorized outside world.

Entire companies have been built up around highly guarded intellectual property and process secrets ... and could easily fall if this was breached. Therefore, keeping the security of the organization intact is one of the vital aspects of any SAP implementation.

SAP BASIS addresses all security issues by incorporating an authorization module. With increased potential for security breaches in the computer systems around the world, BASIS consultants face a tough task of maintaining the integrity and administering the security of SAP systems. Interoperability features of a SAP system makes this task a bit more difficult.

2.0 SAP Security Components – The Big Picture

SAP security in an integrated environment can be viewed in the form of discrete components as shown below (figure 1).

Tight security is required for each of the above components (Network, Workstation, Operating System and Database) as a breach made in one area can compromise the entire system.
The scope of this article is SAP Application Security, which can be achieved with the help of SAP’s BASIS security application through the concept of authorization.

In SAP, security is administered for objects (profiles and authorizations). Users are only authorized to see or change the parts of the system required by their respective job responsibilities.

2.1 SAP Authorization Concept
The SAP authorization concept is based upon the logical relationship between a user ID and the range of system authorizations with which it can be associated. The architecture of the authorization system is based upon the utilization of several individuals but related logical components: Profiles, Objects, Fields, and Authorizations. The user ID refers exclusively to profiles. Each profile grants a set of specific system access authorizations to user. Figure 2 illustrates the hierarchical authorization concept in SAP.

2.2 Composite Profiles
Composite profiles refer to the various employee roles available in the corporation (for instance: Purchasing / Receiving Clerk or Accounts Agent). As the name suggests, composite profiles may contain multiple user IDs necessary to perform all the business operations associated with a particular role. A composite profile may encapsulate another composite profile(s). In practice, a model composite profile should be recognized for each possible role in the organization, which may be used to produce hybrid composite profiles. The over-existence of the hybrids can defy the very purpose of composite profiles and they should be created only when specific needs arise.

2.3 User Ids
User ids allow access to SAP applications. Each user must have a corresponding profile specifically assigned. In many situations, multiple composite profiles can be assigned to a user ID, depending on the role(s) an individual user is responsible for, in the business processes.

2.4 Authorizations
Authorizations are the key building blocks of SAP security. Authorization is the process of assigning values to fields present in authorization objects. In SAP, access to all system functionality is achieved through a complex array of authorizations. Sometimes users find that they lack the necessary authorizations to perform a certain function in the system, in which case the message: "You are not authorized..." is displayed at the bottom of the screen.

An authorization process may ask for second associated authorization process which in turn asks for third and so on. For example, the task of paying a vendor invoice may require 10 different authorizations.

3.0 Security Configuration in SAP
Security configuration and administration in SAP is a multi-phase process. Four key security components are required to ensure the adequate security, privacy, and integrity of information. The phases are as follows:

3.1 User Authentication
The first phase comprises confirmation of user identity and results in authentication of user. Unauthorized access to SAP system is prevented through this initial check. This ensures system integrity by regulating secure access through genuine user authentication.

3.2 Creating and Assigning Authorization Profiles
A Profile Generator (PG) is used to automatically generate and assign authorization profiles. This tool was released with SAP version 3.1g and above. The administrator can also create authorization profiles manually.

Note: Profile Generator can be retroactively installed in SAP versions 3.0f and above.
The authorization objects can be selected using the SAP Profile Generator. Administrators can automatically generate authorization profiles for function-specific access to SAP users after configuring initial settings.

The entire authorization functionality of SAP signifies a new approach to authorization. The administrator can define user authorization based on SAP functions. Based on the selected function, the PG groups objects in administrator-created authorization profiles.

Authorization profiles created by a Profile Generator are based on the given authorizations. It also speeds up the process and simplifies administrator/user communication facilitating both the administrator and users to use the same SAP function terminology. To auto-generate an Authorization profile, an Activity Group needs to be created.

Activity Groups contain simple profiles and usually represent employee or job roles. They are user-defined and allow administrator to organize and maintain system activities. Activity group when used as an information database reduces data entry time. Administrators can define activity groups in two steps:

1.Selecting the criteria, such as access controls.
2.Dividing the activities into appropriate groups.

For example, activities can be organized by functions, such as human resources, payroll, or administration or by job classes, such as computer programming activities, or accounting activities. A combination of function-specific activity and job-specific activity can also be implemented.

Security implementation with the new Profile Generator is based on the creation of activity groups or a collection of linked or associated activities, such as tasks, reports, and transactions.

Consider a business situation involving a company, ABC Inc. faced with transaction security hiccups in business dealings with its dealers. To address this problem, the company can create authorization profiles for its dealers using the profile generator features. This can be done by implementing the following instruction set:

Instruction 1: A dealer activity group should be created. Name this activity group as Dealer.
Instruction 2: All dealer-specific business transactions should be included in the activity group.
Instruction 3: Generate an authorization profile for Dealers.
Instruction 4: Assign Dealer to a "new user" or in your system and update master records.

3.3 Auditing and Monitoring
In this subsequent phase, a track of the authorizations created (previous phase) is kept. Detailed accounts of system events are used to record the actions of a user corresponding to that unique user account identifier. Auditing/Monitoring activities should be in compliance with enterprise’s overall IT strategy and should be performed on a weekly, monthly, quarterly, and yearly basis.

There are some key tasks that should be included in a monitoring plan. The following reviews should be a part of an ideal monitoring plans.

Using System Logs and Security Audit Logs
The system log records critical information important events. Each individual application server maintains local log files to which the information is written periodically. The security audit log records areas such as successful and unsuccessful dialog log-on attempts, RFC log-on attempts, changes to user master records, and transaction starts.

Reviewing User Activity

All SAP system users must be continuously monitored so that their problems can be rectified as soon as they occur. The timely attention to user problems can reduce administration overheads.

For example, if a SAP administrator wants to check for unrecognizable user Ids or the users trying to use non-permitted transactions, administrator can execute transaction AL08 and review user activity.

Monitoring User access in BASIS User Group
The BASIS users in a SAP system have access to sensitive areas of an organization. Therefore it is vital to monitor their access. Following instructions can be performed to check the access of BASIS User group.

Instruction Set
Enter transaction SUIM to view Repository Information of the system.
Follow the Menu Path:
User > Lists of users (according to selection criteria) > user IDS (Double Click).

Monitoring Change Requests

All change requests need to be properly reviewed and controlled prior to being applied. This formal process needs to be detailed enough to ensure that separation of duties and other control features are not breached. Strong integration knowledge of the SAP system is required for this review. Critical profiles, authorizations, and transactions need to be identified and treated even more carefully.

Checking Important Default SAP Profiles
Administrators must check that default profiles act a template for user defined profiles and are not directly used in production. Default profiles contain values, which apply to all application servers. These include: SAP_ALL, SAP_NEW, S_A.ADMIN, S_A.CUSTOMIZ, S_A.DEVELOP, S_A.DOKU, S_A.SYSTEM, S_A.USER, S_ENT_IMG_GE, S_WF_ALL, and P_ALL.

Changing Default SAP User ID’s
SAP comes with some pre-configure clients (independent business units). They are client 000, 001 and 066 in the non-IDES system. In the IDES system, client 800 is the default client. SAP installation process automatically creates default user Ids and their corresponding passwords. SAP administrators must ensure that they are not used to access the system. The following table explains default user Ids in various SAP clients.

Instruction Set
Change all default passwords and verifying the password change by logging into various client areas.
Assign SAP* to the Super user group.
Enter transaction SE16.
Enter SAP* into the field called BNAME.
Click "Execute" and verify.

As a final step, check that the secret super user has been created (with a different user ID and password). All of the authorizations assigned to SAP* should then be removed (an empty profile list followed by a password change

Auditing Information System (AIS)
SAP Audit Information System (AIS) serves as a centralized repository for reports, queries, and views of interest to auditors. It is designed to address the overall system configuration as well as SAP business processes and their related control features, providing audit and security practitioners with the critical information they need to conduct effective reviews of their SAP systems. SAP administrators can use AIS for security auditing. The AIS plays a supportive role in providing security services for SAP systems. The primary function of AIS is auditing but auditing features can derive the measures that help in developing the security policy for SAP systems.

3.4 Administration and Maintenance
A successful security set up of a SAP system concludes with proper management and administration of user IDs, password resetting, audit trails, audit logs, access control list, and personnel responsibilities.
Security administration in SAP includes maintenance of the overall SAP security environment using the SAP Profile Generator, creating user-level activity groups and creating user master records.
The concept of SAP security is flexible as well as complex. SAP has a multi-layered integrated framework. To ensure adequate protection, security measures must be factored into all layers of the SAP infrastructure. With client/server architecture, SAP systems include many components that exchange information, each of which constitutes a layer of the SAP security infrastructure. Security is often not a priority in an implementation and as a result, the default security is not strong. SAP security functionality could be enhanced using various measures as discussed above.
Enterprises must develop a security strategy to ensure a secure and functional SAP system. A business critical application like SAP needs continuous monitoring and improvement of its security features.

%sc	Search in page
%pc	Download do local file
p+	Page up
p-	Page down
p++	Top of page
p--	End of page