Hierarchy

⤷

⤷

Basic Data
Data Element | OLR3_TV_STRATEGY |
Short Description | Strategy |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OLR3_STRATEGY | |
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table |
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 | Strategy |
Medium | 15 | Strategy |
Long | 20 | Strategy |
Heading | 35 | Strategy |
Documentation
Definition
Further specifies a method.
The strategy is an additional key which uniquely describes a combination of method and table/view.
Use
Depending upon the method, it can be useful to define various strategies:
- Origin of data for existence check
In this case only one strategy is useful.
- Origin of the data for consistency check
In this case only one strategy is useful.
- Search help
The ERP system must search in various views, depending upon which search criteria you enter. You must define a strategy for this method per view.
When the method is called the system reads exactly one strategy (matching a concrete usage of the search help criteria).
- Origin of the data for date retrieval (evaluation/detail screen)
If multiple sources exist from which the data should be read, you must create a strategy for each of these sources.
When the method data retrieval is called, the system reads all strategies.
- Date retrieval for the date graphic in SAP Portfolio and Project Management
In this case only one strategy is useful.
- Origin of data for determining the language-dependent short text
In this case only one strategy is useful.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20141109 |
SAP Release Created in | 200 |