Information about active Usage Types

Easiest way to find out what Usage Types were installed in a SAP System: URL : http://host:http_port/utl/UsageTypesInfo Login with Administrator Id/password.

Note that the Usage Types delivered with other tools - like SDM (via manual deployment of corresponding SCAs) - are not presented here.

Installing SAP Webdispatcher

1. Read SAP Note 538405
2. Read SAP Help: http://help.sap.com/saphelp_nw70/helpdata/en/b4/9aa8862e714e6db8e74e48e5d3283b/frameset.htm
3. Download the webdispatcher from http://service.sap.com/ ->Support Packages and Patches-> Entry by Application Group-> Additional Components-> SAP Kernel-> SAP Kernel 32 Bit or SAP Kernel 64 Bit-> SAP Kernel 7.01 -> Operating system platform-> Database independent ->The package is called sapwebdisp_<>-<...>.SAR, where <> indicates the patch level
4. Create a direactory /usr/sap/SID/webdisp on server and copy the downloaded webdispatcher sapwebdisp_35-10006297.sar
5. Uncar the downloaded file
6. /usr/sap/SID/SYS/exe/run/SAPCAR -xvf sapwebdisp_35-10006297.sar
7. chown SIDadm:sapsys *
8. 
9. Run this commnad to install webdispatcher: sapwebdisp.pfl -cleanup -shm_attach_mode 4 -auto_restart -bootstrap
10. Installation process provide the values to below parameters:
11. Hostname of Message Server (rdisp/mshost):messageserver hostname
12. HTTP Port of Message Server (ms/http_port): 81Instance_Number
13. Unique Instance Number for SAP Web Dispatcher (SAPSYSTEM): Give a unique name
14. HTTP port number for SAP Web Dispatcher: 280_Instance_Number
15. Create configuration for s(mall), m(edium), l(arge) system (default: medium): l
16. At the end you will see this message, SAP Web Dispatcher bootstrap ended (rc=0), ð *** SAP Web Dispatcher up and operational (pid: 12956) ***
17. Then start the webdispatcher: sapwebdisp pf=sapwebdisp.pfl -checkconfig
18. Make sure the dispatcher started :
19. ps -ef grep webdisp
20. SIDadm 14561 11954 0 16:32:13 pts/2 0:00 grep sapwebdisp
21. SIDadm 12956 1 0 16:26:29 pts/1 0:01 sapwebdisp pf=sapwebdisp.pfl -shm_attach_mode 6

How to start/stop SDM on UNIX

To start or stop the SDM Server of the J2EE Engine, proceed as follows:

1. Log in as SIDadm
2. Navigate to the usr/sap/SID/INSTANCE_NUMBER/SDM/program directory of your J2EE Engine installation.
3. To stop the SDM Server, execute the command: StopServer.sh password=sdm_password
4. To start the SDM Server, execute the command: StartServer.sh

Creating Jco Connections in Portal

1. Maintain the default URL of the IGS as documented in SAP note 704604. The URL should be http://host:4SN80
2. Make sure the IGS has been installed correctly on ECC as per SAP note 454042.
3. Access the WebDynpro Content Administrator (open a browser and point to: http://host:5SN00/irj
4. Navigate to Content Administration -> Web Dynpro
5. Click the “Maintain JCo Destinations” button
6. Click the Create link for SAP_R3_Financials_MetaData
7. Accept the default for the J2EE cluster and click Next
8. Make sure that “Dictionary Meta Data” is selected and click Next
9. Select the right message server and then click Next
10. Enter a user name and password that was defined earlier in the ECC system. Then click Next.
11. Verify that everything looks okay, and then click Finish. The status indicator should turn to green
12. Next, set up the SAP_R3_Financials connection
13. Accept the default for the J2EE cluster and click Next
14. Make sure that “Application Data” is selected and click Next
15. Select the right message server and then click Next
16. Select Ticket for Used Method in USer Authentication. Then click Next
17. Verify that everything looks okay, and then click Finish. The status indicator should turn to green
18. Continue the above procedure with other connections.

Single Sing On with Kerberos Authentication

We can use the SPNego configuration wizard to enable authentication for all users belonging to a Active Directory to log on transparently to the AS Java with Single Sign-On.

• WebAS Java 640 SP15 or higher
• JDK 1.4 or higher
• Microsoft Windows Server 2000/2003 Active Directory

How to start the wizard:

1) http://host:port/spnego

2) In the SAP NetWeaver Administrator by following the path System Management -> Configuration -> SPNEGO Configuration Wizard. Steps: 1) Create and configure a service user on the Active Directory Servers (ADS), which act as a Kerberos Domain Controllers (KDC) with the below properties

• The password of the user must never expire.
• The user must be enabled to use DES encryption.

2) On the ADS for each Kerberos Realm, register with the ADS service user a Service Principal Name (SPN) for every DNS name that can be used to access the AS Java with Kerberos authentication.

• setspn -a HTTP/FQDN serviceusername
• setspn -a HTTP/hostname serviceusername
• Do a quick check with setspn -L to see the settings are succssful.
• setspn -L serviceusername
• You should get the below screen.

3) LDAP settings in Configtool

• Logon to the Configtool and navigate to cluster-data -> UME LADAP data
• We have to connect j2ee UME to ADS. In order to do this, upload dataSourceConfiguration_ads_readonly_db_with_krb5.xml attached to the SAP Note 994791

• Enter the data in Connection details
• Make sure to test the connection and Test Authentication
• Restart the J2ee system.

4) Run SPNego wizard

• Start the SPNego wizard
• Select the check box Service user is created and configured in Active Directory to confirm that this step is completed
• Select the checkbox UME configuration includes SPNego specific settings to confirm that this step is completed
• Choose Next to proceed
• In the Jerberos Realm screen, Enter the name of the Kerberos Realm or Windows Domain inside the input field Realm Name.
• Choose Add KDC to add the host address and port for the Key Distribution Center (KDC).
• Choose Retrieve Principal to retrieve the AS Java Kerberos Principal Name (KPN), registered for the AS Java service user in the LDAP Directory. a. Enter the Service User Name. b. Enter the Service User Password.
• Choose Type Principal to manually enter the AS Java’s KPN. a. Enter the KPN of the AS Java in Principal. b. Enter the password for the AS Java service user in Password
• Choose Next to proceed
• Choose the Resolution Mode to use
• Use the Test resolution Mode functions to test the resolution of user ids from the configured domains
• Choose Next to proceed
• Choose the policy configuration to configure for Kerberos. a. Choose Use existing to select an existing template for Kerberos. b. Choose Create new to create a new policy configuration template.
• Add fallback authentication mechanisms for the case when Kerberos authentication fails. a. Choose Enable Basic Password Fallback to enable the login modules for authenticating users with a user id and password as a fallback mechanism. b. Choose Enable SSO with SAP Logon Tickets to enable the login modules for authenticating users with logon tickets as a fallback mechanism
• Choose Next to proceed
• Review the displayed information about the Kerberos configuration changes you made. The confirmation screen shows the configuration information for each of the configured Kerberos Realms or Windows Domains.
• Choose Finish to commit the changes. The wizard proceeds to the Final step and displays a confirmation of the changes you made.
• Restart J2ee system.

Final Steps:

• Logon to Visual Administrator and navigate to Server -> Services ->Security Provider, in Runtime -> Policy Configurations -> Components, select ticket.
• Switch to Edit mode and select spnego from Authentication template
• Select com.sun.security.jgss.accept from Components and choose Login Modul com.sun.security.auth.module.Krb5LoginModule
• Add isInitiator=false
• Change the Internet Explorer settings to use Integrated Windows authentication and test.
• Restart J2ee system.

TEST SSO:

Hit the URL http://host:port/irj/portal, It shoud not ask for username/password.

Enable Debug mode in J2EE System

To enable debug in J2EE , launch the J2EE Config Tool via usr/sap/SID/JC/j2ee/configtool/configtool.sh . Then click on Instance and in the right pane navigate to the Servers Debug tab. There select the Debuggable tick box as well as the Enable Debug Mode tick below it.

Sample Login Module Stacks for Using Logon Tickets

Sample Login Module Stack for Creating Logon Tickets When processing the following login module stack, the server will issue the user a logon ticket after successful authentication using the Basic Authentication mechanism (user ID and password). Login Modules Flag BasicPasswordLoginModule OPTIONAL CreateTicketLoginModule SUFFICIENT Sample Login Module Stack for Accepting Logon Tickets When processing the following login module stack, the server will accept a user’s logon ticket. If the user does not possess a valid logon ticket, then the server reverts to using Basic Authentication. Login Modules Flag EvaluateTicketLoginModule SUFFICIENT BasicPasswordLoginModule SUFFICIENT Sample Login Module Stack for Creating and Accepting Logon Tickets When processing the following login module stack, the server will revert to authentication using Basic Authentication if the user does not possess a valid logon ticket. After successful authentication, the server then issues a logon ticket to the user. This is the login module stack provided with the ticket component. Login Modules Flag EvaluateTicketLoginModule SUFFICIENT BasicPasswordLoginModule REQUISITE CreateTicketLoginModule OPTIONAL

Configuring the J2EE Engine to Accept Logon Tickets

The J2EE Engine uses EvaluateTicketLoginModule to accept logon tickets for SSO. After receiving the logon ticket from the user’s Web browser, the J2EE Engine verifies the ticket signature based on the established trust relationship with the issuing system. Based on the ticket validity, the J2EE Engine authenticates the user. For the case when you use authentication assertion tickets for SSO between the AS ABAP and the J2EE Engine, the corresponding module is EvaluateAssertionTicketLoginModule.

To check the validity of a user’s logon ticket, the J2EE Engine must be able to verify the issuing server’s digital signature. ● If the J2EE Engine is both the ticket-issuing server as well as the accepting server, then it can automatically verify its own digital signature. ● If the ticket-issuing server is a different one, then this server’s public-key certificate must be available in the keystore view that the J2EE Engine uses for verifying logon tickets.

Open the SSO wizard by following the path System Management -> Configuration ->Trusted Systems. There are two ways to add a trusted system. 1) Add a Trusted System by connecting to it.

• In the Trusted Systems section, choose Add Trusted System -> By Querying Trusted System.
• The System Landscape Directory (SLD) opens automatically and lets you select the system you want to add. Select the system and choose OK. The connection details for the selected system are displayed automatically.
• Enter your user name and password in the provided fields and choose Next.
• The details about the selected system’s certificate appear. To add the system, choose Finish. If you want to make changes, choose Back.

2) Adding a Trusted System by Manually Uploading its Certificate.

• Export the ticket issuing Trusted System certificate.
• In the Trusted Systems section choose Add Trusted System ® By Uploading Certificate Manually.
• Enter the System ID and Client in the provided fields.
• Browse to the location of the system’s certificate. Select the certificate and choose Open.
• Choose Next. The information about the system and the certificate is displayed. To add the system as trusted, choose Finish. If you want to make changes, choose Back.

Add the login module EvaluateTicketLoginModule (or EvaluateAssertionTicketLoginModule) to the login module stacks for the J2EE Engine policy configurations of the application components that accept login tickets for SSO. To do this, use the Security Provider Service of the Visual Administrator.

• In the Security Provider Service choose Runtime -> Policy Configurations -> Authentication tab.
• Select the policy configuration for the application component to accept logon tickets from the Components list.
• Choose the Switch to edit mode button.
• Choose Add New. The list of available login modules for the component appears.
• Choose the EvaluateTicketLoginModule (or EvaluateAssertionTicketLoginModule) from the list and choose OK.

After you complete the wizard, the ticket-issuing system is shown in the Trusted Systems list. The J2EE Engine accepts logon tickets that have been issued by the corresponding server.

Deploying SSO wizard for SAP Netweaver 7.0 SP13 or lower

To deploy SSO wizard for SAP Netweaver 7.0 SP13 or lower, check SAP Note 1083421. Once you deployed SDA files to above note the SSO2 wizard is accessible at :/sso2">http://:/sso2 For SAP Netweaver SP14 or higher, we can access the SSO wizard by following the path System Management --> Configuration --> Trusted Systems.

Unicode Conversion troubleshooting guide

I found a good SAP note with checklists and a troubleshooting guide attached on when problems or errors occur during conversion from non-Unicode SAP System to Unicode SAP System. Have a look at SAP Note 765475.

Security Troubleshooting Guide For NetWeaver J2EE 640/700

I found a Netweaver Security troubleshooting guide attached to SAP Note 1296330. This guide is valid for the NW04 and NW04s releases, including EhP1 and EhP2 of NW04s. The index of this document is: Chapter 1 - AuthenticationRead this chapter if you have general problems logging in to a resource on the SAP J2EE Engine (NetWeaver Administrator, User Management, System Information) or to standalone SAP applications which connect to the SAP J2EE Engine (Visual Administrator). No single sign-on must be active on the system. Chapter 2 - AuthorizationRead this chapter if you see error messages saying that the user is not authorized to access the requested resource. Chapter 3 - Session ManagementRead this chapter if you think that the security sessions of the user expire when they should not or if a user is incorrectly logged in to the SAP J2EE Engine as another user. Chapter 4 - Single Sign-OnRead this chapter if you have a single sign-on scenario and it fails. Chapter 5 - SPNegoRead this chapter if you have setup the SAP J2EE Engine to use Kerberos authentication via SAP's SPNego mechanism. Chapter 6 - SSLRead this chapter if you have enabled communication over the SSL protocol and it fails. Chapter 7 - Key StorageRead this chapter if you see error messages saying that there are problems with Key Storage views or if you have problems importing/exporting certificates.

SAP Basis transaction codes

Some of the transaction codes does not exist in new sap versions: AL08 Users Logged On AL11 Display SAP Directories AL12 Display table buffer (Exp. session) AL13 Display Shared Memory (Expert mode) AL15 Customize SAPOSCOL destination 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/PathsNACE 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 IMGSCPR1 Customizing Profiles : Maintenance Tool SCPR2 Comparing Customizing profiles SCUA Central User Administration : Distribution Model Assigment SCUG Central User Administration Structure Display SCULSCUM Central User Administration Field Selection SCU0 Table Analyses And Comparison SCU1 Table Comparison - Export to Tape SCU2 Table Comparison Against Tape SCU3 Table HistorySD11 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 PainterSE43 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 NavigatorSE81 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: InboxSINA 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 SM61SM62SM63 Display/Maintain Operating Mode Sets SM64 Release of an event SM65 Background Processing Analysis Tool SM66 System-wide Work Process Overview SM67 Job schedulingSM68 Job administration SM69 Display/Maintain Logical Commands SMEN Dynamic menuSMGW 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 ApplicationsSOLI 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 CCMSSSM1 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 Monito rST07 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

What is SAP Basis Administration

A set of middleware programs and tools that provide the underlying base that enable applications to be interoperable across operating systems. SAP Basis includes a RDBMS, GUI, and client server architecture. Beyond the interface aspect of Basis, it also includes such components as a data dictionary as well as user and system administration. Basis is a business application software integrated solution. Simply, Basis is the administration of the SAP system. It's a piece of middleware which links the application with the database and the operating system. Basis is most commonly associated with the GUI interface to the SAP, and the Basis administrator is an SAP, professional who is responsible for configuring the SAP environment, including the GUI screens and SAP application servers.

More SAP Training stuff !!!

SAP Service Market Place - here SAP Help - here SAP Trail Softwares - here SAP Forums - here SAP FAQ - 1 2 3 SAP BOOKS - SAP PRESS

SAP Training Materials

There is a very good resource if you want to learn SAP. Click here to see what you can get for less money! They have a huge discount these days, you can get all their SAP materials for only 47 USD. Almost FREE SAP Courses - click here. SDN Forums - Click here SAP Certification Exams and Training - Click here