cancel
Showing results for 
Search instead for 
Did you mean: 

NWDI 7.31 Broken DCs in CBS

Former Member
0 Kudos

Hi Expert,

We are migrating the Biller Direct source code from NWDI 7.02 to NWDI 7.31, but encounter three Broken DCs in CBS. From the CBS Request log, I can see the error as below:

Analyze effect of applied changes to buildspace state... started at 2013-12-26 03:59:13.578 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/fscm/bd/ebpp' DC of 'sap.com_FSCM_BD_1' compartment USES 'sap.com/com.sap.util.monitor.grmg' DC, does not exist [public-part: default] AS Build-Time Dependency [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated 'sap.com/fscm/bd/ebpp' DC of 'sap.com_FSCM_BD_1' compartment USES 'sap.com/tc/monitoring/api' DC, does not exist [public-part: default] AS Build-Time Dependency [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated 'sap.com/fscm/bd/ebpp' DC of 'sap.com_FSCM_BD_1' compartment USES 'sap.com/tc/sec/vsi/interface' DC, does not exist [public-part: default] AS Build-Time Dependency [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated

We already Check-In and Import the below SCA:

sap.com_ENGFACADE.SCA

sap.com_ENGINEAPI.SCA

sap.com_FRAMEWORK.SCA

sap.com-SAP_BUILDT.sca

but still facing the above issue, can anyone please tell us is there any other SCA need to be check-in and imported? Thanks.

Best Regards,

Swee-Tiong Ng

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member191643
Active Contributor
0 Kudos

Try explicitly defining the dependencies mentioned in the log in the NWDI again.

Check if the .dcdef file is correct in the development component file system as well as the server DTR. Also check if this .dcdef file is properly checked-in on the server. You can do this by loggin in to http://<hostname>:<port>/dtr

Former Member
0 Kudos

Hi Bhatankar,

We have fixed the issue after recreate the track. It could be caused by the old source code was check-in to the track whic is not supported. Anyway, thanks for your help.

Best Regards,

Swee-Tiong

ErvinSzolke
Product and Topic Expert
Product and Topic Expert