Generating Forecast Packages

This chapter explains how the administrator constructs the forecast packages for the forecasters.  The process includes managing user dataset access. In the cases where the work methods are either distributed offline or online, the administrator also creates tools for the forecast packages (such as, defining filters, creating favorite views, and to-do lists). Finally the forecast packages are generated. They are then distributed or the central version is opened for forecasters.

Outcome

A tailored forecast package for each forecaster is available to forecasters using distributed work method and the central version is open for forecasters using central work method.

The forecast packages and the central version are used by the forecasters to make their Market Forecast Proposals based on market intelligence.

Data import and any forecast activities performed in M3 DMP do not affect M3 Business Engine. The M3 Business Engine is only affected when exporting data from M3 DMP. See Exporting Consolidated Sales Forecast Proposal.

Before starting

The Changeable Time Horizon for the Version must be defined before version is opened and packages are created. See Adjusting Environment.

Processes

To make data available, only activities four and five are necessary. Activities one through three are used to create optional tailored tools for the forecasters and can be performed in a different order. Activity six is only necessary to perform if one or more forecasters are not connected to the M3 DMP server.

Activity Description

  1. Define filters

    Use this activity to define filters, that are used to select parts of a Dataset for example, views. To identify which records from the Dataset that should be included, a range of periods, key values and data types are selected. see About Filters.

  2. Create to-do lists (optional)

    In this activity, To-do items are established and assigned to forecasters. This list is included in the forecast package generated for the forecaster or is available for a forecaster logged on to a central version. See Create a To Do list.

  3. Define user dataset access and user domains

    In this activity each users access rights to the Datasets in the Version are defined. The user can be assigned with the following rights to a Dataset: change, view, or none. If a user is given rights to either change or view a Dataset, certain domain rights can be assigned to the Dataset. It means that a user can be limited to have access to specific data in a Dataset. A users access rights and domains determine which Datasets can be included in a forecast package to the user or is available in Datasets menu for a forecaster using central process flow: only Datasets with change or view rights can be included.  See About Users and Define user dataset access.

  4. Open Version and Generate forecast packages

    In this activity the forecast packages for the forecasters are created. It is possible, in the Open dialog box, to run an automatic clean-up of where the old packages are stored before the generation of new ones.

    The previous Sales Activities from a user are included in the forecast. Note that only changes that are committed will be included in a package. The generated forecast packages are available on the specified online or offline location (depending on work method).

    A forecaster who is using the central process flow will have access to the Datasets assigned to him when the administrator opens the version. See Open Version, Close Version and Generate Forecast Packages.

  5. Distribute forecast packages

    Use this activity to distribute forecast packages if one or more forecasters are using distributed offline work method (not connected to the M3 DMP server). Forecast packages for these users are stored as a compressed file in the specified offline location, which offers many alternatives to distribute the package (email, file copy, and so on).  See About Forecast Cycle in M3 DMP.