Version 260 from Jun 14, 2019 in English
1. Select the proper ST-A/PI release
2. Implementation
4. Combination with other add-ons
All combinations of ST-A/PI with all other addons are released. No conflicts with any other support package or addon.
II. Implementation of supportpackages for addon ST-A/PI
Note: For the current 01T* version (>= basis 640) a support package SP02 becomes available as of 17th June 2019.
[For the older 01S* version support packages up to SP03 are available.]
For the 01Q* version, which is the valid version for customers <= basis 620, a supportpackage SP02 is available.
VI. Questions&Answers section
Symptom
As preparation for a SAP EarlyWatch/GoingLive session you want to implement the application-specific tools from SAP Support (Application monitor ST14, RTCCTOOL, ST12 and application specific SDCC data collectors).
Other Terms
ST-A/PI "Service Tools for Applications Plug-In",
SAP GoingLive, SAP EarlyWatch, Service preparation, RTCCTOOL,
Application monitor, Logistics Monitor, ST14,
Analyis&Service Tools Launchpad, ST13
ABAP Trace for EarlyWatch/GoingLive, ST12
SAP GoingLive, SAP EarlyWatch, Service preparation, RTCCTOOL,
Application monitor, Logistics Monitor, ST14,
Analyis&Service Tools Launchpad, ST13
ABAP Trace for EarlyWatch/GoingLive, ST12
Reason and Prerequisites
As of SAP release 4.0B, ST14 monitor & RTCCTOOL are delivered in one addon ST-A/PI "Service Tools for Applications Plug-In".
Only for older R/3 releases 3.0D-3.1I, ST14 and RTCCTOOL are still delivered as separate transports from sapserv3-7.
Only for older R/3 releases 3.0D-3.1I, ST14 and RTCCTOOL are still delivered as separate transports from sapserv3-7.
Note that the ST14 monitor and transactions ST12 and ST13 are not officially documented and are only released for use by SAP or certified Service consultants during SAP Service Sessions (for example SAP GoingLive Check or Solution Management Optimization Services). They are only available in English.
Solution
Contents
I. Implementation of addon ST-A/PI (for SAP releases >= 4.0B)
II. Implementation of supportpackages for addon ST-A/PI
III. Implementation of ST14 transport (for old SAP Releases <= 3.1I)
VI. Question&Answer section
II. Implementation of supportpackages for addon ST-A/PI
III. Implementation of ST14 transport (for old SAP Releases <= 3.1I)
VI. Question&Answer section
I. Implementation of addon ST-A/PI (for SAP releases >= 4.0B)
1. Select the proper ST-A/PI release
Note:
1) As of 17th June 2019 new addon support packages ST-A/PI 01T* SP02 become available.
2) As of 2014 new deliveries for lower basis releases <= 620 are discontinued. These customers should implement ST-A/PI 01Q* SP02 plus any note corrections recommended by RTCCTOOL.
3) On change from ST-A/PI >= 01Q* to >= 01R* some table contents will be migrated once (/SSF/PTAB->/SSF/BTAB).While this usually takes seconds, on few systems which are heavily using the BPMon functionality in SAP Solution Manager it can take 30min. During system upgrade the conversion is suppressed and runs afterwards "on first usage" (details see section 2d). On SolMan<=SP11 an additional SAP note 2046683 for ST-A/PI 01R* should be applied you use BPMon]
Use the matrix below to find the exact release (only 1) which is valid for your system. The release only depends on the SAP basis release. Application-dependent coding is included in comments (*) and is uncommented automatically during import.
2) As of 2014 new deliveries for lower basis releases <= 620 are discontinued. These customers should implement ST-A/PI 01Q* SP02 plus any note corrections recommended by RTCCTOOL.
3) On change from ST-A/PI >= 01Q* to >= 01R* some table contents will be migrated once (/SSF/PTAB->/SSF/BTAB).While this usually takes seconds, on few systems which are heavily using the BPMon functionality in SAP Solution Manager it can take 30min. During system upgrade the conversion is suppressed and runs afterwards "on first usage" (details see section 2d). On SolMan<=SP11 an additional SAP note 2046683 for ST-A/PI 01R* should be applied you use BPMon]
Use the matrix below to find the exact release (only 1) which is valid for your system. The release only depends on the SAP basis release. Application-dependent coding is included in comments (*) and is uncommented automatically during import.
SAP release
(SAP_BASIS) | further decisions based on installed software components (table CVERS) | Addon Release |
7.31
7.40 7.50 7.51 7.52 7.53 7.54 7.6x | for all systems on basis 7.31-7.69 | 01T_731 |
| 7.10 7.11 7.20 7.30 | for all systems on basis 7.10-7.30 (Netweaver 2007) | 01T_710 |
| 7.00 7.01 7.02 | for all systems on basis 7.00-7.02 | 01T_700 |
| 6.40 | for all systems on basis 640/Netweaver04 | 01T_640 |
| 6.20 | for all systems on 6.20 basis | 01Q_620 |
| 6.10 | for all systems on 6.10 basis | 01Q_610 |
| 4.6D | 01Q_46D | |
| 4.6C | 01Q_46C | |
| 4.6B | 01Q_46B | |
| 4.5B | 01Q_45B | |
| 4.0B | 01Q_40B |
2. Implementation
a) Verify SPAM/SAINT patch level
The only prerequisite for ST-A/PI is a minimum SPAM/SAINT level
- 39 for basis >= 700
- 16 for SAP basis release 6.10-6.40. See Q&A below for info how to implement a SPAM/SAINT update.
- 36 for SAP basis release 4.0B-4.6D
The only prerequisite for ST-A/PI is a minimum SPAM/SAINT level
- 39 for basis >= 700
- 16 for SAP basis release 6.10-6.40. See Q&A below for info how to implement a SPAM/SAINT update.
- 36 for SAP basis release 4.0B-4.6D
b) Download of ST-A/PI
Open http://support.sap.com/supporttools and click on 'Installations/Upgrades' below 'ST-A/PI' in the right-hand info. Select the proper addon release and 'Installation'. When the addon is displayed in the left area, click on 'Title' and download the file to your frontend PC. File size is 31-55 MB.
Also ST-A/PI addons for SAP Basis 700 and higher should be downloaded in the above way (only its support packages have to be donwloaded via maintenance optimizer).
Open http://support.sap.com/supporttools and click on 'Installations/Upgrades' below 'ST-A/PI' in the right-hand info. Select the proper addon release and 'Installation'. When the addon is displayed in the left area, click on 'Title' and download the file to your frontend PC. File size is 31-55 MB.
Also ST-A/PI addons for SAP Basis 700 and higher should be downloaded in the above way (only its support packages have to be donwloaded via maintenance optimizer).
c) Implementation with SAINT
ST-A/PI is easy to apply and does not interfere with productive coding. It can be implemented anytime and there is no necessity to logoff users. Warning popups regarding open BW data extraction requests can be ignored because the addon does not contain any BI data structures.
Call transaction SAINT in client 000. Choose 'Installation Package->Load Package->From frontend' to upload the addon file. (*)
The addon should now appear in the table control 'Installable addons', on the entry screen or after pressing the 'Start' button. EBP/CRM 4.00 and CRM 5.00-7.14 customers have to use the special addon manager via the menu. Mark the line with 'ST-A/PI' and choose 'Continue' several times to start the installation process. Installation takes about 15 minutes. Confirm with 'Finish'.
Then proceed with the next point 'Procedure after addon implementation'.
ST-A/PI is easy to apply and does not interfere with productive coding. It can be implemented anytime and there is no necessity to logoff users. Warning popups regarding open BW data extraction requests can be ignored because the addon does not contain any BI data structures.
Call transaction SAINT in client 000. Choose 'Installation Package->Load Package->From frontend' to upload the addon file. (*)
The addon should now appear in the table control 'Installable addons', on the entry screen or after pressing the 'Start' button. EBP/CRM 4.00 and CRM 5.00-7.14 customers have to use the special addon manager via the menu. Mark the line with 'ST-A/PI' and choose 'Continue' several times to start the installation process. Installation takes about 15 minutes. Confirm with 'Finish'.
Then proceed with the next point 'Procedure after addon implementation'.
(*) Tip: For subsequent systems which share the same transport directory, it is quicker to press the 'Load' button in SAINT and F3 'Back', i.e. upload from application server instead of from frontend.
Wait until installation finishes before starting the import into the next system.
Wait until installation finishes before starting the import into the next system.
[Error during Dictionary distribution or Import phase:
"Inconsistency DD <-> DB", "SSF/.." does not exist in nametab".
This may occur on the first ST-A/PI implementation after a combined upgrade with unicode conversion. On the first error press "Continue" in SAINT to proceed to the Main Import phase where SAINT stops again. Now run the newly imported utility report /SSF/SSF_TAB_ACT from SE38. After this SAINT finishs without error.]
"Inconsistency DD <-> DB", "SSF/.." does not exist in nametab".
This may occur on the first ST-A/PI implementation after a combined upgrade with unicode conversion. On the first error press "Continue" in SAINT to proceed to the Main Import phase where SAINT stops again. Now run the newly imported utility report /SSF/SSF_TAB_ACT from SE38. After this SAINT finishs without error.]
d) Procedure after addon implementation
As of ST-A/PI 01P* this step has been automated by an XPRA.
As of ST-A/PI 01P* this step has been automated by an XPRA.
ST-A/PI contains analysis coding in comments (*) for smaller software components (like BW, PI, SRM_SERVER, IBU Banking, FM/EA-PS, SEM-BW or IS-Utilities) or commented checks that require certain (basis) supportpackage levels (e.g. SDCC data collectors for MaxDB, DB2, DB6, Oracle). Conditions when the coding has to be uncommented are delivered together with the addon. From ST-A/PI 01P* this uncomment runs automatically as an XPRA during import. Runtime for the XPRA is 1-3 min. The uncomment procdure can also be started manually by starting report RTCCTOOL from SE38. If any analysis coding is to be uncommented RTCCTOOL will recommend this (takes two clicks from inside RTCCTOOL).
When changing to ST-A/PI >= 01R* a migration of table contents is triggered once (/SSF/PTAB->/SSF/BTAB). Reason is better performance and smaller data size (factor up to 15) due to digital compression in /SSF/BTAB. Usual runtime is < 1 min. However on a few customer systems that are heavily using the BPMon Business Process Monitoring functionality in SAP Solution Manager, table conversion can take 30 min or even more. Check the table size of /SSF/PTAB, conversion speed is roughly 1 GB per 8 min.
Conversion runs in an asynchronous dialog process [In the unlikely case /SSF/PTAB contains single packed objects large than 500 MB an additional background job may be triggered]. During system upgrade conversion is suppressed, in this case it is triggered automatically after upgrade "on first usage" of any ST-A/PI functionality.
Until the conversion is finished, ST-A/PI functionalities cannot be used, the processes will sleep/cancel after 5 min until conversion has finished. For very few large customers with heavy BPMon usage this may delay data collection. On the other hand those are the same customers that will most benefit from the data compression in the new table /SSF/BTAB.
Conversion runs in an asynchronous dialog process [In the unlikely case /SSF/PTAB contains single packed objects large than 500 MB an additional background job may be triggered]. During system upgrade conversion is suppressed, in this case it is triggered automatically after upgrade "on first usage" of any ST-A/PI functionality.
Until the conversion is finished, ST-A/PI functionalities cannot be used, the processes will sleep/cancel after 5 min until conversion has finished. For very few large customers with heavy BPMon usage this may delay data collection. On the other hand those are the same customers that will most benefit from the data compression in the new table /SSF/BTAB.
3. Upgrade behaviour
If you are already on the newest ST-A/PI release 01T *and* the target basis would require the very same ST-A/PI (e.g. upgrade basis 700->702) then
a) choose "KEEP".
Else as of ST-A/PI 01N* provide either the normal addon installation or the exchange upgrade package:
b) If your upgrade source system is
ERP >= 6.0
CRM/SCM/SRM >= 7.0
NetWeaver >= 7.0 (except upgrades to/from basis 7.10-7.30)
then the normal addon installation is required.
ERP >= 6.0
CRM/SCM/SRM >= 7.0
NetWeaver >= 7.0 (except upgrades to/from basis 7.10-7.30)
then the normal addon installation is required.
c) In other cases the exchange upgrade package is the proper choice. The upgrade exchange packages are
01T_700 SAPK-01TB7INSSA
01T_710 SAPK-01TB8INSSA
01T_731 SAPK-01TB9INSSA
01T_700 SAPK-01TB7INSSA
01T_710 SAPK-01TB8INSSA
01T_731 SAPK-01TB9INSSA
In case of doubt it is never wrong to provide even both installation and exchange upgrade package, the upgrade will pick the right one.
Put the upgrade package(s) into the EPS inbox prior to the IS_SELECT phase. In IS_SELECT choose "Upgrade with SAINT Package".
Put the upgrade package(s) into the EPS inbox prior to the IS_SELECT phase. In IS_SELECT choose "Upgrade with SAINT Package".
[For the upgrade behaviour of prior ST-A/PI releases <= 01M*
d) see SAP note 1570913.
In the very rare case of a upgrade to a basis older than 640
e) choose "DELETE":
This case should be rare. Since no upgrade packages are provided, choose "Passive deletion" (= "Delete the Addon. The tables are not deleted on the DB except if they are empty") whenever the upgrade asks you about
ST-A/PI. Like this the addon ST-A/PI gets lost just like standard coding during system upgrade.
After upgrade you may find messages like "Table /SSF/.. exists without DDIC reference" concerning service tool tables in the CHK_POSTUP phase or in DB02. These are harmless and most easily solved by implementing
ST-A/PI on the new release. Then run report RTCCTOOL and follow the recommendation 'Procedure after upgrade' (takes 2 clicks from inside the tool).]
This case should be rare. Since no upgrade packages are provided, choose "Passive deletion" (= "Delete the Addon. The tables are not deleted on the DB except if they are empty") whenever the upgrade asks you about
ST-A/PI. Like this the addon ST-A/PI gets lost just like standard coding during system upgrade.
After upgrade you may find messages like "Table /SSF/.. exists without DDIC reference" concerning service tool tables in the CHK_POSTUP phase or in DB02. These are harmless and most easily solved by implementing
ST-A/PI on the new release. Then run report RTCCTOOL and follow the recommendation 'Procedure after upgrade' (takes 2 clicks from inside the tool).]
4. Combination with other add-ons
All combinations of ST-A/PI with all other addons are released. No conflicts with any other support package or addon.
5. Impacted functionalities
To prevent any possibility of conflicts or interference with productive transactions, ST-A/PI objects are in independent separate namespaces /SSF/+/SSA/ (transaction codes ST12-ST14 and report sources RTCCTOOL+RSECNOTE are the only exception to this rule).
Therefore implementation of ST-A/PI cannot affect your business transactions and does not require a functional retest. The only areas that are updated are data collection for SAP Solution Manager (e.g. EarlyWatch, BPM in SolMan), transactions ST12-ST14 and RTCCTOOL+RSECNOTE.
As explained in section 2d) the table conversion /SSF/PTAB->/SSF/BTAB never runs during system upgrade with SUM/R3up and thus does not impact downtime.
To prevent any possibility of conflicts or interference with productive transactions, ST-A/PI objects are in independent separate namespaces /SSF/+/SSA/ (transaction codes ST12-ST14 and report sources RTCCTOOL+RSECNOTE are the only exception to this rule).
Therefore implementation of ST-A/PI cannot affect your business transactions and does not require a functional retest. The only areas that are updated are data collection for SAP Solution Manager (e.g. EarlyWatch, BPM in SolMan), transactions ST12-ST14 and RTCCTOOL+RSECNOTE.
As explained in section 2d) the table conversion /SSF/PTAB->/SSF/BTAB never runs during system upgrade with SUM/R3up and thus does not impact downtime.
6. Addon content info
The RTCCTOOL "Service preparation check" checks the availibility of required tools for a SAP service session. Run the report from SE38. The report connects to SAP Support Portal or SAPNet R/3 and fetches a list of recommendations and notes for your system configuration. It checks whether they are implemented successfully and presents a list of missing addons and notes. The list combines all necessary information such as SAP Notes, implementation status, short description & implementation text and transport logs. Helpful procedures regarding servicetools before/after upgrade are integrated into the tool and it can provide help for transport implementation.
As of ST-A/PI 01T* SP01 RTCCTOOL no longer creates its own RFC destination SAPNET_RTCC (copy of SAPOSS). Instead it reuses standard connectivity to SAP: Via HTTP destination SAP-SUPPORT_PORTAL to SAP Support Launchpad (as of SAP kernel 742), or via the SAPOSS RFC destination to SAPNet R/3. If those would not work RTCCTOOL automatically tries alternatives: via the old SAPNET_RTCC RFC destination, or indirectly via your Solution Manager system.
As of ST-A/PI 01L* the RTCCTOOL will also run in background during SDCC data collection. Service preparation recommendations are then visible also in the EWAlert report (from ST-SER 2008_2). A new "Settings" popup allows to show/hide additional recommendations for specific services (like e.g. Business Process Monitoring or Solution Transition). Activate those settings on request from SAP Support to prepare for an upcoming service.
The RTCCTOOL "Service preparation check" checks the availibility of required tools for a SAP service session. Run the report from SE38. The report connects to SAP Support Portal or SAPNet R/3 and fetches a list of recommendations and notes for your system configuration. It checks whether they are implemented successfully and presents a list of missing addons and notes. The list combines all necessary information such as SAP Notes, implementation status, short description & implementation text and transport logs. Helpful procedures regarding servicetools before/after upgrade are integrated into the tool and it can provide help for transport implementation.
As of ST-A/PI 01T* SP01 RTCCTOOL no longer creates its own RFC destination SAPNET_RTCC (copy of SAPOSS). Instead it reuses standard connectivity to SAP: Via HTTP destination SAP-SUPPORT_PORTAL to SAP Support Launchpad (as of SAP kernel 742), or via the SAPOSS RFC destination to SAPNet R/3. If those would not work RTCCTOOL automatically tries alternatives: via the old SAPNET_RTCC RFC destination, or indirectly via your Solution Manager system.
As of ST-A/PI 01L* the RTCCTOOL will also run in background during SDCC data collection. Service preparation recommendations are then visible also in the EWAlert report (from ST-SER 2008_2). A new "Settings" popup allows to show/hide additional recommendations for specific services (like e.g. Business Process Monitoring or Solution Transition). Activate those settings on request from SAP Support to prepare for an upcoming service.
As of April 2010 RTCCTOOL recommendations come with digital signatures attached. As of ST-A/PI 01M* you can activate digital verification of these signatures to make sure only authentic non-manipulated recommendations signed by SAP can be shown in RTCCTOOL or RSECNOTE. A PSE file SAP_AGS_OLCNT_VERIFY.pse will be created in DIR_INSTANCE/sec and an entry SAPAGS in transaction STRUST in client 000 (on SAP basis >= 620). The necessary certificates will be downloaded, verified and put into the same PSE file automatically. Fresh certificates may be added about once per year. The same PSE may be used in future to verify other online content from SAP AGS like SDCCN Service definitions or SAP Solution Manager Online content. Only digital verification is done, no cryprography.
Online input for data collection: As of ST-A/PI 01N* the same RTCCTOOL update mechanism delivers online input for certain data collectors that are generic, but their degree of freedom is limited in order to be secure. E.g. the DVM (data volume management) analyis tool receives an up-to-date list of what table(-field)s to analyze. The most advanced of these are SDCCN collector for Oracle and for HANA that can do selects on system tables based on online input. Examples for input are the automated Oracle parameter check (SAP note 1171650), the Oracle mini checks (SAP note 1695354) or the HANA mini checks (SAP note 2517313). The input SQL statements are a) digitally verified to come from SAP, b) security-checked to be strictly read-only ("set transaction read-only", syntaxcheck in brackets where 1=0 etc.), c) are logged into SDCCN download. Refresh period for this online input is 7 days, but it is also refreshed when you choose "List->Refresh from SAPNet" in RTCCTOOL.
Online collectors for BPMon/BPAnalytics data collection: As of ST-A/PI 01R* SP02 "Online monitors for BPMon/BPAnalytics" are introduced. They are also based on same RTCCTOOL update mechanism from SAPNet R/3. For these you can decide via transaction ST13->TBI_REPORTS_ONLINE_MONITORS_ADMI whether they should be updated automatically, or only manually plus on ST-A/PI update. As they are guranteed read-only and digitally signed, we regard them as generally safe and recommend to choose "Update automatically" to have always the newest and best version.
The online input is written in a restricted ABAP-like read-only language. Technically it is never passed to ABAP runtime. Instead it is a collector in addon ST-A/PI that receives it as input, parses it and processes it statement-wise. This design allows to assure a strict read-only, and to control what commands are allowed. Currently these are database selects SELECT and subsequent processing on internal data (calculations, conditionals IF, statements on internal tables). Digital content verification assures the content is from SAP (must be switched on in report RTCCTOOL as a precondition).
For convenience and to receive always the latest content and corrections, we recommend to allow automatic update. Drawbacks of this are theoretically:
-> a flawed correction might temporarily lead to missing data for an active monitor. We expect such cases to be resolved again quickly.
-> a functional correction to the where-clause (e.g. adding "where type = A or B") might slow down a join select if DB chooses another access path.
However both cases should occur very rarely.
Online input for data collection: As of ST-A/PI 01N* the same RTCCTOOL update mechanism delivers online input for certain data collectors that are generic, but their degree of freedom is limited in order to be secure. E.g. the DVM (data volume management) analyis tool receives an up-to-date list of what table(-field)s to analyze. The most advanced of these are SDCCN collector for Oracle and for HANA that can do selects on system tables based on online input. Examples for input are the automated Oracle parameter check (SAP note 1171650), the Oracle mini checks (SAP note 1695354) or the HANA mini checks (SAP note 2517313). The input SQL statements are a) digitally verified to come from SAP, b) security-checked to be strictly read-only ("set transaction read-only", syntaxcheck in brackets where 1=0 etc.), c) are logged into SDCCN download. Refresh period for this online input is 7 days, but it is also refreshed when you choose "List->Refresh from SAPNet" in RTCCTOOL.
Online collectors for BPMon/BPAnalytics data collection: As of ST-A/PI 01R* SP02 "Online monitors for BPMon/BPAnalytics" are introduced. They are also based on same RTCCTOOL update mechanism from SAPNet R/3. For these you can decide via transaction ST13->TBI_REPORTS_ONLINE_MONITORS_ADMI whether they should be updated automatically, or only manually plus on ST-A/PI update. As they are guranteed read-only and digitally signed, we regard them as generally safe and recommend to choose "Update automatically" to have always the newest and best version.
The online input is written in a restricted ABAP-like read-only language. Technically it is never passed to ABAP runtime. Instead it is a collector in addon ST-A/PI that receives it as input, parses it and processes it statement-wise. This design allows to assure a strict read-only, and to control what commands are allowed. Currently these are database selects SELECT and subsequent processing on internal data (calculations, conditionals IF, statements on internal tables). Digital content verification assures the content is from SAP (must be switched on in report RTCCTOOL as a precondition).
For convenience and to receive always the latest content and corrections, we recommend to allow automatic update. Drawbacks of this are theoretically:
-> a flawed correction might temporarily lead to missing data for an active monitor. We expect such cases to be resolved again quickly.
-> a functional correction to the where-clause (e.g. adding "where type = A or B") might slow down a join select if DB chooses another access path.
However both cases should occur very rarely.
Online collectors for SDCCN and SAP SolMan data collection: As of ST-A/PI 01T* SP0 online collectors can collect data for SDCCN data collection (e.g. EarlyWatch, EWAlert) or for SolMan (e.g. SolMan workcenter for DVM). Like the online collectors for BPMon they are read-only and digitally signed. They can select from database or call white-listed read-only function modules, process those data and pass them to SDCCN download or SolMan.
In Service preparation check RTCCTOOL via menu Goto->Online collectors you can decide whether to allow or disable online collectors.
In tx ST13 -> ONLINE_COLLECTORS_DEMO you see in detail how online collectors work, how online content commands are processed statement-wise by command form routines.
In tx ST13 -> ONLINE_COLLECTORS_EXE_LOG you see all online collector versions that have been executed in your system at least once.
SAP note 2530502 contains up-to-date info what data are collected by online collectors.
In Service preparation check RTCCTOOL via menu Goto->Online collectors you can decide whether to allow or disable online collectors.
In tx ST13 -> ONLINE_COLLECTORS_DEMO you see in detail how online collectors work, how online content commands are processed statement-wise by command form routines.
In tx ST13 -> ONLINE_COLLECTORS_EXE_LOG you see all online collector versions that have been executed in your system at least once.
SAP note 2530502 contains up-to-date info what data are collected by online collectors.
RSECNOTE "SAP Security Notes Check" checks whether the most important Security notes (http://support.sap.com/ alias /securitynotes) are implemented. See SAP note 888889 for details. However will be replaced by system recommendations (see SAP note 1890782).
The ST14 application monitor is mainly used during SAP GoingLive session. Analysis batch jobs collect performance-relevant key figures such as document statistics and customizing settings, the analysis results can be viewed as a tree and downloaded to a service session. The addons contains analyses for R/3 standard (SD PP MM CO Retail FI PS TR CA Data management FI-Funds Management), for APO and APO R/3 backend, for EBP/CRM and for industry solutions Banking, Utilities, Healthcare, IS-Public Sector Strategic Enterprise Management. From transaction ST13 "Analysis&Servicetools launchpad" the ITS trace viewer tool or analysis reports for EBP, APO Livecache, R/3 variant configuration or CO/FI can be started.Transaction ST12 "ABAP trace for EarlyWatch/GoingLive" allows to run ABAP traces like transaction SE30, but offers enhanced possibilities to switch on the trace (trace activation for another user, for incoming RFC; kernelpatch is required for this) or to evaluate the ABAP trace (buttom-up/top-down call hierarchy, internal table names etc.). ST12 is described in note 755977.
ST-A/PI also contains new data collectors for transaction SDCC which are relevant for SAP EarlyWatch/GoingLive/EarlyWatch Alert downloads. The addon contains SDCC data collectors for BW, SCM, CRM, XI, Security checks and databases.
The ST14 application monitor is mainly used during SAP GoingLive session. Analysis batch jobs collect performance-relevant key figures such as document statistics and customizing settings, the analysis results can be viewed as a tree and downloaded to a service session. The addons contains analyses for R/3 standard (SD PP MM CO Retail FI PS TR CA Data management FI-Funds Management), for APO and APO R/3 backend, for EBP/CRM and for industry solutions Banking, Utilities, Healthcare, IS-Public Sector Strategic Enterprise Management. From transaction ST13 "Analysis&Servicetools launchpad" the ITS trace viewer tool or analysis reports for EBP, APO Livecache, R/3 variant configuration or CO/FI can be started.Transaction ST12 "ABAP trace for EarlyWatch/GoingLive" allows to run ABAP traces like transaction SE30, but offers enhanced possibilities to switch on the trace (trace activation for another user, for incoming RFC; kernelpatch is required for this) or to evaluate the ABAP trace (buttom-up/top-down call hierarchy, internal table names etc.). ST12 is described in note 755977.
ST-A/PI also contains new data collectors for transaction SDCC which are relevant for SAP EarlyWatch/GoingLive/EarlyWatch Alert downloads. The addon contains SDCC data collectors for BW, SCM, CRM, XI, Security checks and databases.
II. Implementation of supportpackages for addon ST-A/PI
Note: For the current 01T* version (>= basis 640) a support package SP02 becomes available as of 17th June 2019.
[For the older 01S* version support packages up to SP03 are available.]
For the 01Q* version, which is the valid version for customers <= basis 620, a supportpackage SP02 is available.
a) Download of the ST-A/PI supportpackage
Path to the download is http://support.sap.com/supporttools and click on 'Support packages' below 'ST-A/PI' on the right-hand.
[Note that Addon installation and support packages are NOT found on the same download page but are different SWDC pages.].
File size is 35-44 MB. Supportpackages for SAP Basis 700 and higher have to be put to download basket and released via maintenance optimizer.
Path to the download is http://support.sap.com/supporttools and click on 'Support packages' below 'ST-A/PI' on the right-hand.
[Note that Addon installation and support packages are NOT found on the same download page but are different SWDC pages.].
File size is 35-44 MB. Supportpackages for SAP Basis 700 and higher have to be put to download basket and released via maintenance optimizer.
b) Implementation
Upload the support package to transaction SPAM, define a queue for 'ST-A/PI' and import. Import takes about 8 min.
Upload the support package to transaction SPAM, define a queue for 'ST-A/PI' and import. Import takes about 8 min.
************************************************************************
III. Implementation of ST14 transport (for very old SAP Releases <= 3.1I)
III. Implementation of ST14 transport (for very old SAP Releases <= 3.1I)
For R/3 Releases 3.0D-3.1I:
ST14 monitor and RTCCTOOL are delivered as separate transports from sapserv3-7.
See note 187939 for the implementation of RTCCTOOL for releases 3.0D-3.1I.
To implement the application monitor ST14, execute the following depending on your R/3 Release:
ST14 monitor and RTCCTOOL are delivered as separate transports from sapserv3-7.
See note 187939 for the implementation of RTCCTOOL for releases 3.0D-3.1I.
To implement the application monitor ST14, execute the following depending on your R/3 Release:
1. Release 3.0D-3.0E: Execute the following steps
a) Download the files for transport requests
EWSK000065 / TM1K000185 / EWSK000117
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release5/30de.
b) Import request EWSK000065 in accordance with Note 13719. You can ignore a return code 8 if it is only based on a generation error from Report BAM6GEN1, BAM6CGEN, SAPLV01B or SAPLBAXX.
c) Import request EWSK000117 according to Note 13719.
d) Execute report RSSTAT93.
e) Import request TM1K000185 in accordance with Note 13719.
2. Release 3.0F: Carry out the following steps
a) Download the files for transport requests
ARGK000073 / TM1K000185 / EWSK000152
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release5/30f.
b) Import request ARGK000073 in accordance with Note 13719. You can ignore a return code 8 if it is only based on a generation error from report BAM6GEN1 or BAM6CGEN.
c) Import request EWSK000152 in accordance to Note 13719.
d) Execute report RSSTAT93.
e) Import request TM1K000185 in accordance with Note 13719.
3. Release 3.1G: Execute the following steps
a) Download the files for transport requests
ARGK000135 / TM1K000321
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release6/31g.
b) Import request ARGK000135 in accordance with Note 13719. You can ignore a return code 8 if it is only based on a generating error from Report BAM6GEN1 or BAM6CGEN.
c) Execute report RSSTAT93.
d) Import request TM1K000321 in accordance with Note 13719.
4. Release 3.1H-3.1I: Execute the following steps
a) Download the files
KVSDA30.SAP
RVSDA30.SAP
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release11/31hi. These files contain the information on request SAPKVSDA30. The transport described in Note 127642 (RSCOLL00: Tuning the COLLECTOR_FOR_PERFORMANCEMONITOR) is also included in these transports.
As an alternative you can also download the file SAPKVSDA30.CAR and unpack it using the the SAP tool CAR in accordance with Note 29372. Use the command car -xvf <file name> to do so
b) Import request SAPKVSDA30 according to Note 13719. You can ignore a generation error in report RSFEA950 or BAM6GEN1. In case of generation problems with tables, use the utility report RTCCTABG from note 309711. Afterwards, re-import the transport again using tp import SAPKVSDA30 <SID> U126.
c) Afterwards, execute the two reports RSSTAT93 and RSWLPARA in Transaction SE38 one after the other (no parameters).
Background: The periodic workload collector RSCOLL00 reads its control parameters via the import of MONI. However, the transport can change the parameter structure and report RSWLPARA will convert to the new structure in order to prevent a possible conne_import_wrong_comp_type erro in program SAPLSTUW.
************************************************************************
a) Download the files for transport requests
EWSK000065 / TM1K000185 / EWSK000117
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release5/30de.
b) Import request EWSK000065 in accordance with Note 13719. You can ignore a return code 8 if it is only based on a generation error from Report BAM6GEN1, BAM6CGEN, SAPLV01B or SAPLBAXX.
c) Import request EWSK000117 according to Note 13719.
d) Execute report RSSTAT93.
e) Import request TM1K000185 in accordance with Note 13719.
2. Release 3.0F: Carry out the following steps
a) Download the files for transport requests
ARGK000073 / TM1K000185 / EWSK000152
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release5/30f.
b) Import request ARGK000073 in accordance with Note 13719. You can ignore a return code 8 if it is only based on a generation error from report BAM6GEN1 or BAM6CGEN.
c) Import request EWSK000152 in accordance to Note 13719.
d) Execute report RSSTAT93.
e) Import request TM1K000185 in accordance with Note 13719.
3. Release 3.1G: Execute the following steps
a) Download the files for transport requests
ARGK000135 / TM1K000321
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release6/31g.
b) Import request ARGK000135 in accordance with Note 13719. You can ignore a return code 8 if it is only based on a generating error from Report BAM6GEN1 or BAM6CGEN.
c) Execute report RSSTAT93.
d) Import request TM1K000321 in accordance with Note 13719.
4. Release 3.1H-3.1I: Execute the following steps
a) Download the files
KVSDA30.SAP
RVSDA30.SAP
from sapservX by anonymous ftp from the directory general/R3server/abap/note.0069455/release11/31hi. These files contain the information on request SAPKVSDA30. The transport described in Note 127642 (RSCOLL00: Tuning the COLLECTOR_FOR_PERFORMANCEMONITOR) is also included in these transports.
As an alternative you can also download the file SAPKVSDA30.CAR and unpack it using the the SAP tool CAR in accordance with Note 29372. Use the command car -xvf <file name> to do so
b) Import request SAPKVSDA30 according to Note 13719. You can ignore a generation error in report RSFEA950 or BAM6GEN1. In case of generation problems with tables, use the utility report RTCCTABG from note 309711. Afterwards, re-import the transport again using tp import SAPKVSDA30 <SID> U126.
c) Afterwards, execute the two reports RSSTAT93 and RSWLPARA in Transaction SE38 one after the other (no parameters).
Background: The periodic workload collector RSCOLL00 reads its control parameters via the import of MONI. However, the transport can change the parameter structure and report RSWLPARA will convert to the new structure in order to prevent a possible conne_import_wrong_comp_type erro in program SAPLSTUW.
************************************************************************
VI. Questions&Answers section
Q1: about ST-A/PI releases ?
A1: As of version 01P* all ST-A/PI releases depend only on the SAP basis release.
A1: As of version 01P* all ST-A/PI releases depend only on the SAP basis release.
Q2: how to delete an invalid ST-A/PI release from the SAINT 'Installable addons' overview ?
A2: In transaction SEPS choose Goto->Inbox and delete the addon file.
A2: In transaction SEPS choose Goto->Inbox and delete the addon file.
Q3: about SPAM/SAINT update ?
A3: To check the SPAM/SAINT level call transaction SPAM and look at the version in the title line. To implement a SPAM/SAINT update, open in your web browser http://support.sap.com/patches, choose "Browse our download catalog" -> "Additional components", drill down on 'SPAM/SAINT UPDATE' and download the files for the your basis release. In your system call transaction SPAM, choose 'Support package ->Load package->From frontend' to upload the file. Choose 'Support Package-> Import SPAM update' to start the import.
A3: To check the SPAM/SAINT level call transaction SPAM and look at the version in the title line. To implement a SPAM/SAINT update, open in your web browser http://support.sap.com/patches, choose "Browse our download catalog" -> "Additional components", drill down on 'SPAM/SAINT UPDATE' and download the files for the your basis release. In your system call transaction SPAM, choose 'Support package ->Load package->From frontend' to upload the file. Choose 'Support Package-> Import SPAM update' to start the import.
Q4: old servicetools transport implemented after addon ST-A/PI ?
A4: If you implement an old servicetool transport after implementation of ST-A/PI, either because supportpackagelevels for ST-PI are not met (note 560630) or by error, execute the following afterwards:
Run report /SSF/SAO_UTILS from SE38. On the selection screen choose 'Redirect entry points (ST14, RTCCTOOL)' and press 'Execute'.
A4: If you implement an old servicetool transport after implementation of ST-A/PI, either because supportpackagelevels for ST-PI are not met (note 560630) or by error, execute the following afterwards:
Run report /SSF/SAO_UTILS from SE38. On the selection screen choose 'Redirect entry points (ST14, RTCCTOOL)' and press 'Execute'.
Q5: on Solution Manager system ?
A5: The addon ST-A/PI should be implemented on the Solution Manager as well as on the satellite systems.
Q6: when calling report RTCCTOOL only a not very detailed 5 lines output shows up like for example
"Existence Text for Required TCC Tools"
"Version 03-12-1998"
"Note 091488 missing"
"Note 116095 missing" ?
A6: This is a very old version of RTCCTOOL which exists in basis standard as of 4.6A but which is no longer valid nor helpful.
Implement the above addon to get a valid version of RTCCTOOL.
A5: The addon ST-A/PI should be implemented on the Solution Manager as well as on the satellite systems.
Q6: when calling report RTCCTOOL only a not very detailed 5 lines output shows up like for example
"Existence Text for Required TCC Tools"
"Version 03-12-1998"
"Note 091488 missing"
"Note 116095 missing" ?
A6: This is a very old version of RTCCTOOL which exists in basis standard as of 4.6A but which is no longer valid nor helpful.
Implement the above addon to get a valid version of RTCCTOOL.
Q7: ST14 analysis results get lost ? (only for very old SAP release 3.0D-3.1I)
A7: ST14 analyses are saved into cluster table MONI area RELID = 'AA'. To prevent a too frequent reorganization of this area, make sure that the following entry is entered into the table SAPWLREORG (can be entered manually using transaction SE16-> 'Create' button):
ID = 'AA' / MONIKEY = '++++++++++++++<Date__>' /
RESIDENCY = '4' / DESCRIPTN = 'Application Analysis'
A7: ST14 analyses are saved into cluster table MONI area RELID = 'AA'. To prevent a too frequent reorganization of this area, make sure that the following entry is entered into the table SAPWLREORG (can be entered manually using transaction SE16-> 'Create' button):
ID = 'AA' / MONIKEY = '++++++++++++++<Date__>' /
RESIDENCY = '4' / DESCRIPTN = 'Application Analysis'
Q8: deactivate single ST14 analysis subroutine ?
A8: An ST14 analysis job calls a sequence of analysis subroutines. If one subroutine fails, proceed ad follows: from the short dump get the subroutine name (e.g. AFI_FI_SCAN_T685). Run report /SSA/AXM from SE38. On the selection screen, enter the first 3 letters of the subroutine name into parameter P_APPL and execute. In the left section 'ST14 customizing' choose 'Mapping: Assign analy. subroutines to GRPIDs' and press the button 'Change'. In the following tablecontrol deselect the 'Active' checkbox for analysis subroutine that should be skipped and press 'Save'.
Then schedule a new analysis from ST14.
A8: An ST14 analysis job calls a sequence of analysis subroutines. If one subroutine fails, proceed ad follows: from the short dump get the subroutine name (e.g. AFI_FI_SCAN_T685). Run report /SSA/AXM from SE38. On the selection screen, enter the first 3 letters of the subroutine name into parameter P_APPL and execute. In the left section 'ST14 customizing' choose 'Mapping: Assign analy. subroutines to GRPIDs' and press the button 'Change'. In the following tablecontrol deselect the 'Active' checkbox for analysis subroutine that should be skipped and press 'Save'.
Then schedule a new analysis from ST14.
Q9: Procedure for customers
a) using an internet VPN/SNC connection to sapserv1 or sapserv2
b) without RFC connection to sapserv ?
A9:
a) Customers with internet VPN/SNC connection cannot download transport files from sapserv via FTP. However, the most important service tools are available in SAP Support Portal http://support.sap.com/supporttools. These are especially the Addons for service preparation ST-PI (from note 116095) and ST-A/PI (this note 69455). Also many transport files for database monitors are available as attachment to SAP notes in SAP Services Marketplace. RFC connection to SAP is possible with VPN/SNC, so RTCCTOOL and ST14 download work as usual.
b) Customers without RFC connection to SAP can also get the tools for service preparation from SAP Services Marketplace. However, the service preparation check has to be done manually from note 91488 because RTCCTOOL does not work without RFC connection to SAP. Also the 'Procedure after implementation of addon ST-A/PI' (this note) is different: instead of starting RTCCTOOL, these customers should run report /SSF/SAO_UTILS from SE38 with option 'Uncomment/Recomment analyis coding for additional components'.
To transfer ST14 analyses from such a system, the textfile download (see Q10 below) should used.
a) using an internet VPN/SNC connection to sapserv1 or sapserv2
b) without RFC connection to sapserv ?
A9:
a) Customers with internet VPN/SNC connection cannot download transport files from sapserv via FTP. However, the most important service tools are available in SAP Support Portal http://support.sap.com/supporttools. These are especially the Addons for service preparation ST-PI (from note 116095) and ST-A/PI (this note 69455). Also many transport files for database monitors are available as attachment to SAP notes in SAP Services Marketplace. RFC connection to SAP is possible with VPN/SNC, so RTCCTOOL and ST14 download work as usual.
b) Customers without RFC connection to SAP can also get the tools for service preparation from SAP Services Marketplace. However, the service preparation check has to be done manually from note 91488 because RTCCTOOL does not work without RFC connection to SAP. Also the 'Procedure after implementation of addon ST-A/PI' (this note) is different: instead of starting RTCCTOOL, these customers should run report /SSF/SAO_UTILS from SE38 with option 'Uncomment/Recomment analyis coding for additional components'.
To transfer ST14 analyses from such a system, the textfile download (see Q10 below) should used.
Q10: Textfile download for ST14 analyses ?
A10: Choose transaction ST14, Utilities->Analysis browser. From the menu of the analysis browser you have the possibility to export a chosen 'GUID based' analysis to your frontend, or to upload a textfile with such an analysis to the system. Since the GUI menu is not completely translated to English in some of the current ST-A/PI addons, here the path: It is the first menu in the analysis browser and normally reads
Download > Download
Textfile download > Export to frontend
Import from frontend
A10: Choose transaction ST14, Utilities->Analysis browser. From the menu of the analysis browser you have the possibility to export a chosen 'GUID based' analysis to your frontend, or to upload a textfile with such an analysis to the system. Since the GUI menu is not completely translated to English in some of the current ST-A/PI addons, here the path: It is the first menu in the analysis browser and normally reads
Download > Download
Textfile download > Export to frontend
Import from frontend
Q11: Error analysis for SDCC data collectors in ST-A/PI ?
A11: Two error situations are possible:
a) short dumps in one data collector
b) customer forgot to uncomment data collectors
In case a) an error message would appear in the download message log in transaction SDCC for the function module SSF_COLLECT_DATA_FOR_SDCC. In such a case also the data from other SDCC data collectors in ST-A/PI are missing.
Proceed as follows:
-> repeat the SDCC data collection max. two more times, until the eror message has disappeared from the SDCC message log. The errous data collector is locked after two short dumps, so the third execution should run through and contain data from the other SDCC data collectors in ST-A/PI.
-> open a customer message on SV-GST-SDD to inform the developer about the short dump.
To detect locked data collectors in a download, use the "Viewer for ST-A/PI data in the SDCC download". It can be reached via transaction ST13->SDCCVIEWER, or transaction DCT_STAPI_V in the SAP internal service system CTP. Click on the nodes <context>->XAD->DATACOLL_MSG_LOG->SUBROUTINE_LOGS if available.
A message 'Lock entry DEACT exists' means that the collector was locked due to short dumps. To unlock a data collector, use ST13->PROJBROWSER.
An error of type b) can happen if the customer forgets the 'Procedure after implementation of addon ST-A/PI' described some pages above.
To detect an error case b) in the download, look into the same SUBROUTINE_LOGS as for error case a), but look for a message 'Lock entry CMTD exists'. In such a case the customer simply has to run report RTCCTOOL and follow the recommendation to uncomment the analysis coding (takes two clicks from inside RTCCTOOL ). Info about the ST-A/PI release in the download can be found in the same viewer under path DATA_PER_R3SYSTEM->DCA->GENERAL.
A11: Two error situations are possible:
a) short dumps in one data collector
b) customer forgot to uncomment data collectors
In case a) an error message would appear in the download message log in transaction SDCC for the function module SSF_COLLECT_DATA_FOR_SDCC. In such a case also the data from other SDCC data collectors in ST-A/PI are missing.
Proceed as follows:
-> repeat the SDCC data collection max. two more times, until the eror message has disappeared from the SDCC message log. The errous data collector is locked after two short dumps, so the third execution should run through and contain data from the other SDCC data collectors in ST-A/PI.
-> open a customer message on SV-GST-SDD to inform the developer about the short dump.
To detect locked data collectors in a download, use the "Viewer for ST-A/PI data in the SDCC download". It can be reached via transaction ST13->SDCCVIEWER, or transaction DCT_STAPI_V in the SAP internal service system CTP. Click on the nodes <context>->XAD->DATACOLL_MSG_LOG->SUBROUTINE_LOGS if available.
A message 'Lock entry DEACT exists' means that the collector was locked due to short dumps. To unlock a data collector, use ST13->PROJBROWSER.
An error of type b) can happen if the customer forgets the 'Procedure after implementation of addon ST-A/PI' described some pages above.
To detect an error case b) in the download, look into the same SUBROUTINE_LOGS as for error case a), but look for a message 'Lock entry CMTD exists'. In such a case the customer simply has to run report RTCCTOOL and follow the recommendation to uncomment the analysis coding (takes two clicks from inside RTCCTOOL ). Info about the ST-A/PI release in the download can be found in the same viewer under path DATA_PER_R3SYSTEM->DCA->GENERAL.
Q12: Known problems with SDCC data collectors in ST-A/PI ?
A12: The following data collectors of the older 01F* version may cause dumps during data collection in certain system configurations:
Form DDB_ORA_GET_UNDO_STATS
This can occur on an APO/SCM system with Oracle database. The error is caused by other data collectors that run before and do not reset the DB connection. Therefore the solution is to deactivate the following two data collectors:
Form DAP_LC_SEL_CONFIGURATION
Form DAP_LC_SEL_CLASSCONTAINERS_FCT
To deactivate them, run report /SSA/DXM from SE38.
Enter 'DAP' for parameter P_PROJID.
Select 'Declare subroutines for SDCC download' and press 'Change'.
Look for the two subroutines in the list and deselect the 'Active' checkbox for these two subroutines. Then press 'Save'.
Then the two data collectors will not be called anymore by SDCC. These errors will be corrected in the next version of ST-A/PI.
A12: The following data collectors of the older 01F* version may cause dumps during data collection in certain system configurations:
Form DDB_ORA_GET_UNDO_STATS
This can occur on an APO/SCM system with Oracle database. The error is caused by other data collectors that run before and do not reset the DB connection. Therefore the solution is to deactivate the following two data collectors:
Form DAP_LC_SEL_CONFIGURATION
Form DAP_LC_SEL_CLASSCONTAINERS_FCT
To deactivate them, run report /SSA/DXM from SE38.
Enter 'DAP' for parameter P_PROJID.
Select 'Declare subroutines for SDCC download' and press 'Change'.
Look for the two subroutines in the list and deselect the 'Active' checkbox for these two subroutines. Then press 'Save'.
Then the two data collectors will not be called anymore by SDCC. These errors will be corrected in the next version of ST-A/PI.
Q13: Transport names of current addons
A13: Transport name Addon Release
SAPKITAR1J ST-A/PI 01Q_40B
SAPKITAR2J ST-A/PI 01Q_45B
SAPKITAB1J ST-A/PI 01Q_46B
SAPKITAB2J ST-A/PI 01Q_46C
SAPKITAB3J ST-A/PI 01Q_46D
SAPKITAB4J ST-A/PI 01Q_610
SAPKITAB5J ST-A/PI 01Q_620
SAPKITAB6U ST-A/PI 01T_640
SAPKITAB7U ST-A/PI 01T_700
SAPKITAB8U ST-A/PI 01T_710
SAPKITAB9U ST-A/PI 01T_731
A13: Transport name Addon Release
SAPKITAR1J ST-A/PI 01Q_40B
SAPKITAR2J ST-A/PI 01Q_45B
SAPKITAB1J ST-A/PI 01Q_46B
SAPKITAB2J ST-A/PI 01Q_46C
SAPKITAB3J ST-A/PI 01Q_46D
SAPKITAB4J ST-A/PI 01Q_610
SAPKITAB5J ST-A/PI 01Q_620
SAPKITAB6U ST-A/PI 01T_640
SAPKITAB7U ST-A/PI 01T_700
SAPKITAB8U ST-A/PI 01T_710
SAPKITAB9U ST-A/PI 01T_731
Q14: "Last run of report RTCCTOOL" in EWAlert too old
A14: May occur if the satellite system is on ST-A/PI >=01L but Solution Manager does not yet have the ST-SER 701_2008_2 (both as of December 2008). RTCCTOOL was enhanced as of ST-A/PI 01L to deliver the full recommendations to the EWAlert, but the older Solution Manager release does not yet understand this.
As a workaround run report RTCCTOOL from Tx SE38 and choose Goto->Old RTCCTOOL from the menu. This runs the old tool, which should now also return green status lights for everything that's up to date. The next EWA ( with your current ST-SER) takes this info from the old tool into account.
As a permanent solution, update your Solution Manager to EhP1 (ST 400 SP18, ST-SER 701_2008_2).
Q15: Unicode conversion - Invalid (non ASCII-7) chars in /SSF/DTAB
A15: /SSF/DTAB contains mainly application or pre-upgrade analyses from transaction ST14. Please verify that no SAP Service is currently still ongoing. As soon as the service is done, the data can be deleted from /SSF/DTAB.
To delete them, Call transaction ST14->Utilities-> Delete old analyses->Set a date in the future.
Q16: ST-A/PI not offered for reimplementation in SAINT after upgrade
A16: This may occur if you have chosen "Passive deletion" instead of "Keep with vendor key" in an upgrade with minor or no change in basis release (e.g. CRM 500 to 701, SCM 500 to 701; see above).
Check with transaction SE16. Display table PAT03 with criteria
ADDON_ID = ST-A/PI and ADDON_REL like 01N*.
If you find an entry
PATCH SAPKITAxxx
STATUS I
CONFIRMED X
ADDON ID ST-A/PI
ADDON REL <the release you want to reimplement e.g. 01N_700CRM>
then open a customer message on BC-UPG-ADDON with reference to this note and Q16 and request that this addon should be allowed for reinstallation.
A14: May occur if the satellite system is on ST-A/PI >=01L but Solution Manager does not yet have the ST-SER 701_2008_2 (both as of December 2008). RTCCTOOL was enhanced as of ST-A/PI 01L to deliver the full recommendations to the EWAlert, but the older Solution Manager release does not yet understand this.
As a workaround run report RTCCTOOL from Tx SE38 and choose Goto->Old RTCCTOOL from the menu. This runs the old tool, which should now also return green status lights for everything that's up to date. The next EWA ( with your current ST-SER) takes this info from the old tool into account.
As a permanent solution, update your Solution Manager to EhP1 (ST 400 SP18, ST-SER 701_2008_2).
Q15: Unicode conversion - Invalid (non ASCII-7) chars in /SSF/DTAB
A15: /SSF/DTAB contains mainly application or pre-upgrade analyses from transaction ST14. Please verify that no SAP Service is currently still ongoing. As soon as the service is done, the data can be deleted from /SSF/DTAB.
To delete them, Call transaction ST14->Utilities-> Delete old analyses->Set a date in the future.
Q16: ST-A/PI not offered for reimplementation in SAINT after upgrade
A16: This may occur if you have chosen "Passive deletion" instead of "Keep with vendor key" in an upgrade with minor or no change in basis release (e.g. CRM 500 to 701, SCM 500 to 701; see above).
Check with transaction SE16. Display table PAT03 with criteria
ADDON_ID = ST-A/PI and ADDON_REL like 01N*.
If you find an entry
PATCH SAPKITAxxx
STATUS I
CONFIRMED X
ADDON ID ST-A/PI
ADDON REL <the release you want to reimplement e.g. 01N_700CRM>
then open a customer message on BC-UPG-ADDON with reference to this note and Q16 and request that this addon should be allowed for reinstallation.
Q17: Key check error in upgrade RUN_RDDIT006_PRE for /SSF/PTAB keys
A17: This may occur if you KEEP an older ST-A/PI version 01K* or lower during the upgrade. As above you should instead update to the new 01N* as target release.
Alternatively you may also manually delete some E071K entries. Determine the transport for your ST-A/PI release, e.g. SAPKITAB7C for ST-A/PI 01K_BCO700. Then use SE16 to display table entries for table E071K. Enter filter critetia TRKORR = transport name (e.g. SAPKITAB7C) and TABKEY = *_* (as pattern). Execute.
This should select about the following 16 entries:
TRKORR PGMID OBJECT OBJNAME
SAPKITAB7C R3TR TABU /SSF/PTAB
A17: This may occur if you KEEP an older ST-A/PI version 01K* or lower during the upgrade. As above you should instead update to the new 01N* as target release.
Alternatively you may also manually delete some E071K entries. Determine the transport for your ST-A/PI release, e.g. SAPKITAB7C for ST-A/PI 01K_BCO700. Then use SE16 to display table entries for table E071K. Enter filter critetia TRKORR = transport name (e.g. SAPKITAB7C) and TABKEY = *_* (as pattern). Execute.
This should select about the following 16 entries:
TRKORR PGMID OBJECT OBJNAME
SAPKITAB7C R3TR TABU /SSF/PTAB
with the following values for field TABKEY:
TCABOCOUNT_ENTRIES *
TCABOHINT_MODE *
TCABOINPUT_STAT4 *
TCABOINPUT_STAT6 *
TCABOTAANA_VAR *
TCABOTABLE_TAANA *
TCCMMCUST_BOLL *
TCCMMCUST_FICA *
TCCMMCUST_MAIN *
TCCMMPERF_TABS *
TCEBOVH_PHASES *
TCEIMVH_PHASES *
TCRTCSETTINGS LAST_SAPNET_REFRESH *
TCRTCSETTINGS SETTINGS_ENTERED *
TCSTXSE30_CUST *
TCSTXSQLR_CUST *
Select the entries and choose "Delete all". Deleting those entries from E071K will do no harm.
TCABOCOUNT_ENTRIES *
TCABOHINT_MODE *
TCABOINPUT_STAT4 *
TCABOINPUT_STAT6 *
TCABOTAANA_VAR *
TCABOTABLE_TAANA *
TCCMMCUST_BOLL *
TCCMMCUST_FICA *
TCCMMCUST_MAIN *
TCCMMPERF_TABS *
TCEBOVH_PHASES *
TCEIMVH_PHASES *
TCRTCSETTINGS LAST_SAPNET_REFRESH *
TCRTCSETTINGS SETTINGS_ENTERED *
TCSTXSE30_CUST *
TCSTXSQLR_CUST *
Select the entries and choose "Delete all". Deleting those entries from E071K will do no harm.
Q18: Full refresh of RTCCTOOL recommendations customizing ?
A18: Run report RTCCTOOL from SE38. From the menu choose List->Other utilities -> Forced full refresh from SAPNet.
[If this menu point is not available on older releases, do the following instead:
Run report /SSA/NXS from SE38. Choose [Clear all local recommendations to force a full refresh] and press F8 Execute.
Run RTCCTOOL from SE38. Choose List->Refresh from SAPNet. This takes just a few seconds more than usual.
Go completely out of RTCCTOOL and once more restart RTCCTOL from SE38. Then the fully refreshed recommendations should appear.
As of ST-A/PI 01N* SP01 choose "List->Other utilities->Forced full refresh from SAPNet".]
A18: Run report RTCCTOOL from SE38. From the menu choose List->Other utilities -> Forced full refresh from SAPNet.
[If this menu point is not available on older releases, do the following instead:
Run report /SSA/NXS from SE38. Choose [Clear all local recommendations to force a full refresh] and press F8 Execute.
Run RTCCTOOL from SE38. Choose List->Refresh from SAPNet. This takes just a few seconds more than usual.
Go completely out of RTCCTOOL and once more restart RTCCTOL from SE38. Then the fully refreshed recommendations should appear.
As of ST-A/PI 01N* SP01 choose "List->Other utilities->Forced full refresh from SAPNet".]
Q19: Vendor keys for ST-A/PI ?
A19: usually you should not need vendor keys to keep ST-A/PI. However, vendor keys for the SAPehpi installer/SUM and for other upgrades with SAPup are
A19: usually you should not need vendor keys to keep ST-A/PI. However, vendor keys for the SAPehpi installer/SUM and for other upgrades with SAPup are
| Target Basis | Key for SAPehpi/SUM | Key for SAPup |
| 700 | 2050448 | 3037227 |
| 701 | 1271425 | 2552828 |
| 702 | 1671774 | 2069453 |
| 703 | 1679426 | 3944055 |
| 730 | 1807471 | 2960991 |
| 731 | 1684309 | 2760676 |
| 732 | 2085170 | 2822245 |
| 740 | 809161 | 2902571 |
| 750 | 728339 |
2319360
|
| 751 | 735735 |
3167604
|
| 752 | 1136596 |
2836732
|
| 753 | 1537201 |
2635905
|
Software Components
| Software Component | From | To | And Subsequent |
|---|---|---|---|
| SAP_APPL | 40B | 40B | |
| SAP_APPL | 45A | 45B | |
| SAP_APPL | 46B | 46B | |
| SAP_APPL | 46C | 46C | |
| SAP_APPL | 470 | 470 | |
| SAP_APPL | 500 | 500 | |
| SAP_APPL | 600 | 600 | |
| SAP_APPL | 602 | 602 | |
| SAP_APPL | 603 | 603 | |
| SAP_APPL | 604 | 604 | |
| SAP_APPL | 605 | 605 | |
| SAP_APPL | 606 | 606 | |
| SAP_APPL | 616 | 616 | |
| SAP_APO | 310 | 310 | |
| SAP_BASIS | 46A | 46D | |
| SAP_BASIS | 610 | 640 | |
| SAP_BASIS | 700 | 702 | |
| SAP_BASIS | 710 | 730 | |
| SAP_BASIS | 731 | 731 | |
| SAP_BASIS | 740 | 740 | |
| SCM | 410 | 410 | |
| SCM | 500 | 500 | |
| SCM | 510 | 510 | |
| SCM | 700 | 700 | |
| SCM | 701 | 701 | |
| SCM | 702 | 702 | |
| SCM | 712 | 712 | |
| BBPCRM | 300 | 300 | |
| BBPCRM | 310 | 310 | |
| BBPCRM | 350 | 350 | |
| BBPCRM | 500 | 500 | |
| BBPCRM | 510 | 510 | |
| BBPCRM | 520 | 520 | |
| BBPCRM | 600 | 600 | |
| BBPCRM | 700 | 700 | |
| BBPCRM | 701 | 701 | |
| BBPCRM | 702 | 702 | |
| BBPCRM | 712 | 712 |
