Report Versioning (SAP Library - EH&S Product Safety)

Report Versioning

Use

This function supports the assignment of version numbers to a number of reports that are generated for the same specification, generation variant, and language.

As long as a report is not yet released and not assigned a version, the new report replaces the old report. Once, however, a report has been released and therefore every version must be preserved, a new version of the report is created for the newly generated report, which does not replace the old one.

Prerequisites

To enable versioning, you must have set the Version requirement indicator in the generation variant header.

If the relevancy indicator was set, new main or sub-versions of reports are created. You can set the relevancy indicator:

In the value assignment usage

The corresponding value assignments are marked in the manually or automatically generated ready-to-ship report if you have set the Generate change marks indicator in the generation variant header, and a released and versioned report exists as a previous version. The SAP System determines the relevant changes made since the previous report was generated.

Reports that contain relevant changes to specifications are included automatically when the worklist is generated.

In the report header

The report may not have status RR (Report request), RE (Released), or HI (Historical).

Features

Start Version

If you generate a report for a specification, generation variant, and language for the first time and choose Accept when the report has the status CO (Completed), a dialog box appears in which you specify the start number for the main version regardless of whether you have set the Version requirement indicator or not. This start version can be used, for example, as the initial report version following the replacement of legacy systems. In this case, the sub-version is always zero.

Numbering

If you choose Accept again for a report with status CO (Completed), the following system reactions occur:

Version requirement indicator
Result

The indicator is not set.

The report is always assigned the version number V1.0, regardless of whether the relevancy indicator has been set.

The indicator has been set and the report is relevant.

The SAP System assigns the next highest number to the main version and sets the sub-version to zero (V2.6 ® V3.0, for example).

The system does not permit gaps in the main version.

The indicator has been set and the report is not relevant.

The SAP System assigns the next highest number to the sub-version and leaves the main version unchanged (V2.6 ® V2.7, for example).

When main versions are assigned, no gaps in the numbering are permitted.

A version number assigned to a report cannot be changed.

Taking the Key Date into Account

Report shipping always selects the most current released version of a report. The most up-to-date version is always assigned to the last report generated, independent of its key date:

For reports with key date in the future that must be versioned and released before the key date is reached, you must therefore check

Whether a report with a higher version number was generated subsequently and released because of a change
Whether the subsequently generated report has the same future key date

If the key date is not in the future, you must create a report request manually for the key date in the future so that this report has the highest version number and no data is lost during shipping.

Example

Version 3.2 contains specification data valid for August 1^st.

Version 4.0 contains specification data valid for May 1^st and relevant changes were made to it.

Version	Generated on	Released on	Key date
3.2	April 1^st	April 1^st	August 1^st
Relevant change => 4.0	May 1^st	May 1^st	May 1^st

If a report shipping order is created on August 1^st, the system selects the reports with the highest version numbers (version 4.0). However, the data valid for August 1^st is not contained in this version.

To create a version that contains the relevant changes as well as the data valid for August 1^st, you must create a report request manually with key date August 1^st. =>

	Version	Generated on	Released on	Key date
	4.1	May 1^st	May 1^st	August 1^st

This scenario remains the same for relevant and non-relevant changes.

Bypassing Versioning

You can bypass the status CO (Completed) by defining RE (Released) as the initial status in the generation variant. How the system continues depends on whether the Version requirement indicator is set in the generation variant header.

Version requirement indicator

Result

The indicator is not set.

The acceptance of the report in the last release status leads automatically to the final release of the report. The report is always assigned version V1.0.

During this process, the currently released report is replaced.

The indicator is set.

The SAP System automatically specifies V1.0 as the start version for the first generated report. The subsequent versions depend on whether the relevancy indicator has been set or not.

Activities

Editing Worklists for Reports

See also:

Generation Variant Indicators

Report Editing

Relevancy Indicator

Version requirement indicator	Result
The indicator is not set.	The report is always assigned the version number V1.0, regardless of whether the relevancy indicator has been set.
The indicator has been set and the report is relevant.	The SAP System assigns the next highest number to the main version and sets the sub-version to zero (V2.6 ® V3.0, for example). The system does not permit gaps in the main version.
The indicator has been set and the report is not relevant.	The SAP System assigns the next highest number to the sub-version and leaves the main version unchanged (V2.6 ® V2.7, for example).