Financial Planning and Analysis (2FM_IN) PUBLIC
Purpose Error: Reference source not found 1
Test Script PUBLIC
SAP S/4HANA - 14-09-21
Financial Planning and Analysis (2FM_IN)
Table of Contents
1 Purpose
2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
3 Overview Table
4 Test Procedures
4.1 Maintain Financial Statement Version
4.2 Maintain Semantic Tags for Financial Statement Version
1 Purpose
This scope item allows SAP S/4HANA customers to leverage a predefined Financial Statement Version (FSV) that supports financial planning and analysis
across the enterprise.
The FSV supports financial planning and analysis within SAP Analytics Cloud, and can be used within embedded analytics in SAP S/4HANA.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each
process step, report, or item is covered in its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the
process but are needed for testing are marked accordingly. Project-specific steps must be added.
Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different
notation, enter values as appropriate.
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 2
2 Prerequisites
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and busi-
ness conditions.
2.1 System Access
Sys- Details
tem
Sys- Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various
tem apps assigned to your role.
2.2 Roles
Assign the following business roles to your individual test users. Alternatively, if available, you can create business roles using the following spaces with
pages and predefined apps for the SAP Fiori launchpad and assign the business roles to your individual test users.
These roles or spaces are examples provided by SAP. You can use them as templates to create your own roles or spaces.
For more information about business roles, refer to Assigning business roles to a user in the Administration Guide to Implementation of SAP S/4HANA with
SAP Best Practices .
Name (Role) ID (Role) Name ID (Space) Log
(Space) on
General Ledger Ac- SAP_BR_GL_ACCOUNTANT General SAP_BR_GL_ACCOUNTANT
countant Ledger
2.3 Master Data, Organizational Data, and Other Data
Default Values
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 3
The organizational structure and master data of your company was created in your ERP system during implementation. The organizational structure reflects
the structure of your company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your com-
pany.
The business process is enabled with this organization-specific master data, examples are provided in the following section.
Additional Default Values
You can test the scope item with other SAP Best Practices default values that have the same characteristics.
Check your SAP ECC system to find out which other material master data exists.
Using Your Own Master Data
You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create
master data, see the Master Data Procedures documentation.
Use the following master data in the process steps described in this document:
Master Data Sample De- Com-
Value tails ment
Company Code 1810
Financial Statement FPA1
Version
Controlling Area A000
Cost Center 18101001
For more information on creating master data objects, see the following Master Data Scripts (MDS):
Sys- Details
tem
BNM Create Cost Center and Cost Cen-
ter Group
BNG Create G/L Account and Cost Ele-
ment
BNH Create Profit Center
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 4
3 Overview Table
The Financial Planning and Analysis scope item consists of one process step provided in the following table.
If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the
typical tasks of a business role.
You can find all other apps not included on the homepage using the search bar.
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Process Step Business Role App/Transaction Expected Results
Maintain Financial Statement Version General Ledger Manage Financial Statement Versions You maintained the financial statement
[page ] 6 Accountant (OB58) version.
Maintain Semantic Tags for Financial State- General Ledger Assign Semantic Tags to FSV Semantic tags are maintained for the finan-
ment Version [page ] 8 Accountant (FINSC_FAGL2SEMTA) cial statement version.
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 5
4 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
4.1 Maintain Financial Statement Version
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Tester Name Testing Enter a test date.
Date
Business
Role(s)
Responsibil- <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
ity
Context
In this activity, you maintain the financial statement version.
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 6
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /
Step Comment
#
1 Log On Log on to the SAP Fiori launchpad as a General
Ledger Accountant.
2 Access the SAP Fiori Open Manage Financial Statement Versions (OB58). The Change View "Financial Statement Ver-
App sions": Overview view is displayed.
3 Select Financial Select the following financial statement version and The Change Financial Statement Version view
Statement Version choose Financial Statement Items: is displayed.
Financial Statement Version: FPA1
4 Delete Accounts Expand to the item to be maintained, select the ac- The account is deleted from the financial
count, and choose the Delete button. statement.
5 Save Save your entries.
6 Assign Accounts Select the item where the account should be added The Change Accounts entry view displays.
and choose Assign Accounts.
Note The account cannot be in multiple items.
7 Enter Account Make the following entries and choose Continue: The account is assigned to the financial state-
Note The account cannot be in multiple rows. ment.
From Acct: <your account>
To Acct: <your account>
D: Selected
C: Selected
8 Save Save your entries.
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 7
4.2 Maintain Semantic Tags for Financial Statement Version
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Tester Name Testing Enter a test date.
Date
Business
Role(s)
Responsibil- <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
ity
Context
In this activity, you maintain semantic tags for the financial statement version.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment
1 Log On Log onto the SAP Fiori launchpad as a Gen-
eral Ledger Accountant.
2 Access the SAP Open Assign Semantic Tags to FSV The Change View "Mapping of Financial Statement Ver-
Fiori App (FINSC_FAGL2SEMTA). sions to Semantic Tag" view is displayed.
3 Select Semantic Scroll and select a semantic tag relevant to
Tag for FSV your FSV.
FS Vers: FPA1
FS Item: 18
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 8
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment
4 Delete Semantic Choose Delete. The semantic tag is deleted from the FSV.
Tag
5 Save Save your entries.
6 Add Semantic Choose New Entries.
Tag
7 Select Semantic Select Assign Semantic Tag to FS Item and
Tag Type choose Continue.
8 Assign Semantic Make the following entries and choose Save: The system displays the message Data was saved.
Tag Fin.Stmt.Vers.: FPA1
FS Item: 18
Semantic Tag: OPEREXP
Financial Planning and Analysis (2FM_IN) PUBLIC
Test Procedures Error: Reference source not found 9
Typographic Conventions
Type Description
Style
Example Words or characters quoted from the screen. These include field names, screen titles, push-
buttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
www.sap.com/contactsap
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program names, transaction
codes, table names, and key concepts of a programming language when they are surrounded
by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and data-
base tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Ex- Variable user entry. Angle brackets indicate that you replace these words and characters with
ample> appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
© 2021 SAP SE or an SAP affiliate company. All rights re-
served.
No part of this publication may be reproduced or transmitted
in any form or for any purpose without the express permis-
sion of SAP SE or an SAP affiliate company. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distribu-
tors contain proprietary software components of other soft-
ware vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate
company for informational purposes only, without representa-
tion or warranty of any kind, and SAP or its affiliated compa-
nies shall not be liable for errors or omissions with respect to
the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in
the express warranty statements accompanying such prod-
ucts and services, if any. Nothing herein should be construed
as constituting an additional warranty.
SAP and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Ger-
Financial Planning and Analysis (2FM_IN) PUBLIC
many and other countries. All other product and service
Test Procedures names mentionedError: Reference
are the source
trademarks not found
of their respective 10
companies.
See www.sap.com/copyright for additional trademark infor-
mation and notices.
