Maintenance Planner not picking correct product instances installed

[former_member196664]

All,

I have built a new sandbox Enterprise Portal system and I am about to upgrade. Maintenance Planner is not picking up correct installed product instances. My old systems EP Dev, Qa and Prod systems have

Application Server Java

BI Java

Enterprise Portal

EP Core..

But the newly built SBX system is picking Application Server Java and BI Java automatically, and in Maintenance Plannner, under VERIFY it is giving 2 other installed instances to add Enterprise Portal and Developer Workplace. Why is this different for this system only? How do I correct? Is this correct and all other 3 systems wrong? How to add EP core? Please advise ASAP as I have to start upgrade ASAP, I had experience before if we did not choose proper installed instances in SMSY (usage type), some components will not be upgraded. I am afraid that might happen here as well. Please advise ASAP.

Below are installed components.

ADOBE DOCUMENT SERVICES	7.00	0027	SP027	ADOBE DOCUMENT SERVICES 7.00
BI BASE SERVICES	7.00	0027	SP027	BI BASE SERVICES 7.00
BI INFORM. BROADCASTING	7.00	0027	SP027	BI INFORM. BROADCASTING 7.00
BI META MODEL REPOSITORY	7.00	0027	SP027	BI META MODEL REPOSITORY
BI REPORTING AND PLANNING	7.00	0027	SP027	BI REPORTING AND PLANNING 7.00
BI UNIVERSAL DATA INTEGRATION	7.00	0027	SP027	UNIVERSAL DATA INTEGRATION 700
BI WEB APPLICATIONS	7.00	0027	SP027	BI WEB APPLICATIONS 7.00
BI WEBDYNPRO ALV	7.00	0027	SP027	BI WEBDYNPRO ALV 7.00
CAF EU	7.00	0027	SP027	SAP NetWeaver 05 End User 7.00
DI BUILD TOOL	7.00	0021	SP021	SAP BUILD TOOL 7.00
EP BUILD TOOL	7.00	0021	SP021	EP BUILD TOOL 7.00
J2EE ENGINE BASE TABLES	7.00	0027	SP027	BASETABLES
J2EE ENGINE CORE TOOLS	7.00	0027	SP027	CORE TOOLS J2EE ENGINE
JAVA LOG VIEWER	7.00	0027	SP027	SAP JAVA LOG VIEWER 7.00
JAVA SP MANAGER	7.00	0027	SP027	JAVA SP MANAGER 7.00
KMC BASE COMPONENTS	7.00	0027	SP027	KMC BASE COMPONENTS 7.00
KMC COLLABORATION	7.00	0027	SP027	KMC COLLABORATION 7.00
KMC CONTENT MANAGEMENT	7.00	0027	SP027	KMC CONTENT MANAGEMENT 7.00
LIFECYCLE MGMT PORTAL	7.00	0027	SP027	LIFECYCLE MGMT PORTAL 7.00
LIFECYCLE MGMT TOOLS	7.00	0027	SP027	LIFECYCLE MGMT TOOLS 7.00
PDK PORTAL SERVICES	7.00	0027	SP027	PDK PORTAL SERVICES 7.00
PORTAL CORE SERVICES	7.00	0027	SP027	EPBC 7.00
PORTAL FRAMEWORK	7.00	0027	SP027	EPBC2 7.00
PORTAL PLATFORM	7.00	0027	SP027	PORTAL PLATFORM 7.00
PORTAL WEB DYNPRO	7.00	0027	SP027	PORTAL WEB DYNPRO 7.00
RTC	7.00	0027	SP027	RTC 7.00
RTC-STREAM	7.00	0027	SP027	RTC-STREAM 7.00
SAP CAF	7.00	0027	SP027	SAP Composite Application Framework 7.00
SAP CAF-KM	7.00	0027	SP027	SAP CAF-KM 7.00
SAP CAF-UM	7.00	0027	SP027	SAP CAF-UM 7.00
SAP INTERNET KNOWLEDGE SERVLET	7.00	0027	SP027	SAP Internet Knowledge Servlet 7.00 (SAP J2EE IKS)
SAP J2EE ENGINE	7.00	0027	SP027	SAP J2EE ENGINE 7.00
SAP J2EE ENGINE CORE	7.00	0027	SP027	SAP J2EE ENGINE CORE 7.00
SAP JAVA TECHNOLOGY S OFFLINE	7.00	0027	SP027	SAP TECH S 7.00 OFFLINE
SAP JAVA TECHNOLOGY SERVICES	7.00	0027	SP027	SAP JAVA TECH SERVICES 7.00
UME ADMINISTRATION	7.00	0027	SP027	UME ADMINISTRATION 7.00
UWL COLL PROCESS ENGINE	7.00	0027	SP027	UWL COLL PROCESS ENGINE 7.00
VISUAL COMPOSER BASE	7.00	0027	SP027	VISUAL COMPOSER BASE 7.00
VISUAL COMPOSER BI KITS	7.00	0027	SP027	VISUAL COMPOSER BI KITS 7.00
VISUAL COMPOSER FLEX	7.00	0027	SP027	VISUAL COMPOSER FLEX 7.00
VISUAL COMPOSER FRAMEWORK	7.00	0027	SP027	VISUAL COMPOSER FRAMEWORK 7.00
VISUAL COMPOSER GP KITS	7.00	0027	SP027	VISUAL COMPOSER GP KITS 7.00
VISUAL COMPOSER XX KITS	7.00	0027	SP027	VISUAL COMPOSER XX KITS 7.00
WEB DYNPRO EXTENSIONS	7.00	0027	SP027	WEB DYNPRO EXTENSIONS 7.00

Also not sure about SAP CAF component question in below screen,

Other system have below usage types.

Thanks,

Kavitha Rajan.

[TomCenens · Accepted solution]

HI Kavitha Rajan

please ensure that the info comes into LMDB automatically, if it states manual entry, I would suggest you  to redefine the system in LMDB and push als data supplier job from the Java stack again.

if it came in automatically but maintenance planner takes wrong instance, check if the product instance assignment in LMDB is correct. If that is also the case, check for SAP notes with corrections, there are multiple recently released SAP notes for bug fixing.

kr

TOm

[former_member196664 · Accepted solution]

Tom,

Sorry for the late reply. In LMDB, I can see the data is AUTOMATIC and it has 4 product instances similar to what I have for dev, qa and prod. Only in maintenance Optimizer, the new sandbox system is giving issue with product instances. The system is in error and when I try to verify, there is no option to choose EP Core, but I have NW Developer workplace. We have components DI build tool and EP build tool which were not upgraded during the Support Stack upgrade as you see all the components above. May be this NW Developer Workplace is for those components? But then why other systems are not picking up this product instances. Thank you, I appreciate the guidance and pls help.

Thanks,

Kavitha Rajan.