Process documentationMaintaining SNP Master Data and Time Series Locate this document in the navigation structure

 

Keeping Supply Network Planning (SNP) master data and time series up-to-date is an important prerequisite for successfully using Supply Network Planning (SNP) applications.

Time series key figures in SNP are assigned to SNP aggregates, which represent certain planning relevant master data combinations, for example, location and product. When a planning area is first initialized, SNP master data is generated representing valid combinations of APO master data, and the corresponding time series are created in liveCache. However, changes in APO master data are not immediately reflected in SNP master data or time series in liveCache. To make sure that changes are visible in SNP, use the following reports:

  • Initialize Planning Area (transaction /SAPAPO/TSINIT)

  • Consistency Check of Time Series Network (transaction /SAPAPO/TSCONS)

  • Reorganize SNP Time Series (report /SAPAPO/TS_LCM_REORG_SNP)

Prerequisites

You have understood the differences between the different storage methods in Demand Planning and Supply Network Planning, and know which functions are supported by which storage methods. For more information, see Saving Data in DP and SNP.

You have understood the role and purpose of the following:

Note Note

To use time series, you need an SNP planning area that contains time series key figures. For more information, see Planning Area Administration. If you are using planning areas without time series key figures (for example, planning area 9ASNP02), the steps for updating and checking time series are not relevant for you.

End of the note.

Process

This graphic is explained in the accompanying text.

SNP Time Series Update and Maintenance Cycles

The SNP master data and time series monitoring tools integrated into CCMS help to set up the correct frequency of running the update and maintenance cycles and to detect any unexpected alert situations. Monitoring alerts can initiate update and maintenance cycles.

Time Series Update Cycle

The purpose of the update cycle is to adapt SNP master data and time series to the changes in APO master data. Therefore, the frequency of the update cycle depends on the frequency and amount of master data changes. A typical example is to use a periodic – most often daily - CIF master data change import and perform the time series update cycle immediately after CIF import.

The update cycle consists of the following steps:

  1. APO master data changes

  2. Delta initialization of planning areas, including

    • SNP queue update

    • SNP master data update

    • Delta initialization of SNP time series

For more information about SNP queue and master data update, see Processing Master Data Queues in Supply Network Planning (SNP).

Time Series Maintenance Cycle

The purpose of the maintenance cycle is to check the consistency of SNP master data and time series, and to correct any possible errors. The frequency of running maintenance tasks also depends on the frequency and amount of master data changes. A typical example is to run consistency check weekly or monthly and reorganization once a quarter or year.

The maintenance cycle consists of the following steps:

  1. SNP time series update cycle

  2. SNP time series consistency check

  3. SNP time series reorganization