SAP ABAP IMG Activity EHS_SR_250_21 (Set Up Jobs for Generating Worklists)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBUI (Package) Company Environment Information System
IMG Activity
ID EHS_SR_250_21 Set Up Jobs for Generating Worklists  
Transaction Code S_SH8_72000998   IMG Activity: EHS_SR_250_21 
Created on 20001013    
Customizing Attributes EHS_SR_250_21   Set Up Jobs for Generating Worklists 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_SR_250_21    

Use

In Report management, you can generate and schedule a worklist of all changed reports automatically. These worklists are generated automatically using the programs RC1AVGE1 and RC1AVGE2.

  • The program RC1AVGE1 determines the reports that could be affected by a change to a specification or a phrase, known as reports with potential changes.
  • The program RC1AVGE2 then determines whether the reports with potential changes that you selected have actually been affected by a change to a specification or a phrase.

The generation of the worklist takes into account:

  • Time-dependent changes, or in other words, changes in the future are only taken into account when they become valid
  • Document status and phrase status
    • The system only takes into account released report templates.
    • If no phrase status is specified, the phrase is taken into account.
      • If a phrase status is specified, the system checks whether the PhSymExpan indicator (expansion of phrase symbols in the report) is set for the status in the IMG activity Specify Phrase Status. If so, the phrase is taken into account. If not, it is not taken into account.
  • Changes that occur due to changes in other specifications that are used in the specification to be checked in the following ways:
    • In a referencing relationship
    • In an inheritance relationship
    • In a composition
    • In a transport classification

For more information, see the documentation for the programs RC1AVGE1 and RC1AVGE2.

Requirements

  • Manually or automatically generated report requests exist.

    Note:

    • The SAP system puts manually generated report requests straight into the worklist. For automatically generated report requests, you can have the SAP system create it for you in cycles.
  • You have set up the environment parameters AVGEN_SPLIT and AVGEN_SHOW_MSG in the IMG activity Specify Environment Parameters. For more information, see the IMG activity.

Activities

  1. Schedule the program RC1AVGE1 to run periodically, for example, on a daily basis.
    1. On the SAP Easy Access screen, choose System -> Services -> Jobs -> Define Job.
    2. Enter a job name, WORKLIST_GEN for example, and choose a suitable job class.
    3. Choose Edit -> Start Time and choose Date/Time in the dialog box that appears.
    4. Enter the required data and select Periodic job.
    5. Choose the function Period values and specify the periods.
    6. Choose Check and save your entries.
    7. Choose Edit -> Steps and in the following Create step 1 dialog box, choose ABAP program.
    8. In the Name field, enter RC1AVGE1.
    9. Choose Check and save your entries.
      10. The step list appears.
    10. Go back and save your entries.

      The SAP system creates the worklist periodically for the defined start date.

  2. Schedule a job for the program RC1AVGE2 using one of the following options:
    • You can schedule the program RC1AVGE2 together with the program RC1AVGE1. To do this, schedule a job that has program RC1AVGE1 assigned as step 1, and program RC1AVGE2 assigned as step 2.
      • Note:
      Make sure that no variants with selection criteria are scheduled for the program RC1AVGE2 that restrict the selection of reports with potential changes. This would prevent all reports that were determined by program RC1AVGE1 from being checked.
    • If changes to a specification or phrase could lead to the report program RC1AVGE1 determining very many reports as having potential changes, you should schedule the job for report program RC1AVGE2 in such a way as to prevent all of the reports with potential changes from being checked in one run. Otherwise the runtime could be extremely long.
      • For this reason, you should schedule the job for program RC1AVGE2 with selection criteria (for example, authorization group, specification, report generation variant (RGV), language, number of reports to be checked). This means you can run several jobs simultaneously or spread the checks out over several days.
      Note:
      With this procedure, you must make sure that the selection criteria are chosen for the different jobs in such a way that each report with potential changes is taken into account for checking by at least one job. If the criteria overlap, the report with potential changes is checked by the job that selects the report first.
    • Apart from scheduling jobs periodically, you can also always start the job for the program RC1AVGE2 whenever the reworking of a particular specification or phrase is completed in a particular language.
      • For example, if a specification is reworked over a period of two weeks, we do not recommend that you generate new versions of the reports for this specification within these two weeks. In this case, after a specification has been reworked, you should start the job for the program RC1AVGE2 with a variant that has this specification as a selection criterion.
      In the same way, for example, you should only check all English reports when the reworking of all the English phrases has been completed.
      Note:
      With this procedure you must once again make sure that the reports specified are not forgotten during the checks. We therefore recommend that you run the job for the report program RC1AVGE2 at regular intervals without selection criteria to be sure that all the reports with potential changes are checked.

Result

All reports generated for the worklist have the initial status that is defined in the generation variant header. You can then call the reports in the worklist and edit them.

Depending on the status, older report versions that exist for the same specification, generation variant and language are updated as follows:

  • If the older report version is not yet available with the status Released, the SAP system replaces the older report version with the updated report.
  • If the older report version is available with the status Released, the SAP system newly creates the updated report.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG EHS_SR_250_21 0 HLA0003437 Report Management 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20010320 
SAP Release Created in