Show TOC
Report RC1AVGE1
and Report RC1AVGE2
Report RC1AVGE1 and Report
RC1AVGE2
For performance reasons, worklists are
generated using two reports.
The report program RC1AVGE1 determines the
reports that could have been affected by changes to substances or phrases.
Reports such as these are described in the following as reports
with potential changes. The report program RC1AVGE2 then
determines whether the selected reports with potential changes are actually
affected by changes to substances or phrases and then creates the reports if
required.
Report RC1AVGE1
determines the reports with potential changes and stores them in a database
table. It proceeds as follows:
- It determines the relevant checking
period
- It determines which substance were changed in
this period
- It determines which phrases were changed in
this period
- It determines which substances were changed
due to phrase changes
- It determines which report templates were
changed due to the phrase changes
- It determines which report generation variants
were changed due to report template changes
- It determines which substances changed because
they contain changed substances as components or reference
substances
- It determines the reports for the changes
substances
- It determines the reports for the changed
report generation variants
- It calls a customer exit RC1A0001 to filter the determined reports with potential
changes.
In the customer exit
interface, the reports are transferred to five tables, depending on the reason
for the change. The individual objects that led to the selection of the report
are recorded in each of the five tables so that you can access this
information in the customer exit.
- It determines the reports with potential
changes that were not graded by the filter function
- It saves the reports with potential changes in
a database table
When saving the
reports with potential changes, the system checks whether the report was
already saved as a report with potential changes.
If the report was
not yet saved, it is saved.
If the report was
saved, the report program RC1AVGE1 checks whether the report has already been
processed by report program RC1AVGE2. If so, the report is saved again. If
not, the report is not saved.
All the steps
described above are logged by report RC1AVGE1. You can use the environment
parameter AVGEN_SHOW_MSG to determine in the IMG activity Specify environment parameters whether only reports with
potential changes, or all changes are to be displayed in the log.
Report RC1AVGE2
selects the reports with potential changes using different criteria and checks
whether the reports have actually changed. If required, the report program
creates new reports. To do this, the report program performs the following
steps:
- It selects the reports with potential changes
using the following criteria:
- Substance
authorization group
-
Substance
- Generation
variant
- Report
language
For each of the
criteria listed above, a multiple selection can be carried out. This means you
can, for example, specify several substances or define areas of substance keys
for selection.
Entries with
placeholders are allowed in every input field. In addition, you can specify a
maximum number of reports that are to be selected. The reports are selected
via the database table that is filled by the report program RC1AVGE1 with the
reports with potential changes. Since the report program RC1AVGE2 can be
executed more than once simultaneously, the system checks whether each report
you select has already been processed.
- It processes the selected reports in
packages
Selected reports are
processed in packages. You can define the size of a package using the
environment parameter AVGEN_SPLIT in the IMG activity Specify environment parameters . After a package has been
processed, the changed data is saved in the database and all blocks are
released.
The steps described
below are executed for each package:
- It calls the customer exit RC1A0002 to add substance data before checking the
reports.
In the customer exit
interface, a table is transferred with all the reports of a package. In the
customer exit, you can start secondary data determination for the substances
of a report, such as the EH&S Expert, for example. This ensures that the
substance data is complete before checking the report for actual
changes.
When checking the
reports, the R/3 System establishes whether the changed substance or phrase
data occurs in the report. If this is the case, the report is marked as
changed.
- It deletes and performs initial creation of
the reports to be replaced
Changed reports that
do not yet have released status are replaced with new reports. The changed
report is deleted and a new report with changed data is created.
- It performs initial creation of reports that
were changed and already released.
A new version of the
report is created for reports that were changed and that already have released
status. In other words, the changed report is retained.
- It starts the generation of newly created
reports
- It deletes the checked reports from the table
containing the reports with potential changes.
All reports of the
package are deleted from the table containing the reports with potential
changes.
All the
above-mentioned steps are logged by report RC1AVGE2.
If the
test mode indicator is set at the start of the report, the
report only checks how many reports with potential changes are selected with
the entered criteria. No further steps are carried out.
Note
Setting Up the Report
Programs
- The report RC1AVGE1 should be scheduled in
cycles.
To schedule the job,
proceed as follows:
- If your system is based on a 3.X standard
release, from the SAP R/3 screen, choose
Tools -> Administration and then Jobs -> Define
job.
- If your system is based on a 4.X standard
release, from the SAP R/3 screen, choose
System -> Services -> Jobs -> Define
job
- You have the following options for scheduling
the report RC1AVGE2:
- manually (ad hoc), when the reworking of a
particular substances is completed, for example.
If the report is
scheduled with certain selection criteria, you should make sure that the
selection criteria are selected so that all the reports with potential changes
are checked.
Setting Up the Customer
Exits
To create the enhancements for the customer
exits, proceed as follows:
1. Call transaction CMOD and create an enhancement
project.
Create either a new
enhancement project or use an existing one.
2. Activate the project.
Your enhancement
will only take effect after being activated.
Unlike modifications, enhancements can be
applied to any release since they are not carried out in the SAP original, but
in a namespace that is reserved for the customer. You can find the general
procedure for creating enhancements in the enhancement transaction by choosing
Utilities -> Online manual.