SCV application defaults for Planning Engine variables
The Planning Engine SP SCO variables have been populated using the interface service "SP
- SCV - SCO - Import Variables", which assigned static values to the Planning Engine variables
created from SP_SCO, as defined in the interface service query. These values have been
hardcoded, making it difficult to adjust or extend the default values. It is now possible to
use the values defined in the Planning Engine Definition, or to load the values from SCV
Application Defaults.
The new scv_apsco_use_internal_variables application variable controls which values are assigned to the Planning Engine variables, SP SCO, as part of the standard master data import:
- When scv_apsco_use_internal_variables = 0 (default), variable values are imported from SCV Application Defaults using the interface service "SP - SCV - SCO - Import Variables - App Defaults".
- When scv_apsco_use_internal_variables = 1, internal default values are used for the variables as defined in the PE model.
- When scv_apsco_use_internal_variables = 2, variable values are imported from static values
using the interface service "SP - SCV - SCO - Import Variables".Note: This option is deprecated and only included for backward compatibility.
This new application variable is added:
- scv_apsco_use_internal_variables, default = 0. Use an internal Model Variables (1), Import from SCV Application Defaults (0) or deprecated static definition (2) for backward compatibility
This new interface service is added:
- SP - SCV - SCO - Import Variables - App Defaults
This macro is updated, to conditionally execute related interfaces based on the application variable value:
- SP - SCV - SCO - Import Master Data
Note: This feature is enabled after loading the Planning Engine SP SCO template (apsco.zip) for
this release. The option to load the values from SCV Application Defaults will be enabled by
default (scv_apsco_use_internal_variables = 0).
You are not required a new role or privilege access to use this feature.