Hierarchy

⤷

⤷

Basic Data
Data Element | BS_CT_INSTRUMENT_TYPE |
Short Description | Context Instrument Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BS_CT_INSTRUMENT_TYPE | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | BST_CT_INSTRTYPE |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | InstrType |
Medium | 15 | Instrument Type |
Long | 20 | Instrument Type |
Heading | 20 | Instrument Type |
Documentation
Definition
Nomination of runtime information that is used to determine context accords.
Use
An instrument type corresponds to a specific kind of runtime information. A concrete value of that information is called instrument. An instrument type defines both, theperception and the type of an instrument.
By composing instrument types to actual instruments an arrangement of context accords is done in a way that allows to find an unique context accord.
Dependencies
Example
The instrument type Web Dynpro Application defines a perceiver that determines the name of the currently running web dynpro application. Hence for that instrument type the name of a web dynpro application is an actual instrument, for example BS_OVP_BP.
Composing example:
The sequence of instrument types is the following:
Instrument Type Sequence Description
WD_CONFID 100 Web Dynpro Application Configuration ID
WD_APPL 200 Web Dynpro Application Name
The composing is like:
Instrument Type Instrument Context Accord
WD_APPL BS_OVP_BP BS_BP
For the first instrument type Web Dynpro Application Configuration ID no composing is found hence the perception goes on to the next instrument type Web Dynpro Application Name. The perceiver of that instrument type is returning the current instrument, here the name of the currently running web dynpro application. If that instrument corresponds to a composed one, the associated context accord is selected as the actual one for the current runtime environment. If the web dynpro application BS_OVP_BP is currently running then the context accord BS_BP is being concerted.
But if the composing is enhanced the result might be different.
Instrument Type Instrument Context Accord
WD_APPL BS_OVP_BP BS_BP
WD_CONFIG BS_OVP_SP BS_SP
With the sequence illustrated above the perception firstly determines the current WebDynpro application configuration ID of the currently running WebDynpro application. The composition is checked for WebDynpro application configuration IDs now and, if the current ID is found there then the assigned context accord is being concerted. For example if there's a configuration ID BS_OVP_SP existing for WebDynpro application BS_OVP_BP and this application is currently running utilizing that configuration ID then the perception of instruments will find a corresponding composition for the first instrument type already, which is WebDynpro Application Configuration ID. Hence, running the application with that configuration ID will lead to concerting context accord BS_SP, whereas all other potentially existing configuration IDs of the same application will still concert context accord BS_BP. Note, that in that case according of BS_SP most probably should at least contain the same Context IDs as according of BS_BP to ensure that all contextual information is still accessable when running this application with that configuration ID, otherwise you might get runtime exception errors if a component mandatorily requires a particular Context ID.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 731 |