Test Script CUSTOMER

SAP S/4HANA
August 2021
English SAP Project Budgeting & Planning for SAP
S/4HANA Cloud (2YG)
ID: 2YG

Table of Contents

1 Project Planning and Budgeting for SAP S/4HANA Cloud (2YG) 3

1.1 Test and Process Description 3
1.2 Prerequisites 4
1.3 Proposed Planning Process 4
1.4 System Access 6
1.5 Roles 6
1.6 Model Overview Table 7
1.7 Input Forms - SAP__PRJ_GEN_PROJPLANACCT_INPUT and SAP__PRJ_GEN_PROJBUDFORM_INPUT 8

2 End-User Test Procedures 12

2.1.1 Financial Planning & Analysis Input Forms - Account Input 12
2.1.2 Financial Planning & Analysis Input Forms - Project Budget Formulation Input 13
Document History

Revision Change Date Description

1.0 February 2018 Created version for 1805 release
2.0 August 2018 Update for 1808 release
3.0 November 2018 Update for 1811 release

CUSTOMER
End-User Test Procedures Error: Reference source not found 2
1 Project Planning and Budgeting for SAP S/4HANA Cloud (2YG)

1.1 Test and Process Description

This document explains how to launch project planning and budgeting stories in SAP Analytics Cloud. The planning process in SAP Analytics Cloud is embedded in Project and Budget process
steps executed in SAP S/4HANA Cloud. Please make yourself familiar with the Project Financial Control (1NT) process, which describes how the complete project lifecycle can be supported by a
project financial controller in SAP S/4HANA Cloud for various kinds of projects, such as overhead or investment projects. The Project Financial Control process starts with the creation of
appropriate projects including Work Breakdown Structure (WBS) elements. The WBS elements then can be used for cost planning and budgeting processes in SAP Analytics Cloud.

Once the project master data has been replicated to SAP Analytics Cloud, you can use the input layouts to create planned costs for the newly created projects. SAP Analytics Cloud planning features
help you distribute data along the time and WBS project dimension. Use the lock cell function to block planning combinations from receiving distributed data and create comments to explain data
entries to colleagues. Besides the public version, which will be used to replicate data back to S/4HANA Cloud, you can create multiple private versions. Collaboration features support
communication with team members and stakeholders.
After the replication of planned costs or budgets back to SAP S/4HANA Cloud and the release of the project or project parts by the project financial controller in SAP S/4HANA Cloud, the WBS
elements then can be used for various account assignments in time recording, finance or procurement. As part of the period-end closing process, the actual overhead costs can be allocated and costs
settled to cost centers or asset accounting, if required. Project reports will enable the project financial controller, as well as project managers or project steering committee members, to monitor the
project progress and compare the actual costs and commitments with the planned costs or project budget. Reference SAP S/4HANA Cloud scope item 1NT for more information.
Additional functions for managing and reviewing projects and their corresponding financial data, milestones, and business statuses are available for project managers and project steering committee
members via the Project Review (1YF) business process.
CUSTOMER
End-User Test Procedures Error: Reference source not found 3
1.2 Prerequisites
This section summarizes all prerequisites required to conduct the testing of systems, users, master data, transactional data, and other data and business conditions.

1.3 Proposed Planning Process

The process below is proposed and should be adjusted as you see fit. Use help.sap.com for SAP Analytics Cloud to learn more about features and functions of SAP Analytics Cloud, including how-
to videos.

Process Planning Step How? Comments

Step #
1. Create Project in S/4HANA Cloud In your SAP S/4HANA Cloud system, create
new projects using a work break down structure
(WBS). Please have a look at Project Financial
Control (1NT)
2. Load or update master data from SAP Follow the integration steps in the configuration
S/4HANA Cloud into SAP Analytics Cloud guide 'Import SAP S/4HANA Cloud Project data
into SAP Analytics Cloud' - (2JX)
Newly created objects will be replicated to
SAP Analytics Cloud to enable planning and
replication back to SAP S/4HANA.
You will need to load master data for
Company Code, WBS Element and update the
Account Dimension to your needs.

3. Input updated planned foreign exchange Go to Browse → Models → Currency

currency rates Conversion tab →
SAP__FI_ANA_CURRENCY.
Review and edit the USD and EUR rates as
desired for average and closing rate types.
4. Clear Plan data out of the working Plan In SAP Analytics Cloud, go to the Models, Clear data which is no longer needed. If in
version browse, select the model, and use the Delete doubt, please use the Version Management
Facts icon to clear out data.
to archive the current plan version into a
separate one and clear the facts of the model
afterwards.
5. Set Time Planning Horizon in the Input forms. Go to each story page in the planning story, and An administrator should set the planning time
Set the relevant Plan version for input. make sure the planning time horizon and version horizon and the Version whenever you kick
(SAP__PRJ_GEN_PROJBUDFORM_INPUT are correct and coordinated across all stories. off a new planning or forecast process.
and
SAP__PRJ_GEN_PROJPLANACCT_INPUT
)
6. Confirm that planning security is correct for Do users have the right Company, Cost Center
planning users and Version security? Planners need to be able
to input planning data.

CUSTOMER
End-User Test Procedures Error: Reference source not found 4
 Process Planning Step How? Comments
Step #
7. Announce the start of Planning process in SAP Use your company's preferred collaboration tool. Inform Planners and Analysts where Plan data
Analytics Cloud to key users. is going to be stored, so they can run their own
reports.
8. Planners Plan Enter data into SAP Analytics Cloud input Plan data can be saved in private versions.
layouts and use reports to evaluate your plan. This allows for example for best, worst or the
Create comments and collaborate with team average case scenarios. Once satisfied with the
members about your input figures. plan data save it to the public version which
will be used for data replication to S/4HANA
Cloud.
9. Announce the end of Planning process in SAP Use your company's preferred collaboration tool. Adjust security to close off write-access if
Analytics Cloud to key users. required.
10. Copy the working Plan data into an archived While in a Story related to the model, use the You also have the option to use an input form
Version name. Change security to make the Version Manager to save a Version of Working and the Copy and Paste functionality within
archived version read-only Plan into an archive Plan version. SAP Analytics Cloud to copy data between
Versions, and/or to copy data from one period
to another.
11. Retract Plan data from SAP Analytics Cloud to Follow the integration steps in the configuration
SAP S/4HANA Cloud guide Retract SAP Analytics Cloud Financial
Planning data into S/4HANA Cloud (2JW).
12. Optionally get a project review from project Check Projekt-Review (1YF) for more details. It is recommended that you collaborate with
manager the project managers before plan data will be
replicated to SAP S/4HANA Cloud to be able
to adjust figures in planning grid. Here you
can use the commenting function to outline
your thoughts.
13. Repeat the cycle from the top during next
Planning round

1.4 System Access

System Details
System Accessible via SAP Analytics Cloud. Your system administrator provides you with the URL to
access the models and stories.

CUSTOMER
End-User Test Procedures Error: Reference source not found 5
1.5 Roles
Use the following standard test users or assign roles to SAP Analytics Cloud testers, respectively:

SAP Analytics Cloud

Business Role Name The main functions of role Log On

The users in SAP Analytics Cloud with
Analyst role.
The users in SAP Analytics Cloud with
Planner role.
The users in SAP Analytics Cloud with
Administrator role.
Analyst - allows for read only access to
information
Planner - allows of input of data in time
periods within the planning horizon
Administrator - imports models, copies This role is not used in end-user testing
models, maintains dimensions, imports data,
exports data, clears data, sets up user security,
establishes planning time horizon in input
templates, communicates readiness of data and
planning process

1.6 Model Overview Table

The proposed financial planning model for SAP S/4HANA Cloud is the following financial model for Project Budget planning activity created in SAP Analytics Cloud. The model is made up of a
combination of critical dimensions sourced from SAP S/4HANA Cloud and other dimensions maintained only in SAP Analytics Cloud.

Dimension Public Dimension Name Integrated to Summary Notes

SAP S/4HANA
Cloud
Company Code SAP_ALL_COMPANY_CODE Yes (Secure) An organization type dimension that contains legal company codes. Local currency is driven
from the currency attribute in this dimension.
G/L Account SAP_PRJ_S4HC_GLACCOUNT Yes. SAP Contains the best practice G/L Accounts (YCOA) available in SAP S/4HANA Cloud and is supported
S/4HANA Cloud- by a hierarchy built and maintained in SAP Analytics Cloud for the initial release.
based hierarchy is
built and
maintained
manually,
WBS Element SAP_ALL_PROJECT_WBSELEMENT Yes Structure element of the work breakdown structure (WBS). A WBS element describes either a certain
task or a partial task that can be subdivided further. Data Access Control and / or Responsibility can
be switched on for this dimension. By default Access Control and Responsibility is switched off.
Time N/A (System dimension) No Contains time periods with lowest level of time = month.
Version N/A (System dimension) No (Secure) Contains the types of data tracked, for example ACTUAL, PLAN, FORECAST.

CUSTOMER
End-User Test Procedures Error: Reference source not found 6
1.7 Input Forms - SAP__PRJ_GEN_PROJPLANACCT_INPUT and SAP__PRJ_GEN_PROJBUDFORM_INPUT
The input forms are displayed in a grid as known from Microsoft Excel. This provides you with a familiar look and feel during data input. In the Project Planning on Account input form, the periods
are displayed in columns and the WBS Elements with G/L Accounts in rows. SAP Analytic Cloud planning features can be used to distribute values from top hierarchy nodes to leaf nodes. Using the

control item Lock Cell, you can block cells from data input. As a best practice, the SAP Analytics Cloud administrator should open and set the time planning horizons and version value
consistently on each tab before the start of the planning cycle.

Figure 1: Screen Shot of Input Form SAP__PRJ_GEN_PROJPLANACCT_INPUT

We recommend you select a single company code to facilitate input of plan data. When all selected company codes use the same currency, the currency label will appear below the story title.

CUSTOMER
End-User Test Procedures Error: Reference source not found 7
We recommend you use the Mass Data Entry option to allow for multiple cells to be input before being submitted. After inputting plan data into this template, make sure to select Version
Management from the SAP Analytics Cloud menu bar, and choose Save for the relevant Plan version.
Tip: When the version says Edit Mode, that means there is plan data to save back to the model.
The Project Budget Input form provides an input grid with Version and Time Dimension in columns and the specific WBS Elements of the project in rows. The SAP Analytics Cloud content story
uses a fix filter value for G/L Account dimension. The value is: 65008300 (Services – General). All plan data is stored in the database with the same G/L Account 65008300.

Figure 2: Filter Settings for Input Form SAP__PRJ_GEN_PROJBUDFORM_INPUT

Story filters, which you can change, are Company Code and WBS Element. Data entry for entire year or individual periods are possible. The system aggregates or distributes the data. If you want to
block cells from changes, use the Lock Cell function of SAP Analytics Cloud.

Figure 3: Screen Shot of Input Form SAP__PRJ_GEN_PROJBUDFORM_INPUT

Via Version Management data is saved to either public or private versions. Private version can be used to compare different scenarios.

CUSTOMER
End-User Test Procedures Error: Reference source not found 8
 Input Forms
SAP__PRJ_GEN_PROJPLANACCT_INPUT
SAP__PRJ_GEN_PROJBUDFORM_INPUT
End-User Test Procedures
Major User Controls Best Practice Usage Notes
Company Code The main purpose of this form is to plan WBS Elements on G/L Company Code, Projects (WBS Element) and
account level. G/L Accounts are replicated from your source
system. Via filter function you can restrict the
planning layout to display only relevant data.
Company Code is defined as an
organizational dimension in this SAP
Analytics Cloud model and defines the
currency for plan data input.
Company Code, The main purpose of this form is to capture planned project costs Project Budget Formulation planning requires
WBS Element for a specific Company Code Company Code and WBS
Element selection only.
Company Code is defined as an
organizational dimension in this SAP
Analytics Cloud model and defines the
currency for plan data input.
CUSTOMER
Error: Reference source not found 9
2 End-User Test Procedures

This section describes test procedures for each process step that belongs to this scope item.

2.1.1 Financial Planning & Analysis Input Forms - Account Input

Purpose

Confirm the SAP__PRJ_GEN_PROJPLANACCT_INPUT story is available and operating properly.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail /
Comment
1. Open Analytics Cloud Log on to SAP Analytics Cloud as a 'Planner'. The Home - Welcome to SAP Analytics Cloud
The Planner role will let the user submit Plan data into SAP screen is displayed.
Analytics Cloud, but the delivered template should restrict the
user from submitting data into Actual periods.
14. Access the Story page Open the Browse  Stories in the Main Menu. The Story page is displayed.

15. Access the Story Find and display the story under Public tab < The Story
SAP__PRJ_GEN_PROJPLANACCT_INPUT >. SAP__PRJ_GEN_PROJPLANACCT_INPUT is
displayed.
16. Story Displayed The story will show. The report will show a planning Grid with WBS
Elements and G/L Account in rows and Version and
Time Periods in columns.
17. Set Filter value for Company The story includes an Input Control for Dimension Company Selecting the desired value for Company Code
Code Code. Choose Input Control and select the desired company changes the filter of the grid. Either an empty grid or
code. data for the selected Company Code is displayed.
18. Collapse WBS Element Choose the arrow below the WBS Element and collapse Column WBS Element displays all top node
Hierarchy the dimension hierarchy to top nodes. members of this dimension.

19. Expand WBS Element to Choose the arrow of WBS Element to expand the Column WBS Element displays next level nodes of
desired level dimension member for which you would like to enter plan this dimension. The users can further drill down to

CUSTOMER
End-User Test Procedures Error: Reference source not found 10
 Test Step # Test Step Name Instruction Expected Result Pass / Fail /
Comment
data. lowest level.
20. Expand column G/L Account to Choose the arrow of G/L Account dimension to expand the Column G/L Account displays next level nodes of
desired level hierarchy to the desired level for which you would like to enter this dimension. The users can further drill down to
plan data. lowest level.

21. Enter plan data into Grid Enter manually or copy and paste values into data cells of the Data entered in cells is displayed. Values are
planning grid. aggregated along the hierarchy. Values entered on
hierarchy nodes are distributed automatically to leaf
nodes proportionally once you choose Enter. If leaf
nodes contain no data, the distribution to leaf nodes
is executed equally.
22. Save data Use the Version Management function to save data.
Choose Version Management from the tool bar and You can decide to save your plan data to a Private or
choose Save for the Plan version. Public version. After processing, you should see the
value is no longer highlighted and your value is the
same as your input.

2.1.2 Financial Planning & Analysis Input Forms - Project Budget Formulation Input

Purpose

Confirm the SAP__PRJ_GEN_PROJBUDFORM_INPUT story is available, actual data refreshes, and Plan data input is possible.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail /
Comment
1. Open SAP Analytics Cloud Log on to SAP Analytics Cloud as a Planner. The Home - Welcome to SAP Analytics Cloud
The Planner role will let the user submit Plan data into SAP screen is displayed.
Analytics Cloud, but the delivered template should restrict the user
from submitting data into Actual periods.
23. Access the Story page Open the Browse  Stories in the Main Menu. The Story page is displayed.

24. Access the Story Find and display the story under Public tab < The Story
SAP__PRJ_GEN_PROJBUDFORM_INPUT >. SAP__PRJ_GEN_PROJBUDFORM_INPUT is
CUSTOMER
End-User Test Procedures Error: Reference source not found 11
 Test Step # Test Step Name Instruction Expected Result Pass / Fail /
Comment
displayed.
25. Story Displayed By default, the story displays the Project Budget Formulation form The report shows a planning grid with values for
upon opening. WBS Element in the rows and Version and Time
members in the columns.
26. Review the Budget This input form is used to plan Budget at WBS Element level for a Planning grid displays WBS Element members in
Formulation Input page specific year and Version. the rows and allows plan data input in column B.
Note: The page uses two filter Input Controls, one for Company
Code and one for WBS Element. Select the desired values.
27. Input some data into Plan Expand the WBS Element hierarchy and or Time hierarchy, enter Confirm the data was allowed in the cell and is
periods in the Budget Plan data and choose Enter. equal to the value you enter after processing is
Formulation Input page Repeat if needed. done. (Note: if you input into a parent node, the
value will be allocated down to other accounts.
This is expected behavior).
28. Commit the Plan input into Select Version Management from the tool bar and choose Save for After processing, you should see that the value is
public version of Plan. the Plan version. no longer highlighted and your value is the same
as you input.

CUSTOMER
End-User Test Procedures Error: Reference source not found 12
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. 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 database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the
documentation.
<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 .

© 2021 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
affiliate company.
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. Please see
http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
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
informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop or release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform
directions and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice.
The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned
not to place undue reliance on these forward-looking statements, which speak
CUSTOMER
End-User Test Procedures only as of their dates, and they Error:
shouldReference
not be relied upon
source notinfound
making 13
purchasing decisions.