Test Script

SAP S/4HANA - 14-09-23

Statistical Sales Conditions (34B_US)

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 Additional Manual Configuration
2.5 Preliminary Steps
2.5.1 Set Initial Stock for Material

3 Overview Table

4 Test Procedures
4.1 Create Sales Order
4.2 Create Delivery
4.3 Execute Picking
4.4 Post Goods Issue
4.5 Create Billing Document
4.6 Sales Order Actual Report
1 Purpose

Overview

To transfer statistical conditions from SD to account-based COPA, you write statistical condition values to extension ledger 0C. The transfer of statistical SD conditions to account-based COPA is
via G/L accounts. The account key is assigned to a statistical condition, is posted to the G/L, and is set as relevant for account determination in the pricing procedure. For example, a statistical cash
discount is posted to the extension ledger during billing.
To use the functionality for other statistical SD condition use cases (such as warranties, discounts, and so on), you make the following settings for the price condition: the price condition is used for
statistics only, that is, you have selected the Statistics indicator; you have selected an Account key that defines two accounts (the Accruals key is not considered).
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.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 2
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
Assign the following business roles to your individual test users. Alternatively, if available, you can create business roles using the following spaces with pages and predefined apps for the SAP Fiori
launchpad and assign the business roles to your individual test users.

Note These roles or spaces are examples provided by SAP. You can use them as templates to create your own roles or spaces.
For more information about business roles, refer to Assigning business roles to a user in the Administration Guide to Implementation of SAP S/4HANA with SAP Best Practices.

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

Internal Sales Representative SAP_BR_INTERNAL_SALES_REP Internal Sales SAP_SD_SP_INTERNAL_SALES

Shipping Specialist SAP_BR_SHIPPING_SPECIALIST Shipping SAP_LE_SP_OUTBD

Cost Accountant - Sales SAP_BR_SALES_ACCOUNTANT Sales Accounting SAP_SFIN_SP_SA_ACC

Billing Clerk SAP_BR_BILLING_CLERK Billing SAP_SD_SP_BILLING

Warehouse Clerk SAP_BR_WAREHOUSE_CLERK Inventory Processing SAP_MMIM_SP_INVENTORY_PROCESS

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 3
2.3 Master Data, Organizational Data, and Other Data
SAP Best Practices Standard Values based on new global template will be used once available. In the table you still see the master data used for the current baseline.
Essential master and organizational data was created in your SAP S/4HANA system in the implementation phase, such as the data that reflects the organizational structure of your company and mas-
ter data that suits its operational focus, for example, master data for materials, vendors, and customers.
This master data usually consists of standardized SAP Best Practices default values, and enables you to go through the process steps of this scope item.

Note Additional Master Data (Default Values)

You can test the scope item with other SAP Best Practices default values that have the same characteristics.
Check your SAP system to find out which other material master data exists.

Note Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data.

Note The condition type DCD1 or DCD2 for cash discount is filled only if in the material master the indicator for cash discount is set: (View - Sales Order, Field - Cash discount) - for exam-
ple, as marked in material master TG11.

Use the following master data in the process steps described in this document:

Master / Org. Data Value Master / Org. Data Details Comments

Material TG11 Trading Good for Reg. Trading (MRP planning) See sections Business Conditions and Preliminary Steps.
No serial number, no batch

Material TG12 Trading Good for Reg. Trading (reorder point planning) See sections Business Conditions and Preliminary Steps.
No serial number, no batch

Sold-to Party 17100002 Domestic US Customer 2

Ship-to Party 17100002 Domestic US Customer 2

Payer 17100002 Domestic US Customer 2

Plant 1710

Storage Location 171A

Shipping Point 1710

Sales Organization 1710

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 4
 Master / Org. Data Value Master / Org. Data Details Comments

Distribution Channel 10

Division 00

SD Condition Type DCD2 Cash Discount Net These are marked as statistical conditions and relevant for Account Determination (demo data)
DCD1 Cash Discount Gross

Account Key YSC

G/L Account 71055000 Accrual statistical condition Posting to extension ledger 0C

21775000 Statistical condition cash discount

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

BNF Create Product Master of Type "Trading Good"

BND Create Customer Master

2YX Create Customer-Material Info Record

2.4 Additional Manual Configuration

Before you can test this scope item, you must have completed the additional configuration steps that are described in the Set-Up Instructions for this scope item. These configuration steps are specific
for your implementation and include mandatory settings that are not delivered by SAP and must be created by you. For more information, follow the link to the document:
Link to Set-Up Instructions

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 5
2.5 Preliminary Steps

2.5.1 Set Initial Stock for Material

Purpose

To execute this scope item, the materials must be available in stock.

Procedure

Test Step Test Step Name Instruction Expected Result Com-

# ments

1 Log On Log on to the SAP Fiori launchpad using a Warehouse Clerk. The SAP Fiori launchpad displays.

2 Access the App Open Post Goods Movement (MIGO) The Goods Issue Other - <warehouse_clerk USER ID>
screen displays.

3 Input Movement Type Make the following entry and choose Enter. The Goods Receipt Other screen displays.
● Executable Action in Transaction MIGO: Goods Receipt
● Reference Document for MIGO Transaction: Other

4 Input on the Goods Receipt Other screen: Mate- On the Goods Receipt Other screen: Material tab, make the following entry and
rial tab choose Enter:
● Material: Material Number, for example TG11

5 Enter Quantity Data On the Goods Receipt Other screen: Quantity tab, make the following entry and
choose Enter:
● Qty in Unit of Entry: Qty in UOM, for example 5
● Unit of Entry: PC

6 Input on the Goods Receipt Other screen: On the Goods Receipt Other screen: Where tab, make the following entries and
Where tab choose Enter:
● Movement Type: 561 - Receipt per initial entry of stock balances into unr.-use
● Plant: <Enter a Plant>, for example 1710
● Storage Location: <Enter a Storage Location>, for example 171A

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 6
 Test Step Test Step Name Instruction Expected Result Com-
# ments

7 Input on the Goods Receipt Other screen: Batch On the Goods Receipt Other screen: Batch tab, make the following entry and
tab choose Enter:
● Date of manufacture: <Enter the current date or a date in
the past>

Note Only applicable for batch relevant materials.

8 Save your entries. Click Post.

Financial postings:

Material Debited Accounts Credited Accounts

Trading Good (HAWA) 13600000 39912000

Inventory TradingGd Inv Init SF&amp;Fin Bal

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 7
3 Overview Table

This scope item consists of several process steps that are listed in the following table:

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 apps not included on the homepage using the search bar.
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 Transaction/App Name Expected Results

Create Sales Order [page ] 9 Internal Sales Representative Manage Sales Orders (F1873) The Manage Sales Orders screen displays.

Create Delivery [page ] 11 Shipping Specialist Create Outbound Deliveries - From Sales Orders (F0869A) The Create Outbound Deliveries screen displays.

Execute Picking [page ] 12 Shipping Specialist My Outbound Delivery Monitor (VL06O) The Manage Sales Orders screen displays.

Post Goods Issue [page ] 13 Shipping Specialist My Outbound Delivery Monitor (VL06O) The goods issue is posted.

Create Billing Document [page ] 14 Billing Clerk Create Billing Documents (F0798) The Create Billing Document screen displays.

Sales Order Actual Report [page ] 16 Cost Accountant - Sales P&L - Plan/Actual (F1710) The actual figures for sales orders displays.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 8
4 Test Procedures

This section describes procedures for each process step that belongs to this scope item.
The Enterprise search function provides a central entry point for finding business objects in your company from different sources using a single search request, You can search for objects such as:
Apps, factsheets for business objects. From the data found, you can go directly to the respective apps and factsheets to display, edit the data or find related objects.
How to access and check a factsheet:
1. Log onto the SAP Fiori Launchpad using the respective user, for example, Internal Sales Representative.
2. Access the Enterprise Search Bar and choose the magnifying glass button in the upper right corner.
3. The Enterprise Search bar is displayed, two filter fields appear left to the search button. Enter your Search Criteria and choose the business object type, for example, Sales orders from drop-down
menu in 1st field, enter sales order number in 2nd field and choose Search, The sales order is listed.
4. Choose the sales order number link: the system navigates to the factsheet screen and sales order related information is integrated and summarized in one Fiori page, You can get detailed data via
choosing the corresponding links.
There are factsheets available for the following objects: (Visible depending on the assigned role)
● Sales order
● Quotation
● Create Nota Fiscal
● Billing document
● Credit Memo
● Debit Memo
● Customer 360 Fact sheet

4.1 Create Sales Order

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>

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 9
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Rep- The SAP Fiori launchpad displays.
resentative.

2 Access the SAP Fiori Open Manage Sales Orders (F1873). The Manage Sales Orders screen displays.
App

3 Navigate to Create Order Choose the Create Sales Orders - VA01 button.
Screen

4 Enter the Order type OR On the Create Sales Documents screen, make the following
(Standard Order) entries and choose the Continue button:
● Order Type: OR
● Sales Organization: 1710
● Distribution Channel: 10
● Division: 00

5 Enter Order Details On the Create Standard Order: Overview screen, make the Customer master data 17100002 is defaulted with payment terms 0004, so you can assign payment
following entries and press Enter: terms 0002 in the customer order.
● Sold-To Party: 17100002 This ensures the cash discount in this sales order, and therefore condition type DCD1 or DCD2 for cash
● Ship-To Party: 17100002 discount is filled. This statistical condition value will be posted to Extension Ledger 0C.

● Cust. Reference: <Enter a customer purchase

order number as reference>
● Cust. Ref. Date: <Enter a date>
● Pyt Terms: 0002
● Material: <Material number>, for example TG11
● Order Quantity: <Enter a quantity>

6 Save Document Choose the Save button. Make a note of the sales order The order is saved and the order confirmation is printed out.
number.

Note You can also navigate to a fact sheet screen in the Manage Sales Orders app:
1. On Manage Sales Orders screen, enter search terms in filter bar and choose Go.
2. In search result, choose your sales order number.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 10
4.2 Create Delivery

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 create the delivery.

Procedure

Test Step Test Step Name Instruction Expected Result Com-

# ments

1. Log On Log on to the SAP Fiori launchpad as a Shipping Specialist.

2. Access the SAP Fiori Open Create Outbound Deliveries - From Sales Orders The Create Outbound Deliveries screen displays.
App (F0869A).

3. Search Sales Order Make the following entries and choose Go:
● Shipping Point: 1710
● Planned Creation Date: <Delivery selection date>
● Sales Document: Sales order number created
previously

4. Create Delivery Select your sales order items and choose Create Deliveries. Creation of a delivery is triggered.

5. Check Details Choose Display Log The Analyze Delivery Log screen displays, delivery is created successfully with delivery number
shown on tab Deliveries.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 11
To avoid open deliveries, ensure that there is sufficient inventory quantity at the time of delivery creation. Additionally, you have the following options to restrict the creation of deliveries with no
confirmed quantities:
● You can increase the replenishment lead time which is used during the availability check (has to be larger than the selection period used for delivery creation).
● You can change the customization settings for the incompleteness procedure for delivery creation, so that only complete deliveries are saved.
● You can change the customization settings for the used delivery-item-category. The Check quantity 0 field must be adapted to B = Situation rejected with an error message.

Note With the Analyze Delivery Logs app, you can display an overview about the logs of all the deliveries which have been created in your system. You can filter by Created by and other addi-
tional settings. If you select the arrow on the right of each delivery log entry, you can display the exact message type and text and also the related sales document.

4.3 Execute Picking

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

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 Shipping Specialist. The SAP Fiori launchpad screen displays.

Statistical Sales Conditions (34B_US)

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

2 Access the SAP Fiori App Open My Outbound Delivery Monitor (VL06O). The Outbound Delivery Monitor screen
displays.

3 Choose Picking Choose For Picking.

4 Enter Shipping Point Make the following entries, and choose Execute.
● Shipping point: 1710
● Only Picking without WM: X

5 Change Outbound Delivery From Day’s Workload for Picking , select your delivery number and choose Change Outbound Deliveries.
(Original)

6 Check if Batch Split Exists Navigate to the Picking tab, check if batch split exists in Batch Split Indicator column:
Yes: go to 7 a.
No: go to 7 b.

7 Enter Picked Quantity ● 7a: Choose Batch Split Exists to expand subitems, enter quantity equal to delivery Qty in the Picked Qty
field for subitem.
● 7b: Enter quantity equal to delivery Qty in the Picked Qty field for picking related items.

8 Choose Enter Choose Enter.

9 Save Choose Save. The delivery has been picked.

4.4 Post Goods Issue

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>

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 13
Purpose

In this activity, you post the goods issues for the delivery.

Procedure

Test Step Test Step Name Instruction Expected Result Com-

# ments

1. Log On Log on to the SAP Fiori launchpad as a Shipping Specialist.

2. Access the SAP Fiori App Open My Outbound Delivery Monitor (VL06O). The Outbound Delivery Monitor screen dis-
plays.

3. Open Outbound Delivery Moni- Choose For Goods Issue. Make the following entry and choose Execute. A list of relevant deliveries is displayed.
tor Shipping point: 1710

4. Post Goods Issue Mark the relevant delivery and choose Post Goods Issue. Select today’s date from the dialog box and choose The goods issues are posted for the delivery.
Continue.

Financial Postings:

Material (Original) Debited Accounts Credited Accounts Cost Element / CO Object

Trading Good (HAWA) 51600000 13600000 none

Consptn Trde Gds Inventory TradingGd

4.5 Create Billing Document

Test Administration

Customer project: Fill in the project-specific parts.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 14
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 billing is handled in this activity.

Create Billing Document

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Billing Clerk. The SAP Fiori launchpad displays.

2 Access the SAP Open Create Billing Documents (F0798). The Create Billing Documents
Fiori App (F0798) screen displays.

3 Define billing Choose Billing Settings in the bottom bar, and make the following settings:
setting ● Set billing date and type before billing: ON
● Create separate billing document for each item of billing due list: OFF
● Automatically post billing documents: ON
● Display billing documents after creation: ON
● Choose delivery items to be billed and select quantities: OFF

4 Search for In the search condition, use criteria if necessary. The sales documents display.
billing due list

5 Select items for Select rows of sales document created previously and choose the Create button. Create Billing Documents displays.
billing

6 Maintain Billing Choose billing type Invoice (F2) and maintain billing date, for example current date, then press button OK. The draft billing document with ID
Date Sxxxxxxxx will be displayed.

7 Save Billing In the Billing Document screen, choose the Save button. The draft version billing document with ID Sxxxxxxxx turns into a saved The system generates an invoice for
Document billing document with ID xxxxxxxx, make a note of the billing document number: __________.. billing.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 15
Financial Postings:

Material Debited Accounts Credited Accounts Cost Element / CO Object

Trading Good (HAWA) 17100002 41000000 none

Rcvbls Domestic US 3 Rev Domestic Prod
22001000
Sales/Use Tax Accrue
22002000
Sales/Use Tax Accrue
22003000
Sales/Use Tax Accrue
22004000
Sales/Use Tax Accrue
21730000
(optional) Freight Clrg MM

4.6 Sales Order Actual Report

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, the sales order report is generated.

Statistical Sales Conditions (34B_US)

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

2 Access the SAP Fiori Open P&L - Plan/Actual (F1710). The P&L - Plan/Actual screen displays.
app

3 Enter Data Make the following entries : The actual figures for sales orders displays.
Ledger: 0C (Management Accounting)
Fiscal Year of Ledger: <Enter the current year>
Fiscal Period: <Enter the current period>
Company Code: 1710
G/L Account Hierarchy: YPS2
Planning Category: ACT01
Choose Go.

4 Set Dimensions To set dimensions for reporting, drag and drop items from section Dimensions into sections The selected dimensions are presented as rows and columns on
Columns or Rows. the report.

Statistical Sales Conditions (34B_US)

Test Procedures PUBLIC 17
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-

Statistical Sales Conditions (34B_US) tion and notices.
Test Procedures PUBLIC 18