What it does:

The Data Copy utility copies data from one category to another. Data can be copied directly or be factored before it is copied to the new category. All values or a specified value can be copied to the new category.

How it processes:

Categories that share the same number of buckets: Data Copy will perform best when copying data to and from categories that share the same View Group bucket mappings. In these cases, the copy will write out one record to the pending for each bucket.  Please note that when the “Replace” option is used and data exist, additional records will be written to the pending file to offset the existing data.

Categories that do not share the same number of buckets:  Data Copy will use additional logic in order to copy and summarize data.

For example:

Data Copy selecting Daily Structure to copy to Weekly Structure, specifying a view set of months.

    1. First Data Copy determines the days making up the month based on the view group bucket mapping. Then it identifies the sum for the month.

Daily: Jan = days 1-31, sum the amount in the buckets for these days = 18.00

Weekly: Jan = weeks 1-6, divide the amount 18 by 6 (the number of weekly buckets which make up Jan). Writes out a record for each of the 6 weeks buckets to the pending file. Per this example the amount will be 3 for each of the six weeks.

  1. Do the same process all over again for the next month.
  2. If the “replace” option is used, the process will write out records to reverse/zero out existing data. This will appear as additional records in the pending file.

(For more information on options and setting for Data Copy see System Administration Guide, Chapter 5, “Using Utilities”).

When to use:

This function is primarily used during the budget process. At the start of the budget process, the data for last year’s budget or from last year’s actual sales are copied to become the rough-cut budget for the new year.

In this case we suggest both categories share a view set bucket mapping at the lowest entity considering both categories to avoid the overhead associated with summarization.  In the case of “Daily” category to “Weekly” category, use a “Weekly” view set in Data Copy to minimize summarization.

Also, clear data in the “to” category to avoid using the “Replace” option which will write out additional records to the pending file.

When not to use:

When there is a large amount of data needed for multiple years, such a historical load. In this scenario it is better to use an import program along with specifying a memory size in the DALOAD command. These types of jobs should always be directed to process in a dedicated subsystem. This will give the best performance. (Refer to “Setting up a Dedicated Subsystem” for more details)