Test Script

SAP S/4HANA Cloud - 08-07-24

Universal Allocation (2QL_ES)

PUBLIC

Table of Contents

1 Purpose

2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 File Format Requirements
2.5 Preliminary Steps
2.5.1 User Settings - Set Controlling Area
2.5.2 Set Report Relevancy
2.5.3 Replicate Runtime Hierarchy
2.5.4 Open Cost Accounting Period
2.5.5 Situation Handling
2.5.5.1 Manage Situation Types
2.5.5.2 Manage Teams and Responsibilities
2.5.5.3 Finishing up the Situation Type

3 Overview Table

4 Test Procedures
4.1 Import Financial Plan Data
4.1.1 Template for File Upload
4.1.2 Import File
4.2 Import Statistical Key Figure Plan Data
4.2.1 Template for File Upload
4.2.2 Import Statistical Key Figure Plan Data
4.3 Execute Cost Center Plan Assessment Cycle of Shared Expenses
4.4 Allocation Results
4.5 Download and Import Allocation Cycles
4.6 Optional: Simulate Run
4.7 Execute Plan Profit Center Distribution
4.8 Optional: Intercompany Allocation
4.8.1 Record Costs
4.8.2 Create Allocation Cycle
4.8.3 Execute Allocation Cycle
4.9 Optional: Schedule Allocation Run
4.10 Optional: Working with Allocation Groups
4.10.1 Create Allocations in Groups
4.10.2 Run Allocation Groups
4.11 Optional: Manage Cycle Run Groups
4.12 Optional: Manage Allocation Changes
4.13 Analytics
4.13.1 Allocation Tags
4.13.1.1 Create Allocation Tags
4.13.1.2 Assign Allocation Tags
4.13.2 Plan Data Reporting for Cost Centers
4.13.3 View Plan Profit Center Distribution

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 2
1 Purpose

Note Intercompany overhead calculation, settlement, and manual re-postings are supported. Intercompany allocation via Universal Allocation is currently
supported with some limitations.

Overview

The Universal Allocation scope item covers plan and actual allocations. For plan allocations of cost centers in overhead cost controlling, it covers the upload
of cost center plan data and the execution of the plan allocation cycles. Annual planning is supported via cost redistribution through defined allocation cycles,
by definition of sender and receiver rules by fixed amount and percentage. You can control your costs and compare plan and actual costs by allocating the
cost elements to cost centers in overhead cost controlling. For examples of actual allocations, see the Overhead Cost Accounting (J54) test script. Profit cen-
ters are also covered.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each
process step, report, or item is covered in its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the
process but are needed for testing are marked accordingly. Project-specific steps must be added.

Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a
different notation, enter values as appropriate.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 3
2 Prerequisites

This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and busi-
ness conditions.

2.1 System Access

System Details

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

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

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

Cost Accoun- SAP_BR_OVERHEAD_A Overhead Accounting SAP_BR_OVERHEAD_ACCOUNTANT

tant - Over- CCOUNTANT
head

Divisional Ac- SAP_BR_DIVISION_A Divisional Accounting SAP_BR_DIVISION_ACCOUNTANT

countant CCOUNTANT

Cost Accoun- SAP_BR_SALES_AC- Sales Accounting SAP_BR_SALES_ACCOUNTANT

tant - Sales COUNTANT

Configuration SAP_BR_BPC_EXPERT Business Process Configuration / Business Configuration - Fea- SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC /
Expert - Busi- ture Management / Business Process Configuration - Workflow / SAP_CA_SPT_BPC_WORKFLOW_PC / SAP_CA_SPT_IC_LND_BASE_PC /

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 4
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
Template) On

ness Process Manage your Solution / Business Process Configuration - Exten- SAP_EI_SPT_BPC_EXT_PC / SAP_FIN_SPT_BPC_EXPERT_PC /
Configuration sibility Explorer / Business Process Configuration - Finance / SAP_MM_SPT_BIZ_PROC_CONFIGN_PC / SAP_TM_SPT_TRANSPCFG_PC
Business Process Configuration - Procurement / Business Con-
figuration - Transportation

General SAP_BR_GL_ACCOUN- General Ledger SAP_BR_GL_ACCOUNTANT

Ledger Ac- TANT
countant

For details about the business role content, refer to the Maintenance of SAP Fiori Artefacts for SAP S/4HANA section in the Check S/4HANA Technical Settings
(BG0) configuration guide.

2.3 Master Data, Organizational Data, and Other Data

The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the
structure of your company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your com-
pany.
Use your own master data or the following sample data to go through the test procedure.

Data Sample Value De- Comments

tails

OPERATING CONCERN A000

CONTROLLING AREA A000

COMPANY CODE 2410

G/L ACCOUNT 94201000 Cost Element used for Buildings & Periodic Service Allocation.
29500000 A G/L account for allocation clearing must be available. Use your specific clearing GL or use the demo
63005000, 63004000, data 29500000.
94222000,94201000 For optional intercompany.

COST CENTER 24101902,

24101101,
Manufacturing 1 (ES),
24101750,

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 5
Data Sample Value De- Comments
tails

24101401,
24101601

PLAN ALLOCATION CY- OP2410

CLE

For more information on creating master data objects, see the following Master Data Scripts (MDS)
Table 1: Master Data Script Reference
Master Data ID Description

BNM Create Cost Center and Cost Center Group

BNG Create G/L Account and Cost Element

2US Create Universal Allocation Master Data

2.4 File Format Requirements

Format Values:
Plan data must be formatted as a comma separated values file (CSV file).
All organizational units and all master data for which you want to plan must exist in the system.
For the time-dependent organizational units or master data, the following applies :
● It must exist in the period specified in the same data row
● If period 0 is specified, the master data must exist in period 1
● If a special period is specified, the master data must exist in the last normal period of the fiscal year
● If only the fiscal year is provided, the master data must exist at some time during the fiscal year
The source files in this example should use the following values :
● Category, use PLN as default
● Company Code
● Controlling Area
● Ledger
● Cost Center
● Customer Group

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 6
● Account Number
● Fiscal Year
● Posting Period (values defined by fiscal year variant)
● Amount in Global Currency
● Global Currency
Decimal Digits :
The amounts may have a currency sign (for example, €). The import cuts it off and reads the currency code from the next column.
The upload accepts only two decimal digits.
The following decimal marks or thousands indicators may be used :
European format:
● Comma (,) as decimal mark
● Point (.) as thousands indicator
For example, 1.234.567,89
US format:
● Point (.) as decimal mark
● Comma (,) as thousands indicator
For example 1,234,567.89
No decimal mark and no thousands indicator (for example, 12345)
Currency As used by the system, for example, EUR instead of €
CSV Files :
The csv-upload supports the following separators :
● , (comma)
● ; (semi colon)
● . (period)
● | (pipe)
If you use Microsoft Excel to create the CSV file, you can specify the separator in your Microsoft Windows control panel by choosing Region and Language
Formats.
The source CSV files must have the following structure :
1. Row: The technical name of the field for which you want to import data.
2. Row: Any explanatory text, for example, the field description.
3. Row: The characteristics defining the plan data scope of the source file flagged by an X (capitalized or non capitalized). For the values of these characteris-
tics, the plan data from the source file overwrites the existing plan data.
To prevent the plan data scope of a source file becomes too big, the app expects a minimal set of characteristics defining the plan data scope.
You must at least flag the following characteristics :
• Category (CATEGORY)
• Company Code (RBUKRS) or Controlling Area (KOKRS)

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 7
 • Fiscal year (RYEAR)
The app reads the plan data starting from the fourth line.

Note If the third row contains other characters than X, the system assumes that the third row contains plan data and starts reading from there. In this
case, the system uses the following default set of characteristics defining the plan data scope :
● Category (CATEGORY)
● Company Code (RBUKRS)
● Fiscal year (RYEAR)

2.5 Preliminary Steps

2.5.1 User Settings - Set Controlling Area

Purpose

The controlling area must be set before you carry out the first steps in controlling.

Procedure

Step # Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Choose User Preferences Choose the user icon on the top right corner of the screen, and choose Set- The Default Values dialog box displays.
tings.
Choose Default Values.

3 Enter Data On the CO Area field, Controlling area A000 is set for your
enter the following value: A000. user.

Choose Save.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 8
2.5.2 Set Report Relevancy

Purpose

Report relevancy must be done when you execute any reports for the first time. If you make a subsequent change in cost center, profit center, or G/L hierar-
chy, perform this step again to get the latest information.
Also, you must manually replicate set-based hierarchies (such as Cost Center Group or Profit Center Group) and financial statement hierarchies to the back-
end database hierarchy tables. Normally, this would be created as a periodic job that would run in the background.

Procedure

Step Step Name Instruction Expected Result Pass/Fail/Com-

# ment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Set Report Relevancy - Set-Based Hierarchies (F5295). The Set Report Relevancy for Set-Based
Fiori App Hierarchies screen displays.

3 Enter Header Make the following entries and choose Go:

Data Set Class: For example,0101, for the cost center group
Organizational Unit: A000
Set Name: A000
Include Subnodes: Yes

4 Mark as Report In the Set Report Relevancy section, select the row and choose Edit. In the dialog box,
Relevant make the following entries:
Report Relevant: Yes

5 Save Choose Save. Set updated message displays.

Note If you are using the optional procedure Commitment Management and Cost Cen-
ter Budgeting, repeat steps 1-5 with the following entries instead:
Set Class: 0102
Organizational Unit: YCOA
Set Name: YBA000_CE
Include Subnodes: <Select>

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 9
2.5.3 Replicate Runtime Hierarchy

Purpose

You must manually replicate set-based hierarchies (such as Cost Center Group or Profit Center Group) and financial statement hierarchies to the backend
database hierarchy tables. Normally, this would be created as a periodic job that would run in the background.

Procedure

Step Step Name Instruction Expected Result Pass/Fail/Com-

# ment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead.

2 Access the SAP Fiori App Open Schedule Overhead Accounting Jobs (F3767). The Application Jobs screen dis-
plays.

3 Create Choose the Create button. The New Job: Replicate Runtime
Hierarchy (SAP) view displays.

4 Header Data for Hierarchy ID In the header area, make the following entries and choose Schedule:
0101/A000/A000 Job Template: Replicate Runtime Hierarchy (SAP)
Job Name: <Enter a text>
Choose the Step 2 button.
Start Immediately: Select
Choose the Step 3 button.
In the Create Hierarchy area, make the following entry:
Hierarchy ID: 0101/A000/A000

Note If you are using the optional procedure Commitment Management and Cost
Center Budgeting, follow steps 1-4, but make the following entries instead:
Job Template: Manually Replicate Runtime Hierarchy
Hierarchy ID: 0102/YCOA/YBA000_CE

5 Hierarchy ID YPS2 Repeat the above steps using hierarchy ID YPS2.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 10
2.5.4 Open Cost Accounting Period

Use

The posting period for cost accounting must be open.

Prerequisites

Check and ensure that the cost accounting period is open for the period you are working.

Note For more details on this step, see the Manage Posting Periods step in Accounting and Financial Close (J58) script.

Procedure

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

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

countant.

2 Access the SAP Fiori Open Manage Posting Periods - Cost Accounting (F4684). The Manage Posting Periods - Cost Accounting view
App displays.

3 Check/Open Period Make the following entries and choose Go: Controlling posting period is now open.
Company Code: 2410
Fiscal Year: <current fiscal year>

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 11
2.5.5 Situation Handling

2.5.5.1 Manage Situation Types

Purpose

This template is used for situation handling that informs specific users when a condition is met. In this example the user, Overhead Accountant, receives a
notification (icon located in the upper right side the window) when the allocation run triggers a warning or error in the execution of universal allocation run.
For information on the Situation Template for Allocation Runs, see https://help.sap.com/docs/SAP_S4HANA_CLOUD/a630d57fc5004c6383e7a81efee7a8bb/
e929d26943b34cc889681e8f9eaadc77.html.

Note This requires the configuration expert role for business processes.

For additional information on situation handling, see the generic setup documentation for object-based Situation Type
https://help.sap.com/docs/SAP_S4HANA_CLOUD/a630d57fc5004c6383e7a81efee7a8bb/19460b5cabb746b0b5198fc82f14335a.html.

Note Though you may be able to set up the alerts, there is no error test data provided and therefore notification may not be triggered during testing.

Prerequisite

Ensure that Situation Handling (31N) scope item is installed before you execute this step.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as Configuration Expert - Business

Process Configuration.

2 Access the SAP Fiori Open Manage Situation Types (F2947). The Manage Situation Types view displays.
App

3 Copy the Situation In the Search field, enter FIN_ALLOCATION_RUN_WARNING_ERROR

Template and choose Go.
Select the checkbox for the row FIN_ALLOCATION_RUN_WARNING_ER-

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 12
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

ROR, and then choose Copy.

4 Maintain Admin Infor- Make the following entries and choose Create (accept all warning and The initial situation type for allocation run warning or
mation enable messages): error message is created.
ID: <enter your template name>
Name: <enter your template description>
Situation Monitoring:
Monitor Instances: <selected>

2.5.5.2 Manage Teams and Responsibilities

Procedure

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

1 Log On Log on to the SAP Fiori launchpad as Configuration Expert - Business

Process Configuration.

2 Access the SAP Fiori App Open Manage Teams and Responsibilities. The Manage Teams and Responsibilities
Select any Manage Teams and Responsibilities app, and remove any view displays.
preset category filters.
In Category, enter UNIVALLOC and choose Go.
If no results exist, go the next step to create a new team.

3 Manage Teams and Respon- Choose Create. A New Situation Type view displays.
sibilites Make the following entries and choose Create (accept all warning and
enable messages):
Name: <Team Name>
Global ID: <Global ID name>
Type: Universal Allocations (UNIVALLOC)
Team Owner

Universal Allocation (2QL_ES)

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

Business Partner: <BPC expert ID>

Team Members
Business Partner: <Overhead Accountant user ID>

Note To find the overhead accountant user ID, use the search func-
tion with:

Last name: OverheadAccountant

Error The table contains errors. Filter Items is corrected by entry:
Functions: <Cost Center run>

2.5.5.3 Finishing up the Situation Type

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as Configuration Expert - Business Process
Configuration.

2 Access the SAP Fiori Open Manage Situation Types (F2947). The Manage Situation Types view displays.
App

3 Assign Responsibility to Select Category: Situation Types and using the filter function enter the situa- The initial situation type for allocation run
the Template tion type name you created in the previous step and choose Go. warning or error message is created.
Select the situation type and choose the > sign on the right of the page.
In the Recipients section, under Responsibility by Teams, choose Add Team
Category, make the following entries and choose Save:
ID: <UNIVALLOC>
Functions: <Cost Center run>

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 14
3 Overview Table

This scope item consists of several process steps provided in the table below.

Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for per-
forming the typical tasks of a business role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.

Import Financial Data

Process Step Business Role Transaction/App Expected Results

Template for File Upload [page ] 17 Cost Accountant - Overhead Import Financial Plan Data (F1711) Predelivered template file is prepared for upload.

Import File [page ] 19 Cost Accountant - Overhead Import Financial Plan Data (F1711) File is imported.

Upload Statistical Key Figure Plan Data

Process Step Business Role Transaction/App Expected Results

Template for File Upload [page ] 20 This procedure occurs outside the system.

Import Statistical Key Figure Plan Data [page ] Cost Accountant - Over- Import Statistical Key Figure Plan Data Statistical key figure plan data file imports success-
22 head (F3779) fully.

Process Step Business Role Transaction/App Expected Results

Execute Cost Center Plan Assessment Cycle of Cost Accountant - Manage Allocations (F3338) Assessment cycle is executed.
Shared Expenses [page ] 23 Overhead

Allocation Results [page ] 25 Cost Accountant - Allocation Results (F4363) The existing allocation results can be reviewed after a success-
Overhead ful run.

Download and Import Allocation Cycles [page ] 26 Cost Accountant - Manage Allocations (F3338) The existing allocation cycles can be downloaded, changed
Overhead and re-imported.

Optional: Simulate Run [page ] 28 Cost Accountant - Manage Allocations (F3338) The simulation run shows how many postings would occur
Overhead based on the cycle's definition.

Execute Plan Profit Center Distribution [page ] 29 Divisional Accoun- Manage Allocations (F3338) The profit center distribution is executed.
tant

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 15
Process Step Business Role Transaction/App Expected Results

Record Costs [page ] 31 General Ledger Ac- Post General Journal Entries The journal entry is posted.
countant (F0718)

Create Allocation Cycle [page ] 34 Cost Accountant - Manage Allocations (F3338) The allocation cycle is created.
Overhead

Execute Allocation Cycle [page ] 36 Cost Accountant - Run Allocations (F3548) The allocation cycle is executed and docments are posted.
Overhead

Optional: Schedule Allocation Run [page ] 37 Cost Accountant - Schedule Overhead Accounting You can schedule allocation cycles based on a schedule or set
Overhead Jobs (F3767). time.
Divisional Accoun- Schedule Division Accounting
tant Jobs (F5288).
Cost Accountant - Schedule Sales Accounting Jobs
Sales (F1483)

Process Step Business Role Transaction/App Expected Results

Create Allocations in Groups [page ] 39 Cost Accountant - Overhead Manage Global Hierarchies (F2918) The hierarchy is now active.

Run Allocation Groups [page ] 41 Cost Accountant - Overhead Run Allocations (F3548) The run is created.

Optional: Manage Cycle Run Groups [page ] 42 Cost Accountant - Overhead Manage Cycle Run Groups (F4935). A cycle group is created.

Optional: Manage Allocation Changes [page ] 44 Cost Accountant - Overhead Manage Allocation Changes (F7272) You can view the version history of a cycle.

Analytics

Process Step Business Role Transaction/App Expected Results

Create Allocation Tags [page ] 45 Cost Accountant - Overhead Manage Allocation Tags (F4523) Allocation tags are created.

Assign Allocation Tags [page ] 46 Cost Accountant - Overhead Manage Allocation Tags (F4523) Allocation tags are assigned.

Plan Data Reporting for Cost Centers [page ] 47 Cost Accountant - Overhead Cost Centers - Plan/Actual The newly allocated plan data displays.

View Plan Profit Center Distribution [page ] 48 Divisional Accountant Profit Centers - Plan/Actual (F2889) The profit center distribution plan displays.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 16
4 Test Procedures

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

4.1 Import Financial Plan Data

4.1.1 Template for File Upload

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Context

In this activity, you download the predelivered template and prepare your plan data for upload. Use the sample data in the preceding labeled sections to pop-
ulate the template.

Note Planning for Cost Centers, Internal Orders, and WBS elements automatically derive the Profit Center and Segment organizational fields that are re-
flected in the corresponding Plan/Actual report.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 17
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead . The SAP Fiori launchpad
displays.

2 Access the SAP Open Import Financial Plan Data (F1711) . The Import Financial Plan
Fiori app Dataview displays.

3 Select Template Choose the Download Templates button. In the Download Templates view, select the template file by
placing the cursor directly on the line Cost Center Planning and choose Close.
Open the csv file.

4 Save Template Save the file in the CSV format on your desktop.

5 Update Tem- Open the template and maintain the following data listed below.
plate

Maintain the following cost center plan data. Note that this is an example. Check global currency, year, and period as applicable:

CATEGORY RYEAR POPER RBUKRS RCNTR RACCT KSL RKCUR

Plan Category General Ledger Fiscal Year Posting Period Company Code Cost Center Account Number Amount in Global Currency Global Currency

X X X X X

PLN 2022 09 2410 24101750 61003000 100000 USD

PLN 2022 10 2410 24101750 61003000 200000 USD

PLN 2022 11 2410 24101750 61003000 300000 USD

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 18
4.1.2 Import File

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

The app performs the following checks:

1.The app checks whether the values in the source file are valid. If required, it returns a list of error messages.
You must correct the values in the source file until they are all valid before you can proceed.
2. If all values are valid, the app checks all versions, fiscal years, posting periods, and company codes that are contained in the source file.
● If no plan data exists in the system for any combination of these four characteristics, you can directly import the plan data.
● If plan data exists in the system for any combination of these four characteristics, the app displays the affected values. It assumes that you want to com-
pletely replace the existing plan data by the new plan data import.

Note One source file should therefore always contain full plan data sets for a certain combination of version, company code, and fiscal year (including all
posting periods).

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Import Financial Plan Data (F1711) .

Fiori app

3 Enter Source File Enter the following values: The Block Asset Processing view displays.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 19
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

Source File:
<Your .CSV file that contains your plan>
Choose Enter.

4 File Check The upload performs a check to ensure the format is correct. The selected file contains data replacing or deleting the
Correct any error message that appears. data message that appears.

5 Review Note the informational messages. The list of the data uploaded appears.
Your plan data import will incorporate X lines from CSV file. For more
information, go to the Preview List.
Select the links in the messages to review data, and choose the Back
button.

6 Import Choose Import Source File. Import successful

message appears.

4.2 Import Statistical Key Figure Plan Data

Context

Plan statistical key figures are used to create relative weighted values for use in allocations like overhead. Common statistical key figures include headcount
and square footage.

4.2.1 Template for File Upload

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 20
Tester Name: Duration:

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

Context

In this activity, you download the predelivered template and prepare your plan data for upload. Depending on the scope of your solution, the actual data you
fill the template with would differ. In this step, you download the Cost Center Statistical Key Figures template. Use the sample data in the preceding labeled
sections to populate the template.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad
displays.

2 Access the SAP Open Import Statistical Key Figure Plan Data (F3779). The Import Financial Plan
Fiori app Dataview displays.

3 Select Tem- Choose the Download Templates button. In the Download Templates view, select the template file by
plate placing the cursor directly on the line Cost Center Statistical Key Figures and choose Close.
Open the csv file.

4 Save Template Save the file in the CSV format on your desktop.

5 Update Tem- Open the template and maintain the following data listed below.
plate

Review the following statistical key figure plan data:

CATEGORY RYEAR POPER RBUKRS RCNTR STAGR MSL RUNIT

Plan Category General Ledger Fiscal Year Posting Period Company Code Cost Center Statistical Key Figure Quantity Quantity Unit

X X X X X X

PLN 2022 11 2410 24101101 1001 100 PC

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 21
CATEGORY RYEAR POPER RBUKRS RCNTR STAGR MSL RUNIT

PLN 2022 11 2410 Manufacturing 1 (ES) 1001 50 PC

4.2.2 Import Statistical Key Figure Plan Data

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - The SAP Fiori launchpad displays.
Overhead.

2 Access the SAP Fiori Open Import Statistical Key Figure Plan Data (F3779). The Import Statistical Key Figure Plan Data (F3779)
app screen displays.

3 Enter Source File Use the Browse button to select the CSV extension file you The Plan Data Scope for the CSV file uploads.
wish to upload. The upload performs a check to ensure that the format
Enter the following Field Value: is correct.
Source File : Corrections can be made if any error messages appear.
Your .CSV file that contains your plan
Choose Enter

4 Import Choose Import Source File. The file import is successful.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 22
4.3 Execute Cost Center Plan Assessment Cycle of Shared Expenses

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

In this activity, you execute a plan assessment cycle (cost center). Both cost centers and wbs elements can be used as receivers in the plan assessment cy-
cle. In this example, cost center as receiver is demonstrated.

Prerequisites

The plan assessment cycle demo data has been created for testing. For details on how to create your own plan assessment cycle defining senders and re-
ceivers, see the Create Universal Allocation Master Data (2US) master data script.

Procedure

Test Test Step Instruction Expected Result Pass / Fail /

Step # Name Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - The SAP Fiori launchpad displays.
Overhead.

2 Access the Open Manage Allocations (F3338). The Manage Allocations screen displays.
SAP Fiori App

3 Input Initial Make the following entries and choose the Go button: The Allocation Cycles view displays.
Screen ● Allocation Context: Cost Centers

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 23
Test Test Step Instruction Expected Result Pass / Fail /
Step # Name Comment

● Allocation Cycle: OP2410

● Company Code: 2410
● Allocation Type: Overhead Allocation
● Ledger : 0L

4 Select Alloca- Select the allocation cycle row and then choose the > to the The Manage Allocations view displays.
tion Cycle right of the allocation cycle row.

5 Edit Alloca- Do the following: Note Selection criteria for statistical key figures can be single values,
tion Cycle ● Under Segments, select the segment and choose the > to ranges or groups. Groups of Statistical key figures can be created by us-
the right of the segment row. ing Manage Global Hierarchies (F2918) app.
● Choose the Receiver Basis tab.
● Make the following entry:
Var. Portion Type: Stat. Key Figures - Plan (SKF-1)
Selection Criteria:
Stat. key figure*
Value Type: Single Value
Single Entry/From: 1001
● Save the entry.

6 Select Alloca- Select the allocation cycle row and choose the Run button. The Run Allocations screen displays.
tion Cycle

7 Test Run Select the allocation cycle row and choose the Test Run but- The Run Allocation(s) - Test Run screen displays.
ton.

8 Input Values Make the following entries and choose Validate. You get a success message. If everything looks correct, you can repeat the
Test Run Name: <enter your desired value> steps above and choose Run instead of Test Run.

Ledger: 0L
Fiscal Period From: <current period and year>
Fiscal Period To: <curent period and year>
To review the results, choose Go. Viewing the completed run,
you can further drill into the report to view specific senders
and receivers, and values.

9 Check for No- While in the Overhead Accountant overhead window, check if The allocation run triggers a warning or error in the execution of universal
tifications a notification is generated (icon located on the upper right allocation run. If no notification, the run had no error.
side the window).

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 24
4.4 Allocation Results

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Context

In this activity, existing allocation results can be reviewed after a successful run.

Procedure

Test Test Step Instruction Expected Result Pass / Fail /

Step # Name Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Ac- The SAP Fiori launchpad displays.
countant - Overhead.

2 Access the Open Allocation Results (F4363). The Allocation Result view displays.
SAP Fiori App

Note The Show Increments button adds previous incremental postings of in-
cluded cycles into journal entries view. Postings are grouped by date and sorted
chronologically from latest to oldest.

3 Enter Values Make the following entries and choose the Go but-
in Search ton:
View Type: Run

4 Select the Run Select the allocation you had executed in the previ- An overview detail of the allocation executed can be seen via the various tabs.
ous step and choose the Details button on the right

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 25
Test Test Step Instruction Expected Result Pass / Fail /
Step # Name Comment

of the screen.

5 View Network In the same view, choose the Network Graph but- The graphical view of the data displays.
Graph ton on the right of the screen.

6 Change To further refine the views, choose the Group By

Grouping View button.
For example, in the Group by window, make the fol-
lowing entry:
First Level: Functional Area

4.5 Download and Import Allocation Cycles

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Context

In this activity, existing allocation cycles can be downloaded, changed and re-imported.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 26
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launch-
pad displays.

2 Access the SAP Open Manage Allocations (F3338). The Manage Alloca-
Fiori App tions view displays.

3 Input Initial Make the following entry and choose the Go button: The Allocation Cycles
Screen ● Allocation Cycle: OP2410 view displays.

4 Allocation Cycle Select the allocation cycle row.

5 Download Alloca- Choose the Upload/Download Template button. In the Upload new values window, select Download Tem-
tion Cycle plate with Selected Data and save to your local drive.

6 Change Value On your desktop, open the file and replace the cycle value from OP2410 to ZXXXX. Do this for all tabs in
the Excel sheet where OP2410 is present (Cycle, Segment, Senders, Receivers, Receiver Basis).

7 Manage Alloca- Go back to Manage Allocations (F3338) app. The Manage Alloca-
tions app tions view displays.

8 Upload Cycles Choose the Upload/Download Template button. In the Upload new values window, choose Upload.

9 Upload Excel In your local file open window, select your Excel file created in the previous step and choose Open.
Choose Confirm.

10 Postpending During postpending, you can make additional corrections or changes to the file.
Choose the Senders tab and choose Edit.

11 Update Sender Make the following entries and choose Save:

Cost center Replace the cost center 24101750 with another cost center within the same company code, for example
Manufacturing 1 (ES).

12 Submit New Allo- Choose Apply and exit the screen. New allocation is cre-
cation Cycle ated.

Note You can also import values via the Import Allocation Data - Values (F5596) app.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 27
4.6 Optional: Simulate Run

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

Allocations can be complex and have long runtimes and dumps. The simulation run shows how many postings would occur based on the cycle's definition de-
rived from the actual or planned data. If several potential records exist, you may want to adjust the cycle or the run parameters.

Prerequisite

An existing allocation cycle.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Manage Allocations (F3338). The Manage Allocations screen displays.
Fiori App

3 Select Allocation Using the Search field, enter the recently uploaded allocation and choose Go. The Detail screen of the Manage Allocations dis-
Select the checkbox next to the allocation and choose Details. plays.

4 Input Initial Choose the Run button. On the Create new run screen, choose Test Run. Make The simulation run shows how many postings
Screen

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 28
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

the following entries and choose Validate and Run: would occur based on the cycle's definition.
● Ledger: 0L
● Fiscal Period From: for example, 005.2022
● Fiscal Period To: for example, 005.2022

4.7 Execute Plan Profit Center Distribution

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

Using plan profit center distribution, it is possible to distribute balance sheet account balances to and from various profit centers.

Prerequisites

1. A G/L account for allocation clearing must be available. Create G/L 29500000 CO Allocation Clearing using GL 29500100 as a reference. For details on how
to create the G/L, refer to Create G/L Account and Cost Element (BNG) test script.
2. Assign splitting rule via configuration activity Define Document Splitting Characteristics for Controlling for copying values from 29500100 to 29500000.
3. The plan assessment cycle demo data has been created for testing and is ready to use. For details on how to create your own plan assessment cycle
defining senders and receivers, see the Create Universal Allocation Master Data (2US) test script.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 29
Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Divisional Accountant. The SAP Fiori launchpad displays.

2 Access the SAP Open Manage Allocations (F3338). The Manage Allocations view displays.
Fiori App

3 Input Initial Screen Make the following entries and choose the Go button: The assessment is done.
Allocation Context: Profit Centers
Allocation Type: Distribution
Ledger: 0L
Company Code: 2410
Allocation Cycle: OPPCD24

4 Review Allocation Do the following:

Cycle ● Select the allocation cycle row and choose the > sign.
● In the Manage Allocations view, choose the Segments tab
and select Edit.
● Select the segment row and choose the > sign. Review seg-
ment tabs (Rules, Senders).
● Choose the Sender Basis tab and change the amount to
1000.
● Choose the Check Segment button.
● Choose the Save button.

5 Run Allocation Select the allocation cycle row and choose the Run button. The Run Allocations screen displays.

6 Test Run Select the allocation cycle row and choose the Test Run button. The Run Allocation(s) - Test Run screen displays.

7 Input Values Make the following entries and choose Validate and Run. A success log displays. To review the results, choose the
Test Run Name: <enter your desired value> Display Run Result button.

Ledger: 0L
Fiscal Period From: <current period and year>
Fiscal Period To: <curent period and year>

Tip To reverse an assessment posting, use the app Run Allocations (F3548) and choose Go. Select the allocation cycle job and choose Reverse.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 30
4.8 Optional: Intercompany Allocation

4.8.1 Record Costs

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

Intercompany allocations are possible by creating an allocation using a settlement or an allocation structure. This example uses an allocation structure.

Note Currently allocations for cost centers on actual data utilized the leading ledger is supported. Receivers can be either cost centers, WBS elements.

Also note the new intercompany (ICO) allocations behave differently compared to the cost center allocations in Universal Allocation: The ICO allocations cal-
culate values from the data in the leading ledger and post the same results to all ledgers, thus acting somehow like a prima-nota posting. In contrast, regular
cost center allocations in the Universal Allocation operate for each ledger explicitly.
The following limitations currently apply:
• Intercompany cycles must not be defined as iterative or cumulative cycles.
• Cannot explicitly include transaction amounts or transaction quantities.
• Each segment, exactly one sender company code must be specified.

Prerequisites

The following demo data is already provided for creating the intercompany universal allocation with the allocation structure based on the script.
Allocation structures, cost element groups, and intercompany settings must be maintained based on your specific business needs and are described below:

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 31
Allocation Structure: Universal Allocation structure shell is delivered as standard content and must be modified based on your specific user requirements via
the configuration activity Maintain Allocation Structures.
Allocation Structure: UA Universal Allocation Structure:

Line Description Source Cost Element Group Assessment Cost Element

10 Rents UA100 94201000

20 Other costs UA200 94222000

Two empty cost element groups UA100 and UA200 are also delivered in standard content with no G/L accounts assigned and can be maintained via the Edit
Cost Element Group app to suit your requirements. For the demo/test purposes we have assigned two GL accounts listed below:

Cost Element Groups GL Assignment Description

UA100 63005000 Office/Building Rent

UA200 63004000 Insurance

Intercompany Clearing must also be maintained via configuration activity Automatic Account Determination.
For demo/test purposes, we have maintained the following:

Costs/Rev Account Cost/Rev Account to Description Source Cost Element Group Assessment Cost Element

94201000 Buildings & Periodic Service 70030000 70030000

94220000 COPA Assessment 70030000 70030000

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

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

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 32
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

2 Access the SAP Fiori Open Post General Journal Entries (F0718). The Post General Journal Entries view displays.
App

3 Enter Journal Entries In the Header pane, make the following entries and choose the Go but-
Header Data ton:
Journal Entry Date: <current date>
Posting Date: <current date>
Period: <current period, for example, 05>
Journal Entry Type: SA
Company Code: 2410
Transaction Currency: EUR

4 Enter Line Item Data In Line Items (2), make the following entries and press Enter: An overview detail of the allocation executed
Company Code: 2410 can be see via the various tabs.

G/L Account: For example, 63005000

Debit: amount, for example, 100000>

Note Make the entry in the debit or credit column as appropriate.

Tax Code: V0
Cost Center: 24101750

5 Enter Second Line De- In Line Items (2), to add another line, select the Add Line Item button The graphical view of the data is displayed.
tail at the bottom right and press Enter:
Company Code: 2410
G/L Account: For example, 11001000
Credit: <amount, for example, 100000>

Note Total debit amount shown (that is, Debit Amount + Tax Rate
amount, based on the tax code entered).
Next, make the following entries:
Value date: <Current date>
House Bank: DEBK1
House Bank Account: DEAC1

Note The value date is required for cash accounts.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 33
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

6 Post Choose Post. Make a note of the document number. The journal entry is posted.

7 Create a Second Post- Repeat steps 3 to 6 with G/L Account 63004000, cost center 10101750,
ing with G/L and credit/debit amount 2000.

4.8.2 Create Allocation Cycle

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This activity creates the allocation cycles incorporating the allocation structure.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Manage Allocations (F3338). The Manage Allocations screen displays.
Fiori App

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 34
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

3 Create Cycle Choose the Create button and select Create New Cycle.
Header

4 Input Initial Make the following entries and choose the Create button: The Allocation: Create Plan Overhead Allocation
Screen Allocation Cycle: <enter a cycle ID beginning with Z> Cycle: Header Data view displays.

Allocation Context: Cost Centers

Allocation Type: Intercompany Allocation
Ledger : 0L
Valid From: 01/01/2021
Valid To: 12/31/9999
Cycle description: <enter a cycle description>
Actual/Plan: Actual

5 Change Value In the Segments tab, choose Create and make the following entries: Allocation cycle is created. Make note of the
Segment Name: <any> name as it will be required in the next step.

Segment Description: <any>

Choose OK.
In the Rules section, make the following entries:
Sender Rule: Posted amounts
Allocation Structure: UA
Receiver Rule: Fixed percentages
In the Senders section, make the following entries:
Company Code:
● Value Type: Single Value
● Single Entry/From: 2410
Account Number:
● Value Type: Group
● Group: <use search help to select UA100 (Group ID 0102YCOAUA100)>
Cost Center:
● Value Type: Single Value
● Single Entry/From: 24101750
In the Receivers section, choose Add. In the following dialog box, select Cost Cen-
ter and choose Add.
Cost Center: <see the note below>

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 35
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

Note This should be the receiving company code’s cost center. Though com-
pany codes are not entered directly, they are inferred via the cost center.

In the Receiver Basis tab, make the following entry.

Percentage: 100
Save the entries.

4.8.3 Execute Allocation Cycle

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This activity executes the allocation cycle created in the previous step.

Prerequisite

Universal Allocation is created.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 36
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Run Allocations (F3548). The Run Allocations screen displays.
Fiori App

3 Input Initial Screen Choose the Add button. The Select: Allocation Cycles for the Run
dialog box displays.

4 Allocation and Cy- Using the search field, enter the recently created allocation and choose Go. Select
cle the cycle from the list and choose OK.

5 Run Choose the Run button. On the Run Allocation(s) - Live Run screen, make the fol- The cycle is then executed and docu-
lowing entries and choose Validate and Run. ments are posted.
Test Run Name: <enter your desired value>
Ledger: 0L
Fiscal Period From: <current period and year>
Fiscal Period To: <curent period and year>

4.9 Optional: Schedule Allocation Run

Purpose

In addition to running a single allocation, it is possible to schedule allocation cycles based on a schedule or set time.

Procedure

Step Step Name Instruction Expected Result Pass/Fail/Com-

# ment

1 Log On Log on to the SAP Fiori launchpad as either Cost Accountant - Overhead, Divisional Accountant, The role and app used depends on the

Universal Allocation (2QL_ES)

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

or Cost Accountant - Sales. actual type of allocation that is run.

2 Access the For overhead allocations, open Schedule Overhead Accounting Jobs (F3767). The Application Jobs screen displays.
SAP Fiori For Profit Center allocations, open Schedule Division Accounting Jobs (F5288).
App
For Profitability (COPA) allocations, open Schedule Sales Accounting Jobs (F1483).

3 Create Choose the Create button. The New Job: Actual Cost Rate Calcula-
tion screen displays.

4 Template In the header area, make the following entries and choose Step 2:
Selection Job Template: <Based on the respective roles, select the desired template, for ex-
ample, Universal Allocation Run - Cost Centers (SAP), or Universal Allocation
Run - Profit Centers (SAP) or Universal Allocation Run - Margin Analysis (SAP)>

Tip Delete the entry to see all the job templates available.

Job Name: <Enter a text>

5 Scheduling Make the following entries and choose Step 3:

Options Start Immediately: Select

Note You can also select the Define Recurrence Pattern to schedule in advance or on a reg-
ular schedule.
Start: <Accept the default>

6 Parameters Make the following entries and choose Check to validate your entries: A message that you can go ahead and
Cycle Parameters schedule the job appears if the check is
successful, else make the required cor-
Ledger: For example, 0L
rections.
Allocation Type: <Choose a valid type based on the cycle chosen>
Actual/Plan: <Select based on the cycle chosen>
Cycle/Group
Use Cycle: For example, Test Run
Master Data
Cycle Selection: <Your cycle>
Run Parameters
Run Type: For example, Test Run

Universal Allocation (2QL_ES)

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

Run Name: <Any>

Run Ledger: For example, 0L
Fiscal Year: <current year>
Fiscal Period From: <current period>
Fiscal Period To: <current period>

7 Schedule Once the check is successful, choose Schedule. The job is scheduled.

4.10 Optional: Working with Allocation Groups

4.10.1 Create Allocations in Groups

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

In this activity, you group allocation cycles together to run in a specific sequence using groups. The first step is create a hierarchy sequence. Once created,
this sequence can be maintained and adjusted within the allocation run.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 39
Prerequisite

Planned allocation cycles must be created in the system to view sender and receiver information. Planned cost center data and planned statistical key figures
must be posted in the SAP system.

Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Open Manage Global Hierarchies (F2918). The Manage Global Hierarchies
Fiori App view displays.

3 Input Initial Screen Choose the Create button. The Create New Hierarchy dialog
box displays.

4 New Hierarchy Make the following entries and choose the Create button:
● Type: Universal Allocations Hierarchy
● Hierarchy ID: <any ID>
● Hierarchy Description: <enter a description>
● Allocation Context: Cost Centers
● Allocation Type: Overhead Allocation
● Ledger : 0L
● Actual/Plan. Indicator: Plan

5 Select Hierarchy Select the newly created hierarchy row and choose the > button. The Universal Allocations Hierarchy
view displays.

6 Adding Allocations Choose the Edit button and then choose the + button. In the Add Node dialog box,
make the following entries and choose OK:
● Select Allocation Cycle
● Allocation Cycle: <select an allocation cycle>

Note This step can repeat to add as many allocation cycles in your desired se-
quence run.

7 Save and Activate Choose the Save button and then choose the Activate button. The hierarchy is now active.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 40
4.10.2 Run Allocation Groups

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

In this activity, this sequence can be maintained and adjusted within the allocation run.

Prerequisite

Planned cost center data and planned statistical key figures must be posted in the SAP system. A Universal Allocation Hierarchy must exist.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad dis-
plays.

2 Access the SAP Open Run Allocations (F3548). The Run Allocationsscreen dis-
Fiori App plays.

3 Input Initial Choose the Add button. The Select: Allocation Cycles for
Screen the Run dialog box displays.

4 Add Hierarchy Choose the Add Hierarchy tab. Make the following entries and choose the Go button: The Run Allocations screen dis-

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 41
Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

● Allocation Context: Cost Centers plays.

● Ledger : 0L
● Allocation Type: Overhead Allocation
● Actual/Plan: Plan

5 Select Hierarchy Select your recently created hierarchy and choose OK.

6 Making Se- In the Run Allocations view, you can select individual allocation cycles and move them. To move an The sequence is changed.
quence Changes allocation cycle, select an allocation within your hierarchy and choose the Move up or Move down
arrows.

7 Run Hierarchy Select the Cycle/Group checkbox to select all allocations. Choose the Test Run button. Make the The run is created.
following entries and choose Validate.
Test Run Name: <enter your desired value>
Ledger: 0L
Fiscal Period From: <current period and year>
Fiscal Period To: <curent period and year>

Note If the test run is successful, you can then choose the Run button.

4.11 Optional: Manage Cycle Run Groups

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 42
Purpose

When cycles are initially created, they are assigned to a generic default processing group. If multiple allocation cycles are chosen in a run execution, they are
run one cycle at a time (one after the other). This optional step allows the parallel processing of cycles via groups which reduces the time to run all the cycles
requested. Cycles that are assigned to a different group would always be processed in parallel, thus reducing the run time. The example below describes how
to create these assigned cycles to parallel processing groups.

Prerequisite

Universal allocation is created.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad dis-
plays.

2 Access the SAP Fiori Open Manage Cycle Run Groups (F4935). The Manage Cycle Run
App Groups view displays.

3 Create Group Choose Create. Make the following entries and choose Save: The allocation cycle group
● Cycle Run Group: <any 4 characters> is created.

● Object Description: <any>

● Ledger: 0L
● Allocation Context: Cost Centers
● Allocation Type: Overhead Allocation
● Actual/Plan: Plan

4 Add Allocation Cy- Select the cycle run group recently created and choose Assign. Allocation cycle group is
cles to Group In the Select: Allocation Cycles for Group XXX dialog box, use the search function to find the de- created.
sired allocation cycles you want run together as a group and choose Assign.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 43
4.12 Optional: Manage Allocation Changes

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

When cycles are initially created, the version is set. Versions are generated either through a live run (provided there have been changes made between live
runs) or upon deletion of a cycle.

Prerequisite

Allocation cycles must exist.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Over- The SAP Fiori launchpad displays.
head.

2 Access the SAP Fiori App Open Manage Allocation Changes (F7272). The Manage Allocation Changes view dis-
plays.

3 Enter Data Make the following entry and choose Go: The list of allocation cycles display.
● Company Code: 2410

4 Select your Allocation Cycle Select your allocation cycle, and choose the Select Version but- You can view the version history of a cycle.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 44
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

ton.

Note You can use the Allocation Results (F4363) to find out the version in which the cycle was run, but only when using live run mode. To find the version
ID information in the Allocation Results, choose the Settings button and select Version ID (note that the Version ID column does not appear by default).

4.13 Analytics

4.13.1 Allocation Tags

4.13.1.1 Create Allocation Tags

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Context

In this activity, allocation tags are used to label allocation cycles with tags. Allocation tags can be used for better organization of allocation process.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 45
Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Overhead. The SAP Fiori launchpad displays.

2 Access the SAP Fiori App Open Manage Allocation Tags (F4523). The Allocation Tag view displays.

3 Enter Values Make the following entries and choose the Create button: The newly created tag is ready to
Tag ID: <enter an ID beginning with Z> use.

Tag name: <enter a tag description>

4.13.1.2 Assign Allocation Tags

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Context

In this activity, you can use allocation tags to label allocation cycles with tags. Allocation tags can be used for better organization of allocation process. They
are used as selection criteria for various reports making it easier to view them collectively.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 46
Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Over- The SAP Fiori launchpad displays.
head.

2 Access the SAP Fiori Open Manage Allocation Tags (F4523). The Manage Allocation Tags view displays.
App

3 Enter Values Make the following entry and choose Go:

Allocation Tags: <enter an ID that has been previously
created>

4 Assign Allocation Select the allocation tag row and choose Assign. The Assign Allocation Tag window displays.
Tag

5 Assign Allocation Select the company code-specific allocation cycles you want to Tags are now assigned and are used as selection crite-
Cycles tag and choose Assign. ria in various reports.

4.13.2 Plan Data Reporting for Cost Centers

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Context

In this activity, you run the actual data reporting for cost centers.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 47
Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Cost Accoun- The SAP Fiori launchpad displays.
tant - Overhead.

2 Access the SAP Fiori Open Cost Centers - Plan/Actual. The Cost Centers - Plan/Actuals screen displays.
App

3 Selection Criteria Make the following entries and choose Go: Scroll to the Plan Amount in CC Crcy and you can see the newly
Ledger: 0L allocated plan data.

Fiscal Year of Ledger: <Current year>

Plan Category: PLN
Key Date: <Current date>
Company Code: 2410

4.13.3 View Plan Profit Center Distribution

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

In this activity, you view the profit center distribution.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 48
Procedure

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

1 Log On Log on to the SAP Fiori launchpad as a Divisional Ac- The SAP Fiori launchpad displays.
countant.

2 Access the SAP Fiori Open Profit Centers - Plan/Actual (F2889). The Prompts dialog box displays.
App

3 Selection Criteria Make the following entries:

Ledger: 0L
Ledger Fiscal Year: <Current year>
Planning Category: PLN
Company Code: 2410
Key Date: <Current date>

4 Choose Choose OK. Using the report filters on profit centers, you can see the al-
locations.

Universal Allocation (2QL_ES)

Test Procedures PUBLIC 49
Typographic Conventions

Type Style Description

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

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

EXAMPLE Technical names of system objects. These include report names, program names, transaction
codes, table names, and key concepts of a programming language when they are surrounded
by body text, for example, SELECT and 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 . © 2024 SAP SE or an SAP affiliate company. All rights re-
served.
No part of this publication may be reproduced or transmitted
in any form or for any purpose without the express permis-
sion of SAP SE or an SAP affiliate company. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distribu-
tors contain proprietary software components of other soft-
ware vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate
company for informational purposes only, without representa-
tion or warranty of any kind, and SAP or its affiliated compa-
nies shall not be liable for errors or omissions with respect to
the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in
the express warranty statements accompanying such prod-
ucts and services, if any. Nothing herein should be construed
as constituting an additional warranty.
SAP and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Ger-
many and other countries. All other product and service
names mentioned are the trademarks of their respective
companies.

See www.sap.com/copyright for additional trade-

Universal Allocation (2QL_ES) mark information and notices.
Test Procedures PUBLIC 50