understanding Software Components (SCs)

[Former Member]

I'm slowly getting a handle on configuring and putting a JDI into practice. What I don't understand is the concept of assigning SC's to a track. I have created a development track, and can import it into NWDS. We have 2 basic J2EE Web Dynpro projects going on that are going to enhance functionality of an SAP SD module process. How do I know which SC to assign, or how to go about finding it in the list of 3000+ of them?

[Former Member]

We aren't modifying existing SAP objects. We're building Web dynrpos that will basically replace some of the heavily used SAP GUI transactions to better tailor the front end experience.

[Former Member]

In that case you should create your own Product(s) and SC(s). Do not forget to define to correct Usage Dependencies for your own SC(s). These are normally SAP_BUILDT, SAP_JTECHS and SAP-JEE.

In case you want to build portal applications on NW2004s you also need a dependency for EP_BUILDT. This is new in NW2004s: the portal application build plugins have been removed from SAP_BUILDT and moved to this new SC, together with some new plugins. These new plugins cannot be used yet however, since there are no component types defined that use them in the current release of NWDS.

[Former Member]

Maybe it will be helpful if you consider SCs as "Shipping units". It's the way SAP delivers software to customers and it is also the way that you can deliver your software/products. It is basically a container that says "We will ship these (development) components together".

[Former Member]

First of all: You can only modify SAP components if you have the source code for them. If you do, the SCA that contains this source code can tell you the name of its SC.