Show TOC

Versioning DataLocate this document in the navigation structure

Use

The versioning data are located on the following tabs:

"Software Components" Tab

  • Software Components: For example, SAP_BASIS. You can list several software components. If you use the F4 help, you can select the actual software components from the local system or the maintenance ( Target) system.

  • Releases: You can specify the Releases (for example, 620) and patch levels for which the test script is valid. If you use the F4 help, you can select the actual values from the target system.

    • You need not specify the patch level.

    • If you specify a particular combination of software component, Release, and patch in one version, that combination cannot be specified in another version. Backup versions are the exception to this rule.

    • In one version only, you can enter an asterisk (*) in the Release field. This version will be used if no other version has Release data that matches that of the target system.

    • If you enter R (for required) in the Relevance field of a row, then the validity of the version is always determined by the entries in the row. Alternatively, you can enter O (for optional). This is useful for specifying several combinations, only one of which need exist in the target system for the version to be valid.

  • Backup: To exclude a version from the version search, select Backup. This prevents the version from being executed by a test configuration or REF command. It can only be executed from the test script editor.

"Business Functions" Tab

Today, software tests no longer depend only on software components, Releases and patch levels, but also on business functions activated in the switch framework.

You can declare that a version of a test script or a version of a test data container should be valid for a client of a System Under Test only if one or more business sets are active.

  • Business Functions Pool: You can list several business functions. If you use the F4 help, you can select business functions from the target system.

    If some versions already exist, and you create a new version, all business functions that are used in the existing versions are displayed by default.

    You can use the following functions to populate the Business Functions Pool:

    • Yellow light bulb: Populate the pool with all business functions that are active in the current target system.

    • Grey light bulb: Populate the pool with all business functions that are available in the current target system.

  • Business Functions: Specify one or more business functions. If you use the F4 help, you can select business functions from the Target system.

    Business Function Active:

    • If this checkbox is marked, the version will be valid only if the business function is available and active in the system under test.

      If this checkbox is unmarked, the version will be valid only if the business function is available and inactive in the system under test.

    • If you enter R (for required) in the Relevance field of a row, then the validity of the version is always determined by the entries in the row. Alternatively, you can enter O (for optional). This is useful for specifying several combinations, only one of which need exist in the target system for the version to be valid.

  • Backup: To exclude a version from the version search, select Backup. This prevents the version from being executed by a test configuration or REF command. It can only be executed from the test script editor.

Version Finding

During test execution, when the system determines which version to use, the system takes into account software component / Release / patch as well as business functions.

The system processes these data in the following order:

  1. Version finding by software component / Release / patch

  2. Version finding by business function

This means:

  • If no version is found to fit by software component / Release / patch, the search processing is ended.

  • If the system finds exactly one version by software component / Release / patch, it is only checked for "Required" business functions in place.

  • If the system finds multiple versions by software component / Release / patch, the "Required" business functions are checked for existence, and the "Optional" business functions are taken into account if a matching version is still not found.