View configurations are determined according to a special search sequence. Sometimes it seems that the framework has not found the correct configuration. The following table describes the search logic of view configurations.
| Role Key | Component Usage | Object Type | Object Sub Type |
1 | X | X | X | X |
2 | X | X | X | |
3 | X | X | X | |
4 | X | X | X | |
5 | X | X | ||
6 | X | X | ||
7 | X | |||
8 | X | X | ||
9 | X | |||
10 | X | |||
11 |
This means, the framework first looks for a matching configuration with all four attributes. The second search uses <DEFAULT> as Object Sub Type. The third search uses <DEFAULT> as Component Usage. Etc. - The first found configuration will be used.
Background information: The search is implemented in class: CL_BSP_DLC_XML_STORAGE2 methods PROC_ACC_SEQ_FOR_SEARCH_KEY/CHOOSE_CONFIG_BY_AC_SEQ_NEW.
Hint: With enhancement BSP_DLC_ACCESS_ENHANCEMENT you can add your own determination.