on 11-11-2014 10:53 AM
Hi Shashank,
If you check the TargetVersionReport.html then you will come to know the exact reason.
Since you are moving from ISAGENT SP23 to SP24 thats why it is not picking up the component.
Since Solman 7.1 is based on SAP Netweaver 7.02 you can deploy the same component with the help of JSPM or SDM.
You can only deploy the patches for the corresponding SUM tool not the SP level.
Also check the sapnote 1837305 - SCA provided using Manually Prepared Directory are rejected and not detected by SUM tool during validation or while scanning
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems like I need to generate stack xml? as per the note 1641062?
Software Component Archives - rejected:
Component Name/Current Version | Target Version Archive names | Type | Status / Required Action |
ISAGENT 8.23.0 Vendor: sap.com Provider: SAP AG | ISAGENT24P_1-10007435.SCA 8.24.0Vendor: sap.com Provider: SAP AG | SC | Rejected due to following reason(s):• 002 : Component sap.com/ISAGENT cannot be updated to higher SP level • 005 : Component sap.com/ISAGENT is part of the following usage type: SM; |
LM-SERVICE 7.10.11.0 Vendor: sap.com Provider: SAP AG | LMSERVICE12P_1-20006622.SCA 7.10.12.1Vendor: sap.com Provider: SAP AG | SC | Rejected due to following reason(s):• 002 : Component sap.com/LM-SERVICE cannot be updated to higher SP level • 005 : Component sap.com/LM-SERVICE is part of the following usage type: SM; |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a feeling he is on ST SP12 but the java stack failed to be updated accordingly.
You will have to use JSPM or generate a stack file if you are going to use SUM.
Best option generate the stack file and fix your entire system with patches/SPs as you have other issues if ST and LM-Service are not on recommended releases.
Hi Shashank,
You have to check whether it is possible to upgrade only Java stack using SUM in this situation or not because I failed to do so in our scenario. I would request you to proceed with this option once you take suggestions from experts otherwise you may face issues with SUM if something goes wrong. In my situation, I regenerated mopz and upgraded both Abap and Java to SP12 using SUM tool. In my case, our Abap was on a higher stack (SP08) level and Java on SP04.
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.