Statistical Sales Conditions (34B - MX) : Test Script SAP S/4HANA - 30-08-19

Statistical Sales Conditions (34B_MX) PUBLIC
¡Error! Utilice la pestaña Inicio para aplicar Heading 1 al texto que desea que aparezca aquí. Error: Reference source not found 1
Test Script PUBLIC

SAP S/4HANA - 30-08-19
Statistical Sales Conditions (34B_MX)
Table of Contents
1 Purpose 2
2 Prerequisites 3
2.1 System Access 3
2.2 Roles 3
2.3 Master Data, Organizational Data, and Other Data 3
2.4 Preliminary Steps 5
2.4.1 Set Initial Stock for Material 5
3 Overview Table 8
4 Test Procedures 9
4.1 Create Sales Order 9
4.2 Create Delivery 11
4.3 Execute Picking 13
4.4 Post Goods Issue 14
4.5 Create Billing Document 15
4.6 Sales Order Actual Report 17
1 Purpose
To transfer statistical conditions from SD to account-based COPA, you write statistical condition values to Extension Ledger 0C. The transfer of statistical SD condition 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.

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.
Note The following roles are provided as example roles from SAP. You can use these as templates for your own roles.
Business Role Business Role ID as Delivered by Log

SAP On
Internal Sales Representative SAP_BR_INTERNAL_SALES_REP
Shipping Specialist SAP_BR_SHIPPING_SPECIALIST
Cost Accountant - Sales SAP_BR_SALES_ACCOUNTANT
Billing Clerk SAP_BR_BILLING_CLERK
Warehouse Clerk SAP_BR_WAREHOUSE_CLERK
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 S/4HANA system in the implementation phase, such as the data that reflects the organizational structure of your company and master
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.
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.
Using Your Own Master Data
You can also use customized values for any material or organizational data for which you have created master data. For more information about creating master data, see the Master Data Procedures
documentation.
Use the following master data in the process steps described in this document:
Master / Org. Value Master / Org. Data Details Comments

Data
Material TG11 Trading Good for Reg. Trading (MRP planning) See sections Business Conditions and Preliminary Steps.
No serial number, no batch Use TG11 to test customer material, recorded with customer 55100009.
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 55100001 Customer domestic 01
Ship-to Party 55100001 Domestic MX Customer 1
Payer 55100001 Domestic MX Customer 1
Plant 5510
Storage Location 551A
Shipping Point 5510
Sales Organization 5510
Distribution 10
Channel
Division 00
SD Condition DCD2 Cash Discount Net These are marked as statistical conditions and relevant for Account Determination
Type DCD1 Cash Discount Gross (demo data)
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 the following Master Data Scripts (MDS)

Table 1: Master Data Script Reference
MD Description
S
BNF Create Product Master of Type "Trading Good"
BND Create Customer Master
2YX Create Customer-Material Info Record
2.4 Preliminary Steps
2.4.1 Set Initial Stock for Material
Purpose
To execute this scope item, the materials must be available in stock.
Procedure
Test Test Step Name Instruction Expected Result Comme

Step # nts
1 Log On Log on to the SAP Fiori launchpad using a Warehouse Clerk. The SAP Fiori launchpad displays. OK
2 Access the App Open Post Goods Movement (MIGO) The Goods Issue Other - <warehouse_clerk USER OK
ID> screen displays.
3 Input Movement Type Make the following entry and choose Enter. The Goods Receipt Other screen displays. OK
● Executable Action in Transaction MIGO: Goods Receipt
● Reference Document for MIGO Transaction: Other
4 Input on the Goods Receipt Other On the Goods Receipt Other screen: Material tab, make the following OK
screen: Material tab entry and choose Enter:
● Material: Material Number, for example TG11
5 Enter Quantity Data On the Goods Receipt Other screen: Quantity tab, make the following OK
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 On the Goods Receipt Other screen: Where tab, make the following OK
screen: Where tab entries and choose Enter:
● Movement Type: 561 - Receipt per initial entry of stock balances
into unr.-use
● Plant: <Enter a Plant>, for example 5510
● Storage Location: <Enter a Storage Location>, for example
551A
7 Input on the Goods Receipt Other On the Goods Receipt Other screen: Batch tab, make the following OK
screen: Batch tab entry and 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. OK
Financial postings:
Material Debited Accounts Credited Accounts

Trading Good 13600000 39912000
(HAWA) Inventory TradingGd Inv Init SF&Fin
Bal

3 Overview Table
This scope item consists of several process steps that are listed in the following table:
Process Step Business Role Transaction/App Name Expected Results

Create Sales Order [page ] 9 Internal Sales Manage Sales Orders - Beta Version (F2712) The Manage Sales Orders screen displays.
Representative
Create Delivery [page ] 11 Shipping Specialist Create Outbound Deliveries - From Sales Orders The Create Outbound Deliveries screen displays.
(F0869A)
Execute Picking [page ] 12 Shipping Specialist My Outbound Delivery Monitor (VL06O) The Manage Sales Orders screen displays.
Post Goods Issue [page ] 14 Shipping Specialist My Outbound Delivery Monitor (VL06O) The goods issue is posted.
Create Billing Document Billing Clerk Create Billing Documents (F0798) The Create Billing Document screen displays.
[page ] 15
Sales Order Actual Report Cost Accountant - Sales Sales Orders - Actuals (F1035) The actual figures for sales orders displays. You can see that the cash discount is
[page ] 17 posted in ledger 0C.

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.
1. Access the Enterprise Search Bar and choose the magnifying glass button in the upper right corner.
2. 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.
3. 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> Tester Name Testing Date Enter a test date.

Business
Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an The SAP Fiori launchpad displays. OK
Internal Sales Representative.
2 Access the SAP Open Manage Sales Orders (F1873). The Manage Sales Orders screen displays. OK
Fiori App
3 Navigate to Create Choose the Create Sales Orders - VA01 button. OK
Order Screen
4 Enter the Order On the Create Sales Documents screen, make OK
type OR (Standard the following entries and choose the Continue
Order) button:
● Order Type: OR
● Sales Organization: 5510
● Distribution Channel: 10
● Division: 00
5 Enter Order Details On the Create Standard Order: Overview Customer 55100002 is eligible for cash discount as per terms of payment 0002 and in this OK
screen, make the following entries and press sales order, condition type DCD1 for cash discount is filled. This statistical condition value
Enter: will be posted to Extension Ledger 0C.
● Sold-To Party: 55100002
● Ship-To Party: 55100002
● 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 The order is saved and the order confirmation is printed out. Pedido estándar
sales order number. 8 se ha grabado.
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.
4. In search result, choose your sales order number.
4.2 Create Delivery
Test Administration
Business
Role(s)
Purpose
In this activity, you create the delivery.

Procedure
Test Test Step Name Instruction Expected Result Comments

Step #
1. Log On Log on to the SAP Fiori launchpad as a Shipping OK
Specialist.
2. Access the SAP Open Create Outbound Deliveries - From Sales The Create Outbound Deliveries screen displays. OK
Fiori App Orders (F0869A).
3. Search Sales Order Make the following entries and choose Go: OK
● Shipping point: 5510
● Planned Creation Date: <Delivery selection
date>
● SD Document: Sales order number created
previously
4. Create Delivery Select your sales order items and choose Create Creation of a delivery is triggered. Entrega 80000009
Deliveries. grabado
5. Check Details Choose Display Log The Analyze Delivery Log screen displays, delivery is created successfully with OK
delivery number shown on tab Deliveries.
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 Outbound 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
additional 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

Business
Role(s)
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

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Shipping Specialist. The SAP Fiori launchpad screen OK
displays.
2 Access the SAP Fiori App Open Manage Outbound Deliveries - VL06O (VL06O_CLOUD). The Manage Outbound Deliveries OK
screen displays.
3 Choose Picking Choose For Picking. OK
4 Enter Shipping Point Make the following entries, and choose Execute. OK
● Shipping point: 5510
● Only Picking without WM: X
5 Change Outbound From Day’s Workload for Picking , select your delivery number and choose Change OK
Delivery (Original) Outbound Deliveries.
6 Check if Batch Split Exists Navigate to the Picking tab, check if batch split exists in Batch Split Indicator column: OK
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 OK
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. Entrega 80000009
grabado
9 Save Choose Save. The delivery has been picked. OK
4.4 Post Goods Issue
Test Administration
Business
Role(s)
Purpose
In this activity, you post the goods issues for the delivery.
Procedure
Test Test Step Name Instruction Expected Result Comme

Step # nts
1. Log On Log on to the SAP Fiori launchpad as a Shipping Specialist. OK
2. Access the SAP Fiori Open Manage Outbound Deliveries (F0867A). The Manage Outbound Deliveries screen OK

App displays.
3. Open Outbound Choose For Goods Issue. Make the following entry and choose Execute. The Goods Issue for Outbound Deliveries to be OK
Delivery Monitor Shipping point: 5510 Posted view displays.
4. Post good issue Mark the relevant delivery and choose Post Goods Issue (Original). Select today’s date The goods issues are posted for the delivery. OK
from the dialog box and choose Continue.
Financial Postings:
Material (Original) Debited Credited Accounts Cost Element / CO

Accounts Object
Trading Good 51600000 13600000 none
(HAWA) Consptn Trde Gds Inventory TradingGd
4.5 Create Billing Document
Test Administration
Business
Role(s)
Purpose
The billing is handled in this activity.

Create Billing Document
Test Test Step Instruction Expected Result Pass / Fail /

Step # Name Comment
1 Log On Log on to the SAP Fiori launchpad as a Billing Clerk. The SAP Fiori launchpad OK
displays.
2 Access the Open Create Billing Documents (F0798) The Create Billing Documents OK
SAP Fiori App (F0798) screen displays.
3 Define billing Choose Billing Settings in the bottom bar, and make the following settings: OK
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
4 Search for In the search condition, use criteria if necessary. Sales documents display. OK
billing due list
5 Select items Select rows of sales document created previously and choose the Create button. Create Billing Documents OK
for billing displays.
6 Maintain Choose billing type Invoice (F2) and maintain billing date, for example current date, then press button The draft billing document with OK
Billing Date OK. ID Sxxxxxxxx will be displayed.
7 Save Billing In the Billing Document screen, choose the Save button. The draft version billing document with ID The system generates an invoice Documento
Document Sxxxxxxxx turns into a saved billing document with ID xxxxxxxx, make a note of the billing document for billing. 90000006 grabado.
number: __________..
Financial Postings:
Material Debited Credited Cost Element / CO

Accounts Accounts Object
Trading Good 41000000 none
(HAWA) Rev Domestic Prod

4.6 Sales Order Actual Report
Test Administration
Business
Role(s)
Purpose
In this activity, the sales order report is generated.
Procedure

Step # Comment
1. Log On Log on to the SAP Fiori launchpad as a Cost Accountant - Sales. The SAP Fiori launchpad displays.
2. Access the SAP Open Sales Orders - Actuals (F1035). The Sales Orders - Actuals screen displays.
Fiori app
3. Enter Data Make the following entries : The actual figures for sales orders displays. You can see that the
Ledger Fiscal Year: <Enter the current year> cash discount is posted in ledger 0C.
Ledger: 0C
Fiscal Period: <Enter the current period>
Company Code: 5510
G/L Account (Hierarchy): YPS2

Sales order: <Created in the previous step>
Choose Go.
4. Set Dimensions To set dimensions for reporting, drag and drop items from section The selected dimensions are presented as rows and columns on
Dimensions into sections Columns or Rows. the report.

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
INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and
parameters, source text, and names of installation, upgrade and database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the
documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system. © 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . for any purpose without the express permission of SAP SE or an SAP
affiliate company.
The information contained herein may be changed without prior notice. Some
software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP 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
warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop or release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platforms,
directions, and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice.
The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned
not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their
Statistical Sales Conditions (34B_MX) respective logos are trademarks or registered trademarksPUBLIC
of SAP SE (or an
¡Error! Utilice la pestaña Inicio para aplicar Heading 1 al texto que desea que aparezca aquí. Error:and
SAP affiliate company) in Germany Reference source not
other countries. Allfound
other product 19
and service names mentioned are the trademarks of their respective
companies.
See www.sap.com/copyright for additional trademark information and

notices.

Statistical Sales Conditions (34B - MX) : Test Script SAP S/4HANA - 30-08-19

Uploaded by

Copyright:

Available Formats

Statistical Sales Conditions (34B - MX) : Test Script SAP S/4HANA - 30-08-19

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

Statistical Sales Conditions (34B - MX) : Test Script SAP S/4HANA - 30-08-19

Uploaded by

Copyright:

Available Formats

Statistical Sales Conditions (34B_MX) PUBLIC

Test Script PUBLIC