BI-IP tables Table RSPLF_SRV RSPLF_SRV_COND RSPLF_SRV_CU RSPLF_SRV_P RSPLF_SRV_PS RSPLF_SRV_TI RSPLF_SRVT RSPLF_SRVTYPE RSPLF_SRVTYPE_D RSPLF_SRVTYPE_P RSPLF_SRVTYPE_PT RSPLF_SRVTYPE_PV

RSPLF_SRVTYPET Description Planning Service Rule Condition in Planning Service Characteristic Usage Parameter Value (Elementary Type) Parameter Value (Selection Type) Index: Associated TLOGO Objects Text Table for Planning Service Definition of Planning Service Dialog Information Parameter Definition for Planning Service Text Table for Parameter Definition&nbsp Maintenance View for Parameter Definition Text Table for Definition of Planning Services

Tables for planning sequences: Table Description RSPLS_SEQUENCE Planning Sequence RSPLS_SEQUENCE_S Planning Steps RSPLS_SEQUENCET Texts for Planning Sequences Tables for aggregation levels: Table Description RSPLS_ALVL Planning: Primary Table for Aggregation Level RSPLS_ALVL_IOBJ Planning: Aggregation Levels for InfoObjects RSPLS_ALVLT Planning: Text Table for Aggregation Level Tables for data slices: Table Description RSPLS_DS Data Slices RSPLS_DS_FIELD Data Slices: InfoObejcts with Restrictions RSPLS_DS_HEAD Data Slices: Header Table RSPLS_DS_RANGE Data Slices: Selection RSPLS_DST Text Table: Data Slices Characteristic Relationships :

You use characteristic relationships to link characteristics that have similar content. You can use characteristic relationships to define rules to check permitted combinations of characteristic values for real-time InfoCubes. You can also define rules for the system to use to derive values from one characteristic for another characteristic. This is useful, for example, if you want the derivable characteristics to be available for further analysis. You can define characteristic relationships for the master data of a characteristic (type attribute), a hierarchy (type hierarchy), a DataStore object (type DataStore) or an exit class (type exit). Data Slices Data slices are a concept for protecting the main data of a real-time enabled InfoCube against changes. This protection affects input-ready queries and all planning functions that use this InfoCube. If you want to ensure that certain plan versions can no longer be changed after a certain point in time, for example, and current data is not overwritten, you can use a data slice that contains these plan versions. Aggregation Level Aggregation levels are used as InfoProviders for planning: with an aggregation level, you model levels whose data can be changed manually using input-ready queries or automatically using planning functions. An aggregation level is set using a set of characteristics and key figures from the underlying InfoProvider. The key figures included in the aggregation level are aggregated using the characteristics that are not included in the aggregation level. Filters : Filters are used in reporting, analysis and planning, for example, to restrict data to a certain business area, certain product groups or certain time periods. You segment data in this way so that users or user groups only have access to the data that is relevant to them In planning functions, a filter on the characteristic restrictions describes the data for which a planning function is executed. Filters in Queries, The values defined in the characteristic restrictions restrict the data that is available for further filtering at runtime of a query. You cannot apply a filter to a characteristic value that is not included in this value set.

Planning Functions : Planning functions are used within BI Integrated Planning for system-supported editing and generation of data. A planning function specifies the ways in which the transaction data for an aggregation level can be changed you a number of standard planning function types: Unit conversion You use the Unit Conversion function type to convert units of key figures into other key figures using unit relationships. Generate combinations

You use the Generate Combinations function type to generate empty records for an aggregation level. The empty records are generated for all permitted combinations using the master data and characteristic combinations. Formula

The planning function type Formula provides you with a simple programming language for manipulating transaction data. in BI Integrated Planning the name of the key figure is always part of the operand. Copy

You use the Copy function type to copy the key figure values from existing characteristic combinations to other characteristic combinations. Delete

You use the Delete function type to delete the key figure values for the selected data records. Delete invalid combinations

You use the Delete Invalid Combinations function type to delete all key figure values for all records whose combination of characteristic values does not correspond to the characteristic combinations that are defined for the underlying real-time InfoCube.

Note the following condition: A planning function of this type can only be created on an aggregation level that itself has been created directly on a real-time. The aggregation level has to include all the InfoObjects of the InfoCube that are valid in aggregation levels. Forecasting

You use a forecast procedure to predict the future development of key figure values. The default planning function type Forecasting of BI Integrated Planning offers a number of strategies and statistical methods for calculating forecasting values for the future from historical data. Repost

You use the Repost function type, like the Copy function type, to post the key figure values for existing characteristic combinations to other combinations. In contrast to copying, the key figure values for the From values are deleted Repost by characteristic relationships

You use the Repost by Characteristic Relationship function to repost transaction data so that it is consistent with the characteristic relationships. The original records are deleted and reposted to the correct characteristic combinations. A planning function of this type can only be created on an aggregation level that itself has been created directly on a real-time InfoCube (a simple aggregation level, see Aggregation Level). The aggregation level has to include all the InfoObjects of the InfoCube that are valid in aggregation levels. Revaluation

You use the Revaluation function type to increase or decrease key figures by a percentage figure. Distribute by reference data You use the Distribution by Reference Data function type to generate combinations of characteristics that correspond to the reference data. The system distributes data in accordance with these combinations. The key figure values are distributed by percentage in accordance with the reference data. Distribute by key You use the Distribution by Key function type to generate the characteristic combinations to which data is distributed in accordance with the master data and characteristic relationships. The key figure values are distributed according to the expressly specified distribution keys. These are distribution functions that determine the weighting of the distribution.

Currency translation

You use the Currency Translation function type to convert currencies of key figures into other key figures. Standard key : The standard key date is a key date that is used in the entire planning model. It can be set for every real-time enabled InfoCube in the characteristic relationships.

Planning functions can be executed directly from a Web application or a BEx workbook. However, you have to enable this in the relevant design tool first. To execute a planning function in the Planning Modeler, you have to include it in a planning sequence (see Planning Sequences). In the last step of the Planning Wizard you create a temporary planning sequence. This contains exactly one planning function. Before the planning function is executed, the system checks whether the planning function is consistent. Planning Sequences: Planning sequences are used within BI Integrated Planning to group planning functions. They allow you to save groups of planning functions in a sorted sequence and execute groups of planning functions sequentially. By integrating planning sequences into process chains, you can execute planning sequences in the background. You can include a planning sequence in a process chain by including a process of process type Execute planning sequence in an existing process chain. Planning Sequence for Bottom-Up Planning Variables : Variables are used to parameterize a query, a planning function, a filter, a characteristic relationship or a data slice. When a query, planning function or Web application is executed, they are filled with values.

Lock Concept and Lock Management When a user requests transaction data in change mode, this data has to be locked exclusively for the user. The data records that have to be locked are specified in a selection table. A data record is locked by the selection table if for each characteristic in the selection table, the characteristic value in the data record lies within the selection. It does not matter whether this data record is on the database. The following rules apply: All the records in the selection are locked. If the selection table is empty, each data record is locked since no restrictions exist. For characteristics outside the aggregation level, selection * (all) is always locked.