Ansicht
Dokumentation

CRM_IC_OVW_VIEW - Register Views for Overview View Sets

CRM_IC_OVW_VIEW - Register Views for Overview View Sets

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you can access the overview view repository and register additional views for use in overview view sets.

For each view, you can display technical details and a view description. This information is useful when you select the views that you want to use in your overview view set.

In the overview view repository, you can register views for use in overview view sets. You can register your own views that you have developed especially for the overview view sets as well as all "conventional" views in the Interaction Center (IC) WebClient.

Please note, however, that because of implementation dependencies that a view may have upon custom controllers, certain view sets, or other views, there is no guarantee that all conventional views can be seamlessly integrated into an overview view set.

You can reuse all views that are registered in this Implementation Guide (IMG) as often as you like; You need only register the views once, rather than multiple times using different technical names.

There is no need to manually record the overview views or the overview view sets in the runtime repository.

Note:

In this IMG activity, you are simply mapping the existing implementation of the views; you cannot change the views. It is only possible to implement and edit views from the workbench.

Ensure that you represent the views correctly during registration so that they will function properly in the overview view sets.

You have implemented one or more views or you know the name of the view that you want to use in addition to the dedicated overview view.

If you define your own overview views, you must observe the following:

  • The delivery class of the view repository is "E".
You can define your own views in the customer namespace (beginning with X, Y, or Z). The name of the overview view does not need to be the same as the implementation name of the view in the workbench.
  • For a view to use the infrastructure of the overview view set fully, the implementation class of its view controller must implement the ABAP interface IF_CRM_IC_OVW_VIEW_CONFIG.
We recommend deriving the implementation class of the view controller from abstract basis class CL_CRM_IC_OVW_VIEW_BASE. Views that do not implement this interface have no influence on the tray title and tray mode; in addition, they do not receive any configuration values.
  • A view that transfers its own tray tag has no influence on the tray title or tray mode. It also does not get any automatic tab links if other views are assigned to the same view area in an overview view set.
  • In special cases, for navigation links, you can define a corresponding return link for backward navigation. This return link allows the view that is accessed in this navigation to trigger backward navigation. This function is only required in special cases and is dependent upon the implementation of the target view.

The standard system contains views that were created especially for use in overview view sets.

Specify all views that you want to use in overview view sets.

Specify the following view attributes:

  • Name and language-dependent description of the overview view set
  • Business Server Page (BSP) application (including namespace) and BSP view name (without suffix) of the view that implements the overview view
  • Whether the tray tag from the overview view set should be available, or whether a separate tray tag exists
  • The view area size that the view is meant for, or whether the view should adapt to the available view area size
  • ABAP dictionary structure that defines the fields for view-specific configuration
  • Language-dependent long text documentation that describes the function of the view
  • Navigation links that activate the view in its implementation; if necessary, a standard navigation target per navigation link that is used at runtime, if it is not redefined by the use of the view in the overview view set.






TXBHW - Original Tax Base Amount in Local Currency   General Material Data  
This documentation is copyright by SAP AG.

Length: 4538 Date: 20240523 Time: 162155     sap01-206 ( 74 ms )