CL_RSPLFC_BPS_EXITS - Wrapper for BPS ExitsBAL_S_LOG - Application Log: Log header data General Data in Customer Master
This documentation is copyright by SAP AG.
This class is delivered as an implementation of a planning function type in BI Integrated Planning. It allows you to reuse function modules of type Exit in BI Integrated Planning that were written for planning functions in BW-BPS or SEM-BPS.
Note that the old BPS planning functions themselves are not called; the BI Integrated Planning data is filled in the corresponding tables of the function module interfaces and these function modules are called directly. This means that BPS objects (for example the data buffer) are not used. Due to the specific requirements of the interfaces and the fact that BPS objects are not used, there are certain limitations which have to be taken into account for the planning function types that are realized.
This class assumes that the names of the function modules are transferred in two elementary parameters with fixed definitions. The names of the parameters are defined in constant P_C_NAME_EXIT_PARAM and P_C_NAME_INIT_PARAM. The class recognizes additional parameters generically - therefore this class can be used as the implementing class for various planning function types. The planning function types can define additional elementary parameters for the predefined parameters. The class recognizes these additional elementary parameters automatically and passes them on to the exit parameter table of the function module.
The class is realized in such a way that conditions can be used - you can even specify a record of the function module for each condition. The function module for the exit always has to be filled; the function module for the init module is optional.
If you want to use the class as in a planning function type, proceed as follows:
1. Create an InfoObject that accepts the name of the function module as a characteristic value. We recommend that you create an InfoObject of type character with length 30 and indicate that this InfoObject is "Without Master Data".
2. In transaction RSPLF1, create a new function type. Chose the "Reference Data" option and enter the name of the class. This does NOT imply that reference data is read automatically, but results from the requirements for implementing the class.
3. On the "Parameter" tab page, create two parameters - one for the exit module and one for the init module. The parameters should be "elementary". Chose the InfoObject you created in step two as the dedicated InfoObject. The names of the parameters are determined from the values of constant P_C_NAME_EXIT_PARAM and P_C_NAME_INIT_PARAM.
4. If you require additional parameters in your function module (called exit parameters), you create these parameters as elementary parameters (with appropriate InfoObjects). Note an additional predefined parameter here - in many function modules, the name of the area is used from which the module is called. The area is not used in BI Integrated Planning but it may be the case that an area was created in BPS which only uses the current InfoCube. For this reason, you can create a parameter with the name specified in constant P_C_NAME_AREA_PARAM by specifying the name of this area to the function module. The value of this parameter is passed on to the function module in the interface as the value of the importing parameter I_AREA. Note that this technology can generally only by used for Basis InfoCubes and simple planning areas (not multi- planning areas or MultiProviders).
You can create additional elementary parameters as long as the names do not correspond to the predefined names. The class automatically recognizes the additional parameters and transfers them to table IT_EXITP in the function modules.
5. After you have activated the planning function type, you can create planning functions and fill the parameters accordingly.
In addition to the information given above, note the following limitations when using this class:
Note that the function modules are called from the environment of BI Integrated Planning. This may lead to an unexpected system response when you try to access objects in the BPS environment from these function modules, for example, while reading the values of BPS variables or reference data over the BPS-internal interfaces. In particular, the values of the importing fields such as area (see above), planning level, methods, parameter group and package are not recognized in the function modules that you call. You may also get unexpected results when you call the BPS API.
Note that filter selections in BI Integrated Plannig can be formulated more generally (with exclusions, for example). The selection is passed on to the function module in this form. If coding is written for this selection in the function module, the coding has to be modified as appropriate.
The procesdure for creating a planning function type with this class is also described in a How to Paper.
CL_GUI_FRONTEND_SERVICES - Frontend Services BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 5228 Date: 20191113 Time: 104055 sap01-206 ( 42 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.