Page is moved to below link.
0049 - Security - All SAP - Check SAP* and DDIC Passwords
Ever forget if you changed the SAP* user password to something other than the 06071992 default? Or wonder if the password is the same in all your clients?
SAP provides a program called RSUSR003 that gives a good report on the status of your SAP*, DDIC, SAPCPIC, and EARLYWATCH user IDs across all clients of a SAP instance as well as information on these login instance parameters:
- login/accept_sso2_ticket
login/certificate_request_ca_url
login/certificate_request_subject
login/create_sso2_ticket
login/disable_cpic
login/disable_multi_gui_login
login/disable_multi_rfc_login
login/disable_password_logon
login/failed_user_auto_unlock
login/fails_to_session_end
login/fails_to_user_lock
login/min_password_diff
login/min_password_digits
login/min_password_letters
login/min_password_lng
login/min_password_specials
login/no_automatic_user_sapstar
login/password_change_for_SSO
login/password_expiration_time
login/password_logon_usergroup
login/password_max_new_valid
login/password_max_reset_valid
login/system_client
login/ticket_expiration_time
login/ticket_only_by_https
login/ticket_only_to_host
login/ticketcache_entries_max
login/ticketcache_off
login/update_logon_timestamp
0081 - General - All SAP - Replace SAP Splash Logo
If you want to replace the default SAP splash screen, do the following:
1. Identify a picture to replace the existing SAP logo. This picture can be in any valid picture format - gif, bmp, jpg. But I would convert it to jpg since that is the smallest available picture type. Store the picture somewhere on your workstation.
2. Go to transaction SMW0.
3. On the SAP Web Repository: Initial Screen, click "on" the radio button for Binary data for WebRFC applications, and click the Find icon or press F8.
3. On the SAP Web Repository: Objection selection screen, click the Execute icon or press F8.
4. On the SAP Web Repository: Object display screen, first make sure that the mime extension exists for your picture type. Click Settings -> Maintain MIME types. Look to the far right of the Data Browser: Table MIMETYPES Select Entries screen, and if you don't see your file type - gif, jpg, bmp - then you need to add it. Once you at done, back out to SAP Web Repository: Object display screen.
5. Now you can upload your picture. Click the Create icon or press F5. Fill in the name of your picture and a brief description and click the Import icon. Then provide the location of your picture and load it in.
6. Go to transaction SM30. Fill in the table name SSM_CUST and click Maintain.
7. On the Change View "Set Values for the Session Manager / Profile Generator" screen, click New Entries and add an entry called START_IMAGE and set the value to the name of your picture created in step #5. Then press the Save icon.
You have replaced the SAP splash screen picture. Log off and back on to view your work!
0083 - UNIX - All SAP - UNIX Kernel Patch
UNIX Kernel Replacement
- 1. Download the two necessary archives - SAPEXE.SAR and SAPEXEDB.SAR - from SAP MarketPlace. There files can be found at http://service.sap.com/patches. Be careful that your Basis level is high enough to use the patch level of the files you download. For example, if your SAP instance is on Basis level 39 and the description of one of the SAPEXE.SAR files is Stack 42, you need to download a SAPEXE.SAR of a lower level.
2. Once both files have been downloaded, log on to the UNIX server as <sid>adm and copy them up to a directory on the UNIX server - I use one called /usr/sap/trans/NewKernel. unCAR the files with SAPCAR command "sapcar -xvf "SAPEXE*.SAR".
3. As <sid>adm, stop the SAP instance. Log on as ora<sid> and stop the TNS listener, and log on as root and stop saposcol.
4. Make a backup of your run directory before patching. I usually create a /usr/sap/<SID>/SYS/exe/backup_run and copy all the files in /usr/sap/<SID>/SYS/exe/run to it.
5. Copy all the files unCARed in step 2 to /usr/sap/<SID>/SYS/exe/run. If prompted, overwrite all.
6. Change the owner of saposcol to root, sapdba & all br* files to ora<sid>, and all the rest to <sid>adm.
7. Start saposcol, the TNS listeners, and the SAP instance.
You have patched your UNIX SAP kernel. If you run into any problems starting your SAP instances, stop everything, rename the directories /usr/sap/<SID>/SYS/exe/run to /usr/sap/<SID>/SYS/exe/bad_run and /usr/sap/<SID>/SYS/exe/backup_run to /usr/sap/<SID>/SYS/exe/run to restore your old kernel.
0087 - Basis - All SAP - Auto Start your Windows Instance
This one is easy but sometime hard to find. And it only works for Windows.
Use transaction RZ10 to edit your startup profile. Add the following entry:
Then save the profile. Next time your server reboots, your SAP instance will come up automatically!
0105 - General - All SAP - Use CTRL+Y to Copy SAP Screen Text
This TKR is dedicated to Brosser, who helped me see the light...
I confess... I feel like one of Richie's Tuly Idiots for not knowing this one. I knew about CTRL+C, CTRL+V, and CTRL+X but somehow I never used CTRL+Y back in the old DOS days so this command meant nothing to me. Maybe it is because CTRL+Y is used for Redo and CTRL+Z for Undo in so many programs like Notepad, Word, etc.
Now that I am a convert, it is time to spread the word! It all started when I posted a blurb in the What's Messed Up in SAP forums about wishing you could use CTRL+C in st22 so you could copy the OSS Note search terms and not have to type them out by hand. And someone asked why I didn't use CTRL+Y.
CTRL+Y works similarly to Edit -> Mark from a DOS prompt only you can to a CTRL+C afterwards. The data you mark for copying does not have to be just a line or two, you can copy any part of a text screen. And what you copy keeps the spacing, etc. that is shown on the original screen.
So, I have done my good deed of the day. Enjoy!
0110 - Transport - All SAP - Add an Object to a Transport
So, you just finished a project and everything is contained in one big transport. Before releasing it to be transported to QAS, you look through the object lists just to make sure you got everything. And, low and behold, you see that you are missing program ZPROGRAM. What do you do? You want everything to be contained in one transport but there is no transport for ZPROGRAM!
As long as the main transport has not been released, you can add the ZPROGRAM to it. If it has been released, you need to use se03 to create a new main transport. If you don't know how to do this, please see 0074 - TMS - All SAP - Recover Local Transport Request in this Technical Knowledge Repository before reading the rest of this TKR posting.
To add an object to a existing unreleased transport, you must do the following:
- 1. Log on to the client in which the main transport was created.
2. Go to transaction se10 and pull up a list containing the main transport.
3. High-light the main transport in the list - not the subtasks contained in the list - and click Ctrl+F11.
4. Turn "on" the radio button "Freely selected objects" that appears in the popup and press Enter
or click the Copy button.
5. In the "Include objects in request" screen, turn "on" the "Selected Objects in the Selection by
type and name" section.
6. Check "on" the check box on the appropriate line, and enter the name of the object to be
added to the transport - ZPROGRAM in our case. Click the Execute button or press F8.
7. On the "Include objects in request" screen, click the "Include Request" button or press F9. You will
see a confirmation message in the status bar at the bottom of the screen.
Now you can release your transport and let it move to QAS!
How to set-up and open a REMOTE SERVICE CONNECTION WITH SAP
As most of you probably know, SAP has changed the way you open your system for SAP to access it remotely. Here is the new way it is done written by Mirella Jolicoeur from Natrol. She learned this method the hard way late one night.
1. Set-up a remote network connection to SAP.
2. Install SAP router on a Windows machine.
3. Install SAPCRYPTOLIB on the same machine.
4. Check the saprouttab file : a) you should have only one in your system and b) it should look like this:
Code:
P 10.1.1.* 194.117.106.129 *
P 10.1.1.* 194.117.106.130 *
P 194.117.106.129 10.1.1.61 3200
5. Test you connection to SAP by DOS cd: ping sapserv1.
6. Go to http://service.sap.com/system-data.
7. Go to the Problem Solving tab.
8. Go to the Connecting to SAP tab.
9. Click on Maintain Connections
10. Click on “Display all systems”
11. Double click on your system ID
12. The Service Connection-System ID page opens.
13. Click on Systemdata – next to Logbook
14. Under System tab, scroll down to SAP-router, and look for an edit icon to the right. Click on the edit icon, and enter the saprouter’s NETBIOS name, and under Service-port enter 3299.
15. Under DB server tab click on the change icon and enter the NETBIOS name of the server, along with the local IP address. Unless you have two saprouters, do not enter anything under Additional SAP-Router field.
16. Under Appl.Server tab do the same thing. If you have a system that has the db server and the application server running on it, then the IP address will be the same.
17. On a workstation (Windows XP) that has the SAP GUI, install Service Connector from SAP’s site.
18. Install on the same machine LOP (Line Opener program).
19. To set-up the maximum time for SAP connection, click on Semi-Automatic Opening and enter the number of days for connecting to SAP
When you are done installing them, run first SAPServiceConnector, and the LOP.
After less than a minute, you can check on the SAP website if the connection is open.
0112 - Basis - R/3 6.20+ - SAPConnect SMTP Setup
Sending email out of SAP using SMTP
1. First, make sure your SAP Server has the SMTP service installed and that the service is active.
2. Activate the SMTP service using SICF.
3. Using the SCOT transaction, click View -> System Status.
a.Click Settings -> Default Domain. Enter your email domain WITHOUT the @ sign. For example. The domain for SAP Super Users would be sapsuperusers.com. Save the information and go back to the main SCOT page.
b.Double-click on the SMTP node under INT. Change the Mail Host and Mail Port information, and turn Node in Use “on”. Click the Set button beside Internet in the Support address types section. Put an * in the firstline of Address area. Confirm your way back to the main screen.
c.Back on the main SCOT screen, click View -> Jobs. Click the create button and fill in a name for the email send job then click on the green check mark. Highlight the variant you want to use – I use SAP&CONNECTALL – then click the Schedule button. Fill in the start date and time, and then click Schedule periodically. Fill in the correct periodic information and click Create. Your job has been added.
Receiving email into SAP using SMTP
1. Complete the tasks in “Sending email out of SAP using SMTP”.2. Using transaction RZ10, add these parameters to your instance profile:
icm/server_port_<*> = PROT=SMTP,PORT=<port>
is/SMTP/virt_host_<*> = <host>:<port>,<port>,...;
The second parameter is only necessary if you are going to have multiple clients in the same SAP system receiving email. Here is an example of how these parameters can be configured:
rdisp/start_icman = true
icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180 icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180 is/SMTP/virt_host_0 = *:25000;
is/SMTP/virt_host_1 = *:25001;
If multiple clients in your SAP system need to receive External email, your must create a unique is/SMTP/virt_host_<*> parameter for each client.
3. Using transaction SU01, create a SAPEmail system user with the S_A.SCON profile. And make sure all the users who will be receiving email have a valid email address in their SU01 profile.
4. Using transaction SICF, each client to receive email must be assigned an SMTP server. There is one already provided as a template. If only one client will be receiving email you only need to use the template. Make these changes:
a.Change the Host Data to contain the proper Profile Parameter Number. See step 2.
b.Change the Logon Data to contain the information about the user created in step 3.
c.Change the Handler List to SMTP_EXT_SAPCONNECT on line 1.
5. Save your changes, deactivate the SAPconnect service andthen re-activate it.
0113 - Basis - All SAP - Technical Table Characteristics
Data class
The data class defines the physical area of the database (for ORACLE the TABLESPACE) in which your table is logically stored. If you choose a data class correctly, your table will automatically be assigned to the correct area when it is created on the database.
The most important data classes are (other than the system data):
APPL0 Master data
APPL1 Transaction data
APPL2 Organisational and customizing data
Master data is data which is frequently read, but rarely updated. Transaction data is data which is frequently updated. Organizational and customizing data is data which is defined when the system is initialized and then rarely changed.
There are two more data classes available, USR and USR1. These are reserved for user developments. The tables assigned to these data classes are stored in a tablespace for user developments.
Note:The data class only has an effect on table storage for the database systems ORACLE and INFORMIX.
Size category
The size category determines the probable space requirement for a table in the database.
You can select the categories 0 to 4 for your table. Each category is assigned a specific fixed storage area value in the database. When you create a table, initial space is saved for it in the database. If more space is required later as a result of data that has been entered, the storage space is increased in accordance with the category selected.
Press F4 on the field Size category to see the number of data records that can be maintained for the individual categories of your table without complications ensuing. These complications could be for example a reorganization becoming necessary because the maximum space to be reserved for the table was exceeded due to the maintained size category.
Buffering status
The buffering status specifies whether or not a table may be buffered.
This depends on how the table is used, for example on the expected volume of data in the table or on the type of access to a table. (mainly read or mainly write access to the table. In the latter case, for example, one would not select buffering).
You should therefore select:
- Buffering not allowed if a table may not be buffered.
- Buffering allowed but not activated if buffering is principally allowed for a table, but at the moment no buffering
should be active. The buffering type specified in this case is only a suggestion.
- Buffering allowed if the table should be buffered. In this case a buffering type must be specified.
Buffering type
The buffering type defines whether and how the table should be buffered.
There are the following types of buffering:
single-record buffering
generic area buffering
full buffering
In generic area buffering, a number of key fields between 1 and no. of key fields-1 must be specified.
Log data changes
The logging flag defines whether changes to the data records of a table should be logged. If logging is activated, every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database.
Note: Activating logging slows down accesses that change the table.
First of all, a record must be written in the log table for each change. Secondly, many users access this log table in parallel. This could cause lock situations even though the users are working with different application tables.
Logging Dependencies
Logging only takes place if parameter rec/client in the system profile is set correctly. Setting the flag on its own does not cause the table changes to be logged.
The existing logs can be displayed with Transaction Table history (SCU3).
Convert to transparent table or maintain transparency
This flag shows that a table should be transparent and that this attribute should be kept even after a change of release or an upgrade.
Transparent Table Use
You can convert pooled tables into transparent tables in a simple manner using the transparent flag. The pooled table must have 'active' status.
Activate the technical settings after setting the flag. You can now decide whether the table should be converted to a transparent table in the background or interactively for a pooled table.
If you want to change the type of a table whose transparent flag has been set, you must first reset the flag and activate the technical settings. The table type must then be changed explicitly and the table must be converted using the database utility.
Note: Only use the transparent flag if the table type is to change from pooled to transparent. You should never use the flag for other table conversions.
0114 - Basis - All SAP - User/Gateway Disconnect
We support 100+ SAP consultants at my company but there have always been one or two who have a problem staying connected to our internal SAP systems. They appear as "Connection to user ** (*******), terminal ** (*****) lost" errors in the sm21 log. Immediately following this message is a "gethostbyaddr failed" message. This implies that something is wrong with the DNS server or the entries therein.
In order to correct this problem, check the C:\windows\system32\drivers\etc\hosts file and see if there is an entry for the server on which the disconnecting SAP system resides. Say, the server is IP address 10.1.1.3, its name is sapserver, and it belongs to the SPACELEY.COM domain. Look for this entry:
10.1.1.3 sapserver SAPSERVER.SPACELEY.COM
If it isn't there, add it using notepad and make sure there is a blank line right after it. See if this fixes your disconnect problem. I thought it was a really long shot I found a really obscure OSS note re: something similiar and it seems to correct the problem. And it is easier than getting the IT folks to correct the problem with the DNS server.
0115 - Basis - All SAP - Resolve problems with SAPGUI history
SAPGUI has a handy feature that remembers fields contents, This is pretty useful especially when loging into SAP. I simply type the first letter of my UserID, press the Arrow-Down key and finally press ENTER. There ya go, my whole userID is typed for me.
Unfortunately, sometimes SAP stops showing old entries. Here's how to troubleshoot this:
Basic steps:
- Press ALT-F12 (or click the color-monitor icon)
- Choose OPTIONS
- Click on the LOCAL DATA tab.
- Make sure that History is set to ON
- Make sure that Directory for Local Data really exists. if unsure, change that to C:\
- If anything was changed, click on OK, stop your all SAPGUI sessions and do not forget to shutdown SAPLOGON (or SAPLOGON PAD)
- restart SAPGUI/SAPLOGON and check if all works
Low-Speed...
- in SAPLOGON, click once on the entry you wish to connect
- Click on CHANGE ITEM
- Click on ADVANCED
- Make sure that LOW-SPEED CONNECTION is not checked.
Corrupted MDB
- in the directory "Directory for Local data" found in Alt-F12, You should find a SAPhistory*.MDB and SAPhistory*.LDB files, these may be corrupted.
Close down SAPGUI and SAPLOGON
- Delete all these files
- Note that all history will be lost but it may re-enable the functionnality
Corrupted DAO files
- SAPGUI uses the MsJet Access database engine to store history. These files may get ruined by another application.
- possible solution is to re-install SAPGUI from scratch
- other possibility is to re-install DAO. These files are available in the DAO35 or DAO36 folder of the SAPGUI installation CD. You can also get it Here
Additional steps
- Make sure that SAPGUI is fully patched
- read OSS Note 199527.
- try rebooting your PC!
__________________
SAP NetWeaver '04 SAP Web AS for ORACLE certified
0116 - Basis - All SAP - Troubleshooting SAP Startup Problems in Windows
Checklist: Troubleshooting SAP startup problems in Windows
by Giovanni Davila at www.sapadministration.com
edited by SSULibrarian at www.sapsuperusers.com
There's probably nothing worse than not being able to start your SAP system … Especially the production system! Aside from the operating system and the database server you must pay close attention to certain places in SAP to find out what caused the problem and how to solve it. Here are the two places you will definitely need to check: EventViewer (Application and System logs) and the SAP Management Console (MMC).
EventViewer can provide useful information and it may help you pinpoint where the problem resides. The SAP MMC gives you the ability to visually see the system status (green, yellow or red lights), view the work processes status and view the developer traces, which are stored in the "work" directory. Example: \usr\sap\TST\DVEBMGS00\work.
For a central SAP instance to start successfully, both the message server and the dispatcher need to start. If one of them or both fail to start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message:
"*** DISPATCHER EMERGENCY SHUTDOWN ***".
Things you need to get familiar with:
Developer Traces:
-- dev_disp Dispatcher developer trace
-- dev_ms Message Server developer trace
-- dev_wp0 Work process 0 developer trace
The "services" file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file is located under %winnt%/system32/drivers/etc.
Windows Task Manager (TASKMGR.exe).
Dispatcher Monitor (DPMON.exe), which is located under \usr\sap\<SID>\sys\exe\run.
Database logs.
EventViewer (EVENTVWR.exe).
TROUBLESHOOTING SAP STARTUP PROBLEMS
Scenario 1: Dispatcher does not start due to a port conflict
Symptoms
No work processes (disp+work.exe) exist in Task Manager.
Dispatcher shows status "stopped" in the SAP MMC.
Errors found in "dev_disp":
***LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti.c 1488]
*** ERROR => NiIBind: service sapdp00 in use [nixxi.c 3936]
*** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi.c 3505]
*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
Problem Analysis
Possible causes for error messages above:
Address already in use
Service sapdp00 in use
The TCP port number assigned in the "services" file is being occupied by another application. Due to the conflict, the dispatcher shuts down.
Solution
If your server has a firewall client, disable it and attempt to start the SAP instance again.
If the instance starts successfully you can enable the client firewall back again.
If there is no firewall client at all, or if disabling it did not resolve the problem, edit the "services" file and check what port the appropriate "sapdp" is using.
If the instance number is 00, look for sapdp00. If the instance number is 01 look for sapdp01 and so on. You can use the following OS command to help you resolve port conflicts:
netstat -p TCP
There are also utilities on the Internet that can help you list all the TCP and UDP ports a system is using.
Scenario 2: Dispatcher dies due to a database connection problem
Symptoms
No database connections.
No work processes.
SAP MMC -> WP Table shows all processes as "ended".
Errors found in "dev_disp":
C setuser 'tst' failed -- connect terminated
C failed to establish conn. 0
M ***LOG R19=> tskh_init, db_connect (DB-Connect 000256) [thxxhead.c 1102]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8437]
*** ERROR => W0 (pid 2460) died [dpxxdisp.c 11651]
*** ERROR => W1 (pid 2468) died [dpxxdisp.c 11651]
*** ERROR => W2 (pid 2476) died [dpxxdisp.c 11651]
. . .
*** ERROR => W11 (pid 2552) died [dpxxdisp.c 11651]
*** ERROR => W12 (pid 2592) died [dpxxdisp.c 11651]
my types changed after wp death/restart 0xbf --> 0x80
*** DP_FATAL_ERROR => DpEnvCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
DpModState: change server state from STARTING to SHUTDOWN
Problem Analysis
A connection to the database could not be established because either the SQL login specified in parameter "dbs/mss/schema" is set incorrectly or the SQL login was deleted from the database server. This parameter needs to be set in the DEFAULT.pfl system profile (under \usr\sap\<SID>\sys\profile). In the messages above, we see that the SQL login 'tst' is expected but it does not exist at the database level.
Solution
Set the entry to the appropriate database owner. If the system is based on Basis <= 4.6 or if the system was upgraded from 4.x to 4.7 the database owner should be "dbo". But, if the system was installed from scratch and it's based on the Web AS 6.x the database owner should match the SID name in lower case. Example: if the SID is TST then the database owner should be "tst". If the parameter is set correctly in the DEFAULT.pfl profile check at the database level if the SQL login exists. If it doesn't, create it and give it database ownership to the <SID>.
Scenario 3: SAP does not start at all: no message server and no dispatcher
Symptoms
The message server and the dispatcher do not start at all in the SAP MMC.
The following error when trying to view the developer traces within the SAP MMC: The network path was not found.
No new developer traces written to disk (under the "work" directory.)
Problem Analysis
The network shares "saploc" and "sapmnt" do not exist. That explains the "network path not found" message when attempting to view the developer traces within the SAP MMC.
Solution
Re-create the "saploc" and "sapmnt" network shares. Both need to be created on the \usr\sap directory.
Scenario 4: Users get 'No logon possible' messages when they attempt to log in
Symptoms
Work processes start but no logins are possible.
Users get the login screen but the system does not log them in. Instead, they get this error: No logon possible (no hw ID received by mssg server).
In the SAP MMC, the message server (msg_server.exe) shows status "stopped".
The dev_ms file reports these errors:
[Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv.c 8163]
[Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv.c 1561]
[Thr 2548] *** ERROR => main: MsSInit [msxxserv.c 5023]
[Thr 2548] ***LOG Q02=> MsSHalt, MSStop (Msg Server 2900) [msxxserv.c 5078]
Problem Analysis
Work processes were able to start but the message server was not. The reason is because the "services" file is missing the SAP System Message Port entry. Example: SAPmsTST 3600/tcp
Solution
Edit the "services" file and add the entry. Then, re-start the instance. Make sure you specify the appropriate TCP port (e.g. 3600) for the message server.
Scenario 5: The message server starts but the dispatcher doesn't
Symptoms
The dispatcher shows status "stopped" in the SAP MMC.
The "dev_disp" file shows these errors:
***LOG Q0A=> NiIServToNo, service_unknown (sapdp00) [nixxi.c 2580]
*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
Problem Analysis
The keyword in the messages above is "service unknown" followed by the entry name "sapdp00". The dispatcher entry "sapdp00" is missing in the "services" file. Example: sapdp00 3200/tcp
Solution
Add the necessary entry in the "services" file. Example: sapdp00 3200/tcp Then, re-start the instance.
Scenario 6: Work processes die soon after they start
Symptoms
All work processes die right after the instance is started.
The SAP MMC shows work processes with status "ended".
Only one work process shows status "wait".
An ABAP dump saying "PXA_NO_SHARED_MEMORY" is generated as soon as a user logs in.
The SAP MMC Syslog shows the following error multiple times: "SAP-Basis System: Shared Memory for PXA buffer not available".
Problem Analysis
The instance profile contains misconfigured memory-related parameters.
Most likely the "abap/buffersize" instance profile parameter is set to high.
Solution
Edit the instance system profile at the OS level under \usr\sap\<SID>\sys\profile and lower the value assigned to "abap/buffersize". Then, restart the instance. Also, it's important to find out if any other memory parameter were changed. If not, the system should start once the adequate memory allocation has been set to the the "abap/buffersize" parameter.
0117 - Basis - All SAP - Understanding the Two Internet OSS Links
I am one of those Basis people who give the Remote Connectivity Data Sheet to the IT group on the very first day of my involvement in the project. And I tell them "Do this as soon as possible. But I know you won't and eventually the functional team will hit a problem that SAP responds to by saying they need access to your SAP landscape via a service connection. And then all hell will break through until you get the job done. It will be ugly."
But, of course, the IT group never does listen. And many times it is partially do to me not being able to explain the two most common OSS link options offered by SAP. I believe that the frame relay is still offered but it is way expensive so we are going to concentrate on the two internet options: VPN and SNC.
If VPN is your choice for connection to SAP, you will need the help of your IT staff to make the adjustments to the company's current VPN mapping. You provide an IP address for your VPN and your saprouter server IP address to SAP, and they FAX you back an information sheet with data similiar to this:
Once the proper configuration of the VPN has been done, you just install the saprouter software - I usually install it on the DEV server - test it out, and you are done.
The second alternative is SNC over the internet. In this case, you need a server with a public IP address placed in your DMZ - a real DMZ which means that the server is not behind a firewall. SAP will be looking for a connection from the public IP address and no other IP address in your network.
Once the server is in the DMZ and ready to go, you send your information to SAP - the server public IP address and the server name - and SAP will send you information regarding how to install and configure the saprouter software, SAP cryptograhic software, and SNC. The instructions are pretty easy to follow so you should be ready to test before you know it.
I generally use a very open saprouttab for testing, and tighten it later. So you can test with:
PHP Code:
P * * *
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
This saprouttab opens permission for all servers to go out to sapserv2.
So, that is really all there is to it. Hopefully, you can explain this procedure with better understanding to your current and future employers/clients.
Send an Instant Message in R/3
Ever wanted to send a message to a single logged on user but don't know their email address or phone number? Run function TH_POPUP from SE37 and enter the client, message (128 chars max) and username. The message immediately appears on that user's screen.
0008 - Hints, Tricks - All R/3s - Change Data In Table Without Authorization Using Transaction se16
There is a way to change entries of a table with SE16 even if you don't have the authorization:
Go in SE16, enter your table Name (ex: USR02). Display the entry (or entries) you want to modify.
When you have your entry, write '/h' to go in debug mode. Cross the line you want to modify and press F7 (display function). Here, you are in the code... Press F7 again to skip some code...
Now you should see the code:
Refresh Exclude_Tab.
If Code = 'SHOW'.
Set Titlebar 'TAB' With Name 'anzeigen'(100).
Elseif Code = 'EDIT'.
...
Change the value from SHOW to EDIT, click Change FLD Contents, and press F8...
or to delete an entry
Change the value from SHOW to DELE, click Change FLD Contents, and press F8...
Here we are... You can change the value to what you want, and don't forget to save!
0023 - Auditing - All R/3s - Trace A User's Activity
Creating a User Audit Profile
1. Log on to any client in the appropriate SAP system.
2. Go to transaction SM19.
3. From the top-most menu bar on the Security Audit: Administer Audit
Profile screen, click Profile -> Create.
4. On the Create new profile popup, type in a new Profile name and click
the green √ picture-icon.
5. On the Filter 1 tab of the Security Audit: Administer Audit Profile
screen, click the □ to the left of Filter active to place a √ in the box.
In the Selection criteria section, select the Clients and User names to
be traced. In the Audit classes section, click "on" all the auditing
functions you need for this profile. In the Events section, click the
radio button to the left of the level of auditing you need. Once you
have entered all your trace information, click the Save picture-icon.
You will receive an Audit profile saved in the status bar at the bottom
of the screen.
6. Please note that while the user trace profile has been saved, it is not
yet active. To activate the user trace, see the next section Activating
a User Audit Profile.
7. You may now leave the SM19 transaction.
Activating a User Audit Profile
1. Log on to any client in the appropriate SAP system.
2. Go to transaction SM19.
3. On the Security Audit: Administer Audit Profile screen, select the audit
profile to be activated from the Profile dropdown. Click the lit match
picture-icon to activate it. You will receive an Audit profile activated
for next system start in the status bar at the bottom of the screen.
The audit will not begin until after the SAP instance has been recycled.
4. You may now leave the SM19 transaction.
Viewing the Audit Analysis Report
1. Log on to any client in the appropriate SAP system.
2. Go to transaction SM20.
3. In the Selection, Audit classes, and Events to select sections of the
Security Audit Log: Local Analysis screen, provide your information to
filter the audit information. If you need to trace the activities of a
specific user, be sure to include that user's ID. Click the Re-read
audit log button.
4. The resulting list is displayed. This list can be printed using the usual
methods.
5. You may now leave the SM20 transaction.
