Entering content frame

Procedure documentation Defining Usage Dependency for a DC Locate the document in its SAP Library structure

Only if there is an explicit usage dependency for a public part in the DC to be used can a used DC access each object from this public part. Parent DCs (as is the case with nesting) are the only DCs that do not require any usage declaration for a public part of the embedded DC since this is implicit.

Prerequisites

This graphic is explained in the accompanying text

The public part for the DC to be used exists already.

This graphic is explained in the accompanying text

You have already logged on to the DTR server.

This graphic is explained in the accompanying text

The project structure for the DC used is currently displayed.

Procedure

To create a usage dependency for a DC, proceed as follows:

...

       1.      In the project structure of the DC used, expand the subnode This graphic is explained in the accompanying textDC MetaData.

       2.      Open the context menu for This graphic is explained in the accompanying text Used DCs and choose Add Used DC.

Since all the changes so far have not yet been assigned to any DTR activity, the Select Activity dialog box appears now.

       3.      Now assign an activity.

The Used Help: Used DCs display frame appears.

       4.      Expand the tree for the relevant software component and then choose the public part for the required DC.

       5.      Enter the time when the dependency you are going to define is to be valid.

This graphic is explained in the accompanying text

       6.      Choose Finish.

Result

You have created the usage dependency for a DC to use a public part of another DC. In this way, the DC used can access all the development objects from this public part. 

See also:

Example: Using a Foreign Web Dynpro Component

 

 

 

Leaving content frame