Context Key
You use this function to specify a combination of application and business object that distinguishes the configuration of BCV in your application from any other configurations that might exist in the system.
Structure of the Context Key
As Business Context Viewer (BCV) is an application that several other applications can use at the same time in the same system, it is necessary to separate the configuration settings of the individual applications. The context key identifies the application using BCV and the business object it processes.
In case the application uses BCV in several instances, we recommend that you include the identifier of the business object in the context key.
If the application uses a namespace, the context key must start with this namespace. In this case, the namespace serves as the identifier for the application.
The Influence of the Context Key on the Presentation of Data
The context key influences the way the business objects in BCV, for example queries and query views present data.
The following table describes this influence on the different BCV objects:
BCV Object |
Influence of the Context Key |
|---|---|
search connector |
None. You can use any search connector in any application with any context key. This approach supports the reuse of search connectors. You can restrict the visibility of data by applying the necessary authorization restrictions. For more information, see Authorization Concept in Business Context Viewer (BCV). |
query |
You can assign a query to one or several context keys. You cannot display data from queries that have no context key assignments. A query and its query views can be seen in any application that is specified in the context key. |
query view |
You can define several query views for one query, and a query view can belong to more queries. All queries assigned to the query view must have at least one context key in common. Query views automatically inherit the context key assignment of the query they are assigned to. If you change the assignment of the query, the context key assignment of the query views belonging to that query also change. |
dashboards and quick views |
Dashboards and quick views are always assigned to one context key, and you cannot change the context key assignment of these objects. Both can contain only queries and query views that are assigned to the same context key. If you change the context key assignment of a query, the corresponding query views do not appear as quick views anymore. If various applications need the same dashboard, it must be defined individually for each application with the context key of each application assigned to it. |
Business Add-In (BAdI) Filter
The context key has an ID which contains a part identifying the application using BCV, and a part identifying the processed object (this is required in case the same application uses BCV for several different business objects). The part of the context key that identifies the application is used as a filtering value for several BAdIs in BCV (for example, BAdI: Unit Conversion (/BCV/FND_UNIT_CONV) or BAdI: Currency Conversion (/BCV/FND_CURRENCY_CONV). The behavior of these BAdIs can depend on the application where they are implemented.