Check Component Dependency for NW JAVA
When we do SPS upgrade for SAP NW JAVA, dependency is getting calculated by the maintenance planner automatically. But many times we need to apply only Patch for specific components and not even SP updates. In such cases, it makes sense to check dependency manually for the required Component patch level. In this post, let’s check out how to Check Component Dependency for SP Updates for SAP NW JAVA.
Option 1 : SAP JAVA Support Tool
You can use the SAP JAVA Support tool to automatically check the component dependency for specific SP or patch levels. But this tool will need sidadm login.
Option 2 : Manual SCA Dependency Analysis
This is a manual option to do SCA dependency analysis. For this, you will need an S-User login for SAP Support Portal with authorizations for Software Downloads. Let’s check it out with one example.
Assume that you need to apply patch 15 for the LMNWABASICAPPS component which is on version 7.50 SP19. So how to check dependencies for this? Login to SAP Support Portal, and Go to Software Download.
Also Read
SAP System Sanity Checks Post Maintenance Activities
Go to SUPPORT PACKAGES & PATCHES section -> By Alphabetical Index (A-Z) -> N -> SAP NETWEAVER -> SAP NETWEAVER 75 ->
APPLICATION SERVER JAVA -> LM NWA BASIC APPS 7.50. Here you will get all the latest SPs and their patches for this component. Here we have our SP19 Patch 15 file as well i.e. LMNWABASICAPPS19P_15-80000675.SCA.
Under the Related Info column, you can see one Icon, once you click on that, you will get an option of SCA Dependency with an exclamation mark icon.
Once you click on that, it will open a new window with details of Component dependencies with their minimum SP and Patch levels.
So now you know How to Check Component Dependency for SP Update for SAP NW JAVA. Please note that the details shown here are for the Minimum patch and SP level requirements. Thus if you already have a higher patch in the system for the dependent component then you are good to go, else you need to update that component to the minimum required level. And again to check if any additional dependency is there for that component, you can use the same above process.
