1 Enhancing an Input-Ready Query with a Comments Column in SAP BPC for S/4HANA An Example-Based How-To Guide Applies to: SAP BPC for S/4HANA Summary SAP customers who use SAP BPC for S/4HANA are often in the situation that they want to add comments to their plan data. With SAP NetWeaver 7.40 SP08 and SAP Business Objects Analysis 1.4.9, input-ready queries for planning can be enhanced with additional columns in which users can make comments. This How-To guide describes step-by-step, using an example, how customers can enhance content delivered by SAP with SAP BPC for S/4HANA, on-premise edition 1503 support package stack 1508, by adding comment columns to input-ready queries. Author(s): Günter Graf Company: SAP SE Created on: 14 August 2015 Author Bio Günter Graf is a Senior Developer at SAP SE in Walldorf, Germany. He has 8 years experience in developing SAP standard software, the last 4 years in the ERP Financials area.
Transcript
1
Enhancing an Input-Ready Query with a Comments Column in SAP BPC for S/4HANA An Example-Based How-To Guide Applies to: SAP BPC for S/4HANA
Summary
SAP customers who use SAP BPC for S/4HANA are often in the situation that they want to add comments to
their plan data. With SAP NetWeaver 7.40 SP08 and SAP Business Objects Analysis 1.4.9, input-ready
queries for planning can be enhanced with additional columns in which users can make comments. This
How-To guide describes step-by-step, using an example, how customers can enhance content delivered by
SAP with SAP BPC for S/4HANA, on-premise edition 1503 support package stack 1508, by adding comment
columns to input-ready queries.
Author(s): Günter Graf Company: SAP SE Created on: 14 August 2015
Author Bio
Günter Graf is a Senior Developer at SAP SE in Walldorf, Germany. He has 8 years experience
in developing SAP standard software, the last 4 years in the ERP Financials area.
2
Table of Contents
Business Scenario .............................................................................................................................................. 3
Background Information ...................................................................................................................................... 3
See Also............................................................................................................................................................ 33
Business Scenario SAP users can use the queries and workbooks delivered by SAP in SAP BPC for S/4HANA for financial planning in Management Accounting. These queries and workbooks serve as examples for different types of planning and can be readily used. For example, an SAP customer can use the delivered Analysis Office Workbook for Cost Center Planning on Years (/ERP/SFIN_A00_WB01) to plan costs on the granularity of cost center/cost category/fiscal year in a Microsoft Excel environment (see Figure 1).
Figure 1: Analysis Office Workbook for Cost Center Planning on Years
Users can in fact make an explanatory comment for each planned figure locally in Microsoft Excel (for example, in an Excel column outside the table area of the data source). However, this comment can only be saved locally and not centrally in the SAP system.
This How-To guide describes how the Workbook and the underlying objects in SAP SAP BPC for S/4HANA can be enhanced so that users can make comments in the Workbook that can be persisted together with the planned figures in the SAP system.
Background Information SAP delivers planning scenarios for financial planning in Management Accounting as local BW content (that is, BW content in the ERP system, not in the central BW system), based on the real-time InfoCube /ERP/SFIN_R01 (Financials Planning). Analysis Office Workbooks constitute part of the planning scenario. Customers can use these to enter planned figures in a Microsoft Excel environment.
4
SAP delivers the following Workbooks:
Cost Center Planning on Years (/ERP/SFIN_A00_WB01)
Cost Center Planning on Periods (/ERP/SFIN_A01_WB01)
Internal Order Planning on Years (/ERP/SFIN_A10_WB01)
Internal Order Planning on Periods (/ERP/SFIN_A11_WB01)
Project Planning on Years (/ERP/SFIN_A20_WB01)
Project Planning on Periods (/ERP/SFIN_A21_WB01)
Market Segment Planning on Years (/ERP/SFIN_A50_WB01)
Market Segment Planning on Periods (/ERP/SFIN_A51_WB01)
Profit Center Planning on Years (/ERP/SFIN_A70_WB01)
Profit Center Planning on Periods (/ERP/SFIN_A71_WB01)
P&L Planning on Years (/ERP/SFIN_A90_WB01)
P&L Planning on Periods (/ERP/SFIN_A91_WB01)
Figure 2 shows the technical architecture of the delivered planning scenarios.
5
BW
HANA Views from Content Package sap.erp.sfin.co.pl
BW CharacteristicsBW Characteristics
Master Data ViewsMaster Data Views
Master Data Views FCO_C_<…>
Characteristics /ERP/<…>
Real-Time InfoProvider /ERP/SINF_R01
(Plan Data)
Aggregation Level ERP/SFIN_A<…>
Input Ready Query /ERP/SFIN_A<…>_IRQ<…>
Analysis Office Workbook /ERP/SFIN_A<…>_WB01
Virtual Provider /ERP/SINF_V01 (Actual
Data)
BW CharacteristicsBW Characteristics
Key Figures /ERP/<…>
Multiprovider /ERP/SFIN_M01
HANA Information Model
FCO_C_IBP_ACDOCA (Actual Data)
Plan Data
Figure 2: Architecture of the Delivered Planning Scenarios
On the highest level are the Analysis Office Workbooks, with which end users can enter planned figures. The figures entered in this way are persisted in InfoCube /ERP/SFIN_R01.
InfoProvider /ERP/SFIN_V01 is used to read the actual values from the previous year and compare the planned values of the current year in the Workbooks. A planning function can also be used to copy the actual values from the previous year as a template for the planned values of the current year in the Workbooks. The InfoProvider is based on HANA Information Model sap.erp.sfin.co.pl. FCO_C_IBP_ACDOCA.
The characteristics of both InfoProviders read their master data from the ERP master data tables, which are accessed in HANA Views FCO_C_<…>. For example, master data access for characteristic /ERP/MATERIAL is based on HANA View FCO_C_PRODUCT, which in turn contains ERP master data tables MARA and MAKT.
Step-by-Step Procedure This How-To guide describes how you can enhance the delivered Analysis Office Workbooks and underlying queries with a comment column. Comments that can be persisted in the SAP system upon saving can then be entered in the Workbooks and queries. The assignment to planned figures is retained.
The description of the procedure is based on Cost Center Planning on Years (Analysis Office Workbook /ERP/SFIN_A00_WB01).
6
In essence, a DataStore Object (DSO) in the Z namespace (in the example, with technical name ZCMNTDSO) is created as a data store for the comments and is added to the MultiProvider /ERP/SFIN_M01 delivered by SAP. This DSO contains a characteristic for the comments that can be represented as a column with input fields, analogous to an input-ready key figure in the input-ready queries and Workbooks. To do this, the comment characteristic (in the example with technical name ZCOMMENT) must be taken into account accordingly in higher-level objects (aggregation level, query). See Figure 3.
HANA Views from Content Package sap.erp.sfin.co.pl
BW
Master Data ViewsMaster Data Views
Aggregation Level ERP/SFIN_A<…>
Input Ready Query /ERP/SFIN_A<…>_IRQ<…>
Analysis Office Workbook /ERP/SFIN_A<…>_WB01
Virtual Provider /ERP/SINF_V01 (Actual
Data)
Multiprovider /ERP/SFIN_M01
HANA Information Model
FCO_C_IBP_ACDOCA (Actual Data)
DataStore Object ZCMNTDSO
(Comments)
Characteristic ZCOMMENT
BW Characteristics
Master Data Views FCO_C_<…>
BW CharacteristicsCharacteristics /ERP/<…>
BW CharacteristicsBW Characteristics
Key Figures /ERP/<…>
Real-Time InfoProvider /ERP/SINF_R01
(Plan Data)
Plan Data
Figure 3: Architecture with Comment DSO and Comment Characteristics
This guide describes how to proceed if you want to modify the scenario for Cost Center Planning on Years delivered by SAP. Analogously, you can of course also create your own objects in the Z namespace and set up your requirements accordingly.
Step 1: Create Comment Characteristic
First of all, create a comment characteristic in the Z namespace.
7
- Use transaction RSD1 to create the new characteristic.
8
- On the General tab page, select data type CHAR with length 250 and select the Lowercase Letters checkbox.
9
- On the Master Data/Texts tab page, deselect the With Master Data and With Texts checkboxes.
- Save and activate your characteristic.
Step 2: Create DataStore Object
Now create the DSO. The comments are saved in this in the desired granularity.
10
- Use transaction RSA1 to create a new DataStore Object.
- Change the settings of the DSO. Set the DSO type to Direct Upload and select the Planning Mode checkbox.
- Add the following characteristics as key fields:
o Fiscal Year 0FISCYEAR
o Category (/ERP/CATEGORY)
o Chart of Accounts (/ERP/CHRTACCT)
o Client (0MANDT)
o Company Code (/ERP/COMPCODE)
o Controlling Area (/ERP/CO_AREA)
o Cost Center (/ERP/COSTCNTR)
o Currency Key (0CURRENCY)
o Debit/Credit Indicator CO (/ERP/DCINDCO)
o Fiscal Year (0FISCYEAR)
11
o Fiscal Year Variant (0FISCVARNT)
o G/L Account (/ERP/GL_ACCT)
o Ledger (ERP/LEDGER)
Add the following key figures/characteristics as data fields:
o Amount (/ERP/AMOUNT)
o Comment (ZCOMMENT) – your comment characteristic
When you have added your comment characteristic as a data field, it also appears in the Characteristics as Key Figures area. Also select the checkbox in the On/Off column.
- Save and activate your DSO.
12
Step 3: Add DSO to MultiProvider
Now add your DSO to the MultiProvider /ERP/SFIN_M01 delivered by SAP.
- Open MultiProvider /ERP/SFIN_M01 in editing mode.
13
- Add your DSO to the MultiProvider.
14
- Identify the characteristics of the DSO in the MultiProvider.
- In the following dialog, use the Down button to run down and assign each characteristic. The screenshot shows this for characteristic 0FISCVARNT.
15
- Enhance the assignment of the following characteristics as shown in the respective screenshots. All other characteristic assignments remain unchanged.
o 0FISCVARNT (see above)
o 0FISCYEAR
o /ERP/LEDGER
o /ERP/CATEGORY
16
o /ERP/CHRTACCT
o /ERP/GL_ACCT
o /ERP/DCINDCO
17
o /ERP/CO_AREA
o /ERP/COMPCODE
/ERP/COSTCNTR
18
o 0MANDT
- Confirm the dialog
- Transfer your comment characteristic from the Characteristics as Key Figures area of your DSO to the Key Figures area of the MultiProvider.
19
- Select the key figures of the MultiProvider.
- In the following dialog, assign the key figure /ERP/AMOUNT of your DSO by selecting the checkbox.
20
- Use the Down button to switch to key figure 1KYF_ZCOMMENT. Select the checkbox there and confirm the dialog.
- Save and activate the InfoProvider.
21
Step 4: Adjust Aggregation Level
In this step, you add the comment field to the higher-level aggregation level /ERP/SFIN_A00 (Cost Center Planning on Years).
- Open aggregation level /ERP/SFIN_A00 with transaction RSPLAN in edit mode.
22
- In the following screen, transfer your comment characteristic from the Key Figures area of the MultiProvider to the Key Figures area of the aggregation level.
- Save and activate the aggregation level.
23
Step 5: Adjust Query
In this step, you add the comment field to the input-ready query /ERP/SFIN_A00_IRQ0001 (Cost Center Planning on Years).
- In the BEx Query Designer, open query /ERP/SFIN_A00_IRQ0001.
- Transfer the Comment field from the Key Figures area of the InfoProvider to the Column area of the query.
24
- Open the context menu of the Comment column and select Edit.
25
- In the following dialog, restrict the key figure Comment analogously to the plan key figure. That is, restrict the key figure to the following:
o The InfoProvider that corresponds to your DSO
o The category saved in variable /ERP/P_CATEGORY
o The fiscal year saved in variable /ERP/P_0FISCYEAR01
- Confirm the dialog with OK
26
- In the properties for the Comments key figure, select the Input-Ready option on the Planning tab page. To specify disaggregation, you can choose between No Disaggregation and Disaggregation Copy. Analogous to normal key figures, in Disaggregation Copy the comment is also input-ready in totals lines or on hierarchy nodes. Disaggregation for comments means that the same comment is simply copied to all lower-level objects.
- Save the query.
27
- Test the query, for example, with transaction RSRT.
- Click Execute and enter suitable selection options in the variable screen. Click Execute again.
28
- In the following screen, you should only see the query result with input-ready columns for the annual plan value and an additional input-ready column for comments.
29
- The comments column is also present in the Analysis Office Workbook Cost Center Planning on Years (/ERP/SFIN_A00_WB01) (see chapter Business Scenario) mentioned at the beginning of this document
30
Step 6: Use Comment Field in Planning Function (Optional)
The comment field functions like a key figure, so it can also be used like a key figure in planning functions. That is, planning functions can also be created to manipulate the comments. For example, you can create a planning function that copies plan figures together with comments from one category to another.
The following screenshots show an Analysis Office Workbook that you can use to do exactly that. This Workbook is not part of the SAP delivery, but is created as a Z object.
The Workbook contains a Copy Source -> Target button that users can click to copy the plan figures together with commentary from a source category to a target category.
Clicking the button executes a planning sequence that calls a planning function in turn. This planning function copies the amounts and the comments from the source category to the target category.
31
The definition of the objects involved can be seen from the following screenshots. The planning sequence, planning function, and planning filter in turn are not part of the SAP delivery but were created as Z objects. So was variable Z_TARGET_CATEGORY, which you can also see in the screenshots, in which the target category is saved at query runtime.
Planning sequence:
32
Planning function:
Planning filter:
33
Technical Prerequisites To use the short text function, you need at least SAP NetWeaver Version 7.40 SP08.
Regarding front-end technology, there are some restrictions at the time of writing this document. Not everything works with all front ends. For example, the Bex Analyzer can display the short texts but cannot save them, and only texts with a limited field length can be saved when using transaction RSRT.
Current front-end technologies such as Bex Web, Analysis Office und EPM Add-in provide unrestricted support for the functionality; Analysis Office as of Version 1.4x and EPM as of Version 10.0 SP20.
See Also For the NetWeaver documentation on the new comments function, see the SAP Help Portal under
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE and its affiliated companies (“SAP SE Group”) for informational purposes only, without representation or warranty of any kind, and SAP SE Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP SE and other SAP SE products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
