Skip to Content
avatar image
Former Member

NWDI EH3 imported, broken software components

Hello,

our NWDI is on version SP18. We created a new track to analysis impact to our custom coding if we upgrade to NW04s SP18, ERP SP15, EH3 Patch4.

We have problems after importing the Support Packages in the track. From the 1300 components 350 are in the status broken.

We have added the following five SC in our track.

SAPPCUI_GP 603, SAP_ASR 600, SAP_ESS 603, SAP_MSS 600, SAP_PSS 600 and the corresponding support packages have been imported in the track.

CBS:

Development Component Build (2009-03-11 13:42:04)

Component name: pcui_gp/xsscfg

Component vendor: sap.com

SC compartment: sap.com_SAPPCUI_GP_1

DC Model check:

All used DCs are available locally

validating dependency to build

plugin "sap.com/tc/bi/bp/portalapplication"

validating dependency to public part "default" of

DC "sap.com/webservices_lib"

validating dependency to public part "default" of

DC "sap.com/sapxmltoolkit"

validating dependency to public part "default" of

DC "sap.com/com.sapportals.htmlb"

validating dependency to public part "default" of

DC "sap.com/epbc.prtpars._htmlb"

validating dependency to public part "default" of

DC "sap.com/epbc.prtpars._soap"

validating dependency to public part "default" of

DC "sap.com/epbc.prtapi._test"

validating dependency to public part "default" of

DC "sap.com/servlet"

validating dependency to public part "default" of DC "sap.com/jaxm"

validating dependency to public part "default" of

DC "sap.com/com.sap.security.api.sda"

validating dependency to used DC "sap.com/tc/epbc/basis/jndisupport"

validating dependency to used

DC "sap.com/tc/epbc/pcm/pcmadminimplsrv"

validating dependency to public part "api" of

DC "sap.com/tc/epbc/pcm/adminapi/java"

validating dependency to public part "api" of

DC "sap.com/tc/epbc/pcd/pars/srvgl"

validating dependency to public part "api" of

DC "sap.com/tc/pp/appdsgn/api/contentcatalogapi"

validating dependency to public part "default" of

DC "sap.com/epbc.prtapi._api"

ERROR: Illegal dependency: Access list does not allow use of

sap.com/tc/epbc/basis/jndisupport for sap.com/pcui_gp/xsscfg

(sap.com_SAPPCUI_GP_1).

ERROR: Illegal dependency: Access list does not allow use of

sap.com/tc/epbc/pcd/pars/srvgl for sap.com/pcui_gp/xsscfg

(sap.com_SAPPCUI_GP_1).

Build failed with errors.

Someone a idea?

Regards,

Alexander Türk

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Mar 20, 2009 at 11:06 AM

    Hello Alexander,

    We just applied SP18 and facing the same problem. We reported the error and SAP is aware of the situation. Now they are working on a solution. Til now they have no idee how long it will take.

    Regards,

    Marcel

    Edited by: M. Peters on Mar 20, 2009 12:07 PM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 05, 2009 at 05:14 AM

    Helllo,

    answer from SAP:

    "Dear Alexander,

    patch 2 for component EPBC2 (PORTAL FRAMWORK 7.0) is now available on

    the service marketplace. Please download it and import it into your

    track, it should solve your problems."

    We have postponed our patching. So I'm wont be able to test it the next month.

    Regards,

    Alexander

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      A quick update on my previous post. We applied EPBC2 SCA and most of the broken dc's got fixed except the pcui_gp/xsscfwizard, this only one dc has broken now in PCUI_gp sca.

      Please advice how toresolve this one specific broken DC. for this DC build log same like ACL list problem.

      If i have one broken DC on pcui_gp SCA, staill can I assemble with broken DC? and traonsport to QA?

      Please advice.

      Thanks