Migrating from a Classic Account Model into a New Model Type in SAP Analytics Cloud Planning

[former_member228880]

Introduction:

The introduction of the New Model type is bringing a new set of capabilities when designing planning applications.

The new model type offers much more possibilities and flexibility than a classic account model, allowing you to integrate both an account and multiple measures in a single model.

To benefit from these extended functionalities, you can convert your classical account model into a new model type using the button Migrate to New Model Type in the modeling area.

Migrating a Classic Account Model into New Model Type:

The below example shows the approach of Migrating a Classic Account Model into New Model Type (Model with measures and no account dimension).

 

Creation of a Classic account Plan Enabled Model based on File Source.

File Data & Fields:

Creation of Classic Account Model based on Source File.

Enrich the model by assigning right dimension type and with Version Mapping.

Assigning Version Mappings.

Finalize & Build the Model.

Enable Planning Option and Selecting Plan Date Dimension for the model.

Model Structure of Classic Account Model

Migrate Classic Account Model to New Model Type

Navigate to Model Structure and click on Migrate Option

Select Migrate Option (This action cannot be undone).

Upon successful Migration , Navigate to Model Structure area and find the new options of New Model Type.

 

Enrich the Data Model to be compatible with source file:

Signed Data will be the default measure and can be enhanced with additional measures to make compatible with Source file measures (Ex: QuantitySold , GrossMargin).

Remove the Account Dimension and Signed Data fields and Save the model.

Final Model Structure only with Required Dimensions & Measures.

Existing data also will be copied from Account based Model during Migration hence Delete the existing data from New Model and load again from same source file into New Model.

Select Import (File) option to upload data from source file.

Select the first job run to make set up import. The second job run was migrated as part of Classic account Model and no longer useful.

Prepare Data:

Validate all the Columns and their data types.

Map to Target:

Since both Source (File Structure) and Target (New Model) structures are same all the fields will get assign automatically or else manual default assignments need to perform.

Review Import:

Final Data Load Status:

Data load jobs can be scheduled further based on source of New Model type.

Conclusion:

Please be noted below points before Migration of Account Model to New Type Model.

• The migration is not possible if your classic account model has dependent objects or if the currency conversion is turned on.


• If your classic account model has currency conversion enabled, you need to turn it off before migrating the model.


• The new model is created with the currency conversion turned off.


• Then it's up to you to turn it on again and redefine the currency conversion measures in your target model.


• The migration cannot be undone.


• Data import/export job of the new model type is not compatible with the old import/data import job for a classic account model.


• Therefore, there is no migration from old job type to new job type. Job scheduling based on future execution no longer exist, but previous job execution history can still be observed.


• So, after the conversion you will have to create new data import/export job for the new model type.