Hierarchy
⤷ BW-WHM-DBA (Application Component) Data Basis
⤷ RSD_IPRO (Package) BI InfoProvider
Basic Data
Data Element | RSHYBRTYPEX |
Short Description | Creation Types of a HybridProvider |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 0 | |
Medium | 15 | Creation Mode |
Long | 0 | |
Heading | 0 |
Documentation
Definition
When you create a HybridProvider, you can decide whether the HybridProvider consists of
- an InfoCube with a DataStore object that has a data store in the BW system,
- or an InfoCube with a VirtualProvider. The data of the VirtualProvider is located outside of the BW system and is read using a function module.
You can also decide whether to store the data of the InfoCube in a standard InfoCube or in the BWA.
With both options (DataStore object or VirtualProvider), you can
- use an existing object as the basis
- or define a completely new HybridProvider.
Note that if you create a HybridProvider based on an existing provider, this existing provider can "lose its independence". In other words, you cannot maintain or transport this provider anymore, because it is now part of the HybridProvider.
When the HybridProvider is created;
- and it is a completely new HybridProvider, it does not contain any InfoObjects
- and it is based on an existing InfoProvider, it starts with the same InfoObjects and further InfoObjects can be added to it.
The associated, required InfoCube is created in any case.
You should choose the second option, if you want to change an existing InfoProvider, including the environment (queries, data, transformation rules and so on), into a HybridProvider.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 710 |