NWDI broken by itself DC('s)

Question

Hi
I'm also very new to NWDI.
For a customer were busy with XSS/ESS. When starting NWDI i've got hunderds of broken by Itself DC's
Impoting SC resolved most of them.
No I only got one left : ess/tw/addr
So the question is how do I figure out to which SC the DC ess/tw/addr is missing ?
Marcel Nijskens

Answer 1

Answers are usefull, but we've gotten to the customer were I don't know if the NWDI environment is set up properly.
Checking in the SC each time gives a different amount of broken DC"s ?
Which implies the order of checkin in is important (correct me if not) I used this order (found on SDN)
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 (TAKES A LONG TIME) gives exclusinve lock messages
SAPPCUIGP10P_2-20001215.SCA sap.com_SAPPCUI_GP 600 10
EPPSERV13_0-10003474.SCA sap.com_EP-PSERV 7.00 13
EPWDC13_0-10003557.SCA sap.com_EP-WDC 7.00 13
EPBC13_0-10003473.SCA sap.com_EPBC 7.00 13
EPBC213_0-10003489.SCA sap.com_EPBC2 7.00 13
SAPEU13_0-10003026.SCA sap.com_SAP-EU 7.00 13
Should I check in all sc's and then build them or check in an SC build it and then the next SC's ?