Data Processing in Mass Runs

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/a9/fdc5536a51204be10000000a174cb4/frameset.htm

Created on June 10, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Table of content
1 Data Processing in Mass Runs
1.1 Parallelization of Data Processing
1.2 Create Counters for Mass Runs
1.3 Assignment of Reconciliation Keys in Mass Runs
1.4 Functions for Scheduling Program Runs
1.5 Handling Parameter Records

PUBLIC Page 2 of 6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1 Data Processing in Mass Runs

Purpose
Business processes where large volumes of data are processed, such as the payment run or dunning run, are realized in Contract Accounts Receivable and
Payable by mass activities. Mass activities automatically split the dataset to be processed, such as a quantity of business partners or contract accounts,
into several technical jobs and process them in parallel.
In addition to the mass activities delivered by SAP, you can also create your own installation-specific mass activities. For instructions about how to proceed,
see the Implementation Guide for Contract Accounts Receivable and Payable under Technical Settings Prepare Mass Activities .

1.1 Parallelization of Data Processing

With the mass activities of Contract Accounts Receivable and Payable, you can split the data for processing over several jobs that the system then
processes in parallel. See also SAP Note 607797 ( Job Control for Mass Activities: FAQ ).

Process
All mass activities have a uniform layout. You enter data on the following tab pages:
General Selections
Activity-Specific Selections
Technical Settings
Logs
On the Technical Settings tab, you can choose one of two options for load balancing: either an automatic distribution by the system, where you enter only the
number of jobs, or an explicit load distribution, where you enter explicitly how many jobs are to run and on which servers. For more information about the
entries on the individual tabs, see Functions for Scheduling Program Runs.
Once you have made all of the entries required to execute the business process, you can schedule the program run. You can choose between immediate
processing in the background or processing on a specific date. If you use the job container, you can also select the containers available.
During the processing of the data, the system distributes the dataset to be processed to several parallel jobs automatically. The details for distributing the
keys for the parallel objects are stored in variants that you have to update periodically. For example, you can create a variant for the business partners that
splits the business partner set to be processed into 1000 equal intervals.
During parallel processing, the system makes sure that the processes do not block each other because of changing accesses to the same database
resources, which could be the case, for example, in the assignment of document numbers or the update of transaction figures.

Example
A payment run for all business partners starts several processes (for example, 10) that process the intervals created automatically one after the other.
When the processing is completed for an interval, the system processes the next free interval. If all intervals have been processed and therefore all
technical jobs are completed, the business task receives the status Completed .

You can schedule the parallel interval jobs of mass activities, execute them in a specific order, and monitor them using the following tools:
Job Commander of Contract Accounts Receivable and Payable
External job control system

1.2 Create Counters for Mass Runs

Use
You want to add your own counters in an interval, in addition to the standard counters, such as error count and number of hits.

Procedure
To add counters to the mass activities provided by SAP, proceed as follows:
1. In Customizing for Contract Accounts Receivable and Payable, choose Technical Settings Prepare Mass Activities and select the mass
activity, for which you want to make settings. If you do not want the standard counters to be displayed in logs, you can suppress these counters. To do
so, choose General Control in the tree structure and then the Other tab. If the Display Standard Counter indicator in the Standard Counter group
box is not set, then the standard counters are not displayed.
2. Choose Counter Definition in the tree structure.
3. Enter the counter number in the Counter field. The number corresponds to the COUNTID field that is in the structure FKK_MASS_ACT_COUNT
implemented in the interval module.
4. Enter a description for the counter in the CounterTyp field. The description is needed for displaying the counter in the application log.
5. Enter a data element in the Element field. The field labels of the data element are needed when the counter is displayed in the job log.
6. In the Application Log field, specify if the counter is listed in the application log.
7. In the Job Log field, specify if the counter is displayed when the job logs are displayed.
To implement counters for your own custom mass activities, use the interval module defined for the mass activity. To do so, define a table T_COUNTER with
structure FKK_MASS_ACT_COUNT in the interface of the interval module. The structure FKK_MASS_ACT_COUNT consists of two elements that are filled in

PUBLIC Page 3 of 6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 table T_COUNTER. COUNTID contains the counter number, and VALUE contains the value of the counter. A sample implementation in the interval module has
the following form:
DATA: wa_t_counter LIKE LINE OF t_counter.

wa_t_counter-countid = <Zählernummer>.

wa_t_counter-value = <Wert des Zählers>.

APPEND wa_t_counter TO t_counter.

1.3 Assignment of Reconciliation Keys in Mass Runs

Use
For mass activities that post, such as dunning, payments, and interest calculations, you can define a reservation key for reconciliation keys in Customizing.
This ensures that not all mass activities access the same origin key.

Activities
In the Implementation Guide for Contract Accounts Receivable and Payable , under Technical Settings Prepare Mass Activities , in the General
Control on the tab page Reconciliation Key , an origin key is defined for every mass activity. If no value is defined here, the origin 18 Other Activities is
used.
If you set the indicator No Reconciliation , no reconciliation key is reserved, opened, closed, and released for the mass activity type concerned. You can also
define a reservation object for the reconciliation key. If you do not make an entry in the field Object , the system automatically uses the reservation object of
007 Mass Activities .

1.4 Functions for Scheduling Program Runs

You want to schedule a mass run.

Activities
The functions listed below are available on the individual tabs:

Tab Functions Action

General Selections Function for entering, changing, or displaying the
parameters of a program run. You can only make
changes to program runs that have not been
scheduled yet.
Enter the parameters that you want to use to restrict, for
example, the items to be processed (for example,
company code, contract account, business partner).
Enter no selection criteria if you want the program run
to process the whole data set.

Tab(s) for activity-specific selections, for example, Enter additional activity-specific parameters, such as Enter parameters as required.
Custom Selections additional selection parameters.

Technical Settings If you wish, the programs are run in parallel. To Select either Automatic Load Distribution or Explicit
execute several jobs at the same time (parallel Load Distribution and specify the number of jobs and
processing), enter the number of processes and the the target host.
target host. Several jobs are then started Select a variant. The system proposes the block size.
simultaneously in one program run, each processing If the program run is to be executed by a single run
one of the intervals in parallel. You can divide the (that is, not in parallel), you do not have to make any
intervals according to different criteria. This division is technical settings.
controlled by variants in which you can specify the
number and size of the intervals, and which key area
each interval covers. If you want to run the program in
parallel, either specify a target host and the number of
jobs assigned, or specify several target hosts with the
number of jobs assigned to each one. For parallel runs,
you can also use automatic load distribution. This
means that you specify a number of jobs that the
system automatically distributes to the application
servers available.
The block size is used differently by the individual
mass activities. For example, you can control how
many selected items are held in the main memory or
how large a COMMIT block is. For information about
using the block size, see the documentation for the
individual mass activities.

Logs The job log records status information and any errors Choose the log you want.
that occur during the program run. The application log
contains business-relevant information. You can make
the following additional settings for the application log:
By making a specification in the Problem Class field,
you specify the importance that a message must have
to be output in the application log. For production, SAP
recommends class 2, for testing, class 4:

PUBLIC Page 4 of 6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Very important (1)
Important (2)
Average (3)
Additional information (4)
If you specify class 3, logs with lower classes are also
output, that is, also 1 and 2.
The expiry date specifies the earliest date on which the
log expires. It can also influence the event in which the
log is deleted. This is particularly relevant because
from the application log, you can schedule jobs, and
delete logs from the database where the expiry date
has been reached.
The Hold until Expiry Date indicator prevents the log
from being deleted before the expiry date specified.
The application logs are displayed in Enhanced
Message Management (transaction EMMA). There you
can create and monitor clarification cases for error
messages.

The following functions are also available:

Function Meaning Action

Display/Change Switch between display and change mode. Choose whether you want to display or change the
program run.

Copy Copy the parameters of a program run Specify a name for the program run that you created
using the copy function.

Adjust Copy the run parameters of a program run and move

the run date and other date fields by n days.This
function is not supported in all applications.

Variants On the Technical Settings tab, you can create variants To create a variant:
dependent on the parallelization object for the split into 1. Choose the button Variant Maintenance .
intervals. If dynamic interval creation is not supported 2. Choose New . You can specify either the
for a mass activity, you can change the variants interval size or the number of intervals.
manually. If the underlying data changes frequently, 3. Choose Execute.
you should regenerate the variants regularly to achieve To display the intervals created or to edit the variant,
an even interval distribution.
double-click on a variant name on the initial screen of
variant maintenance.

Simulation Run In most mass activities, you can repeat a run as a Set the Simulation Run indicator and schedule the
simulation run as many times as required; however, run.
you can only execute it as an update run once. After
you have executed a simulation run, the parameters
remain ready for input. When you schedule a run that
has already been executed as a simulation run, three
actions are carried out:
Deletion of temporary interval distributions
Deletion of jobs
Deletion of the application log

Schedule Defines when the run is to be started Choose the Schedule Program Run ( Schedule )
pushbutton. In the dialog box that appears, you can
choose between an immediate start in the background,
a start in the background with specification of start date
and time, or a start in the background via a job
container of the job commander.

End Early Terminates a run.

That means that if the program is running, once the
current interval has been processed, all jobs are
terminated with this command.

Restart Run Restarts runs that have been stopped.

Delete Deletion of a program run. All parameters of the

program run are deleted. If the program run has
already been scheduled or started, it cannot be
deleted.

Deactivate Old Runs This excludes runs that are no longer needed from
being displayed in the entry help. To remove the data
from the database permanently, in the menu of the
mass activity, choose Program Run Delete . Or
on the SAP Easy Access screen, choose Periodic
Processing Administration of Mass Processing
Delete Parameter Records .

Environment Enables navigation to other transactions dependent on

the application area. (Not available in all mass
activities.)

1.5 Handling Parameter Records

PUBLIC Page 5 of 6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.5 Handling Parameter Records

Use
You can hide or delete parameter records that you no longer need if necessary, or display records that you have deleted.

Activities
To hide parameter records, in the SAP menu choose Periodic Processing Administration of Mass Processing Hide Parameter Records . This
enables you to display only the runs important to you in the possible entries help.
To physically remove parameter records no longer required from the database, in the SAP menu choose Periodic Processing Administration of Mass
Processing Delete Parameter Records .
To delete data from payment runs, in the SAP menu choose Periodic Processing Delete Data .
If you deactivate parameters records of a mass activity, you can reactivate them – provided they have not been finally deleted under Administration of
Mass Processing Delete Parameter Records . In the SAP menu choose Mass Processing Display Parameter Records Again .

PUBLIC Page 6 of 6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.