Error Import Broken DCs SAP_BUILDT

[carlos_madrid]

Hello

My problem occurs after import SCA: SAP_BUILDT,

SAP-JEE, SAP_JTECHS (SP21 WAS 6.40) in the CMS

and the log of CBS shows the following error:

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: sap.com/tc/bi/bp/webDynpro of compartment sap.com_SAP_BUILDT_1 USES sap.com/tc/bi/antTasks of compartment sap.com_SAP_BUILDT_1 public-part: bytecode AS Run-Time Dependency

validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED

Thank you whom I can provide information

Carlos Madrid

[carlos_madrid]

The SAP_BUILDT Software component on the service market place seems

to be incomplete. The public part bytecode has been removed and should

never be referenced.

So, obivously the buildspace is in a bad state and needs a cleanup

Delete the involved buildspaces on the buildserver and open the track in CMS Landscape configurator save the track again (which

will recreate the buildspaces) restore system state, and import again.

About to deleting the buildspace: the sources won't disappear since

they are stored in the CBS. All you won't be able to do when you delete

it is, that you cannot activate and sync, until you resave the track

(to recreate the BS) and reimport all the components, since saving the

track initiates also a restore system state and import. With other wordsdeleting a BuildSpace can block your activations/syncs for certain hours(in case of ESS import the import itself can take an hour) since you

have to reimport the Software components of the given track you have

defined on the track configuration for that track. Where you have only

the basic build plugins (like SAPBUILDT, JEE and JTECHS) there you will

block these actions for 15-30 minutes, since this is the required time

(after saving the track) until you import again these build plugins.

[snehal_kendre]

Hi,

did you tried with different .sca file of sap_buildt. download a new one and kept it in cms inbox, then try again