SeimensNotes101 151

$GGLWLRQDO,QIRUPDWLRQ
l 6$3/LEUDU\
l KWWSKHOSVDSFRP
l KWWSVHUYLFHVDSFRP
l 6$31RWHV
SAPDOCCD.INI - Description
SAPDOCCD.LOG - Description
Composite Note: Extended help and SAP Library
Settings variants for online help
Common errors for SAP Library settings
 SAP AG 2002
© SAP AG ADM100 6-11
Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

$FFHVVWR+HOS6XPPDU\
<RXDUHQRZDEOHWR
l 6HWXSDFFHVVWRWKHRQOLQHGRFXPHQWDWLRQ
l 8VHWKHLQIRUPDWLRQSURYLGHGE\WKH6$36HUYLFH
0DUNHWSODFH
 SAP AG 2002

$FFHVVWR+HOS([HUFLVHV
These exercises will familiarize you with using transaction 65 to configure help
access, and the use of selected services from the SAP Service Marketplace. As there
may not be a local copy of the online documentation of the SAP Web Application
Server 6.10 in the training center that you are using, the first three exercises are
optional.
1R ([HUFLVHV
3DUW2SWLRQDO6HWWLQJXSDFFHVVWRRQOLQHGRFXPHQWDWLRQ
8QVXFFHVVIXOFDOORIWKHRQOLQHGRFXPHQWDWLRQ
1.1 Start the call for the online documentation. This should fail.
6HWWLQJVLQWUDQVDFWLRQ65
2.1 In your system, call the cross-client maintenance of the online documentation
access. Maintain the settings for the help type +WPO+HOS)LOH in accordance
with the example values in the training manual (see graphic showing
7UDQVDFWLRQ65([DPSOH).
Note that you cannot specify a correct path to the online documentation files.
The online documentation is not accessible for the servers in the training
environment for administrative training courses. Therefore, the settings in the
VDSGRFFGLQL file on your frontend take precedence, once you have made
settings in 65.
6XFFHVVIXOFDOORIWKHRQOLQHGRFXPHQWDWLRQ
3.1 Start the call for the online documentation. Although the settings from 65
do not point to accessible online documentation, the call should still succeed,
as there is a local VDSGRFFGLQL file on your frontend. This links to help that is
accessible for your frontend. If there is no SAP Web AS 6.10 online
documentation available in the training center that you are attending, you can
use the Internet-based help for the rest of this training course, under
http://help.sap.com.
3DUW8VLQJWKH6$36HUYLFH0DUNHWSODFHVHUYLFHV
&RQQHFWWRWKH6$36HUYLFH0DUNHWSODFH
4.1 Call the URL for the SAP Service Marketplace: KWWSVHUYLFHVDSFRP
4.2 Either use your own “S user” (as an SAP customer, you have a number of
this type), or get the details for a dummy user from the instructor.
)XQFWLRQVRIWKH6$36HUYLFH0DUNHWSODFH
5.1 Call the Quick Link QRWHV to access SAP Note 333584. During the rest of the
course, you can always display SAP Notes on the SAP Service Marketplace.

$FFHVVWR+HOS6ROXWLRQV
These exercises will familiarize you with using transaction 65 to configure help
access, and the use of selected services from the SAP Service Marketplace. As there
may not be a local copy of the online documentation of the SAP Web Application
Server 6.10 in the training center that you are using, the first three exercises are
optional.
1R 6ROXWLRQV
3DUW2SWLRQDO6HWWLQJXSDFFHVVWRRQOLQHGRFXPHQWDWLRQ
8QVXFFHVVIXOFDOORIWKHRQOLQHGRFXPHQWDWLRQ
1.1 6WDUWWKHFDOOIRUWKHRQOLQHGRFXPHQWDWLRQ7KLVVKRXOGIDLO
Choose +HOS→6$3/LEUDU\. The system displays the message 1R
GRFXPHQWDWLRQDYDLODEOH.
6HWWLQJVLQWUDQVDFWLRQ65
2.1 ,Q\RXUV\VWHPFDOOWKHFURVVFOLHQWPDLQWHQDQFHRIWKHRQOLQH
GRFXPHQWDWLRQDFFHVV0DLQWDLQWKHVHWWLQJVIRUWKHKHOSW\SH
+WPO+HOS)LOHLQDFFRUGDQFHZLWKWKHH[DPSOHYDOXHVLQWKHWUDLQLQJ
PDQXDOVHHJUDSKLFVKRZLQJ7UDQVDFWLRQ65([DPSOH
1RWHWKDW\RXFDQQRWVSHFLI\DFRUUHFWSDWKWRWKHRQOLQHGRFXPHQWDWLRQ
ILOHV7KHRQOLQHGRFXPHQWDWLRQLVQRWDFFHVVLEOHIRUWKHVHUYHUVLQWKH
WUDLQLQJHQYLURQPHQWIRUDGPLQLVWUDWLYHWUDLQLQJFRXUVHV7KHUHIRUHWKH
VHWWLQJVLQWKHVDSGRFFGLQLILOHRQ\RXUIURQWHQGWDNHSUHFHGHQFHRQFH
\RXKDYHPDGHVHWWLQJVLQ65
Start transaction 65or follow the path listed in the course manual. Then
enter the example settings on the +WPO+HOS)LOHtab page listed in the user
manual.
6XFFHVVIXOFDOORIWKHRQOLQHGRFXPHQWDWLRQ
3.1 6WDUWWKHFDOOIRUWKHRQOLQHGRFXPHQWDWLRQ$OWKRXJKWKHVHWWLQJVIURP
65GRQRWSRLQWWRDFFHVVLEOHRQOLQHGRFXPHQWDWLRQWKHFDOOVKRXOG
VWLOOVXFFHHGDVWKHUHLVDORFDOVDSGRFFGLQLILOHRQ\RXUIURQWHQG7KLV
OLQNVWRKHOSWKDWLVDFFHVVLEOHIRU\RXUIURQWHQG,IWKHUHLVQR6$3:HE
$6RQOLQHGRFXPHQWDWLRQDYDLODEOHLQWKHWUDLQLQJFHQWHUWKDW\RX
DUHDWWHQGLQJ\RXFDQXVHWKH,QWHUQHWEDVHGKHOSIRUWKHUHVWRIWKLV
WUDLQLQJFRXUVHXQGHUKWWSKHOSVDSFRP
Follow the exercise instructions.
3DUW8VLQJWKH6$36HUYLFH0DUNHWSODFHVHUYLFHV
&RQQHFWWRWKH6$36HUYLFH0DUNHWSODFH
4.1 &DOOWKH85/IRUWKH6$36HUYLFH0DUNHWSODFH
KWWSVHUYLFHVDSFRP
Start the browser of your frontend and user the specified address. Confirm
any dialog boxes that the system displays.

4.2 (LWKHUXVH\RXURZQ³6XVHU´DVDQ6$3FXVWRPHU\RXKDYHDQXPEHU
RIWKLVW\SHRUJHWWKHGHWDLOVIRUDGXPP\XVHUIURPWKHLQVWUXFWRU
Choose (QWHU1RZ on the initial screen of the SAP Service Marketplace to
display the username and password query.
)XQFWLRQVRIWKH6$36HUYLFH0DUNHWSODFH
5.1 &DOOWKH4XLFN/LQNQRWHVWRDFFHVV6$31RWH'XULQJWKHUHVW
RIWKHFRXUVH\RXFDQDOZD\VGLVSOD\6$31RWHVRQWKH6$36HUYLFH
0DUNHWSODFH
After successfully logging on to the SAP Service Marketplace, replace
everything that follows https://<Host>.sap-ag.de/ in the address (in
the address line of your browser), such as ORJLQ, with QRWHV. In this way you
access a search page for SAP Notes. Select the relevant note, and display it.

%DVLFVRI'DWDEDVH$GPLQLVWUDWLRQ
,QWURGXFWLRQWRV\VWHPFRQILJXUDWLRQ
7HFKQRORJ\FRPSRQHQWVIRU,QWHUQHWFRQQHFWLRQ
$FFHVVWR+HOS
%DVLFVRIGDWDEDVHDGPLQLVWUDWLRQ
6\VWHPODQGVFDSHVDQGWUDQVSRUWUHTXHVWV
6XSSRUW3DFNDJHVDQG,QGXVWU\6ROXWLRQV
6FKHGXOLQJEDFNJURXQGWDVNV
3ULQWLQJIURP6$3V\VWHPV
 SAP AG 2002

%DVLFVRI'DWDEDVH$GPLQLVWUDWLRQ
&RQWHQWV
l +RZGDWDEDVHVVWRUHWKHLUGDWD
l +RZGDWDEDFNXSVIURP6$3V\VWHPVFDQEHSHUIRUPHG
2EMHFWLYHV
$WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWR
l %DFNXSWKHGDWDEDVH
l 'HWHUPLQHZKHWKHU\RXUGDWDEDVHEDFNXSVKDYHEHHQ
VXFFHVVIXOO\SHUIRUPHG
 SAP AG 2002

'DWDEDVH&RQFHSWV
'DWDEDVH%XIIHULQ0DLQ0HPRU\
' 9 ( % 6
'DWDEDVH3URFHVVHV
/RJ%XIIHU
6SHFLDO
'%3URFHVVHV
/RJ)LOH 6WUXFWXUH'DWD

2QJRLQJ/RJ,QIRUPDWLRQ 'DWD)LOH 'DWD)LOHQ

 SAP AG 2002
n A database management system (DBMS) includes database processes, a buffer in the main memory,
data files that contain the data, and log files, in which changes to the data are logged.
n At the start of an SAP system, all work processes are linked to a database process. SAP work
processes pass database queries to their dedicated database processes, which perform the query on
the database.
n The data is stored in the data files. Access to the data always takes place using the buffer in main
memory.
n The special database processes are responsible for the exchange of data between the buffer and the
data files. During this exchange, the data is always read and written in complete pages (which
usually contain several data records).
n If changes are made to the data, these are logged in the buffer. The buffer contains the status changes
of the database. Only the changes, and not the complete pages, are logged in the log buffer. The
entries are written from the log buffer to the log file. There can be one or more than one log file,
depending on the database. For every database, there is a mechanism that backs up the log
information from the log file to other files or directly to a backup medium. This ensures that the log
file does not become too large. You should mirror the log file. Some databases provide special
software mirrors to allow you to do this.
&DXWLRQ This mechanism cannot be deactivated, as otherwise the status changes could be lost. This
would mean that there was a threat of data loss if a hard disk crash occurred.
n A database always also includes structure data that contains essential information for the database,
such as the number of data files, and so on.

%DFN8SRIWKH'DWDDQG/RJ,QIRUPDWLRQ
6WUXFWXUH'DWD

2QJRLQJ/RJ,QIRUPDWLRQ 'DWD)LOH 'DWD)LOHQ

 SAP AG 2002
n A backup concept for the database always includes the regular backup of the data files, the structure
data, and also the log information.
n The backup of the data files and the log information is performed in different steps.
All data files and structure data are backed up in one step.
In another step, the ongoing log information (this may include the structure data) is backed up
separately.
n You can schedule both of these steps in the SAP system (except for AS400) as regular actions in the
database planning calendar (transaction '%).

6FHQDULRV'DWDEDVH5HVWRUDWLRQ

W W

 SAP AG 2002
n Selected scenarios for restoring a database in the case of the loss of data files, such as through a disk
crash.
n Resetting the database (ZLWKGDWDORVV):
If a disk crash occurs at a point between t1 and t2,all data from the data backup t1 is imported. If no
further action is taken, all data changes that were made after t1 are lost.
n Restoring the database (ZLWKRXWGDWDORVV):
All data from data backup t1 is imported. Some databases allow you to import only the data files that
are missing. In this case, the system follows all log information written since t1 (22, 23, and so on).
As a final step, the log file is followed. This means that all data is now in the same state again as at
the point when the disk crash occurred. Only if all log information since the data backup is available,
with no gaps, will there be no data loss.

6FHQDULRV'DWDEDVH5HVWRUDWLRQ

W W W W W

 SAP AG 2002
n Storing the data and log info backups:

The backed-up log information is deleted at operating system level so that no disk space problems
occur. If a disk crash occurs at time t5 and a backup medium for the backup t3 is defective, an earlier
data backup (in this case, t1) must be used. To restore the database without data loss, it is absolutely
necessary to have DOOORJLQIREDFNXSV (in this case: t2 and t4) since the data backup t1 and the log
information as of 28. It is therefore necessary to keep older data and log info backups.
n Some databases also require log information to be able to reset the database. You should ensure that
you perform GDWDDQGORJEDFNXSV regularly.

5HFRPPHQGHG%DFNXS&\FOH
9HUILFDWLRQ
RI%DFNXSV
%DFNXSRI'DWD
/RJ,QIRUPDWLRQ
GD\V %DFNXSRI'DWD
/RJ,QIRUPDWLRQ

 SAP AG 2002
n The duration of a backup cycle should be 28 days. The backup media for the data and log info
backups is overwritten after 28 days, at the earliest.
n Perform complete GDWD backups every day. Some databases offer the option of performing
differential or incremental data backups that do QRW backup the complete data of the database (these
data backups are described in the following as partial data backups). If you use a partial data backup
as your daily backup, you must perform a complete data backup at least once a week. There must be
at least four complete data backups contained in the backup cycle.
n The log information should be backed up at least once a day. Always have two different backup
media containing the same information.
n Perform a data and log info backup with verification of the backup media at least once in the backup
cycle.

6FKHGXOLQJDQG0RQLWRULQJ'%%DFNXSV
57698 :;9<:9=?><@ ACBEDA DF>G;9H@ = D;9I*:9;JACKGLMJA :IONP:98 Q

!#"
$&%('*) + ,.-0/1#)2$3,%*1*4
\^]`_[a`bEcedf7g#h ] _`h #w E 7#w 3
R#D SGT U : SGV W= KP6 KT
R#D SGT U : SGV W= KP6 KT '%

R#D SGT U : SGV W= Schedule
S Action for Tu. 01.01.02
KPGX S K[7Y7[Z
i kjelnm oqp repkj`m s p
pk{^|~}
22:00:00 1 xzy
R#D SGT U : SGV W= S
tvu
KPGGX m w K[7Y7[Z
Complete data backup

Incremental data backup
Log backup
Check optimizer statistics
! "
 SAP AG 2002
n You can schedule and monitor regular database backups with transaction '% in the SAP system.
n Select the data backup procedure for each weekday (recommendation: the database-specific
procedure for complete data backup) and enter the repetition period (such as 1). Choose the start time
or immediate start.
n If a manual medium swap is required if you are using a local tape station, check which medium is
required for the next backup every day by choosing 9ROVQHHGHG, and insert this medium before the
start of the backup.
n Enter the log info backup for every weekday in the same way as the data backup.
n You can set the display of the planning calendar by choosing 3ODQQLQJ→&DOHQGDUGLVSOD\.
n Check every day whether your backups have been successfully completed. In the planning calendar,
a successful backup is displayed with green or yellow (with warnings) labeling. Red labeling
indicates an erroneous (and therefore unusable) backup. You can display additional information with
transaction '%.
n You can control and monitor the backups for your entire system landscape with the central planning
calendar (transaction '%&). The schedules are transferred to the remote systems using an RFC
connection.

'DWDEDVH0RQLWRULQJ2XWORRN
'D\ KKKK
%DFNXS á
$UFKLYHá
'DLO\0RQLWRULQJ
6WRUDJHPDQDJHPHQW
3HUIRUPDQFHPRQLWRULQJ
2SWLPL]HUVWDWLVWLFV
(UURUKDQGOLQJ
'DLO\WDVNV $XWRPDWLFSURFHVVHV
5HJXODUWDVNV
 SAP AG 2002
n In addition to the daily monitoring of the database backups, there are a number of other checks that
must be made regularly, depending on the database. Some of these can be scheduled using the DB
planning calendar (transaction '%).
n For example, these checks can be:
é Growth of the database (such as free space).
é Generation of statistical data for the data record accesses performance.
é Checks for general database problems or errors.
n For more information about these checks, contact your database vendor, see the technical literature
and documentation, contact an SAP consultant, or attend one of our administration courses for the
database that you are using.

%DVLFVRI'DWDEDVH$GPLQLVWUDWLRQ6XPPDU\
<RXDUHQRZDEOHWR
l %DFNXSWKHGDWDEDVH
l 'HWHUPLQHZKHWKHU\RXUGDWDEDVHEDFNXSVKDYHEHHQ
VXFFHVVIXOO\SHUIRUPHG
 SAP AG 2002

'DWDEDVH$GPLQLVWUDWLRQ([HUFLVHV
This unit familiarizes you with some basic database backup and database
maintenance activities. The tool used for this is transaction '%. The transaction is
available with appropriate functions for every database supported by SAP. For the
SAP DB database, SAP Note 431508 was considered in the preparation of this
training course.
Caution: The runtime estimates in the exercises apply only for the training systems
used here. In production systems, the runtimes may be much higher.
1R ([HUFLVHV
3DUW6WDUWWUDQVDFWLRQ'%
&DOOLQJ'%LQDV\VWHPZLWKQRSUHYLRXV'%DFWLYLWLHV
1.1 &DOOWUDQVDFWLRQ'%&RQVLGHUWKHHUURUPHVVDJHGLVSOD\HG$WWHPSW
WRUHPRYHWKHFDXVHRIWKLVHUURU
&KHFNWKHVHWWLQJVLQWUDQVDFWLRQ'%
2.1 'LVSOD\DQRYHUYLHZRIWKHXWLOL]HGEDFNXSPHGLD,I\RXKDYHSHUIRUPHG
DVXFFHVVIXOEDFNXSZKDWPXVW\RXWKHQFRQVLGHUEHIRUH\RXFDQVWDUW
WKHQH[WEDFNXS+LQW2YHUZULWDELOLW\"
6FKHGXOHDQGSHUIRUPDEDFNXSZLWKFKHFNSRLQW
3.1 6FKHGXOHD&RPSOHWHGDWDEDFNXSZLWKFKHFNSRLQWLQWUDQVDFWLRQ'%
8VHWKHGHYLFH)25'$7$DVWKHEDFNXSGHYLFH,IWKHEDFNXSVWDUWHG
VXFFHVVIXOO\WKHODEHOIRUWKHEDFNXSUXQLV\HOORZSURFHVVLVUXQQLQJ
7KHEDFNXSUHTXLUHVDWOHDVWPLQXWHV
<RXFDQREVHUYHWKHJURZWKRIWKHEDFNXSILOHDWRSHUDWLQJV\VWHP
OHYHORUWDNHWKHRSSRUWXQLW\IRUDEUHDN
2SWLRQDO2WKHUUHTXLUHGDFWLRQVLQ'%
%DFNXSORJLQIRUPDWLRQ
4.1 6FKHGXOHD/RJ%DFNXSLQWUDQVDFWLRQ'%8VHWKHGHYLFH)25/2*
DVWKHEDFNXSGHYLFH7KHEDFNXSWHUPLQDWHVLPPHGLDWHO\$WWHPSWWR
GHWHUPLQHWKHFDXVHRIWKLVHUURUXVLQJWKHORJV
8SGDWLQJWKHVWDWLVWLFDOGDWD
5.1 &KHFNWKHH[LVWLQJRSWLPL]HUVWDWLVWLFV
Estimated runtime: 2 minutes
5.2 5HIUHVKWKHH[LVWLQJVWDWLVWLFDOGDWD
Estimated runtime: 20 seconds

'DWDEDVH$GPLQLVWUDWLRQ6ROXWLRQV
This unit familiarizes you with some basic database backup and database
maintenance activities. The tool used for this is transaction '%. The transaction is
available with appropriate functions for every database supported by SAP.
For the SAP DB database, SAP Note 431508 was considered in the preparation of
this training course.
Caution: The runtime estimates in the exercises apply only for the training systems
used here. In production systems, the runtimes may be much higher.
1R 6ROXWLRQV
3DUW6WDUWWUDQVDFWLRQ'%
&DOOLQJ'%LQDV\VWHPZLWKQRSUHYLRXV'%DFWLYLWLHV
1.1 &DOOWUDQVDFWLRQ'%&RQVLGHUWKHHUURUPHVVDJHGLVSOD\HG$WWHPSW
WRUHPRYHWKHFDXVHRIWKLVHUURU
The function '%0B*(7) failed for the command '%$+,67
'$7( . This message means that no historical data was found for
database activities. After the first action that is started using '%, this
message no longer appears.
&KHFNWKHVHWWLQJVLQWUDQVDFWLRQ'%
2.1 'LVSOD\DQRYHUYLHZRIWKHXWLOL]HGEDFNXSPHGLD,I\RXKDYHSHUIRUPHG
DVXFFHVVIXOEDFNXSZKDWPXVW\RXWKHQFRQVLGHUEHIRUH\RXFDQVWDUW
WKHQH[WEDFNXS+LQW2YHUZULWDELOLW\"
Choose %DFNXSPHGLD to obtain an overview of the available backup media.
As the name of the backup file is a fixed assignment, you can only start the
next backup once the existing backup file has been renamed or moved to a
different location, due to the setting 2YHUZULWDEOH 12.
6FKHGXOHDQGSHUIRUPDEDFNXSZLWKFKHFNSRLQW
3.1 6FKHGXOHD&RPSOHWHGDWDEDFNXSZLWKFKHFNSRLQWZLWKLPPHGLDWHVWDUW
LQWUDQVDFWLRQ'%8VHWKHGHYLFH)25'$7$DVWKHEDFNXSGHYLFH,I
WKHEDFNXSVWDUWHGVXFFHVVIXOO\WKHODEHOIRUWKHEDFNXSUXQLV\HOORZ
SURFHVVLVUXQQLQJ7KHEDFNXSUHTXLUHVDWOHDVWPLQXWHV
<RXFDQREVHUYHWKHJURZWKRIWKHEDFNXSILOHDWRSHUDWLQJV\VWHP
OHYHORUWDNHWKHRSSRUWXQLW\IRUDEUHDN
When you return from your break, the backup should be successfully
completed, and displayed as green in '%. If the label has not changed to
green, check the time of the last successful backup using transaction '%.
If the backup that you have just performed is shown here, there is a display
problem in '%.
2SWLRQDO2WKHUUHTXLUHGDFWLRQVLQ'%

%DFNXSORJLQIRUPDWLRQ
4.1 6FKHGXOHD/RJ%DFNXSLQWUDQVDFWLRQ'%8VHWKHGHYLFH)25/2*
DVWKHEDFNXSGHYLFH7KHEDFNXSWHUPLQDWHVLPPHGLDWHO\$WWHPSWWR
GHWHUPLQHWKHFDXVHRIWKLVHUURUXVLQJWKHORJV
The job or action log displays that the database is in a log mode that is invalid
for this backup type.
8SGDWLQJWKHVWDWLVWLFDOGDWD
5.1 &KHFNWKHH[LVWLQJRSWLPL]HUVWDWLVWLFV
Start the &KHFNRSWLPL]HUVWDWLVWLFV action with ,PPHGLDWHVWDUW using '%.
Check its success. Ensure that there are no other active '% actions. You
can display today’s '% actions, for example, by double clicking the 'D\
OLQH in the scheduling calendar. Estimated runtime: 2 minutes
5.2 5HIUHVKWKHH[LVWLQJVWDWLVWLFDOGDWD
You can refresh the existing statistical data by choosing 5HIUHVK
RSWLPL]HUVSDFHVWDWLVWLFV. This data is a requirement for an efficiently running
SAP system. Estimated runtime: 20 seconds (this is not a large task in this
training system).

6\VWHP/DQGVFDSHVDQG7UDQVSRUW5HTXHVWV
7HFKQRORJ\FRPSRQHQWVIRU,QWHUQHWFRQQHFWLRQ
$FFHVVWR+HOS
%DVLFVRIXVHUDGPLQLVWUDWLRQ
 SAP AG 2002

&RQWHQWV
l 'DWDVWUXFWXUHRIDQ6$3V\VWHP
l 7KHWKUHHV\VWHPODQGVFDSH
l 7UDQVSRUWV
l 0RGLILFDWLRQVDQGXSJUDGHSUREOHPV
2EMHFWLYHV
l 'HVFULEHWKHGDWDVWUXFWXUHRIDQ6$3V\VWHPDQGWKHWKUHH
V\VWHPODQGVFDSH
l 3HUIRUPEDVLFWUDQVSRUWVWHSV
 SAP AG 2002

'DWD6WUXFWXUHRIDQ6$36\VWHP
&OLHQW

&URVV&OLHQW&XVWRPL]LQJ
5HSRVLWRU\
 SAP AG 2002
n SAP systems have a specific data structure. In addition to business settings (Customizing) that are
only relevant for certain clients of the SAP system, an SAP system also always contains cross-
application settings and objects: cross-client Customizing and the Repository.
n The 5HSRVLWRU\ is the central store for all development objects of the ABAP Workbench and is
cross-client. The repository objects are stored in packages. 3DFNDJHV are containers for development
objects that belong together semantically. They replace development classes. A package consists of
sub-packages and development objects (programs, tables, screens, function modules, classes, and so
on) that are developed and transported together. Packages are characterized by the properties nesting,
interfaces, visibility and use accesses. Packages are created and managed with the Package Builder.
The recording and transport of object changes are also controlled by the Change and Transport
System (CTS) using assignment to a package.
n The settings of an SAP system are described as &XVWRPL]LQJ. The enterprise-neutral and industry-
specific business functions that are delivered are tailored to the specific requirements of the
enterprise in the Customizing process. Customizing is obligatory both during the first installation and
during an upgrade and is performed in the SAP system using the Implementation Guide (IMG).
n SAP systems differentiate between client-dependent and cross-client Customizing. Cross-client
Customizing includes the public holiday calendar, or settings for the transport domains and system
changeability.

&OLHQW
&OLHQW
$SSOLFDWLRQ
'DWD
8VHU'DWD
&OLHQW'HSHQGHQW
&XVWRPL]LQJ
 SAP AG 2002
n SAP systems are divided into business units, in clients. A FOLHQW is a self-contained unit in
commercial, organizational, and technical terms in an SAP system and consists of business settings
(Customizing), its own master and transaction data, and its own user data.
n A client’s data is described as client-dependent or client-specific data. Client-dependent data types
are closely interdependent. Thus, when application data is entered, the system checks whether the
data matches the client’s Customizing settings. If there are inconsistencies, the application data is
rejected. Application data is therefore only meaningful in business terms in the relevant Customizing
environment.
n Examples of client-dependent Customizing are company codes and business settings such as plants,
warehouses, and so on.
n Client-dependent data is data that is only valid in that client. This includes, for example, material
master records, orders, and invoices.
n User data and authorizations are also client-dependent.
n Various client roles are used in an SAP system. A Customizing client is required for the client-
dependent Customizing in the development system. In test systems, a client is created for test
purposes (Test role); in production systems, a client is created for productive work. You can assign
the roles to the clients using transaction 6&&.

$GMXVWPHQWVWRWKH'DWD6WUXFWXUH
&XVWRPL]LQJ
$SSO'DWD
$SSO'DWD
8VHU'DWD
8VHU'DWD

&XVWRPL]LQJ &XVWRPL]LQJ
&XVWRPL]LQJ
&URVV&OLHQW
&XVWRPL]LQJ
5HSRVLWRU\
0RGLILFDWLRQ &XVWRPHU
([WHQVLRQ
 SAP AG 2002 'HYHORSPHQW
n As well as client-specific and cross-client Customizing, you can make additional adjustments to the
data structure. Changes to Repository objects are not absolutely necessary for the use of an SAP
system. Changes or extensions to the Repository are possible in a variety of ways:
n a) Extension of the Repository through your RZQGHYHORSPHQWV. In the SAP system, it is possible to
create your own Repository objects such as tables, programs, transactions, and so on. All customer
developments are usually performed in the customer name space. All objects created by customers
have names from a specified namespace, and must begin with the letter Y or the letter Z. You can,
also request your own namespace that begins and ends with “/” free of charge from SAP. This must
be a maximum of eight characters, including the “/”, such as “/Firm/”. All of the objects that you
write then have a name beginning with “/Firm/”, such as “/Firm/GreatProgram”.
n b) Adjusting the Repository using FXVWRPHUHQKDQFHPHQWV. In this case, the Repository is extended
with customer objects. The SAP standard programs can be extended with customer objects at
specified points in the coding, called &XVWRPHU([LWV.
n c) 0RGLILFDWLRQVto the SAP Standard: Changes to SAP objects (programs and table definitions) are
described as modification. The Repository delivered by the SAP system is not only extended, but
also changed.

0RGLILFDWLRQVDQG8SJUDGH
5HSRVLWRU\
:LWKPRGLILHG6$3V\VWHPREMHFWV
6\VWHPVZLWFK
6723
0RGLILFDWLRQ
DGMXVWPHQW
5HSRVLWRU\1HZ
8SJUDGH :LWK6$3V\VWHPREMHFWVLQQHZYHUVLRQ
 SAP AG 2002
n SAP delivers new or functionally extended versions of SAP standard programs and other Repository
objects with an upgrade; that is with a change to a higher release. If a customer has already modified
an existing SAP object, a modification adjustment must be performed during an upgrade. The
different versions of the object can be compared and edited using the Modification Assistant. There
are two options in SAP systems:
1. Copy the new SAP standard and store the modified program version in the version database of
the development system.
2. The integration of both versions (0RGLILFDWLRQ$GMXVWPHQW).
n Modification adjustment is required for every program modified by the customer for which SAP has
delivered an updated version with the new release. Programs that SAP has not changed do not
require modification adjustment. Where possible, avoid modifications, as these require additional
effort during an upgrade.
n During an upgrade, the Repository of an SAP system is replaced with a new Repository (System
Switch). After the release change, the Repository objects are available in an updated version.

3KDVHVRIWKH8SJUDGH
3UHSDUH ,QLWLDOL]DWLRQ 'DWD7UDQVIHU $GMXVWPHQW &RPSOHWLRQ

DQG
$FWLYDWLRQ

! " -465#

# $%! '& / %)102,2

(*)+ "$%', 7 899, +'&
(*)+ $%',
,QFOXGH
6XSSRUW
3DFNDJHV -.
/%)10",2
3 $2! '&
(*)+ $%',
58S 2OG5HOHDVH 1HZ5HOHDVH
 SAP AG 2002
n A PREPARE run is started before an actual upgrade. The PREPARE run prepares the following
upgrade and performs a large number of checks. The upgrade is also performed with the R3up
program.
n The most important phases during the upgrade are initialization, data transfer, adjustment and
activation of the objects, and completion.
n During the initialization, most of the checks from the PREPARE run are performed again, to
determine the changes that have been made to Repository objects. During the data transfer phase,
new Repository objects are imported into the SAP system and compared with objects in the customer
system, to identify customer developments and modifications.
n During the adjustment phase, a modification adjustment (transaction 63'') is performed for all
modified ABAP Dictionary objects (such as tables) for which a new version is delivered with the
new release. During this adjustment, the modifications are compared with the new ABAP Dictionary
objects. You can either copy the modifications to the new version, or use the new object and lose the
modifications that you have made (and the DATA associated with these). The system is unavailable
during the following activation of the ABAP Dictionary objects. The new Repository and the new
Kernel are available after activation. Other Repository objects must be adjusted with transaction
63$8 in a final step.

7KH7KUHH6\VWHP/DQGVFDSH
7KUHH6$3V\VWHPVIRUGHYHORSPHQWTXDOLW\
DVVXUDQFHDQGSURGXFWLRQRSHUDWLRQ
AB*C FGH D9E=A
'LIIHUHQWFOLHQWV
$SSO $SSO LQRQH6$3V\VWHP
8VHU'DWD
8VHU'DWD
'DWD 'DWD
: 'HYHORSPHQW
&XVWRPL]LQJ &XVWRPL]LQJ : 7HVW&XVWRPL]LQJ
; +9,",9< ; 2 ; 02,21=> ?"@
7
8, + &
 SAP AG 2002
n As the Repository objects are cross-client, you should not develop in a system at the same time as
you are working in it productively, as this carries the danger of possible data inconsistency. If you
are making changes to the Repository, we recommend that you use at least two, but ideally three
separate systems (one system for development, a second system for tests and quality assurance, and a
third system in which you work productively). A system landscape of three systems.
n A three-system landscape allows you to use the following, recommended procedure: You develop
your own programs and perform the required Customizing in the development system. The
Customizing settings that you make and all changes to the Repository (developments, corrections,
and modifications) are recorded in the development system and then transported to the quality
assurance (or Test) system, and are checked there without influencing production operation. All
objects and settings imported into the test system can then be transported to one or more production
systems after a successful test.
n Different clients can be created for different purposes in one system. If you perform client-dependent
Customizing in a development system that you want to check before transporting it to other systems,
a test client in the development system can be useful. Clients with specified roles are usually created
in each system: a development client in the development system, a client for testing in the quality
assurance system, and a client for productive work in the production system. The clients should have
an identical ID, as far as possible, as the following rule applies during transporting: Source client =
Target client.

7UDQVSRUWVLQD7KUHH6\VWHP/DQGVFDSH
'HYHORSPHQW 4XDOLW\$VVXUDQFH 3URGXFWLRQ
'(9 4$6 35'
([SRUW
([SRUW ,PSRUW
,PSRUW ,PSRUW
,PSRUW
&HQWUDOWUDQVSRUWGLUHFWRU\DWRSHUDWLQJV\VWHPOHYHO
 SAP AG 2002
n The transport of objects is divided into Export and Import phases: Export from the source system,
import of the objects into other target systems.
n After release, the Repository objects are copied to a data file in the transport directory. The
successful release and export is stored in the transport log of a change request.
n The import into the target system is usually not automatic, but is triggered by the transport
administrator in the Transport Management System (TMS). The import logs can then be checked.
n In technical terms, a copy of the data from the development system database is written to the central
transport directory during the export of the change request. During the import, the change request
stored in the central transport directory is copied into the database of the target system.
n The central transport directory, to which all systems that belong to a system landscape must have
access, is physically on a server of the system landscape (transport server) and is accessed as
/usr/sap/trans or /sapmnt from the other servers involved (by share or mount). Every system finds out
the location of the transport directory to be used using the profile parameter DIR_TRANS.

6WUXFWXUHRI:RUNEHQFK5HTXHVWV
'HYHORSPHQW
'HYHORSPHQW
3URMHFW/HDGHU
3URMHFW/HDGHU
'HYHORSHU
'HYHORSHU 'HYHORSHU
'HYHORSHU
'HYHORSHU
'HYHORSHU
&KDQJHUHTXHVWZLWKDVVLJQHGWDVNV
 SAP AG 2002
n When a development project starts, the development project leader creates a change request. In doing
so, he or she assigns the team members to the change request. The Transport Organizer (transaction
6() assigns a number (<sid>K9<nnnnn>, such as DEVK900050) to the change request. A request
should contain objects that are logically connected and can only be meaningfully executed together.
A request allows you to transport and administer complete, meaningful, and self-contained
developments.
n The Transport Organizer creates a task for every involved employee in the request. If an employee
assigns a Repository object to the change request, the Repository object is logged in the task of that
employee. In this way, all Repository objects that an employee edits during the development project
are collected in the task.
n When the development project is completed from the point of view of the employee, he or she
releases his or her task. This transfers the objects in the task to the change request. Once all
employees have released their tasks, the development project leader can release the change request
and, in doing so, trigger the export. A change request combines Repository objects that have been
created or changed during a development project.

'HYHORSPHQW5HOHDVHDQG7UDQVSRUWRI
5HSRVLWRU\2EMHFWV
/RFN
&UHDWHFKDQJH
UHTXHVW
A9A9IXIKJLJLILINM M O2O2PNPNQ#Q#I%I%RTRTS S
D"DUYUVOKOXW'WYI\I[ZTZ\S S
]*]*ITIT^*^[_L_NI%I%U U &UHDWHREMHFW
$VVLJQPHQW
WRSDFNDJH
'HYHORSHU
'HYHORSHU 'HYHORSHU
'HYHORSHU
$VVLJQPHQWWR
FKDQJHUHTXHVW
&ORVHRIGHYHORSPHQW 5HOHDVHWDVN
a9U^NRTbP*OU S9A=c UI*ZXSVOU d

5HOHDVHFKDQJHUHTXHVW
A9AIKIXJLJLINILM M O"O"PNPNQ#Q`I%I%R\RTS S
 SAP AG 2002 D"DUYUVOKOXW'WYI\I[ZTZ\SS9]*]*ITIX^[^L_N_LI%IU U ([SRUW
n If a Repository object is edited and included in a change request by a developer, it is exclusively

reserved for processing by this change request. Only developers that also have a task in this change
request can make changes to this object. The development or maintenance of development objects is
locked for all other developers that are not involved in the same change request until the change
request is released. These developers can only display the objects.
n Every employee that is involved in the request that edits the object receives a corresponding entry in
the object list of his or her task. In this way, it is possible to determine which employee actually
edited the object.
n The object locks are removed when the change request is released. All developers can then edit the
objects again. Changes to Customizing data are also registered in the Transport Organizer, although
in the case of Customizing, the tables are only locked during the actual editing.
n The Transport Organizer also ensures that the Repository objects are versioned, allowing both
comparisons and access to earlier versions. You can document, and even recreate, the released states
before and after a change request or development project. A version is created when a Repository
object is changed and when a change request is released.

6WUXFWXUHRI&XVWRPL]LQJ5HTXHVWV
&XVWRPL]LQJ3URMHFW
&XVWRPL]LQJ3URMHFW
$GPLQLVWUDWRU
$GPLQLVWUDWRU
&XVWRPL]LQJ3URMHFW
&XVWRPL]LQJ3URMHFW
7HDP0HPEHU
7HDP0HPEHU
&XVWRPL]LQJ3URMHFW
&XVWRPL]LQJ3URMHFW
7HDP0HPEHU
7HDP0HPEHU
&XVWRPL]LQJ3URMHFW
&XVWRPL]LQJ3URMHFW
7HDP0HPEHU
7HDP0HPEHU
&XVWRPL]LQJUHTXHVWZLWKDVVLJQHGWDVNV
 SAP AG 2002
n When a Customizing project starts, the Customizing project administrator creates a change request
for Customizing objects in the Transport Organizer. He or she assigns the employees involved to the
Customizing request. The Transport Organizer (transaction 6() assigns a number
(<sid>K9<nnnnn>, such as DEVK900055) to the Customizing request. A Customizing request can
only contain client-dependent Customizing objects. Cross-client Customizing that is to be
transported must be recorded in a change request of Workbench type, as it is dealing with settings
that apply system-wide.
n The Transport Organizer creates a sub-task for every employee in the request. If an employee assigns
a Customizing object to the Customizing request, the object is logged in the task of that employee. In
this way, all Customizing objects that an employee edits during the project are collected in the task.
n When the Customizing project is completed from the point of view of the employee, he or she
releases his or her sub-task. This transfers the objects in the task to the Customizing request. Once all
employees have released their tasks, the Customizing project leader can release the change request
and therefore export.

([HFXWLRQ5HOHDVHDQG7UDQVSRUWRI&XVWRPL]LQJ
&UHDWHUHTXHVW
eef f b[b[S'SYONO%QjQgc ch*h[c c R*R*igijD9DUVUVOXOKWVW'I[I[ZTZ\S S
G G _%_QjQgc c RR%c cb*b[S S UU^T^TSYSVO2O"U U
3HUIRUP
&XVWRPL]LQJ
$VVLJQPHQWWR5HTXHVW &XVWRPL]LQJ3URMHFW
&XVWRPL]LQJ3URMHFW
7HDP0HPEHU
7HDP0HPEHU
&XVWRPL]LQJ
5HOHDVHWDVN
ILQLVKHG
5HOHDVHUHTXHVW a9U^%RTbP[OUlSAc UI*ZXSYOU d

ee-f f b[bTSYS'O%ONQgQjc ch*h*c c R[RTi6
ijD"DUYUVOKOXW'W'I\ITZTZ\S S
 SAP AG 2002
G G __NQgQjc c RRc c bTb[SkS UU^T^TSVSYO"O2U U ([SRUW
n The structure of Customizing projects is similar to the structure of development projects. The
employees involved in this case are the Customizing project adminsitrator, who creates and realeases
the Customizing requests, and the project team members, who perform the Customizing and assign it
to a Customizing request.
n Changes to Customizing data are registered in the Transport Organizer. In Customizing, the tables
(or table entries) are only locked during the actual editing.

&KHFNLQJ7UDQVSRUWV
AB*C FGH D9E=A
5HOHDVHDQG([SRUW ,PSRUWWR6XEVHTXHQW6\VWHPV
([SRUW/RJ ,PSRUW/RJV
 SAP AG 2002
n During transporting, the transport steps performed in the various transport phases are logged. You
can use the Transport Organizer to control transports: There is a list of your transports and repairs on
the right side of the initial screen of the Transport Organizer.
n By choosing 7UDQVSRUWV, you display a hierarchical display of your released transports and their
transport steps, structured by target systems.
n You can identify the success or failure of the individual transport steps from the colored labeling, the
comment, and the return code. In the case of erroneous transports, the transport log contains notes
about the cause of the errors. By selecting a transport step, you display its transport log.
n All import steps are also logged during the import, which is performed by the transport administrator
in transaction 6706. In this case, it is also possible to display the relevant information using the
Transport Organizer.
n To obtain additional information about the import, you can call the system log for the monitoring
system by choosing transaction 6706→,PSRUW2YHUYLHZ. To do this, choose the system to be
checked in the import overview and display the system log by choosing *RWR→736\VWHPORJfrom
the import queue. From here, you can perform additional error analysis using other log files.

6XPPDU\
<RXDUHQRZDEOHWR
l 'HVFULEHWKHGDWDVWUXFWXUHRIDQ6$3V\VWHPDQGWKH
WKUHHV\VWHPODQGVFDSH
l $VVHVVWKHXVHRIPRGLILFDWLRQV
l 3HUIRUPEDVLFWUDQVSRUWVWHSV
 SAP AG 2002

6\VWHP/DQGVFDSHVDQG7UDQVSRUW5HTXHVWV([HUFLVHV
1R ([HUFLVHV
:RUNLQJZLWKWKH7UDQVSRUW2UJDQL]HU
1.1 Use the Transport Organizer to create a change request with the type
:RUNEHQFK5HTXHVW. You can start the Transport Organizer by choosing
7RROV→$%$3:RUNEHQFK→2YHUYLHZ→7UDQVSRUW2UJDQL]HUor with
transaction code 6(.
1.2 Give your change request a meaningful short description and save it.
1.3 Display the number of your request and the assigned tasks.
&UHDWHD5HSRVLWRU\REMHFW
2.1 Create a package with the Object Navigator (6().
2.2 Assign the name =B3DFNDJHB to your package, where is your group
number.
2.3 Assign the necessary attributes to the package: A meaningful short
description, assignment to a software component and the standard transport
layer =6,'!. Choose &UHDWH to create your package.
2.4 The system prompts you to assign your newly created Repository object to a
Workbench request. Under 2ZQ5HTXHVWV, choose the change request that
you created in exercise 1 by double clicking it, and confirm the selection.
2.5 Check the assignment to your request in the Transport Organizer.
5HOHDVHWKHFKDQJHUHTXHVWDQGWKHWDVN
3.1 Release your task (the package that you created) in the Transport Organizer.
3.2 Release your change request.
&KHFNLQJ7UDQVSRUWV
4.1 Obtain an overview of the transport logs created during the release and
export.

6\VWHP/DQGVFDSHVDQG7UDQVSRUW5HTXHVWV 6ROXWLRQV
1R 6ROXWLRQV
:RUNLQJZLWKWKH7UDQVSRUW2UJDQL]HU
1.1 8VHWKH7UDQVSRUW2UJDQL]HUWRFUHDWHDFKDQJHUHTXHVWZLWKWKHW\SH
:RUNEHQFK5HTXHVW<RXFDQVWDUWWKH7UDQVSRUW2UJDQL]HUE\
FKRRVLQJ7RROV→$%$3:RUNEHQFK→2YHUYLHZ→7UDQVSRUW
2UJDQL]HURUZLWKWUDQVDFWLRQFRGH6(
On the initial screen, choose the request type :RUNEHQFKUHTXHVW and then
choose &UHDWH. On the next dialog screen, choose :RUNEHQFKUHTXHVW again,
if required, and then confirm by choosing the green tickmark.
1.2 *LYH\RXUFKDQJHUHTXHVWDPHDQLQJIXOVKRUWGHVFULSWLRQDQGVDYHLW
Enter a meaningful short description for your change request and save it by
choosing 6DYH.
1.3 'LVSOD\WKHQXPEHURI\RXUUHTXHVWDQGWKHDVVLJQHGWDVNV
On the next screen, the system displays the (automatically generated)
number of your transport request (<SID>K9nnnnn) and the number(s) of the
assigned task(s).
&UHDWHD5HSRVLWRU\REMHFW
2.1 &UHDWHDSDFNDJHZLWKWKH2EMHFW1DYLJDWRU6(
You can also call the Object Navigator by choosing 7RROV→$%$3
:RUNEHQFK→2YHUYLHZ→2EMHFW1DYLJDWRU. On the initial screen of the
Object Navigator, choose 5HSRVLWRU\%URZVHU and choose the entry SDFNDJH
in the dropdown list below this.
2.2 $VVLJQWKHQDPH=B3DFNDJHBWR\RXUSDFNDJHZKHUHLV\RXU
JURXSQXPEHU
As your package does not yet exist, the system asks you if you want to
create it after you choose (QWHU. Confirm this with <HV.
2.3 $VVLJQWKHQHFHVVDU\DWWULEXWHVWRWKHSDFNDJH$PHDQLQJIXOVKRUW
GHVFULSWLRQDVVLJQPHQWWRWKHVRIWZDUHFRPSRQHQW+20(DQGWKH
VWDQGDUGWUDQVSRUWOD\HU=6,'!&KRRVH&UHDWHWRFUHDWH\RXUSDFNDJH
See exercise text.
2.4 7KHV\VWHPSURPSWV\RXWRDVVLJQ\RXUQHZO\FUHDWHG5HSRVLWRU\
REMHFWWRD:RUNEHQFKUHTXHVW8QGHU2ZQ5HTXHVWVFKRRVHWKH
FKDQJHUHTXHVWWKDW\RXFUHDWHGLQH[HUFLVHE\GRXEOHFOLFNLQJLWDQG
FRQILUPWKHVHOHFWLRQ
See exercise text.
2.5 &KHFNWKHDVVLJQPHQWWR\RXUUHTXHVWLQWKH7UDQVSRUW2UJDQL]HU
Display all change requests that you created but that are not yet released by
choosing 'LVSOD\.
There is a task described as 'HYHORSPHQW&RUUHFWLRQ under your change
request.

5HOHDVHWKHFKDQJHUHTXHVWDQGWKHWDVN
3.1 5HOHDVH\RXUWDVNWKHSDFNDJHWKDW\RXFUHDWHGLQWKH7UDQVSRUW
2UJDQL]HU
To release your task, switch in the Transport Organizer to your change
requests that have not yet been released by choosing 'LVSOD\. Select the
task to be released (the package that you created is below it) and release
this by choosing 5HOHDVH'LUHFWO\.
3.2 5HOHDVH\RXUFKDQJHUHTXHVW
To release the entire change request, select it and choose 5HOHDVH'LUHFWO\.
&KHFNLQJ7UDQVSRUWV
4.1 2EWDLQDQRYHUYLHZRIWKHWUDQVSRUWORJVFUHDWHGGXULQJWKHUHOHDVHDQG
H[SRUW
You can display the logs that were created during the transport in the
Transport Organizer. To do this, on the initial screen of the Transport
Organizer, under 5HTXHVW6WDWXV, choose the released requests and choose
'LVSOD\. The system displays all released requests in the next window. Select
the desired request and then 7UDQVSRUW/RJV. The system displays a log, a
returncode and the time of the transport step for all transport steps that have
already been performed.
By clicking the log, you display a long version of the log that you may have to
expand further.

$FFHVVWR+HOS
%DVLFVRIXVHUDGPLQLVWUDWLRQ
5HPRWHFRQQHFWLRQV
 SAP AG 2002

&RQWHQWV
l 63$0,PSRUWLQJ6XSSRUW3DFNDJHV
l 6$,17,QVWDOODWLRQDQGXSJUDGHRI,QGXVWU\6ROXWLRQV
l ,QWURGXFWLRQWRWKH1RWH$VVLVWDQW
2EMHFWLYHV
l ,PSRUW6XSSRUW3DFNDJHVZLWKWUDQVDFWLRQ63$0
l ,QVWDOODQGXSGDWH,QGXVWU\6ROXWLRQVZLWKWUDQVDFWLRQ6$,17
l 8VHWKH1RWH$VVLVWDQW
 SAP AG 2002

%XVLQHVV6FHQDULR
l 7KH6$3V\VWHPLVNHSWDWWKHQHZHVWFRUUHFWLRQ
VWDWXVVRWKDWHUURUVLQWKHVWDQGDUGUHOHDVHDUH
SURDFWLYHO\UHPRYHG
l ,QDGGLWLRQWRWKHVWDQGDUGIXQFWLRQVLQDQ6$3
V\VWHPDGGLWLRQDOIXQFWLRQVDUHUHTXLUHGIURPDQ
LQGXVWU\VROXWLRQ
l 7RPLQLPL]HWKHHIIRUWXVHWKH1RWH$VVLVWDQWWR
LPSRUW6$3FRUUHFWLRQV
 SAP AG 2002

:KDW,VD6XSSRUW3DFNDJH"
l $6XSSRUW3DFNDJHLVDQXPEHURI
FRUUHFWHG6$3REMHFWV
6XSSRUW3DFNDJH
l 6XSSRUW3DFNDJHVDUHUHTXLUHGWR
6$3B$33/
FRUUHFWHUURUVLQWKHGLIIHUHQWVRIWZDUH
FRPSRQHQWV
l 7KLVLVGRQHE\UHSODFLQJHUURQHRXV
REMHFWVZLWKFRUUHFWHGREMHFWV

,6 ,6 (QWHUSULVH([WHQVLRQV,QGXVWU\6ROXWLRQV

3OXJ,Q 3OXJ,QV
$33/ +5 %: 650
&50 0DLQFRPSRQHQWV
$%$
%DVLVFRPSRQHQWV
%DVLV
 SAP AG 2002
n IS: Industry Solution

n PI: Plug-In
n APPL: Core applications
n HR: Human Resources
n BW: Business Information Warehouse
n SRM: Supplier Relationship Management
n CRM: Customer Relationship Management
n ABA: Application interface

7\SHVRI6XSSRUW3DFNDJHV
$23,66XSSRUW3DFNDJH

&57&RQIOLFW5HVROXWLRQ
,6
7UDQVSRUW&ROOHFWLYH
RU6LQJOH
3OXJ,Q
$33/ +5 %: 650
&50 &236RIWZDUH&RPSRQHQW
6XSSRUW3DFNDJH
$%$

%DVLV
3$763$06$,178SGDWH
 SAP AG 2002
n COP (Component Package):

SAP_APPL (SAP R/3 Support Package) SAPKH<rel><nr>
SAP_BASIS (SAP Basis Support Package) SAPKB<rel><nr>
SAP_ABA (Application Interface SP) SAPKA<rel><nr>
SAP_HR (SAP R/3 HR Support Package) SAPKE<rel><nr>
SAP_APO (APO Support Package) SAPKY<rel><nr>
SAP_BW (BW Support Package) SAPKW<rel><nr>
n AOP (Add-On Package): Some New Dimension Integration (NDI) products are treated as Add-Ons.
n CRT (Conflict Resolution Package): Solves conflicts between Support Packages and Add-Ons (such
as an Industry Solution) and can also contain corrections for the Add-On. Can be used either for each
individual Support Package or as a collective CRT for a range of several Support Packages
(SAPKI*, SAPKJ*, SAPKP*, and SAPKG*).
n PAT: Provides new functions for transactions SPAM and SAINT. There is only one SPAM/SAINT
update for each release, but in different versions. SAPKD<5 digit number>
n No longer exist since SAP R/3 4.6: FFD: Final Delta Patch for First Customer Shipment (FCS),
HOT: Hot Package, LCP: Legal Change Patch for HR, BWP: Business Information Warehouse
Patch

63$0DQG6$,17
7UDQVDFWLRQ 7UDQVDFWLRQ
63$0 6$,17
,PSRUW6XSSRUW ,QGXVWU\6ROXWLRQ
3DFNDJHV ,QVWDOODWLRQ8SJUDGH

,6 ,6

3OXJ,Q 3OXJ,Q
$33/ +5 %: 650
&50
$%$

%DVLV
 SAP AG 2002
n Transaction 63$0 allows you to import Support Packages. This applies to Support Packages for the
standard SAP system, for Industry Solutions, and for CRTs.
n You can only import a SPAM/SAINT update using transaction 63$0.
n Transaction 6$,17 allows you to install and upgrade an Add-On, such as an Industry Solution, from
the SAP system. To install or upgrade an Add-On, it can be necessary to import Add-On Support
Packages and CRTs. Transaction 6$,17deals with this.
n In terms of transaction 6$,17, an Add-On is everything that does not belong to the SAP standard.
This includes, for example, Industry Solutions, Software Development Projects (SDPs), and Plug-
Ins.

63$0 3UHUHTXLVLWHVDQG$XWKRUL]DWLRQV
l 7KHUHTXLUHG6XSSRUW3DFNDJHVPXVWEHDYDLODEOH
l 7KHUHPXVWEHHQRXJKIUHHVSDFHLQWKHILOHV\VWHP
l 7KHLPSRUWVKRXOGEHSHUIRUPHGGXULQJDWLPHRIORZRSHUDWLRQ
l 7KHQHZHVW63$06$,17XSGDWHLVUHTXLUHG
l 706&76PXVWEHFRQILJXUHG
l 1RDERUWHG6XSSRUW3DFNDJHVLQWKHV\VWHP
l &OLHQWIRULPSRUWLQJLQDOORWKHUFOLHQWVRQO\GLVSOD\IXQFWLRQ
l 6\VWHPDXWKRUL]DWLRQVIRU63$0
l 2QO\WKHV\VWHPDGPLQLVWUDWRUVKRXOGEHDXWKRUL]HGWR
l'RZQORDG6XSSRUW3DFNDJHV
l,PSRUW6XSSRUW3DFNDJHV
l&RQILUPVXFFHVVIXOO\LPSRUWHG6XSSRUW3DFNDJHV
l5HVHWWKHVWDWXVRID6XSSRUW3DFNDJH
 SAP AG 2002
n The authorizations S_TRANSPRT and S_CTS_ADMIN are required to run 63$0. These
authorizations are part of authorization profile S_A.SYSTEM.
n Only the system administrator should be authorized to:
é Download Support Packages
é Import Support Packages
é Confirm successfully imported Support Packages
é Reset the status of Support Packages
n System: Check the correct function of the transport tools with 8WLOLWLHV→&KHFN7UDQVS7RRO.
Ensure that there is enough space (size of the OCS files multiplied by two) in the transport directory
(see SAP profile parameter DIR_TRANS with transaction $/ or transaction 6( and report
RSPFPAR). You should especially ensure that there is enough space in the subdirectories
trans/EPS/in and trans/data.
n Use the newest SPAM/SAINT update. Check whether the SPAM/SAINT update provided in the
SAPNet - R/3 Frontend or on the SAP Service Marketplace is newer than the update in your system.
(The version of the SPAM/SAINT update in your system is displayed in the title bar of the Support
Package Manager.)
n No incompletely imported Support Packages are allowed in your system. Check the 7HUPLQDWHG
6XSS3DFNDJHVoption under 'LUHFWRU\and choose 'LVSOD\. There must not be any Support
Packages displayed.

63$0/RDG6XSSRUW3DFNDJHV
266
/RDGIURP6$31HW±
Request
5)URQWHQG
Load
6$36HUYLFH0DUNHWSODFH
Settings
&' $SSO6HUYHU
Queue
0%
Import
/RDG6XSSRUW3DFNDJH Logs
WRIURP)URQWHQG 6$36\VWHP
Confirm
SAP
SAP GUI
GUI
 SAP AG 2002
n Before you can import Support Packages, you must first load the relevant Support Packages. SAP
provides Support Packages in the SAPNet - R/3 Frontend (previously OSS), in the SAP Service
Marketplace, and on Collection CDs (not always absolutely up-to-date).
n SAPNet – R/3 Frontend: Before loading a Support Package from the SAPNet - R/3 Frontend,
maintain the network parameters for logging on to the SAPNet - R/3 Frontend. Use transaction 266
to do this.
1. Request the desired Support Packages in the SAPNet - R/3 Frontend.
2. Load the requested Support Packages into your SAP system by choosing 6XSSRUW3DFNDJHV →
/RDG3DFNDJHV→)URP6$31HW5)URQWHQG.
n Loading a Support Package from the SAP Service Marketplace or from CD:
1. Load the Support Packages from the SAP Service Marketplace or from the relevant CD and
decompress them.
2. Now load the Support Packages into your system by choosing 6XSSRUW3DFNDJH→/RDG3DFNDJH
→)URPDSSOLFDWLRQVHUYHU.
n If the compressed files are on your frontend server and are smaller than around 10 MB, you can
transfer these files to the application server and decompress them directly from the Support Package
Manager.
1. Call the Support Package Manager with transaction code 63$0.
2. Choose 6XSSRUW3DFNDJH→/RDG3DFNDJHV→)URPWKH)URQWHQG.
3. To decompress the files in the archive, choose 'HFRPSUHVV.

63$06HWWLQJV
'HIDXOW
l /RDGLQJIURP6$31HW±5)URQWHQG Request
n 7UDQVPLVVLRQ0RQLWRU 2II
l /RDGLQJD&$56$5$UFKLYHIURPWKH)URQWHQG Load
n 'LVSOD\FRQWHQWVEHIRUHGHFRPSUHVVLRQ 2Q
Settings
n 'HOHWHILOHDIWHUGHFRPSUHVVLRQ 2Q
n 6DYHODVWXSORDGGLUHFWRU\ 2Q Queue
l ,PSRUWWKHWKH6XSSRUW3DFNDJH4XHXH
n 7HVWVFHQDULR 6WDQGDUG Import
n ,QDFWLYHLPSRUWRIUHSRUWV 2II
l ,PSRUW4XHXH Logs
n 5HJHQHUDWHGDWDILOH 2Q
Confirm
n 'HOHWHGDWDILOHDIWHULPSRUW 2Q
n $%$3VFUHHQJHQHUDWLRQ 1HYHU
 SAP AG 2002
n Transmission Monitor: Load the Support Packages with graphical monitoring.

n Import the the Support Package Queue: The standard scenario is used to import Support Packages
completely and all steps are performed. You can select ,QDFWLYHLPSRUWRIUHSRUWVRXUFHVDQGWH[WV
here (see appendix). Use the test scenario to determine before the actual import of the Support
Package whether a modification adjustment is required or whether conflicts occur that must be
removed before the import. No data and objects are imported during the test scenario.
n Import Queue: Regenerate data file/Delete data file after import: If you are operating a multiple
system landscape with a shared transport directory, it is sensible only to select this option in the first
system in to which you import the Support Packages. This saves time when importing into other
systems.
n ABAP/screen generation: You use this option to define whether the programs and screens delivered
with the Support Packages should be generated during the import. You have the following options:
é Never Execute: With no automatic generation, the programs and screens are generated the first
time they are called.
é Always Execute: With this option, screens and programs are always generated. Note that
generation can last a very long time, and errors may occur during generation.
é According to SAP Instructions: In this case, programs and screens are only generated if the
generation during the import of these Support Packages is allowed by SAP.

63$0'HILQHDQG,PSRUW4XHXH
Request
&KRRVHFRPSRQHQWV 6$3B%$6,6
Load
'HWHUPLQHTXHXHHQG
Settings
6$3.%
6$3.%
6$3.% Queue
6$3.%
Import
,PSRUW 6XSSRUW3DFNDJH
Logs
,PSRUW4XHXH Confirm
 SAP AG 2002
n The Support Package Manager ensures that only Support Packages that match your system are
displayed in the queue. Support Packages that are intended for a different release or an Industry
Solution that is not installed do not appear in the queue, even if you have loaded them into your SAP
system.
n Alternatively, you can calculate a queue for all software components in the system, by choosing $OO
&RPSRQHQWV.
n The queue contains the Support Packages available for the selected component(s) in your system and
any required Conflict Resolution Transports (CRTs) and associated IS Support Packages.
n If Support Packages in the queue are related to Support Packages for another software component
(other predecessor relationship and required CRT), the queue is extended with other Support
Packages until all predecessor relationships are fulfilled.
n Test scenario or standard scenario: To set the desired scenario, choose ([WUDV→6HWWLQJV

63$03HUIRUP0RGLILFDWLRQ$GMXVWPHQW
:LWKRXW,QGXVWU\ Request
6ROXWLRQ &XVWRPHU
Load
Settings
6$36WDQGDUG
6XSSRUW Queue
3DFNDJH $GMXVWPHQW
:LWK,QGXVWU\6ROXWLRQ
Import
&XVWRPHU
Logs
,QGXVWU\6ROXWLRQ
Confirm
6$36WDQGDUG
12$GMXVWPHQW
 SAP AG 2002
n 1. The Support Package Manager stops to allow the modification adjustment. The Support Package
Manager will resume processing at step RUN_SPAU or RUN_SPDD.
n 2. Create a request in the Transport Organizer and tasks under the request for the developers, so that
your developers can perform the modification adjustment.
n 3. Ask the developers to perform the modification adjustment for those objects. As long as you have
not yet confirmed the queue, you can perform a context-sensitive switch from the initial screen of the
Support Package Manager in transaction 63'' or 63$8 by choosing ([WUDV→0RGLI$GMXVWPHQW
n After the adjustment is complete, the developers must release their tasks and inform you. The
adjustment can be performed in any client.
n 4. If you left the transaction, call the Support Package Manager (transaction 63$0), and choose
6XSSRUW3DFNDJH→,PSRUW4XHXH. The system prompts you again to perform the modification
adjustment. Since the modification adjustment has already been completed, ignore the message and
choose &RQWLQXH. The Support Package Manager completes the processing and displays the status.

63$0&KHFN/RJVDQG&RQILUP4XHXH
Request
&KHFNORJV
Load
&RQILUP6XSSRUW3DFNDJHV4XHXH
&RQILUPDWWKHODWHVW Settings
%HIRUHWKHQH[W6XSSRUW3DFNDJH
%HIRUHWKHQH[WXSJUDGH Queue
7HVWWKHUHVXOWRIWKHLPSRUW
Import
'(9 4$6 35'

Logs

,IWKHUHLVRQHWKHQLPSRUW6XSSRUW Confirm
3DFNDJHVLQWRWKHQH[WV\VWHP
 SAP AG 2002
n The /RJfunction displays logs for steps of the Support Package Manager that use the transport
control program tp. After the queue has been successfully imported, you should always check these
logs. To jump to the log display, choose *RWR→/RJ→4XHXH in the initial screen of the Support
Package Manager.
n Confirm the successful import of the queue into your system. This ensures that you can import other
Support Packages in future. Without this confirmation, it is not possible to import additional Support
Packages.
If you have not yet confirmed successfully imported Support Packages, you are prompted to confirm
these packages during an upgrade of the system.
n Import Support Packages into other systems.
n Prerequisites:
1. The Support Packages were successfully imported into one system (development system).
2. You have performed the modification adjustment.
3. The systems have a shared transport directory.
n Procedure:
1. Load the Support Packages into the next system (quality assurance or production system).
SPAM → 6XSSRUW3DFNDJH→8SORDGin target system
2. Import the Support Packages in the usual way.
3. Import the modification adjustment transport.

:KDWLVDQ,QGXVWU\6ROXWLRQ"
l 7KHFXVWRPHUUHTXLUHVIXQFWLRQVWKDWDUHQRWLQFOXGHGLQWKHVWDQGDUG
6$3V\VWHPEXWZKLFKDUHRIIHUHGE\DQLQGXVWU\VROXWLRQ
l $QLQGXVWU\VROXWLRQEULQJVQHZREMHFWVDQGDGGLWLRQDO&XVWRPL]LQJ
LQWRWKHV\VWHP
l $QLQGXVWU\VROXWLRQFDQPRGLI\H[LVWLQJ6$3VWDQGDUGREMHFWVDQG
FKDQJHH[LVWLQJ&XVWRPL]LQJ
l $&57FDQEHUHTXLUHGWRFRUUHFWFRQIOLFWVEHWZHHQWKH6$3VWDQGDUG
DQGDQLQGXVWU\VROXWLRQRUDQ,66XSSRUW3DFNDJH
,62EMHFWV
&57
,6&XVWRPL]LQJ
6$36WDQGDUG2EMHFWV
&XVWRPL]LQJ
 SAP AG 2002
n Add-Ons are imported with transaction 6$,17:

In terms of transaction 6$,17, an Add-On is everything that does not belong to the standard SAP
system. This includes, for example, Industry Solutions, Software Development Projects (SDPs), and
Plug-Ins.
n Examples of Industry Solutions:
• mySAP Aerospace & Defense, mySAP Automotive
• mySAP Banking, mySAP Chemicals
• mySAP Consumer Products, mySAP Engineering & Construction
• mySAP Financial Service Provider, mySAP Healthcare
• mySAP Higher Education & Research, mySAP High Tech
• mySAP Insurance, mySAP Media
• mySAP Mill Products, mySAP Mining
• mySAP Oil & Gas, mySAP Pharmaceuticals
• mySAP Public Sector, mySAP Retail
• mySAP Service Providers, mySAP Telecommunications
• mySAP Transportation, mySAP Utilities

6$,173UHUHTXLVLWHVDQG$XWKRUL]DWLRQV
l 7KHUHTXLUHG,QGXVWU\6ROXWLRQV6XSSRUW3DFNDJHVDQG&57VPXVW
EHDYDLODEOH
l 7KHUHPXVWEHHQRXJKIUHHVSDFHLQWKHILOHV\VWHP
l 7KHLPSRUWVKRXOGEHSHUIRUPHGGXULQJDWLPHRIORZRSHUDWLRQ
l 7KHQHZHVW63$06$,17XSGDWHLVUHTXLUHG
l 706&76PXVWEHFRQILJXUHG
l 1RDERUWHG6XSSRUW3DFNDJHVRU,6LQWKHV\VWHP
l &OLHQWIRULPSRUW
&OLHQW!GLVSOD\IXQFWLRQRQO\
l 6\VWHPDXWKRUL]DWLRQVIRU6$,17
l 2QO\IRU3UHFRQILJXUHG6\VWHP3&6
n 123&6LQVWDOOHG\HW
n &OLHQWPXVW127EHRU
n 1RSURGXFWLYHFOLHQWLQV\VWHP6&&
 SAP AG 2002
n The authorizations S_TRANSPRT and S_CTS_ADMIN are required to run 6$,17. These
authorizations are part of authorization profile S_A.SYSTEM.
n System: Check that the transport tool is functioning correctly. Ensure that there is enough free space
(size of the OCS files multiplied by two) available in the transport directory.
n Use the newest SPAM/SAINT update.
n The procedures for an Add-On installation and an Add-On upgrade are identical.
n There must not be any incompletely imported Support Packages or aborted Add-On installations and
upgrades in your system.

SeimensNotes101 151

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SeimensNotes101 151

Enviado por

Direitos autorais:

Formatos disponíveis

$GGLWLRQDO,QIRUPDWLRQ

© SAP AG ADM100 6-11

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 6-12

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 6-13

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 6-14

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 6-15

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-1

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-2

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

2QJRLQJ/RJ,QIRUPDWLRQ 'DWD)LOH 'DWD)LOHQ

© SAP AG ADM100 7-3

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

2QJRLQJ/RJ,QIRUPDWLRQ 'DWD)LOH 'DWD)LOHQ

© SAP AG ADM100 7-4

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-5

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

n Storing the data and log info backups:

© SAP AG ADM100 7-6

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-7

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

57698 :;9<:9=?> < @ ACBEDA DF>G;9H@ = D ;9I*:9;JACKGLMJA :IONP:98 Q

R#D SG T U : SGV W= KP6 KT '%

Complete data backup

© SAP AG ADM100 7-8

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-9

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-10

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-11

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-12

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 7-13

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 8-1

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 8-2

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 8-3

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 8-4

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 8-5

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

© SAP AG ADM100 8-6

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

3UHSDUH ,QLWLDOL]DWLRQ 'DWD7UDQVIHU $GMXVWPHQW &RPSOHWLRQ

  ! " -465#

58S 2OG5HOHDVH 1HZ5HOHDVH

© SAP AG ADM100 8-7

Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.

AB*C FGH D9E=A

© SAP AG ADM100 8-8

2QJRLQJ/RJ,QIRUPDWLRQ 'DWD)LOH 'DWD)LOHQ

2QJRLQJ/RJ,QIRUPDWLRQ 'DWD)LOH 'DWD)LOHQ

57698 :;9<:9=?><@ ACBEDA DF>G;9H@ = D;9I*:9;JACKGLMJA :IONP:98 Q

R#D SGT U : SGV W= KP6 KT '%

! " -465#

58S 2OG5HOHDVH 1HZ5HOHDVH

AB*C FGH D9E=A

a9U^NRTbPOU S9A=c UIZXSVOU d

5HOHDVHUHTXHVW a9U^%RTbP[OUlSAc UI*ZXSYOU d

AB*C FGH D9E=A