Test Script

SAP S/4HANA Cloud - 06-07-23

Event-Based Revenue Recognition - Project-Based

Sales (4GQ_DE)

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 Business Conditions
2.5 Preliminary Steps
2.5.1 Set Report Relevancy
2.5.2 Project Profitability Report
2.5.3 Maintain Financial Statement Versions
2.5.4 Replicate Runtime Hierarchy
2.5.5 Check and Update Derivation of Recognition Key for Project-Based Sales Documents

3 Overview Table

4 Test Procedures
4.1 Monitor Revenue Recognition (Event-Based): Projects
4.2 Manage Real-Time Revenue Recognition Issues
4.3 Run Revenue Recognition: Projects
4.4 Manage Revenue Recognition Issues: Projects
4.5 Optional: Revenue Recognition Reversal
4.6 Project Actual Data Reporting
5 Appendix
5.1 Reverse Month-End Revenue Recognition Postings
5.2 Inspect Revenue Recognition Postings

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 2
1 Purpose

Overview

In this scenario, you create an enterprise project using the Project with Revenue profile. You then assign this project to sales order items to capture the costs and revenues of sales order processing.
The accounting object is the WBS billing element you assign to the sales order items. The actual cost of the project is considered from the sales order item goods issue. You can also assign additional
costs to the project, such as time confirmation. Revenue recognition is triggered by each accounting event, enabling real-time margin analysis. If necessary, period-end closing corrects real-time rev-
enue recognition postings. The functionality is provided for dedicated sales order item categories; the supported scenarios are continuously enhanced.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.

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

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix 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 business conditions.

2.1 System Access

System Details

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

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

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

Configuration SAP_BR_BPC_EXPERT Configuration Expert - Business Process Configuration / Business Configuration - SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC /
Expert - Busi- Feature Management / BPC Expert Workflow Space / Business Process Configura- SAP_CA_SPT_BPC_WORKFLOW_PC / SAP_CA_SPT_IC_LND_BASE_PC
ness Process tion – Manage your Solution / Business Process Configuration - Extensibility Ex- / SAP_EI_SPT_BPC_EXT_PC / SAP_FIN_SPT_BPC_EXPERT_PC /
Configuration plorer / Business Process Configuration – Finance / Materials Management - Busi- SAP_MM_SPT_BIZ_PROC_CONFIGN_PC /
ness Process Configuration / Transportation Business Process Configuration SAP_TM_SPT_TRANSPCFG_PC

Cost Accoun- SAP_BR_OVERHEAD_A Cost Accountant - Overhead SAP_BR_OVERHEAD_ACCOUNTANT

tant - Overhead CCOUNTANT

Cost Accoun- SAP_BR_SALES_AC- Cost Accountant - Sales SAP_BR_SALES_ACCOUNTANT

tant - Sales COUNTANT

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 4
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 company.
Use your own master data or the following sample data to go through the test procedure.

Data Sample Value Details Comments

Controlling area A000 Controlling Area A000

Company code 1010 Company Code 1010

Cost Center 10101902, 10101903 Cost Centers

Activity Types T001-T006

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

BNN Create Activity Type and Activity Type Group

2.4 Business Conditions

Before this scope item can be tested, the following business conditions must be met.

Scope Item Business Condition

4I9 - Project All steps of test script must be completed.

Control – Sales
Note Engineering-to-Order (ETO) covers event-based revenue recognition via material with strategy group-E2, requirement type E21 with requirement class E21, item category TAN, CBXN, CB2,
CBLN, CBAO, and RA key EPMFC- EPM. Project cost-based PoC production variance/price difference of ETO are considered in revenue recognition PoC calculation via source line YPD-Price
Differences and Production Variances. Produced material are considered in PoC during consumption to project.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 5
2.5 Preliminary Steps

2.5.1 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 hierarchy, 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 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/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 Open Set Report Relevancy - Set-Based Hierarchies (F5295). The Set Report Relevancy for Set-Based Hierar-
App chies screen displays.

3 Enter Header Data
Make the following entries and choose Go:
Set Class: For example,0101, for the cost center group
Organizational Unit: A000
Set Name: A000
Include Subnodes: Yes

4 Mark as Report Rel- In the Set Report Relevancy section, select the row and choose Edit. In the dialog box, make the following en-
evant tries:
Report Relevant: Yes

5 Save Choose Save. Data is saved.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 6
 Step # Step Name Instruction Expected Result Pass/Fail/Comment

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

2.5.2 Project Profitability Report

Purpose

The SAP Project Profitability report comes with predelivered KPIs (see table below). In SAP S/4HANA cloud, these KPIs are linked to the predelivered financial statement version (FSV) YPS2
(GLs) via semantic tags.

Project KPI Associated Seman- Linked FSV node YPS2

tic Tag

Billed Rev- BILL_REV 23- Revenue

enue

Actual Cost ACT_COST 24- Material Costs, 26- Costs third party, 27- Labor Costs, 28- Manufact. costs Setup time, 29- Manufact. costs Machine Time, 30- Overhead costs-Material, 33- Licenses Cost, 36-
Overhead costs-Production, 29- Manufact. costs Machine Time, 47- Time recording cost, 48- Travel Cost, 49- Purchased Services, 50- Overhead Cost Admin, 51- Other Miscellaneous
Cost, 52- Hardware Cost, 56-Settlement Cost via Maintenance Order, 57- Secondary GL Settlement Cost via FXA and GL

Recognized RECO_REV #20- Net Sales/Revenue

Revenue

Recognized RECO_COS #38- Cost of Goods Sold

COS

Recognized REC_MARGIN #12- CM II

Margin

Revenue Ad- ADJ_REV #25- Revenue Adjustments

justment

COS Adjust- ADJ_COS #45- Rev rec cost adjustments

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 7
 Project KPI Associated Seman- Linked FSV node YPS2
tic Tag

ment

Deferred DEF_COST #44- Deferred Cost

COS

Deferred DEF_REV #42- Deferred Revenue

Revenue

Accrued ACR_REV #41- Accrued Revenue

Revenue

Accrued ACR_COST #43- Accrued Cost

COS

Reserves

Margin in Calculated
Percent

Note If you want to add your own G/L accounts or create additional nodes in FSV YPS2 that are relevant for Project Profitability report, the G/L or the new node must be under one of the exist-
ing nodes (non-calculated one). See the next step for details on how to update FSV.

2.5.3 Maintain Financial Statement Versions

Purpose

In this activity, you maintain the financial statement (FS) version. This activity must be carried out only if you choose to add additional G/L accounts.

Note You can access and use Manage Financial Statement Versions (OB58) as a General Ledger Accountant to display financial statement version data. However, changes can only be made
and saved using the procedure below.

Caution This test step is relevant only if the new Q2P maintenance mode for G/L accounts is switched on. In case you are not on new Q2P for G/Ls, you need to use the Manage Financial State-
ment Versions (OB58) app.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 8
It is important that all G/L accounts used for revenue/deductions in a project/product profitability must be included and mapped to the Financial Statement Version YPS2 and tagged to a single re-
spective semantic tag. Note that if you are just adding GL to an existing predelivered node, tags are already mapped. This is essential as many functionalities in project reporting and budgeting use
these values to report all costs booked.
There are two factors to consider:
1. Assign all the G/Ls relevant for cost booking under any existing node/item under Cost of Goods Sold. All the predelivered existing items are already mapped.
2. Create a new node/item under Cost of Goods Sold. All nodes/items must be mapped to semantic tag ACT_COST and an individual tag. For example, material cost is mapped to overall cost tag
ACT_COST and individual tag MATCST.

Note This step is only required if you add a new node/item under Cost of Goods Sold. If you are using project budgeting, the budget controls are via semantic tags. In the budget, you can either
map ACT_COST tag or any other child level tag as long as it is a part of overall ACT_COST and assigned to FSV YPS2.

Procedure

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
1. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2. Open Manage Your Solution (F1241).
3. If necessary, change the country by choosing Set Local Version.
4. Choose Configure Your Solution.
5. Make the following entries:
Application Area: Finance
Sub Application Area: General Ledger
6. For the row with Item Name of Chart of Accounts, choose Details (>).
7. For the Define Financial Statement Versions row, choose Configure.

Note If you cannot find the configuration activity, the Q2P maintenance mode for FSVs is not active for your system. Complete the changes with the Manage Financial Statement Versions
(OB58) app (part of General Ledger Accountant).

8. Continue with the procedure in the table below.

SAP Central Business Configuration:
1. Log on to the project experience in SAP Central Business Configuration.
2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view, search for the Define Financial Statement Versions activity.
3. Choose Open Documentation for the found line item to see more details about this configuration activity.
4. Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
5. Continue with the procedure in the following table.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

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

1 Select Financial Statement Ver- Select the following financial statement version and choose the Financial Statement Items button. The Change Financial Statement Version view
sion FS Version: YPS2 displays.

2 New Node Drill at the top nodes until you find the Cost of Goods Sold node. To add your new node, choose the
Create Items button.

3 Save Choose Save.

Add Semantic Tags to Newly Created Node

Purpose

In this activity, you assign semantic tags to the newly created node.

Prerequisites

Before you do this step, you need to know the item number for the newly created item. To find this item number:
● Open the Manage Financial Statement Versions (OB58) app as a General Ledger Accountant.
● In the Change View "Financial Statement Versions": Overview view, select the YPS2 financial statement version and choose the Financial Statement Items button.
● Choose Menu > Settings > Change , in the Change Settings dialog box, select Item keys visible and choose the Continue button. Note the number of the new items created.

Procedure

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
1. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2. Open Manage Your Solution (F1241).
3. Choose Configure Your Solution.
4. Make the following entries:
Application Area: Finance

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 10
 Sub Application Area: General Ledger
5. For the row with Item Name of Chart of Accountss, choose Details (>).
6. For the Assign Semantic Tags to Financial Statement Versions row, choose Configure.

Note If you cannot find the SSCUI, the Q2P maintenance mode for FSVs is not active for your system. Complete the changes with Assign Semantic Tags to FSV (FINSC_FAGL2SEMTA)
app (part of General Ledger Accountant).

7. Continue with the procedure in the table below.

SAP Central Business Configuration:
1. Log on to the project experience in SAP Central Business Configuration.
2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab.
3. Search for the Assign Semantic Tags to Financial Statement Versions activity and choose Go to Activity.
4. Continue with the procedure in the following table.

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

1 New Entries Choose the New Entries button. The New Entry dialog box displays.

2 New Entry Type Select Assign Semantic Tag to FS Item and choose Continue. The New Entries: Details of Added Entries view dis-
plays.

3 Enter Data Make the following entries and choose Save:

FS Version: YPS2
FS Items: <The new item you created as part of the Prerequisites section
in this step>
Semantic Tag: ACT_COST
Repeat the step with individual tag. Select the tag from existing available tags.

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

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 11
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.

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

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

4 Enter Header Data
In the header area, make the following entries and choose Schedule:
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: YPS2

Note Repeat the step for hierarchy ID 0102/YCOA/YBA000_CE.

2.5.5 Check and Update Derivation of Recognition Key for Project-Based Sales Documents

Purpose

In the activity, you can check and update derivation of recognition key for project-based sales documents.

Procedure

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
1. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2. Open Manage Your Solution (F1241).
3. If necessary, change the country by choosing Set Local Version.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 12
4. Choose Configure Your Solution.
5. Make the following entries:
Application Area: Finance
Sub Application Area: Profitability Analysis
6. For the row with Item Name of Revenue Recognition, choose Details (>).
7. For the displayed row, choose Details (>).
8. For the Derivation of Recognition Key for Projects row, choose Configure.
9. Continue with the procedure in the following table.
SAP Central Business Configuration:
1. Log on to the project experience in SAP Central Business Configuration.
2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view, search for the Derivation of Recognition Key for Projects activity.
3. Choose Open Documentation for the found line item to see more details about this configuration activity.
4. Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
5. Continue with the procedure in the following table.

Step # Step Name Instruction Expected Result Pass / Fail /

Comment

1 Add/Change Entry for Required
Item Category
Choose the New Entries button and make The following item categories are supported in event-based revenue recognition and based on your scope activated
the following entries: and business requirements, you must ensure that the derivation is set for all used item categories.
Company Code: <enter your com- The allowed item categories are TAN, CBAO, CTAX, CTAD, CBTC, CBTD, TAD, TAX, CBTA, TAQ, CBTQ,
pany code> CB1, CB1C, CB2, CB2C, CB3, CB4, CBAB, CBLN, CBTN, CBXB, CBXN, CMHD, CPHD, DB1, DB2, DBAB,
Item Category: <for example, TAN> TADN, TAXN.
Material : <for example, *>
Note The RA key is represented by RecKeyArea 200.
Note Keep material as * if the same
RA key is valid for all the materials.

Recognition Key: <for example,

EPMFC>
Save the entries.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 13
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 performing the typical tasks of a business
role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.

Process Step, Report or Item Business Role App Name Expected Results

Monitor Revenue Recognition (Event- Cost Accountant Event-Based Revenue Recognition - Project documents are reviewed.
Based): Projects [page ] 15 - Sales Projects (F4767)

Manage Real-Time Revenue Recogni- Cost Accountant Manage Real-Time Revenue Recog- Posting entries where no corresponding real time revenue recognition posting exists are listed and the necessary correc-
tion Issues [page ] 16 - Sales nition Issues (F4101) tions can be made.

Run Revenue Recognition: Projects Cost Accountant Run Revenue Recognition - Projects Values for real-time revenue and cost adjustment for professional service with sales order integration based on cost-
[page ] 17 - Sales (F4277). based POC (default RA key EPMFC) or RA EPMCC-completed contract method are posted.

Manage Revenue Recognition Issues: Cost Accountant Manage Revenue Recognition Issues Resolve Revenue recognition issues.
Projects [page ] 18 - Sales - Projects (F4100)

Optional: Revenue Recognition Rever- Cost Accountant Revenue Recognition Reversal The document is reversed.
sal [page ] 19 - Sales (F4869)

Project Actual Data Reporting [page ] Cost Accountant Projects - Actuals (F0942A) You can view actual figures based on your selection criteria.
19 - Sales

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 14
4 Test Procedures

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

4.1 Monitor Revenue Recognition (Event-Based): Projects

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

Event-based revenue recognition calculates and posts real-time revenue and cost adjustment for professional service with sales order integration based on cost-based POC (default RA key EPMFC)
or RA EPMCC-completed contract method.
Processes that don't write a general ledger entry don't result in any real-time revenue recognition postings. For example, changes of plan data don't directly result in revenue recognition postings. Pe-
riod-end-closing postings (periodic revenue recognition) correct the event-based postings. After the period-end-closing, the posted values are correct and no separate settlement is required any
longer.

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

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

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

2 Access the SAP Fiori Open Event-Based Revenue Recognition - Projects The Revenue Recognition - (Event-Based) (2) - Projects view displays.
App (F4767).

3 Enter Selection Crite- Make the following entries and choose Go: Your project revenue recognition details are shown.
ria Company Code: 1010
Project Definition: <enter your definition>

4 Review Detail Select your billing element and choose the Details but- The project detail is now shown for the current period and includes details such as project status and
ton. periodic view/charts.

Note To view a different period, choose the Set Parameters tab and change to another To Period
value.

4.2 Manage Real-Time Revenue Recognition Issues

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

During cost or revenue posting on the cost object, errors that stop real time revenue postings can occur. This activity allows you to review these posting entries where no corresponding real time rev-
enue recognition posting exists and make the necessary corrections. All errors must be addressed prior to the month end revenue recognition month end process.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 16
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 -

Sales.

2 Access the App Open Manage Real-Time Revenue Recognition Issues

(F4101).

3 Enter Selection Make the following entries: No data found indicates that there are no issues. If issues are shown, review and process corrections.
Criteria Fiscal Year Period: <mm.yyyy>
Tip To download the issue list, make your filter selections and select Show Error Summary. From the
Company Code: 1010 list, you can choose the Download button.
Choose the Adapt Filters button and in the dialog box that
appears, choose Go.

4.3 Run Revenue Recognition: Projects

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 run the event-based revenue recognition for projects.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 17
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 - Sales. The SAP Fiori launchpad displays.

2 Access the SAP Fiori App Open Run Revenue Recognition - Projects (F4277). The New Job: Run Revenue Recognition - Projects view dis-
plays.

3 New Job Choose the Create button. The New Job view displays.

4 Enter Selection Criteria Make the following entries and choose the Schedule button: The new job is executed.
Job Template: Run Revenue Recognition – Projects
Job Name: <Enter a description or leave the default de-
scription>
Next, choose Step 2.
Start Immediately: <checked>
Next, choose Step 3.
To Period: <mm/yyyy>
Company Code: 1010
Ledger: 0L

4.4 Manage Revenue Recognition Issues: Projects

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>

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 18
Purpose

The errors occurred during Run Revenue Recognition Projects, can be monitored and reprocessed after the error is fixed via this step.

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 Ac- The SAP Fiori launchpad displays.
countant - Sales.

2 Access the SAP Open Manage Revenue Recognition Issues -

Fiori App Projects (F4100).

3 Enter Selection Cri- Make the following entries and choose Go: No data found indicates that there are no issues. If issues are shown, review and process corrections.
teria Fiscal Year Period: <PPP/YYYY>
Tip To download the issue list: Make your filter selections and choose the Show Error Summary button. Once
Company Code: 1010 the list is displayed, choose the Download button.
Ledger: 0L
Project Definition: <your definition>

4.5 Optional: Revenue Recognition Reversal

You could reverse revenue recognition if you made an error. For information on revenue recognition reversal, see the Reverse Month-End Revenue Recognition Postings step in the Appendix sec-
tion.

4.6 Project Actual Data Reporting

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 19
Tester Name: Duration:

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

Purpose

In this activity, you run the Project Actual Data report.

Procedure

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

1 Log On Log onto the SAP Fiori launchpad as a Cost Accountant - Sales. The SAP Fiori launchpad displays.

2 Access the SAP Fiori App Open Projects - Actuals (F0961). The Projects - Actuals screen displays.

3 Enter Report Criteria Make the following entries: The actual figures for projects - actuals display.
Ledger: 0L
Fiscal Year of Ledger: <current year>
Key Date: <Current date>
Company Code: 1010
G/L Account Hierarchy: YPS2

4 Accept Choose OK.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 20
5 Appendix

5.1 Reverse Month-End Revenue Recognition Postings

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

Occasionally, you may be required to reverse revenue recognition posts.

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 - Sales. The SAP Fiori launchpad displays.

2 Access the SAP Fiori App Open Reverse Revenue Recognition. The Application Jobs screen displays.

3 Create Choose the Create button. The New Job: Reverse Revenue Recognition view displays.

4 Enter Selection Criteria In the Template Selection section, make the following entries: The Scheduling Options view display.
Job Template: Reverse Revenue Recognition
Job Name: Reverse Revenue Recognition
Choose Step 2.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 21
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

5 Scheduling Options Select Start Immediately checkbox and choose Step 3. The Parameters view display.

6 Parameters Make the following entries: The figures for projects display.
Posting Date: <Enter a desired date>

Note This must be a month-end date. Otherwise, no selection will be returned.

Company Code: 1010

Ledger: <enter a ledger>
Journal Entry: <Enter the document you want to reverse>

7 Schedule Job Choose the Schedule button. The document is reversed.

5.2 Inspect Revenue Recognition Postings

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 project revenue recognition and flows are shown.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 22
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 - Sales. The SAP Fiori launchpad displays.

2 Access the SAP Fiori App Open Inspect Revenue Recognition Postings (F4008).

3 Enter Selection Criteria Make the following entries:

Account Assignment Object: <project or WBS element>
Ledger: 0L
Currency Type: Company Code Currency
Document Range: All

4 Execute Choose Go.

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE)

Appendix PUBLIC 23
Typographic Conventions

Type Style Description

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

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

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and
key concepts of a programming language when they are surrounded by body text, for example, SELECT and IN-
CLUDE.

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

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

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

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

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

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affili-
ate company. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in the express war-
ranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.

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

Event-Based Revenue Recognition - Project-Based Sales (4GQ_DE) tion and notices.
Appendix PUBLIC 24