Transfer Structure is a data enrichment function that can be used when data has to be enriched with calculated attributes, while also pre-aggregating the results based on all characteristics other than the condition fields themselves. If the conditions are not met, Transfer Structure retains the source data.
As a prerequisite, you have made available either the data model or the output from another business function that is to be enriched. The attributes for enrichment are available at calculation unit level or at environment level, depending on the level at which data enrichment is to be executed. You have identified the conditions to form the basis for the data enrichment. You have identified the fields to be derived.
On the Transfer Structure page, under the Fields road map step, choose an Input Function ID from the dropdown list.
Based on the business requirement, choose either Projection or Aggregation as the View Type.
Choose Add, add the attributes and mark them as calculated attributes.
To set the condition fields, choose Condition as the source category.
On the Rules road map: The number of key figures that have been retained for the function determines whether or not the Field Value column is displayed.
If only one key figure is selected for the function, then the system enters it by default as the field value in the second step, which makes the process easy for the user.
If there is more than one key figure in the source table, the user must set the field value data manually. To do so, use the dropdown list to select the value field. The system updates all rules automatically to include the value field selected by the user.
On the Rules road map step, choose Add to add rules.
If the rules are to be imported from other systems, there is also the possibility to import the rules from Microsoft Excel.
For guidance about how to maintain the derivation rules, see the documentation about Derivation Rules.
Save your data.
Choose Generate.
To preview the results, choose Test.
Scenario: Transfer Structure
Data to be enriched.
Product |
Cost Center |
Amount |
Premium |
---|---|---|---|
P1 |
CC01 |
100 |
200 |
P2 |
CC02 |
150 |
400 |
P3 |
CC03 |
200 |
550 |
P4 |
CC04 |
250 |
700 |
P1 |
CC05 |
300 |
850 |
P2 |
CC06 |
350 |
1000 |
P3 |
CC07 |
400 |
1150 |
P4 |
CC08 |
450 |
1300 |
P3 |
CC09 |
500 |
1450 |
P4 |
CC10 |
550 |
1600 |
P1 |
CC01 |
600 |
1750 |
P3 |
CC05 |
800 |
2350 |
P4 |
CC06 |
850 |
2500 |
P1 |
CC07 |
900 |
2650 |
P1 |
CC08 |
950 |
2800 |
P2 |
CC09 |
950 |
2950 |
Rules contain the conditions and action fields. For example, in the rule below, Cost Center is the condition field and Premium is the action field. If the cost center is CC01, the value of the “Amount” is moved to the Premium field.
Cost Center |
Field Name |
Field Value |
---|---|---|
CC01 |
Premium |
"Amount" |
Product |
Premium |
---|---|
P1 |
700 |
P2 |
4350 |
P3 |
5500 |
P4 |
6100 |
Operators |
Example |
Description |
Comments |
---|---|---|---|
!= |
!= ABC |
Not Equal To |
Single quotes required to consider value as a value and not as operator, value specified without single quotes considers IN as operator |
In |
In (’BD’, ’BC’, ’BE’, ’BF’) |
In |
Single quotes required to consider value as a value and not as operator, value specified without single quotes considers IN as operator |
Not In |
Not In A;B;C |
Not In |
|
Like |
Like Abc* |
Like (regex/wildcard) |
|
Not Like |
Not Like Abc* |
Not Like (regex/wildcard) |
Operators |
Example |
Description |
---|---|---|
!= |
!=10 |
Not Equal To |
In |
In 1;2 |
In |
Not In |
Not In 1;2 |
Not In |
> |
> 20 |
Greater Than |
>= |
>= 20 |
Greater Than or Equal |
< |
< 10 |
Description: Less Than |
<= |
<= 10 |
Less Than or Equal |
Between |
Between 20 and 30 |
Between |