Ansicht
Dokumentation

WCF_GENIL_VIEW_DEF - Define Views

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this Implementation Guide (IMG) activity, you assign read views to component sets of the generic interaction layer.

Additionally, you define the object quantity of the read views and configure the structure of the objects that are combined in a read view.

Using read views improves system performance and is optional. Objects in read views can be bundled and called in the Business Object Layer, which enables the screen layout to be displayed faster.

You should only use this activity if you want to define your own read views for your application.

There must be at least one component set defined in IMG activity Basic Settings.

The standard version of this IMG activity contains all required entries for all SAP applications that use the generic interaction layer.

The existing entries should neither be changed nor deleted since these actions could affect other applications that are based on the generic interaction layer.

Define View area

Define a technical view name and assign the desired component set. The F4 help provides a selection list of the component sets that were defined in IMG activity Basic Settings. Mark the component set as a default.

You can assign multiple component sets to a read view. This view is then valid for the assigned component sets. To do so, repeat the view name in the following row and assign another component set, and so on. You must mark one component set as the default for the respective view. The entries in the F4 input help of an object are defined using the standard set in the Maintain View area of the screen.

Maintain View area

The possible combinations of root objects, higher-level objects, objects, and relations appear in the model browser for the generic interaction layer (transaction GENIL_MODEL_BROWSER). You can use this transaction to plan the combination of your read view and then define it accordingly in this activity. Note that only the combinations that appear in transaction GENIL_MODEL_BROWSER are possible.

In each row, enter an object with all the necessary information:

• Enter the root object. A view has one root object with no higher-level object. The root object must be an access object. The available access objects appear in the model browser for the generic interaction layer.

• The other objects in a view always have a uniquely definable higher-level object and an object name and object type:

• Enter the object name and assign a number that is unique to this object in this view.

• Enter the number of the higher-level object.
  You can enter an object as a higher-level object as often as you like, as long as the desired combination is possible according to transaction GENIL_MODEL_BROWSER.

• The possible values appear for column Relation to Higher-Level Object in the F4 input help. Choose the appropriate relation.

• You can use the Inactive column to deactivate certain object assignments within a read view, if you like.

• If an object assignment within a read view is no longer needed, you can delete it.

ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3724 Date: 20240523 Time: 214901     sap01-206 ( 79 ms )