Parameters
Xtract Universal supports multiple options to dynamize extractions:
While script expressions compute values, extraction parameters and by extension SQL parameters require users to pass actual values when running an extraction. Extraction parameters affect the extraction settings, destination settings, the SAP connection settings, and the user-defined (custom) runtime parameters of an extraction. This includes the runtime parameters that are used in SQl commands (SQL parameters).
About Custom Runtime Parameters
User-defined runtime parameters can be used to filter SAP data before writing the data to the destination. They are part of the extraction parameters and can be used in SQL statements, see SQL parameters. There are two types of custom runtime parameters:
- scalar parameters that represent a single value.
- list parameters that represent multiple values separated by a comma, e.g., 1,10 or “1”, “10”.
Most extraction types offer an Edit runtime parameters menu that allows users to create custom runtime parameters.
Once runtime parameters are available, a switch is added to all input fields that support runtime parameters. The switch allows users to switch between a static input value ( ) and an existing runtime parameter ( ), e.g., Parameter0.
The following table shows what extraction types and settings support custom runtime parameters:
| Extraction Type | Settings that Support Custom Runtime Parameters |
|---|---|
| BAPI | Import parameters, Table parameters |
| BWCube | BEx variables, dimension filters |
| DeltaQ | Selections |
| ODP | Selections |
| Query | Selections |
| Report | Selections |
| Table | WHERE clause, HAVING clause |
| Table CDC | WHERE clause |