Filter Data

You can filter or restrict your data using the Filter tab.

To filter your data, perform these steps:

In the Edit Data Flow wizard, select the transform in which you want to add a filter.
Select the Filter tab.
(Optional) If you want to ignore identical duplicate rows so that your results contain only distinct rows, select Select Distinct Rows.
This is similar to specifying a SELECT DISTINCT SQL statement.
From the Input pane, drag the column containing the data you want you filter and drop it in the Filter field.

As needed, type filter conditions or use the built-in functions.

Examples of filter conditions are shown in the following table:

Type	Filter	Description
Constant	`VBAK.SPART = '07'`	In a sales order header table, filters for rows containing Division 7.
Complex	`VBAP.NETWR < ( VBAP.WAVWR * VBAP.ZMENG )`	Filters for rows where the net value of the sales order is less than the product of the cost of the item multiplied by the quantity ordered.
Global variable	`(CSKB.ERSDA >= $G_SDATE)`	In a cost elements table, filters for rows with a date equal to or more recent than the value of the global variable $G_SDATE.
Function	`BKPF.CPUDT >= sysdate() -1`	Filters for Financial Documents Header rows created yesterday or more recently.

If your source is an adapter datastore, you can also filter the rows retrieved from the datastore in the Adapter Source tab.
The columns that you can use for adapter-based filtering depend on the type of adapter.

Restriction

When you filter in an XML Map transform, source columns must come from the source schemas in the current iteration rule or those that appear in the iteration rules associated with the parents of the selected target schema. Additionally, the path from the column being used to the source schema must contain no repeatable schemas.

Target columns must come from the selected target schema or parents of the selected target schema. Additionally, the path from the column being used to the target schema must contain no repeatable schemas.

Note

If your expression contains varchar comparisons, SAP Cloud Integration for data services ignores trailing blanks in the data. For Oracle data, use the rtrim or rpad functions if the number of trailing blanks might differ on either side of the comparison.