Validation of input parameters

The values specified for the input parameters are validated. These are the validation rules for each parameter in the EXECUTE_TRANSFER program:

  • REFRESH_MODE: The specified value must be Full, Partial, or Incremental. Else, an error message is logged, and the execution is stopped.
  • TARGET_DELETE_MODE: The specified value must be Physical, Logical, or None. Else, an error message is logged, and the execution is stopped.
  • TARGET_UPDATE_MODE: The specified value must be Insert or Merge when the value in the TARGET_DELETE_MODE parameter is set to None. Else, an error message is logged, and the execution is stopped.
  • MAPPING_ID:
    • The specified value must exist with the Active status in the SZ_MAPPING table. If there are no active entries in the SZ_MAPPING table with the provided mapping_id value, an error message is logged, and the execution is stopped.
    • The specified mapping must be active.
  • MAPPING_NAME:
    • The specified value must exist with the Active status in the SZ_MAPPING table. If there are no active entries in the SZ_MAPPING table with the provided mapping_name value, an error message is logged, and the execution is stopped.
    • The specified mapping name must be active.
    Note: The program continues with execution only if all mappings in scope of the current execution are valid. Else, an error message is logged, and the execution is stopped.
  • TARGET_TABLE_NAME: The specified value must exist in the SZ_REG_TABLE table. If there are no active entries in the SZ_REG_TABLE table with the provided table_name value, an error message is logged, and the execution is stopped.
  • TARGET_TABLE_GROUP_ID: The specified value must exist with the Active status in the SZ_REG_TABLE_GROUP table. If there are no active entries in the SZ_REG_TABLE_GROUP table with the provided table_group_id value, an error message is logged, and the execution is stopped.
  • TARGET_TABLE_GROUP_NAME: The specified value must exist with the Active status in the SZ_REG_TABLE_GROUP table. If there are no active entries in the SZ_REG_TABLE_GROUP table with the provided table_group_name value, an error message is logged, and the execution is stopped.
  • TARGET_TABLE_AREA: The specified value must exist as a valid table area value in the SZ_REG_TABLE table. If there are no active entries in the SZ_REG_TABLE table with the provided table_area value, an error message is logged, and the execution is stopped.
    Note: 
    • You can only specify one of these parameters at a time. Else, an error message is logged, and the execution is stopped:
      MAPPING_ID, MAPPING_NAME, TARGET_TABLE_NAME, TARGET_TABLE_GROUP_ID, TARGET_TABLE_GROUP_NAME and TARGET_TABLE_AREA.
    • If TARGET_TABLE_NAME, TARGET_TABLE_GROUP_ID, TARGET_TABLE_GROUP_NAME, or TARGET_TABLE_AREA is specified:
      • All target tables in the scope of the current execution must contain at least one active mapping.
      • Only one mapping for the same target table is set as default (Default Flag=On) when a target table has multiple active mappings.
  • SNAPSHOT_COLUMN:
    • If the REFRESH_MODE parameter is set to Incremental and the value in the SNAPSHOT_COLUMN parameter is specified, the current mapping is executed in incremental mode using snapshots for the specified column.
    • If the REFRESH_MODE parameter is set to Incremental and the value in the SNAPSHOT_COLUMN parameter is not specified, the current mapping is executed in incremental mode. However, all records are processed from the source without snapshot filtering.
  • INCLUDE_USER_DATA:
    • If this parameter is set to Y and the table area of the target table is Core, user-created records from the corresponding Planning Configuration table are included in the transfer. The records are added to the source data set generated based on the specified mapping definition.
    • If this parameter is set to N, only the source data set defined by the mapping definition is used for the transfer.
    • If this parameter is set to Y, the table area of the target table is Core, and the corresponding Planning Configuration table does not exist, a warning message is logged, and execution continues using only the source data set defined by the mapping definition.
    • If this parameter is set to Y and the table area of the target table is not Core, an error message is logged, and the execution is stopped.