Purpose
You use this program to determine the quantities of the substances to betracked.

Prerequisites
In Customizing for Substance Volume Tracking, you have processedthe following IMG activities and made the required settings there foreach relevant regulation:

• Check Prerequisites


• Specify Scenarios


• Specify Selection Criteria for Volume
Tracking

• Specify Data Transfer (Property Tree)


• Set Up Job for Volume Tracking

In this last IMG activity, you also find information about how you needto schedule this program so you can implement substance volume tracking.
Before executing the substance volume tracking, all relevantmaterial-substance relationships and substance compositions must be tra
nsferred into the substance-volume-tracking tables using filling reportRREGCH_FILL. To do this, start the report without any selectioncriteria.
If you perform a run in the past and you work with change numbers, thefilling must be performed for this time period. This means that you mustuse the relevant valid-from date.

Features


• Initial Run

All logistics documents that are new or have been changed between thestart date and end date are read and tracked in the initial run.
The start and end date for the selection do not refer to the date onwhich the documents were posted. If the dates were to correspond withthe actual posting or validity dates, such as delivery date, documentscould be posted twice or not posted at all.
To track all documents for a time period, you must extend the timeperiod into the past and into the future, so that all postings that arerelevant for the time period are taken into account.
For confirmed volumes, the posting date is used as the validity date forsubstance volume tracking. For planned volumes, the date used depends onthe scenario (for example, delivery date).

• Delta Runs

All new or modified logistics documents after the last successful runare read and tracked in the delta run. The delta run can also coverseveral days.

• Completed Runs

The time period for previously completed runs is stored in tableCCRCT_RUN for each scenario and regulation. Further substance-volum
e-tracking runs must follow on directly from this time period and cannotoverlap with existing time periods. This enables several initial runs tobe performed directly after one another. Initial runs cannot be carriedout for the period after a delta run is completed. However, you canrepeat an initial run for the time period before previously completedruns.

• Runs with Errors

If an error occurs during the substance volume tracking, the substancevolume tracking is interrupted, starting with the current selection timeperiod. Volumes are not tracked for this time period and the CCRCT_RUNtable is not adjusted. If data was already previously tracked for theselection time period in the same run, this data is saved and tableCCRCT_RUN is adjusted for the last completed selection time period.

• Track History

The history can be recorded during substance volume tracking. Set theTrack History indicator in IMG activitySpecify Scenarios. If you do not recordthe history, you can define this in the IMG activityPackage Processing.

• Save Additional Info to Log

Set this indicator to save messages of the additional informationproblem class to the application log. The following messages areexamples of additional information:
"Calling function module &1"
"Document &1: recipient country/country of origin &2 not relevant toregulation &3/identical"

Selection

Standard_variants

Output
The tracked substance volumes are displayed in transactionSubstance Volume Tracking: Monitoring (CBRC20).
You can call the application logs for substance volume tracking intransaction Substance Volume Tracking: Log (CBRC10).