Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Public part incomplete for generated SC

Ok, first some background information.

I have two SCs in the same product: SC1 and SC2. Each SC is developed on it's own track - in this case, SC1 is developed on TSC1, and SC2 on TSC2. There is a track connection from TSC1 -> TSC2.

There are two DCs in SC1: an External Library contains 11 jar files (all of which have been added to a public part), and a J2EE Server Library that references the External Library. The resulting SDA does contain all 11 archives.

After checking in and activating the changes as well as releasing the transport, SC2 is successfully built, and placed into the queue for the Development System for TSC2. I can import the package, and after download the developer config, I can see SC1 and SC2 both in TSC2.

PS: I had to alter the XML configuration for SC2 in TSC2 to specify the compartment dependancy, as per another message on SDN. Before I did this, I was unable to create a usage relationship between the two SCs.

Now, the problem.

When I synchronize the components on my workstation, only 1 (one!) jar file is downloaded with SC1, instead of the 11 that were part of the original SC. The PublicPart XML file contains references to each jar file, but only one has a FileSet declaration, so it seems that the construction of SC1 in the JDI is flawed.

Has anyone else ran into this problem? This seems pretty basic to me, and as it stands right now, it's a show stopper.

BTW, we're on SP16, both on the JDI side, and on the Dev.Wkstn side.

When I try

Former Member
Not what you were looking for? View more on this topic or Ask a question