4 Replies Latest reply: Mar 24, 2009 5:14 PM by Guest RSS

Apply ST-PI and ST-A/PI

jason xu
Currently Being Moderated

Dear Gurus,


I want to apply ST-PI and ST-A/PI in our ECC DEV system.

I am not familier with the using of 'SAINT'.

Could you tell me the steps ?





Target system__|Component__Current release__Current patch level____Target release


ECC DEV           ST-PI                 2005_1_700                  4          2008_1_700

ECC DEV          ST-A/PI           01K_ECC600                 0          01L_ECC600






  • Re: Apply ST-PI and ST-A/PI
    Chetan Seth
    Currently Being Moderated

    Hi Jason


    also please check the following links:



    1. SAP recommendation

    We recommend you to always import the latest version of the SPAM/SAINT update before you import installation packages. It is also a good idea to download the latest versions of executables tp and R3trans from a sapserv# application server (see Note 19466).


    If you are using several application servers, make sure that profile parameter rdisp/bufrefmode is set to sendon,exeauto, and if you are using only one application server, make sure that the profile parameter is set to sendoff,exeauto. Otherwise, you only have the option of executing the "/$sync" command to make the changes become completely effective after the installation.


    2. Known problems and solutions


    Termination in the XPRA_EXECUTION step (TP_FAILURE)

               Symptom: A termination occurs when you import an add-on or a preconfigured system (PCS). The fplowing dialog box appears:


    Error in step: XPRA_EXECUTION

    Cause of error: TP_FAILURE

    Return code: 0204

    Error message: parameter is missing


               Solution: If you encounter this error, proceed as described in Note 537881.


    SPAM/SAINT - Version 0003 - Version 0008

               Symptom: User exits are deactivated after you import an installation queue. Only user exists are affected, however, that are contained in inactive CMOD enhancement projects.


               Reason: With SPAM/SAINT Version 0003, an automatic import reprocessing was implemented that automatically reactivates any user exits that may have been deactivated during the import (see Note 402972). In the first version of this postprocessing, the case not supported by SAP that there may be active user exits in inactive CMOD enhancement projects has not been taken into account correctly. Therefore, when restoring the consistency of the customer enhancements, all user exits in inactive CMOD enhancement projects are deactivated.


               Solution: If the given case has occurred in your system (active user exits in inactive CMOD enhancement projects), please check whether the implementation of the user exits can be changed to the SAP standard case (active user exits only in active CMOD enhancement projects or inactive user exits only in inactive CMOD enhancement projects).

    In addition, the import postprocessing in SPAM/SAINT Version 0009 was enhanced so that all combinations of the user exit status and the enhancement project status are now correctly dealt with.


    SPAM/SAINT - Version 0013

               Symptom: An error occurs in the phase ADD_SYNCMARKS when you import an installation queue. The action log contains the fplowing tp message:

    tp finished with return code: 200

    Not exactly one SYNCMARK set; buffer unchanged!


               You also find the same error message in SLOG.


               Reason: The enhanced transport contrp is activated in the TMS (tp parameter CTC=1 is set in the transport profile). The tp command line used in SPAM/SAINT Version 0013 to set SYNCMARKs does not work in this case.


               Solution: The problem is spved in SPAM/SAINT - Version 0014.

    Use 'Back' to delete the installation queue in SAINT. Then import the SPAM/SAINT update - Version 0014 (or higher) in the Support Package Manager. Then restart the installation in SAINT.


    SPAM/SAINT Version 0016: Incorrect Support Package proposals

               Symptom: As of Version 0016, you can link additional Support Packages to an add-on installation queue. When you upgrade an add-on, the system determines (in the same way as for system upgrades) which Support Packages need to be included for the target add-on release based on the Support Packages that have been imported for the add-on source release to achieve the same maintenance state. In SPAM/SAINT Version 0016, a program error means that the system does not just determine this for the add-on contained in the upgrade, but for all components. As a result, you may find that Support Packages that should not be imported at all have been preselected on the Support Package selection screen. It is easy to undo this preselection using the relevant dropdown fields. However, if you overlook this preselection, the selected Support Packages are included in the installation queue and then imported once the import conditions have been met.


               Solution: SPAM/SAINT Version 0017 corrects this problem.

    When you use SPAM/SAINT Version 0016, you should always check carefully which Support Packages have been selected for the individual components on the Support Package selection screen, and if necessary, undo any incorrect preselections.


    SPAM/SAINT Versions 0016, 0017: Unauthorized Support Packages in the queue

               Symptom: As of Version 0016, you can add further Support Packages to an add-on upgrade queue. If the Support Packages you are adding require Support Packages of the pd release in your system for the add-on you are upgrading, these Support Packages that belong to the pd system may be sorted after the add-on installation/upgrade package. This is incorrect and means that after importing this queue, the add-on is inconsistent.

    Note that sorting before the installation/upgrade package is correct and is not an error.


               Solution: The problem is spved with SPAM/SAINT Version 0018.

    When you use SPAM/SAINT Version 0016 or 0017, before you begin the import, carefully check whether the Support Packages of the pd release for the add-on you are upgrading have been sorted after the add-on installation/upgrade. If this is the case, do not import this queue. In this instance, only import the actual installation/upgrade queue without the added Support Packages. The additional Support Packages should then be imported with the Support Package Manager in a second step.


    Problems with R3trans patch level 1848 (SAP Kernel 6.20) and patch level 62 (SAP Kernel 6.40)

               Symptom: If you use R3trans with patch level 1848 (SAP Kernel 6.20) or patch level 62 (SAP Kernel 6.40) (see R3trans -v) to import OCS packages, the import may terminate when you activate the DDIC or when you execute the after-import method. Error messages of the fplowing type appear in the logs:

    LANG DTEL * Object information could not be imported

    LANG TABL * Object information could not be imported


    Object "..." "..." has not yet been imported successfully


               Solution: Do NOT use R3trans with patch level 1848 (SAP Kernel 6.20) or patch level 62 (SAP Kernel 6.40) to import a SAINT queue.

    If you have already encountered these errors, it is no longer sufficient to simply change the R3trans. In this case, contact SAP Support (component BC-UPG-OCS).


    Usage of a 6.40 kernel with a database of the family IBM DB2

               Symptom: When you import Support Packages to use a 6. 40 kernel on an IBM DB2 database, in some circumstances problems can occur with the buffer synchronization.


               Solution: Refer to Note 841938 and only use the kernel and transportation top versions recommended there.


    Downtime-minimized import only with R3trans from December 06, 2005 (or later)

               The downtime-minimized import mode in the Add-on Installation Top may only be used with an R3trans version from December 06, 2005 (or later). If you use an pder R3trans version, ABAP Object methods may not be imported correctly. Note 906008 describes this phenomenon and the symptoms that occur.

    As of Version 0020, the Add-On Installation Top checks whether the minimum R3trans version exists.


    "SAPCAR error: format error in header" when extracting an SAR archive

               Symptom: When you unpack an SAR archive, the SAPCAR utility terminates with the error message "SAPCAR error: format error in header".


               Reason: The SAR archive was packed using SAPCAR Version 700. Since changes were made to the SAR archive format in this version, pder SAPCAR versions can no longer unpack the archive (also refer to SAP Note 892842).


               Solution: Use SAPCAR Version 700 or SAPCAR Version 640 patch level 4. These versions can process the new archive format (refer to SAP Note 892842).


    SAR archives cannot be loaded and unpacked using the function "Load from front end"

               Symptom: You want to unpack an SAR archive using the function "Load from front end". The system refuses the archive with the message "File '???.SAR' is not a CAR or SAPCAR file'.


               Reason: The SAR archive was packed using SAPCAR Version 700. Since changes were made to the SAR archive format in this version, and the archive format versions were also changed, the Support Package Manger does not recognize the file as a valid SAR archive.


               Solution: SPAM/SAINT Version 620/0020 contains an adjustment to the new SAR archive format. Note that you may require a new SAPCAR version (refer to the problem described above, or to SAP Note 892842).


    Avoiding DDIC activation errors during the import

               To avoid DDIC activation errors when you import installation queues (especially long queues), you must implement the fplowing notes BEFORE you implement the corrections.

    791984  "Simultaneous activation of view append and appending view"

    1015068 "Deleting and recreating dictionary objects"


               Alternatively, check whether you have already implemented this notes as part of a Basis Support Package.


    Termination of table conversion (tp step "N") on MSSQL systems

               Symptom: When you import installation queues on MSSQL Server systems, the import step for the table conversion (tp step "N") terminates. The job log of the associated background job RDDGEN0L contains the runtime error SAPSQL_SUBQUERY_ILL_TABLE_TYPE.


               Solution: To avoid the error, implement the corrections contained in Note 1042435 before you import the Support Package.

    If you have already encountered the error, proceed as described in Note 1042435.


    I hope this is sufficient




  • Re: Apply ST-PI and ST-A/PI
    Currently Being Moderated

    Hi Jason


    I will recommend you the following things:


    1. Update the latest SPAM and SAINT version


    2. Take a full backup of system so suppose the patches give you errors and you are not able to resolve,you can always restore the system


    3. Also Check SAP Note 822379,this will help you if you face any errors