Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose 

This page is to explain how system sets the search key and uses opportunity details view as an example.

Overview

Sometime you open the view and notice that the used configuration is not what you expected. A view can have several configurations. During runtime system will determine which configuration is used based on the search key. The search starts with the definitive parameters in the search configuration key and, if this is not successful, fewer parameters are used step-by-step until a configuration is successfully determined. So to determine a correct configuration, the search key must be filled correctly. This page describes how system sets the search key.

Press F2 to get the configuration information

Logon with the business role SALESPRO, go to opportunity search screen, search and open an opportunity, move the cursor on the field Prospect in the Opportunity Details view, press F2 on the keyboard, then the Technical Data popup appears. In the Configuration part of the popup, you will see the search key and the found key.

 

The search key, which contains four parameters, is:

Role Key (Searched For): SALESPRO

Comp. Usage (Searched For): CUBTOpptOverview

Object Type (Searched For): BT111_OPPT

Subobject Type (Searched For): YK02

 

The found key is:

Role Key (Found): <DEFAULT>

Comp. Usage (Found): <DEFAULT>

Object Type (Found): <DEFAULT>

Subobject Type (Found): <DEFAULT>

Role Key and Component Usage set by framework

The Role Key is automatically determined by the Business Role the User is logged on for and it can be defined in view CRMV_UI_CONFIG. You can check method CL_BSP_DLC_CONFIGURATION2->CONSTRUCTOR to see how role key is set.

The Component Usage is automatically set by the Framework and it is derived from the component usage itself. You can check method CL_BSP_WD_VIEW_CONTROLLER->WD_VIEW_INITIALIZE to see how component usage is set. 

Object Type and Subobject Type set by application 

The Object type and Subobject type is set by the application in method DO_CONFIG_DETERMINATION. For business transaction, it is set in method CL_CRM_BT_WINDOW->DO_CONFIG_DETERMINATION.

For business partner, the method CL_BP_HEAD_BPHEADOVERVIEW_IMPL->DO_CONFIG_DETERMINATION, CL_CRM_BUPA_VIEW_CONTROLLER->DO_CONFIG_DETERMINATION, and CL_BP_HEAD_ACCOUNTDETAILS_IMPL->DO_CONFIG_DETERMINATION are used to the set the object type and object subtype

If you do not know in which class the method DO_COFNIG_DETERMINATION is defined in your application, you can set breakpoint in the following class which will call the method DO_CONFIG_DETERMINATION, and debug: 

CL_BSP_WD_WINDOW->DO_REQUEST

CL_BSP_WD_OVW_VIEWSET->DO_REQUEST        

CL_BSP_WD_VIEW_CONTROLLER->DO_REQUEST 

With this way, the breakpoints will be reached several times and you only need to debug into when it is the view you are concerned.

Related Content

Related Documents

Related SAP Notes/KBAs
__________________________________________________________________________________________________________

Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.

  • No labels