cancel
Showing results for 
Search instead for 
Did you mean: 

SolMan 7.0 Problem with ST SAPKITL425 and ST-PI 2005_1_700 installation or upgrade of support packages

Former Member
0 Kudos

Hi experts,

I have to update our Solution Manager 7.00 installation with the latest support packages.

Currently the system level is as following:

ComponentReleaseLevel
SAP_BASIS7000013
SAP_ABA7000013
PI_BASIS2006_1_7000006
ST-PI2008_1_7000006
SAP_BW7000013
SAP_AP7000010
BBPCRM5000010
CPRXRPM4000008
ST4000014
ST-A/PI01L_CRM6700000
ST-ICO150_7000015
ST-SER700_2005_20000
SPAM7.000046

I cannot install any further support packages because the generated queues (e.g. SAP_BASIS level:0014) contain always the next ST package (SAPKITL425), which leads me to an error message when I import the queue in "test" mode.

"Konflikte mit installierten Add-Ons"

Phase ADDON_CONFLICTS_?

Konflikte zwischen Add-On ST-SER 700_2005_2 und Support Packages

Komponente: ST

Release: 400

Support Package: SAPKITL425

Information zur Konfliktlösung: CRT: DUMMY

Therefor I tried to upgrade the ST-SER component in Transaction SAINT but I am not able to install any other level or version of this component, because when selecting an import file (e.g. ST-SER_2008_1) the system tells me that there is a missing constraint to ST-SER_700_2005_1).

I already downloaded all possible ST-SER and ST-PI versions for SolMan 7.00 but they are not installable through SAINT.

ST-SER 700_2008_1

Message: "OCS-Package SAPKITLONB passt nicht zum aktuellen Softwarekomponentenvektor."

Next window displays ST-PI_2005_1_700 as a prerequisite with error message "Kein erlaubtes Release von Add-On ST-PI installiert".

I am stuck and need help! Please, any hint will be great!

Thanks and regards,

Shapoc

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

SOLVED:

OK, got it working by downloading complete Support Package Stack 17, uploaded all packages to EPS\in and tried again installing ST-SER 700_2008_1 in transaction SAINT.

Maybe there where some missing packages which were not obviously to me. But now it works and I am updating all packages to SPS 17.

Answers (0)