SAP Basis Tech Supports

Symptom
This note contains information about using transaction SAINT for an add-on delta upgrade.
Other terms
SAINT, Add-On, installation, BANK-TRBK, BANK-ALYZE, FSAPPL 200, SAP NetWeaver 7.1 for banking services from SAP, banking services from SAP 6.0, SAP NetWeaver Application Server ABAP 7.1
Reason and Prerequisites
You use transaction SAINT to install an add-on or to perform a delta upgrade.
Solution

Make sure that you have the current version of this note before you start the installation.
Important: The original version of this note is in German. This means that all changes in this note are made in German first and then translated into English, which can take some time.
Contents
1. Change history
2. Prerequisites for the delta upgrade FSAPPL 200
3. Preparing for the delta upgrade FSAPPL 200
4. Performing the delta upgrade FSAPPL 200
5. After the delta upgrade to FSAPPL 200
6. Language support
7. Password
1. Change history

DateTopicShort Description20.10.20082FSAPPL and IBS (CYT)06.03.20082Conflict with SAP_ABA14.12.2007initialreleased2. Prerequisites for the delta upgrade FSAPPL 200
Uninstalling FSAPPL.
Before you install FSAPPL or perform the delta upgrade FSAPPL, keep in mind that it is not possible to uninstall ABAP add-ons or to reset the system to the previous release. Further restrictions, which concern the upgrade and maintenance of your SAP system and are caused by the installation of an add-on, are described in Release Strategy Note 983007.Required release
The following releases are required:SAP NetWeaver Application Server ABAP 7.1 with the add-on FSAPPL 100 (already installed).Import the latest SPAM/SAINT update.
Make sure that you have installed the latest SPAM/SAINT update in your system. If a newer version is available on SAP Service Marketplace, import the new SPAM/SAINT update.Import the latest R3trans and tp.
Ensure that you have imported the latest kernel version into your system. If a newer version is available on SAP Service Marketplace, import the most recent kernel.Obtain the following notes before you begin the installation:
Add-ons: Conditions 70228Overview note 983008Release strategy note 983007Maintenance note 1096850Problems with transaction SAINT 954792
Prerequisites:
Check that your system meets the following prerequisites:Required Components and Support Packages
ComponentReleaseSupport PackageSAP_BASIS710Support Package 4, SAPKB71004SAP_ABA710Support Package 4, SAPKA71004SAP_BW710Support Package 4, SAPKW71004FINBASIS700Support Package 1, SAPK-70001INFINBASISSEM-BW700Support Package 1, SAPK-70001INSEMBWIn addition, we recommend that you include FSAPPL 200 Support Package 01, SAPKISC301 in the delta upgrade or directly import it into your system after the upgrade. For the FSAPPL 200 Support Package 01 level, refer to Note 1125028.
You must have already installed the two NetWeaver add-ons FINBASIS 700 and SEM-BW 700, or you must have incorporated them into the installation upgrade queue. For more information, see Notes 1037878 (Installing FINBASIS 700) and 1037738 (Installing SEM-BW 700).If you have not yet imported these Component Support Packages, you can include them in the installation upgrade queue for FSAPPL 200. For more information, see Note 83458.Additional Component Support Packages
The add-on FSAPPL 200 does not contain any modifications. However, there is one exception (see next section). You do not require Conflict Resolution Transports (CRTs) of FSAPPL to import further Support Packages of other software components. For more information about CRTs, see Note 53902.Conflict of FSAPPL 200 with SAP_ABA Support Package 4.
If your FSAPPL 100 system has been historically created during a repository switch upgrade from BANK-TRBK 30 or BANK-TRBK 40 to FSAPPL 100, the system may issue a conflict message concerning SAP_ABA Support Package 04 (SAPKA71004) during the delta upgrade to FSAPPL 200. In this case, include the CRT FSAPPL 200 that is available on SAP Service Marketplace and has the package name ‘SAPKISC3A1′ in the upgrade queue.FSAPPL and IBS (CYT)
If, in addition to the component FSAPPL 100, you install the component IBS 5.0 (CYT) in your system, you must perform the delta upgrade to FSAPPL 200 as well as the delta upgrade to IBS 6.0. This constellation is automatically checked as of SPAM Version 25 and the simultaneous inclusion of FSAPPL 200 Support Package 05 (SAPKISC305). If you use an older version of SPAM or you do not include FSAPPL 200 Support Package 05 in the delta upgrade, you must then manually ensure that the correct version of the component IBS is available in your system.Additional prerequisites:
Space required in the database 1 GBSpace required in transport directory 1 GB
Additional information about the add-on delta upgrade
DVD material number or add-on delta upgrade 51033103approximately 2-8 hours, depending on the system3. Preparing for the delta upgrade FSAPPL 200
Make the FSAPPL 200 add-on available as follows:
The delta upgrade DVD for FSAPPL 200 is not sent to all customers automatically. Request the DVD with material number 51033103 from your local subsidiary or download the DVD from SAP Service Marketplace.Log on as user:
<sid>admfor UNIX<SID>OFRfor AS/400<SID>admfor Windows NT
Switch to the <DIR_EPS_ROOT> directory of your SAP system (usually /usr/sap/trans/EPS). The <DIR_EPS_ROOT> directory is also displayed under DIR_EPS_ROOT after you execute the RSPFPAR report.Go to the higher-level directory of <DIR_EPS_ROOT>.To unpack the SAR archive KISC18H.SAR on the DVD, use the following statement:
SAPCAR -xvf /<DVD_DIR>/DATA/KISC18H.SARfor UNIXSAPCAR ‘-xvf /QOPT/<VOLID>/DATA/KISC18H.SAR’for AS/400SAPCAR -xvf <DVD_DRIVE>:\DATA\KISC18H.SARfor Windows
The file entitled CSN0120061532_0028930.PAT should now be located in the <DIR_EPS_ROOT>/in directory.4. Performing the delta upgrade FSAPPL 200
User to be used
Log on to your SAP system in client 000 as a user with SAP_ALL authorization. Do NOT use the SAP* or DDIC users.Displaying the add-on delta upgrade package
Call transaction SAINT and choose ‘Load’. After the list of uploaded packages is displayed, you can return to the initial screen of transaction SAINT by choosing either F3 or ‘Back’.Start the delta upgrade.
Call transaction SAINT. Select the add-on FSAPPL 200 and then choose ‘Continue’. If all of the necessary conditions for importing the add-on have been fulfilled, the system will now display the relevant queue. The queue consists of the delta upgrade package (SAPKISC18H) and it may also contain Support Packages and Add-On Support Packages. To start the upgrade process, choose ‘Continue’. For more information, call transaction SAINT and choose ‘Info’ on the application toolbar.
5. After the delta upgrade to FSAPPL 200
Importing Support Packages after the delta upgradeThe add-on FSAPPL 200 does not modify any other software components. Therefore, after the delta upgrade, you do not require CRTs for the add-on FSAPPL 200 to import further Support Packages for other software components. For more information about CRTs, see Note 53902.Generation errorsThe delta upgrade package of the add-on FSAPPL 200 does not contain any generation errors if you are using SAP_ABA 710 Support Package Level 4 (SAPKA71004) and you have also implemented Note 1113000 in your system. Generation errors should no longer occur in higher Support Package levels.Delivery CustomizingDelivery Customizing is imported into client 000 and may have to be copied to other clients. For more information, see Note 337623.
6. Language support
In addition to German and English, the following languages are supported by FSAPPL 200: Chinese, French, Russian, Japanese, Spanish, Italian, Korean, Portuguese and Hebrew.All language-dependent portions of FSAPPL 200 are contained in the delta upgrade package for the add-on. If the relevant standard language exists in the system when you import FSAPPL 200, the language part of the add-on is automatically imported too. You do not need to import a language transport separately.If you import a new standard language into your system after the delta upgrade FSAPPL 200, you must manually ensure that the corresponding language-dependent part of the add-on is imported. For more information, see Note 195442.
7. Password
During the installation, the system prompts you to enter a password. This password is: 34E56A26AF