Importing Master Data

Now that you have viewed your source accounting and group reporting master and transaction data, it's time to import the master data into SAP Analytics Cloud for your team's hybrid planning solution.

Watch the following video to find out more about the master data import process.

To import master data from SAP S/4HANA, import queries are created in the SAP Analytics Cloud dimensions using CDS views.

There are a few key points to note:

• In this lesson, we will use delivered CDS views. However, you can create your own CDS view, if needed.
• Depending on the source dimension, several import queries may be needed to import the members, text, and hierarchy data. We will use five import queries for accounting master data and three for group reporting master data.
• Only one hierarchy can be imported per import query.
• You can run import queries as you need them, or you can schedule them from the dimension or from a model that includes the same dimension.
• Multi actions can be set up to run import queries.
• In the Query Batch Size dialog, you can change the number of records per batch that are retrieved during the import. The default is set to the maximum value of 50,000 records; however, you can lower this number if needed.

Generic and organizational dimensions in SAP Analytics Cloud include an unassigned member with ID # as you can see in the following example of the Dimension Workspace.

However, unassigned members are not available for the account, date, and version dimensions.

When records are imported into models, irrelevant dimensions use the unassigned member. For example, when importing income statement data, revenue records do not contain a value for cost center (because cost center is only relevant for expense). In this case, as displayed in the following example, the unassigned member is used.

When you create an import query, you select the CDS view that includes the corresponding SAP S/4HANA dimensions that you require. For example, if you are importing data into the SAP Analytics Cloud account dimension, then you need to select the CDS view that includes accounts.

When you import G/L account master data members, properties, text, and hierarchies, you need to create five import queries:

1. Members and Properties
2. Descriptions
3. Hierarchy Parent Nodes
4. Hierarchy Parent Node Descriptions
5. Hierarchy Leaf Nodes

After running the imports, the accounting master data values can be viewed in the SAP Analytics Cloud dimension.

We will use G/L accounts for the examples, but the import process for cost center and profit center follows the same steps: create your query, select the data to include, add any required filters, map and wrangle data, then run the import.

In the practice exercises in this lesson, you will cover the steps that you need to take to successfully import master data into an account dimension. However, you can tailor the import query creation to suit your own business requirements. For example, by using the Set Incremental Load button, you can specify the fields that should be checked for changes.

During the import, SAP Analytics Cloud will connect to your SAP S/4HANA system and compare those fields against the data that was previously imported. If a change is detected, then that record will be imported into SAP Analytics Cloud.

You import accounting master data members and properties into the SAP Analytics Cloud dimension using the relevant CDS view.

In the G/L Account example used in this lesson, the members and properties are imported into the dimension using the A_GLAccountInChartOfAccounts CDS view.

You import accounting master data descriptions into the SAP Analytics Cloud model dimension using the relevant CDS view.

In the G/L Account example used in this lesson, the descriptions are imported into the dimension using the A_GLAccountText CDS view, which is a delivered CDS view used for G/L Accounts.

In the G/L Account example used in this lesson, the hierarchy nodes and parent nodes are imported using the C_GLAccountHierarchyNode CDS view.

The G/L account, Hierarchy ID, will be inserted as a prefix for nodes and parent nodes to create unique nodes by hierarchy. The Hierarchy ID is the same as the Financial Statement Version ID.

In the example used in this lesson, the SACAccountType is used to populate account type property. It includes the following selections:

• G/L Account Hierarchy
• Node
• Parent Node
• SACAccountType

There can be several versions of an FSV present, so it would be best to use the Validity End Date and Validity Start Date fields to narrow down to one version of the FSV.

The FAGL_011TC table shows the last changed date for the FSV items. You can run the query in SAP Analytics Cloud and include the Hierarchy ID in the filter and put the Validity Start Date and Validity End Date in the Selected Data. With the results, you can determine how you would like to set the validity filters.

A financial statement version is assigned to one specific chart of accounts, so you should not specify the chart of accounts during the loading of nodes or node texts.

Whenever a change to an account hierarchy (financial statement version) has been made in SAP S/4HANA, the hierarchy may need to be replicated to the HRRP tables so that SAP Analytics Cloud can access it.

The SAP S/4HANA transaction code for this is HRRP_REP (as an alternative transaction, SA38 or SE38, may be used with program, FINS_REPLICATION_HIER_N).

In the G/L Account example used in this lesson, the leaf nodes are imported using the C_GLAccountHierarchyNode CDS view.

In the G/L Account example used in this lesson, the hierarchy node descriptions are imported using the C_GLAccountHierarchyNodeT CDS view.

In this lesson, we will use the delivered CDS views that are included in SAP Analytics Cloud, however, remember that it is possible to create custom CDS views to meet your business requirements should they be required.

The exercises are designed to take you step-by-step through the group reporting master data process.

When you import group reporting FS Item members, properties, text, and hierarchies, you need to create three import queries:

1. Members, Properties, and Descriptions
2. Hierarchy Nodes and Descriptions
3. Leaf Nodes

After running the imports, the accounting master data values can be viewed in the SAP Analytics Cloud dimension.

In the FS Item example used in this lesson, the members, properties, and descriptions are imported using the FinancialStatementItem CDS view.

In the FS Item example used in this lesson, the hierarchy nodes and descriptions are imported using the FinancialStatementItemHier CDS view.

In the FS Item example used in this lesson, the leaf nodes are imported using the FinancialStatementItemHier CDS view.

After data is written to the database and the import query appears in the Data Management workspace.

In the following example, you can see all five of the import queries used in this lesson for importing accounting master data. If you were to open the Data Management workspace for the group reporting master data, then you would see three queries displayed.

When you select the import query, there are several options you can perform:

• Edit Query: Change the filter criteria for the import. Once the import has been run, accounting master data import query selections cannot be changed but filter values can be changed at any time. In the example below, you can see how to open the Edit SAP S/4HANA Query dialog with the Edit Query button.
• Schedule Settings: Schedule the import to run periodically. This is covered in detail later in the course.
• View Mapping and Transformations: Display the mapped columns as well as any transformations.
• Delete Source: Delete the import query (this does not delete the data from the dimension).

You can view and drill down into the imported hierarchies by selecting Toggle Hierarchies icon in the Dimension workspace.

In the following example, you can see that all the import queries have been run and all nodes and descriptions are in the dimension.