Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-EI-APD (Application Component) Analysis Process Designer⤷
RSAN_WB (Package) APD - Tool - User Interface
Basic Data
| Data Element | RSAN_WB_DST_LIST_VEC |
| Short Description | Transformation "List -> Data Record" |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | STRG | Character String of Variable Length |
| Length | 0 | |
| Decimal Places | 0 | |
| Output Length | 0 | |
| 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 | Text |
| Medium | 20 | Description |
| Long | 40 | Description |
| Heading | 60 | Description |
Documentation
Use
Transforming a list into a flat data record makes it possible to change the internal data structure. In this way, a list of table lines that arrives at a node is transformed into a single-lined data record after processing.
The transformation of a list of data records into one data record takes place using a transformation field, usually a characteristic. In addition, you select a transposition field (usually a key figure) and its contents are placed into the new fields of the output structure depending on the characteristic value.
A new field in the output structure of the node can be assigned to each combination of a characteristic value of the transformation field and the selected transposition field. The new field shares the same technical definition as the transposition field. The values of all non-selected fields are forwarded to the subsequent node without being changed.
Activities
- In the Definition tab page, choose from all available fields a transformation field that is to be used to fill the new fields generated in the output structure.
- Choose a transposition field.
- In the Details tab page, assign a new field from the flat data record to each combination of a characteristic value from the transformation field and a transposition field. Enter a technical name for each new field. If you do not specify a field name, the value for this combination is not forwarded and is therefore not available for subsequent nodes after processing.
Runtime behavior
The input and output structure are different when a list is being transformed into a data record. The transformation field and the transposition field are not forwarded to the subsequent nodes. Instead, only the non-selected fields and the new fields defined in the details are forwarded. The structure for the data is wider in the data record form, that is, the internal tables of the analysis process have more fields, even though they contain less data. For this reason, problems can arise if characteristics with many characteristic values are to be used as a transformation field. If new field names are to be specified for all or many of the characteristic values, the maximium length of the data structures can be exceeded. In this case, expect the process to issue error messages.
Example
The questionnaire for a survey contains the questions and answers in table form, that is, each record contains as a characteristic the number of the question and as a key figure the value of the answer to this question. For the analysis, however, the data needs to be in a transformed form in which the answer to each question is made available in a separate field. Transformation into a data record can be used for this.
If the questionnaire contains 3 questions, then the input structure looks as follows:
Questionnaire No. Question No. Answer
A 1 2
A 2 1
A 3 4
B 1 3
B 2 2
B 3 1
If you transfer the questionnaire number directly and you define the question number as the transformation field and the answer as transposition field, then the output structure of the node has the following form:
Questionnaire No Answer to Ques.1 Answer to Ques.2 Answer to Ques.3
A 2 1 4
B 3 2 1
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 30B |
