SAP® Documentation

Single view

/FRE/CONVERT_FRP_COMPRESS_DATA - Migration of Order Forecast/Demand Period Data

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to migrate a database from conventional data storage method to clustered and compressed data storage method for demand period, and/or order forecast data or vice versa.

We recommend that you use the clustered and compressed data storage method only in the case that an extremely high amount of data for one of the tables leads to problems in the database.

The migration can be carried out for both tables separately.

The migration of order forecast data is done by switching the storage method for this type of data to what you select under Storage Method. It transfers all existing data of this type from the current table (the table currently used for this type of data) to the new table (the table used for this type of data after the switch).

The demand period data is not transferred while migrating the data storage because the data is only used by the Forecasting and Replenishment Porcessor (FRP) run (which deletes and recalculates the existing data) and for traceability purposes. So, the existing data is lost during migration and the calculation details are not available until the next FRP run is started.

See also: SAP Note 1389741

Integration

As the report does not check any FRP locks, do not execute it in parallel with an FRP run. To avoid interfering with the FRP runs, you can etsimate the approximate run time of the report in advance.

You must use the same level of parallel processing in the report and in FRP execution.

  • Approximate run time of changing storage method for order forecast data:
The run time of the data transfer takes approximately as long as the run time of task /FRE/FU_CL_FRP_SAFIN_ORDFCST (if order forecast is executed for all location products on the same planning day), the same applies to the deletion of the superfluous data.
  • Approximate runtime of changing storage method for the demand period data:
    As there is no data transfer, you only have to consider the run time of the deletion of the superfluos data. If you have activated the order forecast for all location products, the approximate run time is as long as the run time of task /FRE/FU_CL_FRP_SAFIN_ORDFCST. If you have no order forecast activated, the run time depends on the optimization horizon.

Prerequisites

Features

Selection

  • Data Migration: You can select the migration of demand period data and order forecast data separately.
  • Storage Method: You can select how the data should be stored in the future - in a compressed or a conventional (uncompressed) manner.
  • Delete Source Data: You can decide to not choose this option which then does not directly delete the superfluous data in the source tables. This option can be selected, for example, if you have to reduce the report's run time because the time window you are using to run the report is critical . The deletion of source data can then be carried out at a later time.
  • Processing Options:You can specify how background jobs are split into parallel processes. Here you define how many parallel processes can be used, the database package size and whether a particular server group is to be used.

Standard Variants

Output

Activities

Example






BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3850 Date: 20191021 Time: 172507     sap01-206 ( 26 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.