Not original. From http://abaptutorial.blogspot.com/2006/01/sap-abap-transaction-codes.html

SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)

SE12 Dictionary: Initial Screen – enter object name.

SE13 Access tables in ABAP/4 Dictionary.

SE14 Utilities for Dictionary Tables

SE15 ABAP/4 Repository Information System

SE16 Data Browser: Initial Screen.

SE16N Table Browser (the N stands for New, it replaces SE16). Provided by Smijo Mathew.

SE17 General Table Display

SE24 Class Builder

SE30 ABAP/4 Runtime Analysis

SE32 ABAP/4 Text Element Maintenance

SE35 ABAP/4 Dialog Modules

SE36 ABAP/4: Logical Databases

SE37 ABAP/4 Function Modules

SE38 ABAP Editor

SE39 Splitscreen Editor: Program Compare

SE41 Menu Painter

SE43 Maintain Area Menu

SE48 Show program call hierarchy. Very useful to see the overall structure of a program. Thanks to Isabelle Arickx for this tcode.

SE49 Table manipulation. Show what tables are behind a transaction code. Thanks to Isabelle Arickx for this tcode.

In addition to selecting OSS Notes related to upgrades, you can also go directly to the Release and Upgrade area on the SAP support portal.

Doing this type of searching in the SAP Support Portal requires a great deal of repeated searching. Therefore, it makes a lot of sense to use their single sign on. You can apply for it by Applying for an SAP Passport.

Its good to backup this passport in order to use it on other computers.

Now instead of asking for a logon when you type in http://service.sap.com/ you will be greeted with:

You can find pretty much anything about a release from the Support Website including which database platforms it works with.

SAP has come a long way in its management and display of OSS notes. By going to http://service.sap.com/notes you will be taken to a login screen. Select “Search for SAP Notes” in the upper left hand corner of the screen. You can then search by search term or application area. (you can even search by the OSS Note if you have it handy by selecting in the search box in the upper right corner)

With such a broad search, you can now select by a more detailed view. You can search by release or by area of the module. The note looks like this:

According to SAP their are over 450,000 entries for all SAP solutions or subject areas.

In addition to seaching you can also receive new OSS notes in your inbox. This is called TopNotes or HotNews. One problem was that the listing was a bit old (APO version 3.1 when we did our search) Here you can see we are setting up our filter for SCM related news.

This is necessary to setup in order to perform imports and exports using the OEM. You can get into this setup by typing “emca” at the command prompt.

After selecting to configure a local OMS, then below you will be asked to…

Create a new repository. Now it gives you a repository summary.

The final step is it goes through and creates it:

Then it asks for your password.

Finally it is complete

The next step is to connect the OMS to the OEM.

This is from the SAP install manual. However we were not able to find any file like this in our installation disks.

“You use this procedure to install the R3SETUP tool on the domain controller where the Active
Directory is located.
…
1. Log on to the domain controller as domain administrator.
2. Check that the TEMP environment variable has been set:
a. Right-click My Computer on the Windows desktop
b. Choose Properties → Advanced → Environment Variables.
TEMP is normally set to:
%userprofile%\Local Settings\Temp
For more information, see SAP Note 387745.
3. Insert the SAP Kernel CD.
4. Start the program R3SETUP.BAT from the directory
<CD_DRIVE>:\NT\COMMON
The R3SETUP window opens.
5. Enter the following when R3SETUP prompts you:
􀁻 The name of your SAP system <SAPSID>
􀁻 The directory on your hard disk that the R3SETUP files are to be copied to. The
default directory is <DRIVE>:\USERS\<SAPSID>ADM\INSTALL
When you have made all the required entries, the R3SETUP tool is automatically
installed.
6. Choose Yes when a dialog box appears prompting you to log off or reboot.
The R3SETUP tool now automatically logs off or reboots.” – SAP Installation Manual

This post simply lists the details of our SAP Install. We recommend you document your install the same way so its easy to find:

Oracle SYSTEM USER

user: system
password: na*******

Schema SAPSAP
password: SAPSAP

user: SYS
password: na******

user: SAPUSER
password: SAPUSER

Port

1521

Host Name

SAP

We now want to login to the Oracle schema that was created through Part 2 SAP Install on Windows Server 2003.

We will start off by starting Oracle Enterprise Manager off of the Start Menu

This will take us to the main screen:

Once we select our database, we will be asked to login under a user.

What is confusing is that the schema created by SAP does not have a password. However, you did assign a password to the default schema. In our case we used:

user: system
password: na*****

Once in, there is a huge amount of detail in this Oracle Enterprise Manager. Its beneficial to go through the different screens and understand what has been setup.

Here you can use the Schema selection to import data into a schema.

The next step is to create a user for the SAP data to be installed in. You can use the OEM to do this or use SQLPlus. We will show both ways.

To create a user in the OEM, select the green cube in the upper left corner. Then scroll down and select the user item.

Then fill in the necessary information

The other way is to use SQLPlus. In addition you will need to grant the user privileges:

Even though the user has now been created, you will find that there are no tables defined in the schema.

Next it will ask to start the installation and provide you with a checklist of what you selected through the process up to this point.

This next screen is the screen shown during the installation.

The next step will take us to the MMC, which should have been installed and is available off of your Start Menu.

In SAP its Required to setup an LDAP server.

“The Lightweight Directory Access Protocol (LDAP) is a feature of Windows 2000 or higher
that allows important information within a corporate network to be stored centrally on a server.
The advantage of storing information centrally for the entire network is that you need only
maintain data once, so avoiding redundancy and inconsistency.” – From SAP

As you can see, we instead choose to use the Active Directory Service. Since we are explaining how to install on a single Virtual Machine for personal use, we do not need to concern ourselves with the LDAP server. (If you are interested in this goto R/3 System Information in Directory Services in SAP Service Marketplace service.sap.com/msplatforms – Microsoft – Windows Server)

Implications for Login

The SAPMSG.ini file is a configuration file to find SAP systems and their message servers from the directory.

MMC

This is the GUI for administering SAP. Events can be tracked in this interface.

The first step is to prepare the Active Directory so it can store SAP data. (as you can see this was done in the LDAP step above) You will see the MMC after you have completed the base installation of SAP.

This is how you start and stop the SAP system. Do this by selecting the SAP logo and performing a right mouse click. Select “Stop”. Notice the change in the SAP logo color.

Then start SAP by doing the same action, but selecting “Start.” The system will boot with SAP started, just as Oracle starts from system startup.

The Process List is very handy in MMC. Here it shows we have a problem connecting to the database.

After we reboot this issue is solved. However, we still have problems. We can view them by selecting the Syslog to see its messages. Errors have different categories and our serious errors have to do with the database, so the SAP database is still not setup correctly. This should not be a surprise as we do not have any data loaded into the system yet.

First you need to start with server software installed. We are installing SAP on Windows Server 2003. This is a good reliable server. It is also available for free for 6 months of use from the Microsoft website.

Overall Recommendation

The SAP installation is tricky for this reason we recommend that you install on a Virtual Machine and make copies of the virtual machine along the way.

Oracle Installation

Oracle installation for SAP works a bit differently than for most applications.

Environmental Variables

1. Change the system date and move it back 20 years. This is to move around SAP’s licensing. It should not be an issue if the system is only used for learning purposes
2. Change the name of the computer to be less than 13 characters

Oracle Install

1. You install the Oracle 9.2.0 database software (but do not create any databases yet).

\SAP Install\Disk 1\INST\SAPINST\NT\I386\setup.exe

• For a 32-bit system there are three RDBMS CDs. They are located on the RDBMS DVD for 32-bit in the directories ORA92_1 to ORA92_3.
• For a 64-bit system there are two RDBMS CDs. They are located on the RDBMS DVD for 64-bit in the directories ORA92_1 to ORA92_2.
• During the installation, you are prompted to specify the correct path to CD2 and CD3, if applicable. To avoid this, you can copy the CDs to disk as follows

Before the installation:

1. Copy the contents of ORA92_1\NT\ on the RDBMS DVD to \disk1 on your hard disk.
2. Repeat this for the second CD.
3. For a 32-bit system, also repeat this for the third CD.
4. \disk1 to \disk3 can be on a network drive if required.
5. You must run different files to install the client and the server software.
6. MSCS only:
7. Install the Oracle 9.2.0 software on both nodes

Procedure
…
1. Start the Oracle Universal Installer as follows:
Place the Oracle RDBMS DVD for 32-bit or 64-bit in the DVD drive and start
from \ORA92_1\NT\
If you have copied the CDs to disk, start from \disk1

Select SAPSERVER.CMD

On the database server, double-click the file sapserver.cmd

This procedure tells you how to run SAPinst to install one or more SAP instances.
It describes an installation where SAPinst GUI and SAPinst server are running on the same
host. If you want to perform a remote installation (SAPinst GUI is running on another host),
see Remote Installation with SAPinst [Page 115].
SAPinst normally creates the installation directory sapinst_instdir directly below the
Program Files directory.

Each SAP instance requires a separate installation directory.

The SAPinst Self-Extractor extracts the executables to a temporary directory ($TEMP, $TMP,
$TMPDIR, or $SystemRoot). These executables are deleted after SAPinst has stopped
running. Directories with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the
temporary directory. You can safely delete them.

In the temporary directory you can also find the SAPinst Self-Extractor log file
dev_selfex.out, which might be useful if an error occurs.

If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following:

• Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit.
• Click the icon for the SAPinst output window located in the Windows tray and choose File → Exit.

Prerequisites

• You need at least 50 MB of free space in the installation directory for each ABAP installation service. In addition, you need 60-200 MB free space for the SAPinst executables. If you are not able to provide 200 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP or TMPDIR to another directory with 200 MB free space for the SAPinst executables.
• We recommend that you keep all installation directories until the system is completely and correctly installed.
• If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.
• If you are installing a second or subsequent SAP system into an existing database, make sure that the database is up and running before starting the installation. For more information, see Installation of Multiple Components in One Database [Page 37].
• SAPinst GUI Handling
• The following push buttons are available on the different SAPinst GUI dialogs (input screens, installation progress screen, message boxes):

Here it will ask you for basic data for the install. Filling in SAP for the SAPSID is fine, 00 for the instance number and SAP for the instance host is fine.

Next it will ask for more basic info:

SAP LDAP vs. ADS and MMC for an explanation on this

After LDAP or the ADS selection is complete it will ask if you want to locate executables on a central instance host. In most cases you will say yes and select the C: drive for installation.

During a central instance installation the following directory is created:

\usr\sap This is how it should look after the installation:

This directory can be accessed from all the hosts in the SAP system. The SAP software is stored in the \usr\sap directory. This directory is shared with the sapmnt and saploc. Because traces are created in this directory is must be able to grow large. We are using VMWare and we think this can grow in a way only limited by the hardware.

Next it will confirm the Database details. We only have the one datbase home so it simply grabs the default

It will ask for a file:

Select SAP Install\Disk1\KERNELU\ There is a LABEL.ASC sitting in this directory and it will pick it up.

1. The tricky part next is pointing SAP to the correct LABEL.ASP file. As you can see from my Finder screenshot there are many LABEL.ASP files to choose from.

As you can see there are a number of them:

We used TextMate (for mac, but there are similar editors for Windows) to view what is in these files.

The SAP installer has a good error generator, so it tells you which file it wants.

This is actually the correct one.

SAP Install Disk 1/IGS/DVD_NW_04_SR1_SAP_WEB_AS_JAVA/IGS/IGS_SOFT

Basic host parameter information follows. Accept the defaults.

LDAP comes next and is explained in Part 2 LDAP and MMC

Select SAPCLIENT.CMD

On the database client double-click the file sapclient.cmd
2. Enter the information as shown in the following table.