Importing Transaction Data

Objective

After completing this lesson, you will be able to import transaction data from SAP S/4HANA.

Transaction Data Import Process

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

Import Transaction Data

Importing transaction data is covered in detail in the Importing and Wrangling Transactional Data in a Model lesson in the Designing Data Models and Transforming Data in SAP Analytics Cloud learning journey.

Below, you will find some additional information related to creating an import query to suit your own business requirements when creating a hybrid planning solution.

Map Data

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). For example, the S4H_Audit dimension is fixed to the S4H member and the S4H_Flow dimension is fixed to the Ending member.
  3. It is possible to import multiple measures. For example, you can import local amount, group amount, and quantity in the same import.
Map to Facts with mapping options visible.

Review Date Settings

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 field, you can choose between:

  1. Map by Date: Choose this option if your source data is a calendar date. The system will find 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, which 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.

Map to Facts, Review Date Settings Dialog.

Run Import

When you select Run Import, a dialog provides an overview of the data that is being imported. It is possible to 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 lesson linked at the top 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 will prevent data from being imported to non-leaf members.

Change Settings selected in the Run Import dialog. Job Settings dialog on screen.

After you run an import query and the data is in the planning model:

  • 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.

Edit the Import Job

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

SAP Analytics Cloud Data Management Workspace with Import Jobs displayed.

View the Data

From the Model Structure workspace, it is possible to view the imported transaction data.

The model structure workspace open with Data Foundation table highlighted.

Note

Transaction data imports can be triggered in a Multi Action. For more information, see Configuring Multi Actions.

Import Accounting Transaction Data

Business Scenario: As part of the integration project, you need to import the accounting transaction data from SAP S/4HANA to use in your hybrid planning solution.

Task Flow: In this practice exercise, you will:

  • Create an import job in the Data Management workspace of the model
  • Build the query using the A_JournalEntryItemBasic CDS view
  • Select the required data and apply filters
  • Set up the import and wrangle data
  • Map the source and target data
  • Review the import and run the import
  • View the imported data in the Model Structure workspace
ExerciseStart Exercise

Import Group Reporting Transaction Data

Business Scenario: As part of the integration project, you need to import the group reporting (or consolidation) transaction data from SAP S/4HANA Finance for group reporting. You will use an OData Connection data source instead of a CDS view.

Some of your planners need to plan by consolidation unit and profit center revenue values that are net of intercompany transactions. However, you also have other planners who need to plan on revenue values that include intercompany transactions. To meet this requirement, the SAP Analytics Cloud model includes the following dimensions for consolidation unit and profit center.

In the following example:

  • The ConsolidationUnit dimension is used to access data that excludes intercompany transactions.
  • The CnsldtnUnitForElimination dimension is used to access data that includes intercompany transactions.
  • The Profit Center dimension is used to access data without inter-profit center transactions.
  • The ProfitCenterForElimination dimension is used to access data with inter-profit center transactions.
SAP Analytics Cloud model with dimensions for consolidation unit and profit center highlighted.

You have been provided with the following script to use to create a freehand query for the import job:

Code Snippet
12
GRTransactionData(P_ConsolidationUnitHierId='$',P_ConsolidationPrftCtrHierId='$',P_ConsolidationSegmentHierId='$',P_KeyDate=datetime'2023-01-01T14:49:52')/Results?$select=ConsolidationVersion,FiscalYearPeriod,ConsolidationLedger,ConsolidationUnit,CostCenter,ProfitCenter,Segment,ConsolidationUnitForElim,ConsolidationPrftCtrForElim,ConsolidationSegmentForElim,CustomerSupplierCountry,FinancialStatementItem,FinancialTransactionType,FunctionalArea,SubItem,FunctionalArea,PartnerConsolidationUnit,PartnerProfitCenter,PostingLevel,ConsolidationGroup,GLRecordType,PostingLevel,PeriodMode,ConsolidationDocumentType,GroupCurrency,LocalCurrency,AmountInGroupCurrency,AmountInLocalCurrency&$filter=ConsolidationVersion eq 'U00' and ConsolidationLedger eq 'Y1' and FiscalYearPeriod eq '012%2F2024' and PeriodMode eq 'PER' and ConsolidationGroup eq 'CG00W' and (GLRecordType ne 'R')

In the above script, note:

  1. The P_ConsolidationUnitHierId='$', P_ConsolidationPrftCtrHierId='$',and P_ConsolidationSegmentHierId='$' selections are set to $ because your team needs to plan on data net of intercompany eliminations. The $ selection denotes a blank hierarchy.
  2. P_KeyDate selects time-dependent hierarchy data.
  3. Several dimensions such as Consolidation Version and Fiscal Year Period are included in the data import.
  4. The filter values include consolidation version = U00 and so on.
  5. Local and group currency values are included.

Task Flow: In this practice exercise, you will:

  • Create an import job in the Data Management workspace of the model
  • Build the query using an OData Services data source, a group reporting connection, and a freehand query
  • Set up the import and wrangle data
  • Map the source and target data
  • Review the import and run the import
  • View the imported data in the Model Structure workspace
ExerciseStart Exercise

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn