Test Script

SAP S/4HANA Cloud - 26-12-22

Financial Planning and Analysis (2FM_IN)

PUBLIC

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

Note 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 appropri -
ate.

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 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 business conditions.

2.1 System Access

System Details

System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.

2.2 Roles
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role for the Administrator in the product assistance for SAP S/4HANA Cloud.

Name (Role Template) ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log on

General Ledger Accountant SAP_BR_GL_ACCOUNTANT General Ledger Accountant SAP_BR_GL_ACCOUNTANT

2.3 Master Data, Organizational Data, and Other Data

Default Values
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 mas -
ter data represents materials, customers, and vendors, for example, depending on the operational focus of your company.
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.

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 3
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 Proce-
dures documentation.
Use the following master data in the process steps described in this document:

Master Data Sample Value Details Comment

Company Code 1810

Financial Statement Version FPA1

Controlling Area A000

Cost Center 18101001

For more information on creating these master data objects, see the following Master Data Scripts (MDS)

MDS Description

BNM Create Cost Center and Cost Center Group

BNG Create G/L Account and Cost Element

BNH Create Profit Center

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 4
3 Overview Table

The Financial Planning and Analysis scope item consists of one process step provided in the following table.

Note 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 (searchable) apps not included on the homepage using the search bar (2434549).
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 [page ] 6 General Ledger Accoun- Manage Financial Statement Versions (OB58) You maintained the financial statement version.
tant

Maintain Semantic Tags for Financial Statement Version [page ] General Ledger Accoun- Assign Semantic Tags to FSV Semantic tags are maintained for the financial statement version.
7 tant (FINSC_FAGL2SEMTA)

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 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> Testing Date:

Tester Name: Duration:

Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Context

In this activity, you maintain the financial statement version.

Caution You can't save changes to the Financial Statement Version in a Q-system with the Manage Financial Statement Version app. If you require to save changes to the Financial Statement
Version in the Q-system, open an incident to the service center using the component XX-S4C-SRV-CON. It's possible to change and save the changes to the Financial Statement Version in the
P-System.

Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger Accountant.

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 6
 Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

2 Access the SAP Fiori App Open Manage Financial Statement Versions (OB58). The Change View "Financial Statement Versions": Overview view is
displayed.

3 Select Financial Statement Ver- Select the following financial statement version and choose Financial Statement The Change Financial Statement Version view is displayed.
sion Items:
Financial Statement Version: FPA1

4 Assign Accounts Select the item where the account should be added and choose Assign Accounts. The Change Accounts entry view displays.

Note The account can't be in multiple items.

5 Enter Account Make the following entries and choose Continue: The account is assigned to the financial statement.

Note The account can't be in multiple rows.

From Acct: <your account>

To Acct: <your account>
D: Selected
C: Selected

6 Save Save your entries.

7 Delete Accounts Expand to the item to be maintained, select the account, and choose the Delete The account is deleted from the financial statement.
button.

8 Save Save your entries.

4.2 Maintain Semantic Tags for Financial Statement Version

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 7
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Context

In this activity, you maintain semantic tags for the financial statement version.

Caution You can't save changes to the Financial Statement Version in a Q-system with the Assign Semantic Tags to FSV app. If you require to save changes to the Financial Statement Version
in the Q-system, open an incident to the service center using the component XX-S4C-SRV-CON. It's possible to change and save the changes to the Financial Statement Version in the P-Sys-
tem.

Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

1 Log On Log on to the SAP Fiori launchpad as a General Ledger Ac-

countant.

2 Access the SAP Fiori Open Assign Semantic Tags to FSV The Change View "Mapping of Financial Statement Versions to Semantic Tag" view is displayed.
App (FINSC_FAGL2SEMTA).

3 Add Semantic Tag Choose New Entries.

4 Select Semantic Tag Select Assign Semantic Tag to FS Item and choose Con- The New Entries: Details of Added Entries view is displayed.
Type tinue.

5 Assign Semantic Tag Make the following entries and choose Save: The system displays the message Data was saved.
FS Version: FPA1
FS Item: 68
Semantic Tag: OPEREXP

6 Cancel Choose Cancel. The Change View "Mapping of Financial Statement Version to S..": Overview view displays the
list of semantic tags.

7 Select Semantic Tag for Scroll and select a semantic tag relevant to your FSV.
FSV FS Vers: FPA1
FS Item: 68

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 8
 Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

8 Delete Semantic Tag Choose Delete. The semantic tag is deleted from the FSV.

9 Save Save your entries.

Financial Planning and Analysis (2FM_IN)

Purpose PUBLIC 9
 Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names,
menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions. www.sap.com/contactsap

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 IN-
CLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parame-
ters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documenta-
tion.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affili-
ate company. 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 or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies 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 war-
ranty statements accompanying such products 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 Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.

See www.sap.com/copyright for additional trademark informa-

Financial Planning and Analysis (2FM_IN) tion and notices.
Purpose PUBLIC 10