置顶
===========================================================
SAP Best Practices Installation
===========================================================
项目需要所以安装了SAP Best Practices,按照下图准备系统;
再按照如下步骤激活系统配置;
===========================================================
北京
===========================================================
进入新公司在长安呆了数天便飞到了北京,突然的气温变化，真是让人受不了; 北京的气温虽然很低,但人文环境比广东要好;
这边的项目估计要下个月才会开始，我最近的任务就是做硬件方案,集成商评估,数据库和软件早就买了，SAP under DB2,
第一次基于DB2+LINUX安装SAP,不过还算是顺利，花了两三天时间装好了第一套IDES的系统;
只是希望今年过年前就能离开北京，因为北京的冬天太可怕了!!!
===========================================================
Oracle Database Open Error
===========================================================
When I open the database after apply patch 10.2.0.2:
SQL> startup open;
ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced
I find the error log from $ORACLE_HOME/saptrace/alertPRD.log
Errors in file /oracle/PRD/saptrace/usertrace/prd_ora_22379.trc: ORA-00704: bootstrap process failure ORA-39700: database must be opened with UPGRADE option Thu Dec 25 09:34:45 2008 Error 704 happened during db open, shutting down database
Solution:
Enter the following SQL*Plus commands:
SQL> STARTUP UPGRADE SQL> @$ORACLE_HOME/rdbms/admin/catupgrd.sql
Run the
utlrp.sqlscript to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
===========================================================
ECC 6.0 Install on Solaris X86 64bit PC
===========================================================
ECC 6.0 Install on Solaris X86 64bit PC
Hard Env:
CPU: Intel Duol Core E2200
Memory: 4GB DDR
Harddisk: 500GB
Software Env:
OS: Solaris 10 u4 x86
MySAP erp 2005 sr2 (ECC 6.0)
Database: Oracle 10.2.0.2 (For Solaris X86 64bit)
JDK: Sun j2sdk 1.4.2_13 for Solaris for x86
CPU Check Result:
bash-3.00# isainfo -v
64-bit amd64 applications
cx16 mon sse3 sse2 sse fxsr mmx cmov amd_sysc cx8 tsc fpu
32-bit i386 applications
cx16 mon sse3 sse2 sse fxsr mmx cmov sep cx8 tsc fpu
Issue :
bash-3.00# ./sapinst
[==============================] / extracting... done!
Starting GuiServer using:
/usr/j2se/bin/java -cp /tmp/sapinst_exe.947.1230119416/JAR/instgui.jar:/tmp/sapinst_exe.947.1230119416/JAR/inqmyxml.jar -Djava.security.egd=file:/dev/urandom SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
load resource pool /instcd/master/IM_SOLARIS_X86_64/resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host recovery, port 21200 to continue with the installation
guiengine: login in process.
iauxsysex.c:317: child /tmp/sapinst_exe.947.1230119416/sapinst (pid 948) has crashed. Executable directory is /tmp/sapinst_exe.947.1230119416. Contact Support.
iaextract.c:814: child has signaled an exec error. Keeping directory /tmp/sapinst_exe.947.1230119416
bash-3.00# ls
Solution :
SAP for Solaris 10 on x64 requires at least Solaris 10 Update 1 (= Solaris 10 1/06).
Operating system patches recommended for Solaris 10 on x64
127112-05 SunOS 5.10_x86: kernel patch
120069-03 SunOS 5.10_x86: in.telnetd patch
119964-05 SunOS 5.10_x86: Shared library patch for C++_x86
120754-02 SunOS 5.10_x86: Microtasking libraries (libmtsk) patch
122033-04 SunOS 5.10_x86: Update timezones patch
===========================================================
How to start JSPM (java support package management)
===========================================================
Starting JSPM
Prerequisites
● The J2EE Engine and the SDM server are running.
● No application is connected to the SDM server. There can be only one connection to the SDM server at a time. For example, if you have an open SDM GUI, you must disconnect from the SDM server. Otherwise, the JSPM cannot connect to the SDM server to apply support packages and to deploy software components.
● Directories and files have not been deleted, renamed, or created in the following directories and their subdirectories: /usr/sap/<SID>/SYS/exe and /usr/sap/<SID>/SYS/profile. Otherwise, JSPM cannot detect the kernel and the system profiles, and cannot be started. If a backup of the kernel and the system profiles has been required, it has been created in a different directory.
● You have logged on to the operating system as a <SID>adm user. If you have not done this, you must switch to it before starting to use JSPM. Fore more information, see below.
● If your system is an IBM eServer iSeries:
○ You have logged on as a <SID>adm or a <SID>ofr user.
○ The release of JSPM is not lower than SAP NetWeaver 7.0 SPS06.
○ If you have to deploy JSPM as of SAP NetWeaver 7.0 SPS06, the go and StartGui scripts have been downloaded. For more information, see SAP Note 885063.
...
Switching to <SID>adm user
For Windows OS
You can do this in two ways.
With menu options
1. Open Start ® Programs ®Accessories
2. Click with the secondary mouse button on the Command Prompt icon.
3. From the pop-up menu, choose Run As.
4. Choose <SID>adm user.
5. Start JSPM from the new console.
With runas command
Use the following command line:
runas /profile /user:<domain or host><sid>adm <full path to JSPMgo.bat>
runas /profile /user:%COMPUTERNAME%j70adm D:usrsapJ70JC03j2eeJSPMgo.bat
For UNIX OS
1. Use the following command:
su - <sid>adm
2. Start JSPM.
Starting JSPM on Any Operating System
1. In the file system, go to the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM directory.
Depending on the system, the name of the central instance has the following syntax:
● For a standalone system – JC<xx>
● For an add-on system – DVEBMGS<xx>, where xx is the number of the central instance.
2. To start JSPM, run the go script file.
In this step you can specify a temporary inbox directory. SeeDetecting and Changing the Global EPS Inbox Directory.
3. Enter your password for the SDM and choose Log On.
If you enter an incorrect password three times in a row, the SDM server will be stopped. You must start it and log on to the JSPM again. For more information about starting the SDM server, see Starting and Stopping the Software Deployment Manager.
Starting JSPM on an IBM eServer iSeries System
...
1. To prevent JSPM from automatically starting its GUI, in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/param/jspm_config.txt file, change the /dialog/SDTServerConnection/SDTGui/launch property from true to false.
2. Run the go script on the IBM eServer iSeries host using the following OS/400 command:
QSH CMD('/usr/sap/<SID>/<Central instance name>/j2ee/JSPM/go').
3. To start the JSPM GUI, from the mounted /usr/sap/<SID>/<Central instance name>/j2ee/JSPMdirectory, run the StartGui script.
The JSPM GUI appears.
4. In the Host field, enter the target IBM eServer iSeries host.
5. Enter your password for the SDM and choose Log On.
Prerequisites
● The J2EE Engine and the SDM server are running.
● No application is connected to the SDM server. There can be only one connection to the SDM server at a time. For example, if you have an open SDM GUI, you must disconnect from the SDM server. Otherwise, the JSPM cannot connect to the SDM server to apply support packages and to deploy software components.
● Directories and files have not been deleted, renamed, or created in the following directories and their subdirectories: /usr/sap/<SID>/SYS/exe and /usr/sap/<SID>/SYS/profile. Otherwise, JSPM cannot detect the kernel and the system profiles, and cannot be started. If a backup of the kernel and the system profiles has been required, it has been created in a different directory.
● You have logged on to the operating system as a <SID>adm user. If you have not done this, you must switch to it before starting to use JSPM. Fore more information, see below.
● If your system is an IBM eServer iSeries:
○ You have logged on as a <SID>adm or a <SID>ofr user.
○ The release of JSPM is not lower than SAP NetWeaver 7.0 SPS06.
○ If you have to deploy JSPM as of SAP NetWeaver 7.0 SPS06, the go and StartGui scripts have been downloaded. For more information, see SAP Note 885063.
...
Switching to <SID>adm user
For Windows OS
You can do this in two ways.
With menu options
1. Open Start ® Programs ®Accessories
2. Click with the secondary mouse button on the Command Prompt icon.
3. From the pop-up menu, choose Run As.
4. Choose <SID>adm user.
5. Start JSPM from the new console.
With runas command
Use the following command line:
runas /profile /user:<domain or host><sid>adm <full path to JSPMgo.bat>
runas /profile /user:%COMPUTERNAME%j70adm D:usrsapJ70JC03j2eeJSPMgo.bat
For UNIX OS
1. Use the following command:
su - <sid>adm
2. Start JSPM.
Starting JSPM on Any Operating System
1. In the file system, go to the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM directory.
Depending on the system, the name of the central instance has the following syntax:
● For a standalone system – JC<xx>
● For an add-on system – DVEBMGS<xx>, where xx is the number of the central instance.
2. To start JSPM, run the go script file.
In this step you can specify a temporary inbox directory. SeeDetecting and Changing the Global EPS Inbox Directory.
3. Enter your password for the SDM and choose Log On.
If you enter an incorrect password three times in a row, the SDM server will be stopped. You must start it and log on to the JSPM again. For more information about starting the SDM server, see Starting and Stopping the Software Deployment Manager.
Starting JSPM on an IBM eServer iSeries System
...
1. To prevent JSPM from automatically starting its GUI, in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/param/jspm_config.txt file, change the /dialog/SDTServerConnection/SDTGui/launch property from true to false.
2. Run the go script on the IBM eServer iSeries host using the following OS/400 command:
QSH CMD('/usr/sap/<SID>/<Central instance name>/j2ee/JSPM/go').
3. To start the JSPM GUI, from the mounted /usr/sap/<SID>/<Central instance name>/j2ee/JSPMdirectory, run the StartGui script.
The JSPM GUI appears.
4. In the Host field, enter the target IBM eServer iSeries host.
5. Enter your password for the SDM and choose Log On.
===========================================================
关于SAP中的Check and update optimizer statistics任务(Oracle CBO在SAP中的应用)
===========================================================
在SAP 中使用DB13安排系统后台任务时，有Check and update optimizer statistics这样一个任务，SAP的NOTE上推荐是一个星期执行一次（note:132861）;
实际上这个就是ORACLE的CBO（Cost Based Optimizer基于成本的优化器），使用SQL语句：select job_name,program_name,last_start_date,next_run_date,comments from dba_scheduler_jobs;可以查询到ORACLE本身对这个任务的定义，许多朋友说但在Oracle 10.2.0.2和10.2.0.3的版本上这个JOB自动执行都会有些问题，所以还是不要用Oracle自动的模式，从SAP的DB13中就可以定义这个任务；这对整个系统的性能会有很大的帮助；
进入事务代码DB14，再选择Function IDs查询sta的结果，就是这个Update optimizer statistics的执行纪录；
===========================================================
Exception CX_SFW_EXISTENCE when import SAPKB70015&SAPKB70016
===========================================================
When I import BASIS support package SAPKB70015&SAPKB70016 together,meet the error "Runtime Error UNCAUGHT_EXCEPTION"
"Exception CX_SFW_EXISTENCE";
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SFW_EXISTENCE', was not caught in
procedure "INIT" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Object SFBS EA-DFP does not exist
Solution:
please refer sap note 1160050.
create the report used Transaction SE38 and execute it.
REPORT ZBFSDEL.
tables:
sfw_bs,
sfw_active_b1.
* if Parameter Start = 'X' delete entry
parameters: start type char1.
* Delete entry from table sfw_bs
select * from sfw_bs where bset = 'EA-DFP'.
if sy-subrc is initial and start = 'X'.
delete from sfw_bs where bset = 'EA-DFP'.
if sy-subrc is initial.
write:/ 'Business Function Set EA-DFP deleted'.
endif.
endif.
endselect.
* Delete entry from table sfw_active_b1
select * from sfw_active_b1 where bset = 'EA-DFP'.
if sy-subrc is initial and start = 'X'.
delete from sfw_active_b1 where bset = 'EA-DFP'.
if sy-subrc is initial.
write:/ 'Active Business Function Set EA-DFP deleted'.
endif.
endif.
endselect.
===========================================================
Oracle issue note: ORA-00600
===========================================================
HD Env: SUN SPARC 64bit
DB Env: Oracle 10.2.0.2
Message in alertPRD.log
ORA-00600: internal error code, arguments: [kdtdelrow-2], [208], [208], [], [], [], [], []
Errors in file /oracle/PRD/saptrace/usertrace/prd_ora_2248.trc:
Solve solution:
Refer SAP Note: 1001930 - ORA-600 [kcbnew_3] / [KCBZ_CHECK_OBJD_TYP_3] / [kdtdelrow-2]
The solution to Oracle Bug 5376783 is contained in the kts mergefix 5667736.
See SAPNet Note 1002062 for information on the availability of patches.
===========================================================
5 days basis training
===========================================================
This week,I had a training about SAP BASIS,following is the course list;
ADM100 SAP Web AS Administration I;
ADM102 SAP Web AS Administration Ⅱ;
ADM505 Database Administration Oracle I;
ADM506 Database Administration Oracle II;
===========================================================
SAP Cannot logon issue
===========================================================
Last weekend,I installed the DR system, There is a SAP DEV system on this server exsit already;
Hard env: SUN M4000 CPU:4*4 Memory:32GB
OS env: Solaris 64bit on SPARC
Oracle Version: 10g Realse 2
SAP Version: MySAP ERP 2005 SR2
The two system used different file system;(e.g. /sapmnt;/usr/sap;/usr/sap/trans;/oracle),and there are used different resource control item;
DR system was installed all right;Then I umount the file system for DR system, and mount the file system for DEV system,and startup ORACLE and SAP DEV system;
At this time, I cannot logon to the DEV system;By many try hard, at last,used the tool("sappfpar check") check the profile,and modify the wrong parameter,and the problem was solved;following is the result for SAPPFPAR:
erpdev:devadm 19% sappfpar check pf=DEV_DVEBMGS06_erpdev
================================================================================
== Checking profile: DEV_DVEBMGS06_erpdev
================================================================================
***WARNING: Unexpected parameter: j2ee/dbhost =erpdev
***WARNING: Unexpected parameter: j2ee/dbname =DEV
***WARNING: Unexpected parameter: j2ee/dbtype =ora
***WARNING: Unexpected parameter: jstartup/vm/home =/usr/j2se
***ERROR: Size of shared memory pool 10 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 10
with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 10
with parameter: ipc/shm_psize_10 =178000000
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
with parameter: ipc/shm_psize_40 =238000000
Shared memory disposition overview
================================================================
Shared memory pools
Key: 10 Pool
Size configured.....: 124000000 ( 118.3 MB)
Size min. estimated.: 175451010 ( 167.3 MB)
Advised Size........: 178000000 ( 169.8 MB)
Key: 40 Pool for database buffers
Size configured.....: 224000000 ( 213.6 MB)
Size min. estimated.: 235055040 ( 224.2 MB)
Advised Size........: 238000000 ( 227.0 MB)
Shared memories inside of pool 10
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.
Key: 13 Size: 60500000 ( 57.7 MB) Alert Area
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring
Key: 17 Size: 2672386 ( 2.5 MB) Roll administration
Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.
Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer
Key: 54 Size: 51453952 ( 49.1 MB) Export/Import buffer
Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist
Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem
Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset
hared memories inside of pool 40
Key: 42 Size: 35392992 ( 33.8 MB) DB TTAB buffer
Key: 43 Size: 101014392 ( 96.3 MB) DB FTAB buffer
Key: 44 Size: 21142392 ( 20.2 MB) DB IREC buffer
Key: 45 Size: 11926392 ( 11.4 MB) DB short nametab buffer
Key: 46 Size: 20480 ( 0.0 MB) DB sync table
Key: 47 Size: 12289024 ( 11.7 MB) DB CUA buffer
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer
Key: 49 Size: 2968344 ( 2.8 MB) Spool admin (SpoolWP+DiaWP)
hared memories outside of pools
Key: 1 Size: 2500 ( 0.0 MB) System administration
Key: 2 Size: 6021400 ( 5.7 MB) Disp. administration tables
Key: 3 Size: 13714400 ( 13.1 MB) Disp. communication areas
Key: 4 Size: 517048 ( 0.5 MB) statistic area
Key: 6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key: 7 Size: 14838 ( 0.0 MB) Update task administration
Key: 8 Size: 67108964 ( 64.0 MB) Paging buffer
Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer
Key: 14 Size: 4400000 ( 4.2 MB) Presentation buffer
Key: 18 Size: 917604 ( 0.9 MB) Paging adminitration
Key: 19 Size: 30000000 ( 28.6 MB) Table-buffer
Key: 30 Size: 26624 ( 0.0 MB) Taskhandler runtime admin.
Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue
Key: 33 Size: 10240000 ( 9.8 MB) Table buffer, part.buffering
Key: 34 Size: 16777216 ( 16.0 MB) Enqueue table
Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes
Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.
Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0
Key: 58900106 Size: 4096 ( 0.0 MB) SCSA area
Nr of operating system shared memory segments: 24
Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....: 24
System-imposed number of shared memories.: 252
Shared memory segment size required min..: 1064960000 (1015.6 MB)
System-imposed maximum segment size......: 86973087744 (82944.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 1804.3 MB
..in pool 10 118.3 MB, 141% used !!
..in pool 40 213.6 MB, 104% used !!
..not in pool: 1405.7 MB
Processes........................: 324.2 MB
Extended Memory .................: 8184.0 MB
------------------------------------------------
Total, minimum requirement.......: 10312.5 MB
Process local heaps, worst case..: 1908.0 MB
Total, worst case requirement....: 12220.5 MB
Errors detected..................: 2
Warnings detected................: 4
erpdev:devadm 20%
===========================================================
list of sap kernel command and description
===========================================================
List of interesting SAP Executables in alphabetical order:
• car - The Compression Tool of SAP for nearly all delivered files and executables. CAR is the name for old releases and the SAPCAR is the name as of 4.6D. It works a bit similar to WinZip.
• dipgntab - Activation and adjustment of the nametabs with the ABAP Dictionary.
• dw - disp+work - "Dispatcher & Workprocess" - "The complete Kernel" - Here the complete ABAP is processed ...
• niping - Small Client and Server in order to test the saprouter internally with the NI-Protocol (SAP Network Interface).
• lib_dbsl - The Database-Shared Library for the kernel programs (as of 4.5A).
• librfc - The RFC (Remote Function Call) Library, that is available for any platform to develop and run a RFC Server or RFC Client.
• ntscmgr.exe - ntscmgr - the tool for installing the SAProuter as service. It is part of every Windows SAP Kernel. As it has no known errors, it is not necessary, to patch it. Just use ntscmgr.exe from your existing windows kernel.
• r3check - This is a tool, that can Cluster-Tables for errors.
• r3ldctl - The tool for exporting all table structures to the file system during a OS/DB-Migration.
• r3load - The table import & export tool of SAP during Installation, Upgrade and Migration.
• r3setup - The Installation (and Migration) Tool for all SAP systems up to Release 6.10.
• r3szchk - The tool for determing the sizes of the different tables in the target database during the import in an OS/DB-Migration.
• r3trans - This is the tool, that does the real work for tp. tp controls the import and export of changes and r3trans does them using scripts, that were generated from tp.
• r3up - The tool that controls the Upgrade (Moving to higher SAP Releases) of an SAP System.
• rfcexec - The tool to start other programs from within SAP (ABAP) on the OS level via the gateway on any other (or the same) server.
• rfcoscol - Similar to saposcol. It is needed, when no SAP instance is running on the Database Server.
• sapcar - The Compression Tool of SAP for nearly all delivered files and executables. It works a bit similar to WinZip.
• sapevt - This program is able to trigger events within the SAP system. The tp tool uses this feature. It can be used as trigger for self-written interfaces as well.
• sapftp - FTP Client, that can be used from within the SAP system (from ABAP) to communicate with other FTP servers.
• saphttp - HTTP Client, that can be used from within the SAP system (from ABAP) to communicate with other HTTP servers - e.g. for interfaces.
• sapinst - The Installation (and Migration) Tool for all SAP systems as of Release 6.20.
• saplicense - The Tool for the installation of a new SAP License. This is needed when the license expires e.g. because of a hardware change.
• saposcol - The SAP Interface to the Operating System for Performance Data. The Operating System Collector collects CPU Usage, Disk Performance, Paging etc.
• sappad - Very nice & small Editor a lot better than notepad. It handles LF and CR/LF correctly as well.
• sappfpar - This tool can be used for checking the profiles after changes and before restarting the SAP system.
• saprouter - The program for the Router Connection from customers to SAP and vice versa.
• sapxpg - The tool for starting OS commands from within SAP Systems.
• sapwebdisp - The SAP Web dispatcher is used for load balancing for an setting up an SAP Internet scenario. It is the only application, that needs to be located in the DMZ. Everything "behind" this can (and should) be located in your intranet. So, only one port on one IP adress needs to be opened to internet and the SAP Web dispatcher can handle the traffic with the different SAP instances.
• startrfc - The tool is a very easy SAP command line interface to start all of the implemented function modules of SAP systems.
• tp - "The" Transport Tool. This program coordinates the complete import and export of program and table changes made within the SAP system in order to transport them through the complete System Landscape.
• car - The Compression Tool of SAP for nearly all delivered files and executables. CAR is the name for old releases and the SAPCAR is the name as of 4.6D. It works a bit similar to WinZip.
• dipgntab - Activation and adjustment of the nametabs with the ABAP Dictionary.
• dw - disp+work - "Dispatcher & Workprocess" - "The complete Kernel" - Here the complete ABAP is processed ...
• niping - Small Client and Server in order to test the saprouter internally with the NI-Protocol (SAP Network Interface).
• lib_dbsl - The Database-Shared Library for the kernel programs (as of 4.5A).
• librfc - The RFC (Remote Function Call) Library, that is available for any platform to develop and run a RFC Server or RFC Client.
• ntscmgr.exe - ntscmgr - the tool for installing the SAProuter as service. It is part of every Windows SAP Kernel. As it has no known errors, it is not necessary, to patch it. Just use ntscmgr.exe from your existing windows kernel.
• r3check - This is a tool, that can Cluster-Tables for errors.
• r3ldctl - The tool for exporting all table structures to the file system during a OS/DB-Migration.
• r3load - The table import & export tool of SAP during Installation, Upgrade and Migration.
• r3setup - The Installation (and Migration) Tool for all SAP systems up to Release 6.10.
• r3szchk - The tool for determing the sizes of the different tables in the target database during the import in an OS/DB-Migration.
• r3trans - This is the tool, that does the real work for tp. tp controls the import and export of changes and r3trans does them using scripts, that were generated from tp.
• r3up - The tool that controls the Upgrade (Moving to higher SAP Releases) of an SAP System.
• rfcexec - The tool to start other programs from within SAP (ABAP) on the OS level via the gateway on any other (or the same) server.
• rfcoscol - Similar to saposcol. It is needed, when no SAP instance is running on the Database Server.
• sapcar - The Compression Tool of SAP for nearly all delivered files and executables. It works a bit similar to WinZip.
• sapevt - This program is able to trigger events within the SAP system. The tp tool uses this feature. It can be used as trigger for self-written interfaces as well.
• sapftp - FTP Client, that can be used from within the SAP system (from ABAP) to communicate with other FTP servers.
• saphttp - HTTP Client, that can be used from within the SAP system (from ABAP) to communicate with other HTTP servers - e.g. for interfaces.
• sapinst - The Installation (and Migration) Tool for all SAP systems as of Release 6.20.
• saplicense - The Tool for the installation of a new SAP License. This is needed when the license expires e.g. because of a hardware change.
• saposcol - The SAP Interface to the Operating System for Performance Data. The Operating System Collector collects CPU Usage, Disk Performance, Paging etc.
• sappad - Very nice & small Editor a lot better than notepad. It handles LF and CR/LF correctly as well.
• sappfpar - This tool can be used for checking the profiles after changes and before restarting the SAP system.
• saprouter - The program for the Router Connection from customers to SAP and vice versa.
• sapxpg - The tool for starting OS commands from within SAP Systems.
• sapwebdisp - The SAP Web dispatcher is used for load balancing for an setting up an SAP Internet scenario. It is the only application, that needs to be located in the DMZ. Everything "behind" this can (and should) be located in your intranet. So, only one port on one IP adress needs to be opened to internet and the SAP Web dispatcher can handle the traffic with the different SAP instances.
• startrfc - The tool is a very easy SAP command line interface to start all of the implemented function modules of SAP systems.
• tp - "The" Transport Tool. This program coordinates the complete import and export of program and table changes made within the SAP system in order to transport them through the complete System Landscape.
