Validation and execution
These are the execution rules:
- The parameter list is defined in the "-name=value" format. For example:
RunSCV("Initialize discrete scenario", "-profile=Base", "-mode=Full", "-boi=", "boi_group=Master Data")
Note: The order in which the SCV parameters are defined can vary.
- The current scenario can be translated to a specific planner instance for SCV to interact with the RunSCV command when run.
- Future horizon can be passed as a parameter to SCV for enabling the transfer process by setting the future horizon profile parameter.
- The warnings and errors generated by SCV are logged to the SCV audit log. A log is created for each BOI task.
- 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 "Initialize discrete scenario" (which executes various commands) to transfer data from SCV to a planner, passing three named parameters (profile, Mode, and boi_group) with the corresponding values "Base", "Full", and "Master Data". For example, execute SCV program Initialize discrete scenario with these parameter values:
|
RunSCV("Initialize discrete scenario","-profile=Base","-Mode=Full","-boi_group=Master Data") |
Run the SCV job "Publish discrete scenario" (which executes various commands) to import purchase orders from planner to SCV, passing three parameters ("Base," "Incremental," and "Purchase Orders"). For example, execute SCV program Publish discrete scenario with these parameter values:
|
RunSCV("Publish discrete scenario","-profile=Base","-Mode=Incremental","-boi_gourp=Purchase Orders") |
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? |
---|---|---|
Pending | N/A | No |
Archived | Any | No |
Running, Completed, Paused, Aborted | Any | Yes |