Ansicht
Dokumentation

_CRM_SI_WB_VC - Define Object Workbench Profiles

CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Objects can be identified and edited in the object workbench using role-dependent defined search functions.

You can use the workbench profile to assign the search functions and the object detail views to a user role. The workbench profile can be assigned to the user role as a function profile.

You can define the following in this Customizing activity:

• You can define views, which you can use in the object workbench as search, search result or object detail views.

• You can create search functions, which are used to control the corresponding search criteria or displays of the search results.

• You can define object detail views to represent objects of different types with their respective attributes in the object workbench.

• You can maintain templates for creating new objects using the object workbench.

• You can define profiles to combine the search functions and object detail views created previously and assign them to a user role.

The view repository defines all views to be used in the object workbench.

First create the views required as usual in the system. A view can only be used in the workbench if it is identified in the view repository. To do so enter the BSP application and BSP view and assign a usage (search, search result or detail view) and the BOL type to be displayed. Views that you have defined in this way can now be used in the search functions and object details.

The BSP views, which you want to use in the object workbench must meet certain prerequisites:

The view controller classes must inherit from the following abstract basic classes:

• CL_CRM_IU_IC_OBJ_QUERY_VIEW (Search view)

• CL_CRM_IU_IC_OBJ_RESULT_VIEW (Search result view)

• CL_CRM_IU_IC_OBJ_DETAIL_VIEW (Object detail view)

The context for views should consist of a model node that is connected to the component context node SEARCH (search view) or SEARCHRESULT (search result view). The model node must inherit from the abstract basic class CL_CRM_IU_IC_OBJ_DETAIL_CNODE and be connected to the component controller using the specialist DO_CONTEXT_NODE_BINDING_PLUS method in the view controller basic class CL_CRM_IU_IC_OBJ_DETAIL_VIEW.

The search functions describe the search criteria and display of the corresponding search results. The system offers the user the search functions that have been assigned to their user role via the workbench profile in a selection list.

Assign a view from the view repository to the search function. You can use the F4 Help to select a view that has been defined as a search view. If you require address variants for the search criteria, you can select the Use Address Variants for Search Criteria indicator.

The search result can be displayed using a search result view or a results tree. If you want to use a search result view, you can select the corresponding F4 Help.

If you require address variants for the search results view, you can select the Use Address Variants for the Search Results View indicator.

Alternatively, the search result can be displayed using a results tree. Select a corresponding object hierarchy profile. Two different profiles can be assigned for display in wide (100% window) or narrow (50% window) mode.

The Unique Search Instance indicator controls whether the search function can be used in the user profile in isolation from the other search functions in the user profile. The system does not exchange any attributes or search criteria with other search functions during the runtime. Entering search criteria therefore does not affect other search functions. The standard system response is for BOL attributes with the same names to be exchanged between search functions. The system only observes visible search criteria for the search inquiry here.

To define the layout of the search view, select the UI object type required in the configuration tool for the associated BSP view. The system offers you the search function as a subobject type via the F4 Help.

If you have activated address variants for a view, the system also offers you the corresponding variants as subobject types.

The following UI object types are supported for search views:

• IUICOBJSEA_COBQ,,IS-U/T Object maintenance search view: Connection object search

• IUICOBJSEA_PODQ,,IS-U/T Object maintenance search view: Point of delivery search

• IUICOBJSEA_PRMQ,,IS-U/T Object maintenance search view: Premise search

• IUICOBJSEA_SCPQ,,IS-U/T Object maintenance search view: Service access point

• IUICOBJSEA_TOBQ,,IS-U/T Object maintenance search: Technical object search

• IUICOBJSEA_TOCQ,,IS-U/T Object maintenance search: Cust.-spec. T.Obj.src

The following UI object types are supported for search result views:

• IUICOBJRES_COB,,IS-U/T Object maintenance search result view: Connection object

• IUICOBJRES_POD,,IS-U/T Object maintenance search result view: Point of delivery

• IUICOBJRES_PRM,,IS-U/T Object maintenance search result view: Premise

• IUICOBJRES_SCP,,IS-U/T Object maintenance search result view: Service access point

• IUICOBJRES_TOB,,IS-U/T Object maintenance search result view: Technical object

Object detail views are used in the object workbench to display different objects. You can use the F4 help to assign a view from the repository to the object detail view. The view text assigned here is used as a header in the object workbench. You can use the placeholders &1, &2, &3 and &4 to incorporate dynamic values from the object displayed in this text. You can select the corresponding path for the BOL attribute using the F4 Help.

You can use groupings to position attributes for an object in different layouts in the object detail views. To do so, select a grouping mode and create the corresponding groupings for the object detail view. The system offers the user tab pages or a selection list according to the mode selected so that you can switch between the groupings/layouts.

If you require address variants for the object details, you can select the Address Variant indicator.

To define the layout for the object detail views, select the UI object type required in the configuration tool for the associated BSP view. The system offers you the object detail views as a subobject type via the F4 Help.

If you have activated address variants for a view the system also offers you the corresponding variants as subobject types.

If you want to use groupings, the system offers you these as subobject types.

The following UI object types are supported for the object detail views:

• IUICOBJDET_COB,,IS-U/T Object maintenance detail view: Connection object

• IUICOBJDET_PCO,,IS-U/T Object maintenance detail view: Service access point in the provider order

• IUICOBJDET_POD,,IS-U/T Object maintenance detail view: Point of delivery

• IUICOBJDET_PPD,,IS-U/T Object maintenance detail view: Technical object in the provider order

• IUICOBJDET_PPM,,IS-U/T Object maintenance detail view: Premise in provider order

• IUICOBJDET_PRM,,IS-U/T Object maintenance detail view: Premise

• IUICOBJDET_SCP,,IS-U/T Object maintenance detail view: Service access point

• IUICOBJDET_TOB,,IS-U/T Object maintenance detail views: Technical object

You can define templates to create structured objects (such as connection object - premise - point of delivery). To do so, assign an initial object to the template, which is used to define the template selection during the runtime. If you for instance want to create a template for creating a premise, specify the connection object as the initial object. If the user now selects a connection object, the system offers them the template for creating a premise in the object workbench. If a completely new installed base is to be created, choose Installed base 2 levels or Installed base 3 levels.

The template hierarchy enables you to create several objects in parallel or hierarchically. To do so, enter the preceding object here or leave an initial value in this field if new objects are to be created directly for the initial object.

The following hierarchies or sections are supported:

• Installed base 2 levels -> Service access point -> Technical object

• Installed base 3 levels -> Connection object -> Premise -> Point of delivery

You can maintain the default attributes for each new object that is created. These are assigned to the new object if a template is used.

In addition to the default template objects, you can enable the Maintain Equipment checkbox by activating the CRM_UT_EQP_1 switch. To enable this checkbox, you must maintain the Equipment folder in the Customizing activity Define Object Hierarchy and Object Attributes for Customer Relationship Management under Industry-Specific Solutions -> Utilities Industry -> Settings for User Interfaces -> Settings for Object Workbench. As an example, you can refer to the profile IUIC_SL3.

The profile for the object workbench combines various search functions, object detail views and templates. Assign an object hierarchy profile to the profile so that hierarchical display of objects is possible in the object workbench.

The object workbench profile also defines the user authorization: You can define here whether the user is allowed to create or modify specific objects.

When assigning search functions or object detail views, you can override specific texts according to the profile. The system can offer the user the search functions in a specific order using the Positionfield.

You can use the function profile IUICOBJ to assign the object workbench profile to the user role in SAP CRM.

CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 11451 Date: 20240523 Time: 182922     sap01-206 ( 202 ms )