Standard XSteps: Versioning 
Use
You can create several versions with different validity periods for a standard XStep. If you explode an SXS reference either from within an application or in the SXS repository itself, the system searches for the SXS version that is valid and released as at the key date (i.e. with the status Released or Released for Test ). You can choose any name for the version. The version names are only unique within the standard XStep.
Features
Automatic Number Assignment
In Customizing for Production Planning – Process Industries, you can specify under Process Coordination→Execution Steps→ Standard XStep Repository→Settings for Standard XStep Repositorythat numbers are to be assigned automatically for the versions of a standard XStep.
The first new version of a standard XStep is assigned the number 0001. If several versions already exist for a standard XStep, the system chooses the newest version. If the key of the newest version consists of numbers, the system increases the number by one. If the system does not find a valid predecessor number, the number 0001 is assigned.
if you have activated automatic number assignment, you cannot then change the version number manually. If you wish to change the version number manually, you must first reverse your Customizing setting.
Automatic Calculation of the Validity Period
In Customizing for Production Planning – Process Industries, you can specify under Process Coordination → Execution Steps→ Standard XStep Repository→Settings for Standard XStep Repositorythat the valid-to date of a version is to be determined by the system. Manual entries for the valid-to date are then not possible.
At any one point in time, there can only be one valid version of a standard XStep. If you change the status of a version to Released or Released for Test , the system checks the validity of the versions. If a valid version previously existed, the time period of this version is limited to the valid-from date of the new version.
For a standard XStep, version 1 with the validity period 03.31.06 until infinite (12.31.9999) was hitherto released. If you release version 2 as at 09.30.07, the validity period of version 1 is limited to 09.29.07.
There are a number of special aspects:
If the valid-to date of the new version lies before the valid-from date of the old version, the valid-to date of the new version ends one day before the valid-from date of the new version.
If a new version whose period lies between two released versions is released, the same rule as above applies:
The valid-to date of the earlier version ends one day before the valid-from date of the new version.
The valid-to date of the new version ends one day before the valid-from date of the later version.
The date of the new version may not lie before the current day’s date.
The new and the old version may not have the same valid-from date.
