---
title: "Creating and Configuring Planning Data Levels"
description: "Planning data levels are used for recreating your corporate planning. With the aid of planning data levels, you can create not only the general planning but also scenarios and forecasts."
source_url: https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/create-configure-planning-datalvls
language: en
last_updated: 2023-08-16
---
# Creating and Configuring Planning Data Levels

## Overview

Planning data levels are used for recreating your corporate planning. With the help of planning data levels, you can create not only the general planning but also scenarios and forecasts.

There is exactly one actual data level and up to 254 planning data levels with different descriptions. The planning data levels are based on the actual data level. This means the opening balance sheet of the planning data level corresponds to the closing balance sheet of the actual data level.

## Creating Planning Data Levels

To create a planning data level:

{% stepper %}
{% stepper-step %}
Right-click the **Data levels** root folder.
{% /stepper-step %}
{% stepper-step %}
Choose **Create | Planning data level level** from the context menu.

{% /stepper-step %}
{% /stepper %}
The following options are available in the **Create Planning Data Level** dialog:

Create a planning data level

#### Element name

Name of the element

#### Template

Existing planning data levels as templates:

- Keep the default setting if you want to adopt **planning data, planning wizards**, and **accounting rules**.
- Select **Planning wizards and accounting rules** or **Accounting rules only** to restrict the scope of the data to be transferred accordingly.

{% info-box %}
No data is transferred for elements of type **Group**.
{% /info-box %}

#### Period

**Start** and **end period** of the data level

{% warning-box %}
If you specify a template and then change the period, only the data of the template data level that is in the selected period will be copied.
{% /warning-box %}

## Configuring Planning Data Levels

When configuring a data level, the following options are available:

Editing a planning data level

#### Period

**Start period** and **end period** of the data level

#### Data level closed

The planning data level can be closed in order to block an entire data level against postings. This prevents plannings from being inadvertently altered afterwards.

#### Data level archived

Planning data levels can be archived in such a way that they cannot be selected in the dimension bar. This is useful when outdated plannings are retained but should no longer be visible.

{% info-box %}
You can cancel the archiving at any time by deactivating the check box.
{% /info-box %}

### Planning Data Level Status

Each planning data level has one of the following statuses, whicg is shown on the **Status** tab.

#### Data level is synchronized with the actual data level ()

This data level is synchronised with the actual data level. Furthermore, all periods before the start of this data level are closed in the actual data level. This ensures that the actual data level can no longer be changed before the start of this data level, meaning that the planning data level would no longer be synchronized with the actual data level.

#### Open periods in the actual data level before the start of the planning data level ()

Periods prior to the start of the planning data level are open in the actual data level. It is possible that the actual data level can be changed before the start of the planning data level, meaning that the planning data level would no longer be synchronized with the actual data level.

{% info-box %}
Open the **Period locks** workspace to close the open periods of the actual data level. Please note that you can only view, create, and/or edit period locks if you have the appropriate permissions (see [Defining User Permissions for Data Model Roles](https://support.lucanet.cloud/en/documentation/administration/user-management.md)).
{% /info-box %}

#### The planning data level is not synchronised with the actual data level ()

Since the creation or since the last synchronization, changes have taken place in the actual data level before the start of the planning data level. To transfer the changes to the planning data level, the planning data level must be synchronized.

{% info-box %}
The data level can be synchronized at any time with the actual data level (see [Synchronizing Planning Data Levels](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/platform-dimensions/data-levels/synchronize-planning-data-level.md)).
{% /info-box %}