on 03-23-2012 7:21 AM
Hello,
We have a DC sap.com/utilities which has dependencies with other DCs.
Among all used Dcs it is facing problem with below DCs
The status of all these used DCs is in Red under Used DC section.
Thus it is resulting in Broken DC for sap.com/utilities.
Below is error trace:
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/Utility of compartment ae.com_ZCWM_1 USES UNKNOWN DC: sap.com/tc/aii/base/offline/facade [public-part: api] AS Build-Time Dependency
[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
DC: sap.com/Utility of compartment ae.com_ZCWM_1 USES UNKNOWN DC: sap.com/tc/bl/exception/lib [public-part: api] AS Build-Time Dependency
[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
DC: sap.com/Utility of compartment ae.com_ZCWM_1 USES UNKNOWN DC: sap.com/tc/bl/logging/api [public-part: api] AS Build-Time Dependency
[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
DC: sap.com/Utility of compartment ae.com_ZCWM_1 USES UNKNOWN DC: sap.com/tc/ddic/runtime/facade [public-part: runtime] AS Build-Time Dependency
[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
DC: sap.com/Utility of compartment ae.com_ZCWM_1 USES UNKNOWN DC: sap.com/tc/wd/api [public-part: default] AS Build-Time Dependency
[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
DC: sap.com/Utility of compartment ae.com_ZCWM_1 USES UNKNOWN DC: sap.com/tc/wd/api [public-part: gci] AS Build-Time Dependency
[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]
How to resolve it.
Do I need to add some SC in my track ?
It seems these Dcs are not available on server.
Please advise
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This Track has already been created.
The person who did this...has already left organization
Now we have this broken DC issue.
Yes, I do believe that this dependent SC is missing.
We only have 3 SCs imported in our track right now...these are :
SAP_JEE
SAP_BUILDT
SAP_JTECHS
As per log trace...The DCs which are causing problem are below.
I believe none of these DCs are part of SCs which we have already imported. (SAP_JEE , SAP_BUILDT , SAP_JTECHS )
Now I need to know that these missing DCs are part of which SC in SAP.
Which SCs should I import ?
Hi Saurabh,
interestingly these DCs are not 700 DCs.
These are all DCs from SCAs higher than 710.
Now as mentioned you want to use 700 but these DCs are all in release higher than 700.
The SCs SAP_BUILDT, SAP-JEE and SAP_JTECHS are all 700.
Problem is that the architecture significantly changed as of 710 even most of the SCA names are different, e.g. there is no more SAP_JTECHS or SAP-JEE as of 710, and also the other way round, on 700 there is no WD-RUNTIME, and so on.
These notes will help you to decide which SCs to use:
#1080927 - Creating CMS Tracks for Common Application Types
#1465468 - Required SCs for Specific Type of Development in 7.1 Track
#1463541 - Required SCs for Specific Type of Development in 7.2 Track
#1457908 - Required SCs for Specific Type of Development in 7.3 Track
If you are sure you intend to develop for 700 I suggest this:
1. Ensure that on the Track configuration of this track, under your custom SC you have build time dependencies to SAP_BUILDT, SAP-JEE and SAP_JTECHS
2. Trigger Restore System State (You do this in CMS webui -- Transport Studio -- Development tab -- button "Restore..." (button "Restore System State" on lower releases).
3. reimport the software
4. If you would somehow still have broken DCs (which are all higher than 710) then please attept "Initialize Compartment..." which you can trigger in the CBS webui -- Compartment View.
I hope this helps.
Best Regards,
Ervin
Hi Saurabh,
Maybe your buildspace needs to be re-created/re-built?
Please check this thread to see if it's relevant
http://scn.sap.com/thread/2053876
Hope it helps.
Dao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, as Dao said, if the unwanted DCs are still somehow there, then delete the CBS buildspaces (both DEV and CONS) and resave the track, and do the import afterwards. This will ensure that before you do the import the CBS buildspaces are really empty, but do this only if my above suggestion would not help.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.