Use this template to optionally define the relationship between a step of type ISV_StepType_VWP_Population and its output targets.
Table 34 provides information about each token in the
template.
Table 34. StepVWPOutputTable.tag tokens
| Token | Description | Allowed values |
|---|---|---|
| Entity parameters | ||
| *StepName | The name of the step that is being related. | A text string. |
| Relationship parameters | ||
| *DatabaseName | The business name of the database that is being created. | A text string. |
| *TableOwner | The owner, high-level qualifier, collection, or schema of the table that
is being described.
This value must be a valid qualifier as defined by the rules of ODBC. | A text string. |
| *TablePhysicalName | The physical table name as it is known to ODBC (the system DSN name). | A text string. |
| *ProcessName | The name of the processthat is being created or related | A text string. |
| *CurrentCheckPointID++ | An index, starting with 0, that increases each time that it is
substituted in a token.
This token is required. | A numeric value. |
Table 35 provides example values for each token to illustrate the
kind of metadata that you might provide for each token.
Table 35. Example values for StepVWPOutputTable.tag tokens
| Token | Example value |
|---|---|
| *StepName | Revenue by product |
| *DatabaseName | Finance Warehouse |
| *TableOwner | FINADMIN |
| *TablePhysicalName | INVENTORY |
| *ProcessName | Marketing process |
| *CurrentCheckPointID++ | 1 |