Show TOC

 Planning Service Manager

Purpose

The Planning Service Manager (PSM) is a tool that you use to execute automated planning tasks. You can group various planning tasks, such as forecast, replenishment planning, or Transport Load Builder (TLB), in a planning profile . When you execute a planning profile, all planning tasks within it are executed, and the results are saved.

The PSM carries out planning tasks using planning services . The forecast service, the replenishment service, and the TLB service are all examples of planning services. Using data managers, the planning services access master data, transaction data (such as orders, time series, or stock), alerts, and all other kinds of data. The storage service saves new and changed data to the database and clears the data manager buffers.

The PSM and the planning services write an application log. You can call this up from the SAP Easy Access screen under Start of the navigation path SCM Basis Next navigation step Planning Service Manager Next navigation step Analyze Application Log End of the navigation path

The Package Creation and Parallel Processing functions enable the PSM carry out performant processing of data quantities.

Integration

The PSM uses other functions from SCM Basis and from SAP Supply Network Collaboration (SAP SNC) . You must carry out one or more of the following points in the Customizing, depending on the different applications you want to use the Planning Service Manager in.

  • Order Document Management (ODM):

    Start of the navigation path SCM Basis Next navigation step Order Document Management End of the navigation path

  • Time Series Data Management (TSDM):

    Start of the navigation path SCM Basis Next navigation step Basic Settings Next navigation step Time Series Data Management End of the navigation path

  • Logistics Inventory Management System (LIME):

    Start of the navigation path SCM Basis Next navigation step Logistics Inventory Management System (LIME) End of the navigation path

  • Transaction Data Layer (TDL):

    Start of the navigation path SCM Basis Next navigation step Data Management Layer Next navigation step Transaction Data Layer (TDL) End of the navigation path

  • Trigger (for planning file entry):

    Start of the navigation path SCM Basis Next navigation step Data Management Layer Next navigation step Trigger (for Planning File Entry) End of the navigation path

The PSM is an SCM Basis tool that can be used by various applications. Planning services and service profiles for the PSM are prepared by the respective applications. It is possible for every planning service to have a service profilewhere you can set parameters such as model, planning horizon, or time series, that you want the system to take into account during the planning run. The parameter type and the number of parameters can differ a great deal, depending on the service.

Features

Data and Objects in PSM

The following graphic is an example of which data and objects the PSM accesses and how it uses these in the planning profile.

The system calls up the PSM with a planning profile. In the planning profile, you define which planning steps are executed in which process blocks . The PSM calls up the planning services (such as the forecast service, the replenishment service, and the storage service) in sequence, as defined in the planning profile. The storage service calls up the data managers that are responsible for reading and buffering time series, orders, and master data for example. In the selection, you define which planning objects you want the system to consider when executing the various planning services.

Structure of the Planning Profile and Process Blocks

The following graphic shows the structure of the planning profile:

A planning profile consists of header data and one or more process blocks. The header data contains administrative information for the planning profile, such as who created or changed the planning profile, and when. The process blocks follow the header data. A selection, a planning version, a process profile, and an optional trigger group are defined in every process block. These setting apply for all planning services that are executed in the attached service list.

Every planning service can have a service profile that is prepared by the respective application. At the end of the service list, the system automatically calls up the storage service with the &SAVE+INIT profile, without executing it in the service list.

The PSM creates packages of planning objects for every process block from the selection and planning version defined. The PSM creates packages using the package creation method defined in the process profile. If a trigger group has been defined, only planning objects for which at least one trigger of the trigger group is set are considered during package creation. The packages can be processed in sequence or in parallel. Parallel processing helps improve performance. Instead of processing packages in sequence, packages can be processed in parallel, which can save time. The PSM executes the planning services from the service list separately for each package .

Examples of package creation methods are: Location Product (by Product), Transportation Lane (Simple Method), and No Package Creation.

Planning Services

In the Responsive Replenishment replenishment scenario, you can plan the following planning services in a planning profile for example:

  • Order Forecast Service

  • Deletion Service (only for TLB shipments and replenishment orders)

  • Replenishment Service

  • ProAct Check Service

  • Forecasting Service

  • TLB Service

The storage service is available for all applications and scenarios.

The planning services are assigned to specify package creation methods.

For more information on setting options in the PSM , see Customizing for SCM Basis under Planning Service Manager.

Restrictions

You can only use the PSM if the application concerned provides the necessary planning services, data managers, and storage profiles as standard.

Parallel processing is not available for all planning services, and is dependent on the assigned package creation method.