Introduction
...
- Direct assignment – just copies one to one data from a source field to a target field
- Routine – a custom implementation which changes the value in the selected field
- Currency – transformation of currency values according to a currency key
- Meaningful field values – translation of values according to a domain, mapping table, SID or a custom conversion routine
Business function – adjust values with business functions
- Trigger operation type - in trigger delta extractor, fill operation type (INSERT, UPDATE, DELETE)
- Trigger operation timestamp - in trigger delta extractor, fill timestamp of the operation
- Routine: Unique recordmode - similarly to the standard routine, this transfer rule generates include for custom adjustment of data. However, this routine contains a predefined implementation for suppressing duplicate rows with the same semantic key but a different recordmode field. Moreover, because this routine is specific for recordmode field present in the Change log table, you can use it only for Change log delta type. This routine is described in more details in the chapter (Glue-2011) BW Transfer Rules.
...
This is the default type when an extractor is created. The extractor takes a source value and copies it in an unchanged form to a target. In the this case, the system sets a different rule and you change it to the direct assignment rule, the old rule (include form) with the existing code is deleted.
...
In the case that value in a particular field needs to be changed, deleted, or adjusted, you can create your custom ABAP code that will be then processed for the selected field during the load. To perform these changes:
Select Routine as a transfer rule and click 
in the column Edit Rule to access the generated form. The form can be edited in the same way as any Z*/Y* ABAP report. Importing parameter is_record contains the whole record which is processed. This parameter should not be modified. You can change the value of the selected field through the parameter cv_field which modifies the value according to your requirements.
...
Skip the records during the extraction process
You have an option to set up a condition to skip records during the extraction process. To perform this, you should set the flag 'gv_skip_line' under your condition.
...
SAP applications displaying these values, perform a conversion according to a currency key during the extraction. It is necessary to convert the value of the currency field to a correct form before it is stored in an external database. Our functionality enables this conversion automatically, as it finds the currency key during the data load and changes the particular amount into a proper value, and stores it in target storage.
...
This option allows you to use certain Business functions to adjust values during extraction.
Meaningful field values
...
On the contrary with the above-listed transformation types, this type must be already specified while creating a Glue table by selecting the checkbox Use meaningful values. This option automatically adjusts the table structure on in the background, so that the fields can store longer texts.
For every data element (e.g. 'AA') there are different ways on how to transform values. This information is stored in a database table and can be a part of customizing settings. You can adjust the settings in the GLUE Cockpit.
When you create an extractor for a target table with checked Meaningful Field Values, the Apply rules function automatically creates all meaningful field rules.
| Note |
|---|
When you create an extractor for a target table without checked Meaningful field values, you can still add this transformation rule to specific fields using the pop-up menu in the Fieldname Mapping section. This step generates a transformation of the selected table column. However, it is important to note that since the target table is already active, its field size isn't adjusted and that may lead to string leaks. |
...
You can specify which field should be used as a source for a meaningful value in the 'Reference table'. This is part of the customization option that was mentioned above.
Mapping of the third way (SID) can be adjusted in Glue Cockpit.
| Note |
|---|
Please note: If meaningful values are missing some content, run the program '/DVD/GL_BPL_SPKFL_CONTENT_GEN'. |
...
Example without using of meaningful values:
Example with using of meaningful values:
If a meaningful value is not found for value, the system stores the original value and puts it into brackets – please see the column TYPE in the picture below.
In the case values of data, element RSSID are included in the Master data table, then by a SID conversion, they are converted into a value from this table. However, this conversion makes sense for HANA optimized cubes without dimension tables and the F table already contains SID values (this points directly to the values in the Master data table). Every part of the process (adjusting fields during table creation and making rules in extractor) is performed automatically. For example, the source table can look like this:
And an example of converted values in the target table:
