Importing Transaction Data

Watch this short video to take a closer look at the next phase of your integration project: creating a hybrid profit center planning solution. You have created your model and now you must do the initial transaction data import from SAP Business Warehouse.

Data acquisition limits for new models:

• Non-SAP Data Center Platform: 1,000,000,000 cells, 1000 columns.
• SAP Data Center Platform: 10,000,000 cells, 1000 columns.

As with importing master data, you can restrict the transaction data that is imported by applying filters in the import query. When importing transaction data, it's common to filter year and period.

In the Map to Facts step, keep the following in mind for transaction data imports:

1. The version defaults to Actual. You can switch to a different public version by remapping the dimension.
2. Generic and organization dimension types can use a member as a default or # (unassigned).
3. It is possible to import multiple measures. For example, you can import local amount, group amount, and quantity in the same import.

The date settings can be adjusted in the Map to Fact step by selecting Review Settings.

In the Mapping Summary tab, you can change Mapping and Preferences.

In the Mapping

1. Map by Date: Choose this option if your source data is a calendar date. The system finds the date dimension member that matches this date and import data to it.
2. Map by ID: Choose this option if your source data is fiscal shifted, or similar to the date dimension ID member. If your source data does not match the date dimension ID member, pick a format for the source data.

In the Preferences section, you can select Apply fiscal settings to column values. This allows you to pick a format for the incoming data, such as Same as Target Dimension (YYYYPP) or YYYY.PP.

In the Fiscal Settings tab, you can view the time settings for the model. For example, which periods are included in the fiscal year and the starting period for the year.

When you select Run Import, a dialog provides an overview of the data that is being imported. You can change the settings at this point, if required.

In the Import Settings, you can update:

1. Import Method: When data is imported multiple times for the same data region, the update method is used to control the data update. These options are covered in detail in the Importing and Wrangling Transactional Data in a Model, linked at the beginning of this lesson.
2. Reverse Sign by Account Type: Use this option if the source data does not have the correct sign. For example, activate this option if revenue is stored as a positive value in the source system.
3. Update Local Dimensions with New Members: Use this option to update private dimensions during the transaction data import.

If Validation Settings is enabled, you may select which hierarchies to validate against. Validating against selected hierarchies prevents data from being imported to non-leaf members.

After you run an import query and the data is in SAP Analytics Cloud:

• Import query selection and data source can be changed for a model.
• Import query selections for dimensions can be changed.
• Import query filters can be changed for both models and dimensions.

From the Data Management Workspace, it is possible to access a More actions menu, allowing you to refresh, edit, or delete the import job.