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

The purpose of this page is to explain how UI configuration is determined at runtime.

UI Configuration Determination

In the CRM Web UI the configuration of views is based on configurations that have been created with the UI Configuration Tool. With the UI configuration tool, it is possible to create multiple configurations using the different keys for one view. The keys are role configuration Key, component usage, object type, subobject type (depending on the Object Type). During runtime the configuration to be used to visualize the layout is determined based on the search key set at runtime. Using the search key the corresponding successful key is determined.

Search Key:

Combination of parameters (role configuration key, component usage, object type, and sub object type) that is returned at runtime. This combination of parameters is used to determine the configuration.

Successful Key:

Combination of parameters (role configuration key, component usage, object type, and sub object type) with which a configuration was found. The successful key is the key that most closely matches the search key, but which is not necessarily identical to the search key.

The  role config Key is automatically determined by framework based on the Business Role the User is logged on for. The Component Usage is automatically set by the Framework as it is derived from the component usage itself. The  object type and subobject type are set by application.

Access Sequence

To determine the configuration during runtime, the access sequence as shown in the below table is executed.

The search starts with the search key with definitive parameters from the customer configuration and, if this is not successful, fewer parameters are used step-by-step. If no configuration is found from customer configuration, it searches from the standard configuration, and the access sequence is identical. The parameters with which a configuration is successfully determined are called 'successful key'. 

Example

The example used here is the sales order details screen.

Component: BT115H_SLSO

View: DETAILS

This view has several configurations as shown below:

In the CRM WebUI, the user logs on the system with the business role SALESPRO and displays an sales order with transaction type TA. During runtime, the configuration is determined using this search key, which consists of:

Role Configuration Key: SALESPRO

Component usage: CUBTSalesOrder

Object Type: BT115_SLSO

Subobject Type: TA 

First, the customer configurations are checked. According to the access sequence, system starts searching for a configuration with key: 

Role Configuration Key: SALESPRO

Component usage: CUBTSalesOrder

Object Type: BT115_SLSO

Subobject Type: TA 

no configuration is found, then system searches for a configuration with key: 

Role Configuration Key: SALESPRO

Component usage: CUBTSalesOrder

Object Type: BT115_SLSO

Subobject Type: <DEFAULT>

no configuration is found, then system searches for a configuration with key: 

Role Configuration Key: SALESPRO

Component usage:  <DEFAULT>

Object Type: BT115_SLSO

Subobject Type: TA 

still no configuration is found, then system continues the searching according to the access sequence, until the configuration with the default values in the customer configuration is found.

After the sales order screen appears,  put the mouse cursor in any field of the Sales Order Details view, press F2, the left hand side shows the search keys and the right side shows the found keys which is the successful keys that actually have been found in the configuration, and the configuration origin is "Customer Configuration".

Badi to Change the Access Sequence Logic

The customer can change the standard access sequence logic completely by implementing Badi DLC_CONFIG_ACCESS_BADI. You can refer to the following IMG documentation for details:
Customer Relationship Management -> UI Framework -> UI Framework Definition -> Business Add-Ins -> Define Configuration Access 

Technical Information

CL_BSP_DLC_CONFIGURATION20->IF_BSP_DLC_CONFIGURATION~GET_CONFIG_DATA is used to get the configuration.

CL_BSP_DLC_XML_STORAGE2=>PROC_ACC_SEQ_FOR_SEARCH_KEY is used to process Access Sequence for search key.

Table BSP_DL_XMLSTRX2 stores standard configuration data.

Table BSPC_DL_XMLSTRX2 stores customer configuration data.

Report BSP_CXP_CONFIG_EDIT convers the configuration to the XML and you can edit the configuration.

 

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