3dj s4cld2108 BPD en XX

Test Script CUSTOMER
SAP S/4HANA
August 2021
English Workforce Planning for
SAP S/4HANA
ID: 3DJ
Table of Contents
1 Workforce Planning for SAP S/4HANA 4

1.1 Test Description 4
1.2 Prerequisites and How-to-Implement 5
1.3 Proposed planning Process 7
1.3.1 System Access 13
1.3.2 Roles 13
1.3.3 Security 14
1.3.4 Data Locking 15
1.3.5 Currency Translation Considerations 17
1.4 Data Flow Diagram 20
1.5 Model Overview table 21
1.6 Report - SAP__FI_ANA_WFP_JOB_REPORTS 23
1.7 Report - SAP__FI_ANA_WFP_JOB_OVERVIEW 25
1.7.1 Job Overview - Performance 25
1.7.2 Job Overview – Actuals vs Plan 26
1.8 Input Forms/Story - SAP__FI_ANA_WFP_JOB_INPUT 27
1.9 Input Forms - SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITION 40
1.10 Advanced Formulas 41
1.10.1 SAP__FI_ANA_WFP_JOB_ADMIN1 - Process Actual Data 41
1.10.1.1 FTE_Initialize: 42
1.10.1.2 copy annual salary SFSF to SAC audit Id: 43
1.10.1.3 FTE_Hire_Term_End_Initialize 43
1.10.1.4 FTE_Transfer_Initialize 44
1.10.2 SAP__FI_ANA_WFP_JOB_ADMIN2 - Copy Actual to Plan 44
1.10.2.1 copy actual to plan - FTE, expenses 45
1.10.2.2 copy actual to plan - latest salary/wage 46
1.10.2.3 Copy Actual to Plan – FTE Hire, Term Plan (Future) 47
1.10.3 SAP__FI_ANA_WFP_JOB_ADMIN3 - Process Plan Data 47
1.10.3.1 calc_FTE_end_initalize 48
1.10.3.2 calculate historical expenses and FTE: 49
1.10.3.3 calc_total_historical_percent_and_perFTE 51
1.10.4 SAP__FI_ANA_WFP_JOB_CALC_PLAN - Process plan Data 53
1.10.4.1 calc_fte_carryforward 53
1.10.4.2 calculate salary based on merit 54
1.10.4.3 calculate final plan results 55
2 End-User Test Procedures 57

2.1.1 Financial planning & Analysis Reports 57
2.1.1.1 SAP__FI_ANA_WFP_JOB_REPORTS story 57
2.1.2 SAP__FI_ANA_WFP_JOB_OVERVIEW story 58
2.1.3 Financial planning & Analysis Input Forms 60
3 Appendix 63
Workforce Planning for SAP S/4HANA CUSTOMER

Typographic Conventions Error: Reference source not found 2
Document History
Revision Change Date Description

1.0 November 2018 Published version
2.0 February 2019 Published version
3.0 November 2019 Published version
4.0 May 2020 Published version
5.0 February 2021 Update – Documentation only
CUSTOMER
Workforce Planning for SAP S/4HANA Error: Reference source not found 3
1 Workforce Planning for SAP S/4HANA
1.1 Test Description

Check out the Implementor’s Guide with Training Videos
The suite, Financial Planning & Analysis for SAP S/4HANA, is made up of 1) Financial Planning & Analysis 2) Sales Planning and 3) Workforce Planning. The Financial Planning suite for SAP
S/4HANA is available for both Cloud and On-Premise scenarios for SAP S/4HANA. The purpose of this document is to: 1) explain prerequisites and how to implement Workforce Planning for
SAP S/4HANA, and 2) explain how to launch and use planning and analysis stories in SAP Analytics Cloud. . This document explains how to perform workforce planning in SAP Analytics
Cloud based on SAP S/4HANA, SAP Success Factors, and an account-based model. The underlying content accelerates your opportunity to perform workforce planning in the cloud using SAP
solutions. A summary of the content is in the graphic below.
CUSTOMER
.
1.2 Prerequisites and How-to-Implement

This section summarizes all prerequisites and high-level steps implement the scope and conduct testing of models, users, master data, transactional data, and stories. The customer should follow
these steps in order to implement the models/content/stories underlying scope item 3DJ.
CUSTOMER
Within SAP S/4HANA– Pre-planning Steps
SAP Best Practice SAP S/4HANA Scope Summary Notes

Item to Implement
Integration between SAP S/4HANA and Customers should request activation of scope The result of setup will be a SAP S/4HANA
SAP Analytics Cloud (1YB)– if G/L item 1YB and follow instructions in 1YB’s URL, which the customer will use during the
source is SAP S4/HANA Cloud customer guide to setup a communication setup of the connection in SAP Analytics Cloud.
arrangement in SAP S/4HANA in order to
integrate to SAP Analytics Cloud
Financial planning and Analysis (2FM) – Customers should request activation of scope Customers should set time aside to adopt the
if G/L source is SAP S4/HANA item 2FM, which delivers a SAP S/4HANA FPA1 Financial Statement Version in SAP
G/L Account hierarchy (via Financial S/4HANA to their own needs. This includes: 1)
Statement Version FPA1) specifically for mapping new accounts to FPA1 2) removing un-
Note: Available as of SAP S/4HANA Financial planning & Analysis. The accounts necessary accounts from FPA1 3) redefining,
2020 Release and in SAP S/4HANA needed are employee related accounts only. renaming, and/or retagging G/L Account nodes in
Cloud. FPA1 to customer preference.
Employee Integration - Employee Central The JB1 guide includes integration between To be considered if implementing SAP
Integration (JB1) SAP S/4HANA and SAP SuccessFactors S/4HANA, the JB1 guide supports transfer of
Employee Central. employee data (including contingent workers). It
includes basic data, such as employee name and
ID, and contact details, such as workplace
address, e-mail, and telephone information.
Within SAP Analytics Cloud (3DJ implementation steps) – planning Steps
SAP Best Practice Analytics Summary Notes

Configuration Guide to Follow
Import SAP S/4HANA planning/Analysis The 2JX guide included with scope item 3DJ In the lifecycle of using pre-delivered content,
model into SAP Analytics Cloud (2JX)- will instruct the customer how to import the you should import the content just one time,
under scope item 3DJ planning content from the SAP Analytics make your modifications, and then not import the
Cloud Business Content library model again or else your modifications will be
over-written.
Import actual Workforce data into SAP The 3KT guide included with scope item 3DJ The 3KT guide will instruct you how to import
Analytics Cloud (3KT) – under scope will instruct the customer how to import the your own customer data, but you should plan to
item 3DJ customer’s own master data and transaction refer to this guide whenever you re-load data in
data from SAP S/4HANA and Success Factors future planning rounds. You should always look
Employee Central into the SAP Analytics to the latest 3KT guide online and look to
Cloud model covered in Configuration Guide leverage any newly recommended best practices
2JX in the import process.
Implement Best Practice planning process Refer to “Proposed planning Process” in Adjust the plan process as you see fit, including:
in SAP Analytics Cloud section 1.3 of this document for best practice the naming convention of plan versions, the
CUSTOMER
Configuration Guide to Follow
recommendations on how to implement a timing and frequency of import/export processes,
planning process using the pre-configured and the design of input templates, reports, and
content dashboards.
Within SAP Analytics Cloud –Complementary offerings under Financial Planning & Analysis (Optional)

Scope Item to Implement:
Financial Planning & Analysis for SAP Provides model and stories for Financial Planning data in Workforce Planning for SAP
S/4HANA – 2EB Planning & Analysis in SAP Analytics Cloud S4HANA integrates into Financial Planning for
for SAP S/4HANA SAP S/4HANA – 2EB
Sales Planning for SAP S/4HANA – 4DP Provides model and stories for Sales Planning Planning data in Sales Planning integrates into
in SAP Analytics Cloud for SAP S/4HANA Financial Planning & Analysis for SAP
S/4HANA – 2EB (roadmap)
1.1 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 Action Role Comments

Step #
Archive a copy of plan data out of the Follow the plan Copy steps in the SAC Since SAP Analytics Cloud will
working plan version so that you have a configuration guide 'Import SAP S/4HANA Administrator dynamically calculate Default Currency in
1. copy of the last plan locked down – Actual Financial data into SAP Analytics any plan version, you need to archive a set
make sure to reflect desired FX rates into Cloud' - (2JV) of FX rates with any copy of plan
the archived plan version name
Update S4/HANA Cloud Master Data Import the master data for the following SAC Follow the guidance provided within
dimensions (as necessary): Administrator relevant sections of “Import actual
Company Code Workforce data into SAP Analytics Cloud
2.
Building Block Configuration Guide
Cost Center
(3KT)”. Insure that the correct data source
(from S4/HANA Cloud) is selected.
CUSTOMER
Step #
Update SuccessFactors Master Data Import the master data for the following SAC Follow the guidance provided within
dimensions (as necessary): Administrator relevant sections of “Import actual
Location Workforce data into SAP Analytics Cloud
3. Building Block Configuration Guide
Job
(3KT)”. Insure that the correct data source
(from SuccessFactors Employee Central) is
selected.
Update key master data properties Update the following attributes in the SAC These properties are used to direct the
Version dimension: Administrator proper operation of the associated data
StartDate (format: YYYYMM) actions and Planning input template layout
4.
EndDate (format: YYYYMM)
LastMonthofactuals (format: YYYYMM)
CutOver (Flag as “X”)
5. Update hardcoded time values in these Update hardcoded first plan period in the SAC Follow menu path: SAC Home Page >
Data Actions data actions in the following detail sections: Administrator Browse > Processes > Data Actions.
SAP__FI_ANA_IM_WFP_JOB_ADMI 1.10.1.2 “copy annual salary SFSF to SAC Update hardcoded dates (bold font) within
N1 audit Id” identified advanced data actions to current
SAP__FI_ANA_IM_WFP_JOB_ADMI 1.10.2.1 “copy actual to plan – FTE, plan data planning horizon (this will be
N2 expenses” based on current Actual / Plan automated in future releases via master data
time horizon properties).Refer to exact steps in manual
SAP__FI_ANA_IM_WFP_JOB_ADMI
update section of Data Actions
N3 1.10.2.2 “copy actual to plan – latest
salary / wage” based on current Actual /
Plan time horizon
1.10.3.2 “Calc Total Historical expenses
and FTE” (FTE = Full Time Equivalent
employee)
6. Updated hyperlink in New FTE tab Update hyperlink to location of story: SAC This is a one-time step at the start of the
SAP__FI_ANA_WFP_JOB_INPUT_ Administrator implementation, and needs to be repeated
NEW_POSITION in the New Positions tab any time you migrate the model/stories into
of the story a new SAP Analytics Cloud
SAP__FI_ANA_WFP_JOB_INPUT tenant/environment.
7. Update FX rates Go to Browse → Currencies tab → SAC

SAP__FI_ANA_CURRENCY Administrator
Review and edit the USD and EUR rates as or lead
desired for average and closing rate types, planner
See section 1.3.5 for information on the

currency conversion process.
CUSTOMER
Step #
8. Load a new set of actual employee Follow the integration steps in the SAC You will need to decide if you are loading
expenses from SAP S/4HANA into SAP configuration guide: Import actual Administrator the latest month, the latest quarter, or the
Analytics Cloud - including master data Workforce data into SAP Analytics Cloud entire year. One reason you may need to re-
and transaction data (3KT) load more than the latest period is if there
These expenses are to be loaded into Audit are revisions to actuals in prior months that
Id: SAP S/4HANA (S4HC) need to be reflected in SAP Analytics
Cloud.
9. Reconcile actuals in SAP Analytics Follow the integration steps in the SAC By reconciling each time, you are loading
Cloud to SAP S/4HANA configuration guide: Import actual Administrator new data, you gain confidence, and can help
Workforce data into SAP Analytics Cloud identify any issues early in the process and
(3KT) before notifying users that latest results are
available. (see section 1.3.5 for limitations
on currency conversion)
10. Load a new set of actual employee Follow the integration steps in the SAC You will need to decide if you are loading
headcount and annual salary data from configuration guide: Import actual Administrator the latest month, the latest quarter, or the
SAP Success Factors Employee Central Workforce data into SAP Analytics Cloud entire year and coordinate with the SAP
into SAP Analytics Cloud (3KT) S4/HANA Cloud load (section 5). One
reason you may need to re-load more than
the latest period is if there are revisions to
actual headcount and salary data are to be
actuals in prior months that need to be
loaded into Audit Id: Success Factors
reflected in SAP Analytics Cloud.
Employee Central (SFSF_EC)
11. Reconcile actuals in SAP Analytics Follow the integration steps in the SAC By reconciling each time, you are loading
Cloud to SAP Success Factors Employee configuration guide: Import actual Administrator new data, you gain confidence, and can help
Central Workforce data into SAP Analytics Cloud identify any issues early in the process and
(3KT) before notifying users that latest results are
available (see section 1.3.5 for limitations
on currency conversion)
12. Announce the availability of actuals in Use your company's preferred collaboration SAC Announcing you have a new set of actuals
SAP Analytics Cloud to key users. Also, tool. Administrator in SAP Analytics Cloud allows planners
announce which version of plan users and analysts to start variance and trend
should use for variance and plan analysis, before updating the plan.
analysis.
Announcing what version of plan to use in
SAP Analytics Cloud keeps planners and
analysts informed.
CUSTOMER
Step #
13. Clear plan data out of the working plan In SAP Analytics Cloud, go to the Models, SAC
version for periods being to be replaced browse, select the model SAP__FI_ Administrator
by new actuals ANA_IM_WFP_JOB, and use the Delete
Facts icon to clear out data.
14. Turn off data locking Access the control for data locking by SAC Turn off data locking for the actual version
selecting the path Browse →Files → Public Administrator to allow the data action in step 13
→ Models → SAP__FI_ (SAP__FI_
ANA_IM_WFP_JOB → Preferences → ANA_IM_WFP_JOB_ADMIN1) to
Access & Privacy → Data Locking → Off generate the FTE hierarchy from the actual
FTE loads (step 7)
15. Execute data action: Expose “Work Area” hidden tab and SAC Action includes the following details:
SAP__FI_ANA_IM_WFP_JOB_ADMI execute function “Admin 1”: “Process Administrator 1. Extending the FTE load, FTE Hires &
N1 actual Data” data action. FTE Terminations to the FTE hierarchy
on actual data. 2. Copies historical data into the SAC Audit
Trail ID
3. Calculates FTE Annualized Salary from
FTE Annualized Total Salary load per FTE
4. Calculates FTE Transfers based on FTE
Load values for End, Hire and
Terminations, if required
SAP__FI_ANA_IM_WFP_JOB_ADMI execute function “Admin 2”: “Copy actual Administrator 1. Extending the FTE load to the FTE
N2 Data” data action. hierarchy
on plan data. 2. Copies future Hire, Terminations (Retire)
data of current Plan year to Plan version
with Plan View Audit ID
3. Establishes the SAC Audit ID for FTE
Employee
SAP__FI_ANA_IM_WFP_JOB_ADMI execute function “Admin 3”: “Process Administrator 1. Copy actual to plan version
N3 Data” data action.
2. Calculates the 12-month historical ratios
on plan data. for selected account groups by cost center
3. Populates all cost center. location, and
job combinations with calculated historical
ratios
CUSTOMER
Step #
18. Turn ON data locking Access the control for data locking by SAC Turn ON data locking for the actual version
selecting the path Browse → Files → Administrator to prevent planner changes to the data.
Public → Models → SAP__FI_
ANA_IM_WFP_JOB → Preferences →
Access & Privacy → Data Locking → ON
19. Confirm that planning security is correct Do users have the right Company, Cost SAC Note: Execution of data actions Admin 1,
for planning users Center security? Version security? Administrator 2, and 3 require actuals to be open for
planners need to be allowed to input change. Once the administration setup
planning data. process has been completed all actual data
should be set to LOCKED to prevent
changes.
20. Announce the start of planning process Use your company's preferred collaboration SAC Inform planners and analysts where plan
in SAP Analytics Cloud to key users. tool. Administrator data is going to be stored, so they can run
their own reports.
21. Planners and analyst use reports and Review plan and actual FTE plan and SAC planner, Use stories included with scope item 3DJ
dashboards (see section 1. 6 “Report Employee Expenses. SAC Analyst
-SAP__FI_ANA_WFP_JOB_REPORTS
“and 1.7 “Report -
SAP__FI_ANA_WFP_JOB_OVERVIE
W “) to review results
22. Planners input plan data planners input data into SAP Analytics SAC planner Planners use the forms on story
Cloud and use reports to evaluate plan. SAP__FI_ANA_WFP_JOB_INPUT
23. Run post-plan script processing as Run the Data Action Trigger “Process plan SAC planner After the planning users complete their
needed to generate desired plan results Data” (data action as needed (or inputs, these advanced formulas are
“SAP__FI_ANA_WFP_JOB_CALC_PLA SAP executed to generate planned employee
N”) located on the “planning Trigger” tab Administrator expense data.
of the Input Form on their
SAP__FI_ANA_WFP_JOB_INPUT behalf)
24. Planners and analyst use reports and Review financial statements, KPI, trend, SAC planner, Use stories provided under 3DJ: (see
dashboards (in scope item3DJ) to review variance, etc. SAC Analyst section 1. 6
results “SAP__FI_ANA_WFP_JOB_REPORTS
“and 1.7 “Dashboards -
SAP__FI_ANA_WFP_JOB_OVERVIEW
“) to review results
25. Announce the end of planning process in Use your company's preferred collaboration SAC Adjust security to close off write-access if
SAP Analytics Cloud to key users tool. Administrator required.
26. Copy the working plan data into an While in a Story related to the model, use SAC Administrator You also have the option to use an input
archived version. Change security to the Version Manager to save a Version of form and Version Management to copy data
CUSTOMER
Step #
make the archived version read-only. Working plan into an archive plan version. between Versions if the destination version
is new.
27. Repeat the cycle from the top during n/a
next planning round
1.2.1 System Access
Details
System The names of the objects are searchable under Models, Dimensions, or Files in SAP Analytic
Cloud. Or, the SAP Analytics Cloud system administrator should you with the URL to access the
models and stories.
1.2.2 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 - allows for read only access to Please ask your system administrator to assign
Analyst role. information the role to the testers.
The users in SAP Analytics Cloud with planner - allows for input of data in time Please ask your system administrator to assign
planner role. periods within the planning horizon the role to the testers.
The users in SAP Analytics Cloud with Administrator - imports models, copies This role is not used in end-user testing
Administrator role. models, maintains dimensions, imports data,
clears data, sets up user security, establishes
planning time horizon in input templates,
communicates readiness of data and planning
process
CUSTOMER
CUSTOMER
1.2.3 Security
The following model dimensions are suggested to be identified as secured dimensions:
SAP_ALL_COMPANY_CODE (Company Code)
SAP_ALL_COSTCENTER (Cost Center)
VERSION
Access dimension preferences for each secured dimension and check off “Enable Data Access Control”.
SAC administrators require WRITE access to the actuals version to allow the administrative data action SAP__FI_ANA_WFP_JOB_ADMIN1 (section 1.10.1) be executed successfully.
SAC planners/analysts only have READ access to the actual version.
SAC administrators require WRITE access to the plan version so they can execute data actions SAP__FI_ANA_WFP_JOB_ADMIN2 and SAP__FI_ANA_WFP_JOB_ADMIN3 (sections 1.10.2,
and 1.10.3).
SAC planners/analysts require WRITE access to the plan version, their access is also restricted to Company Code and Cost Center security.
CUSTOMER
1.2.4 Data Locking
Data locking for specific regions of data are suggested:
All Time periods and accounts for the actual version should be locked after the successful execution of the three administration functions (1.10.1, 1.10.2, and 1.10.3).
Note: The actual version must remain unlocked to allow the proper functioning of the admin functions which do create some actual records when developing the FTE hierarchy from the
SuccessFactors headcount loads.
Turn on Data Locking for the model in model “Preferences” under Access and Privacy section.
Press the Configure Data Locks Button to access the configuration screen.
CUSTOMER
CUSTOMER
1.1.1 Currency Translation Considerations
In the FP&A 2EB process, the 2JCV Guide identifies the currency translation process as follows: actual data in Company Code Currency and Global Currency
are both loaded to SAP Analytics Cloud. SAP S/4HANA Company Code Currency is loaded to SAP Analytics Cloud Local Currency and Global Currency is
loaded to Default Currency. The Cross Calculation in SAP Analytics Cloud is used to toggle between the currency types. plan data is loaded in Company Code
Currency and Global Currency is calculated by SAP Analytics Cloud.
Unlike FP&A (2EB), the 3DJ process only loads data in Company Code Currency into SAP Analytics Cloud. SAP S/4HANA Company Code Currency is loaded to
SAP Analytics Cloud Local Currency and Global Currency is calculated in SAP Analytics Cloud for both actuals and plan. The Cross Calculation in SAP Analytics
Cloud is used to toggle between the currency types. As a result of this process actual values may differ from source system values due to any mismatch of
currency conversion rates being applied by SAP Analytics Cloud.
In the 3DJ process, the model SAP__FI_ANA_CURRENCY contains the conversion rates used by SAP Analytics Cloud for the 3DJ
SAP__FI_ANA_IM_WFP_JOB model.
Extending the currency translation rates from S4/HANA Cloud may be facilitated via an inspection of internal currency translation rate tables. When determining
rates to be selected for use in the SAP__FI_ANA_CURRENCY model, please note: 1) source currency, 2) effective date of the rate, 3) ratio factors, 4) rate type
(End, Average, etc.), 5) Category restrictions (if any) , 6) and target currency.
FX rates in S4/HANA Cloud can be access directly via Fiori tile “Maintain Exchange Rates”:
Identify the required rates stored within S4/HANA Cloud (the following list is an example of rate types you may encounter, please note that your actual list of rate
types will likely be significantly different):
CUSTOMER
The exchange rate can be quoted directly or indirectly. The quote is direct when the price of one unit of target currency is expressed in terms of source currency.
The quote is indirect when the price of one unit of source currency is expressed in terms of target currency.
Enter extracted rates into the SAP__FI_ANA_CURRENCY model, noting that all rates are multiplied by the source currency value to determine the target
currency value in SAP Analytics Cloud:
CUSTOMER
CUSTOMER
1.3 Data Flow Diagram
The below diagram details the flow of data from the S/4HANA source system and SuccessFactors – Employee Central into the delivered assets in SAC. The model, reports and input forms are
described in the following sections of this document
CUSTOMER
1.4 Model Overview table
The proposed financial planning model for SAP S/4HANA is the following financial model for Profit & Loss activity created in SAP Analytics Cloud. The model is made up of a combination of
critical dimensions sourced from SAP S/4HANA and other dimensions maintained only in SAP Analytics Cloud.
CUSTOMER
Dimension Public Dimension Name Integrated to Integrated to Summary Notes
SAP SuccessFactors
S/4HANA Employee
Central
Audit Trail N/A (Private dimension) No No Keeps track of where data is sourced from so
that import process can be coordinated by data
source if there is more than one data source.
S4HC – Data sourced from S/4HANA and
used for Actuals
SFSF_EC – Data sourced from
SuccessFactors and used for Actuals on
historic data (past)
SAC – Used for planning and presenting
Actual and Plan data together.
PLAN_VIEW – Sourced from SuccessFactors
future Employee (FTE) hire and
termination/retirements data. Not used for
planning but reporting only
Company Code SAP_ALL_COMPANY_CODE Yes Yes (Suggestion: Secure this dimension by
user/role) An organization type dimension that
contains legal company codes. Local currency
is driven from the currency attribute in this
dimension.
S4HC scope item JB1 describes the process
that synchronizes cost centers and company
codes between SFSF EC and S4HC as
specified in section 1.2 (Prerequisites).
Cost Center SAP_ALL_COSTCENTER Yes. SAP Yes (Suggestion: Secure this dimension by
S/4HANA- user/role) Contains cost centers. Company
based Code, Profit Center, and Functional Area are
hierarchy is available as attributes of this dimension,
built and although all three fields are also dimensions.
maintained The currency attribute in this dimension is
manually, informational only and reflects company code
currency, as the driving currency attribute is in
the company code dimension.
S4HC scope item JB1 describes the process
that synchronizes cost centers and company
codes between SFSF EC and S4HC as
specified in section 1.2 (Prerequisites).
CUSTOMER
Account SAP_FI_HR_Account Partially. No Contains the best practice G/L Accounts
SAP (YCOA) available in SAP S/4HANA and is
S/4HANA- supported by a hierarchy built and maintained
based in SAP Analytics Cloud for the initial release.
hierarchy is Also includes SAC specific accounts to
built and facilitate FTE planning and related reporting
maintained measure/drivers.
manually,
Location SAP_HR_USER_LOCATION No Yes Derived from Success Factors FTE and Salary
data
Job Classification SAP_HR_USER_JOBCLASSIFICATION No Yes Derived from Success Factors FTE and Salary
data
Time N/A (System dimension) No No Contains time periods with lowest level of time
= month.
Version N/A (System dimension) No No (Suggestion: Secure this dimension by
user/role) Contains the types of data tracked,
for example ACTUAL and PLAN. Attributes
include StartDate, EndDate, and
LastMonthofactuals, CutOver
CUSTOMER
1.5 Report - SAP__FI_ANA_WFP_JOB_REPORTS
The grid-style reports are all in one story with four tabs. The first three reports are structured in a similar manner with Time/Version user controls. The fourth report has a secondary Time and
Version selection to facilitate comparison reporting.
Report Major User Controls Best Practice Usage Notes

Summary Time & Version This report is a control report at the FTE and Employee Expense Whenever viewing currency across Company
levels. This report provides access to summarized actual and plan Codes, switch to Default Currency if the
data by Company Code, Cost Center, Location, and Job story filter Company Codes have different local currencies.
selections.
KPI Time & Version This report is a fixed report to display work force planning KPIs. By KPIs are formulas maintained in the Account
default, time is in the columns, but you can use Designer to filter to a dimension. The advantage of using KPIs is you
specific time period and then add another Dimension (e.g. Cost can define them once in the model and re-use
Center) to the columns to see a breakdown by that dimension. This them in multiple stories and multiple levels
report provides access to summarized actual and plan data by within the reporting hierarchy.
Company Code, Cost Center, Location, and Job story filter
selections.
CUSTOMER
Report Major User Controls Best Practice Usage Notes
Trend Time & Version This report is your main slice and dice report. By default, it is Refer to the Financial Statement report as a
filtered on the Account = Employee Expenses, shows Cost Centers control total whenever you are trying to confirm
in the rows, and time in the columns. You can use Designer to add a number.
and/or replace dimensions with any combination of dimensions and
accounts you need.
This report provides access to summarized actual and plan data by
selections.
Compare Time & Version Time 1 & Version 1 This report is designed to compare actual to plan, or to review Year- The time selections are setup to allow you to
Time 2 & Version 2 over-Year actuals, or to compare next year's plan to this year's define your target time periods at monthly,
actuals. quarterly, or annual periods. The default detail
This report provides access to summarized actual and plan data by in report is quarterly but can be modified.
selections. Note: For the Variance % column, the delivered
report will not calculate a variance % if the base
period value is negative. This is done using the
following formula and can be modified if
desired:
IF([#Time & Version 2]<=0,

null,
[#Variance]/[#Time & Version 2])
CUSTOMER
1.6 Report - SAP__FI_ANA_WFP_JOB_OVERVIEW
This story provides visualization across a variety of sample features and Actual vs Plan comparison. Explore the story page and look for visualizations that meet your needs best. Most of the
graphics leverage calculated KPIs contained in the account dimension. These KPIs are based on selected account nodes and allow editing of the underlying accounts. If you revise the underlying
formulas in the account dimension, the KPI Calculations in the Account dimension will automatically be updated.
1.1.2 Job Overview - Performance

Performance tab shows FTE balances and net change for selected dimension of Company Code, Cost Center, Location, and Job Classification. Time horizon can be modified as desired by end users.
Dynamic selection on measures for various KPIs are shown as line chart and average employee expenses with FTE count is shown in bar & line chart. Main story filters Company Code, Cost Center,
Location and Job Class are drivers for all these charts.
CUSTOMER
1.1.3 Job Overview – Actuals vs Plan
Actual vs Plan FTE hire, terminations data is shown in bar chart (top left chart) based on time selections for Actual and Plan. Right hand bar chart shows future FTE planned hires,
retires/terminations information from Success Factors (Plan View) is compared with current plan FTE information (SAC Plan).
Heat map charts below shows Actual FTE trends (bottom left chart) by selected dimension (Location, Cost Center, Job Class and Company code) and Plan FTE trends (bottom right chart) along with
variances for previous month/Quarter/Year (time selection).
CUSTOMER
1.7 Input Forms/Story - SAP__FI_ANA_WFP_JOB_INPUT
The input forms leverage either a Cross-tab layout or Forecast-Layout, which merges actuals and plan periods. In either layout, actuals have a black bar at the top and users are restricted from
inputting data into actual periods. plan periods have a white bar at the top and allow user input.
CUSTOMER
You can modify the Cross-tab layout (by hiding and unhiding columns) to display the desired actuals and plan periods. For the selected time horizon, there will be columns for actual and plan in all
time periods. It is necessary to hide unwanted columns (e.g. actual columns in the planning horizon and plan columns prior to the planning horizon).
For single measure-based story, planning input layout (table) uses dynamic Forecast Layout where public dimension “Version” properties are used to drive planning layout automatically.
Updates required for Cross-Tab Layout for new Planning cycle
Unhide columns use the “Hidden” menu option as shown below:
CUSTOMER
Set table details to visible by navigating through the following path:
Turn on table details (three dots at top of grid option menu):
Access information on what columns are hidden from view by selecting “Hidden”:
CUSTOMER
Hide additional columns by highlighting the column and selecting “Hide column/row” as shown below:
Note: For Cross-tab layout with 2 or more measures in columns, make sure you select measure name while selecting columns to hide. If Time is displayed in columns and selected for “Hidden” then
all measure columns corresponding to the month hidden are invisible.
CUSTOMER
Updates required for Rolling Forecast Layout for new Planning cycle
Rolling Forecast layout uses SAP Analytics Cloud (SAC) Version dimension properties to control the monthly display columns. Version dimension properties “StartDate”, “EndDate” and
“CutOver” values control the display columns. During new planning cycle, SAC Administrator updates these property values as desired. A calculation input control is created to get “StartDate”
of planning cycle. A formula (FIND(“X,[d/Version].[p/CutOver],[d/Version].[p/StartDate]) retrieves StartDate. Configuration for Forecast Layout uses “Look back” on Actuals and “Look ahead” on
Plan with months as number of periods to display.
Note: Current SAC system version has bug that it displays Actual columns incorrectly and feature releases is expected to fix the problem.
 Look back of 1 month, look ahead of 12 months for

Plan is used. Due to SAC bug, two months are
displayed instead of one for look back selection of 1.
Future SAC release shall fix these issues.
 Do not delete Input

Control “CutOverDate” displayed at upper right side
of Headcount (FTE) input story.
CUSTOMER
Report Styling for Actual / Plan data entry layout format
The formatting method used to create the black bar over actuals and white bar over plan is “Report – Styling”
CUSTOMER
Note: As delivered, the input form is configured for plan data entry in Currency (corresponding to the Company Code currency). Upon saving and publishing data, SAC will translate all input data
in Default Currency (interpreted as the global currency for the entire organization).
Default Currency is set up within the model “Preferences”:
CUSTOMER
We recommend the use of 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 Publish Data
from Data section of the SAP Analytics Cloud menu bar. Note: During the publication process all necessary currency translations are performed and only after data is published can it be viewed
with both Currency (company code currency) and Default Currency (the model’s global currency) valuations.
Tip: When the version label has an asterisk next to it (i.e. plan*), that means there is plan data to save back to the model.
CUSTOMER
Tabs User Controls Best Practice Usage Notes
Headcount FTE Input Company Code, This form allows the planning of FTE employees specific to SAP Analytics Cloud does not support Characteristic
Cost Center, Location, Company Code, Cost Center, Location, and Job intersection. Derivation, so the template relies on the historical
Job  “FTE Hire” is always a positive number for number hires relationship between Cost Center and Company Code in
this release.
 “FTE Term” is always entered as negative (-)(minus) sign
and represents number employees removed/retired Planners can enter positive (addition to cost center) or
 “FTE Transfer” is used for intercompany transfers and must negative (removal from cost center) values for transfers,
be entered like a journal entry (both increase and decrease) in Terminations should be planned as negative only,
corresponding Company Code, Cost Center, Location, and although there are no restrictions on planning a positive
Job intersection. Outgoing employee as negative (-) and termination number.
incoming employee as positive numbers. Always must be Hires should be planned as positive numbers, although
zero for sum total entries. there are no restrictions on planning a negative hire
number.
Note: 1) Although actuals are displayed in the template, you are FTE Employee is calculated as sum of starting
allowed to enter data only in plan columns. 2) Rolling Forecast headcount plus hires, minus terminations and any
Layout is used. transfers with inbound (+)/ outbound (-). This value is
same as FTE End value at month end.
Upon entering planned headcount calculate plan expenses and
headcount (see 1.10.4)
New Positions None This tab provides a convenient hyperlink to the SAP Analytics Cloud does not support Characteristic
SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITION story Derivation, so the template relies on the historical
(see section 1.7 for additional details) which will allow the relationship between Cost Center and Company Code in
creation of new positions by Company Code, Cost Center, this release.
Location, and Job. NOTE: the hyperlink to the
SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITIO
N story will need to be updated with correct URL
after customer installation.
CUSTOMER
Salary & Merit Company Code, This form allows the planning of an annual salary override and to Annualized salary for the last month of actuals are
Cost Center, Location, plan any merit increases for at a specific Company Code, Cost sourced from uploaded SAP Success Factors Employee
Job Center, Location, and Job intersection. Central data. The second column of the report allows for
a planner override to this loaded annualized salary.
Entered salary and merit increases will be used to calculate plan planner is also able to enter one or more planned merit
expenses and headcount (see 1.10.4) increases at the Company Code, Cost Center, Location,
and Job level.
If a new Location/Job as been created using the
SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITION
story, then only the second column, representing the
annual salary override value is presented to the planner
(the actual annual salary column is blank because there
would have been no historical actuals loaded).
planner enters percentages in the format of number,
example: “12.5” will be represented on screen as
“12.5%” upon input. SAC requires user to enter a
leading zero before decimal point.
% of Salary and Wages Company Code, This form allows the planning of Bonus, Benefits, Payroll Tax, Existing combinations of specific Company Code, Cost
Cost Center, Location, Overtime, and Payroll Other expenses at a specific Company Center, Location, and Job intersections are prepopulated
Job Code, Cost Center, Location, and Job intersection. based upon historical SAP S4/HANA Cloud data via the
These percentages will be used to calculate plan expenses and admin functions described in sections 1.10.1 – 1.10.3.
headcount (see 1.10.4) planner enters percentages in the format of number,
example: “12.5” will be represented on screen as
“12.5%” upon input. SAC requires user to enter a
leading zero before decimal point.
per FTE Rates Company Code, This form allows the planning of per FTE rates for Travel, Other Existing combinations of specific Company Code, Cost
Cost Center, Location, Expenses, Office, and Commission at a specific Company Code, Center, Location, and Job intersections are prepopulated
Job Cost Center, Location, and Job intersection. based upon historical SAP S4/HANA Cloud data via the
These per FTE rates will be used to calculate plan expenses and admin functions described in sections 1.10.1 – 1.10.3.
headcount (see 1.10.4)
Plan Costs report Report Measure This report summarizes plan inputs cost totals per Cost Center, This report provides planner quick overview on the
Location, Job Classification. current plan inputs.
Planning Trigger n/a This form provides access to the main panning functions that Planner may enter all data on all related tabs and execute
calculated all planned expenses based upon prepopulated the planning trigger once, or the planner may execute the
historical rates and user input (see 1.10.4) planning trigger after the completion of every tab.
Exception: if new employee positions are created using
the input story in section 1.9, the new position must first
be fully initialized (see section 1.10.5).
Publish all generated data after execution of the planning
trigger to view data at global currency.
CUSTOMER
Work Area (hidden tab) n/a This form provides access to the three administration triggers used This tab is hidden and is intended for admin use only.
to initialize the application. To unhide the tab, please place the story in edit mode.
Functions can be executed while in edit mode.
Check Report (hidden tab) n/a This report is used to verify the plan inputs. The planner can use this report to verify the overall
planning input values.
Salary & Merit Tab
This form allows the planning of an annual salary override and to plan any merit increases for at a specific Company Code, Cost Center, Location, and Job intersection. This form uses Cross-tab
layout and requires hiding columns as explained in this section earlier. Data action (planning functions) executed by SAC Administrators sets data in correct months as per planning cycle properties.
Salary override can be entered in the Plan Salary / Wage Annual column and any merit increase as percent (%) of monthly salary can be entered. Any merit % increase is cumulative for successive
months. Planner enters percentages in the format of number, example: “12.5” will be represented on screen as “12.5%” upon input.
CUSTOMER
% of Salary & Wages Tab
This form allows the planning of Bonus, Benefits, Payroll Tax, Overtime, and Payroll Other expenses by percentages at a specific Company Code, Cost Center, Location, and Job intersection. These
percentages will be used to calculate plan expenses and headcount.
CUSTOMER
Per FTE rates
This form provides access to the main panning functions that calculated all planned expenses based upon prepopulated historical rates and user input. These per FTE rates will be used to calculate
plan expenses and headcount.
CUSTOMER
Plan Costs Report
This report provides running plan cost total as per user planning inputs.
CUSTOMER
1.8 Input Forms - SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITION
CUSTOMER
New Positions Company Code, The main purpose of this form is to allow planning of new company SAP Analytics Cloud does not support
Cost Center, Location, code/cost center/ location/job combinations not currently available Characteristic Derivation, so the template relies
Job from the actual load. on the historical relationship between Cost
. Center and Company Code in this release.
Upon planning new positions, planner must

execute Process Plan Data action (see section
1.10.5)
1.2 Advanced Formulas
1.2.1 SAP__FI_ANA_WFP_JOB_ADMIN1 - Process Actual Data
After importing actual data and prior to the start of the planning process, this advanced formula is run to carryforward ending actual FTE balances to next period opening balance.
It is run from a Data Action Trigger located on the Work Area tab of the Input Form SAP__FI_ANA_WFP_JOB_INPUT. The Work Area is a hidden tab and can be seen by toggling the story to
Edit mode by a user with appropriate privileges.
CUSTOMER
Advanced Formula Steps in Data Action
Note: “Copy Annual Salary SFSF to SAC Audit ID” Data Action step requires manual update to plan period time value by SAC Administrator as identified in Version dimension properties
For reference, see details of the advanced formula below:
1.2.1.1 FTE_Initialize:
//The data region against which the formulas will be executed.
//-----------------------------------------------------------------------------------
MEMBERSET [d/SAP_FI_HR_Account] = ("FTE_End")
MEMBERSET [d/Time] = [d/Version].[p/StartDate] to [d/Version].[p/EndDate]
MEMBERSET [d/AUDIT_TRAIL]= "SFSF_EC"
//-----------------------------------------------------------------------------------
//Calculation and Data Writing
//-----------------------------------------------------------------------------------
FOREACH [d/Time]
DATA ( [d/SAP_FI_HR_Account] = "FTE_Net_input", [d/AUDIT_TRAIL] = "SAC" ) = RESULTLOOKUP() - RESULTLOOKUP( [d/Time] = PREVIOUS() )
DATA ( [d/SAP_FI_HR_Account] = "FTE_Base",[d/AUDIT_TRAIL]="SAC" ) = RESULTLOOKUP( [d/Time] = PREVIOUS() )
ENDFOR
1.2.1.2 copy annual salary SFSF to SAC audit Id:

//-----------------------------------------------------------------------------------
MEMBERSET [d/SAP_FI_HR_Account] = "SW_Annualized"
CUSTOMER
//MEMBERSET [d/Time] = [d/Version].[p/LastMonthofactuals] to [d/Version].[p/LastMonthofactuals]
MEMBERSET [d/Time] = "201912" //for Plan Year 2020 - Manual Update by Admin
MEMBERSET [d/AUDIT_TRAIL] = "SFSF_EC"
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
// this creates a duplicate record so it can be presented as actual on the Salary input form in the SAC data source. The duplicate is ok because SW_Annualized is not a reported value at aggregate levels and is used only for
input forms
// SW_Annualized_Total is loaded from Success Factors which is Sum of Salaries of employees in Job Class, Location, Cost Center, Company
// SW_Annualized_Total is divided by FTE_End of corresponding Job Class, Location, Cost Center, Company to get Average SW_Annualized Salary per FTE
DATA ( [d/AUDIT_TRAIL] = "SAC" ) = RESULTLOOKUP([d/SAP_FI_HR_Account] = "SW_Annualized_Total") / RESULTLOOKUP([d/SAP_FI_HR_Account] = "FTE_End")
Note: Manual Updates for Data Actions: Update statement containing YYYYMM date with Actual Plan year data as per Version dimension property values.
MEMBERSET [d/Time] = "201912" //for Plan Year 2020 - Manual Update by Admin
1.2.1.3 FTE_Hire_Term_End_Initialize
//-----------------------------------------------------------------------------------
MEMBERSET [d/SAP_FI_HR_Account] = ("FTE_Hire_End","FTE_Term_End")
//----------Time Horizon of Actual Data, Start Date to End Date - Actual version properties
//-----------------------------------------------------------------------------------
// FTE_Term_End from Success Factors comes as a positive number, due to FTE_Term Account Type NFIN, and Account Hierarchy needs this number needs a - negative sign
//-----------------------------------------------------------------------------------
DATA ( [d/SAP_FI_HR_Account] = "FTE_Hire", [d/AUDIT_TRAIL] = "SAC" ) = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_Hire_End" )
DATA ( [d/SAP_FI_HR_Account] = "FTE_Term", [d/AUDIT_TRAIL] = "SAC" ) = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_Term_End" )* -1
1.2.1.4 FTE_Transfer_Initialize
//-----------------------------------------------------------------------------------
CUSTOMER
//-----------------------------------------------------------------------------------
//----------Time Horizon of Actual Data, Start Date to End Date - Actual version properties
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
//Transfers = FTE_End (SFSF_EC) - FTE_Base (last month FTE_End) (SFSF_EC) - FTE_Hire (SAC) - FTE_Term (SAC).
DATA( [d/SAP_FI_HR_Account] = "FTE_Transfer", [d/AUDIT_TRAIL] = "SAC") = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_End")- RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_End", [d/Time]
= PREVIOUS(1))-RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_Hire", [d/AUDIT_TRAIL] = "SAC") - RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_Term", [d/AUDIT_TRAIL] = "SAC") //End-Base-
Hire+Term
// Blank out any zero (0.0) value transfer for better visibility/display
IF RESULTLOOKUP([d/SAP_FI_HR_Account] = "FTE_Transfer", [d/AUDIT_TRAIL] = "SAC") = 0 THEN
DELETE([d/SAP_FI_HR_Account] = "FTE_Transfer", [d/AUDIT_TRAIL] = "SAC")
ENDIF
1.2.2 SAP__FI_ANA_WFP_JOB_ADMIN2 - Copy Actual to Plan

After the administration users complete SAP__FI_ANA_WFP_JOB_ADMIN1 , this advanced formula is executed to copy actual values into plan:
For reference, see details of the advanced formulas below:
Note: Ignore any warning on “Copy actual to plan - FTE, Expenses” section.
CUSTOMER
1.2.2.1 copy actual to plan - FTE, expenses
Note: Manual Updates for Data Actions: Update Filters for Time selection as per Version dimension property values for Actuals data.
CUSTOMER
1.2.2.2 copy actual to plan - latest salary/wage
Note: Manual Updates for Data Actions: Update Filters for Time selection as per Version dimension property values for Actuals data (Last month of Actuals data)
CUSTOMER
1.2.2.3 Copy Actual to Plan – FTE Hire, Term Plan (Future)
Note: Manual Updates for Data Actions: Update Filters for Time selection as per Version dimension property values for Plan data
1.2.3 SAP__FI_ANA_WFP_JOB_ADMIN3 - Process Plan Data
After the administration users complete SAP__FI_ANA_WFP_JOB_ADMIN1 and SAP__FI_ANA_WFP_JOB_ADMIN2, this advanced formula is executed to derive historical ratios and
prepopulate plan drivers. planners can override these historical ratios during the planning cycle.
CUSTOMER
For reference, see details of the advanced formulas below:
Note: “Calc_Total_Historical_Expenses_and_FTE” Data Action step requires manual update to plan period time values by SAC Administrator as identified in Version dimension properties
1.2.3.1 calc_FTE_end_initalize
MEMBERSET [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FTE_All")
// Select planning horizon

//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
FOREACH [d/Time]
DATA ( [d/SAP_FI_HR_Account] = "FTE_Base") = RESULTLOOKUP( [d/Time] = PREVIOUS() )

DATA ( [d/SAP_FI_HR_Account] = "FTE_End") = RESULTLOOKUP()
CUSTOMER
ENDFOR
1.2.3.2 calculate historical expenses and FTE:

//-----------------------------------------------------------------------------------
//selct all employee expenses
MEMBERSET [d/SAP_FI_HR_Account] =( BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/015"), BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FTE_All"))
//Select actual periods in plan category (can't use attributes as this is plan cateogry)
MEMBERSET [d/Time] = "201901" to "201912" //for Plan Year 2020 - Manual Update by Admin
//-----------------------------------------------------------------------------------
//---------- Planning variables
//-----------------------------------------------------------------------------------
VARIABLEMEMBER #temp_Payroll OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Bonus OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Commission OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Benefits OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_PayrollTax OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Overtime OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Payroll_Other OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Travel OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_Office OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_EmpExpOther OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_FTE_Sales OF [d/SAP_FI_HR_Account]
VARIABLEMEMBER #temp_FTE OF [d/SAP_FI_HR_Account]
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
IF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/038") THEN

DATA ([d/SAP_FI_HR_Account] = #temp_Payroll, [d/Time] = "202001") = RESULTLOOKUP()
ELSEIF [d/SAP_FI_HR_Account] = "61020000" THEN

DATA ([d/SAP_FI_HR_Account] = #temp_Bonus, [d/Time] = "202001") = RESULTLOOKUP()
ELSEIF [d/SAP_FI_HR_Account] = "61500000" THEN

CUSTOMER
DATA ([d/SAP_FI_HR_Account] = #temp_Commission, [d/Time] = "202001") = RESULTLOOKUP()
ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/039") THEN

DATA ([d/SAP_FI_HR_Account] = #temp_Benefits, [d/Time] = "202001") = RESULTLOOKUP()

DATA ([d/SAP_FI_HR_Account] = #temp_PayrollTax, [d/Time] = "202001") = RESULTLOOKUP()

DATA ([d/SAP_FI_HR_Account] = #temp_Overtime, [d/Time] = "202001") = RESULTLOOKUP()

DATA ([d/SAP_FI_HR_Account] = #temp_Payroll_Other, [d/Time] = "202001") = RESULTLOOKUP()

DATA ([d/SAP_FI_HR_Account] = #temp_Travel, [d/Time] = "202001") = RESULTLOOKUP()

DATA ([d/SAP_FI_HR_Account] = #temp_Office, [d/Time] = "202001") = RESULTLOOKUP()

DATA ([d/SAP_FI_HR_Account] = #temp_EmpExpOther, [d/Time] = "202001") = RESULTLOOKUP()
ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FTE_All") THEN
// Stores a calculation of 12 month FTE at both Undefined Location/Job and at Location/Job level
IF [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = BASEMEMBER([d/t.S:SAP_HR_USER_JOBCLASSIFICATION].[h/parentId],"SALES") THEN
DATA ([d/SAP_FI_HR_Account] = #temp_FTE_Sales, [d/Time] = "202001",[d/SAP_HR_USER_LOCATION] = "#", [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = "#" ) =
RESULTLOOKUP()
DATA ([d/SAP_FI_HR_Account] = #temp_FTE, [d/Time] = "202001",[d/SAP_HR_USER_LOCATION] = "#", [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = "#" ) = RESULTLOOKUP()
DATA ([d/SAP_FI_HR_Account] = #temp_FTE, [d/Time] = "202001") = RESULTLOOKUP()
ENDIF

ENDIF
CUSTOMER
//-----------------------------------------------------------------------------------Generate Historical Rates
// ADMIN must change fixed Time Constants as per Planning Cycle
// select first Plan month [d/Time] = "202001"
DATA ([d/SAP_FI_HR_Account] = "Benefits_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Benefits ,[d/Time] = [d/Version].[p/StartDate]) /
RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Payroll,[d/Time] = [d/Version].[p/StartDate])),3)
DATA ([d/SAP_FI_HR_Account] = "PayrollTax_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_PayrollTax ,[d/Time] = [d/Version].[p/StartDate]) /
DATA ([d/SAP_FI_HR_Account] = "Overtime_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Overtime ,[d/Time] = [d/Version].[p/StartDate]) /
DATA ([d/SAP_FI_HR_Account] = "PayrollOther_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Payroll_Other ,[d/Time] = [d/Version].[p/StartDate]) /
DATA ([d/SAP_FI_HR_Account] = "Bonus_percent_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Bonus ,[d/Time] = [d/Version].[p/StartDate]) /
DATA ([d/SAP_FI_HR_Account] = "TravelperFTE_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Travel ,[d/Time] = [d/Version].[p/StartDate]) /
RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_FTE,[d/Time] = [d/Version].[p/StartDate])),0)
DATA ([d/SAP_FI_HR_Account] = "OfficeperFTE_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Office ,[d/Time] = [d/Version].[p/StartDate]) /
DATA ([d/SAP_FI_HR_Account] = "EmpExpOtherperFTE_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_EmpExpOther ,[d/Time] = [d/Version].[p/StartDate]) /
DATA ([d/SAP_FI_HR_Account] = "CommissionperFTE_input", [d/Time] = "202001") = ROUND(( RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_Commission ,[d/Time] = [d/Version].[p/StartDate]) /
RESULTLOOKUP([d/SAP_FI_HR_Account] = #temp_FTE_Sales,[d/Time] = [d/Version].[p/StartDate])),0)
Note: Manual Updates for Data Actions:

Update statements containing fixed YYYYMM date as per Version dimension property values.
MEMBERSET [d/Time] = “201901” to "201912" //for Plan Year 2020 - Manual Update by Admin
All statements containing [d/Time] = “202001” //for Plan Year 2020 - Manual Update by Admin
1.2.3.3 calc_total_historical_percent_and_perFTE
//-----------------------------------------------------------------------------------
//Set Configurations Definitions for the Advanced Formulas.
//-----------------------------------------------------------------------------------
//CONFIG.TIME_HIERARCHY = CALENDARYEAR
//CONFIG.GENERATE_UNBOOKED_DATA = OFF
//CONFIG.FLIPPING_SIGN_ACCORDING_ACCTYPE = OFF
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
//select the FTE accounts

CUSTOMER
//Select planning time horizon

//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
DATA ([d/SAP_FI_HR_Account] = "Benefits_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "Benefits_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#", [d/t.S:SAP_HR_USER_JOBCLASSIFICATION]

= "#" ) *RESULTLOOKUP()/RESULTLOOKUP()
DATA ([d/SAP_FI_HR_Account] = "PayrollTax_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "PayrollTax_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
[d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = "#" ) *RESULTLOOKUP()/RESULTLOOKUP()
DATA ([d/SAP_FI_HR_Account] = "Overtime_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "Overtime_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
DATA ([d/SAP_FI_HR_Account] = "PayrollOther_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "PayrollOther_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
DATA ([d/SAP_FI_HR_Account] = "Bonus_percent_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "Bonus_percent_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
DATA ([d/SAP_FI_HR_Account] = "TravelperFTE_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "TravelperFTE_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",

DATA ([d/SAP_FI_HR_Account] = "OfficeperFTE_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "OfficeperFTE_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
DATA ([d/SAP_FI_HR_Account] = "EmpExpOtherperFTE_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "EmpExpOtherperFTE_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
IF [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = BASEMEMBER([d/t.S:SAP_HR_USER_JOBCLASSIFICATION].[h/parentId],"SALES") THEN

DATA ([d/SAP_FI_HR_Account] = "FTE_Sales",[d/SAP_HR_USER_LOCATION] = "#", [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = "#" ) = RESULTLOOKUP()
DATA ([d/SAP_FI_HR_Account] = "CommissionperFTE_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "CommissionperFTE_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",
ENDIF
1.2.4 SAP__FI_ANA_WFP_JOB_CALC_PLAN - Process plan Data

After the planner users complete all salary adjustments, FTE planning, Merit Increases, and override any pre-loaded historical ratios, this advanced formula is executed to calculate employee
expenses.
Edit mode by a user with appropriate
CUSTOMER
1.2.4.1 calc_fte_carryforward
MEMBERSET [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FTE_All")
//Select planning time horizon
MEMBERSET [d/AUDIT_TRAIL] = "SAC"
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
// Carry Ending Balance forward
FOREACH [d/Time]
DATA ( [d/SAP_FI_HR_Account] = "FTE_Base") = RESULTLOOKUP( [d/Time] = PREVIOUS() )
DATA ( [d/SAP_FI_HR_Account] = "FTE_End") = RESULTLOOKUP()
ENDFOR
CUSTOMER
1.2.4.2 calculate salary based on merit
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
CONFIG.GENERATE_UNBOOKED_DATA = ON
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------

//Select planing horizon
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
FOREACH [d/Time]
//CALC Salary with Merits
DATA ([d/SAP_FI_HR_Account] = "SW_Monthly") = (RESULTLOOKUP([d/SAP_FI_HR_Account] = "SW_Annualized", [d/Time] = [d/Version].[p/LastMonthofActuals])/12 )
DATA ( [d/SAP_FI_HR_Account] = "Merit_cumulative" ) = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "Merit_cumulative" , [d/Time] = PREVIOUS() ) + RESULTLOOKUP( [d/SAP_FI_HR_Account]
= "Merit_base")
DATA ( [d/SAP_FI_HR_Account] = "SW_Monthly_merit") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "SW_Monthly")
DATA ( [d/SAP_FI_HR_Account] = "SW_Monthly_merit") = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "SW_Monthly_merit") +RESULTLOOKUP( [d/SAP_FI_HR_Account] = "Merit_cumulative") *
RESULTLOOKUP([d/SAP_FI_HR_Account] = "SW_Monthly")
DATA ( [d/SAP_FI_HR_Account] = "61100000") = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "SW_Monthly_merit") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "FTE_End")

// Calculated an alternative view of Salary without merit increase, so that it can be compared to 61100000
DATA ( [d/SAP_FI_HR_Account] = "SW_NoMerit") = RESULTLOOKUP( [d/SAP_FI_HR_Account] = "SW_Monthly") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "FTE_End")
ENDFOR
1.2.4.3 calculate final plan results

//-----------------------------------------------------------------------------------
CUSTOMER
//-----------------------------------------------------------------------------------
CONFIG.GENERATE_UNBOOKED_DATA = ON
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
//-----------------------------------------------------------------------------------
//CALC Bonus
DATA ( [d/SAP_FI_HR_Account] = "61020000") =ROUND( RESULTLOOKUP( [d/SAP_FI_HR_Account] = "61100000") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "Bonus_percent_input" ) ,0)
//CALC Benefits
DATA ( [d/SAP_FI_HR_Account] = "61061000") =ROUND( RESULTLOOKUP( [d/SAP_FI_HR_Account] = "61100000") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "Benefits_input" ),0)
//CALC Tax
DATA ( [d/SAP_FI_HR_Account] = "61201000") = ROUND(RESULTLOOKUP( [d/SAP_FI_HR_Account] = "61100000") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "PayrollTax_input" ) ,0)
//CALC Overtime
DATA ( [d/SAP_FI_HR_Account] = "61021000") = ROUND( RESULTLOOKUP( [d/SAP_FI_HR_Account] = "61100000") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "Overtime_input" ) ,0)
//CALC Other
DATA ( [d/SAP_FI_HR_Account] = "61010000") =ROUND( RESULTLOOKUP( [d/SAP_FI_HR_Account] = "61100000") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "PayrollOther_input" ) ,0)
//CALC Travel
DATA ( [d/SAP_FI_HR_Account] = "61008000") = ROUND( RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_End") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "TravelperFTE_input" ) ,0)
//CALC Eplyee Expense Other
DATA ( [d/SAP_FI_HR_Account] = "61400000") = ROUND(RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_End") * RESULTLOOKUP([d/SAP_FI_HR_Account] =
"EmpExpOtherperFTE_input" ),0)
//CALC Office
DATA ( [d/SAP_FI_HR_Account] = "65200000") =ROUND( RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_End") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "OfficeperFTE_input" ) ,0)
//Calc Commissions
DATA ( [d/SAP_FI_HR_Account] = "61500000") =ROUND(RESULTLOOKUP( [d/SAP_FI_HR_Account] = "FTE_End") * RESULTLOOKUP([d/SAP_FI_HR_Account] = "CommissionperFTE_input" ),0)
CUSTOMER
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 Reports
1.2.4.4 SAP__FI_ANA_WFP_JOB_REPORTS story
Purpose
Confirm the SAP__FI_ANA_WFP_JOB_REPORTS 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 the SAP Analytics Cloud as a Viewer. The Home - Welcome to SAP Analytics Cloud
screen is displayed.
28.Access the Story Page Open the Browse  Files in the Main Menu. The Files page is displayed.
29.Access the Story Find the story under The Story SAP__FI_ANA_WFP_JOB_REPORTS is
Public → SAP_Content → SAP_HR_Workforce_Planning displayed.
30.Story Displayed Open Story The report will show with plan and/or actual data
SAP__FI_ANA_WFP_JOB_REPORTS referenced from model: SAP__FI_ANA_WFP_JOB
in SAP Cloud Analytics.
31.Review the Summary Page By default, the story displays the Summary page upon Review the Summary page and confirm it responds
opening. to drill-down and other basic control features.
32.Navigate to the KPI Page Click on the KPI page. Review the KPI page and confirm it responds to
basic control features.
CUSTOMER
Comment
33.Navigate to the Trend Page Click on the Trend page. Review the Trend report page and confirm it
responds to drill-down and basic control features.
Confirm the dynamic text - to the left and right
below the black bar - updates as you make changes
to the story filters and input controls.
The report shows Cost Centers in rows for a filtered
set of expense accounts. You can use Designer to add
new or additional dimensions to the rows.
34.Navigate to the Compare Time Click on the Compare Time & Version page. Review the Compare Time & Version page and
& Version Page confirm it responds to drill-down and basic control
features.
Confirm the dynamic text - to the left and right
below the black bar - updates as you make changes
to Story filters and input controls.
Confirm the Time and Version labels at the top of the
numeric columns update as you make new Time and
Version selections.
Experiment changing the Time and Version and
confirm the report responds.
2.1.2 SAP__FI_ANA_WFP_JOB_OVERVIEW story
Purpose
Confirm the SAP__FI_ANA_WFP_JOB_OVERVIEW story with Performance and Actual vs Plan tabs is available and operating properly.
Procedure
Comment
2. Open Analytics Cloud Log on to the SAP Analytics Cloud as a Viewer. The Home - Welcome to SAP Analytics Cloud
screen is displayed.
CUSTOMER
Comment
36.Access the Story Find the story under The Story SAP__FI_ANA_WFP_JOB_OVERVIEW
Public → SAP_Content → SAP_HR_Workforce_Planning is displayed.
37.Story Displayed Open Story The report will show performance data with plan
SAP__FI_ANA_WFP_JOB_OVERVIEW and/or actual data referenced from model:
SAP__FI_ANA_WFP_JOB in SAP Cloud Analytics.
Based on time horizon past data is Actuals and future
data is Plan information
38.Review the Performance Story By default, the story displays the Performance page upon Review the Performance page and confirm it
Page opening. responds to selected dimensions (Company Code,
Cost Center, Location & Job Class) and other basic
control features.
Select and review various measure selections and
note line chart and line & bar chart responds to
selections.
Select different story filters at header level and note
that all charts respond to selections made to
Company Code, Cost Center, Location and Job Class
39.Navigate to the Actual vs Plan Click on the Actual vs Plan tab page. Review the Actual vs Plan page and confirm it
Story Page responds to basic control features.
Update Actual and Plan time horizon (based on
Version dimension property values).
Review FTE hire, terminations and transfers for both
Actual and Plan data.
2.1.3 Financial planning & Analysis Input Forms
Purpose
Confirm that the SAP__FI_ANA_WFP_JOB_INPUT and SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITION stories are available, that actual data refreshes, and that plan data input is possible.
CUSTOMER
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 restricts user
from submitting data into actual periods.
Public → SAP_Content → SAP_HR_Workforce_Planning
41.Access the Story Open Story The Story SAP__FI_ANA_WFP_JOB_INPUT
SAP__FI_ANA_WFP_JOB_INPUT is displayed.
42.Story Displayed By default, the story displays the Headcount (FTE) input The report shows plan and actual data based on
form upon opening. the prescribed planning horizon, referenced from
model: SAP__FI_ANA_WFP_JOB in SAP
Cloud Analytics.
43.Review the Headcount (FTE) This input form is used to plan Headcount at Company Confirm the color-coded bar at top of each
input Page Code, Cost Center, Location, and Job Id based on historical column shows 'black' for actual and 'gray/striped'
data. for plan.
Note: The Headcount (FTE) input page will load with Confirm the input form responds to basic control
actuals in actual periods, followed by plan in plan periods. features, including changing Story filters for
actual periods have a thick black horizontal line at top of Company Code , Cost Center , Location , and
column. plan periods have grey/striped horizontal line at Job.
top of column. Confirm the dynamic text – located at the top of
the form - updates as you make changes to Story
filters.
44.Enter Data in actual Periods on Users are not allowed to impact actuals in this form. To test You should get a message that input is not
the Headcount (FTE) input the restriction, scroll over to actual period (black column) allowed into actual periods. You should find that
Page and input some data and choose Enter. you cannot impact actual periods at all in this
Repeat as needed. form.
45.Enter Data in plan Periods on the Scroll over to plan period (gray/striped column) and input Confirm the data was allowed in the cell and is
Headcount (FTE) input Page plan data and choose Enter. equal to the value you input after processing is
Repeat as needed. done. (Note: if you input into a parent node, the
value will be allocated down to other accounts.
This is expected behavior).
46.Commit the plan Input into Select Version Management from the tool bar and choose After processing, you should see the value is no
Public Version of plan Publish for the plan version. longer highlighted and your value is the same as
you input.
47.Confirm the new plan Data Open SAP__FI_ANA_WFP_JOB_REPORTS and confirm The numbers you input into Headcount (FTE)
Exists in Reports your new plan data is available when run on plan version input form should be available in any plan views
CUSTOMER
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
and you navigate to proper Story filters and input controls. of story SAP__FI_ANA_WFP_JOB_REPORTS.
48.Navigate to the New Positions Click on the New Positions input hyperlink to open the Confirm the input form responds to basic control
Input Page SAP__FI_ANA_WFP_JOB_INPUT_NEW_POSITION features, including changing Story filters for
story. This story allows the planning of new FTEs that were Company Code.
not represented by any actual values imported into SAC. Confirm the dynamic text (above the data grid)
updates as you make changes to Story filters.
49.Enter Data into the New Identify a unique combination of Company Code, Cost Repeat as needed.
Positions Input Page Center, Location, and Job Note (not currently represented
by actual data) and enter Annual Salary/Wage and number
of FTEs. And enter Salary and number of FTEs.
50.Execute data action in New Execute data action “Process Plan Data”. Confirm the data was allowed in the cell and is
Positions Input Page equal to the value you input, after processing is
complete.
51.Commit the plan Input into Select Publish Data from the tool bar and choose Publish for After processing, you should see the value is no
Public Version of plan the plan version. longer highlighted and your value is the same as
you input.
52.Return to the Return to the SAP__FI_ANA_WFP_JOB_INPUT story and The new positions entered in step 11 should be
SAP__FI_ANA_WFP_JOB_IN open the Salary & Merit form. visible. (note: new positions entered in this
PUT story Adjust story filters to set Company Code, Cost Center, manner will not have an historical actual annual
Location, and Job for the same value(s) used to enter data in salary value, only a planned value will be
step 11. displayed.
Enter any merit increases for the plan entries.
53.Navigate to the % of Salary & Adjust story filters to set Company Code, Cost Center, Values can be updated with new planned values
Wages form Location, and Job then enter override values for one or more
selected time periods.
Enter percentages in the format of number, example: “12.5”
will be represented on screen as “12.5%” upon input.
54.Navigate to the Per FTE Rates Adjust story filters to set Company Code, Cost Center, Values can be updated with new planned values
form Location, and Job then enter override values for one or more
selected time periods
55.Navigate to the planning Trigger Execute the data action “Process plan Data”. Data action executes without errors
form
56.Commit the plan Input into Select Publish Data from the tool bar and choose Publish for After processing, you should see the planned
Public Version of plan the plan version. values are no longer highlighted.
57.Confirm the new plan Data Open SAP__FI_ANA_WFP_JOB_REPORTS and confirm The numbers you input into Headcount (FTE)
Exists in Reports your new plan data is available when run on plan version input form should be available in any plan views
and you navigate to proper Story filters and input controls. of story SAP__FI_ANA_WFP_JOB_REPORTS.
CUSTOMER
2 Appendix
For Administrators use to validate data loads and cross check with source system data, a new report is added as hidden story. Users like SAP Analytics Cloud (SAC) Administrators can access the
“Check Report” in edit mode and going into designer tab. Only users with some SAC application development need to edit selections for checking the data validation.
1. Story Filters: Select story filters as required for validating data
2. Version: For displaying both Actual & Plan data, select these versions.
3. Audit Trail: Same as Version. All planning data for current plan year is with SAP Analytics Cloud (SAC) ID.
4. Display is controlled by Rolling Forecast parameters automatically. If selections are wide open, System may not be able to process data and lower level Story filters must be selected to
reduce data display volume. Advanced knowledge is required to update Rolling Forecast parameters.
5. Select Measure: All available measures are selectable. Most accounts are at leaf level and some are at higher node level. Use drill down options from table control.
Drill down selection for Account hierarchy
Version Selection & Edit Filter
Audit Trail Selection & Edit Filter
CUSTOMER
CUSTOMER
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. www.sap.com/contactsap
Textual cross-references to other documents.
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 only as of their CUSTOMER
dates, and they
Workforce Planning for SAP S/4HANA should not be relied upon in Error:
making Reference source
purchasing not found
decisions. 65

3dj s4cld2108 BPD en XX

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3dj s4cld2108 BPD en XX

Uploaded by

Copyright:

Available Formats

Test Script CUSTOMER

1 Workforce Planning for SAP S/4HANA 4

2 End-User Test Procedures 57

Workforce Planning for SAP S/4HANA CUSTOMER

Revision Change Date Description

3.0 November 2019 Published version

4.0 May 2020 Published version

5.0 February 2021 Update – Documentation only

1.1 Test Description

1.2 Prerequisites and How-to-Implement

SAP Best Practice SAP S/4HANA Scope Summary Notes

Within SAP Analytics Cloud (3DJ implementation steps) – planning Steps

SAP Best Practice Analytics Summary Notes

SAP Best Practice Analytics Summary Notes

1.1 Proposed planning Process

Process planning Step Action Role Comments

7. Update FX rates Go to Browse → Currencies tab → SAC

See section 1.3.5 for information on the

1.2.1 System Access

SAP Analytics Cloud

Business Role Name The main functions of role Log On

Report Major User Controls Best Practice Usage Notes

IF([#Time & Version 2]<=0,

1.1.2 Job Overview - Performance

Updates required for Cross-Tab Layout for new Planning cycle

Unhide columns use the “Hidden” menu option as shown below:

Turn on table details (three dots at top of grid option menu):

 Look back of 1 month, look ahead of 12 months for

 Do not delete Input

Default Currency is set up within the model “Preferences”:

Salary & Merit Tab

Upon planning new positions, planner must

1.2 Advanced Formulas

1.2.1 SAP__FI_ANA_WFP_JOB_ADMIN1 - Process Actual Data

For reference, see details of the advanced formula below:

1.2.1.2 copy annual salary SFSF to SAC audit Id:

1.2.2 SAP__FI_ANA_WFP_JOB_ADMIN2 - Copy Actual to Plan

For reference, see details of the advanced formulas below:

1.2.3 SAP__FI_ANA_WFP_JOB_ADMIN3 - Process Plan Data

// Select planning horizon

DATA ( [d/SAP_FI_HR_Account] = "FTE_Base") = RESULTLOOKUP( [d/Time] = PREVIOUS() )

1.2.3.2 calculate historical expenses and FTE:

//The data region against which the formulas will be executed.

IF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/038") THEN

ELSEIF [d/SAP_FI_HR_Account] = "61020000" THEN

ELSEIF [d/SAP_FI_HR_Account] = "61500000" THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/039") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/042") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/041") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/043") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/033") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/027") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FPA1/034") THEN

ELSEIF [d/SAP_FI_HR_Account] = BASEMEMBER([d/SAP_FI_HR_Account].[h/parentId],"FTE_All") THEN

DATA ([d/SAP_FI_HR_Account] = #temp_FTE, [d/Time] = "202001",[d/SAP_HR_USER_LOCATION] = "#", [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = "#" ) = RESULTLOOKUP()

Note: Manual Updates for Data Actions:

//select the FTE accounts

//Select planning time horizon

DATA ([d/SAP_FI_HR_Account] = "Benefits_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "Benefits_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#", [d/t.S:SAP_HR_USER_JOBCLASSIFICATION]

DATA ([d/SAP_FI_HR_Account] = "TravelperFTE_input") = RESULTLOOKUP([d/SAP_FI_HR_Account] = "TravelperFTE_input", [d/Time] = [d/Version].[p/StartDate],[d/SAP_HR_USER_LOCATION] = "#",

IF [d/t.S:SAP_HR_USER_JOBCLASSIFICATION] = BASEMEMBER([d/t.S:SAP_HR_USER_JOBCLASSIFICATION].[h/parentId],"SALES") THEN

1.2.4 SAP__FI_ANA_WFP_JOB_CALC_PLAN - Process plan Data

MEMBERSET [d/SAP_FI_HR_Account] = ("FTE_End")