Summary

This document describes how Financial Planning can be implemented with BusinessObjects Planning and Consolidation connected to SAP S/4HANA Cloud. Master data and actual data from the Universal Journal in S/4HANA Cloud are replicated into a On-Premise customer system and can be used within the BusinessObjects Planning and Consolidation.

 

 

Table of Contents

Business Scenario

Prerequisite

SAP S/4HANA Cloud

Your BW on premise system

General disclaimer

Step-by-Step Procedure

Step 1: Create communication scenario

Step 2: One-time activation of data sources in the S/4 HANA Cloud

Step 3: Establish the Connection from BW

Step 4: Create DataSources in your BW system

Step 5: Create data target objects

Overview of data flow

InfoObjects

Data Store Object for actuals data

InfoProvider for actuals data

InfoProvider for BPC planning data

MultiProvider for combined actuals/planning data reporting

Aggregation level

Step 6: Create Transformations for data target objects

InfoObjects

Data Store Object for actuals data

InfoProvider for actuals data

Step 7 Create Data Transfer Processes

Master Data

Transactional Data

Step 8 Set up planning query

Step 9 Enter planning values

Copyright

 

 

 

Business Scenario

The business scenario described in the example based how to guide “SAP Business Warehouse Integration for Planning and Consolidation in SAP BusinessObjects Planning and Consolidation” allows you to extract data from the S/4 HANA Cloud System to your on premise BW. This enables you to use this data within your financial planning with BPC.

This document describes how to

  • setup a communication scenario to allow the extraction from S/4 HANA Cloud to BW on premise
  • align with SAP Cloud Operations to do a one-time release and activation of selected financial DataSources in S/4 HANA Cloud
  • setup the ETL processes in your BW on premise system necessary for financial content
  • setup the data and BPC planning model in your BW on premise system
  • setup consolidated reporting for plan and actuals data in your BW on premise system

This how-to guide is based on and refers to the technical documentation delivered with the scope item SAP Business Warehouse Integration for Planning and Consolidation in SAP BusinessObjects Planning and Consolidation (1VG) that explains how to establish the connection. It then dives deeper into the business scenario in BW/BPC, beyond the technical connectivity that is the focus of the scope item.

The how-to guide thus aims to give you an understanding how you can use the connectivity option to enable your planning in BPC.

 

 

Prerequisites

 

SAP S/4HANA Cloud

You need a user with administrator privileges for the SAP S/4HANA Cloud system that you want to integrate with your BW. In particular, the permissions of the catalog SAP_CORE_BC_COM (Communication Management) are required in order to access the SAP Fiori applications for managing the communication arrangement.

Your BW on premise system

You need a user with the permission to create source systems and create analytical objects in your BW. The integration has been tested with BW version 7.40 and above.

General disclaimer

The How-To Guide is not a detailed step by step description and assumes that an experienced BW Modeler and/or BPC expert is executing the steps. Furthermore, the How-To Guide only describes a simple example with a limited amount of master and transaction data. Screenshots shown in the documents are only one possible way of setting up the BPC integration in a simplified way. Specific customer related requirements are not covered in the How-To Guide.

 

 

Step-by-Step Procedure

 

Step 1: Create communication scenario

Communication scenarios are the basis for all inbound and outbound communication with the S/4 HANA Cloud System. Any kind of integration must be based on a communication scenario.

The customer guide accompanying the scope item SAP Business Warehouse Integration for Planning and Consolidation in SAP BusinessObjects Planning and Consolidation (1VG) describes how to create such a communication arrangement. It is necessary to enable the integration between the S/4 HANA Cloud System and your BW on premise system.

You can find the customer guide and all further scope item documentation in the SAP Best Practices Explorer.

 

Step 2: One-time activation of data sources in the S/4 HANA Cloud

You need to create a ticket to request that SAP releases and activates the DataSources for the integration of SAP Business Warehouse / SAP BusinessObjects Planning and Consolidation. This step is mandatory to be able to extract data from the DataSources.

A template for the customer message to SAP can be found in the customer guide and all further scope item documentation in the SAP Best Practices Explorer.

 

Step 3: Establish the Connection from BW

To connect from BW (7.40 or higher) to S/4HANA Cloud, you establish a connection using Operational Data Processing (ODP) via the WebService communication channel (SOAP via HTTPS).

You can find the customer guide and all further scope item documentation in the SAP Best Practices Explorer.

 

Step 4: Create DataSources in your BW system

Note that the DataSources need to be created manually in BW because a replication of metadata is not supported by the Web Service. The test script accompanying the scope item SAP Business Warehouse Integration for Planning and Consolidation in SAP BusinessObjects Planning and Consolidation (1VG) describes how to create such a data source. You can find the test script and all further scope item documentation in the SAP Best Practices Explorer.

The list of the available DataSources to be created can be found in the customer guide and all further scope item documentation in the SAP Best Practices Explorer as well. You need to create attribute, text and hierarchy data sources for all of the InfoObjects that are used in the following.

 

Step 5: Create data target objects

Overview of data flow

There is currently no SAP delivered BI content available for the data source 0FI_ACDOCA_10 (Unified Journal Entry). You need to create a DSO and an InfoCube according to your need. For further details please refer to note 2341038.

In the overview you can find an example of setting up the data flow:

From the S/4 HANA Cloud source system (here: CC2 Client 715) transactional data is getting extracted through the DataSource for the Unified Journal Entry (0FI_ACDOCA_10).

The transactional data is then getting transferred into a DataStore Object. Afterwards the transactional data is getting aggregated into the InfoCube for keeping track of the actual Unified Journal Entries.

Additionally, it is necessary to create a real-time planning cube allowing the data storage of planned data.

On the aggregation level the data model for the planning is getting defined.

Finally, on the MultiProvider you can enable the reporting on combined plan and actuals data.

 

InfoObjects

It is assumed that the necessary objects such as InfoObjects are already activated in your BW system.

 

Data Store Object for actuals data

In order to work with 0FI_ACDOCA_10 you have to setup a DSO with overwrite mode (to process also document changes, clearings and reversals correctly) with the key fields as shown below.

 

 

InfoProvider for actuals data

Please find an example setup of the InfoProvider for the actuals data below.

 

 

InfoProvider for BPC planning data

Please create a Real Time InfoProvider for storing the planned data coming from BPC. You can use the InfoProvider for actuals data as a reference. Please ensure that the flag ‘Real Time’ is activated:

 

 

 

MultiProvider for combined actuals/planning data reporting

Please create a MultiProvider consisting of the InfoProvider for actuals data and the InfoProvider for plan data.

 

 

 

Aggregation level

To allow the entry of planning data you need an aggregation level. Here you define the model levels whose data can be changed manually using input-ready queries. The below shown aggregation level is based on the MultiProvider created in the previous step.

 

 

 

Step 6: Create Transformations for data target objects

InfoObjects

Please find an example for a transformation from the DataSource 0GL_ACCOUNT_ATTR to the target InfoObject 0GL_ACCOUNT – G/L Account. For all other master data DataSources you have to create the transformation as well.

Enter the following values:

The following 1:1 transformation rules for source and target fields are getting defaulted:

Optional: in the example above the Source System has been set to a constant value.

 

 

 

Data Store Object for actuals data

You have to create the transformation for the data transfer from the extraction with DataSource 0FI_ACDOCA_10 to the DSO and from the DSO subsequently to the InfoProvider for actuals. Please consider that the screenshot below shows the Metadata view with regards to the source/target field assignment as a simplified view for the data transfer.

 

Please ensure that the aggregation behavior for key figure ZBPC_KSL in the example above is defined as ‘Overwrite’.

 

InfoProvider for actuals data

You have to create this transformation from the DataStore Object into the InfoProvider for actuals. Additionally, you also enable an aggregation of data, if required.

 

Step 7 Create Data Transfer Processes

 

Master Data

Please find an example for a data transfer process from the DataSource 0GL_ACCOUNT_ATTR to the target InfoObject 0GL_ACCOUNT – G/L Account. For all other master data DataSources you have to create the data transfer process as well accordingly.

It is recommended to use the full update for small amounts of data to be transferred.

 

 

 

Transactional Data

The extraction of the transactional data with the DataSource 0FI_ACDOCA_10 requires multiple steps as follow:

  1. Load initial data via InfoPackage into PSA
  2. Transfer the data from PSA into the DSO with subsequent activation of the DSO data
  3. Transfer the data from the DSO into the InfoProvider
  4. Optional: Create a process chain to cover all upload steps

 

  1. Load initial data via InfoPackage into PSA

Create an InfoPackage with the following parameters:

Please define your data selection as to your needs. Please consider that subsequent uploads have to be handled via an InfoPackage in delta update mode.

 

 

 

  1. Transfer the data from PSA into the DSO with subsequent activation of the DSO data

Create a Data Transfer Process from the PSA of DataSource 0FI_ACDOCA_10 to the DSO.

Please ensure that the delta mode is active and that the parameter from PSA is set.

Afterwards trigger the activation of the DataStore Object data by position the cursor on the DataStore Object in the Data Warehousing Workbench (RSA1) -> right click -> Activate Data.

 

 

  1. Transfer the data from the DataStore Object into the InfoProvider

Create a Data Transfer Process from the DataStore Object to the InfoProvider.

Please ensure that the delta mode is active.

 

 

 

Optional: Create a process chain to cover all upload steps

Please find an example for a process chain which can be scheduled then on a regular basis:

 

 

Step 8 Set up planning query

Open the Business Explorer Query Designer and define your query based on the aggregation level created under step 5. Here is an example:

 

Please ensure that the Change Data radio-button for the Key Figure you would like to use is set to ‘Input-ready (Relevant for Locking)’ to allow planned data entry.

 

 

Additionally, please ensure that the query is getting started in change mode. You can define this parameter as shown below in the query properties:

 

Step 9 Enter planning values

Please open the SAP BusinessObjects Analysis (Edition for Microsoft Office) and open up the query created under step 8. Here you can enter you planned values:

 

Optional: You can also create a more comprehensive reporting query combining more details about the planned and actuals values including additional reporting dimensions. Please find an example below including the profit center reporting dimension:

 

 

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply