Skip to Content

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

Public Part Definition Question

This is first time I've done an Software Component with multiple dependent DCs. All the DC's are web dynpro components. When I check in the code - All are building fine but in the deployment step the Utility DC for some reason is marked as Dirty.

What I have is the following

Model DC - used in Rpts DC

Utility DC - used in the IFace DC and Rpts DC

IFace DC - used in Rpts DC

in the Used DCs here are is component info for each --- did I define these right? Rpts DC is the only application used by the end user. The Utility DC (hind site said should be a Library DC but it's too late in my development to do that now is a bunch of utility Java Classes) has a Calendar class (based on Gregorian Calendar with all the other things we do with dates - LOVE IT). Should I modify the Design/Run time options? I've read the SAP help and it didn't..... How do I declare the public parts?

BuildTime DeployTime DesignTime RunTime

IFace DC

util T F T T

Rpts DC

iFace T F T T

Model T F T T

util T F T T

Rpts DC

iFace T F T T

Model T F T T

util T F T T

===== Processing ===== 
BUILD DCs
	"spiritaero.com/dogs/attendtrack/util" in variant "default"
		Public Part "DogsUtilityPP" has been changed. Dependent components will be marked as DIRTY and re-built later.
		The build was SUCCESSFUL. Archives have been created.
	"spiritaero.com/dogs/attendtrack/dogsiface" in variant "default"
		Public Part "DogsInterfaceModelPP" has not been changed.
		The build was SUCCESSFUL. Archives have been created.
	"spiritaero.com/dogs/attendtrack/rpts" in variant "default"
		The build was SUCCESSFUL. Archives have been created.
===== Processing =====  finished at 2008-10-20 12:49:57.701 GMT and took 1 m 23 s 656 ms


===== Post-Processing ===== 
Waiting 46 ms


Check whether build was successful for all required variants...
	"spiritaero.com/dogs/attendtrack/util" in variant "default"   OK
	"spiritaero.com/dogs/attendtrack/dogsiface" in variant "default"   OK
	"spiritaero.com/dogs/attendtrack/rpts" in variant "default"   OK

Update component metadata...
	"spiritaero.com/dogs/attendtrack/util"  has been CHANGED
	"spiritaero.com/dogs/attendtrack/rpts"  has been CHANGED

STORE build results...
	"spiritaero.com/dogs/attendtrack/util": store meta-data
	"spiritaero.com/dogs/attendtrack/util" in "default" variant  is PROCESSED
	"spiritaero.com/dogs/attendtrack/dogsiface": store meta-data
	"spiritaero.com/dogs/attendtrack/dogsiface" in "default" variant  is PROCESSED
	"spiritaero.com/dogs/attendtrack/rpts": store meta-data
	"spiritaero.com/dogs/attendtrack/rpts" in "default" variant  is PROCESSED
Change request state from PROCESSING to SUCCEEDED

Analyse effect of applied changes to buildspace state... started at 2008-10-20 12:49:58.936 GMT

Handle Cycles...
	No cycles detected.
Activation will FAIL because it would break the following request components:
	"spiritaero.com/dogs/attendtrack/rpts"
===== Post-Processing =====  finished at 2008-10-20 12:49:59.822 GMT and took 2 s 75 ms
Change request state from SUCCEEDED to FAILED


ERROR! The following problem(s) occurred  during request processing:
Request FAILED.


REQUEST PROCESSING finished at 2008-10-20 12:49:59.941 GMT and took 1 m 43 s 629 ms

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