This template defines the relationship between a step and its input source.
This relationship is required for steps of type ISV_StepType_Editioned_Append, ISV_StepType_Full_Replace, and ISV_StepType_Uneditioned_Append.
This relationship is optional for steps of type ISV_StepType_VWP_Population.
The ISV can relate multiple input sources to the step by reusing the template for each unique instance of an input source.
Table 30 provides information about each token in the
template.
Table 30. StepInputTable.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 process that is being 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 31 provides example values for each token to illustrate the
kind of metadata that you might provide for each token.
Table 31. Example values for StepInputTable.tag tokens
| Token | Example value |
|---|---|
| *StepName | Revenue by product |
| *DatabaseName | Finance Warehouse |
| *TableOwner | FINADMIN |
| *TablePhysicalName | INVENTORY |
| *ProcessName | Inventory process |
| *CurrentCheckPointID++ | 6 |