Implementing Planning Function Types (SAP Library

Implementing Planning Function Types

Use

Planning function types are procedures that can be parametrized and that change transaction data within BI Integrated Planning. The system offers you a number of default planning function types (such as copy, delete, repost, revaluate, distribute by reference data or by key, unit and currency translation or FOX formula).

You can also implement customer-specific planning function types in order to implement specific procedures and apply them to transaction data. Each planning function type comprises

● a definition part (metadata) that is created and changed in a transaction (RSPLF1),

● an ABAP-OO class in which the actual procedure is programmed. The class name is part of the definition part.

Integration

With regard to transport, Business Content and activation, planning function types behave like other metadata objects of the BI system.

The active planning function types are visible in the Planning Modeler and can be used to create and execute planning functions.

Features

In the maintenance transaction for planning function types, you can display, change and create customer-specific planning function types.

Activities

Creating Planning Function Types

...

1. To get to the maintenance transaction for planning function types, on the BI Integrated Planning screen in the Administration and Development screen area, choose This graphic is explained in the accompanying text Maintain Function Types. The Edit Planning Function Type screen appears.

2. Enter a technical name for the planning function type.

3. Choose This graphic is explained in the accompanying text Create. The screen for creating a planning function type appears.

4. Enter a description for the planning function type and make the required settings on the Properties and Parameters tab pages.

Tab Page: Properties

Screen Area	Description
Implementation	Enter the name of the ABAP class that implements the procedure. The ABAP class has to implement one of the two interfaces: ● IF_RSPLFA_SRVTYPE_IMP_EXEC ● IF_RSPLFA_SRVTYPE_IMP_EXEC_REF The latter interface is relevant when you need reference data for your procedure. The implementation of methods of the specified interfaces is optional with the exception of the method EXECUTE. In addition, the class can implement specific check methods that are executed at runtime. The interface IF_RSPLFA_SRVTYPE_IMP_CHECK serves this purpose. You can select the following indicators: ● Reference Data: If the indicator is selected, reference data is required when you execute the planning function. ● Without Blocks: If the indicator is selected, the transaction data is processed without creating blocks; that is, all characteristic values in the transaction data can be changed. In this case you cannot create conditions since the selection table for each condition may only contain characteristics that can also be used to create blocks. ● Process Empty Records: If the indicator is not selected, all the empty records are ignored during processing.
Characteristic Usage Interface Display	Using Web Dynpro and development components, you can create your own user interface instead of the standard user interface for characteristic usage. You can also select the following indicators: ● Hide Column of Characteristics to be Changed: This indicator is meaningful if you want to perform processing without blocks or if the characteristics to be changed are the result of other settings. ● Display First When Creating: If this indicator is selected, the user interface of the characteristic usage is first displayed when a planning function is created; otherwise the user interface with the parameter values is displayed.
Parameter Interface	By using Web Dynpro and development components, you can create your own user interface instead of the standard user interface for parameters.

Tab Page: Parameters

Create the required parameters using Create Parameters or Create Components in the context menu of an object in the parameter hierarchy. You can change the details of existing parameters by choosing Properties in the context menu. With This graphic is explained in the accompanying text and , you can change the sequence of the parameters. The sequence of the parameters is taken into account when you create a planning function for this planning function type.

With the Parameter is Tabular indicator you can mark a parameter as a table; it will then behave like an internal table. In this table, each row of the tabular parameter has the properties that correspond to the selected parameter type. The indicator is valid for all parameter types (in the context menu with Properties) with the exception of Key Figure Selection or if parameters are used as components of a structure parameter.

Parameter Type	Description
Elementary (Elementary Parameter)	The value of an elementary parameter is the value of a specific InfoObject. This means that every elementary parameter is based on an InfoObject and thus inherits its technical properties. If the InfoObject is a characteristic, the system automatically checks the validity of a value entered by the user based on the master data.
InfoObject of the InfoProvider	The parameter can include the name of an InfoObject from the current InfoProvider (aggregation level). You can define the valid InfoObjects with the selection Restrict. InfoObject: ● Key Figures Only are valid. ● All Characteristics Only characteristics are valid, but these have no restrictions. ● Block Characteristics Only Block characteristics are used to group the transaction data (see Without Blocks above) ● To-Be-Changed Characteristics Only Only characteristics that are changed by a planning function are valid. Block characteristics are therefore not valid. ● Condition Characteristics Only Only characteristics that are used in the planning function to define the condition are valid.
Data Selection	The selection criteria for multiple characteristics can be included in data selection parameters as they are needed to define the filters. This is a specific selection table. You define the characteristics that are valid for the data selection with Chars. Restriction: ● All Characteristics All characteristics of the InfoProvider are valid. ● Block Characteristics Only Block characteristics are used to group the transaction data (see Without Blocks above) ● To-Be-Changed Characteristics Only Only characteristics that are changed by a planning function are valid. Block characteristics are therefore not valid. ● Condition Characteristics Only Only characteristics that are used in the planning function to define the condition are valid.
Structure (Structure Parameter)	With a structure parameter you can declare other parameters as components of the structure parameter and thus combine them into a structure. Parameters of type Elementary, InfoObject of the InfoProvider and Data Selection are valid as components. To declare a parameter as a component, choose either Create Component in the context menu of a structure parameter or its components, or Properties → Structure Parameter in the context menu of another parameter.
Key Figure Selection	This parameter type selects the key figures to be processed. It is therefore a special case of the type InfoObject of the InfoProvider.

Example

The planning function types delivered by SAP are based on the same technical concept as the customer's own planning function types and can thus be viewed in the maintenance of the planning function types.

Example

The function type Delete (0RSPL_DELETE) is a simple example. There is only one parameter (KYFSEL) for selection of the key figures to be deleted. In the associated ABAP class, the interfaces IF_RSPLFA_SRVTYPE_IMP_CHECK and IF_RSPLFA_SRVTYPE_IMP_EXEC are implemented.