SCV application defaults

New SCV configuration screen is available to specify default values for SCP application. SCV application defaults are used to replace hardcoded default values in SCV database views and SCP interface service queries. This makes application variables and the default values are accessible and allows overriding default values without customizing views or interface services.

Default values can be specified for these application variable types:

  • SCO class properties
  • Planning Engine variables
  • SCV table columns

It is also possible to specify a new default for other custom application variable.

Application defaults are referred from SCV database views or SCP interface services by linking to the underlying SCV configuration table (SZ_APPLICATION_DEFAULT). Currently the following have been updated to use the standard delivered application defaults:

  • SP_* views in the base template to retrieve default values for SCO class properties (application defaults are in apsco template)
  • Interface services in spls template to retrieve default values for Planning Engine variables
  • Interface services in spls template to retrieve default values for SCO class properties.

Additional application defaults can be used in these views and interface services, or existing application defaults can be used in additional views and interface services by altering the view or interface service query definition to join to the SZ_APPLICATION_DEFAULT table. A separate join is needed for each application default to use.

Application default values can be specified for a specific profile or globally for all profiles. The following utility view is delivered to simplify the adjustments to the query using the application default:

  • SC_V_CLASS_PROPERTY_PROFILE

Similarly, for class properties, application default values can be specified for a specific class or globally for all classes. One join is required in the query for each variable. When both levels are defined, one separate join is required to use the global default value for all classes and one other join is required to use the default value for the specific class.

See course SCP v21.3 RT Extensibility: SCV Application Defaults - Product Use for further details.

Note: This feature is available on upgrade. Access to the Application Default function requires one of the following new permissions:
  • SCV Application Defaults - View (Configuration)
  • SCV Application Defaults - Add (Configuration)
  • SCV Application Defaults - Edit (Configuration)
  • SCV Application Defaults - Delete (Configuration)

These permissions are included for default system administration roles upon loading the base template (base.zip) for this version.

Standard application default values are delivered for these types and profiles:

  • SCO class properties for profile APSCO_BASE
  • SCO class properties for profile SPLS_BASE
  • Planning Engine variables for profile SPLS_BASE

Standard delivered application defaults and the altered view and interface service definitions using these are available after appending the base template (base.zip), supply template (spls.zip) and Planning Engine SP SCO template (apsco.zip) for this release.