Hierarchy

⤷

⤷

Basic Data
Data Element | RSDMEM_DATA_SOURCE_NAME |
Short Description | Source Name |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RSDMDM_DATA_SOURCE | |
Data Type | CHAR | Character String |
Length | 72 | |
Decimal Places | 0 | |
Output Length | 72 | |
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 | Src Name |
Medium | 15 | Source Name |
Long | 20 | Source Name |
Heading | 30 | Source Name |
Documentation
Definition
Specifies the name of the query that is used as a training, evaluation or prediction source.
Use
You must enter the query name in the following format:
I_<cube name>_<query name>.
The query used should be released for OLE-DB for OLAP. This could be set in the query properties in the BEx analyser.
For decision tree and clustering, you must use a query having data that is unique with respect to the model keys specified in the model.
For association discovery analysis, you must ensure that the query has two fields , that is, one representing a transaction and the other representing the item. In a cross selling scenario, the transaction could correspond to a sales transaction or to a customer. In a web log analysis scenario, the transaction could correspond to the session id.
For prediction source (or evaluation source in case of decision tree), you must ensure that the fields of the query are logically related to the model fields.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 21C |