Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Broken Dependency (UMEADMIN) exists in standard UCES 6.35 Software Component

Hi Experts,

We have created a track for UCES 6.35 software component for doing the customizations.

When we add UCES 6.35 SC to the track and save the track, one of the dependency (UMEADMIN 7.00) is resulting into broken state because of

which the entire SC is sitting in broken state.

We even tried to create another track for UCES 6.35 and this time, we replaced the dependeny (UMEADMIN 7.00) release version with

(UMEADMIN 7.30) but still this dependency is resulting into broken state but the entire SC is not getting broken in this case.

Please suggest as why this dependency (UMEADMIN) is getting broken as soon as we add / attach the SC (UCES 6.35) to the track.

Landscape Details:

UCES - 6.35 deployed on Portal server 7.4 SP06

NWDI - 7.40 SP06

Any pointers will be highly appeciated.



Former Member
Former Member replied

Hi Hamendra,

Thanks for the reply!!!

The issue has been resolved now.

There were inconsistencies in the Dependency Definitions for the Software Component (SC) which were resolved after synchronizing the Software Component Dependencies.



0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question