## 2.1.3.2 Planning Data with SAP Analytics Cloud models
In Analysis, you can use live data connections and import data connections to connect with SAP Analytics Cloud data sources.
Live Data connection means that you're directly connected to an SAP BW or SAP HANA system via your SAP Analytics Cloud. When using live connections, you can use all options that Analysis offers for planning for these systems. The following chapter specifies the options you can use when planning with import data connections.
Import data connection means that you import (copy) data and save it in SAP Analytics Cloud. Changes made to the data in the source system don't affect the imported data until and unless the data is imported again, either manually or as a scheduled job.
You can enter the planning data manually in a crosstab in your analysis. To enter planning data, you can change the values in existing data cells in the crosstab and you enter planning data in empty cells (unbooked data cells) of the crosstab.
For entering planning data in unbooked data cells, be aware of the following behavior:
- If the dimension has hierarchies defined, but no hierarchy has been selected as display hierarchy (flat presentation), the unbooked cells are not input enabled.
- As hierarchy nodes are shown in the same way as leaves in a flat presentation, this check supports that you do not accidentally book values on hierarchy nodes.
- The data entry on an account with a specific account type is spread to only the accounts with a compatible account type. In SAP Analytics Cloud, you can select between the following account types for account dimensions: INC (Income), EXP (Expense), AST (Asset), LEQ (Liabilities and Equity) and NFIN (Non-Financial). Example for entering planning data in Analysis: The account dimension REVENUE is of type INC and has two children, INCOME of type INC and EXPENSES of type EXP. A data entry on an unbooked cell on REVENUE will only be spread to INCOME. This leads to the limitation that a parent account will not be input enabled if all the leaf accounts of its descendants have an incompatible account type. In theory, the following two groups of account types are compatible among themselves: (INC, AST) and (EXP, LEQ, NFIN). However, semantically meaningful combinations in a hierarchy will only combine INC and EXP or AST and LEQ accounts. So in a semantically meaningful model the value is spread only to leaf accounts of the same account type.
When inserting a cloud model for planning, the System for Data Write back field on the Components tab shows the SAP Analytics Cloud system as planning system. Cell locking for cloud model is always set to Front End Cell Locking .
When working with public versions, you can recalculate the planning data and you can save planning data to save it in the model.
On the Versions tab in the design panel, you can also copy the data of a version to create a new private version. The new private version is added to the crosstab and you can enter the planning data for the new version. When working with private versions, you can recalculate the planning data to save the data automatically in the model.
On the Versions tab you can also:
- Save a private version to publish the data and merge it with the corresponding public version.
- Select Save as for a private version and save it as a new public version.
- Undo and Redo steps executed in private and public versions.
- Share private versions with other users and grant them read or read and write access.
- Revert changes for a version to delete all changes executed for a version since the version was last saved.
- Delete a private or public version.