Planning Level

Technical name

Visible in the UI (Whether and Where)

Description

MCB: Data basis (history-based)

4MCBL030

No

Behind both of these planning levels are functions with which the data can be copied into the planning cube for further processing (cube copy function).

MCB: Data basis (zero-based)

4MCBL020

No

Planning Level

Technical name

Visible in the UI (Whether and Where)

Description

Budget specification

4MCBL015

Yes

You can find this planning object in the Web UI in the Total Overview (graphic).

Total budget proposal (Manager)

4MCBL014

Total budget proposal (Planner)

4MCBL009

Manager: Distribution of the budget

4MCBL038

Yes

You can find this planning object in the Web UI in the Manager Scenario.

Manager: Comparison of the budget

4MCBL017

Maintenance plan: Basis

4MCBL001

Yes

You can find this planning object in the Web UI in the zero-based scenario under Maintenance Plans.

Maintenance plan: Hierarchy

4MCBL010

Maintenance plan: Period-exact

4MCBL034

Maintenance plan: Distribute data to periods

4MCBL036

Task list: Basis

4MCBL002

Yes

You can find this planning object in the Web UI in the zero-based scenario under Task Lists.

Task list: Hierarchy

4MCBL011

Task list: Period-exact

4MCBL003

Ad-hoc: Basis (planned)

4MCBL004

Yes

You can find this planning object in the Web UI in the zero-based scenario under Ad hoc (Planned).

Ad-hoc: Hierarchy (planned)

4MCBL012

Ad hoc:Period-exact (planned)

4MCBL005

History-based: Basis

4MCBL006

Yes

You can find this planning object in the Web UI in the history-based scenario under History-Based.

History-based: Hierarchy

4MCBL013

History-based: Period-exact

4MCBL008

History-Based: Distribute data to periods

4MCBL037

Ad hoc: Basis (Hist)

4MCBL044

Yes

You can find this planning object in the Web UI in the history-based scenario under Ad hoc (Hist.).

Ad hoc: Hierarchy (Hist)

4MCBL042

Ad hoc: Period-exact (Hist)

4MCBL045

General functions

4MCBM021

Yes

You can find this planning object in the Web UI in the both scenarios under Functions.

Submit for approval: Initial

4MCBL030

Yes

This planning object is used in global planning sequences.

Submit for approval: I

4MCBL031

Submit for approval: II

4MCBL032

Reject approval

4MCBL033

Genehmigen

4MCBL035

No

Cost type distribution

4MCBM036

No

Global Planning Sequences

Technical name

Description

Flexibility when distributing the periods: Equally over twelve periods or by reference dates

Determine period distribution for the history-based scenario

History-Based: Distribute data to periods (STS)

4MCBSTS4

The distribution to reference data is provided. To convert, you must change the planning function and the parameter group.

For the status and tracking service (STS) the planning functions refer to the version sent for approval.

History-based: Distribute data to periods

4MCBPS02

The distribution to reference data is provided, to convert, you must change the planning function and the parameter group.

Here the planning functions refer to the current planning version of the planner in the Web UI.

Compilation of functions into corresponding groups

Prepare automatic period distribution

Total period distribution (STS)

4MCBSTS6

Here all the STS period distribution functions are linked with one another. The planning functions refer to the version sent for approval.

Total period distribution

4MCBPS06

Here all the period distribution functions are linked with one another. The planning functions refer to the current planning version of the planner in the Web UI.

Cost type distribution for approved version

Cost type distribution

4MCBPS01

All the cost type distribution functions for the approved version are compiled here.

Global planning sequences that are used in the Web UI or in the STS.

Submit data for approval

Submit for approval: (STS)

4MCBSTS1

This sequence contains the period distribution and creates the manager's data.

Submit for approval

4MCBPS03

This sequence contains the following functions:

·        A status check, whether the submitting is allowed

·        The period distribution for the Web UI

·        A copy function of the current planner data from the current version into the version sent for approval

·        A create function for the data of the version sent to the manager for approval

·        A function that changes the status

Reject approval depending on the planner

Reject approval planner 1 (STS)

4MCBSTS3

This sequence is supplied empty. If you are using the STS, you must define this global planning sequence yourself.

Reject approval

4MCBPS04

This sequence contains the following functions:

·        A function that sets the check functions to o.k.

·        A copy function of the version sent for approval into a rejected version

·        A deletion function for the version sent for approval (in relation to manager data)

The data is defined in the Web UI through the determination of the corresponding variable. (In the manager scenario, the manager can select the planner for whom he or she rejects the data.)

Global planning sequences that are executed from transaction BPS0 or only by the highest-level manager     

Last step: Approve everything

Approve: Everything (STS)

4MCBSTS2

This sequence copies all the records of all the planners of the version sent for approval into the approved version.

Then all the data is available in detailed form. In addition, cost types are automatically distributed for the approved version.

Approve: Everything

4MCBPS05

This sequence copies all the records of all the planners of the version sent for approval into the approved version. Then all the data is available in detailed form. In addition, cost types are automatically distributed for the approved version.