4i9 s4cld2308 BPD en de

Test Script
SAP S/4HANA Cloud - 07-12-23
Project Control – Sales (4I9_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 Maintain Financial Statement Versions
2.5.2 Create Project Coding Mask (Optional)
2.5.3 Create Project Types for WBS Elements (Optional)
2.5.4 Maintain Budget Availability Profile (Optional)
2.5.5 Manage Situation Types (Optional)
2.5.6 Manage Teams and Responsibility for Projects (Optional)
3 Overview Table
4 Test Procedures
4.1 Create Project
4.2 Describe Project
4.3 Upload Planned Costs and Revenues
4.4 Release Project
4.5 Create Sales Order
4.5.1 Option 1: Create Sales Orders with Billing Plan and Assign WBS Element to the Leading Sales Item
4.5.1.1 Change Sales Order (Remove Billing Block)
4.5.1.2 Create Down Payment Request
4.5.1.3 Post a Down Payment
4.5.1.4 Create Delivery
4.5.1.5 Execute Picking
4.5.1.6 Post Goods Issue
4.5.1.7 Check Event Based Revenue Recognition – Project Accounted Sales
4.5.1.9 Billing 38
4.5.1.11 Accounts Receivable
4.5.2 Option 2: Create Sales Order with Free of Charge Item and Assign Billing or Non-Billing WBS Element
4.5.2.4 Create Invoice
4.6 Time Recording
4.7 Complete Milestone
4.8 Monitor Projects
4.8.1 Monitor Projects via Project Financial Controller Overview
4.8.2 Monitor Projects via Monitor Projects App
4.8.3 Monitor Projects via Project Cost Report
4.8.4 Monitor Projects via P&L Plan/Actual
4.9 Close Project
5 Appendix
5.1 Process Integration
5.1.1 Succeeding Processes

Appendix PUBLIC 2
1 Purpose
Overview
As a core ERP functionality, the integration of projects with the sales orders enables the direct flow of revenues to the project. The margin can be easily analyzed along with the incurred costs. This
scenario covers the fixed-price project billing with the possibility of a down-payment and billing plan. Using the Projects with Revenue profile, the user can create a hierarchy as an accounting struc-
ture, set up billing elements, and plan costs and revenues. As soon as the project is released, actual costs and revenues are captured, allowing the project profitability to be analyzed. At the same time,
the revenue is recognized with each cost posting. At the period end, no settlement run is necessary as the postings already have the CO-PA characteristics maintained in the settlement rule or derived
from the sales order.
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.

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 from a Template in the product assistance for SAP S/4HANA Cloud.
Name (Role Tem- ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
plate) On
Project Financial SAP_BR_PROJ_FIN_CON- Project Financial Controller SAP_BR_PROJ_FIN_CONTROLLER

Controller TROLLER
Project Manager SAP_BR_PROJECTMANAGER Project Manager SAP_BR_PROJECTMANAGER
Internal Sales Rep- SAP_BR_INTERNAL_SALES_R Internal Sales Representative / Billing for Internal Sales Representa- SAP_BR_INTERNAL_SALES_REP /
resentative EP tive / Customer Returns for Internal Sales Representative SAP_SD_SPT_BILLING_INT_SALES_PC /
SAP_SD_SPT_RETURNS_INT_SALES_PC
Billing Clerk SAP_BR_BILLING_CLERK Billing Clerk SAP_BR_BILLING_CLERK
Accounts Receiv- SAP_BR_AR_ACCOUNTANT Accounts Receivable Accountant SAP_BR_AR_ACCOUNTANT

able Accountant
Shipping Specialist SAP_BR_SHIPPING_SPE- Shipping Specialist SAP_BR_SHIPPING_SPECIALIST

Appendix PUBLIC 4
Name (Role Tem- ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
plate) On
CIALIST
Cost Accountant - SAP_BR_SALES_ACCOUNTANT Cost Accountant - Sales SAP_BR_SALES_ACCOUNTANT

Sales
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
Plant 1010 Plant 1 DE
Cost Center 10101501 R&D Cost center

10101321 Services/Consltg
Costing Sheet 1010PI Costing Sheet-PS Projects
Activity Types 8 Consulting
G/L Account 61005000 Trav. Expense - Ground transportation

61007000 Trav. Expense - Airfare, Rail, Mileage
61003000 Travel Expenses - Hotel and Accommodation
61008000 Travel Expenses - Miscellaneous
10010000 Petty Cash
44002000 Sales Discounts - Domestic
41000000 Rev Domestic Prod
41000400 Sales Revenue w/ Cost Element
Profit Center YB600 Shared Services

Appendix PUBLIC 5
Functional Area YB25 Consulting/Services
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
BNH Create Profit Center
2.4 Business Conditions

Before this scope item can be tested, the following business conditions must be met.
Scope Item ID Business Condition
BKJ - Sales Order Processing with Customer Down Payment To execute the sales order related activities for the project, the scope item must be activated.
BDA - Free of Charge Delivery To execute the sales order for free goods related activities for the project, the scope item must be activated.
J59 - Accounts Receivable To manage the open receivable invoices that are automatically created from the sales processes for the project, the scope item must be activated.
4GQ - Event-Based Revenue Recognition - Project-Based To execute the Revenue Recognition for Project based sales, the 4GQ- Event-Based Revenue Recognition - Project-Based Sales scope item must be acti-
Sales vated.
31Q - Sales Order Processing for Sales Kits To execute the event based revenue recognition for project based sales,the 31Q- Sales Order Processing for Sales Kits scope item must be activated

Appendix PUBLIC 6
2.5 Preliminary Steps
2.5.1 Maintain Financial Statement Versions
Procedure
To execute this activity, run the preliminary step Maintain Financial Statement Versions from the BNA - Period-End Closing - Projects test script.
2.5.2 Create Project Coding Mask (Optional)
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
You can create the coding mask for the project structure. The coding mask applies to the external identification of project definitions as well as WBS elements.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:

Appendix PUBLIC 7
Test Step Test Step Name Instruction Expected Result Pass/Fail/Com-
# ment
1 Log on Log on to the Fiori Launchpad as a

Configuration Expert - Business Process Configuration
2 Access the SAP Fiori App Open Manage Your Solution (F1241). The Manage Your Solution screen is displayed.
3 Navigate to configuration ac- Choose the link Configure Your Solution. The Change View "Project Number Editing'': Overview screen is
tivity Make the following entries: displayed.
Application Area: Enterprise Portfolio & Project Management

Sub Application Area: Project Financials Control
Click on the line item displayed in the Configuration Items section
Select Define Project Coding Mask and choose Configure
4 Create a Coding Mask Entry Perform the following actions to create the coding mask: Project Coding Mask will be saved.
Choose New Entries
Enter the following details:
PrjID: A
Coding mask: /XXXXXX-00
Description: Test Coding Mask for Key A
Lck: <Select/Deselect>
Choose Save.
● This step is optional.
● Once the coding mask is created, deletion is not possible.
● You cannot create commercial or internal projects in the project services processes,
namely:
• Customer Project Management (J11)
• Internal Project Management (1A8)
that begins with any coding key defined for coding masks.
SAP Central Business Configuration:
Test Test Step Name Instruction Expected Result Pass/Fail/Com-

Step # ment
1 Log on Log on to the project experience in SAP Central Business Configuration.
2 Navigate to configu- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the The Change View "Project Number Editing":
ration activity

Appendix PUBLIC 8
Step # ment
tree view, search for the following activity: Create Project Coding Mask. Overview screen is displayed.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Con-
figuration Expert - Business Process Configuration.
3 Create a Coding Perform the following actions to create the coding mask: Project Coding Mask will be saved.
Mask Entry Choose New Entries
Enter the following details:
PrjID: A
Coding mask: /XXXXXX-00
Description: Test Coding Mask for Key A
Lck: <Select/Deselect>
Choose Save.
● This step is optional.
● Once the coding mask is created, deletion is not possible.
● You cannot create commercial or internal projects in the project services processes, namely:
• Customer Project Management (J11)
• Internal Project Management (1A8)
that begins with any coding key defined for coding masks.
2.5.3 Create Project Types for WBS Elements (Optional)
Test Administration

Appendix PUBLIC 9
Purpose
Project Type is generally used to group or classify projects, it is primarily used for the reporting.
Procedure
Test Step Test Step Name Instruction Expected Result Pass/Fail/Comment

#
1 Log on Log on to the Fiori Launchpad as a Configuration Expert - Business Process Configura-
tion.
2 Access App Open Manage Your Solution (F1241). The Manage Your Solution screen is displayed.
3 Navigate to configuration activ- Choose the link Configure your solution. The Create Project Types for WBS Elements app is dis-
ity Make the following entries played.
Application Area: Enterprise Portfolio & Project Management

Sub Application Area: Project Financials Control
Click on the line item displayed in the worklist section
Select Create Project Types for WBS Elements and choose Configure
4 Create a Project Type Perform the following actions to create the project type: Project Type is saved.
Choose New Entries
Enter the details as mentioned in the following example :
Typ: RD
Description: RD Projects
Choose Save.

Appendix PUBLIC 10
Step # ment
2 Navigate to configu- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree The Create Project Types for WBS Ele-
ration activity view, search for the following activity: Create Project Types for WBS Eleements. ments screen is displayed.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configu-
ration Expert - Business Process Configuration.
3 Create a Project Type Perform the following actions to create the project type: Project Type is saved.
Choose New Entries
Enter the details as mentioned in the following example :
Typ: RD
Description: RD Projects
Choose Save.
2.5.4 Maintain Budget Availability Profile (Optional)
Test Administration
Purpose
The Maintain Budget Availability Profile app is used to create the Budget Availability control profile.

Appendix PUBLIC 11
Prerequisites
If you intend to use Project Budget, make sure that you activate the non-standard scope item Commitment Management (2I3) which is a prerequisite for budgeting. Once activated, commitment man-
agement ledger 0E is active and applicable for all company codes and countries/regions. These commitments are updated in Extension Ledger 0E (predelivered) in ACDOCA table. Commitments are
reduced by various business transactions such as goods receipt. The default content for Project Budgeting utilizes profiles PS001 and you can either update this profile or create your own profile via
configuration activity Maintain Budget Availability Control Profile for Projects.
Ensure that you perform the Preliminary Steps of this document to update the following:
● Maintain Financial statement YPS2
● Tag ACT_COST which is mandatory for G/Ls relevant for Budget check. Note that currently Commitment/Budget do not work for Purchase order without material.
● Maintain Financial Statement Versions (FSV)
● Assign Semantic Tags for FSV
● Set Report Relevancy
● Replicate Runtime Hierarchy. Make sure G/Ls relevant for Budget are part of this structure.
To view commitments in the report, an open purchase order and/or requisition must exist. For details on creating purchase orders, refer to Consumable Purchasing (BNX).
Procedure

Step # ment
1 Log on Log on to the Fiori Launchpad as a Configuration Expert - Business Process Configuration.
2 Access the SAP Fiori App Open Manage Your Solution (F1241). The Manage Your Solution screen is
displayed.
3 Navigate to configuration Choose the link Configure your solution. The Maintain Budget Availability
activity Make the following entries: Profile app is displayed.
Application Area: Finance

Sub Application Area: Overhead Cost Management
Click on the line item Budget Management displayed in the list.
Select Maintain Budget Availability Control Profile for Projects and choose Configure.
4 Create an Availability Perform the following actions to create the availability control profile:
Control Profile Entry Choose New Entries

Appendix PUBLIC 12
Step # ment
Enter the details as shown in the following example:

Profile: ZS001
Availy Ctrl Type: Project System
Budget Availy Ctrl: Profile Name : Default Bdgt Availability prfl
Time Range: Annual Budget / Overall Budget
Budget Currency: Global Currency/Project Currency
Press Enter.
● Overall Budget needs to be selected if you want to perform the budget check across Fiscal years whereas Annual Bud-
get needs to be selected if you want to perform the check per Fiscal year.
● Gobal Currency needs to be selected if you want to calculate the financials at controlling area level whereas Project
Currency needs to be selected if you want to check financials at project level.
For this newly created Availability Control Profile, maintain the Semantic Tags and Tolerance Limits.
Select the AVC profile and choose Semantic Tags and maintain entries as shown in the following example:
Choose New Entries
Sem. Tag: ACT_COST
Semantic Tag Name: Actual Cost
% of Budget used Before First Notification: 80%
% Increment for Further Notifications: 5%
Press Enter.
Select the Semantic tag and choose Tolerance Limits and maintain entries as shown in the following example:
Choose New Entries
Acty Grp: All Activity Groups
MsgType: Warning/Error
%: 90.00
Press Enter.
Choose Save.

Step # ment

Appendix PUBLIC 13
Step # ment
2 Navigate to configuration In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree The Maintain Budget Availability
activity view, search for the following activity: Maintain Budget Availability Control Profile for Projects. Profile screen is displayed.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configura-
tion Expert - Business Process Configuration.
3 Create an Availability Perform the following actions to create the availability control profile:
Control Profile Entry Choose New Entries
Enter the details as shown in the following example:
Profile: ZS001
Availy Ctrl Type: Project System
Budget Availy Ctrl: Profile Name : Default Bdgt Availability prfl
Time Range: Annual Budget / Overall Budget
Budget Currency: Global Currency/Project Currency
Press Enter.
● Overall Budget needs to be selected if you want to perform the budget check across Fiscal years whereas Annual Budget
needs to be selected if you want to perform the check per Fiscal year.
● Gobal Currency needs to be selected if you want to calculate the financials at controlling area level whereas Project Cur-
rency needs to be selected if you want to check financials at project level.
For this newly created Availability Control Profile, maintain the Semantic Tags and Tolerance Limits.
Select the AVC profile and choose Semantic Tags and maintain entries as shown in the following example:
Choose New Entries
Sem. Tag: ACT_COST
Semantic Tag Name: Actual Cost
% of Budget used Before First Notification: 80%
% Increment for Further Notifications: 5%
Press Enter.
Select the Semantic tag and choose Tolerance Limits and maintain entries as shown in the following example:
Choose New Entries
Acty Grp: All Activity Groups
MsgType: Warning/Error
%: 90.00
Press Enter.
Choose Save.

Appendix PUBLIC 14
2.5.5 Manage Situation Types (Optional)
Purpose
In this procedure, you configure the situation type by using template.

Note For details on situations and the process to set up situation types, see the Setting Up Situation Handling (31N) guide.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Log on Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration
2 Open Manage Situ- Open Manage Situation Types (F2947) app. The Manage Situation Types
ation Types screen is displayed.
3 Select the Template In the Standard section, enter the ID EPPM_PROJBUDGETTHRESHOLDEXCEEDED and choose Go. The Situation Type screen is
to Copy Select the latest version of EPPM_PROJBUDGETTHRESHOLDEXCEEDED, then choose Copy. displayed.
4 Maintain the Situa- Make the following entries and choose Save: The situation type is main-
tion Admin Information tained
ID: <ID Name>

Name: <ID Description>
ID: Z_BUDGET THRESHOLD
Name: Budget Consumption Situation
Situation Display
Short Description:
Details:
Notification:
Resend Notifications: YES
Conditions
Maintain the values against the corresponding attributes/ filters to configure the conditions and use this function.
Notification Recipients
Responsibility by teams: Choose + and maintain the team created through the 'Manage Teams and Responsibilities' app and maintain the
value Project Financial Controller in the field Member Functions if necessary.

Appendix PUBLIC 15
Step # Comment
Responsibility Rules: Choose + and maintain the project related users mapped/linked to the projects in the 'Project Brief' app for the roles
of Project Financial Controller and Project Manager.
5 Enable The Situa- Choose Enable, it will change from NO to YES.

tion Type
2.5.6 Manage Teams and Responsibility for Projects (Optional)
Purpose
In this procedure, you configure teams and responsibility for projects.

Note For details on the process of setting up teams and responsibility determination, see the Setting Up Responsibility Determination (1NJ) guide.
You can also define your own responsibility management (functions, teams, and responsibilities) by making use of the following SSCUIs:
● Map Function Profiles to Standard Team Category
● Classify Functions for Standard Team Category
● Map Custom Responsibility Definitions to Standard Team Category
● Define Team Types
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Log on Log on on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration
2 Access the App Open Manage Teams and Responsibilities - Change Record (F2412) . The New Team screen is displyed.
Choose Create.
3 Maintain the Team details Make the following entries:

On the Team Information tab:
● Name: Team_EPPM Description: Team of EPPM
● Status:Enabled

Appendix PUBLIC 16
● Type: SEPPM_PFC
On the Team Members tab:
Choose Create, and maintain the following values:
● Business Partner: use the search function to find the business partner of Project Financial Controller
● Functions: Project Financial Controller
4 Create the Team Choose Create. The team is created.

Appendix PUBLIC 17
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 Business Role App/Transaction Expected Results
Create Project [page ] 21 Project Financial Project Control - Enterprise Projects (F3215) Project definition and WBS Elements with all the re-
Controller quired parameters will be created.
Describe Project [page ] 25 Project Manager My Projects - Project Manager (F1876) Project details and team members are added.
Upload Planned Costs and Revenues [page ] 26 Project Financial Import Financial Plan Data (F1711) Planned costs for the project WBS Element are posted.
Controller
Release Project [page ] 28 Project Financial Project Control - Enterprise Projects (F3215) The project status is changed to REL (Release).
Controller
Create Sales Order
Option 1: Create Sales Orders with Billing Plan Internal Sales Manage Sales Orders (F1873)
and Assign WBS Element to the Leading Sales Representative
Item [page ] 29
Internal Sales Manage Sales Orders (F1873)

Representative
Change Sales Order (Remove Billing Block) [page Internal Sales Manage Sales Orders (F1873)
] 33 Representative
Create Down Payment Request [page ] 33 Billing Clerk Create Billing Documents (F0798)
Post a Down Payment [page ] 34 Accounts Re- Post Incoming Payments (F1345)
ceivable Accoun-
tant
Create Delivery [page ] 35 Shipping Spe- Create Outbound Deliveries - From Sales Orders (F0869A)
cialist

Appendix PUBLIC 18
Execute Picking [page ] 35 Shipping Spe- Manage Outbound Deliveries - VL06O (VL06O_CLOUD)
cialist
Post Goods Issue [page ] 36 Shipping Spe- Manage Outbound Deliveries - VL06O (VL06O_CLOUD)
cialist
Check Event Based Revenue Recognition – Project Shipping Spe- Manage Outbound Deliveries - VL06O (VL06O_CLOUD)
Accounted Sales [page ] 37 cialist
Change Sales Order (Remove Billing Block) [page Internal Sales Manage Sales Orders (F1873)
] 38 Representative
Billing [page ] 38 Billing Clerk Create Billing Documents (F0798)
Check Event Based Revenue Recognition – Project Billing Clerk Create Billing Documents (F0798)
Accounted Sales [page ] 39
Accounts Receivable [page ] 40 Accounts Re- Accounts Receivable Overview (F3242)

ceivable Accoun-
tant
Option 2: Create Sales Order with Free of Charge Internal Sales Manage Sales Orders Without Charge (F2305)
Item and Assign Billing or Non-Billing WBS Ele- Representative
ment [page ] 41
Create Delivery [page ] 43 Shipping Spe- Create Outbound Deliveries - From Sales Orders (F0869A)
cialist
Execute Picking [page ] 44 Shipping Spe- Manage Outbound Deliveries - VL06O (VL06O_CLOUD)
cialist
Post Goods Issue [page ] 44 Shipping Spe- Manage Outbound Deliveries - VL06O (VL06O_CLOUD)
cialist
Create Invoice [page ] 45 Billing Clerk Create Billing Documents (F0798)
Time Recording [page ] 46 See the test See the test script. See the test script.
script.
Complete Milestone [page ] 46 Project Manager My Projects - Project Manager (F1876)
Monitor Projects [page ] 47 Project Financial Project Financial Controller Overview (F3078) or Project Budget Report (F3377) Compare project actual vs planned.
Controller or Monitor Projects (F3088) or P&L - Plan/Actual or Project Cost Report - Plan/Ac-

Appendix PUBLIC 19
tual (F2513)
Monitor Projects via Project Financial Controller Project Financial Project Financial Controller Overview (F3078) The Overall Status, Planned and Active Projects, Actual
Overview [page ] 48 Controller costs, Cost to Date-Timeline and Upcoming Milestones
are dis-played.
Monitor Projects via Monitor Projects App [page ] Project Financial Monitor Projects (F3088) A detailed view of the project cost, project progress is
49 Controller dis-played in graphical form.
Monitor Projects via Project Cost Report [page ] Project Financial Project Cost Report - Plan/Actual (F2513) All plan, actual costs, and their variances are displayed.
50 Controller
Monitor Projects via P&L Plan/Actual [page ] 51 Project Financial P&L - Plan/Actual Variance of planned vs actual costs on the project is dis-
Controller played.
Close Project [page ] 52 Project Financial Project Control - Enterprise Projects (F3215) Project Status is changed to CLSD (Closed).
Controller

Appendix PUBLIC 20
4 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
4.1 Create Project
Purpose
In this activity, you can create a project with revenue with the project definition and WBS element using the Project Control - Enterprise Projects (F3215) app.
Projects with Revenue allow revenue G/L journal entries postings after release. The profitability segment characteristics can be maintained in the settlement rule, however running the settlement isn’t
required anymore due to the direct attribution of cost postings.
For hierarchical project accounting requirements, you can also create a hierarchical project structure by calling up the Project Planning application from the Project Control - Enterprise Projects
(F3215) app.
Procedure
Test Test Step Name Instructions Expected Result Com-

Step ments
#
1 Log On Log on to the SAP Fiori Launchpad as a Project Financial Controller.
2 Access App Open Project Control - Enterprise Projects (F3215). The Project Control screen is displayed.
3 Create Project: Choose Create. Project is created with the provided definition parameters.
Definition Make entries as shown in the following example in the Header and General Information sections: One WBS Element with details as shown in the following example will be
Header created under the project:
Project Name: Project with Revenue WBS Element ID: R.000001
Project ID: R.000001 Project Name: Project with Revenue
Project Profile: Project with Revenue

Multiple Sales Order Item Scenario: Selected

Appendix PUBLIC 21
Step ments
#
Note By selecting this check box, you can assign more than one billing relevant sales order item to the
same billing work package.
Choose the right setting on the project before the first save. After the first save, this decision cannot be
changed.
The setting done on the project level would be valid for all the billing work packages in that project.
Sales order items having different revenue recognition keys cannot be assigned to the same billing
work package.
In case the Multiple Sales Order Item Scenario is NOT selected, the profitability characteristics are au-
tomatically derived based on the sales order and sales order item. In case the Multiple Sales Order Item
Scenario is selected, the profitability characteristics must be defined by the user in the Settlement Rule.
Planned Start: Today (MM/dd/yyyy)

Planned Finish: Today + 3 months (MM/dd/yyyy)
General information:
Responsible Cost Center: 10101501 (R&D Cost center) (for example)
Profit Center: YB600 (Shared Services)
Project Currency: EUR(Automatically filled based on the cost center)
Note You can specify the currency at project level different from controlling area currency, to run
project- specific financial reports.
Project Manager: the Project Manager ID

Priority: the priority suitable for project
Project Type: Project Type created in Create Project Types for WBS Elements (Optional) [page ] 9
Attachments: Choose + to upload project relevant documents from your local drive.
Note To rename the existing attachment, choose the Edit icon present next to the attachment and
change the file name according to the requirement and choose Rename.
Choose Create.
The project is saved and a confirmation message is displayed.
4 Add Values to Once the project is created, from the header section, choose Edit. WBS Element updates with all the provided parameters.
the Project Sum- Make the following entries:
mary Task WBS

Appendix PUBLIC 22
Step ments
#
Element General Information

Plant: 1010
Functional Area: YB25 (Consulting/Services)
Control
Costing Sheet: 1010PI
The following are optional entries, maintain them according to your requirements.
Budget Availability Control Profile: ZS001
If project currency is maintained, you can assign a budget availability control profile where the budget cur-
rency is maintained as Global Currency or Project Currency.
If project currency is not maintained, you can only assign an availability control profile where the budget
currency is maintained as Global Currency.
Budget Availability Control Profile is active: Selected
● You can define your own budget availability control profile using the Maintain Budget Availability Pro-
file SSCUI.
● As soon as you have planned budget for your project and activated the budget availability control, the
hierarchy changes are no longer possible.
Choose Save.
A system message tells you that the project has been saved
Note In case you have entered a budget availability control profile and activated the budget availability
control, all the postings resulting into commitments or actual costs will be checked against the available
budget of the WBS element used as account assignment object.
In case the WBS element does not have any budget, the next higher level budget carrying WBS ele-
ment will be used for the budget availability check.
Depending on the tolerance limits defined for the availability control profile, the system can raise warn-
ing or error messages.
Depending on the Time Range defined for the availability control profile, you will be able to check the
budget consumption for a particular fiscal year or across fiscal years. This setting is valid for all kind of
expense postings and expected expense postings (for example, purchase requisition or purchase orders)
to a WBS element.
Warning messages from budget availability check are not shown in case of automatic periodic postings
and certain goods movement.
5 (Optional) Up- From the header section, choose Settlement Rule. The Program WBS_SETTLEMENT screen is displayed with the system
date settlement On the Maintain Settlement Rule: Overview screen, make the following entries: message confirming that the settlement rule is saved.
rule to Project
Cat: PSG Note Users can maintain a settlement rule to profitability segments for
Choose Enter. the billing element only. The characteristics are used to attribute cost/

Appendix PUBLIC 23
Step ments
#
Maintain the required information and choose Continue. revenue postings to the billing and lower level Work Packages. A set-
Choose Save and then Back. tlement to transfer data to CO-PA hence is not required and therefore
settlement is prohibited by the settlement profile.
Note Once the project / billing work package is account assigned to only one billing and pricing rele-
vant sales order items (and multiple free of charge SO items), the profitability characteristics are auto-
matically derived once the billing work package is assigned to the sales order item. In this case, the
maintenance of the settlement rule in the billing work package is optional. However, If a settlement
rule is maintained on project level, this would have priority and the profitability characteristics for each
posting would be taken from settlement rule.
In case the project/ billing work package is account assigned to multiple billing and pricing relevant
sales order items (and multiple free of charge SO items) the maintenance of the settlement rule in the
billing work package is mandatory and the profitability characteristics will be taken from the settlement
rule maintained, or no profitability characteristic will be derived if no settlement rule is maintained.
6 Navigate to Once the project is created, from the header section, choose Related Apps. A pop-up screen appears The Project Planning app is opened and you can make further entries.
Project Planning From the pop-up screen, select Project Planning to go to the Project Planning app.
Note By default, the project will open in the Display mode. To edit the project, choose Edit.
7 Create WBS In the Project Structure view, select WBS Element created in the above step, and choose Create Work Pack- Project with WBS Element structure is updated with the provided parame-
Packages under age. ters.
Project Summary Make the following entries in the Details screen onto the right.
Task WBS Ele-
ID: <Example: R.0000011>
ment
Name: WBS for project planning
Profit Center: <This data is pre-populated from the first WBS level>
Responsible Cost Center: <This data is pre-populated from first WBS level>
Planned Start: Today
Planned Finish: Today + 3 months
In the Project Structure view, select WBS Element created in the above step, and choose Create Work Pack-
age.
ID: <Example: R.0000012>
Name: WBS for project execution
Profit Center: <This data is pre-populated from the first WBS level>
Responsible Cost Center: <This data is pre-populated from first WBS level>
Planned Start: Today
Planned Finish: Today + 3 months
Create work package structure based on your requirements.

Appendix PUBLIC 24
Step ments
#
Note You can also create workpackage by making use of the Copy Work Package functionality avail-
able in the Project Planing Application
Note In the Project Planning app, the user is able to maintain multiple billing work packages by setting
the Billing Element flag. In order to ensure the correct handling of CO-PA attributes, the billing work
packages can not be in the same sub-structure, meaning that it is not allowed to have one billing ele-
ment under another billing element in the structure. Also, the work packages that are under a billing el-
ement must have the same company code, profit center and functional area to ensure the same prof-
itability segment postings.
8 Save Project Choose Save. Project with WBS Element structure is saved.
Structure
4.2 Describe Project
Test Administration
Purpose
In this activity, the Project Manager describes the project details, such as Milestones, for the first time.

Appendix PUBLIC 25
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Project Manager.
2 Access My Projects (Active Open My Projects - Project Manager (F1876) app. Choose Planned Projects to go to Project Briefs. The Project Briefs screen ap-
Projects) pears.
3 Open the Project From the Projects displayed, select the project and click to open the project. Selected project is displayed.
4 Choose Edit Choose Edit to change the project from Display to Edit mode. Project is editable.
Note By default, the project will open in the display mode.
5 Maintain Priority and Select the priority and project type suitable for the project from the drop-down option list.
Project Type
6 Define Milestones From the Milestones tab, click Create to add the list of relevant milestones. All the milestones are saved
and displayed.
7 Maintain the Planned Finish For each milestone, select the Planned Finish date. Planned Finish dates for the
Dates for the Milestones milestone are maintained.
8 Define Team Scroll down to the Team section and choose + to maintain the names of steering committee team members, project financial controller Team member details are
and team members with relevant roles. maintained
Note The assigned team members will be able to find the WBS elements of Projects assigned in the search box of the Time
Recording app and create tasks with those WBS elements and record their time according to the steps mentioned in the Time
Recording (1Q4) test script.
Choose Create.
4.3 Upload Planned Costs and Revenues
Test Administration

Appendix PUBLIC 26
Purpose
In this activity, you upload planned costs to WBS elements.
Note You will be able to use the Analytics Cloud functionality to input planned costs to the project by executing the 2YG test script.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Project Financial Controller.
2 Access App Open the Import Financial Plan Data (F1711) app. The Import Financial Plan Data
screen is displayed.
3 Download Template; Fill the planned Choose Download Templates. A pop-up window appears. CSV file is saved with the plan
costs in the CSV file In the pop-up window, choose , (Comma) from the Separator for .csv files dropdown and then choose Project Plan- costs.
ning; the template CSV file will be downloaded to the local machine.
Choose Close.
Access the file and fill the plan values.
Make sure to save the file in CSV (Comma delimited) (*.csv) format.
Note Remember the location of the file stored.
Adapt the Project Planning Template

A template table is provided for your reference with sample values as follows:

Appendix PUBLIC 27
Category General Ledger Fiscal Posting Period Company Code Project Definition Work Breakdown Structure Element (WBS Element) Account Number Amount in Global Currency Global Currency
Year
X X X X X
PLN <current year> <current month> 1010 R.000001 R.000001 41000400 -2000 USD
Example 2020 Example 2
PLN <current year> <current month> 1010 R.000001 R.0000011 61005000 1000 USD
Example 2020 Example 2
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
4 Import Planned Cost Choose Browse. Select the CSV file from the local system which has the planned cost data already maintained for the The plan data has been imported suc-
Data project created above. cessfully.
Choose Import Source File.
4.4 Release Project
Test Administration
Purpose
In this activity, you release the project to enable the project execution.
Note To use the workflow for the project release approval process, perform the steps described in Review Workflow for the Release of a Project (Optional) of the Project Review (1YF) test

Appendix PUBLIC 28
script, using the project from this document.
Procedure

Step # Comment
2 Access App Open the Project Control - Enterprise Projects (F3215) app. The Project Control screen is displayed.
3 Open Project In the Standard section, make the following entries, and choose Go. At least one entry is displayed in the Worklist area.
Project : <Refer the respective Project created in Create Project [page ] 21.
R.000001 (for Revenue Project).
4 Release project and structure Select the project and in header section choose Processing Status > Release. Project status is changed to Released.
● You can also use the Change Processing Status option in the Project
Briefs app in a Project Manager role.
● Project once released cannot be renamed or deleted.
5 Maintain actual start date in Choose Related Apps > Project Planning. Choose Edit to open the project in Project is saved with WBS elements Actual start dates.
WBS Elements change mode.
For all the created WBS elements, maintain the Actual Start Date field in the
Work Package Detailed Overview page.
Choose Save.
4.5 Create Sales Order
4.5.1 Option 1: Create Sales Orders with Billing Plan and Assign WBS Element to the Leading Sales Item
Test Administration

Appendix PUBLIC 29
Purpose
In this process step, you create a sales order with a sales order item that has a billing plan, where the first item is a down-payment. The sales order item has the project created before as account as-
signment.
Procedure
To execute this activity, perform he following steps. For more information, refer Create Sales Orders with Billing Plan step in the Sales Order Processing with Customer Down Payment (BKJ) test
script.
Test Test Step Name Instruction Expected Result Pass / Fail

Step # / Com-
ment
1 Log On Log on to SAP Fiori launchpad as an Internal Sales Representative. The SAP Fiori launchpad displays.
2 Access the App Open Manage Sales Orders (F1873). The Manage Sales Orders screen displays.
3 Navigate to Cre- On Manage Sales Orders screen, choose Create and select Create Sales Order - VA01. The Create Sales Documents: Initial screen dis-
ate Sales Order plays.
Screen
4 Enter Sales Doc- Make the following entries: The Create Standard Order xxx: Overview
ument Type ● Order Type: <sales order type>, for example, OR (Standard Order) screen displays.
Organizational Data
● Sales organization: 1010
● Distribution channel: 10
● Division: 00
Choose Enter.
5 Enter Customer Make the following entries:

Number ● Sold-To Party: 10100004

Appendix PUBLIC 30
Step # / Com-
ment
● Cust. Reference: <Reference>

● Cust. Ref. Date: <Date>
Choose Enter.
6 Enter Order De- Make the following entries:

tails ● Order Reason: <Order Reason>
● Material: <material number>
● Order Quantity: <quantity>, for example, 10
● Item Category:
CBAO : Milestone billing plan for Trading goods, for example, TG0012.
CTAD: Milestone billing plan service for Service material SM0001.
CTAX: Milestone billing plan non-stock for Non-stock material NS0002.
CBTC: Configuration at material level
CBTD: Configuration milestone billing plan
TAN: Standard item
TAD: Standard Service Item
TAX: Standard Non-Stock
CBTA: Standard Make-to-Order
CB1 : Third Party items with Shipping Notification (3rd Party with SN)
CB2 : Third Party items without Shipping Notification (3rd Party w/o SN)
CB1C : Third Party variant configuration with shipping configuration
CB2C : Third Party variant configuration without shipping configuration
CBAB : Bought-In Item (Bought-In Item)
DB1 : Milestone Billing Plan with Shipping Notification (MilstBillPl 3Pw/ASN)
DB2 : Milestone Billing Plan without Shipping Notification (MilstBillPl 3Pw/oASN)
DBAB : Milestone Billing Plan with bought-in Items (MilstBillPl OrdSProc)
CBTQ : Pricing header milestone billing plan
TAQ : Pricing at Header Level
Note A service product SM0001 is used in the sales order. It allows the sales of services without delivery and direct or-
der-related billing. You may skip the steps from Create Delivery [page ] 35 to Post Goods Issue [page ] 36.
● Batch: <batch number> This step is optional.
Note The billing of this business process is order-related. This means that the down payment request and the final invoice

Appendix PUBLIC 31
Step # / Com-
ment
only contain the information that is available from the sales order like material, quantity, and batch number. If you need a
batch number on the down payment request and the final invoice you must enter it in the sales order.
Choose Enter.
7 Choose WBS El- Select the item. Choose More > Goto > Item > Account Assignment .
ement
Note Alternatively, you can assign Account Assignment on header level: Choose More > Goto > Header > Account Assign-
ment .
WBS Element: <Example: R.000001>

Profit Center: < Automatically picked from WBS Element. For example, YB600>
Note
● If the multiple sales order items is not selected during project creation, only one billing and pricing relevant item (Item
categories CBAO, CTAD, CTAX, CBTC, CBTD, TAN) can be assigned to one billing work package. However, for the
same billing work package, additionally, multiple free of charge sales order items can be account assigned..
8 Choose Billing Select the item. Choose Menu > Goto > Item > Billing plan .
Plan
Note Alternatively, you can assign billing plan on header level: Choose More > Goto > Header > Billing Plan . The header
billing plan will be applied to all items with item category CBAO, CTAD, or CTAX. The amount is proportionally to the
value of the item participating in the down payment process distributed to the items.
9 Enter Details For the first line item, Down Payment, make the following entries for the advance payment:
● Billing Date: <billing date>. For example, enter today's date.
● Bill Value: <amount of billing>. For example: Down Payment amount.
● Date category (DCat): 04
10 Enter Details For the second line item (Closing Invoice), make the following entries for the advance payment:
● Billing Date: <billing date>. For example, enter today's date.
● Date category(DCat): 02
11 Enter Choose Enter. Confirm system messages with enter, if necessary. Closing invoice related data is determined. For
example, in the Bill value field, the amount of
billing is calculated by the system.
12 Save Sales Order Choose Back.

Choose Save and save your entries.

Appendix PUBLIC 32
Test Administration
Purpose
This process step shows you how to remove billing block from a sales order.
Procedure
To execute this activity, execute the Change Sales Order (Remove Billing Block) step from the Sales Order Processing with Customer Down Payment (BKJ) test script.
4.5.1.2 Create Down Payment Request
Test Administration

Appendix PUBLIC 33
Purpose
This process step shows you how to create a down payment request.
Procedure
To execute this activity, execute the Create Down Payment Request step from the Sales Order Processing with Customer Down Payment (BKJ) test script
4.5.1.3 Post a Down Payment
Test Administration
Purpose
This process step shows you how to post a down payment.
Procedure
To execute this activity, execute the Post a Down Payment step from the Sales Order Processing with Customer Down Payment (BKJ) test script

Appendix PUBLIC 34
Test Administration
Purpose
This process step shows you how to create a delivery.
Prerequisite
The goods receipt are posted to the individual customer’s stock.
Procedure
To execute this activity, execute the Create Delivery step from the Sales Order Processing with Customer Down Payment (BKJ) test script.
Test Administration

Appendix PUBLIC 35
Purpose
The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods are prepared for shipping. This process step shows you how to pick
deliveries.
Procedure
To execute this activity, execute the Execute Picking step from the Sales Order Processing with Customer Down Payment (BKJ) test script.
Test Administration
Purpose
This process step shows you how to post goods issues for delivery.
Procedure
To execute this activity, execute the Post Goods Issue step from the Sales Order Processing with Customer Down Payment (BKJ) test script.

Appendix PUBLIC 36
Test Administration
Purpose
This process step shows you the profitability and the recognized revenue for the project at the time of posting goods issue for deliveries from the sales order item.
Procedure
To execute this activity, execute the following steps from the 4GQ- Event-Based Revenue Recognition - Project-Based Sales test script:
1. Monitor Revenue Recognition (Event-Based): Projects
2. Run Revenue Recognition: Projects
Note In order to check the revenue recorded on the project, maintain the details as follows while executing the above mentioned steps:
Fiscal Year Period: <enter a period in the PPP/YYYY format>
Ledger: 0L
Company Code: 1010
Project Definition: <R.000001>

Appendix PUBLIC 37
Test Administration
Purpose
This process step shows you how to remove billing block from a sales order.
Prerequisite
COGS must be recognized. To recognize revenue in the same month to keep FI and PA in sync, the billing block must be removed manually to process the final invoice.
Procedure
To execute this activity, execute the Change Sales Order (Remove Billing Block) step from the Sales Order Processing with Customer Down Payment (BKJ) test script.
4.5.1.9 Billing
Test Administration

Appendix PUBLIC 38
Purpose
This process step shows you how to bill a customer.
Procedure
To execute this activity, execute the Billing step from the Sales Order Processing with Customer Down Payment (BKJ) test script.
Test Administration
Purpose
This process step shows you the profitability and the recognized revenue for the project after billing the sales order item.
Procedure
To execute this activity, execute the following steps from the 4GQ- Event-Based Revenue Recognition - Project-Based Sales test script:
1. Manage Real-Time Revenue Recognition Issues
2. Run Revenue Recognition: Projects

Appendix PUBLIC 39
3. Project Actual Data Reporting
Note In order to check the revenue recorded on the project, maintain the details as follows while executing the above mentioned steps:
Fiscal Year Period: <enter a period in the PPP/YYYY format>
Ledger: 0L
Company Code: 1010
Project Definition: <R.000001>
4.5.1.11 Accounts Receivable
Test Administration
Purpose
This procedure guides you through the Accounts Receivable Overview. In this activity, you review an overview of relevant figures and statistics related to the accounts receivable process. The Ac-
counts Receivable Overview (F3242) app offers a central point of entry and an overview of the department.
Note For more information, see the SAP Fiori Analytical Apps for Financial Accounting (2JB) test script.
Procedure
To execute this activity, execute the Accounts Receivable Overview sub-step of the Invoice Management Reporting step from the Accounts Receivable (J59) test script.

Appendix PUBLIC 40
4.5.2 Option 2: Create Sales Order with Free of Charge Item and Assign Billing or Non-Billing WBS Element
Test Administration
Purpose
This process step shows you how to create a free of charge sales order.
Procedure
To execute this activity, proceed with the following steps. For more information, you can refer to the Create Sales Orders step in the Free of Charge Delivery (BDA) test script.
Note If you have activated the Accounts Receivable (J59) scope item in your system and if you use the TG11 material and the 10100001 customer, the Minimum quantity 1.000 PC
of free goods has not been reached warning notification may be displayed. To skip the warning, choose Enter.

Step # ments
1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative The SAP Fiori launchpad displays.
2 Access the App Open Manage Sales Orders (F1873). The Manage Sales Orders screen is displayed.
3 Navigate to Create Sales On Manage Sales Orders screen, choose Add and select Create Sales Order - VA01 The Create Sales Documents: Initial screen is displayed.
Order screen
4 Enter Sales Document Make the following entries and choose Continue:
Type ● Sales Document Type: OR (Standard Order)
● Sales Organization: 1010

Appendix PUBLIC 41
Step # ments
● Distribution Channel: 10
● Division: 00
5 Enter Customer Informa- Make the following entries and choose Enter:
tion Sold-to Party: 10100001
6 Enter Order Details Make the following entries: Item category CBXN is determined automatically supporting transfer of costs to
● Cust. Reference: <Reference Number> accounting and creation of proforma invoices.
Under Sales tab, enter the following entries:

● Order Reason: select Free of Charge Sample from the dropdown list
● Material: <Material Number>
● Order Quantity: <Quantity> , for example, 2
● Item Category::
CBXN:Stock item free of charge
TAXN:Non-stock item free of charge
TADNService item free of charge
CB3: Third-Party with Shipping Notification Free of
Charge
CB4: Third-Party without Shipping Notification Free of
Charge
CBLN: Free of Charge Express
CBTN: Configuration at Material Level Free of Charge
CBXB: Bought-In Free of Charge
CB3C:Variant Configuration with Shipping Notification
Free of Charge
CB4C:Variant Configuration without Shipping Notification
Free of Charge
7 Choose WBS Element Select the item. Choose More > Goto > Item > Account Assignment .
Note Alternatively, you can assign Account Assignment on header level: Choose
More > Goto > Header > Account Assignment .
WBS Element: <Example: R.000001>
Note In the WBS Element field, you can assign billing or non-billing WBS element.
Profit Center: <Will automatically pick from WBS Element. For example, YB600>

Appendix PUBLIC 42
Step # ments
8 Save Choose Save.
Note Please ignore any pop-up windows.
Test Administration
Purpose
This process step shows you how to create a free of charge delivery.
Procedure
To execute this activity, execute the Create Delivery step from the Free of Charge Delivery (BDA) test script.

Appendix PUBLIC 43
Test Administration
Purpose
The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods are prepared for shipping. This process step shows you how to pick
deliveries.
Procedure
To execute this activity, execute the Execute Picking step from the Free of Charge Delivery (BDA) test script.
Test Administration

Appendix PUBLIC 44
Purpose
This process step shows you how to post goods issues for delivery.
Procedure
To execute this activity, execute the Post Goods Issue step from the Free of Charge Delivery (BDA) test script.
4.5.2.4 Create Invoice
Test Administration
Purpose
This process step shows you how to create a Pro Forma invoice with reference to delivery and how to create a F2 type of invoice with costs transferred to accounting accordingly.
Procedure
To execute this activity, execute the Create Pro Forma Invoice & Create Customer Invoice step from the Free of Charge Delivery (BDA) test script.

Appendix PUBLIC 45
4.6 Time Recording
Purpose
In this activity, employee enters the time recording for WBS Element using Manage My Timesheet (F1823) application.
Procedure
To execute this activity, you must execute the procedure in the following sub-step (which is from the Time Recording (1Q4) test script) using the WBS Element from this document: Record Actual
Working Time.
Note While creating the task, maintain the Activity Type as 18 and use the WBS element created in the Create Project step of this test script.
WBS Element <R.0000012> <WBS for project execution>
4.7 Complete Milestone
Test Administration
Purpose
In this activity, the Project Manager changes the status of the milestone to be approved based on the feedback received from the Project Steering Committee during the review meeting and sets the
actual dates for the approved milestones.

Appendix PUBLIC 46
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Project Manager.
2 Access App Open the My Projects - Project Manager (F1876) app. Go to Project Brief Overview using the The Project Overview screen appears and the list of
card Upcoming Milestones - Active Projects. projects is displayed.
3 Select Project in which Milestones are Select the project and click to navigate to the Project Brief screen. Details of the selected project are displayed.
to be Approved Selected project opens and can be updated.
4 Choose Edit Choose Edit to change the project from Display to Edit mode. Selected project opens in the edit mode.
Note By default, the project opens in the display mode.
5 Set Milestones Status to Approved Set Milestone Approval Status to Approved. Milestone Approval Status is added in the Mile-
stone section.
6 Update the Actual Finish Date Update the Actual Finish Date for the approved Milestones. The Actual Finish date is updated.
Note Actual Date can be updated only for the released projects.
Choose Save.
4.8 Monitor Projects
Purpose
In this activity, you can analyze the costs (planned/actual) recorded on the project using different tiles available on the Fiori launchpad. You can also check project progress and the overall status of
your project.

Appendix PUBLIC 47
4.8.1 Monitor Projects via Project Financial Controller Overview
Test Administration
Purpose
In this activity, you can analyze the status, timelines, budget, and costs of your project.
Note You will be able to access the reports such as Project Cost, Plan versus Actual, Project Budget Report and Monitor Projects directly from Project Financial Overview.
Procedure
# ment
1 Log On Log on to the SAP Fiori Launchpad as a Project Financial

Controller.
2 Access App Open Project Financial Controller Overview (F3078).
3 Enter Selection Cri- In the Standard section, make the following entries and Projects with selected planning category are displayed in the Data Analysis area.
teria choose Go.
Planning Category: PLN
4 Check Financials Check financial and overall status of the project using the dis- The Overall Status, Planned and Active Projects, Actual costs, Cost to Date-Timeline and Upcoming
played cards. Milestones are displayed.

Appendix PUBLIC 48
4.8.2 Monitor Projects via Monitor Projects App
Test Administration
Purpose
In this activity, you can analyze the cost and the overall progress of your project.
Procedure

Step # Comment
2 Access App Open Monitor Projects (F3088) The Monitor Projects screen is displayed.
3 Enter Selection In the Standard section, make the following entries and choose Go. At least one entry is displayed in the Worklist area.
Criteria Project: <Refer the respective Project created in the chapter Create Project >
Example R.000001 (for Revenue Project)
Planning Category : PLN
4 Check Financials From the Worklist area, select the project. Project Costs and Project Budget reports of the selected
Choose View Costs to check project costs. project are displayed.
Choose View Budget to check the project budget.

Appendix PUBLIC 49
Step # Comment
Choose Back to go to the previous screen.
5 Check Project From the Worklist area, select the project and choose Project Progress to go to the Monitor Project Progress A detailed view of the project progress is displayed in
Progress screen, which displays the project timelines. graphical form.
Note This would only be possible in case the 1YF-Project Review is active.
4.8.3 Monitor Projects via Project Cost Report
Test Administration
Purpose
In this activity, analyze the cost structure of your project and check planned cost.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori Launchpad as a Project Financial

Controller .

Appendix PUBLIC 50
Step # Comment
2 Access App Open the Project Cost Report - Plan/Actual (F2513) app. The Project Cost screen displays.
3 Enter Selection Criteria In the Standard section, make the following entries, and Details of the project structure and the corresponding planned, actual costs,
choose Go. project stock costs, and commitments are displayed.
Project: <Refer to the project created in Create Project>
Planning Category 1: Plan
Planning Category 2: CPM Baseline
R.000001 (for Revenue Project)
4 Navigation to Project Cost Report - Line items; Select the project in the table, and choose View Details. Plan and Actual costs are displayed.
view details of different cost On the Project Costs - line items screen, check financials us-
ing the drill-down and filter options.
4.8.4 Monitor Projects via P&L Plan/Actual
Test Administration
Purpose
In this activity, analyze the cost structure of your project and compare actual vs planned.

Appendix PUBLIC 51
Procedure
2 Access App Open P&L - Plan/Actual(F1710)

.
3 Enter Selection Criteria In the Standard section, make the following entries and choose Go. At least one entry is shown in the Data Analysis area.
Ledger:0L
Ledger Fiscal Year: Current year
Planning Category: PLN
Project definition: <Refer the respective Project created in the chapter Create Project [page ] 21
R.000001 (for Revenue Project)
4 Check Financials Check financials using drill-down and filter options. All actual costs are displayed.
4.9 Close Project
Test Administration
Purpose
Note All the pending down payments should be cleared before you proceed with the project closure. You can use the app Manage Customer Line Items and search for your WBS.
A detailed process on clearing down payments is explained in the Accounts Receivable (J59) test script.
.

Appendix PUBLIC 52
In this activity, you close the completed project, that is, you set the project processing status to Closed.
Procedure
# ment
2 Access App Open the Project Control - Enterprise Projects (F3215) app. The Project Control screen displays.
3 Open Project In the Standard section, make the following entries, and choose Go. At least one entry is displayed in the Worklist
Project: <Refer to the project created in the Create Project test procedure.> area.
4 Close project and struc- Select the Project and in the header section, choose Processing Status > Complete . Then, choose Processing The project is saved with the processing status
ture Status > Close . Closed.

Appendix PUBLIC 53
5 Appendix
5.1 Process Integration

The process to be tested in this test script is part of a chain of integrated processes.
5.1.1 Succeeding Processes

After completing the activities in this test script, you can continue testing the following business processes:
Process Business Condition
BNA Period-End Closing - Projects

Appendix PUBLIC 54
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 .
© 2024 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-

Project Control – Sales (4I9_DE) tion and notices.
Appendix PUBLIC 55

4i9 s4cld2308 BPD en de

Uploaded by

Copyright:

Available Formats

4i9 s4cld2308 BPD en de

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4i9 s4cld2308 BPD en de

Uploaded by

Copyright:

Available Formats

Test Script

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

Project Control – Sales (4I9_DE)

Project Control – Sales (4I9_DE)

Project Control – Sales (4I9_DE)

2.1 System Access

Project Financial SAP_BR_PROJ_FIN_CON- Project Financial Controller SAP_BR_PROJ_FIN_CONTROLLER

Project Manager SAP_BR_PROJECTMANAGER Project Manager SAP_BR_PROJECTMANAGER

Billing Clerk SAP_BR_BILLING_CLERK Billing Clerk SAP_BR_BILLING_CLERK

Accounts Receiv- SAP_BR_AR_ACCOUNTANT Accounts Receivable Accountant SAP_BR_AR_ACCOUNTANT

Shipping Specialist SAP_BR_SHIPPING_SPE- Shipping Specialist SAP_BR_SHIPPING_SPECIALIST

Project Control – Sales (4I9_DE)

Cost Accountant - SAP_BR_SALES_ACCOUNTANT Cost Accountant - Sales SAP_BR_SALES_ACCOUNTANT

2.3 Master Data, Organizational Data, and Other Data

Data Sample Value Details Comments

Controlling Area A000 Controlling Area A000

Company Code 1010 Company Code 1010

Plant 1010 Plant 1 DE

Cost Center 10101501 R&D Cost center

Costing Sheet 1010PI Costing Sheet-PS Projects

Activity Types 8 Consulting

G/L Account 61005000 Trav. Expense - Ground transportation

Profit Center YB600 Shared Services

Project Control – Sales (4I9_DE)

Functional Area YB25 Consulting/Services

BNM Create Cost Center and Cost Center Group

BNG Create G/L Account and Cost Element

BNH Create Profit Center

2.4 Business Conditions

Scope Item ID Business Condition

Project Control – Sales (4I9_DE)

2.5.1 Maintain Financial Statement Versions

2.5.2 Create Project Coding Mask (Optional)

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Project Control – Sales (4I9_DE)

1 Log on Log on to the Fiori Launchpad as a

Application Area: Enterprise Portfolio & Project Management

SAP Central Business Configuration:

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

1 Log on Log on to the project experience in SAP Central Business Configuration.

Project Control – Sales (4I9_DE)

2.5.3 Create Project Types for WBS Elements (Optional)

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Project Control – Sales (4I9_DE)

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

Application Area: Enterprise Portfolio & Project Management

SAP Central Business Configuration:

Project Control – Sales (4I9_DE)

1 Log on Log on to the project experience in SAP Central Business Configuration.

2.5.4 Maintain Budget Availability Profile (Optional)

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Project Control – Sales (4I9_DE)

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