Database Reference
In-Depth Information
Summary
• SAP login checks can be performed at the application level by connecting to the newly
installed back-end SAP system using the SAPLogon program.
• Clients 000, 001, and 066 are standard SAP delivered clients.
• SAPGUI helps in connecting to an individual SAP system to perform application
checks.
• Transaction codes SM28, SM51, SM50, ST22, and SM21 can be used to verify suc-
cessful SAP installation.
• SAP operating system-level checks include successful startup and shutdown of the
SAP system and the underlying database.
• SAP work processes and Oracle processes can be checked for successful verification
of the newly installed SAP system.
• SE06 and STMS transaction codes are used to set up the initial SAP Transport Man-
agement system.
• STMS setup is a prerequisite for performing ABAP and Java support package applica-
tion.
• SPAM transaction is used to apply the SAP ABAP support packages.
• SAINT (SAP Add-on Installation tool) is used to apply SAP add-ons.
• The SAP kernel upgrade procedure replaces the older version of the SAP kernel with
the newer kernel executables.
• SGEN transaction is used to generate ABAP loads in the background.
• The SPAD transaction is used to set up an initial printer in the newly installed SAP
system.
• The SLICENSE transaction code is used to install SAP permanent license keys in the
system.
• The SR13 transaction is used to configure the SAP online help.
• The STZAC transaction is used to configure the system time zone settings.
• Client copy setup and import of profile parameters are some of the other important
post-installation activities.
• Client administration tools are used to copy a SAP-delivered client, such as 000, to a
customer-owned client.
