1) SU01 User Maintainence
2) SCC4 Client Overview ( Create , Quick Delete , Modify )
3) SCC5 Deletes a client completely with tables & other factors
4) SCCL Local Client Copy
5) SCC9 Remote Client Copy
6) SCC3 Client Copy log Analysis
7) DB02 Storage Management & Database Performance
8) DB12 SAP Backup Logs
9) DB14 Database Monitor
10) SM12 Lock Entries
11) SM21 System Logs
12) SM36 Background Job Scheduling
13) SM37 Background Job Monitoring
14) SM31 Table Maintenance
15) SM50 Process Overview
16) ST22 ABAP Dumps
17) ST02 Buffer Analysis
18) ST03 Workflow Analysis
19) RZ04 Operation Mode
20) SE09 Transport Organizer
21) SCC1 Copy as per Transport Request
22) STMS Transport Management System
Tuesday, April 5, 2011
Important SAP Basis T-Code
SAP Basis T-Code
Basis transaction t codes
Administration
AL11 Display SAP Directories
BD54 Maintain Logical Systems
OSS1 Logon to Online Service System
SALE IMG Application Link Enabling
SARA Archive Management
SCC3 Copy Analysis Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCC9 Remote client copy
SCCL Local Client Copy
SCU0 Customizing Cross-System Viewer
SICK Installation 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
SM35 Batch Input Monitoring
SM50 Work Process Overview
SM51 List of SAP Servers
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM66 System Wide Work Process Overview
SAINT SAP Add-on Installation Tool
SPAM SAP Patch Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11 Display Developer Traces
ST22 ABAP/4 Runtime Error Analysis
SU56 Analyze User Buffer
Alert Monitoring
AL01 SAP Alert Monitor
AL02 Database alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL16 Local Alert Monitor for Operat.Syst.
AL18 Local File System Monitor
RZ20 CCMS Monitoring
Configuration
FILE Cross-Client File Names/Paths
RZ04 Maintain Operation Modes and Instances
RZ10 Maintenance of Profile Parameters
RZ11 Profile parameter maintenance
SE93 Maintain Transaction Codes
SM63 Display/Maintain Operating Mode Sets
SPRO Customizing: Initial Screen
SWU3 Consistency check: Customizing
Database Administration
DB01 Analyze exclusive lockwaits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables
Jobs
SM36 Define Background Job
SM37 Background Job Overview
SM39 Job Analysis
SM49 Execute External OS commands
SM62 Maintain Events
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM69 Maintain External OS Commands
Monitoring
AL08 Current Active Users
OS01 LAN check with ping
RZ01 Job Scheduling Monitor
RZ03 Presentation, Control SAP Instances
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
ST07 Application monitor
STAT Local transaction statistics
STUN Performance Monitoring (not available in R/3 4.6x)
Spool
SP01 Output Controller
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration
Transports
SCC1 Client Copy - Special Selections
SE01 Transport Organizer
SE06 Set Up Workbench Organizer
SE07 CTS Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE16 Data Browser
SE80 Repository Browser
SM30 Call View Maintenance
SM31 Table Maintenance
STMS Transport Management System
User Administration
PFCG Profile Generator (Activity Group Maintenance)
PFUD User Master Data Reconciliation
SU01 User Maintenance
SU01D User Display
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Infosystem Authorizations
Other Transactions
AL22 Dependent objects display
BAOV Add-On Version Information
SA38 ABAP reporting
SE38 ABAP Editor
HIER Internal Application Component Hierarchy Maintenance
ICON Display Icons
WEDI IDoc and EDI Basis
WE02 IDoc display
WE07 IDoc statistics
WE20 Partner profiles
WE21 Port definition
WE46 IDoc administration
WE47 Status Maintenance
$TAB Refreshes the table buffers
$SYNC Refreshes all buffers, except the program buffer
SAP Landscape
SAP Landscape
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.
- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
- QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.
- PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
SAP R/3 System architecture
The SAP R/3 System architecture consists of three layers: Presentation, Application, and Data Storage. The
following diagram illustrates the function served by each layer and how the layers work together:
PRESENTATION
Desktop Management
Help desk
WAN Management
WAN Monitoring
MS-DOS
Windows
Macintosh
LAN WAN
UNIX
VMS
NT
UNIX
VMS
Parallel Server
Switch Over
Application
Automation
Workload Distribution
Workload Balancing
High Availability
Performance Tuning
Capacity Planing
DATA STORAGE
Recovery
Backup Strategy
Reorganization
High Availability
Performance & Tuning
Raid disks / Mirrored Disks / Network Backup
Hermes
Novell
OS/2
Presentation
This is where users of the SAP R/3 System will submit input to the SAP R/3 System for the processing of
business transactions. It is also where the output from these transactions appears as output fields, reports,
tables and spread sheets.
On the desktop level, R/3 offers a user-friendly graphical interface called SAPGUI. The system also
integrates alternative interfaces for optimum compliance with your requirements. This includes
integrating common PC applications. Information exchange is also carried out through the Internet, Kiosk
touch screen systems and telephone applications.
Application
An application is a logically independent component residing at the host operating system level within
the SAP R/3 client/server environment. This component is represented by an application server in the
SAP R/3 network. After a user initiates a request at the presentation level, logic is invoked to service and
process that information. The application logic modules can reside on one centralized host machine or be
distributed over several physical host machines within a particular SAP R/3 network.
Typically, the update and enqueue processes reside on the database server in the application layer. In
most cases, the message, spool and gateway processes will also reside on the database server. The
database server may also be referred to as the “central server”.
On the application level, R/3 offers sophisticated mechanisms to optimally use high-performance system
resources. The system implements interconnections between various applications so that they are practical
from a business perspective. R/3 closes the gap between the exacting concept of a business transaction
and transactions from a data processing perspective.
Data Storage
On the database level, R/3 exclusively uses relational database systems by various manufacturers. R/3 is
able to utilize the most advanced features of each database vendor’s product. In other words, it is not
constrained by the lack of features in any individual database engine. Instead, it is able to fully use a
supplier-specific implementation without jeopardizing it’s own portability.
following diagram illustrates the function served by each layer and how the layers work together:
PRESENTATION
Desktop Management
Help desk
WAN Management
WAN Monitoring
MS-DOS
Windows
Macintosh
LAN WAN
UNIX
VMS
NT
UNIX
VMS
Parallel Server
Switch Over
Application
Automation
Workload Distribution
Workload Balancing
High Availability
Performance Tuning
Capacity Planing
DATA STORAGE
Recovery
Backup Strategy
Reorganization
High Availability
Performance & Tuning
Raid disks / Mirrored Disks / Network Backup
Hermes
Novell
OS/2
Presentation
This is where users of the SAP R/3 System will submit input to the SAP R/3 System for the processing of
business transactions. It is also where the output from these transactions appears as output fields, reports,
tables and spread sheets.
On the desktop level, R/3 offers a user-friendly graphical interface called SAPGUI. The system also
integrates alternative interfaces for optimum compliance with your requirements. This includes
integrating common PC applications. Information exchange is also carried out through the Internet, Kiosk
touch screen systems and telephone applications.
Application
An application is a logically independent component residing at the host operating system level within
the SAP R/3 client/server environment. This component is represented by an application server in the
SAP R/3 network. After a user initiates a request at the presentation level, logic is invoked to service and
process that information. The application logic modules can reside on one centralized host machine or be
distributed over several physical host machines within a particular SAP R/3 network.
Typically, the update and enqueue processes reside on the database server in the application layer. In
most cases, the message, spool and gateway processes will also reside on the database server. The
database server may also be referred to as the “central server”.
On the application level, R/3 offers sophisticated mechanisms to optimally use high-performance system
resources. The system implements interconnections between various applications so that they are practical
from a business perspective. R/3 closes the gap between the exacting concept of a business transaction
and transactions from a data processing perspective.
Data Storage
On the database level, R/3 exclusively uses relational database systems by various manufacturers. R/3 is
able to utilize the most advanced features of each database vendor’s product. In other words, it is not
constrained by the lack of features in any individual database engine. Instead, it is able to fully use a
supplier-specific implementation without jeopardizing it’s own portability.
SAP 4.7 installation windows:
Installing SAP 4.7 on Windows XP Pro
and Windows Server 2003:
Minimum System Configuration:
OS: Windows XP Pro Service Pack 3
RAM: 2GB
Processor: 1.6Ghz
Hard Disk
C: Windows OS – 60GB
D: 110 GB – I installed SAP on this empty drive
Minimum System Requirement:
WinXP Pro/Windows Server 2003
Min RAM (I am told 512MB is fine, but I think it will really slow down the installation)
HDD – 120 (If installing on your laptop/desktop)
External HDD: 80GB (You can install SAP IDES 4.7 on external HDD also, so it’s ok if your local
machine has less space available on it)
System name (My computer>right click> properties> computer name - to be less than 13
character. If the system name is more than 13 characters, click on change and type HOME or
something to that effect.
SAP GUI 6.20
download it.
File size: 456MB
SAP IDES 4.7 Installation files. File size 14.5GB
Important Files:
51020178_1, _2, _3 are very important. They contain EXPORT_1,to _7 folders
Oracle folder installs oracle on your drive
Install MS Loopback Network Adaptor
Why? SAP requires some sort of network connection. If you are on the internet and also
working on SAP , and your connection drops…you will be disconnected from the SAP Server.
Go to control panel and click on Add Hardware and follow the directions as below
Enter the IP address for the adapter
Go to Network connection
Right click on Local Area Connection 2
Go to properties and click on Internet protocol TCP/IP and click on properties and enter the IP address
Go to cmd prompt (Start menu >Run > cmd) type ipconfig.
This should give you IP address you just configured for the adapter
Increase the Virtual Memory:
My computer>Right click>Properties>Advanced>Performance-Setting>Advance> Virtual
Memory>Change. (Note: If your system conf is very good, then I guess you can leave it as it).
Click on set and ok.
Oracle Installation
Go to the SAP Installation file
Create the DB? NO
Click on Install and the installation would run.
At about 14% in to the installation, the installer would ask for Oracle cd 2location
Click on browse and give the path as below
At about 45% the installer will ask for Oracle cd3 location.
Click on the browse button and give the path as below
At the end of the installation you will see a pop up for Net Configuration Assistant. Check
the Perform Typical Configuration and click next.
Restart the System.
Now lets install the J2ee sdk file that was downloaded. Double click on the file
Note: If you have Spyware Doctor running, it will block the installation. So either shut it down or
go to Spywarew Doctor’s Setting>History>add the particular event to global action list>then go
to the global action list>right click the event and allow it. The reason I am mentioning it here is
because if you have some spyware installed, it might interfere with the installation as it did with
my JAVA installation.
Click on Yes for the license agreement and change the installation folder to C:\j2sdk
On the next screen, give the 8 character password and click next
Uncheck the Register Application server and click next.
Java is installed on your machine
Assign the Java paths in My Computer>Properties> Advanced > Environment Variables
In the User Variable for Administrator
1. Click on NEW
2. Variable Name : JAVA_HOME
3. Variable Vaule : C:\j2sdk\jdk( This is Java Installed Directory)
4. Click OK
Under System Variable
Select Path > Edit
Add C:\j2sdk\bin at the end of the existing path
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\j2sdk\jdk\b
in;
SAP installation
SAP SETUP
1. Run the R3DLLINS.EXE from E:\SAP_IDES\51019679\NT\I386\NTPATCH
Run SETUP.EXE from E:\SAP_IDES\51019679\SAPINST\NT
1. License Agreement Click> I Agree
2. This will start the SAP Installation GUI
Click on Standard Installation and then click next
Click on Reboot
SAP Installation
After reboot the installation GUI starts again. Click on SAP R/3 and click Next. Then click on I
Agree
Give the System name __ _ and check on Central Instance
Give the default Instance number as 00, Instance Host is the name of your system.
Click Next
Click on local installation
Click on Next
Click on Next
Enter any password for user
Enter any password for SAP service (Note: I entered the same password as previous screen. Its
easier to remember
On the next screen the LABEL.ASC file location is required. Click on browse and select as shown
and click on “check location” and then click ok.
Click on Next
The Central Instance should now begin to install. If there is any errors before this screen, it
means only one thing
1. Your Oracle was not installed properly. Please cancel the installation and re-install oracle.
ΓΌ Your Central Instance has been installed and this installation should not take more than 15-30
minutes. Click on OK
Install the Database Instance.
It takes anywhere between 6-18 hrs, depending on your system configuration. Any error and you
might have to start all over again. Hopefully this guide will stop you from having to do that ☺
Click on START menu, Programs>SAP Inst ORACLE SAPINST> Prepare New Installation. On the
pop up cmd prompt, press any key to continue.
Click on START menu, Programs>SAP Inst ORACLE SAPINST> SAPInst Server with GUI. SAP
installation GUI opens up. Click on SAP R/3 and continue
Enter System ID ____ and check Database Instance
Click on Standard Installation
Click on Install first SAP system into new database
Click next, next for SAP System common parameters
Check Local installation and then click next
Click next for SAP System Instance Directories
Change the drive, as shown, to the drive where your SAP is being installed
You will get a warning notification, click on next.
Type the same password that you entered for Central Instance, for the next two screens
Click on the browse button to point to the path of the LABEL.ASC file.
Click ok to continue to the next screen
In the next screen, the Listener port number is an important parameter. Do the following to see
the port no.
1. Go to the command prompt
2. Type in lsnrctl status listener
Enter the Listener port number and click ok
Click next for database server parameters and drive selection
In your installation you will find 7 EXPORT files. We have to give the path for each one of them
here. Click on browse
Click on next for SAP directory configuration
Give the path for all the EXPORT files from 2 to 7 and click next
Click next for General Load Parameters
Retype the same password that was used earlier
Click on START to install the Database Instance.
Check on “No MNLS support required”
Click on next and the installation will start. This should take 6-18 hours.
Towards the end of the installation the installation will ask you to change ABAP user password.
To Change Default Password.
First go to your desktop, double click on the SAP R3 management console.
Right click on C11 and click on start. The Server color will turn from Grey>Yellow>Green
Go back to the SAP GUI and enter the default password here . The password must be
different from the last 5 entered. Enter 654321..if you want.(can be changed later on,
once you log on to the SAP system). Click ok
Since we are installing IDES, click retry once more (you will get the error again), and
then click OK to end the installation.
Install the SAP GUI and we are good to go.
Log on to ____
Client 000
Use User name SAP*
Password: 06071992
Once logged in the SAP s/w license expiry date would pop up. Click on the green arrow to continue.
Type in the T-Code SU01 (User maintenance) and click the green arrow (enter) next to it to continue
Type SAPUSER in the Test Box and Click on NEW Button
Click on the ‘Logon data’ Tab
Give the initial password (This will be changed in the next logon). Select ‘SUPER’ for user group
authorization.
Click on Profiles Tab
Give the profiles names as SAP_ALL and SAP_NEW
Choose Save
Logout of SAP GUI (System>Log off)
Do the same exercise for Client 800
Log off from SAP
Log in and type user SAPUSER and click on new password
Change the password to a desired one and click the green arrow to continue
Type T-Code SE38 and continue
The popup will ask you for a access key. Type in 36687663221261278694 and click continue.
Enter few details on the next screen (attributes). On the next screen click on local object
The ABAP workbench screen comes up. Click on save and exit SAP.
Your sap has been installed; you can log in SAP as SAPUSER.
and Windows Server 2003:
Minimum System Configuration:
OS: Windows XP Pro Service Pack 3
RAM: 2GB
Processor: 1.6Ghz
Hard Disk
C: Windows OS – 60GB
D: 110 GB – I installed SAP on this empty drive
Minimum System Requirement:
WinXP Pro/Windows Server 2003
Min RAM (I am told 512MB is fine, but I think it will really slow down the installation)
HDD – 120 (If installing on your laptop/desktop)
External HDD: 80GB (You can install SAP IDES 4.7 on external HDD also, so it’s ok if your local
machine has less space available on it)
System name (My computer>right click> properties> computer name - to be less than 13
character. If the system name is more than 13 characters, click on change and type HOME or
something to that effect.
SAP GUI 6.20
download it.
File size: 456MB
SAP IDES 4.7 Installation files. File size 14.5GB
Important Files:
51020178_1, _2, _3 are very important. They contain EXPORT_1,to _7 folders
Oracle folder installs oracle on your drive
Install MS Loopback Network Adaptor
Why? SAP requires some sort of network connection. If you are on the internet and also
working on SAP , and your connection drops…you will be disconnected from the SAP Server.
Go to control panel and click on Add Hardware and follow the directions as below
Enter the IP address for the adapter
Go to Network connection
Right click on Local Area Connection 2
Go to properties and click on Internet protocol TCP/IP and click on properties and enter the IP address
Go to cmd prompt (Start menu >Run > cmd) type ipconfig.
This should give you IP address you just configured for the adapter
Increase the Virtual Memory:
My computer>Right click>Properties>Advanced>Performance-Setting>Advance> Virtual
Memory>Change. (Note: If your system conf is very good, then I guess you can leave it as it).
Click on set and ok.
Oracle Installation
Go to the SAP Installation file
Create the DB? NO
Click on Install and the installation would run.
At about 14% in to the installation, the installer would ask for Oracle cd 2location
Click on browse and give the path as below
At about 45% the installer will ask for Oracle cd3 location.
Click on the browse button and give the path as below
At the end of the installation you will see a pop up for Net Configuration Assistant. Check
the Perform Typical Configuration and click next.
Restart the System.
Now lets install the J2ee sdk file that was downloaded. Double click on the file
Note: If you have Spyware Doctor running, it will block the installation. So either shut it down or
go to Spywarew Doctor’s Setting>History>add the particular event to global action list>then go
to the global action list>right click the event and allow it. The reason I am mentioning it here is
because if you have some spyware installed, it might interfere with the installation as it did with
my JAVA installation.
Click on Yes for the license agreement and change the installation folder to C:\j2sdk
On the next screen, give the 8 character password and click next
Uncheck the Register Application server and click next.
Java is installed on your machine
Assign the Java paths in My Computer>Properties> Advanced > Environment Variables
In the User Variable for Administrator
1. Click on NEW
2. Variable Name : JAVA_HOME
3. Variable Vaule : C:\j2sdk\jdk( This is Java Installed Directory)
4. Click OK
Under System Variable
Select Path > Edit
Add C:\j2sdk\bin at the end of the existing path
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\j2sdk\jdk\b
in;
SAP installation
SAP SETUP
1. Run the R3DLLINS.EXE from E:\SAP_IDES\51019679\NT\I386\NTPATCH
Run SETUP.EXE from E:\SAP_IDES\51019679\SAPINST\NT
1. License Agreement Click> I Agree
2. This will start the SAP Installation GUI
Click on Standard Installation and then click next
Click on Reboot
SAP Installation
After reboot the installation GUI starts again. Click on SAP R/3 and click Next. Then click on I
Agree
Give the System name __ _ and check on Central Instance
Give the default Instance number as 00, Instance Host is the name of your system.
Click Next
Click on local installation
Click on Next
Click on Next
Enter any password for user
Enter any password for SAP service (Note: I entered the same password as previous screen. Its
easier to remember
On the next screen the LABEL.ASC file location is required. Click on browse and select as shown
and click on “check location” and then click ok.
Click on Next
The Central Instance should now begin to install. If there is any errors before this screen, it
means only one thing
1. Your Oracle was not installed properly. Please cancel the installation and re-install oracle.
ΓΌ Your Central Instance has been installed and this installation should not take more than 15-30
minutes. Click on OK
Install the Database Instance.
It takes anywhere between 6-18 hrs, depending on your system configuration. Any error and you
might have to start all over again. Hopefully this guide will stop you from having to do that ☺
Click on START menu, Programs>SAP Inst ORACLE SAPINST> Prepare New Installation. On the
pop up cmd prompt, press any key to continue.
Click on START menu, Programs>SAP Inst ORACLE SAPINST> SAPInst Server with GUI. SAP
installation GUI opens up. Click on SAP R/3 and continue
Enter System ID ____ and check Database Instance
Click on Standard Installation
Click on Install first SAP system into new database
Click next, next for SAP System common parameters
Check Local installation and then click next
Click next for SAP System Instance Directories
Change the drive, as shown, to the drive where your SAP is being installed
You will get a warning notification, click on next.
Type the same password that you entered for Central Instance, for the next two screens
Click on the browse button to point to the path of the LABEL.ASC file.
Click ok to continue to the next screen
In the next screen, the Listener port number is an important parameter. Do the following to see
the port no.
1. Go to the command prompt
2. Type in lsnrctl status listener
Enter the Listener port number and click ok
Click next for database server parameters and drive selection
In your installation you will find 7 EXPORT files. We have to give the path for each one of them
here. Click on browse
Click on next for SAP directory configuration
Give the path for all the EXPORT files from 2 to 7 and click next
Click next for General Load Parameters
Retype the same password that was used earlier
Click on START to install the Database Instance.
Check on “No MNLS support required”
Click on next and the installation will start. This should take 6-18 hours.
Towards the end of the installation the installation will ask you to change ABAP user password.
To Change Default Password.
First go to your desktop, double click on the SAP R3 management console.
Right click on C11 and click on start. The Server color will turn from Grey>Yellow>Green
Go back to the SAP GUI and enter the default password here . The password must be
different from the last 5 entered. Enter 654321..if you want.(can be changed later on,
once you log on to the SAP system). Click ok
Since we are installing IDES, click retry once more (you will get the error again), and
then click OK to end the installation.
Install the SAP GUI and we are good to go.
Log on to ____
Client 000
Use User name SAP*
Password: 06071992
Once logged in the SAP s/w license expiry date would pop up. Click on the green arrow to continue.
Type in the T-Code SU01 (User maintenance) and click the green arrow (enter) next to it to continue
Type SAPUSER in the Test Box and Click on NEW Button
Click on the ‘Logon data’ Tab
Give the initial password (This will be changed in the next logon). Select ‘SUPER’ for user group
authorization.
Click on Profiles Tab
Give the profiles names as SAP_ALL and SAP_NEW
Choose Save
Logout of SAP GUI (System>Log off)
Do the same exercise for Client 800
Log off from SAP
Log in and type user SAPUSER and click on new password
Change the password to a desired one and click the green arrow to continue
Type T-Code SE38 and continue
The popup will ask you for a access key. Type in 36687663221261278694 and click continue.
Enter few details on the next screen (attributes). On the next screen click on local object
The ABAP workbench screen comes up. Click on save and exit SAP.
Your sap has been installed; you can log in SAP as SAPUSER.
SAP GUI Installation steps
Installation - SAP GUI
Find in the folder created previously the following path: GUI\Windows\WIN32 and click on the icon "setup.exe".
Click on 'Next'
Type the appropriate informations as they are written down here.
The 'Description' field is used only to identify the server you want to connect to.
The 'Application Server' field is used to indicate which server you want to connect to.
Here are the steps to install the SAP GUI.
Download the SAP GUI Unzip the file in a folder on your hard drive and follow the steps written here.Find in the folder created previously the following path: GUI\Windows\WIN32 and click on the icon "setup.exe".
A welcome screen appears.
Click on 'Next'.
Click on 'Next'
Create the appropriate elements.
Click on 'Next'.
Click on 'Install'.
When the following screen appears, click on 'Finish'.
When the installation is finished, click on the icon 'SAP Logon'
found on your Desktop. double click
Type the appropriate informations as they are written down here.
The 'Description' field is used only to identify the server you want to connect to.
The 'Application Server' field is used to indicate which server you want to connect to.
- Description:
- Application Server:
- SAP Router String: Leave blank
- SAP System:
- System Number:
| |
|
|
Subscribe to:
Posts (Atom)