Importing SAP BPC Data to a New or Existing Model

Importing into a New Model

1. From the () Main Menu, select Create   Model.

2. Select Get data from a data source  SAP BPC.

   Note

   From the acquire data panel, select the filter icon to narrow down the number of data sources in the list. You can filter by data source type or by category.

3. To create a model from SAP BPC:

   1. Choose a BPC connection type and select a BPC connection from the list of connections.

      Note

      If the connection you select is an OAuth connection that you haven't authenticated, or your OAuth authentication has expired, then a dialog will pop up for you to enter your BPC credentials and complete the OAuth authentication process. If SSO is enabled, you can directly sign in without entering your BPC credentials again.

      You can also create a new connection on the fly by selecting Create New Connection and following the instructions in Import Data Connection to an SAP BPC System.

   2. Choose to create a new query or copy a query from an existing BPC model for mapping later.

      Click Next after completing all the settings on this page.

   3. On the next page, enter a Model Name for the new target model, and optionally a Description.

   4. If you want users to be able to write data back to the BPC model, choose Write-back model. Otherwise, choose the Basic model.

      In a write back model, transaction data is synchronized from time to time based on your model settings. Master data imported from BPC is read-only and cannot be changed.

   5. When the model type is Basic model, you can choose to create new dimensions as public dimensions or private dimensions.

   6. If you need to convert currency values, toggle on Currency Conversion. You can then either directly use an existing SAP Analytics Cloud currency conversion table, or import a currency conversion table from BPC.

      Note

      When currency conversion is enabled, only the local currency is imported from BPC. When currency conversion is disabled, all data values of local currencies and pre-converted currencies are imported without any currency unit.

   7. To create a new conversion table by importing it from BPC, select Add new table from current source from the Currency Conversion Table list. For detailed steps, refer to Import Currency Conversion Table From SAP BPC.

      Click Next after completing all the settings on this page.

4. In the next Select Model from BPC dialog, select an Environment and then select a Model.

   A name is automatically generated for the new BPC query, but you can rename it freely.

5. To build the BPC query you just created:

   1. If you have chosen a basic type model, drag dimensions from Available Data to the Selected Data area.

   2. To restrict the data to be imported, drag dimensions to the Filters area. Set a filter by selecting the filter icon. In the filtering dialog, select members to be included, and then select OK.

      Click Next after completing all the settings on this page.

6. In the dimension mapping dialog, map the source BPC dimensions to the corresponding new dimensions in SAP Analytics Cloud.

   1. Select a type for each dimension from the Dimension Type list.

   2. For the Category dimension, an additional Version Mapping dialog is displayed to let you map the BPC category names to the SAP Analytics Cloud category names.

   3. If you didn't toggle on the Currency Conversion setting in step 3, BPC's original data values are imported into SAP Analytics Cloud.

      In this case, if there's only a single currency used in your BPC system, you can select the Default Currency option and specify the currency; if different currencies are defined for different entities in BPC, you can select the option Local Currency is taken from:, and choose an entity attribute that defines the local currency.

   When you have completed the mapping, select Finish.

7. The new model is created with BPC imported data.

Importing into an Existing Model

About Synchronizing BPC Delta Data to SAP Analytics Cloud in a Write-back Model

By directly clicking the (Refresh) icon in the (Version Management) panel for the version that you want to refresh from BPC, you can bring back only delta data from BPC in BPC 10.1 NW on BW 750 and BPC 11.0, version for BW/4HANA.

Important Information:

• If you are using a BPC 10.1 NW on BW 7.50 version lower than SP09, make sure you first install the SAP Note 2504877 . Otherwise, full data will be loaded into SAP Analytics Cloud when syncing data.
• Syncing delta data to SAP Analytics Cloud is currently not supported in BPC 10.0 Microsoft version, BPC 10.1 Microsoft version, BPC 10.0 NW version and BPC 10.1 NW on BW740.
• Try not to activate BPC data on the BW DataStore Objects (advanced) or compress BPC data on the BW InfoCubes/InfoProviders at BPC side. Otherwise, the time-stamp information can be removed from the activated or compressed requests, and you might not be able to sync delta data from corresponding BPC model.

Performance Tips:

When synchronizing BPC delta data to a write-back model, it will retrieve data calculated by BPC member formula by default. This may bring extra performance burden.

To overcome this issue, we recommend you set the BPC model level IMG parameter "SKIP_GET_FORMULA_DATA" to 'X'. Then BPC calculated data will not be retrieved with delta query for a write-back model.

In a standard configuration of BPC 10.1 on NW 7.50 or higher, most InfoProviders are InfoCubes, but there might be some rare cases in BPC 10.1 on NW 7.52 that are advanced DataStore objects (aDSO).

You can customize the standard data size for an InfoCube based on your environment settings, which is not supported in an aDSO.

This defines the threshold for the total number of requests to be imported or exported each round in an InfoObject in NW 10.1. To do so, set the following parameter in table RSADMIN:

1. Enter report SAP_RSADMIN_MAINTAIN in Tcode se38;
2. In the Object field, enter the parameter: <Infocube ID>_BPC_REQU_SIZE;
3. In the value field, enter the threshold number.

   We recommend a minimum threshold value of 10000.

   Note

   You can improve deployment performance by increasing that number; however, this depends on the maximum number of table partitions allowed in your RDBMS. For more information, see the recommendations of the RDBMS engine used by your NetWeaver platform.

   Example

   For example: in SQL Server, the maximum number of partitions is 1,000. This number is fixed by the database engine. You can calculate limitations as follows: 10,000 * (number of maximum partitions per table).

   This number is different, depending on the database engine you use.

   For SQL Server 2005, 2008, and 2008 R2, the limit is 1,000 partitions per table => 10,000 * 1,000 = 10,000,000 rows per infocube.

About Import Data to a Basic Model or an Existing Model Created in SAP Analytics Cloud

To import data to a basic model or an existing model created in SAP Analytics Cloud:

1. Select (Main Menu)   Browse   Files.

2. Open the model that you want to update.
3. Switch to the Data Management screen.

   

4. In the Draft Sources section, select   Data source  SAP BPC.

5. Choose a BPC connection type and select a BPC connection from the list of connections.

   Note

   You can create a new connection on the fly by selecting Create New Connection and following the instructions in Import Data Connection to an SAP BPC System.

6. Choose to create a new query or copy a query from an existing BPC model for mapping later.

   Click Next after completing all the settings on this page.

7. In the next Select Model from BPC dialog, select an Environment and then select a Model.

   A name is automatically generated for the new BPC query, but you can rename it freely.

8. To build the BPC query you just created:

   1. If the SAP Analytics Cloud model is a basic type model, drag dimensions from Available Data to the Selected Data area.
   2. If you want to restrict the data to be imported, drag dimensions to the Filters area. Set a filter by selecting the filter icon. In the filtering dialog, select members to be included, and then select OK.

   Click Next after completing all the settings on this page.

9. In the dimension mapping dialog, check and map the source BPC dimensions to the corresponding new dimensions in SAP Analytics Cloud. When you've completed the mapping, select Next.

10. In the Import Method dialog, specify how any existing data in the model is to be treated, by choosing one of the following Import Methods:

    Clean & Replace	First deletes the existing data in the default replace scope, then updates existing SAP Analytics Cloud data with data imported from BPC. When there are new records from BPC that don't exist in SAP Analytics Cloud, add the new records directly to the SAP Analytics Cloud model. In this case, you can use the check box for each dimension to decide whether to include or exclude specific dimensions in or from the update.
    Update	Updates the existing SAP Analytics Cloud data, and when there are new records from BPC that don't exist in SAP Analytics Cloud, the new records will be added directly to the SAP Analytics Cloud model.
    Append	Based on the existing SAP Analytics Cloud data, append corresponding BPC data to it, and when there are new records from BPC that don't exist in SAP Analytics Cloud, the new records will be added directly to the SAP Analytics Cloud model.

11. If you choose the Clean & Replace method, you need to further define the default replace scope of the import.
12. Choose Next. The model is updated with BPC imported data.