cancel
Showing results for 
Search instead for 
Did you mean: 

NWDI broken by itself DC('s)

Former Member
0 Kudos

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

Accepted Solutions (1)

Accepted Solutions (1)

nitin_mahajan2
Contributor
0 Kudos

As this is all standard content, I would suggest build the DC and check the build logs. It would specifically tell you if any dc / dependency is missing. Then you can verify which DC is missing.

There may be a possibility that you would have added the DC as a dependency but that DC is not checked in.

Regards,

Nitin

Former Member
0 Kudos

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 ?

nitin_mahajan2
Contributor
0 Kudos

Yes, check in all DCs that you have imported.

Use them till assembly once.

I had the same problem, where in my DCs were fine in NWDS but in NWDI i was getting all broken DCs. The issue was one of the SCAs was not checked in.

I hope yours is the same issue. Good Luck.

Regards,

Nitin

Answers (1)

Answers (1)

thulasi_td
Employee
Employee
0 Kudos

Hi Marcel,

The DC ess/tw/addr is part of SAP_ESS SC.

Please ensure your have checked-in all the required build time dependencies.

such as SAP_BUILDT, SAPJTECHS, SAP_JEE, SAPPCUI_GP...

Regards,

Thulasi