Search This Blog

Monday, January 23, 2012

SAP Note 69455 - Servicetools for Applications ST-API (ST14, RTCCTOOL, ST12)


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



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.

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

I. Implementation of addon ST-A/PI (for SAP releases >= 4.0B)
    1. Select the proper ST-A/PI release
Note: As of 21st March 2011 a new addon version 01N* of addon ST-A/PI has become available. The upgrade behaviour has been changed to standard and release names have been adjusted by basis release. There is a dedicated addon for SAP Solution Manager which is available as addon upgrade only. For the addons on SAP basis >= 640 a supportpackage SP01 has become available on 21st November 2011.

Use the matrix below to find the exact release (only 1) which is valid for your system. If you are unsure, display the content of table CVERS on your system in transaction SE16, check your SAP_BASIS release and look for components SAP_APPL, BBPCRM, SAP_APO or SCM. If you find one of the entries in brackets (), take the corresponding addon release, else take the 01N_xxx_BCO that matches your SAP_BASIS release. You cannot implement any wrong release, it would be refused by transaction SAINT with 'Prerequisites not met'.
Example: For a R/3 standard system (SD,MM,CO,HR, CVERS component SAP_APPL exists) a ST-A/PI release like 01N_xxx_R3 is the proper choice.
  SAP release   further decisions based on installed   ->  Addon
  (SAP_BASIS)   software components (table CVERS)          Release
|--------------------------------------------------------------------|
|   4.0B    |                                          -> 01N_40B_R3 |
|--------------------------------------------------------------------|
|   4.5B    |                                          -> 01N_45B_R3 |
|--------------------------------------------------------------------|
|   4.6B    | for R/3 standard 4.6B  (SAP_APPL 46B)    -> 01N_46B_R3 |
|           | for all other systems on 4.6B basis      -> 01N_46BBCO |
|--------------------------------------------------------------------|
|   4.6C    | for R/3 standard 4.6C  (SAP_APPL 46C)    -> 01N_46C_R3 |
|           | for APO 3.0A  (SAP_APO 30A)              -> 01N_46CAPO |
|           | for all other systems on 4.6C basis      -> 01N_46CBCO |
|--------------------------------------------------------------------|
|   4.6D    | for APO 3.10  (SAP_APO 310)              -> 01N_46DAPO |
|           | for all other systems on 4.6D basis      -> 01N_46DBCO |
|--------------------------------------------------------------------|
|   6.10    | for EBP/CRM 3.00  (BBPCRM 300)           -> 01N_610CRM |
|           | for all other systems on 6.10 basis      -> 01N_610BCO |
|--------------------------------------------------------------------|
|   6.20    | for R/3 Enterprise 4.70 (SAP_APPL 470)   -> 01N_620_R3 |
|           | for CRM 3.1 or EBP 3.5  (BBPCRM 310/350) -> 01N_620CR3 |
|           | for EBP/CRM 4.00   (BBPCRM 400)          -> 01N_620CR4 |
|           | for SCM (APO) 4.00   (SCM 400)           -> 01N_620SCM |
|           | for all other systems on 6.20 basis      -> 01N_620BCO |
|--------------------------------------------------------------------|
|   6.40    | for ERP 2004/ECC 5.00  (SAP_APPL 500)    -> 01N_640ECC |
|           | for SCM (APO) 4.10   (SCM 4.10)          -> 01N_640SCM |
|           | for all other systems on 640/Netweaver04 -> 01N_640BCO |
|--------------------------------------------------------------------|
|   7.00    | for ERP2005/ECC 6.0x  (SAP_APPL 60x)     -> 01N_700ECC |
|   7.01    | for SCM 5.00-7.0x  (SCM 500-70x)         -> 01N_700SCM |
|   7.02    | for CRM 5.00-7.0x                        -> 01N_700CRM |
|   7.31    |  (BBPCRM 500-70x but no Solution Manager)              |
|           | for SAP Solution Manager 4.0-7.10        -> 01N_700SOL |
|           |  (ST 400-710; take the addon upgrade pack.)            |
|           | for all other systems on 700-702 or 731  -> 01N_700BCO |
----------------------------------------------------------------------
|   7.10    | for all systems on Netweaver 2007        -> 01N_710BCO |
|   7.11    |   up to SAP basis 7.30                                 |
|   7.20    |                                                        |
|   7.30    |                                                        |
----------------------------------------------------------------------
|   7.31    |   see the 7.00-7.02+7.31 section above   -> 01N_700*   |
----------------------------------------------------------------------





Read the Full version of this note @ https://service.sap.com/sap/support/notes/69455

1 comment:

  1. your way of explanation of SAP APO is very fantastic.you mention in article lot of information varies types of SAP APO, thanks for given information. Well done keep it up and we are providing SAP APO Online Training on all modules latest courses

    ReplyDelete