Validation and execution

The specified SCV job or program is executed using optional passed parameters in the context of the cycle period, on successful validation and execution of the macro.

These are the execution rules:

  • The parameter list is defined in the "-name=value" format. For example:
    • RunSCV("EXECUTE_VALIDATION","-TABLE_NAME=","-TABLE_GROUP_NAME=","-SOURCE=")
      Note: The order in which the SCV parameters are defined can vary.
  • The warnings and errors generated by SCV are logged to the SCV audit log.
  • The job status is set to error when the SCV job fails to complete.

This table lists the examples of the RunSCV macro:

Example Syntax

Run the SCV job "EXECUTE VALIDATION" (which executes several validations on the SCV Inbox tables) to validate and transfer data to Core with applicable transformations. For example, execute SCV program EXECUTE_VALIDATION with these parameter values:

  • TABLE_NAME = "" (All tables)
  • TABLE_GROUP_NAME = "" (All table groups)
  • SOURCE = "" (All sources)
 RunSCV("EXECUTE_VALIDATION","-TABLE_NAME=","-TABLE_GROUP_NAME=","-SOURCE=")

Run the SCV job "EXECUTE_TRANSFER" to transfer from SCV Inbox to Core tables using an incremental refresh. The latest values from a configured date are only transferred. For example, execute SCV program EXECUTE_TRANSFER with these parameter values:

  • REFRESH_MODE = Incremental
  • TARGET_DELETE_MODE = Physical
  • TARGET_UPDATE_MODE = Merge
  • MAPPING_NAME = BASE_SI_SALES_HIST_AGGR-SC_SALES_HIST_AGGR_INCREMENTAL
 RunSCV("EXECUTE_TRANSFER","-REFRESH_MODE=Incremental","-TARGET_DELETE_MODE=Physical","-TARGET_UPDATE_MODE=Merge","-MAPPING_NAME=BASE_SI_SALES_HIST_AGGR-SC_SALES_HIST_AGGR_INCREMENTAL")

This table lists the status of the supported cycle period and scenarios for which the macro can be executed:

Cycle Period Status Scenario Status Can Execute?
Any Any Yes