Hierarchy
⤷ BW-BEX-OT (Application Component) OLAP Technology
⤷ RSDD_LTIP_TREX_CONNECTION (Package) Connections to TREX Servers
Basic Data
Data Element | RSDDLTIP_DEST_ABBR |
Short Description | Single Character ID for TREX Destination |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | ID Dest. |
Medium | 15 | ID Dest. Short |
Long | 20 | ID Destination Short |
Heading | 0 |
Documentation
Definition
Single character ID for identification of Destinationf for Analytical Indexes.
Use
If you have set up multiple destinations for analytical indexes on your BW system, use a single-character ID in the name of the TransientProvider to identify the analytical index in question.
The single-character ID is not used for the destination in the default BWA.
You can find the InfoProvider name in the settings for the analytical index (maintenance).
Dependencies
Example
You have two destinations DEST_DEFAULT and DEST2 for analytical indexes. Destination DEST_DEFAULT is marked as the default BWA. For DEST2, create a single-character ID "Y".
You have created an analytical index called "myindex" in the default BWA and filled it with data. The associated TransientProvider is then called "@3MYINDEX".
Now create an analytical index "myindex2" on the TREX server at destination DEST2. The associated TransientProvider is then called "@3@YMYINDEX2". The single-character ID is therefore part of the TransientProvider name.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 730 |