Changes to SAP EH&S Release 2.2B, Patch Level 1 and 3

Scope of Functions

This release note describes the changes for SAP EH&S Release 2.2B that have been made up to and including Patch Level 3.

See also: Note

Change to SAP EH&S Release 2.2B

You should create a variant for SAP EH&S Release 2.2B for report

program RC14KCMP for the master data matchup. This variant executes the functions Set deletion indicator and Delete physically. Schedule the variant at night as these functions could require a long time. You will find more information in the IMG activity Set Up Job for Deleting Data.

Changes in Patch Level 1

Note:

Changes have been made available for SAP EH&S Release 2.2B using Patch Levels. For more information, see the following and the OSS note 122878.

Changes have been made to Dok-X report export in Patch Level 1 for EH&S Release 2.2B:

1. Manual export from the report information system

When you create a Dok-X report export order from the report information system, as of Patch Level 1, the R/3 System checks whether the report has already been exported. For more information, see the application help under Product Safety -> Interfaces -> Import and Export: Process -> Report Export: Process

2. Physical Export Path Customizing

The physical export path must be set up in Customizing for Product Safety . For more information, see the IMG activity Specify file paths and names.

3. File Name for the Dok-X Report Export Files

To determine the file names for the export files, the system generates a sequential number from a number range interval. Before Patch Level 1 the version was determined via the environment parameter RE_LAST_DOC_NUMBER.

For more information, see the IMG activity Specify file paths and names.

4. For more information about the following further changes, in the application help based on a standard release 4.5B or higher, choose Product Safety -> Interfaces -> Import and Export: Process -> Report Export: Process:

a) The structure of the key file has changed.

b) When saving the export orders, the most up-to-date Dok-X report export order for a report is retained in the system. Older Dok-X report export orders for the same report are deleted providing they have status 'historical'.

c) During automatic re-export, the system checks for every report that is newly generated whether there is a Dok-X report export order with the previous version of this report. As of Patch Level 1, the system also checks whether the new report generated has already been exported manually from the report information system.

Automatic re-export is performed depending on the initiator. The material name is also taken into account.

Changes in Patch Level 3

The following functional changes were made to EH&S Release 2.2B in Patch Level 3:

1. Extended Searches for Report Shipping Orders

The new parameter FLG_SEARCH_WITH_HEADER_DATA (search only via header data) for the user exit type SRS_QUERY has been created for the extended search for report shipping orders. This parameter can be set for searches in which you only have to search using the header data, thus increasing the speed of the search.

For more information, see the IMG activity

Manage User Exits.

2. Customer Exits for Report Shipping

The following changes were made in Customizing for Product Safety:

• The customer exit CVEA0001 for checking the material name has been enhanced to include the parameter I_REPORT

• The customer exit CVFE0001 for selecting the default output device has been newly set up

1. Enhancing the Definition of the WWI Destination

As of Patch Level 3 you can set up the WWI destination for different categories of report generation orders. The orders are distinguished using the application component and the processing type. For more information, see the IMG activity Check WWI destinations and assign generation server.

2. Automatic Generation of Worklists

For performance reasons, the report for automatic worklist generation (RC1AVGEN) has so far been divided up into report program RC1AVGE1 and report program RC1AVGE2. Report program RC1AVGE1 determines the reports with potential changes and stores them in a database table.

Report program RC1AVGE2 processes the selected reports in packages. You specify the size of the packet with the new environment parameter AVGEN_SPLIT. For more information, see the IMG activity Specify environment parameters.

Report program RC1AVGE1 should run in the same cycle that report report program RC1AVGEN ran in before. Report program RC1AVGE2 can be scheduled so that it runs either periodically, or started manually, for example, when the reworking of a particular substance has been completed. If the report program RC1AVGE2 is scheduled with certain selection criteria, these should be selected so that all reports with potential changes are checked.

Installation Information

Report Program for Deleting Old Value Files

Value files that were stored in report generation as long texts up to Patch Level 3 cannot be used for future enhancements. You must therefore delete these long texts using report program RC1XVALF that you access via transaction SE38. Before you start the report program, you must ensure that neither the report generation and the report shipping processes nor the processes of automatic work list generation are running.

Effects on Customizing

Make the necessary settings in the following IMG activities:

• Set up job to delete data

Patch Level 1

• Points 2 and 3: Specify File Paths and Names

Patch Level 3

• For point 1: Manage User Exits

• For point 2:

• Develop enhancement to check material name

• Develop enhancement to select output device

• For point 3:

• Check WWI destinations and assign generation server.

• For point 4: Specify environment parameters

Note

The following IMG activities have been newly created for Patch Level 3:

• Set up job to delete data

• Develop enhancement to select output device

Changes in Procedure

The Check WL creation function under Environment in the report tree has been withdrawn as of Patch Level 3. You both start report programs RC1AVGE1 and RC1AVGE2 and check the log using the standard report functions.