Broken Dc's in CBS

Hi All,
I am using CE7.1. I faced a problem while creating projects locally. When i checked in CBS, in my track , all the DC's are shown
as broken DC's. How to fix this.
Could anyone help me in resolving this?
Thanks!
Swarnaprakash

Dear Swarnaprakash,
Your SC is missing the build time dependencies.
Kindly follow the below mentioned steps to resolve the issue...
1) Open the following URL to access NWDI web interface
www.http://<hostname>:<port number>/devinf
2) goto Change Management Services
3) Open System Landscape Directory
4) Click on Software Components
5) Here in the Filter give your Software Component name (WebDynpro)
6) after the serach is over select your SC in the table and the below displayed tabs goto Dependencies.
7) in the Context dropdown chose "BuildTime"
8) click on "Define Prerequisite Software Component Versions"
7) In the Name column of the table search for the standard SC dependencies that you have mentioned in your previous reply (for e.g. SAP-JEE, SAP_BUILDT, SAP_JTECHS) and add then one by one as a dependencies.
8) once you are done with this, go back to the 2nd step mentioned above.
9) Goto the Landscape Configurator link.
10) Chose your track inside the table on the left side.
11) goto the Domain Data option, Click on the "Change" button, and then click on "Update CMS" button (This may take some time)
12) once the CMS Update is finished, open the "Track Data" link that is beside "Domain Data"
13) Now click on the "Change" button, from the software component (SCs) table remove the WebDynpro SC, and add it back once again.
14) Save the Track Data.
15) Now goto Transport Studio, make sure your track is selected in the table
16) In the Check-In Tab select all the components displayed in the "Check-In" button.
17) Once the Check-In operation is completed all those component will now be queued up in the Development Tab,
18) In the Development Tab select all the components & click on "Import"
19) Once the Import operation is completed all those component will now be queued up in the Consolidation Tab,
20) In the Consolidation Tab select all the components & click on "Import"
21) Now come back to your NWDS and remove the configuration that you have imported previously and then again load the same configuration once again from the SLD.
This should resolve your problem...
Please revert in case the issue still persists.
Regards,
Shreyas Pandya

Similar Messages

  • How to Resolve the Broken Dc's on CBS.

    Hello all,
    I am facing few broken Dc's in CBS. I tried to resolve the broken DC's by the following procedures, but was not able to completely resolve the broken DC's on CBS. few procedures are
    1. No built and Deploy errors in NWDI
    2.Had released all the activities from transport, no more activity's are in pending state in TSK.
    But I am facing broken DC's in compile state, Metadata and Used Dc's. Can any of you suggest me how to resolve the broken DC's on CBS.
    Thanks you all,
    Anil

    Hi Anil,
    first of all please notice that I've moved this thread to the NWDI forum.
    See the guide:
    Understanding Broken DCs and Dirty DCs
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    You find some other useful documents in the top-most thread of this page in NWDI forum (SAP NetWeaver Development Infrastructure (NWDI))
    Direct link to the thread:
    Most important NWDI related guides and documents
    The specified item was not found.
    Best Regards,
    Ervin

  • Broken DC in CBS Consollidation Build space

    Hi All
    When i assembled the activity in CMS server assembling of components got failed.Reason was Broken DC exist in CBS Consollidation build space.
    I have compared the CBS Development build space and CBS consollidation build space one difference i found that in CBS Consollidation build space under the column Total DC is that number of DC is Zero for the SC Name BI_UDI,SAP-JEE,SAP_BUILDT,SAP_JTECHS.
    Can any body help me how to solve Broken DC problem in the CBS Consollidation Build space?
    CBS Log is as follows:
    Build number assigned: 1925
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "XWD_ETOOLS_C" at Node ID: 289,619,750
         [id: 1,873; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2008-07-08 09:51:16.474 GMT
    ===== Pre-Processing =====
    Waiting 6 ms
    List of activities to be activated:
         1 activity in compartment "wartsila.com_ETOOLS_1"
              SPAX08_08072008_AdvanceSearchModule_ACN44341
                   [seq. no 129][created by SPAX08 at 2008-07-08 09:50:57.0][ID bfe2a18f4cc211dd9a0e000f203c93e0]
    Analyse dependencies to predecessor activities... started at 2008-07-08 09:51:16.486 GMT
    Analysing predecessors in compartment "wartsila.com_ETOOLS_1"
         No dependencies to predecessor activities found.
    Analyse dependencies to predecessor activities... finished at 2008-07-08 09:51:16.558 GMT and took 72 ms
    Analyse activities... started at 2008-07-08 09:51:16.559 GMT
    Analyse dependencies to predecessor activities... finished at 2008-07-08 09:51:16.839 GMT and took 249 ms
              SKIP  : Development Component "wartsila.com/AdvancedSearchModule"
         No components to be build in compartment "wartsila.com_ETOOLS_1"
    Analyse activities... finished at 2008-07-08 09:51:16.877 GMT and took 318 ms
    Change request state from PROCESSING to PROCESSING
    Calculate all combinations of components and variants to be built...
         "wartsila.com/AdvancedSearchModule" variant "default"
              "wartsila.com/AdvancedSearchModule" variant "default" IS BROKEN. The component therefore cannot be built and will be marked as BROKEN.
              [DC 201 variant "default"][SC 388 "wartsila.com_ETOOLS_1"][last successful build: 0]
    Prepare build environment in the file system... started at 2008-07-08 09:51:16.885 GMT
         Synchronize development configuration... finished at 2008-07-08 09:51:16.887 GMT and took 2 ms
         Synchronize component definitions... finished at 2008-07-08 09:51:16.887 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2008-07-08 09:51:16.888 GMT and took 1 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2008-07-08 09:51:16.888 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2008-07-08 09:51:16.888 GMT and took 3 ms
    ===== Pre-Processing =====  finished at 2008-07-08 09:51:16.890 GMT and took 410 ms
    Waiting 2 ms
    ===== Processing =====
    ===== Processing =====  finished at 2008-07-08 09:51:16.892 GMT and took 0 ms
    ===== Post-Processing =====
    Waiting 6 ms
    Change request state from PROCESSING to PROCESSING
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
         "wartsila.com/AdvancedSearchModule" in "default" variant was not built and has no build results to store.
         "wartsila.com/AdvancedSearchModule": store meta-data
         "wartsila.com/AdvancedSearchModule" in "default" variant  is PROCESSED
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2008-07-08 09:51:17.160 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.
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/com.sap.aii.proxy.framework [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/com.sap.aii.util.misc [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/cmi [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/ddic/ddicruntime [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/ddic/metamodel/content [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/wdp/metamodel/content [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/bi/bp/webDynpro [public-part: webDynpro] AS Build Plugin Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/com.sap.exception [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/com.sap.mw.jco [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/logging [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
         DC: wartsila.com/AdvancedSearchModule of compartment wartsila.com_ETOOLS_1 USES  UNKNOWN DC: sap.com/tc/wd/webdynpro [public-part: default] AS Build-Time Dependency
              [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
    Handle Cycles...
         No cycles detected.
    No Collateral Internal Build Requests found
    Determine components that have become DIRTY due to the results of this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Integration of activities in compartment "wartsila.com_ETOOLS_1" started at 2008-07-08 09:51:17.231 GMT
              "SPAX08_08072008_AdvanceSearchModule_ACN44341"   OK
         Integration of 1 activities in compartment "wartsila.com_ETOOLS_1" finished at 2008-07-08 09:51:17.714 GMT and took 483 ms
    Analyse effect of applied changes to buildspace state... finished at 2008-07-08 09:51:17.714 GMT and took 554 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2008-07-08 09:51:17.717 GMT and took 819 ms
    REQUEST PROCESSING finished at 2008-07-08 09:51:17.717 GMT and took 1 s 243 ms
    Thanks & Regards
    Susmita

    Hi Snehal,
    I have checked the Consolidation and i found that the build dependcies which is showing import finished is the old date that is jan 2007.
    Actually one month back Assemble tab was disappeared in CMS server.After that Basis team re import the SC into the track.After reimporting the SC only we are getting build dependency error in CBS Development and Consolidation build space.On 2nd july 2008 they have reimported the required dependecy till Production.after this we are not getting any broken DC in CBS development build space, however still the problem exist (Build dependency error) in consollisation build space of CBSspace.
    I have checked the history of consollidation i am not getting any dependency which was imported on 2nd july.The build dependency which is present in consollidation history page is the much oldest one (Jan 2007).I think basis team did some mistake.
    Could you please tell the procedure so that we can inform the basis team (HP 3rd party) what they need to do?
    Thanks & Regards
    Susmita

  • JDI Broken DC in CBS

    Hi,
    After changing the runtime conditions in the Landscape Configurator all my development components from my tracks are flagged as 'Broken DC' in the CBS. Why is this the case? How can i fix the broken components?
    Thanks for all your help.
    Sivajan

    Hi Kiran,
    These are standard SAP Components. I have imported the ESS and MSS Packages. I have not made any changes to these objects. After modifying the runtime system in the landscape configurator from the CMS, all my development components are marked as broken in my track (within the CBS). How can I fix these. Do i need to check in all the software components(listed below again) and reimport them back into the track (both dev and cons tab)?
    SAP_ESS
    SAP_MSS
    SAP-JEE
    SAPPCUI_GP
    SAP_BUILDT
    SAP_JTECHS
    Please note, i have not yet set up the NWDS, i am still setting up the standard SAP components in the JDI Environment.
    Many thanks for your help
    Sivajan

  • Buildspaces PDE_TRCKXSS_C with all the DCs Broken

    Hi my friends
    In the CBS I have the Buildspaces: PDE_TRCKXSS_D and PDE_TRCKXSS_C.
    In the PDE_TRCKXSS_D  not present any error, while the PDE_TRCKXSS_C appear all the DCs as Broken .
    In the CBS Buildspace Details PDE_TRCKXSS_C appears several SC without DCs: This SC are: SAP-JEE, SAPPCUI_GP, SAPPCUI_GP, SAP_JTECHS.
    In the column total DCS displays 0
    This does not permit me to make transport in the CMS.
    Thank you very much for the help they can provide me

    HI,
    As you see this the problem occur due to the missing dependecies.
    so you have a option to import those dependecies(SAP-JEE, SAPPCUI_GP, SAPPCUI_GP, SAP_JTECHS.) again in you track.
    Go to CMS-> consolidation tab -> Go to history button -> choose proper history date which will show your dependecie-> select those depenecies and say -> add to queue -> back to import queue
    from here you can import them again in youe cosolidation compartment.
    If your cms is not showing the dependecies in history of consolidation, then you need to perform import throught from check-in to assembly.

  • Cannot build because used component is broken

    Hi,
    i'm trying to add external library (com.sap.security.api.jar) into my DC using the blogs
    /people/bala.krishnan2/blog/2006/09/25/bid-adieu-to-bots--using-captchas
    I want to use com.sap.security.api.IUser in my porgram to get the current login id.
    but i'm getting following errors whern i'm trying to build the my WD DC project after adding two public parts 'Compilation' and the other of type 'Assembly' .
    Jul 5, 2009 2:24:35 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: incrprf: Build failed for sap.com/incrprf(sap.com_SAP_ESS_1) in variant "default": Check for used DCs failed: Cannot build because used component is broken: sap.com/extlib( sap.com_SAP_ESS_1)
    Build log -
    Development Component Build (2009-07-05 14:24:35)
      Component name: incrprf
      Component vendor: sap.com
      SC compartment: sap.com_SAP_ESS_1
      Configuration: DEV_XSSTRACK_D
      Location: DEV_XSSTRACK_D
      Source code location: http----
    /sap.com_SAP_ESS/dev/inactive/DCs/sap.com/incrprf/_comp/
      DC root folder: C:\Documents and Settings\----\.dtc\0\DCs\sap.com\incrprf\_comp\
      DC type: Web Dynpro
      Host: -
    DC Model check:
              [dcmake] All used DCs are available locally
              [dcmake] ERROR: Check for used DCs failed: Cannot build because used component is broken: sap.com/extlib( sap.com_SAP_ESS_1)
              [dcmake] Build failed with errors.
    can you please help me on this.
    Thanks
    Ali

    Look at the build log of the broken DC using the CBS WebUI for more information.

  • Error in Creating Project in ESS.

    Hi All,
    I have a requirement where in , there is change in the personal data screen of ESS package. We configured the NWDI server. But when i am trying to extract the ess/in/pdata dc from the ESS SC. It is failing during the project Build and throwing the below error.
    Mar 8, 2009 12:12:17 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: ess/in/pdata: Build failed for sap.com/ess/in/pdata(sap.com_SAP_ESS_1) in variant "default": [Error]   Generation failed!
    Build log -
    Development Component Build (2009-03-08 12:11:23)
      Component name: ess/in/pdata
      Component vendor: sap.com
      SC compartment: sap.com_SAP_ESS_1
      Configuration: NDI_ESS2_D
      Location: NDI_ESS2_D
      Source code location: http://sapdev:50200/dtr/ws/ESS2/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/in/pdata/_comp/
      DC root folder: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\
      DC type: Web Dynpro
      Host: HIC-PCS31092
    DC Model check:
       All used DCs are available locally
       validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
       validating dependency to  public part "default" of DC "sap.com/tc/cmi"
       validating dependency to  public part "default" of DC "sap.com/tc/ddic/ddicruntime"
       validating dependency to  public part "default" of DC "sap.com/tc/ddic/metamodel/content"
       validating dependency to  public part "default" of DC "sap.com/tc/wd/webdynpro"
       validating dependency to  public part "default" of DC "sap.com/tc/logging"
       validating dependency to  public part "default" of DC "sap.com/tc/wdp/metamodel/content"
       validating dependency to  public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
       validating dependency to  public part "default" of DC "sap.com/com.sap.aii.util.misc"
       validating dependency to  public part "default" of DC "sap.com/com.sap.exception"
       validating dependency to  public part "default" of DC "sap.com/com.sap.mw.jco"
       validating dependency to used DC "sap.com/pcui_gp/xssfpm"
       validating dependency to used DC "sap.com/pcui_gp/xssutils"
       validating dependency to used DC "sap.com/ess/per"
       DC model check OK
    Start build plugin:
       using build plugin: sap.com/tc/bi/bp/webDynpro
       starting build plugin from : C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
    Build Plugin 'WebdynproPlugin', Version 7.00 SP 9 (645_VAL_REL, built on 2006-08-23 19:48:09 CEST)
       development component:  ess/in/pdata (sap.com)
          software component:  SAP_ESS (sap.com)
                    location:  NDI_ESS2_D
                        type:  Web Dynpro
               build variant:  default
             source location:  http://sapdev:50200/dtr/ws/ESS2/sap.com_SAP_ESS/dev/inactive/
           plugin start time:  2009-03-08 12:11:39 GMT+05:30 (IST)
                     Java VM:  Java HotSpot(TM) Client VM, 1.5.0-b64 (Sun Microsystems Inc.)
    General options:
      convert *.xlf to *.properties: yes
      include sources for debugging: yes
    Used compilation public part does not exist: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\pcui_gp\xssutils\_comp\gen\default\public\FPMUtils\
    Used compilation public part does not exist: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo\
    Warning: Source folder does not exist, will be ignored: META-INF
    Warning: Source folder does not exist, will be ignored: src/mimes
    Warning: Source folder does not exist, will be ignored: src/configuration
    Plugin initialized in 1.625 seconds
    Preparing data context..
    No 'default' JDK defined, will use running VM.
    Data context prepared in 8.89 seconds
    Executing macro file..
      Using macro file:     C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\macros\build.vm
      Creating output file: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\gen\default\logs\build.xml
    Macro file executed in 1 second
    Starting Ant..
      Using build file:     C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\gen\default\logs\build.xml
      Using build target:   build
      Generation folder:    C:\Documents and Settings\sk46196\.dtc\0\t\7F9C993F9CD60BA2D12EBC39ED1E9345
      Using Ant version:    1.6.2
    compile:
          [echo] Starting dictionary generator
         [ddgen]
         [ddgen] [Info]    Property deployment is true: Deployment information is provided!
         [ddgen] [Info]    Property sourcepath: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\src\packages
         [ddgen] [Info]    Property targetpath: C:\Documents and Settings\sk46196\.dtc\0\t\7F9C993F9CD60BA2D12EBC39ED1E9345\gen_ddic
         [ddgen] [Info]    Property archivename: sap.comessin~pdata
         [ddgen] [Info]    Property vendor: sap.com
         [ddgen] [Info]    Property dcname: ess/in/pdata
         [ddgen] [Info]    Property projectlanguage: en
         [ddgen] [Info]    Property language: Available languages are automatically determined!
         [ddgen] [Info]    Property addpaths ...
         [ddgen] [Info]       SapMetamodelWebdynproContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
         [ddgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
         [ddgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
         [ddgen] [Info]       sap.compcui_gpxssfpm~FloorplanManager.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/pcui_gp/xssfpm/_comp/gen/default/public/FloorplanManager/lib/java
          [ddgen] [Info]    Initialize generation templates from configuration jar:file:/C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
          [ddgen]
         [timer] Dictionary generator finished in 14.733 seconds
          [echo] Starting WebDynpro generator
         [wdgen]
         [wdgen] [Info]    Property deployment is true: Deployment information is provided!
         [wdgen] [Info]    Property sourcepath: C:\Documents and Settings\sk46196\.dtc\0\DCs\sap.com\ess\in\pdata\_comp\src\packages
         [wdgen] [Info]    Property targetpath: C:\Documents and Settings\sk46196\.dtc\0\t\7F9C993F9CD60BA2D12EBC39ED1E9345\gen_wdp
         [wdgen] [Info]    Property archivename: sap.comessin~pdata
         [wdgen] [Info]    Property vendor: sap.com
         [wdgen] [Info]    Property dcname: ess/in/pdata
         [wdgen] [Info]    Property projectlanguage: en
         [wdgen] [Info]    Property language: Available languages are automatically determined!
         [wdgen] [Info]    Property addpaths ...
         [wdgen] [Info]       SapMetamodelWebdynproContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
         [wdgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
         [wdgen] [Info]       SapMetamodelDictionaryContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       sap.compcui_gpxssfpm~FloorplanManager.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/pcui_gp/xssfpm/_comp/gen/default/public/FloorplanManager/lib/java
         [wdgen] [Info]       webdynproruntime_repository_pmr.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       webdynproservices.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       jrfc.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       cmiapi.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       logging.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       logging.perf.jar - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]       SapMetamodelWebdynproContent.zip - C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
         [wdgen] [Info]    Initialize generation templates from configuration jar:file:/C:/Documents and Settings/sk46196/.dtc/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
         [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/HRXSS_PER_P0002_IN.java
         [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_Edit_P0002_In_Output.java
         [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Bapiret2.java
        [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_F4_Value.java
         [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_Modify_P0002_In_Output.java
         [wdgen] [Info]    Generating packages/com/sap/xss/hr/per/in/pdata/model/Hrxss_Per_Delete_P0002_In_Output.java
         [wdgen] WARNING: Metadata of component VcPerPersonalINOverview is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
         [wdgen] WARNING: Metadata of component VcPerPersonalINReview is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.review.VcPerPersonalINReview/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
         [wdgen] WARNING: Metadata of component FcPerPersonalIN is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.fc.FcPerPersonalIN/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
         [wdgen] WARNING: Metadata of component VcPerPersonalINDetail is not valid! ComponentUsage "//WebDynpro/Component:com.sap.xss.hr.per.in.personal.detail.VcPerPersonalINDetail/ComponentUsage:FcPersInfo", Role "UsedComponent": A minimum of 1 object(s) is required
         [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> Component VcPerPersonalINOverview: Has invalid component usage 'FcPersInfo'
         [wdgen] [Error]   .Subtypes: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> ContextModelNode Subtypes [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
         [wdgen] [Error]   .Subtypes.Subtype: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   .Subtypes.Case: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   .Subtypes.Stext: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   .Subtypes.Del_Button: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   .Subtypes.Disp_Only: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   .Subtypes.Cre_Button: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   .Default_Begda: The mapping definition is inconsistent, the mapped context element does not exist.
         [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> ContextModelAttribute Default_Begda [referencedProperty]: The context model attribute has not been bound to a model property
         [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> ContextModelAttribute Default_Begda: Context model attributes which are defined as top level attributes have to be mapped to attributes of other controllers.
         [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> Component VcPerPersonalINOverview [FcPersInfo]: Component usage has no used component
         [wdgen] [Error]   com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview --> Component VcPerPersonalINOverview [FcEmployeeServices]: Component usage has no used component
         [wdgen] [Info]    com.sap.xss.hr.per.in.personal.overview.BizCardsView --> TransparentContainer rootContainer [Children]: Container does not contain children
         [wdgen] [Info]    Catching throwable null
         [wdgen] [Info]    com.sap.webdynpro.generation.ant.GenerationAntTaskError
         [wdgen] ERROR: Unknown exception during generation null (com.sap.webdynpro.generation.ant.GenerationAntTaskError)
         [wdgen] ERROR: Generation failed due to errors (6 seconds)
    Ant runtime 22.31 seconds
    Ant build finished with ERRORS
    [Error]   Generation failed!
    Error: Build stopped due to an error: [Error]   Generation failed!
    Build plugin finished at 2009-03-08 12:12:17 GMT+05:30 (IST)
    Total build plugin runtime: 38.606 seconds
    Build finished with ERROR
    This is coming when i am trying to create project. Though the prooject is getting created in the local NWDS but still i is not recognizing many things internally and throwing error in the code.
    One thing is this partiuclar DC which i am tring t Create project isshown as a Broken DC in the CBS, Will this be any problem??
    Please help me andin this regards with your suggesion., this is really important and critical for us.
    Regards
    Sai Sharan Kalla

    Hi ,
    You need to check the activity in DTR, it seems that its not active.
    Also make sure that all the URL DTR and CBS have FQDN.
    Regards,

  • Configuring Runtime systems for a  Track

    Hello Experts,
            I am new to the NWDI administration,here am having some quries for configuring Track related data.
    We are using NWDI 7.0 SP18 having local SLD with both roles as landscape and Name server.
    We have a requirement to build a new .SCA for MDM-EP perspective.So,we have created a new SC in SLD and created the domain and track for the newly created SC in CMS.
    When we are initially creating a track for newly created SC,we selected runtime systems as DEV,Test and production.
    Here we have one consolidated tab,where it will integrate all the changes in WS-CONS when we imported the requests.But here what kind of system details we need to provide for consolidation,Because we have already identified 3 sepate systems for DEV,QAS(TEST) and PROD.is it necessary to identify a separate system for consolidation?or is it a simply root path for DEV-to-QAS.
    2.For developing with Track,we need to provide the Component Build Service (CBS) with the environment for building the components by importing required .SCA's(SAP-JEE,SAP_BUILDT,SAP_JTECHS).We have imported these SCA's in to DEV before using the track by DEV team.After that these components are added to consolidate tab as well.So,do we need to import all the standard .SCA's in to all the runtime systems for this track?(Pls.Note that all Runtime systems are at same NW 7.0 SP18 level).
    Please provide your valuable suggestions to make myself understand this Java transport concepts clearly.
    Thanks in Advance..
    Regards,
    Sanam.

    Hi,
          Thanks for your clarification.Now we are facing an issue related to broken DC's once we imported the relased requests in to Consolidation phase.
    Our developer activated and released 2 change requests.Once it got released it will automatically comes to the consolidation after successful build and autoimport in DEV system.we have tried to import the change requests in to the consolidation(No physical run time system is assigned to the consolidation)---In this phase if you import the chage requests in to consolidation phase:
    Repisitory-Import is finished successfully
    CBS-Make:identified the broken DC's after CBS Build process
    SDM-Deployment Notication:No deployment,because no runtime system is defined.got finished successfully.
    So,the DC's got broken during CBS Build phase.After some analysis,we identified the dependency SCA's got missed out in Consolidation.So,we imported the required SCA Components again in to the consolidation for build purpose.Here we again tried by adding those relased change requests to the consolidation queue and imported again.But still,the CBS Build identifying the Broken DC's.Our development SCA has the dependency software components as (SAP_EU,SAP_BUILDT,SAP_JEE,SAP_JTECHS).Thse components are successfully imported in to DEV and can able to see it from NWDS.The same components are imported successfully in to the consolidation as well,but from out 4 components we can able to see only 3 components except SAP_EU in NWDS.
    1.So,is that causing any Build problem for my relased change requestes?If yes,why it was missing in consolidation(re-imported twice for SAP_EU).
    2.we tried importing the released CR's  without checking dependecies are available for consolidation.Is that causing my DC's broken for build phase?
    Please suggest your ideas,how can i make my CBS-Build process OK for relased requests.

  • Error in JDI Configuration

    Hi All,
    i am getting an error in JDI configuration in the step importing MSS.sca file in CMS transport studio/development.
    error description as follows
    Fatal:the compartment sap.com_SAP_MSS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment sap.com_SAP_MSS_1 (dcname=mss/ecm dcvendor=sap.com)
    Info:dirty DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec dcvendor=sap.com)
    Info:the compartment sap.com_SAP_MSS_1 contains broken DCs after the CBS build process:
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/budget dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/equ dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/ewa dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/finutils dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/lpa dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mas dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mol dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mov dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/pcr dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/per dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/pla dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/qtp dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/qtt dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec/cand dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec/req dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rpt dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/tmv dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=temp/testforisrlpd dcvendor=sap.com)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2007-02-26 04:52:23.0586 +1:00
    please help me.
    thanks in advance.
    Srinivas.

    Hi ...
    Maintain one more characterictic like Zprice and in Addl data give table as SDCOM and field as VKOND and no values, this is characteristics for variant price and include it in the class which u have created earlier.
    goto CT04 and goto values .... there select one value eg RED and then goto object dependency and give code as
    $self.Zprice = 'A1'
    and for all values give it like that..
    Now goto VK11 and give VA00 .....
    then enter varaitn as A1 and give price
    give A2 and give price
    like all variants 'A1' etc etc etc which u maintained in object dependency ....
    now u can create profile in Cu41 and then run sales order
    so what ever u select ...red, blue green etc in order for eg color characterictics .. u have maintained for each value in characteristics .. object dependency .... as $self.Zprice = 'A1', so A1 price maintained in VK11 so if u select Red ... then price from A1 comes ..
    same procedure u follow for all values in other characterictics .. with only one characteristics Zprice ... i.e $self.Zprice = 'B1' etc .. and maintain values for B1 etc in Vk11 in Va00.
    Reward if useful
    Krishna

  • BPM - "Copy local DC into Track"

    Query has moved to NWDI.

    Hi Dev,
    Understood your problem. Please follow the below mentioned procedure to resolve the issue.
    Assuming that you have a Same Process Composer DC in your Local Environment which is able to build and deploy successfully.
    1) Open your NWDS-Development Infrastructure Perspective, and expand the  Local Development--> My Components
    2) Here right-click Copy your BPM Process Composer DC that you desire to migrate into a track.
    3) Now, Load your development Configurations in your NWDS.
    4) Expand Track --> and just Left click on the Track SC. (Sometimes when you right click the Paste option is disabled)
    5) Now, Right-Click the Track SC and Paste the BPM-DC here.
    6) Once the DC is copied inside the Track SC, then select the same BPM DC inside the Track.
    7) Open the "Permissions" tab and remove the "MyComponent" SC persmission and instead add the Track SC to the permission list.
    8) Now, open the Dependencies tab and click on "Resolve All" button.
    (Here, If you get an Error like "not all the dependencies could be resolved" then your your SC is missing the build-time dependencies.
    Please refer to the 3rd reply from me in thread Re: Broken Dc's in CBS for resolving the issue.
    9) Once all the dependencies are resolved, you have to right the BPM DC and select "Create Project Structure" option.
    10) After Creating the project structure Right click the BPM DC in track and from the Context menu click on "Add to Source Control" option.
    11) As a result of this action you'll be ask to create an Activity. Create it and Check-In the activity from Open Activities view.
    12) After successful Check-In operation, Activate the Activity from Activation view.
    13) After successful Activation operation, Release the Activity from Transport view.
    14) from CMS Web UI, inside Transport Studio import the activity into Consolidation.
    15) Ans finally Assemble the SCA inside Assembly tab.
    I Hope this will resolve your issue.
    Regards,
    Shreyas Pandya

  • Minimum NWDI SP Level for MSS

    Hi All,
    I am currently getting 2 broken DCs in the CBS when creating a track for MSS. However, in my previous experiences everything worked fine. I do notice that the NWDI system is a few SP levels below the Portal J2EE SP Level. Thus, after failing to search up concrete causes of error, I am starting to wonder if the low NWDI SP level is the cause of my headaches. I remember that there is a minimum SP level for the portal J2EE, not sure if that applies to the NWDI system.
    Is there a minimum NWDI SP Level requirement for MSS SCs? Perhaps there is a note that slipped through my research?
    FYI, I am importing MSS 600 SP 12 into NWDI which is SP 12. CIM has been updated and SC Dependencies are synchronized with the SLD. All the required SCs are SP 16 because the portal is at SP16. PCUIGP is SP12 matching MSS.
    Thanks very much for your time!
    Robert
    Edited by: Robert Liu on Dec 2, 2008 4:47 PM

    Robert,
    This are my thoughts:
    NWDI SP should not interfere with the CBS build.
    New NWDI SP may be more stable or have a new feature, but it does not influence the result of the build.
    Only versions of the SCs being built are involved.
    Check the logs of the build.
    You should be able to see exactly why component is marked as broken.
    Regards,
    Slava

  • 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.

  • 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

  • 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

  • Broken DC in CBS for ESS

    Hello All,
    I have imported ESS sc and its depencies to the track. The import finished. But, looks like in CBS there are 236 broken Dc's is it normal to have broken DC or do I have reimport the components?
    your help is appreciated.
    I imported them on to 2 tracks and both of these tracks have same numbe rof broken Dc's.
    your suggestions are appreciated.
    Thanks,
    James

    James,
    The cfg is some thing a custom DC or is it a SCA in ESS?
    I think that there is no sca called cfg for ESS. When we import ESS SCA normally we should add sca's like: ESS, SAPPCUI_GP, JEE,JBUILD,JTECHS. I am not sure where cfg SCA is coming from?
    Some times these issues because of SC dependencies are not synchronised correctly , we resolve these issues while clicking on Synchronize SC Dependencies from the CMS landscape configurator but it may work or may not.
    I am not sure how far the manual build helpful but you can give a try.
    Thanks
    Krishna

Maybe you are looking for