Kontakt

Ansicht
Dokumentation

EHENV_MDEF_CHECK_EXE - Schedule Jobs for Measurement Checks

EHENV_MDEF_CHECK_EXE - Schedule Jobs for Measurement Checks

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can schedule a background job that executes a check for missing, due, or overdue data collection entries in the system.

The background job controls the execution of the report R_EHENV_MDEF_CHECK_EXECUTE.The report executes a check on the system and identifies all active data collection definitions that are ready for the collection of environmental data. The report examines the data collection definitions that consist of missing entries, and, depending on the due date within the period, the background job notifies (via e-mail) the responsible party about the missing data collection. In case the data entries of daily, monthly, or yearly data period are missing at the due date, a reminder (notification) is sent to the responsible environmental technicians. Note that the data entries of data period hourly are collected automatically in the system. For this reason, notifications for missing hourly data collections are not sent to technicians. Otherwise, if any of the data entries are overdue, the notification is sent to the responsible environmental manager.

To trigger the collection of daily, monthly, or yearly environmental data, we recommend that you schedule the background job to run on at least a daily basis (for example, at midnight). You can also schedule the job to run at shorter intervals, but as a prerequisite, prepare report variants with the corresponding input parameters. If your business case features many locations that span different time zones, we recommend that you schedule the background job to run at shorter intervals (for example, every 2 hours). If you wish to trigger the automatic collection of hourly data, schedule the report to run hourly.

This job processes amounts in chunks of 200. After a chunk is processed, the data is saved to the database as a means of backup of the current state of the job.

To prevent the job from running too long and blocking the running of other jobs, there is a set maximum processing time. When the set maximum processing time of 1hr is reached, the job is stopped automatically, even if it is not complete.

Note

Alternatively, you can set the report execution in transaction SM36.

Before you schedule the background job, make sure that the following prerequisites are met:

  • Your user for background processing is authorized to access information for data collection definitions in the system.
  • Create a productive variant of the report (and configure the corresponding input parameters).
  • Use the standard SAP user for the workflow system (SAP_WFRT).

  1. Use the Job wizard to specify general data and schedule the job. You define the job for the report R_EHENV_MDEF_CHECK_EXECUTE.
  2. Schedule the job to run as a background process and specify the corresponding interval.
Depending on your business case, you can schedule the job to run once a day or in shorter intervals.

To create a productive variant of the report, proceed as follows:

  1. Start transaction SE38.
  2. Enter the program R_EHENV_MDEF_CHECK_EXECUTE.
  3. Open the Goto menu and choose Variants.
  4. Enter a variant name and then choose Create.
  5. In the Check Missing Data area, you can specify checks for missing entries of various data periods.
  6. To check for all overdue data explicitly, select the corresponding checkbox.
Note that this option checks for overdue data of all data periods available in the standard delivery: hourly, daily, monthly, quarterly, half-yearly, and yearly.
  1. In the Execution Options area, specify a job execution period.
  2. Deselect the Run in Test Mode (No Save) checkbox.
  3. If you wish to enable extended logging in the background, select the corresponding checkbox.
  4. Choose Attributes and then Copy Screen Assignment.
  5. Enter a description and save your changes.

To schedule the background job to run the report, proceed as follows.

  1. Start the Customizing activity and then open the Job wizard.
  2. In the General job information step, enter a job name.
  3. In the Defining a Job step, choose ABAP program step.
  4. In the Define an ABAP Program Job step, enter the report (R_EHENV_MDEF_CHECK_EXECUTE) in the ABAP program name field and then enter the corresponding variant.
  5. Choose the start condition for the job.
Schedule the date/time at the end of the day and set it to repeat periodically. Note that the period you set must match the period of the selected variant.
  1. Complete the wizard.

For more information about scheduling background jobs, see SAP Help Portal at http://help.sap.com/nw70.
Choose SAP Library -> SAP NetWeaver -> SAP NetWeaver by Key Capability -> System Management -> Background Processing -> Job Scheduling Explained -> Scheduling Background Jobs.






BAL Application Log Documentation   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 6260 Date: 20240523 Time: 165048     sap01-206 ( 95 ms )