Generation of RPM Time Series - SAP Documentation

Use

The system calculates the total of the individual component requirements lying within a time bucket for each component. In the process, the system determines the buckets (periods) on the basis of the settings in the period profile .

These aggregated component requirements are stored in the liveCache in the form of time series and updated in the event of order changes. The time series enable a significantly faster read-out of the component requirements and thus also faster display. The requirement time series also constitute the basis for determining pegging relationships .

This graphic is explained in the accompanying text.

Integration

The system generates time series for all dependent requirements in the matrix. The Collective Requirement indicator has been set for all these components. The system consolidates the dependent requirements for these components in accordance with the settings from the period profile. See also: Grouping Component Requirements
In the product view , you can display the requirements for a component consolidated per period on the Elements tab page.

You cannot display the RPM requirements on the ATP tab page however. You only display fixed components and carry out an ATP check for them.
In the MRP run, the system creates corresponding receipt elements for the aggregated requirements.
The system cannot take the RPM requirements into account on the detailed scheduling planning board .
The system outputs individual records for components for which you have specified individual customer requirement . These components are stored in the order for the end product as requirement components (input nodes). See also: Treatment of Individual Customer Requirements .

Prerequisites

Only requirements for components for which the Always Collective Requirement indicator has been set in the product master can be consolidated and saved in the time series.
You have created a period profile in Customizing for the planning matrix and defined the periods (buckets) in which the system is to consolidate requirements. Because you can assign a separate period profile to each component, you can define different periods for each component.
In the IMG activity Make Global Settings in Customizing for the planning matrix, you have checked the settings for the time series and, if necessary, specified a wait time . With the wait time, you can specify how long the system is to wait before triggering a new time series generation if the system cannot generate the time series directly following the RPM run due to another process that is blocking it.
In the control data for the RPM product , you have specified that the time series are to be generated directly following the RPM run.

Features

Generation of Time Series

Time series can be generated in the following ways:

Directly following an RPM run
Dynamic generation

The system generally generates time series if they are needed the first time to read the data and have not previously been created.
Using the report RPM_TIMELINES_CREATE

You can use this report to generate the time series independently of the RPM run. This always makes sense if there are processes executed parallel to the RPM run and it is not possible to create the time series at this moment.

The system can only create time series for future use if no other parallel transactions (such as a confirmation) that use the old time series are open. This would otherwise lead to inconsistencies.

SAP recommends generating the time series directly following the RPM run. If a parallel transaction (such as a confirmation) is running at the same time, the system recognizes this and waits until the transaction has been completed before generating the time series. For this reason, it is sensible to set a wait time in Customizing for the planning matrix. If the system cannot generate the time series after the wait time has expired, where necessary it performs a dynamic generation.

Updating of Time Series

The dates/times of the time series are adjusted automatically following each order change.

Output quantity changed
Date/time of an order activity moved (e.g. start date changed)
Active mode of an activity changed
Confirmation
ATP check carried out for an order
Component fixed
You change the period profile. This leads to a change in the table of periods . As a result, the affected RPM time series becomes invalid and is deleted. The system should therefore regenerate the RPM time series following reorganization of the table of periods. To achieve this, you must set the Set Up Time Series After Reorg of Table of Periods indicator under Maintain Globale Settings (Valid Client-Wide) in Customizing for the planning matrix.

Caution
The creation or deletion of orders does not influence the existing RPM time series. If new orders come in, you must carry out an RPM run in order to include them in the planning matrix. The component requirements from deleted orders remain in the time series until the planning matrix is updated in the next planning run. After this, these requirements are also removed from the time series.

End of the caution.

Deletion of Time Series

The following actions lead to the deletion of a time series:

You delete a planning matrix, after which the system activates a new matrix.
You change a period profile. The system then adjusts the table of periods accordingly. The time series becomes invalid as a result and is deleted.
Change in the resource timestream

See also: Displaying the Resource Time Stream .

Activities

To be able to dispolay the consolidated requirements for a component, which the system has saved as time series, you must invoke the product view of the desired component.

On the Elements tab page, you can see dependent requirements consolidated per period. The Receipt/Requirements Element column shows the planning matrix from which the requirement was determined for each aggregated dependent requirement. By double-clicking on the name of the planning matrix you invoke an overview listing the causal (pegged) orders.
To check whether the system has generated the time series following an RPM run, you can invoke the RPM log. The log shows whether or not the system has generated time series. If no time series have been generated, the log also shows the process that blocked their generation.

To invoke the log, choose Production Planning Automated Production Planning and Optimization Rapid Planning Matrix Tools RPM Logs.