Broken Dcs in MSS

Hi all,
I see around 27 broken Dcs in MSS. The import is successful but the CNS build space shows 27 broken DCs.
Would it be an issue. Becuase one of the DC cats approval is a DC that I intend to modify.
Appreciate any inputs.
regards
Sam

Hi,
I assume you did perform a "restore system state"?
Otherwise, the "insonsistent" should indicate that SC dependencies were changed somehow after your SLD update. If everything is broken now I'd suspect that something went wrong there and CBS now fails to build anything because of missing dependencies and would check some of the XML fragments in the CMS Landscape configurator.
For MSS this should define these five dependencies:
<dependencies>
<used-compartment>sap.com_SAP_JTECHS_1</used-compartment>
<used-compartment>sap.com_SAP-JEE_1</used-compartment>
<used-compartment>sap.com_SAP_BUILDT_1</used-compartment>
<used-compartment>sap.com_SAPPCUI_GP_1</used-compartment>
<used-compartment>sap.com_EP_BUILDT_1</used-compartment>
</dependencies>
If that's not there then there was something wrong with the SLD import or the imported data, but I'm not an expert for that.
Regards,
Marc

Similar Messages

  • Multiple Broken DCs - ESS MSS

    Hello All,
    We are working on Netweaver Portal 2004s SP15.
    We have deployed ess, mss and pcui_gp patches of SP12.
    We have also installed the NWDI.
    We have created new track, and added ess,mss and pcui_gp software
    components to it. We have checked in and imported following components:
    sap.com_EP_BUILDT 7.00 15
    sap.com_SAP-JEE 7.00 15
    sap.com_SAP_BUILDT 7.00 15
    sap.com_SAP_ESS 600 12
    sap.com_SAP_JTECHS 7.00 15
    sap.com_SAP_MSS 600 12
    sap.com_SAPPCUI_GP 600 12
    But when we observed in CBS, there are many Broken DCs like
    pcui_gp/xssutils, pcui_gp/xsscfg, ess/no/pdata, ess/no/bank, etc.
    Because of this we are unable to build the projects in NWDS
    successfully. NWDS log says:
    General options:
    convert *.xlf to *.properties: yes
    include sources for debugging: yes
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils
    Warning: Source folder "META-INF" does not exist and will be ignored.
    Checking path lengths for sources
    Path length checks finished in 0.09 seconds
    Ant runtime 7.2 seconds
    Ant build finished with ERRORS
    Error Generation failed!
    Error: Build stopped due to an error: Error Generation failed!
    Build plugin finished at 2008-06-26 14:29:36 GMT05:30 (IST)+
    Total build plugin runtime: 10.265 seconds
    Build finished with ERROR
    Please help us solve this problem as soon as possible.
    Regards,
    Vinod

    Hello Daniel,
    Thanks for the reply.
    Till now, I am not able to build the project succssfully. So still, I have not modified anything.
    Regarding, And as a little hint if you're on SP15 (NW), corresponding XSS package is 13!
    Is it necessary to have SP13 ?
    Regards,
    Vinod

  • ESS 177 broken DCs, MSS 20 broken DCs

    Hi,
    We have done many times of activation, build, released and transportation for ESS customozation.
    After Activation failed: CBS Server Error is solved, we encountered the broken DCs problem in the CBS.
    ESS  :                              Total DCs=177 ,                          Broken DCs=177
    MSS   :                             Total DCs=20  ,                           Broken DCs=20
    SAP-JEE :                         Total DCs=0   ,                           Broken DCs=0
    SAPPCUI_GP :                  Total DCs=0   ,                           Broken DCs=0
    SAP_BUILDT   :                  Total DCs=0   ,                           Broken DCs=0
    SAP_JTECHS  :                   Total DCs=0  ,                           Broken DCs=0
    When i viewed the Build Log of each DC, the error is as below:
    USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED / USED BUILD PLUGIN IS UNKNOWN OR UNDEFINED.
    1. It seems that SAP-JEE, SAPPCUI_GP, SAP_BUILDT and SAP_JTECHS has 0 Total DCs. Is it normal or something wrong?
    2. How do i solve this problem?
    Any help would be much appreciated. Thanks.
    - julius

    1. This is wrong.
    2. Re-import them into your track, starting from the Development stage.

  • ESS MSS - Multiple Broken DCs in CBS

    Hello All,
    We are working on Netweaver Portal 2004s SP15.
    We have deployed ess, mss and pcui_gp patches of SP12.
    We have also installed the NWDI.
    We have created new track, and added ess,mss and pcui_gp software
    components to it. We have checked in and imported following components:
    sap.com_EP_BUILDT 7.00 15
    sap.com_SAP-JEE 7.00 15
    sap.com_SAP_BUILDT 7.00 15
    sap.com_SAP_ESS 600 12
    sap.com_SAP_JTECHS 7.00 15
    sap.com_SAP_MSS 600 12
    sap.com_SAPPCUI_GP 600 12
    But when we observed in CBS, there are many Broken DCs like
    pcui_gp/xssutils, pcui_gp/xsscfg, ess/no/pdata, ess/no/bank, etc.
    Because of this we are unable to build the projects in NWDS
    successfully. NWDS log says:
    General options:
      convert *.xlf to *.properties: yes
      include sources for debugging: yes
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo
    Used compilation public part does not exist: C:\Documents and Settings\190812\.dtc\1\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils
    Warning: Source folder "META-INF" does not exist and will be ignored.
    Checking path lengths for sources
    Path length checks finished in 0.09 seconds
    Ant runtime 7.2 seconds
    Ant build finished with ERRORS
    [Error]   Generation failed!
    Error: Build stopped due to an error: [Error]   Generation failed!
    Build plugin finished at 2008-06-26 14:29:36 GMT05:30 (IST)+
    Total build plugin runtime: 10.265 seconds
    Build finished with ERROR
    Please help us solve this problem as soon as possible.
    Regards,
    Vinod

    Hi Alexander
    Thanks for the reply.
    We have imported the required SCAs into new track. That workd fine and these are visible in NWDS.
    The problem is with our custom made SC which contains some DCs built on java1.4. When we import this SCA, it is shown as broken in CBS. that is also fine because the CE7.1 runs on java1.5. (There may be some build errors)
    The problem is we are not able to see these broken DCs in to NWDS.
    Regards
    Arvind

  • ESS enhancement build caused broken DCs

    Hi,
    I'm doing ESSxx_D on <b>leave</b> enhancement and encountered the broken DCs after consolidation process.
    Actually, i had tried the consolidation for 2 times, but none was successful.
    In the first time, there were all 177 broken DCs for ESS_C and 1 broken DC for ESS_D after consolidation.
    The broken DC happened to other DC (ess/tra/tri in ESS_D) which i didnt touch at all (only enhanced on ess/lea in ESS_D).
    1. How could the broken DCs happened to ESS_C (which is supposed to be constant version) and ESS_D (which is not the one that i did enhancement at)?
    Then, i created a new track and redo everything again. I just copied and pasted the source codes.
    After checked-in, activated and released, the enhanced ESSxx_D deployed successfully to the development server. Everything is fine till this point.
    Next, ESSxx_D was imported in the consolidation. After imported, there is ONE broken DC in the <b>ESSxx_C's ess/lea DC</b>. Error message is as below.
    2. Isnt the <b>ESSxx_C</b> the constant version of the ESS and the enhancement will not affecting it? The ESSxx_D has no broken DC.
    3. The source codes were same for the first time and second time consolidation. What could be gone wrong?
    Any help would be much appreciated. Thanks.
    [ddgen] [Info]    Generating datatypes/com/sap/xss/hr/lea/form/adaptivemodel/types/Infty.gsimpletype
    [System.err] [Invoked from  com.sap.ide.metamodel.general.exception.LoadException.printStackTrace(LoadException.java(Compiled Code))]
    [System.err] LoadException: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 32, 30, 30(file:/usr/sap/EPD/JC00/j2ee/cluster/server0/temp/CBS/25/.B/191246/DCs/sap.com/ess/lea/_comp/src/packages/com/sap/xss/hr/lea/reqlist/adaptivemodel/types/P22J_Nabik.dtsimpletype.xlf, row:3, col:3)
    [System.err]      at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java(Compiled Code))
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java(Compiled Code))
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java(Compiled Code))
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:222)
    - julius
    null

    Hi Marc/anyone,
    a) Below are my SPs, are these in the compatible version?
    1. NWDI = SP19
    2. NWDS = SP19
    <b>3. ESS track = SP14
    4. MSS track = SP14</b>
    5. WAS = SP19
    6. JEE = SP19
    7. BUILDT = SP19
    8. JTECH = SP19
    <b>9. PCUIGP = SP14</b>
    b) Below are the source codes structures for the ESS. Are all these necessary to synchronised to the DTR? Which are not?
    1. /bin
    2. /def
    3. /gen (i know this one no need to syn)
    4. /gen_dic
    5. /gen_wdp
    6. /META
    7. /Model Folder
    8. /Src
    9. ClassPath
    10. DCDEF
    11. METAMODEL
    12. PROJECT
    - julius

  • Broken DCs & activation view

    Hi,
    I have created new WDJ DC project in MSS Component e.g mss/transfer using the same track.
    My Project is working fine without any issues, no build errors or no activation errors.
    Now i'm trying to release this project but i not able to do that.
    After check-in my request is long time waiting under the Activation View, it is not moving to the Transport view at all.
    I viewed the Component Build Service(CBS), status is like below.
    Buildspaces
    TRACK_D = Total Dcs : 205, Broken Dcs : 205, Dirty Dcs : 0, Active : YES, input : Open, Request Processing: ON
    & TRACK_C is same but Broken Dcs is 179 .
    Requests
    Request ID :   2,840
    Request State: FAILED
    Request Type: ACTIVATE
    so what to do next?
    Regards
    Ali

    HI,
    1) There might be some Dependent DCs  for the DC you have created and they might  not be deployed .
    IDentify them any deploy them from NWDS. in DC perspective, you can right click on the dependent DCs and deploy.
    2) The other reason can be may be you have not checked in some of the activities in which the Dependent DCs were modified.
    so if there are any, check  in them and try to activate again .
    Regards,
    Satya.
    Edited by: Satya on Aug 20, 2009 2:59 PM

  • Help: NWDI 7.2 CBS build problem - initialize compartment-broken DCs

    Hi all.
    I am facing a problem with CBS build due to broken DCs - invalid dependencies. I have read all the articles and notse related to this issue, but cannot not solve is. Has anyone faced this issue or know a solution?
    The problem:
    In one SC I have a DC A, which used to have public part PP_A.
    In another SC I have a DC B, which used to depend on public part PP_A of DC A.
    As part of implementation, the PP_A in DC A was deleted and replaced by new public parts. The changes are checked in and activated in NWDI successfully.
    Next, the DC B was corrected, its reference to PP_A was deleted and replaced with appropriate replacements.
    I checked in the activity correcting the DC B. Activation fails, because CBS complains that DC B has invalid dependency. I assume that the CBS cache still holds the old sources.
    I took the compartment where DC B is located and triggered a CBS Reinitialize compartment (which should discard the cached sources and load a fresh copy). The CBS Reinitialize compartment request fails too! The log shows the same message as the build log: invalid dependency.
    It seems that during reinitialize, CBS checks the validity of the DCs in the compartment BEFORE it does clean its cache and refreshes from DTR.
    In DTR, I can see the sources of DC A and DC B checked in correctly in the inactive branch, the .dcdef in DC B contains correct references to new public parts of DC A.
    Does anyone know how to force CBS to refresh its sources from DTR where correct sources are checked in?
    Thanks.
    Edited by: Rastislav Cesnek on Dec 20, 2011 3:25 PM

    Right.
    Its not the CONS, it's the active from DEV which is used. I sort of don't understand the NWDI concept then, maybe SAP could learn a little from Hudson, CruiseControl you name it.
    Apparently, as I found out after some trial and error, the checks done before the build AND before the initialize compartment run on sources from ACTIVE branch. So the check-ed in fixed sources of the DC B are ignored by CBS. It then complains about the invalid dependencies all the time.
    Finally, although it looks very scary, I activated the soure code changes of the dependent components (I hade a lot of them, not just one) with the "Activate even if the build fails". Then the initialize compartment did not complain about BROKEN components because of dependencies, because the check of metadata succeeded and the components were rebuilt.
    Thanks for hints.

  • Difference between Dirty and Broken DCs

    Hi All
    Can any one explain me difference between Dirty and Broken DCs? And also please explain me what might be solution if we see any broken or dirty DC?

    hello,
    see [here|http://help.sap.com/saphelp_nw70/helpdata/en/46/14fa07c15214dce10000000a155369/frameset.htm] - the two links under "6. (Optional) Fix the broken and dirty DCs that might appear after the build".
    Regards, Jordan

  • Broken DCs in "BPEM-BUILDT" SC

    Hi,
    I am getting build error while I am creating BPM DC and found 10 broken DCs in BPEM-BUILDT SC.
    tc/bpem/bi/bp/buildtool(default)
    tc/bpem/bpmn2csv/lib(default)              
    tc/bpem/bpmn2tn/lib(default)              
    tc/bpem/exceptioncompiler/lib(default)              
    tc/bpem/generator/lib(default)              
    tc/bpem/interfacecompiler/lib(default)              
    tc/bpem/postprocessor/lib(default)              
    tc/bpem/reportingdefinitioncompiler/lib(default)             
    tc/bpem/rulescompiler/lib(default)              
    tc/bpem/typecompiler/lib(default)
    In CBS, I can see following details -
    INVALID DEPENDENCIES: The following dependencies are marked as invalid:
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bi/model/flow' DC, does not exist [public-part: ?] AS Run-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2csv/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2csv/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2csv/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2tn/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2tn/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: assemble] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2tn/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bpmn2tn/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/exceptioncompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/exceptioncompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/exceptioncompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/generator/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/generator/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/generator/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/interfacecompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/interfacecompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/interfacecompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/postprocessor/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/postprocessor/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: assemble] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/postprocessor/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/postprocessor/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/reportingdefinitioncompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/reportingdefinitioncompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/reportingdefinitioncompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/rulescompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/rulescompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/rulescompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/typecompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: ?] AS Run-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/typecompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: compile] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/typecompiler/lib' DC of 'sap.com_BPEM-BUILDT_1' compartment [public-part: libinf] AS Build-Time Dependency
              [validity: OK]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/esmp/bi/model/wsdl20' DC, does not exist [public-part: ?] AS Run-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/esmp/bi/model/xsd1' DC, does not exist [public-part: ?] AS Run-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                     'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/esmp/bi/wsdlexdexport' DC, does not exist [public-part: ?] AS Run-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                INVALID DEPENDENCIES: The following dependencies are marked as invalid:
    Handle Cycles... started at 2011-06-23 18:41:23.318 GMT
                    No new cycles detected.
                Handle Cycles... finished at 2011-06-23 22:05:17.546 GMT and took 203 m 54 s 228 ms
                "sap.com/tc/bpem/typecompiler/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/rulescompiler/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/reportingdefinitioncompiler/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/postprocessor/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/interfacecompiler/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/generator/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/exceptioncompiler/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/bpmn2tn/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/bpmn2csv/lib" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
                "sap.com/tc/bpem/bi/bp/buildtool" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED
            Analyze effect of applied changes to buildspace state... finished at 2011-06-23 22:05:28.022 GMT and took 216 m 49 s 825 ms
            Request SUCCEEDED
    Need your inputs to fix the issue.
    Appreciate your timely help.
    Thanks,
    cheers
    dev

    Hi Leon,
    I believe the problem is the following (reflecting to the error described at the very beginning of this discussion. Doublecheck your case whether it is really exactly the same error):
    INVALID DEPENDENCIES: The following dependencies are marked as invalid:
    'sap.com/tc/bpem/bi/bp/buildtool' DC of 'sap.com_BPEM-BUILDT_1' compartment USES 'sap.com/tc/bpem/bi/model/flow' DC, does not exist [public-part: ?] AS Run-Time Dependency
    i.e. the SC BPEM_BUILDT has been imported into development space and this is fine, but this SC has a DC called sap.com/tc/bpem/bi/bp/buildtool which has a reference to the DC sap.com/tc/bpem/bi/model/flow, but this DC is not yet part of the buildspace and this is why you face broken DCs. It tries to build, but without this DC the build is not possible.
    Solution
    This DC is located in the SC ESMPBUILDT so what you have to do is to make this SC part of your track configuration, Check it in on the CMS webui and import it into Development space.
    You find this SC here:
    http://service.sap.com/patches -- Browse our Download Catalog (this is at the left hand side pane) -- SAP NetWeaver and complementary products -- SAP NetWeaver -- SAP NETWEAVER 7.3 -- Entry By Component -- BPM -- ESMP BUILD TOOL 7.30
    The above link is an example for 730. obviously pay attention to the release and SP version you use when you download.
    If you have further broken DCs you can analyze and find the missing SC in a similar way, but of course let me know if you face further difficulties.
    See also
    #1457908 - Required SCs for Specific Type of Development in 7.3 Track
    It says:
    Business Process Management (BPM)
    BPEM-BUILDT
    BPEM-CONTENT
    BPEM-FACADE (for BPM public API usage)
    COMP_BUILDT
    CU-BASE-JAVA
    CU-BASE-WD
    DATA-MAPPING
    ECM-CORE
    ENGFACADE
    ESCONF_BUILDT
    ESMP_BUILDT
    ESP_FRAMEWORK
    FP-INFRA
    FRAMEWORK
    MOIN_BUILDT
    SAP_BUILDT
    SERVICE-COMP
    THL-CORE
    WD-RUNTIME
    Best Regards,
    Ervin

  • Broken DCs

    I am running WAS640 SP11.  I am using development scenario 2+.  I have two buildspaces WAS_APPL_C & WAS_APPL_D.  In WAS_APPL_C, I have 5 broken DCs for example.org.  In WAS_APPL_D I have none. The same DCs for appl/tax etc. are green in WAS_APPL_D.  Can I just delete the broken DCs attached to WAS_APPL_C and how?  I get errors when trying to assemble the application.
    How would I go about recollecting all the objects, checking them in and adding them to a new activity for later transport.
    I am stuck!

    Hi Steve,
    You can try a few things to get the build to work in the cons buildspace. The simplest is to use CBS to try and fix the problem.
    First, launch CBS for the track, select the cons buildspace, go to Compartments and then select the Build the Compartment tab. At the bottom of the screen, you should see an Initialize the Compartment button. Select that and CBS should synch up with what is in DTR and build the compartment. You can check your results in the Development Components link to see if the compile state is green.
    If everything looks OK from CBS, go back to CMS and assemble the components.
    If that doesn't work, try looking for pending activities in the cons buildspace and activating them.
    -r

  • Broken DCs in XSS Track after modification

    Hi everybody,
    I got an XSS track in my NWDI which contained the following SCs:
    - SAP_ESS
    - SAP_MSS
    with the appropriate dependencies and did not contain any broken DC.
    Now I've added another SC:
    - SAPPCUI_GP
    defining the appropriate dependecies, changed the track, saved and reimported it.
    The buildspace now contains many broken DCs. I tried to build the compartment but to no avail, still the same number of broken DCs.
    What shoud I be doing?
    Regards,
    Marco

    I did it.
    Excerpt:
    INVALID DEPENDENCIES: The following dependencies are marked as invalid:
                 'sap.com/pcui_gp/xsscfg' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/tc/epbc/basis/jndisupport' DC, does not exist [public-part: ?] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                 'sap.com/pcui_gp/xsscfg' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/tc/epbc/pcm/pcmadminimplsrv' DC, does not exist [public-part: ?] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                 'sap.com/pcui_gp/xsscfg' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/tc/epbc/pcd/pars/srvgl' DC, does not exist [public-part: api] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                 'sap.com/pcui_gp/xsscfg' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/tc/pp/appdsgn/api/contentcatalogapi' DC, does not exist [public-part: api] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
            INVALID DEPENDENCIES: The following dependencies are marked as invalid:
                 'sap.com/pcui_gp/xsscfgwizard' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/wizard_framework' DC, does not exist [public-part: ?] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
                 'sap.com/pcui_gp/xsscfgwizard' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/com.sapportals.portaladmin.wizframework' DC, does not exist [public-part: ?] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
            INVALID DEPENDENCIES: The following dependencies are marked as invalid:
                 'sap.com/pcui_gp/xsscfgedit' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/editor_framework' DC, does not exist [public-part: ?] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
            Change request state from PROCESSING to SUCCEEDED
            Analyze effect of applied changes to buildspace state... started at 2008-11-27 17:11:39.508 GMT
                INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts.
                     'sap.com/pcui_gp/xsscfg' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/tc/epbc/pcd/pars/srvgl' DC, does not exist [public-part: api] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
                     'sap.com/pcui_gp/xsscfg' DC of 'sap.com_SAPPCUI_GP_1' compartment USES 'sap.com/tc/pp/appdsgn/api/contentcatalogapi' DC, does not exist [public-part: api] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
    I defined all the appropriate dependencies:
    - EP-PSERV
    - EP-WDC
    - EPBC
    - EPBC2
    - EP_BUILDT
    - SAP-EU
    - SAP-JEE
    - SAP_BUILDT
    - SAP_JTECHS
    in accordance with the cookbook.
    I also initialized the compartments, but to no avail, still getting a huge amount of broken DCs.
    Thank you.

  • Nonempty list of broken DCs error when we assemble using CBS

    Hi
    We created DC and we are going to assemble using CBS.
    When we assemble, we got below error.
    Info:Starting Step Check-assembly at 2005-03-15T10:13:57.0250-8:00
    Fatal:Contact CBS administrator: Nonempty list of broken DCs -stopping export now
    Error:list of broken DCs:
    Error:lapha.net,nw04/tec/tax/calc_01
    Error:lapha.net,nw04/tech/tax
    Info:Step Check-assembly ended with result 'fatal error' ,stopping execution at 2005-03-15T10:13:58.0500-8:00
    Any idea ?
    Regards, Arnold.

    Hello,
    "broken DC" means that the build failed for this development component.This for example happens if a used component was changed in an incompatible way. It also happens if the DC itself contains errors and the developer used the "activate even if build fails"
    option in NWDS.
    If you view the buildspace of your system in CBS you will see which DCs are actually broken. And you can also see the build logs there.
    The CMS prevents you from assembling a  software component that contains broken DCs.
    Hope this helps
    Regards,
    Wolfram

  • NWDI Broken DCs: SAPPCUI_GP requires SAP_PRT sca file

    Hi, please assist.
    I want to modify SC SAP_ESS 600. I have followed the NWDI cookbook. When creating the track, SAP lists SAP_PRT as a requirement for SAPPCUI_GP 600. Can someone please provide me with the SCA filename for component SAP_PRT, as I now have broken DCs in CBS for SAPPCUI_GP. As I understand I need to place this file in the CMS inbox.
    Thank you for assistance
    Frans

    Hi Sandeep,
    Thanks for suggestion. I have looked at notes 761266 and 908569. We are currently running the following:
    ECC 6.0
    SAP J2EE 7.0 SP13 (minimum 11 suggested by notes)
    SAPESS SP7, SAPMSS SP7, SAPPCUI_GP SP7
    If I look at DC pcui/xsscfg in CBS for example, it is looking for used DC tc/bi/bp/portalapplication which was not imported with CMS.
    Any suggestions? Maybe update SAPPCUI_GP?
    Help will be appreciated.
    Frans

  • Broken DC ESS, MSS & PCUI

    Hello all,
    I am having some troubles with NWDI, when I import the SCA I got that many DC are broken, must of this broken DC are consecuence of prior DC. I fopund out one of the main DC an the build log shows:
    "sap.com/pcui_gp/xsscfg" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED"
    Any Idea on how can I solved this?
    Regards,
    Orlando Covault

    Hi Orlando,
    Did you get this solved?   We have what sounds like a very similar situation.
    After importing the SCAs for ESS we can see that the "D" and "C" buildspaces for our track have 202 Broken DCs.   And following the build logs, we can see that the missing DCs seem to be the same ones that you reported.
    The SCs that we imported per the NWDI XSS Cookbook were:
    EPBUILDT13_0-10003786.SCA        sap.com_EP_BUILDT          7.00 13
    SAPJEE13_0-10003469.SCA           sap.com_SAP-JEE             7.00 13
    SAPBUILDT13_0-10003479.SCA      sap.com_SAP_BUILDT       7.00 13
    SAPESS10P_10-20000512.SCA      sap.com_SAP_ESS           600   10
    SAPJTECHS13_0-10003467.SCA     sap.com_SAP_JTECHS     7.00 13
    SAPPCUIGP10P_2-20001215.SCA   sap.com_SAPPCUI_GP     600  10
    Did we miss something?
    Thanks!
    Bart

  • ESS MSS CBS Failed - Broken DCs */cfg

    Hi,
          I am at the last stage of the import process for ESS MSS and its dependent SCs into our NWDI environment. All the imports are successful however, when I check the status of all the DCs under ESS and MSS components I see that all the ones DCs that end with /cfg are BROKEN in the Compilation state.
         There seems to be some issue that is causing all the */cfg DCs to fail. My attempt to 'Build' this compartment proved unsuccessful.
         I guess, my question is..
          What are these */CFG DCs used for and what could be causing this issue?
    Thanks,
    Winston

    Hi Winston
    Please refer to below docs for more details :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0bb614d-2848-2a10-52a7-b5000043b475
    /people/martin.pospischil/blog/2009/07/08/troubleshooting-nwdi
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Regards
    Arun Jaiswal

Maybe you are looking for

  • How to place Outbound Interface file in APPS SERVER?

    Hi Guys,          Actually I'm running the below pl\sql procedure for the OutBound interface file. CREATE OR REPLACE procedure GE_INV_Out_BAL(Errbuf OUT varchar2,                                        Retcode ouT varchar2,             f_id    in num

  • Delivery Date changed to past date while ATPing 2nd Line

    Hello Gurus, I posted a question a few days ago, but now that I found a new example i have more info of my problem. So here is the scenario. (we are set up for back order) Orders is created for 5000 units on 09.23.2008. we do not have enough stock to

  • Opening file to automatica​lly open and run program with input file

    My program has the ability to save and open a text file with a custom extension.  How do I make the system in which the program is being installed to recognize this file to open the program, AND how to I gather the input file in my program and load i

  • Webcam losing connection

    Hey, I recently installed the trial version of Adobe Premiere Elements 8.0 and tried recording stuff with my webcam. Initially it recorded but the audio was way out of sync, cutting out before the vid ended etc. Now it won't even let me record. I hav

  • Mac and GPS compatibility!

    I have a macbook with an intel core processor. I recently bought a GPS unit and realized that most, if not all, are only PC compatible. What do I need to make my GPS work with my mac? Hopefully I can keep it cheap too. Help!!!!!!!!