Od9 S4CLD2402 BPD en Us

Test Script
SAP S/4HANA Cloud - 21-12-23
Sell from Stock (OD9_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 Business Conditions
2.6 Preliminary Steps
2.6.1 Set Initial Stock for Material
2.6.2 Set Relevant for Proof of Delivery in BP Master Data (Optional)
2.6.3 Create Template Item Proposal (Optional)
2.6.4 Create Condition Records (Optional)
2.6.5 Product Hierarchy
2.6.5.1 Extend Product Hierarchy Materials (Optional)
2.6.5.2 Maintain Product Hierarchy Condition(Optional)
2.6.5.3 Maintain Product Hierarchy to Distribution Chain (Optional)
2.6.5.4 Define Relevant Date for Product Hierarchy Determination (Optional)
2.6.6 Import Sales Orders (Optional)
2.6.7 Create Sales Order with Selling Recommender (Optional)
2.6.7.1 Assign Customer Procedure for Product Proposal to Business Partner
2.6.7.2 Create Sales Orders for Selling Recommender
2.6.7.3 Schedule Job for Intelligent Proposal
2.6.8 Preliminary Steps for Sales Order Approval (Optional)
2.6.8.1 Define and Assign Approval Reasons
2.6.8.2 Implement Cloud BADI
2.6.8.3 Manage Teams and Responsibilities
2.6.8.4 Set up Workflow
2.6.9 Preliminary Steps for Preliminary Billing Approval (Optional)
2.6.10 Derivation Set-up for Cost Center
3 Overview Table
4 Test Procedures
4.1 Create Sales Order
4.2 Create Attachment for Sales Order (Optional)
4.3 Process Sales Order Approval (Optional)
4.3.1 Withdraw from Approval
4.3.2 Approve/Reject/Rework Sales Order
4.3.3 Rework Sales Order
4.3.3.1 Check the Notifications
4.3.3.2 Change Sales Order
4.4 Create Delivery
4.5 Create Attachment for Delivery (Optional)
4.6 Execute Picking
4.7 Check Batches (Optional)
4.8 Maintain Serial Numbers (Optional)
4.9 Split Outbound Delivery (Optional)
4.10 Add Freight Costs (Optional)
4.11 Post Goods Issue
4.12 Proof of Delivery (Optional)
4.13 Create Preliminary Billing Document (Optional)
4.14 Process Preliminary Billing Approval (Optional)
4.14.1 Finalize the Preliminary Billing Document
4.14.2 Rework from Approval
4.14.3 Approve/Reject/Rework Preliminary Billing Document
4.14.4 Rework Preliminary Billing Document
4.14.4.2 Change Preliminary Billing Document
4.15 Create Partial Billing Document (Optional)
4.16 Create Billing Document
4.17 Create Attachment for Billing (Optional)
5 Appendix
5.1 Process Integration
5.1.1 Succeeding Processes
5.2 Scheduling Job (alternative)

Appendix PUBLIC 2
5.2.1 Job Scheduling for Delivery Creation (Alternative)
5.2.2 Job Scheduling for Goods Issue Deliveries (Alternative)
5.2.3 Job Scheduling for Preliminary Billing Documents Creation (Alternative)
5.2.4 Job Scheduling for Billing Creation (Alternative)
5.2.5 Job Scheduling for Billing Release (Alternative)
5.2.6 Job Scheduling for Billing Output (Alternative)

Appendix PUBLIC 3
1 Purpose
Overview
The process starts with the creation of a customer and standard sales order. Depending on the customer and the process starts with the creation of a customer standard sales order.
After the completion of picking, the shipping specialist relieves the inventory. This inventory relief is the actual recording of the physical quantity that is being shipped to the customer.
With the goods issue posting revenue is recognized and cost of goods sold is recorded in Financial Accounting.
Once goods are delivered, you can invoice the delivery.
For details on bundling functionalities for IFRS 15, see note 2524569.
A preliminary billing document can be created from the billing due list items as an optional step. You can show it to customers to align on exact details and change if necessary. The final billing doc-
uments are created that customers are expected to settle.
A preliminary billing document can be created from the billing due list items as an optional step. You can show it to customers for alignment and changes as needed. The final billing documents are
created for the customer settlement.
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 4
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 ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
Template) On
Configuration SAP_BR_BPC_EXPERT Business Process Configuration / Business Configuration - Feature SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC / SAP_CA_SPT_BPC_WORK-
Expert - Busi- Management / Business Process Configuration - Workflow / Manage FLOW_PC / SAP_CA_SPT_IC_LND_BASE_PC / SAP_EI_SPT_BPC_EXT_PC /
ness Process your Solution / Business Process Configuration - Extensibility Ex- SAP_FIN_SPT_BPC_EXPERT_PC / SAP_MM_SPT_BIZ_PROC_CONFIGN_PC /
Configuration plorer / Business Process Configuration - Finance / Business Process SAP_TM_SPT_TRANSPCFG_PC
Configuration - Procurement / Business Configuration - Transporta-
tion
Internal Sales SAP_BR_INTERNAL_SAL Internal Sales / Billing / Customer Returns SAP_BR_INTERNAL_SALES_REP / SAP_SD_SPT_BILLING_INT_SALES_PC /
Representa- ES_REP SAP_SD_SPT_RETURNS_INT_SALES_PC
tive
Shipping Spe- SAP_BR_SHIPPING_SPE Shipping SAP_BR_SHIPPING_SPECIALIST

cialist CIALIST

Appendix PUBLIC 5
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log
Template) On
Warehouse SAP_BR_WAREHOUSE_CL Inventory Processing SAP_BR_WAREHOUSE_CLERK

Clerk ERK
Billing Clerk SAP_BR_BILLING_CLER Billing SAP_BR_BILLING_CLERK

K
Credit Con- SAP_BR_CREDIT_CON- Credit Management SAP_BR_CREDIT_CONTROLLER

troller TROLLER
Master Data SAP_BR_BUPA_MASTER_ Master Data - Business Partners SAP_BR_BUPA_MASTER_SPECIALIST

Specialist - SPECIALIST
Business Part-
ner Data
Sales Manager SAP_BR_SALES_MAN- Sales Management / Billing for Sales Manager / Internal Sales / Cus- SAP_BR_SALES_MANAGER / SAP_SD_SPT_BILLING_SALES_MGR_PC /
AGER tomer Returns for Sales Manager SAP_SD_SPT_INT_SALES_SALES_MGR_PC /
SAP_SD_SPT_RETURNS_SALES_MGR_PC
Business SAP_BR_BUSINESS_PRO Business Process Management / Business Process Management / SAP_BR_BUSINESS_PROCESS_SPEC / SAP_CA_SPT_BPS_PC /
Process Spe- CESS_SPEC
cialist
Administrator SAP_BR_ADMINISTRA- Administration / Administration - Workforce Master Data / Adminis- SAP_BR_ADMINISTRATOR / SAP_BUM_SPT_ADMINISTRATION_PC /
TOR tration - License Compliance / Administration - Output Control SAP_EI_SPT_ADM_LC_PC / SAP_OC_SPT_ADMINISTRATION_PC
Pricing Spe- SAP_BR_PRICING_SPE- Price Management SAP_BR_PRICING_SPECIALIST

cialist CIALIST
Master Data SAP_BR_PRODMASTER_S Master Data - Products SAP_BR_PRODMASTER_SPECIALIST

Specialist - PECIALIST
Product Data
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.

Appendix PUBLIC 6
Master / Org. Data Value Master / Org. Data Details Comments
Material TG11 Trading Good for Reg. Trading (MRP planning) See Business Conditions and Preliminary Steps sections .
No serial number, no batch Use TG11 to test customer material, recorded with customer 17100009.
Material TG12 Trading Good for Reg. Trading (reorder point See Business Conditions and Preliminary Steps sections.
planning)
No serial number, no batch
Material TG20 Trading Good for Reg. Trading (reorder point Only use if you have activated Serial Number Managment (BLL).
planning)
Material TG21 Trad.Good 21,Reorder Point,Batch-FIFO Only use if you have activated Batch Management (BLG) (BLH)(BLJ)(2EG)(BLP) building block.
No serial number, batch controlled (FIFO strategy) See Business Conditions and Preliminary Steps sections.
Material TG22 Trad.Good 22,Reorder Point,Batch-ExpD Only use if you have activated Batch Management (BLG) (BLH)(BLJ)(2EG)(BLP) building block.
No serial number, batch controlled (Exp. Date) See Business Conditions and Preliminary Steps sections.
Material TG11_PH_CO21 Trading Goods for Product Hierarchy Only use if you have activated Product Hierarchy relevant (4EM) (4EN) building block.
TG11_PH_CO30U No serial number, no batch See Business Conditions and Preliminary Steps sections.
TG11_PH_CO30
TG11_PH_CW12
TG11_PH_CW14
TG11_PH_GP200
TG11_PH_GP300
TG11_PH_PP
TG11_PH_WC
Material IF11 Trading Good for IFRS SFS Test Material 1 Only use if you have activated Event-Based Revenue Recognition for Sale from Stock (BRT) (BRU)(37A)
building block.
See Business Conditions and Preliminary Steps sections.
Material IF12 Trading Good for IFRS SFS Test Material 2 Only use if you have activated Event-Based Revenue Recognition for Sale from Stock (BRT) (BRU)(37A)
building block.
See Business Conditions and Preliminary Steps sections.
Material CM-FL-V00 Forklift Only use if you have activated Make-to-Order Production with Variant Configuration (1YT).
Material SM0001 Service Material 01
Material NS0002 Non-stock Material 02

Appendix PUBLIC 7
Master / Org. Data Value Master / Org. Data Details Comments
Sold-to Party 17100003 Domestic US Customer 3 You can test the scope item using another domestic customer.
17100005 Domestic US Customer 5 17100005 is for credit management.
17100008 17100008 is for material listing or exclusion
17100009 17100009 is for customer material record and POD (Proof-of-Delivery)
17100008
17100009
Ship-to Party 17100003 Domestic US Customer 3

17100005 Domestic US Customer 5
17100008
17100009
Payer 17100003 Customer domestic 03

17100005 Customer domestic 05
17100008
17100009
Plant 1710
Storage Location 171A
Shipping Point 1710
Sales Organiza- 1710

tion
Distribution Chan- 10
nel
Division 00
You can find general information on how to create master data objects in the following Master Data Scripts (MDS) :
Table 1: Master Data Script Reference
Master Data ID Description
BNF Create Product Master of Type "Trading Good"

Appendix PUBLIC 8
BND Create Customer Master
2YX Create Customer-Material Info Record
6N3 Create Customer Hierarchy
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
2.5 Business Conditions

The business process described in this test script is part of a bigger chain of integrated business processes or scope items. As a consequence, you must have completed the following processes and
fulfilled the following business conditions before you can go through this scope item:
Scope Item Business Condition
O45 - Procurement of Direct Materials To run through this scope item, the materials must be available in stock. If you use trading goods (HAWA) you can either:
● Run through the Procurement of Direct Materials (O45) test script process.
● Or create stock using Post Goods Movement app (refer to Preliminary Steps section for details).
BNZ - Create New Open MM Posting Period You have completed the step described in the Create New Open MM Posting Period (BNZ) master data script. Posting Period is up to date.

Appendix PUBLIC 9
2.6 Preliminary Steps
2.6.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 as a Warehouse Clerk. The SAP Fiori launchpad dis-
plays.
2 Access the App Open Post Goods Movement (MIGO). The Goods Receipt Otherscreen
It only displays it that way if it was your last transaction. So the action for the user should be to select Reference displays.
Document for MIGO Transaction > Other.
3 Input Movement Type Make the following entry and choose Enter.
● Executable Action in Transaction MIGO: Goods Receipt
● Reference Document for MIGO Transaction: Other
4 Enter Material On the Goods Receipt Other Screen : Material tab, make the following entry and choose Enter:
● Material : <Material Number>
5 Enter Quantity Data On the Goods Receipt Other screen: Quantity tab, make the following entry and choose Enter:
● Qty in Unit of Entry: 1000
● 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 choose Enter:
Where tab ● Movement Type: 561 (Receipt per initial entry of stock balances into unr. use)
● Plant: <Plant>
● Storage Location: <Storage Location>

Appendix PUBLIC 10
# ments
7 Input on the Goods Receipt Other screen: On the Goods Receipt Other screen: Batch tab, make the following entry and choose Enter:
Batch tab ● Date of Manufacture: <Current Date or a Past Date>
Note Only relevant for batch-relevant material.
8 Enter the Goods Receipt Other Screen: Se- On the Goods Receipt Other screen: Serial Numbers tab, enter the serial number of your received material.
rial Number Tab
Note Only relevant for material TG20
9 Save Your Entries Choose Post.
Financial Postings:
Material Debited Accounts Credited Accounts
Trading Good (HAWA) 13600000 39912000

Inventory TradingGd Inv Init SF&Fin Bal
2.6.2 Set Relevant for Proof of Delivery in BP Master Data (Optional)
Purpose
To run the step, you must maintain the Proof of Delivery (POD)-relevant indicator for customer master data. From demo data, only customer 17100009 has been set, following procedure can help
you to set POD relevant for other customer master data if necessary.

Appendix PUBLIC 11
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Log On Log on to the SAP Fiori launchpad as a Master Data Specialist - Business Partner Data. The SAP Fiori launchpad displays.
2 Access the App Open Maintain Business Partner (BP). The Maintain Business Partner screen displays.
3 Enter Business Partner Make the following entry and choose Start.
Double click the line item of Business Partner: 17100009
4 Go to Shipping Tab On the Change Organization:XXXXXXXX screen, choose Customer (Defined) in the Change in BP Role field.
Choose Sales and Distribution in the Menu > More menu, then select Shipping tab .
5 Set POD - Relevant Select POD - Relevant checkbox.
6 Save Choose Save.
2.6.3 Create Template Item Proposal (Optional)
Purpose
This process helps you to create template for item proposal if you want to use the optional step, copy item proposal to sales order, later on, in the process step, sales order entry.
Procedure
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 Item Proposals (F2583). The Manage Sales Item Proposals screen displays.
3 Create New Object On the Manage Sales Item Proposals Screen, choose Create. The Sales Item Proposal Screen displays.
4 Enter Item Proposal Details On the Sales Item Proposal screen, in the Header Data tab, and make the following entries:

Appendix PUBLIC 12
Sales Document Type: PV

Sales Organization: 1710
Distribution Channel: 10
Division: 00
Description: < For example, Item Proposal Template>
Valid-From Date: <For example, Current Date>
Valid-To Date: <For example, Current Date + 1 Year>
5 Enter Item Proposal Details In the Products tab, choose Create:

Material Number: <Material Number>
Target Quantity: <Target Quantity>
6 Save the Entry Choose Create.
2.6.4 Create Condition Records (Optional)
Purpose
In case you have fine-tuned the access sequence of SAP pre-shipped condition types, the relative condition records should be created accordingly.
You can find general information on how to create master data objects in the following Master Data Scripts (MDS) :
Table 2: Master Data Script Reference
BET Create Sales Pricing Condition

Appendix PUBLIC 13
2.6.5 Product Hierarchy
2.6.5.1 Extend Product Hierarchy Materials (Optional)
Purpose
The procedure helps you to extend material organization. It is only relevant If you use ANC procedure to have the new country version, you need to manually extend the materials to your organiza-
tion
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 Master Data Specialist - Product Data.
2 Access the App Open Create Material (MM01)
3 Search for materials Make below entries and choose Continue

Material : TG11_PH_CO21
Material Type: Trading Goods

Appendix PUBLIC 14
# ment
4 Select Views In the pop up screen of Select View(s), select below views and choose Org.Levels:
Basic Data 1
Basic Data 2
Sales: Sales Org. Data 1
Sales: Sales Org. Data 2
Sales: General/Plant Data
International Trade: Export
Purchasing
International Trade: Import
MRP 1
MRP 2
MRP 3
MRP 4
General Plant Data / Storage 1
General Plant Data / Storage 2
Accounting 1
Accounting 2
5 Input Organization inforamtion In the pop up screen of Organization levels, input below entries and choose Continue:
Plant: 1710
Stor.Loc.: 171A/171R
Sales Org:1710
Distribution Channel:10
Note If message The material already exists and will be extended displays, please ig-
nore it.
6 Input Detail On the new screen of Create Material XXXXX (trading Goods),
In the tab of Sales: sales org.1,
● Description
● Tax Data
Choose Enter.
In tab of Sales: sales org.2,
Item Category Group: NORM
Choose Enter.

Appendix PUBLIC 15
# ment
In tab of Sales: General/Plant,

Profit Center: YB700
Choose Enter.
In tab of MRP 1,
MRP Type: PD
MRP Controller: 001
Lot Sizing Procedure: EX
Choose Enter.
In tab of MRP 2,
Planned Deliv. Time: 10 days
Choose Enter.
In tab of Accounting 1,
Valuation Class: 3100
Standard Price: 6
Per. Unit Price: 6
Choose Enter.
Choose Save.
7 Repeat step 1 to step 6 for other materi- Repeat Step 1 to Step 6 for below materials The materials are ex-
als TG11_PH_CO30U tended
TG11_PH_CO30
TG11_PH_CW12
TG11_PH_CW14
TG11_PH_GP200
TG11_PH_GP300
TG11_PH_PP
TG11_PH_WC

Appendix PUBLIC 16
2.6.5.2 Maintain Product Hierarchy Condition(Optional)
Purpose
This process helps you to maintain Product Hierarchy condition DPH1.It is only relevant If you use ANC procedure to have the new country version, you need to manually maintain the product hier-
archy condition for your organization
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Pricing Specialist.
2 Access the App Open Set Material Prices - Sales (VK12) The Manage Product Hierarchy Assignments(F4240) view
displays.
3 Pricing Condition Type On the Change Condition Records view, enter the following information:
PPR0 Condition Type: PPR0
Choose Menu Condition>Create
Choose Material with release Status, and choose Choose.
4 Input price of PPR0 On the Screen of Create Price Condition (PPR0): Fast Entry, input below entries and Condition record for PPR0 is maintained
choose Save.
Sales Org:1710
Distribution Channel:10
Amount: input pricing
Material: Materials expended in last chapter
Choose Save.
Choose Back.
5 Pricing Condition Type On the Screen of Create Condition Records, enter the following information:
DPH1 Condition Type: DPH1
Choose Enter.
6 Input entries for DPH1 On the Screen of Create Product Hierarchy Condition(DPH1): Fast Entry, make entries be- Condition record for DPH1 is saved.
low:

Appendix PUBLIC 17
# ment
● Sales Oraganization: 1710

● Distribution channel:10
● Prod. Hier. Node:ADJUST_JOINT_PLIERS
Amount :10-
Unit: %
Calculat. Type: A
● Prod. Hier. Node: COMB_WRENCHES
Amount :8-
Unit: %
Calculat. Type:A
● Prod. Hier. Node: CUTTING_PLIERS
Amount: 6-
Unit: %
Calculat. Type: A
● Prod. Hier. Node: WRENCHES
Amount :5-
Unit: %
Calculat. Type: A
Choose Save
2.6.5.3 Maintain Product Hierarchy to Distribution Chain (Optional)
Purpose
This process helps you to maintain Product Hierarchy to Distribution Chain if you are using Product Hierarchy relevant materials.

Appendix PUBLIC 18
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Internal Sales Representative.
2 Access the App Open Manage Product Hierarchy Assignments (F4240). The Manage Product Hierarchy Assignments (F4240) view
displays.
3 Create New Object Choose Create. The Create Product Hierachy Assignment Screen displays.
4 Enter General Informa- On the Create Product Hierachy Assignment screen, in the General Information tab, make the fol-
tion lowing entries:
Purpose: 02 Sales
Valid From: <For example, Current Date>
Valid To: <For example, Current Date + 1 Year>
Product Hierachy: TOOLS
5 Save the Entry Choose Create.
2.6.5.4 Define Relevant Date for Product Hierarchy Determination (Optional)

Purpose
This process step shows you how to define relevant date for product hierarchy determination.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1. Log on Log onto the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration . The SAP Fiori Launch Pad displays.
2. Access the App Open Manage Your Solution (F1241). The Manage Your Solution screen displays.
3. Open Configure Your Solution Choose Configure Your Solution. The Configure Your Solution screen dis-

Appendix PUBLIC 19
Step # Comment
plays.
4. Filter Selection Criteria Choose the following entries in filter bar and choose Enter: All entries display in Configuration Items
● Application Area: Sales section.
● Sub Application Area: Sales Master Data Management
5. Find the Entry Find the entry with Configure master data for materials and product hierarchies in sales item name and choose The Configure Your Solution - Materials
arrow at the item end. screen displays.
6. Navigate to SSCUI In Configuration Steps section, choose Configure in the Actions column for Define Relevant Date for Product The Date Relevant for Hierarchy Determina-
Hierarchy Determination (SSCUI ID: 103303) step. tion screen displays.
7. Set Data Relevant for Hierarchy Choose New Entries, enter the following data, and choose Save. Data relevant for Hierarchy determination is
Determination Propose of Product Hierarchy: Sales set
Sales Org: 1010

Relevant Date for Det. Of Prod. Hier: for example, Pricing Date
SAP Central Business Configuration:

Step # Comment
1 Logon Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad is dis-
played.
2 Open Define Relevant Date for In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the The Date Relevant for Hierarchy De-
Product Hierarchy Determination tree view, search for the following activity: Define Relevant Date for Product Hierarchy Determination. termination screen displays.
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
Configuration Expert - Business Process Configuration.
3. Set Data Relevant for Hierarchy Choose New Entries, enter the following data, and choose Save. Data relevant for Hierarchy determi-
Determination Propose of Product Hierarchy: Sales nation is set
Sales Org: 1010

Relevant Date for Det. Of Prod. Hier: for example, Pricing Date

Appendix PUBLIC 20
2.6.6 Import Sales Orders (Optional)
Purpose
In this activity, You can import the sales order with template file.
Procedure
1 Log On Log on to the SAP Fiori launchpad as a Internal Sales Representative. The SAP Fiori launchpad displays.
2 Access the App Open Import Sales Orders (F4293). The Import Sales Orders (F4293) view displays.
3 Download Template Choose Download Template to download a template file.
4 Upload Template Input all the mandatory fields in the template file and choose Browse to upload the file.
5 Import Sales Order Choose Import to import the Sales orders.
6 Check Logs In the Pop-up Information window, choose View History to check the log. The Sales order is imported
2.6.7 Create Sales Order with Selling Recommender (Optional)
2.6.7.1 Assign Customer Procedure for Product Proposal to Business Partner
Purpose
In this activity, you assign customer procedure for product proposal to a business partner.

Appendix PUBLIC 21
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Master Data Specialist - Business Partner Data. The SAP Fiori launchpad displays.
2 Access the App Open Manage Customer Master Data (F0850A). The Manage Customer Master Data view displays.
3 Choose Business Partner Input following entry and choose Go.

Business Partner: for example, 17100003
4 Choose Sales Area Choose the Business Partner and click the line
On the new screen, choose Edit.
Choose the tab of Sales Areas, then choose
Company Code: for example 1710
Click the line.
5 Input PP Customer Proce- In the new screen, choose tab Sales Area Details, make the following entry, and choose Ap- The PP customer procedure has assigned to business part-
dure ply. ner.
PP customer Procedure : for example A
Choose Apply and Save.
2.6.7.2 Create Sales Orders for Selling Recommender
Purpose
As the product proposal is based on historical data- at least 1 order is required to derive a product proposal.
In this activity, you create sales order to get historical data for seting up selling recommender.

Appendix PUBLIC 22
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative. The SAP Fiori launch-
pad displays.
2 Access the App Open Manage Sales Orders (F1873). The Manage Sales Order
screen displays.
3 Navigate to Create On the Manage Sales Order screen, choose Create, and choose Create Sales Orders - VA01.
Order Screen
4 Enter Data On the Create Sales Order screen, make the following entries and choose Enter:
● Order Type: OR
● Sales Organization: 1710
● Distribution Channel: 10
● Division: 00
5 Enter Order De- On the Create Standard Order: Overview screen, make the following entries:
tails ● Sold-to Party: for example 17100003
● Ship-to Party: for example 17100003
● Customer References: Selling Recommender
● Material Number: <Material Number>
● Quantity: <Quantity>
6 Save the Order Choose Save. Make a note of the sales order number: __________.
If you have installed the Free Goods Processing scope item in your system, and used material TG11 and customer 17100001, the following warn-
ing may appear: Minimum quantity 1.000 PC of free goods has not been reached. To skip this warning, choose Enter.
2.6.7.3 Schedule Job for Intelligent Proposal
Purpose
In this activity, You create and process Jobs for intelligent proposal.

Appendix PUBLIC 23
Procedure
Test Step Test Step Instruction Expected Result Pass / Fail / Comment
# Name
1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative. The SAP Fiori launchpad dis-
plays.
2 Access the App Open Schedule Intelligent Product Proposal (F5139).
3 Create Job On the Application Jobs screen, choose Create.
4 Enter Data On theNew Job: Template for Backgorund Job of Intelligent Product Proposal Screen, make the following entries:
Job Template: Template for Background Job of Intelligent Product Proposal
Job Name: Template for Background Job of Intelligent Product Proposal
Choose Step 2, in the tab of Scheduling Options, choose Define Recurrence Pattern, On the pop-up screen, make following entries:
Start Immediately: X
Recurrence Pattern:Single Run
Choose OK
Choose Step 3, in the tab of Parameters, make the following entries:
Create Again: X
Choose Schedule.
2.6.8 Preliminary Steps for Sales Order Approval (Optional)
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Testing Date:

Appendix PUBLIC 24
Tester Name: Duration:
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
This process step shows you how to define and assign approval reasons.
Procedure
Test Step # Test Step Name Instruction Expected Result Com-

ments
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business The SAP Fiori launchpad displays.
Process Configuration.
2 Access the App Open Manage Your Solution (F1241). The Manage Your Solution screen displays.
3 Configure Your Solution Choose Configure Your Solution. The Configure Your Solution: Realize Phase screen
displays.
4 Filter Selection Criteria Choose the following entries in filter bar and choose Enter: All entries display in Configuration Items section.
● Application Area: Sales
● Sub Application Area: Basic Functions
5 Find the Entry Find the entry with Sales Document Approvals item name and choose arrow The Configure Your Solution - Sales Document Ap-
at the item end. provals screen displays.
Perform the following steps 6–7 to define ap-

proval reason.
6 Navigate to Define Rea- In Configuration Steps section, choose Configure in the Actions column for The Define Reasons for Approval Requests: Overview
sons Screen Define Reasons for Approval Requests step. screen displays.
7 Define Approval Reason Choose New Entries, enter the following data, and choose Save. Approval reason is defined.

Appendix PUBLIC 25
ments
● Approval Request Reason ID: for example, ZOR1

● Approval Request Reason: for example, Document needs ap-
proval
Perform the following steps 8–9 to assign ap-

proval reason to Sales order.
8 Navigate to Assign Rea- In Configuration Steps section, choose Configure in the Actions column for The Change View"Assign Reasons for Approval Re-
sons Screen Assign Reasons for Approval Requests step. quests"Overview screen displays.
9 Assign Approval Reason Choose New Entries, enter the following data, and choose Save.
to Sales Order ● Document Category: C
● Approval Request Reason: for example, ZOR1

ments
1 Log On Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
Perform the following steps 2–3 to

define approval reason.
2 Open Define Reasons In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To lo- The Define Reasons for Approval Requests:
for Approval Requests cate the activity in the tree view, search for the following activity: Define Reasons for Approval Overview screen displays.
Requests.
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 Configuration Expert - Business Process Configuration.
3 Define Approval Rea- Choose New Entries, enter the following data, and choose Save. Approval reason is defined.
son ● Approval Request Reason ID: for example, ZOR1
● Approval Request Reason: for example, Document needs approval
Perform the following steps 4–5 to

assign approval reason to Sales or-

Appendix PUBLIC 26
ments
der.
4 Open Define Reasons In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To lo- The Change View"Assign Reasons for Ap-
for Approval Requests cate the activity in the tree view, search for the following activity: Assign Reasons for Approval proval Requests"Overview screen displays.
Requests.
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 Configuration Expert - Business Process Configuration.
5 Assign Approval Rea- Choose New Entries, enter the following data, and choose Save.
son to Sales Order ● Document Category: C
● Approval Request Reason: for example, ZOR1
Test Administration
Purpose
The Business Add-In (BADI) SD_APM_SET_APPROVAL_REASON is called whenever a sales document is saved by a business user. It determines whether a sales document needs to be sent to an
approver and, if so, set an approval request reason on sales document header level.
This means that if you want to use the workflow for the approval of sales documents, implementing this BAdI is a prerequisite. In the Manage Sales Document Workflows (F2190) app, you define
additional preconditions and approval steps.
When the system sets an approval request reason for a sales document, the approval workflow is triggered automatically.

Appendix PUBLIC 27
Procedure
Test Test Step Name Instruction Expected Result Com-

Step # ments
1 Log On Log on to the SAP Fiori launchpad as a Administrator. The SAP Fiori launchpad dis-
plays.
2 Access the App Open Custom Logic (F6957). The Custom Logic screen dis-
plays.
3 Search or Create Custom In the Search Box input below information, and choose Go: The Custom Logic is ready to
Logic Set Approval Request Reasons for Sales Documents use.
Check if the status of the custom logic is published.
If not, please choose the customer logic and choose Publish.
Note If there is no relevant custom logic exists, please go to step 4 to 6 to create the custom logic
4 Input Extension Point Choose Create and make the following entries and choose Search: The New Implementation sec-
Extension points: SD_APM_SET_APPROVAL_REASON tion displays
5 Create Custom Logic Choose the extension points and choose Step 2, In the section of Implementation ID, make following entries: The Custom Logic is created
Implementation Description: Set Approval Request Reasons for Sales Documents
Implementation ID: for example YY1_SETAPPROVALREQUESTREASON
Choose Review.
Choose Create.
6 Publish the Custom Back to Custom Logic Screen, choose the custom logic you created in the last step, and choose Publish. The Custom logic is published.
Logic
7 Add/change Coding You can change the code of the custom logic if needed. The code for custom logic is
(Optional) Choose the custom logic and click the line. changed
Choose Open Code Editor in the header of the screen.

Choose Edit to change/add the code
for example:
If salesdocument-sddocumentcategory = 'C' and salesdocument-sddocumentreason = '005'.
salesdocapprovalreason = 'ZOR1'. endif.
Note Please note that it is possible to have sales document approvals also for other categories of sales documents.
The coding mentioned above can be seen as independent coding that can be added to the BAdI implementation without removing possi-
ble other coding
You can choose Show Sample Code to copy the suggested sample code if needed.

Appendix PUBLIC 28
Step # ments
Choose Publish to save the code you created or added.
Test Administration
Purpose
This process step shows you how to maintain the teams and responsibilities for sales order workflow.
Procedure

Step # ments
1 Log On Log on to the SAP Fiori launchpad as a Business Process Specialist. The SAP Fiori launchpad displays.
2 Access the App Open Manage Teams and Responsibilities (F2412).
3 Create A New Team Choose Create.
4 Enter General Informa- Make the following entries and choose Enter: The Draft Logic section displays
tion ● Name: Sales Order Workflow

Appendix PUBLIC 29
Step # ments
● Description: Sales Order Workflow

● Status: Enabled
● Type: SALES
5 Add Team Members On Team Members tab, choose Create. The Select: Business Partner screen displays.
From the Items section, select a Business Partnercheck box and choose OK. Team member sales manager is added.
Last Name: Sales Manager
6 Add Function to Team In Function field, choose Select. On the Select: Functions screen, select the fol-
Members lowing functions, and choose OK.
● CMR1LVLA: Sales Document Approver -Level 1
● CMR2LVLA : Sales Document Approver -Level 2
7 Save and Publish Choose Save Draft. User created a new team and appropriate function(s) have been assigned to the business
user(s) to be configured as approver(s).
Test Administration
Purpose
This process step shows you how to set up workflow.

In below example, if total amount of the sales order is more than 1000 USD, “Sales Document Approver - Level 2” can approve. If total amount of the sales order is less than 1000 USD, “Sales Doc-
ument Approver - Level 1” can approve.

Appendix PUBLIC 30
Procedure
Test Step Test Step Name Instruction Expected Result Comments
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration. The SAP Fiori launchpad displays.
2 Access the App Open Manage Sales Document Workflows (F3014). The Manage Workflows screen displays.
3 Create the First Workflow Choose Workflow for Sales Orders next to Workflow. The New Workflow screen displays.
Choose Add.
Note If the workflow has already be defined, please skip step 4 to 10.
4 Maintain General Data Make the following entries.

In the Header tab:
Name: <Second Approver- Net Value over 1000>
5 Set Preconditions Make the following entries and choose Save: Preconditions are set.
Preconditions:
Net Amount is greater than
Currency: USD
Amount: 1000
Choose Save.
6 Add Steps From the Step Sequence section, choose Add. The New Step screen displays.
Select the following entries from dropdown lists: The first workflow is created.
Under the Header tab:
Type: Release of Sales order
Under the Recipients tab:
Assignment By: Role
Role: Sales Document Approver - Level 2
Under the Exception Handling tab:
Name: Rework Sales order
Required Action: Rework of Sales order
Action Result: Restart Workflow
Choose Add to append this step to the workflow and choose Save.
7 Create the Second Workflow Choose Back to the Manage Workflows screen. The New Workflow screen displays.

Appendix PUBLIC 31
Choose Add.
8 Maintain General Data Make the following entries.

Name: <First Approval- No Conditions
9 Add Steps From the Step Sequence section, choose Add. The New Step screen displays.
Make the following entries: The second workflow is created.
Type: Release of Sales order
Under the Recipients tab:
Assignment By: Role
Role: Sales Document Approver - Level 1
Under the Exception Handling tab:
Name: Rework Sales order
Required Action: Rework of Sales order
10 Activate Workflows Choose Back to the Manage Workflow screen. Workflows are activated.
Choose Define Order. Adjust the order as below:
Second Approver- Net Value over 1000: Order 1
First Approver-No Conditions: Order 2
Choose Activate to active the workflows.
2.6.9 Preliminary Steps for Preliminary Billing Approval (Optional)
Test Administration

Appendix PUBLIC 32
Purpose
This process step shows you how to define and assign approval reasons.
Procedure

ments
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Busi- The SAP Fiori launchpad displays.
ness Process Configuration.
2 Access the App Open Manage Your Solution (F1241). The Manage Your Solution screen displays.
3 Configure Your Solution Choose Configure Your Solution. The Configure Your Solution: Realize Phase screen
displays.
4 Filter Selection Criteria Choose the following entries in filter bar and choose Enter: All entries display in Configuration Items section.
● Application Area: Sales
● Sub Application Area: Basic Functions
5 Find the Entry Find the entry with Document Approvals item name and choose arrow The Configure Your Solution - Document Ap-
at the item end. provals screen displays.
Perform the following steps 6–7 to define approval

reason.
6 Navigate to Define Reasons In Configuration Steps section, choose Configure in the Actions col- The Define Reasons for Approval Requests: Over-
Screen umn for Define Reasons for Approval Requests step. view screen displays.

Appendix PUBLIC 33
ments
7 Define Approval Reason Choose New Entries, enter the following data, and choose Save. Approval reason is defined.
● Approval Request Reason ID: for example, ZPBD
● Approval Request Reason: for example, Preliminary
Billing Document needs approval
Perform the following steps 8–9 to assign approval

reason to Preliminary Billing Document.
8 Navigate to Assign Reasons In Configuration Steps section, choose Configure in the Actions col- The Change View"Assign Reasons for Approval
Screen umn for Assign Reasons for Approval Requests step. Requests"Overview screen displays.
9 Assign Approval Reason to Choose New Entries, enter the following data, and choose Save.
Preliminary Billing ● Document Category: PBD Preliminary Billing Docu-
ment
● Approval Request Reason: for example, ZPBD

ments
1 Log On Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
Perform the following steps 2–3 to define

approval reason.
2 Open Define Reasons In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To The Define Reasons for Approval Re-
for Approval Requests locate the activity in the tree view, search for the following activity: Define Reasons for Ap- quests: Overview screen displays.
proval Requests.
Choose Open Documentation for the found line item to see more details about this configura-
tion activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration.
3 Define Approval Rea- Choose New Entries, enter the following data, and choose Save. Approval reason is defined.
son ● Approval Request Reason ID: for example, ZPBD
● Approval Request Reason: for example, Preliminary Billing Document
needs approval

Appendix PUBLIC 34
ments
Perform the following steps 4–5 to assign

approval reason to Preliminary Billing
Document.
4 Open Assign Reasons In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To The Change View"Assign Reasons for Ap-
for Approval Requests locate the activity in the tree view, search for the following activity: Assign Reasons for Ap- proval Requests"Overview screen displays.
proval Requests.
Choose Open Documentation for the found line item to see more details about this configura-
tion activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration.
5 Assign Approval Rea- Choose New Entries, enter the following data, and choose Save.
son to Preliminary ● Document Category: PBD Preliminary Billing Document
Billing
● Approval Request Reason: for example, ZPBD
Test Administration
Purpose
The Business Add-In (BADI) SD_APM_SET_APPROVAL_REASON is called whenever a sales document is saved by a business user. It determines whether a sales document needs to be sent to an
approver and, if so, set an approval request reason on sales document header level.
This means that if you want to use the workflow for the approval of sales documents, implementing this BAdI is a prerequisite. In the Manage Preliminary Billing Document Workflows (F4274)
app, you define additional preconditions and approval steps.

Appendix PUBLIC 35
When the system sets an approval request reason for a sales document, the approval workflow is triggered automatically.
Procedure

# ments
1 Log On Log on to the SAP Fiori launchpad as a Administrator. The SAP Fiori launchpad dis-
plays.
2 Access the App Open Custom Logic (F6957). The Custom Logic screen dis-
plays.
3 Search or Create Custom In the Search Box input below information, and choose Go: The Custom Logic is ready to
Logic Set Approval Request Reasons for Preliminary Billing Documents use.
Check if the status of the custom logic is published.
If not, please choose the customer logic and choose Publish.
Note If there is no relevant custom logic exists, please go to step 4 to 6 to create the custom logic
4 Input Extension Point Choose Create and make the following entries and choose Search: The New Implementation section
Extension points: SD_BIL_APM_SET_APPROVAL_REASON displays
5 Create Custom Logic Choose the extension points and choose Step 2, In the section of Implementation ID, make following entries: The Custom Logic is created
Implementation Description: Set Approval Request Reasons for Preliminary Billing Documents
Implementation ID: for example YY1_ PBD_APPROVAL_REASON
Choose Review.
Choose Create.
6 Publish the Custom Logic Back to Custom Logic Screen, choose the custom logic you created in the last step, and choose Publish. The Custom logic is published.
7 Add/change Coding (Op- You can change the code of the custom logic if needed. The code for custom logic is
tional) Choose the custom logic and click the line. changed
Choose Open Code Editor in the header of the screen.

Choose Edit to change/add the code
for example:
IF billingprocdocument-totalnetamount > 1000.salesdocapprovalreason = billingprocdocap-
provalreason = 'ZPBD'. ENDIF.
Note Please note that it is possible to have sales document approvals also for other categories of sales documents.
The coding mentioned above can be seen as independent coding that can be added to the BAdI implementation without removing

Appendix PUBLIC 36
# ments
possible other coding

You can choose Show Sample Code to copy the suggested sample code if needed.
Choose Publish to save the code you created or added.
Test Administration
Purpose
This process step shows you how to maintain the teams and responsibilities for preliminary billing document workflow.
Procedure

Step # ments
1 Log On Log on to the SAP Fiori launchpad as a Business Process Specialist. The SAP Fiori launchpad displays.
2 Access the App Open Manage Teams and Responsibilities (F2412).

Appendix PUBLIC 37
Step # ments
3 Create A New Team Choose Create.
4 Enter General Informa- Make the following entries and choose Enter:
tion ● Name: for example, Preliminary Billing Document Approval Workflow
● Description: Preliminary Billing Document Approval Workflow
● Status: Enabled
● Type: SBILLING
5 Set Value at Responsi- You can put criteria as per your approval conditions, for example, BillingDocu-mentType = F2
bility Definitions sec-
tion
6 Add Team Members On Team Members tab, choose Create. The Select: Business Partner screen displays.
From the Items section, select a Business Partnercheck box and choose OK. Team member is added.
For example, Last Name: Your Manager’s Last Name
Note Please contact your system Administrator if you are not sure if a business part-ner’s role is enough for
preliminary billing document approval. The business role should contain the catalog SAP_SD_BC_BIL_MY-
INBOX_PC.
7 Add Function to Team In Function field, choose Select. On the Select: Functions screen, select the following functions, and choose OK.
Members ● SBILAPRL1: Billing Process Document Approver - Level 1
● SBILAPRL2 : Billing Process Document Approver - Level 2
8 Save the new Team Choose Save at the bottom of the screen. User created a new team and appropriate function(s) have
been assigned to the business user(s) to be configured as ap-
prover(s).
Test Administration

Appendix PUBLIC 38
Purpose
This process step shows you how to set up workflow.

In below example, if total amount of the preliminary billing document is less than 500 EUR, no approval is required. If total amount of the preliminary billing document is more than 500 EUR and
less than 1000 EUR, “Billing Process Document Approver - Level 1” can approve it. If total amount of the preliminary billing document is more than 1000 EUR, it needs “Billing Process Document
Approver - Level 1” to approve it first, then needs “Billing Process Document Approver - Level 2” approve it.
Procedure

Step ments
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration. The SAP Fiori launchpad displays.
2 Access the App Open Manage Preliminary Billing Document Workflows (F4274). The Manage Workflows screen displays.
3 Create a Workflow Choose Add. The New Workflow screen displays.
Note If the workflow has already be defined, you can check if existing one(s) meet your approval conditions
before creating a new one.
4 Maintain Header and Step Properties Make the following entries.

Sector Workflow Name: <It’s mandatory to have a workflow name>
Filling in Description, Valid from and Valid to fields are optional.
5 Set Preconditions in “Start Condi- Make the following entries and choose Save: Preconditions are set.
tions” sector Preconditions:
Net Amount is greater than
Currency: EUR
Amount: 500
Choose Save.
6.1 Add Steps From the Steps section, choose Add. The New Step screen displays.

Appendix PUBLIC 39
Step ments
Step 1 Select the following entries from dropdown lists: The first approval level in this workflow is
In the Header tab: created.
Step Name: Step 1

Step Type: Release of Preliminary Billing Document
In the Recipients tab:
Assignment By: Role
Role: Billing Process Document Approver - Level 1
In the Step Conditions tab:
Set conditions to this step:
Select Net Amount is greater than
Currency: EUR
Net Value: 500
In the Deadlines tab:
You can set approval deadlines if required by choosing Add.
In the Exception Handling tab:
Name: Rework Preliminary Billing Document
Required Action: Rework of Preliminary Billing Document
Choose Add to append this step to the workflow.
6.2 Add Steps From the Steps section, choose Add. The New Stepscreen displays.
Step2 Select the following entries from dropdown lists: The second approval level in this workflow
In the Header tab: is created.
Step Name: Step 2 And the whole workflow is saved.
Step Type: Release of Preliminary Billing Document

In the Recipients tab:
Assignment By: Role
Role: Billing Process Document Approver - Level 2
In the Step Conditions tab:
Set conditions to this step:
Select Net Amount is greater than
Currency: EUR
Net Value: 1000
In the Deadlines tab:
You can set approval deadlines if required by choosing Add.

Appendix PUBLIC 40
Step ments
In the Exception Handling tab:

Name: Rework Preliminary Billing Document
Required Action: Rework of Preliminary Billing Document
7 Activate Workflows Choose Back to the Manage Workflow screen. Workflows are activated.
Click the Radio button and choose Activate to active the workflows.
2.6.10 Derivation Set-up for Cost Center
Test Administration
Purpose
For the billing part in this scope item as cost center has been derived via the substitution tool.

Appendix PUBLIC 41
Procedure
# ment
1 Log On Log on to the SAP Fiori Launchpad as an Configuration Expert - Business Process Configuration. The SAP Fiori Launchpad dis-
plays.
2 Access the SAP Fiori App Open Manage Substitution/Validation Rules - Group Journal Entries (F4406). A list of all existing rules dis-
plays.
3 Create Rule Enter Coding Block as Business Context, Coding Block as Event and Substitution Rule as New Substitution screen dis-
Rule Type. plays.
4 Fill out screen fields and save rule Rule Name: CCTRSD Rule is save in status New.
Rule Description: Cost Center for SD
As precondition:
ReferenceDocumentType (Field) Equal (Operator) to VBRK(Value)
CostCenter (Field) Is empty (Operator)
As Substitution:
CostCenter (Target Field) 17101101(Source)
5 Activate the rule by pressing the Activate Rule is activated.

button
6 Create Rule another Rule Enter Coding Block as Business Context, Coding Block as Event and Substitution Rule as New Substitution screen dis-
Rule Type. plays.
7 Fill out screen fields and save rule Rule Name: CCTRGI Rule is save in status New.
Rule Description: Cost Center for GR
As precondition:
GLAccount (Field) Equal (Operator) to 0051600000 (Value)
ReferenceDocumentType (Field) Equal (Operator) to MKPF (Value)
As Substitution:

button
9 Create Rule another Rule Enter Coding Block as Business Context, Coding Block as Event and Substitution Rule as New Substitution screen dis-

Appendix PUBLIC 42
# ment
Rule Type. plays.
10 Fill out screen fields and save rule Rule Name: CCTRG2 Rule is save in status New.
Rule Description: Cost Center for GI
As precondition:
GLAccount (Field) Equal (Operator) to 0054083000 (Value)
As Substitution:

button

Appendix PUBLIC 43
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 (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 Transaction/App Name Expected Results
Create Sales Order [page ] 46 Internal Sales Representative Manage Sales Orders (F1873) The Manage Sales Orders screen displays.
Create Attachment for Sales Order (Optional) [page ] 50 Internal Sales Representative Manage Sales Orders (F1873)
Process Sales Order Approval (Optional) [page ] 51
Withdraw from Approval [page ] 51 Internal Sales Representative Manage Sales Orders (F1873)
Approve/Reject/Rework Sales Order [page ] 53 Sales Manager My Inbox- All Items
Rework Sales Order [page ] 54
Check the Notifications [page ] 54 Internal Sales Representative My Inbox- All Items
Change Sales Order [page ] 55 Internal Sales Representative Manage Sales Orders (F1873)
Create Delivery [page ] 56 Shipping Specialist Create Outbound Deliveries - From Sales Orders (F0869A)
Create Attachment for Delivery (Optional) [page ] 58 Shipping Specialist Display Outbound Delivery (VL03N)
Execute Picking [page ] 59 Shipping Specialist Manage Outbound Deliveries - VL06O (VL06O_CLOUD)
Check Batches (Optional) [page ] 61 Shipping Specialist Change Outbound Delivery (VL02N) Batch numbers are checked
Maintain Serial Numbers (Optional) [page ] 62 Shipping Specialist Change Outbound Delivery (VL02N)
Split Outbound Delivery (Optional) [page ] 63 Shipping Specialist Split Outbound Delivery (VLSP)
Add Freight Costs (Optional) [page ] 64 Shipping Specialist Change Outbound Delivery (VL02N)

Appendix PUBLIC 44
Process Step Business Role Transaction/App Name Expected Results
Post Goods Issue [page ] 65 Shipping Specialist Manage Outbound Deliveries - VL06O (VL06O_CLOUD) The goods issue is posted.
Proof of Delivery (Optional) [page ] 67 Shipping Specialist POD - Change Outbound Delivery
Create Preliminary Billing Document (Optional) [page ] 68 Billing Clerk Create Preliminary Billing Documents (F2876)
Finalize the Preliminary Billing Document [page ] 70 Billing Clerk Manage Preliminary Billing Documents (F2875)
Rework from Approval [page ] 71 Billing Clerk Manage Preliminary Billing Documents (F2875)
Approve/Reject/Rework Preliminary Billing Document [page ] 73 Billing approval My Inbox - All Items (F2097)
Rework Preliminary Billing Document [page ] 74
Check the Notifications [page ] 74 Billing Clerk My Inbox - All Items (F2097)
Change Preliminary Billing Document [page ] 75 Billing Clerk Manage Preliminary Billing Documents (F2875)
Create Partial Billing Document (Optional) [page ] 76 Billing Clerk Create Billing Documents - VF01 (VF01)
Create Billing Document [page ] 77 Billing Clerk Create Billing Documents (F0798) The Create Billing Document screen displays.
Create Attachment for Billing (Optional) [page ] 80 Billing Clerk Display Billing Documents (VF03) The Display Billing Document screen displays.

Appendix PUBLIC 45
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, fact sheets for business objects. From the data found, you can go directly to the respective apps and fact sheets to display, edit the data or find related objects.
How to access and check a fact sheet:
1. Log on to the SAP Fiori launchpad as a respective user, for example, Internal Sales Representative.
2. Access the Enterprise Search Bar by choosing the magnifying glass icon in the upper right corner.
3. The Enterprise Search bar displays two filter fields next to the search icon: all dropdown menu and a search field. Enter your Search Criteria and choose the business object type, for example, se-
lect Sales orders from the dropdown menu, and enter a sales order number in the search field and choose Search, the sales order lists.
4. Choose the sales order number link. The system navigates to the fact sheet screen and sales order related information is integrated and summarized in one Fiori page. You can get detailed data by
choosing the corresponding links.
There are fact sheets available for the following objects (visible depending on the assigned role):
● Sales order
● Quotation
● Billing document
● Credit Memo
● Debit Memo
● Customer 360 Fact sheet
4.1 Create Sales Order
Test Administration

Appendix PUBLIC 46
Purpose
This process step shows you how to create a sales order.
Procedure
Test Test Step Instruction Expected Result Pass /

Step Name Fail /
# Com-
ment
1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Represen- The SAP Fiori launchpad displays.
tative.
2 Access the Open Manage Sales Orders (F1873). The Manage Sales Order screen displays.
App
3 Navigate to On the Manage Sales Order screen, and choose Create > Create
Create Order Sales Orders - VA01 .
Screen
4 Enter Data On the Create Sales Order screen, make the following entries and
choose Enter:
● Order Type: OR
● Sales Organization: 1710
● Distribution Channel: 10
● Division: 00
5 Enter Order If you would like to use listing and exclusion, continue with Enter
Details listed/ excluded Material Numbers step.
If you would like to use customer material record information,
continue with Enter Customer Material Number step.
On the Create Standard Order: Overview screen, make the follow-
ing entries:
● Sold-to Party: 17100003
● Ship-to Party: 17100003
● Customer References: <PO number>
Note If you have done the Prerequisite steps for Create

Sales orders with selling recommender, you will get items
proposed in the sales order based on your historical data.

Appendix PUBLIC 47
Step Name Fail /
# Com-
ment
You can choose Copy Prod. Proposal Qty to fulfill the

quantities, or maintain them manually, for the items you
don’t need, keep the quantity blank.
● Material Number: <Material Number>

● Quantity: <Quantity>
If you would like to use Sales order approval workflow, please
maintain:
Order Reason: 005
If you would like to use item proposal, continue with the next step.
6 Copy Item On the Create Standard Order: Overview screen, choose Propose Material and quantity recorded in item proposal are copied to sales order item.
Proposal to Items.
Sales Order In the Propose Items dialog box, input item proposal created in
(Optional) preliminary step in Sales Document.
Then choose Default with Quantity.
7 Check Prod- If you used Product Hierarchy relevant Material, On the Create Product Hierarchy information and relevant discount condi-tion type appears.
uct Hierar- Standard Order: Overview screen, choose the line item for Product
chy informa- Hierarchy Material, and choose Display Item Details Botton.
tion (Op- On the Create Standard Order: Item Data Screen, Navigate to
tional) Sales B tab, check the Product Hierarchy information under Prod-
uct Hierarchy (Purpose: Sales)
Navigate to Conditions tab, check the Product Hierarchy condition
DPH1.
Choose Back to back to header level.
8 Enter Data On the Create Standard Order: Overview screen, make the follow- ● Material TG11 is listed, and can be entered without error message.
(Optional) ing entries: ● Material TG12 is excluded. Message Material TG12 has been excluded appears.
Sold-to Party: 17100008
● Material TG20 is not listed. Message Material TG20 is not listed and therefore not al-
Ship-to Party: 17100008 lowed is processed.
Customer References: <Customer References>. Enter a You can use extra controls into product (material) listing and exclusion and influence product salability according to
customer purchase order number as reference. your business needs. please check link :
Enter the following Material Numbers: TG11, TG12 and TG20 https://help.sap.com/viewer/DRAFT/a376cd9ea00d476b96f18dea1247e6a5/2005.500/en-US/
Quantity: <Quantity> For example, 1 PC. 7df6956efb9245c898a36c05f4b81efe.html
9 Remove Not If you have selected the customer for listing/ exclusion, remove Sales Order can be saved only if materials TG12 and TG20 have been removed.
Listed Mate- Materials TG12 and TG20 if a dialog box appears.

Appendix PUBLIC 48
Step Name Fail /
# Com-
ment
rials (Op-
tional)
10 Enter Cus- On the Create Standard Order: Overview screen, make the follow- ● Material TG11 is automatically determined from customer material info record, and copied into the sales order. If
tomer Mate- ing entries: the sales unit is maintained in the customer's material info record, it will be automatically determined and displayed
rial Number ● Sold-to Party: 17100009 in the Sales Unit field.
(Optional) ● You can open Manage Customer Material to edit, or to display the customer material information.
● Ship-to Party: 17100009
● Customer References: <Customer References>. Enter
a customer purchase order number as reference.
● Customer Material Number: <Description from Cus-
tomer Material Info. Record>, such as
CUS_US_TG11.
● Quantity: <Quantity>. For example, 1 PC.
11 Save Docu- Choose Save. Make a note of the sales order number: The order is saved and the order confirmation is printed out.
ment __________.
Note If you have installed the Free Goods Processing scope

item in your system, and used material TG11 and customer
17100001, the following warning may appear: Minimum
quantity 1.000 PC of free goods has not been reached. To skip
this warning, choose Enter.
If you are using TG12 in testing, the following warning may
appear: Reorder point for item 000010 has
been exceeded: 10 PC. To skip this warning, choose
Enter.
Printing form- Output Management
# ment

Appendix PUBLIC 49
# ment
2 Access the App Open Manage Sales Orders (F1873). The Manage Sales Order screen displays.
3 Search for Sales Order Enter search terms in filter bar and choose Go Sales order is displayed in result list.
For example, enter sales order number in Sales Order field.
4 Navigate to Sales Order Click sales order number, and choose Display Sales Orders. The Display Sales Orders xxx: Overview screen
Screen displays.
Note If there is not a Display Sales Orders, then click More Links. Select Display Sales Orders, and
choose OK.
5 Check Output Condition On the Display Standard Order xxx: Overview screen, choose Header Output Preview . The document displays.
Select the line with Output type ORDER_CONFIRMATION and choose Display Document.
Note It can also be navigated 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, click your sales order number, and choose sales order number.
4.2 Create Attachment for Sales Order (Optional)
Test Administration
Purpose
This process step shows you how to create attachment for a sales order.

Appendix PUBLIC 50
Procedure

# ments
2 Access the App Open Manage Sales Orders (F1873). The Manage Sales Orders screen displays.
3 Navigate to Change Sales Order On the Manage Sales Orders screen, enter the respective order number created in previous step and
Screen choose Go.
Click the sales order number and choose Change Sales Order - VA02.
4 Create Attachment for Sales Order Choose Services for Object on the top right corner of screen, choose Create Attachment. The File Upload screen displays.
5 Import File Choose OK in the File Upload dialog box. The attachment was successfully created.
In the Open view, choose local path and file, and choose Open.
6 Check Attachment Choose Services for Object on top right corner of screen, choose Attachment List. Attachment brings up on the Service: Attachment list
screen.
4.3 Process Sales Order Approval (Optional)
Note Only relevant if below conditions are fulfilled:

1. Approval reason(s) is defined and assigned, details refer to the Define and Assign Approval Reasons chapter.
2. The Cloud BAdI that returns an approval reasons is implemented, details refer to the Implement Cloud BADI chapter.
3. Order reason is 005.
4.3.1 Withdraw from Approval
Test Administration

Appendix PUBLIC 51
Purpose
This process step shows you how to withdraw order approval.
Prerequisites
Sales manager has not yet made an approval decision.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail /
# Comment
3 Navigate to Display Sales Or- On the Manage Sales Orders screen, enter the respective order number created in previous step in the Sales Order The Display xxx Order xxx: Overview
der Screen and choose Go. screen displays.
Choose the sales order line that displays and choose the arrow.
4 Withdraw Approval Request In the menu bar at the top, choose More > Edit > Additional Functions > Withdraw Approval Request. The approval request is withdrawn.
Choose Continue to confirm the information shown as The approval request for sales document The Change xxx Order xxx: Overview
XXXXXXX was withdrawn. screen displays.
5 Change Sales Order On the Change xxx Order xxx: Overview screen, make some changes, for example: Approval status is changed to In Ap-
Valid to: <Enter a Date> proval.

Appendix PUBLIC 52
4.3.2 Approve/Reject/Rework Sales Order
Test Administration
Purpose
This process step shows you how to make approval decision: release, reject or request rework.
Prerequisites
Approval status of the order is In Approval.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Sales Manager. The SAP Fiori launchpad displays.
2 Receive Notification Open My Inbox - All Items (F2097). The Inbox screen displays.
Note You can also choose Notifications icon on the top-right corner to navigate to My In-
box screen.
3 Refresh Choose Refresh if necessary. Inbox is refreshed.
4 Approve/Reject/Rework Or- You receive the notification of the order. Choose one from the options on the bottom bar. The Submit Decision dialog box displays.
der

Appendix PUBLIC 53
# ment
Option 1: Release
Option 2: Reject
Option 3: Request Rework
5 Sumbit Enter some comments and choose Submit. Based on above decisions, choose next steps accordingly:
• Release: the whole process ends, no subsequent step is
needed.
• Reject: the whole process ends, no subsequent step is
needed.
• Request Rework: go to Rework Sales order chapter.
4.3.3 Rework Sales Order
Note Only relevant if the workflow is set as Request rework by sales manager previously.
Test Administration
Purpose
This process step shows you how to check the notifications.

Appendix PUBLIC 54
Prerequisite
Approval status of the sales order is To be reworked.
Procedure
# ment
2 Receive Notifica- Open My Inbox - All Items (F2097). The Inbox screen displays.
tion
Note You can also choose Notifications icon on the top-right corner to navigate to
My Inbox screen.
4 Check Inbox Check the inbox items with relative sales order. Orders which needs to be reworked are displayed.
• If rework is not required, sales representative can set Rework not Required
in the inbox.
• If rework is required, go to Change Sales Order chapter.
4.3.3.2 Change Sales Order
Test Administration

Appendix PUBLIC 55
Purpose
This process step shows you how to change sales order.
Prerequisites
Approval status of the sales order is rework.
Procedure

Step # Comment
3 Navigate to Display Sales On the Manage Sales Orders screen, enter the respective order number created in The Display xxx Order xxx: Overview screen displays.
Order Screen previous step in the Sales Order and choose Go.
Choose the arrow of the sales order line that displays.
4 Navigate to Sales Order Choose Change. The Change xxx Order xxx: Overview screen displays.
Screen
5 Change Sales Order On the Change xxx Order xxx: Overview screen, make some changes and save, for Approval status is changed to In Approval if the order amoun is higher than
example: amount set in Implement Cloud BADI chapter.
Order Quantity: <Enter a New Quantity> If amount >500 USD, go to Process Sales Order Approval chapter.
4.4 Create Delivery
Test Administration

Appendix PUBLIC 56
Purpose
This process step shows you how to create delivery.
Procedure

# ments
1 Log On Log on to the SAP Fiori launchpad as a Shipping Specialist.
2 Access the App Open Create Outbound Deliveries - From Sales Orders (F0869A). The Create Outbound Deliveries (F0869A) screen displays.
3 Search Sales Or- Make the following entries and choose Go:
der ● Shipping Point: 1710
● Planned Creation Date: <Delivery selection date>
● Sales Document: Sales order number created pre-
viously
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. Delivery number displays on
Deliveries tab.
Note Depending on the scope item settings, the availability is checked at the delivery creation using the available inventory and replenishment lead time. Without sufficient stock, the created de-
livery has no confirmed quantities, and therefore does not start the warehouse management picking process. As soon as there is sufficient stock for delivery creation, the system creates a deliv-
ery with the starting of the picking process in warehouse management.
To avoid open deliveries, ensure there is sufficient inventory quantity at the time for delivery creation. Additionally, you have the following options to restrict the creation of deliveries with no con-
firmed quantities.
You may increase the replenishment lead time which is used during the availability check (has to be larger than the selection period used for delivery creation).

Appendix PUBLIC 57
You may change the customization settings for the incompleteness procedure for delivery creation, so that only complete deliveries may be saved.
You may 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, for example, 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.
Printing form
# ment
1 Log On Log on to the SAP Fiori launchpad as a Shipping Specialist. The SAP Fiori launchpad displays.
2 Access the App Open Change Outbound Delivery (VL02N)
3 Issue Delivery Out- On the Change Outbound Delivery (VL02N) screen, enter the Delivery Number, and choose Continue. The Outbound Delivery: Output screen dis-
put From the Outbound Delivery xxxxxxxx Change: Overview screen, choose Menu > Extras > Delivery Output > Output plays.
Control .
4 Print Preview On the Outbound Delivery: Output screen, select the line with the DELIVERY_PICK_LIST Output Type, and choose A preview of the print document is dis-
Display Document. played.
5 Print Delivery Pick From the preview of the document, choose Print. The delivery pick list is printed.
List
4.5 Create Attachment for Delivery (Optional)
Test Administration

Appendix PUBLIC 58
Purpose
This process step shows you how to create attachment for delivery.
Procedure

# ments
2 Access the App Open Change Outbound Delivery (VL02N). The Display Outbound Delivery: Initial screen dis-
plays.
3 Enter Outbound Delivery In the Outbound Delivery field, enter <the outbound delivery number created in previous The Display Outbound Delivery xxx: Overview
Number step> and choose Continue. screen displays.
4 Create Delivery Attachment Choose Services for Object on the top right corner of screen, choose (More-->) Services for Object, and then The File Upload screen displays.
choose Create Attachment.
5 Import File Choose OK in the File Upload dialog box. The attachment was successfully created.
In the Open view, choose local path and file, and choose Open.
6 Check Attachment Choose More--> Services for Object, then choose Attachment List. Attachment shows up on Service: Attachment List
screen.
4.6 Execute Picking
Test Administration

Appendix PUBLIC 59
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
# ment
1 Log On Log on to the SAP Fiori launchpad as a Shipping Specialist. The SAP Fiori launchpad
displays.
2 Access the App Open Manage Outbound Deliveries - VL06O (VL06O_CLOUD).
3 Choose Picking Choose For Picking.
4 Enter Shipping Point Make the following entries, and choose Execute:
● Shipping Point: 1710
Under the Picking Data tab, select
● Only Picking Without WM: X
5 Change Outbound De- From Day’s Workload for Picking, select your delivery number, and choose Change Outbound Deliveries.
liveries
6 Check Batch Split Choose the Picking tab, check if batch split exists in the Batch Split Indicator column.
7 Enter Picked Quantity ● If batch split exists, choose Batch Split Exists to expand sub item(s), enter <quantity equal to delivery Qty> in
Picked Qty field for sub item.
● If batch split doesn't exist, enter > in Picked Qty field for picking related item(s).
8 Choose Enter Choose Enter.
9 Save Choose Save. The delivery has been de-

cided.

Appendix PUBLIC 60
4.7 Check Batches (Optional)
Test Administration
Purpose
This process step shows you how to check the batch number assigned to the material.
Prerequisites
Execute this step if batch management is used, such as TG21 and TG22.
Procedure
Test Step # Test Step Name Instruction Expected Result Comments
2 Access the App Open Change Outbound Delivery (VL02N).
3 Enter Outbound Delivery Number In the Outbound Delivery field, enter <outbound delivery number>, and choose Enter.
4 Check Batch Number Assignment If Expand Batch Split exists, go to the Batch field, and check the batch number assignment. Batch numbers are assigned to the materials.
5 Save Document Choose Save.

Appendix PUBLIC 61
4.8 Maintain Serial Numbers (Optional)
Test Administration
Purpose
This process step shows you how to maintain serial number to the material.
Prerequisites
Run this step if Serial Number is used, such as TG20.
Procedure
3 Enter Outbound Delivery Number In the Outbound Delivery field, enter the outbound delivery number, and choose Enter.
4 Navigate to Serial Numbers On the Delivery XXXXXXXXX Change: Overview screen, choose Menu > Extras > Serial Numbers .
5 Maintain Serial Numbers On the Maintain Serial Numbers screen, choose Create serial number automatically and choose Continue.
6 Save Document Choose Save.

Appendix PUBLIC 62
4.9 Split Outbound Delivery (Optional)
Test Administration
Purpose
In this process step, you split up single or multiple items from an existing, completely picked Outbound Delivery and move them to a new delivery document before posting Goods Issue.
Procedure
# ment
2 Access the App Open Split Outbound Delivery (VLSP).
3 Enter Shipping Point On the Split Outbound Delivery screen, make the following entry:
● Shipping Point:1710
4 Enter Outbound De- To speed up selection, make the following entry on the same screen:
livery ● Outbound Delivery: <your Outbound Delivery Document Number>
5 Choose Split Profile In the Split Profile field, make the following entry, and select the following value from
the list:

Appendix PUBLIC 63
# ment
● Split Profile: 0003 (Delivery Split - LE Components)
6 Start Selection Choose Execute. A list of outbound delivery items for the selected shipping point and out-
bound delivery displays.
7 Select Items for ● Select the items that would become part of a new delivery or that would be split ● The selected items display with a new delivery document number.
Split from the current delivery. ● The items not selected for the split still appear with the former docu-
● Enter <Split Quantity> and choose Save Split. ment number.
4.10 Add Freight Costs (Optional)
Test Administration
Purpose
This process step shows you how to add the actual freight costs to the Outbound Delivery after knowing the exact weights and freight charges.
Procedure

Step # ments

Appendix PUBLIC 64
Step # ments
3 Enter Outbound Delivery On the Change Outbound Delivery screen, enter the outbound delivery number, and choose
Number Enter.
4 Open Conditions From the menu, choose Menu > Goto > Header > Conditions .
5 Enter Condition Type In the Condition Type column, input below entry (It’s allowed to enter each one or all of them):
FPA1 - Packaging fee
FIN1 - Insurance fee
6 Enter Freight Cost In the Amount column, enter freight cost (such as , FPA1 10, FIN1 10).
The system distributes the entered amount across the delivery items. The distribution is executed on the
basis of the net weight of each item.
7 Save Save your outbound delivery. Freight Costs are added to the Outbound Delivery and will be
later copied to the Invoice.
Note The system distributes the entered amount across the delivery items. The distribution is executed on the basis of the net weight of each item. See also SAP Note 1921287Pricing with Scale
Conditions in Delivery with Batch Split. When you use the POD functionality (proof of delivery), freight costs in the delivery are not adjusted according to the quantities, weight and volume re-
ported back in the POD. Freight costs are adjusted in the invoice based on POD.
4.11 Post Goods Issue
Test Administration

Appendix PUBLIC 65
Purpose
This process step shows you how to post goods issues for delivery.
Procedure
2 Access the App Open Manage Outbound Deliveries - VL06O (VL06O_CLOUD).
3 Open Outbound Delivery Monitor Choose For Goods Issue. Make the following entries and choose Execute.
● Shipping Point: 1710
4 Post Good Issue Select your outbound delivery note, and choose Post Goods Issues. A message confirms the goods issue has been posted.
Select today’s date from the dialog box, and choose Continue.
Financial Posting
Material Debited Accounts Credited Accounts Cost Element / CO Object
Trading Good (HAWA) 51600000 13600000 none

Consptn Trde Gds Inventory TradingGd
Note When the bundling functionality in context of IFRS15 is tested, the financial document in IFRS ledger (Ledger Group 2L) with the adjusted revenue amount displays.
To check the financial document, use the Warehouse Clerk role, and access the Display Material Document List (MB51) app.
Printing Form
# ment

Appendix PUBLIC 66
# ment
2 Access the App Open Display Outbound Delivery (VL03N). The Display Outbound Delivery (VL03N) screen dis-
plays.
3 Issue Delivery Out- In the Outbound Delivery field, enter <Outbound Delivery Number>, and choose Continue. The Delivery: Output screen displays.
put On the Delivery xxxxxxxx Display: Overview screen, choose Menu > Extras > Delivery Output > Output
Control .
4 Print Preview On the Delivery: Output screen, select the line with the Output Type Delivery Note , and choose Display A preview of the print document is displayed.
Document.
5 Print Delivery Note From the preview of the document, choose Print. The delivery note is printed.
4.12 Proof of Delivery (Optional)
Test Administration
Purpose
In this activity, you record the quantities as confirmed by the respective customer after physical arrival of goods delivered. Thus document the right quantities that should become subject to billing to
this customer.
This is only possible for Outbound Deliveries if the customer master data have been maintained in a way that this customer is "POD-relevant" (on sales area level).

Appendix PUBLIC 67
Procedure

Step # Comment
2 Access the App Open Change Outbound Delivery - Proof of Delivery (VLPOD).
3 Enter Outbound On the same screen, make the following entry, and choose Continue: The selected Outbound Delivery Document screen displays, and
Delivery Outbound Delivery: <your Outbound Delivery Document Number> Overview POD tab becomes active.
4 Quantity Differ- If there is a quantity difference between shipping and receiving, go to step 5 and 6.
ence
5 Enter POD Deliv- In the line with the item for which a differing quantity was reported by the customer, make the following
ery Reason (Op- entry or select the following value from the list:
tional) Reason: <DFG2(Underdelivery, reason unknown)>
6 Enter Deviation In the Quantity Difference field, go to Sales Unit (Qty Diffin Sales Un), enter <respective quantity The quantity displayed for the respective item in the POD quantity
(Optional) (differs from the expected Delivery Quantity as per the Outbound Deliv- field has been recalculated (Quantity Difference subtracted from
ery Item)>, and choose Enter. Delivery Quantity).
The value for POD Status field has changed to B (Differences Re-
ported).
7 Confirm Delivery Choose Confirm Proof of Delivery. The POD Date field has been filled with the current date.
Proof The value for the POD Status field has changed to C (Confirmed).
8 Save Choose Save. The Outbound Delivery document is saved with confirmation for
actually delivered quantities.
These will be used for the consecutive billing step.
4.13 Create Preliminary Billing Document (Optional)
Test Administration

Appendix PUBLIC 68
Purpose
In this activity, the billing clerk creates preliminary billing documents based on these billing due list items, adjusts view settings and filters to customize your experience.
Procedure

# ments
1 Log On Log on to the SAP Fiori launchpad as a Billing Clerk. The SAP Fiori launchpad displays.
2 Access the App Open Create Preliminary Billing Documents (F2876). The Create Preliminary Billing Documents screen
displays.
3 Search for Billing Due List Items To enable a filter, type in a value directly to trigger autosuggest and press Enter, or use the in- The Sales Document is displayed in the result.
put help to choose a value.
4 Define Preliminary Billing Settings Choose Preliminary Billing Settings at the bottom and make the following settings:
● Set billing date and enter before creating Preliminary billing document - OFF
● Create separate preliminary billing document for each item of billing due list - OFF
● Display preliminary billing document after creation - ON
5 Adjusting Settings Choose Settings above the worklist to open the View Settings view.
Each of the four tabs (Columns, Sort, Filter, Group) lets you perform a different function.
● The Columns tab allows you to add or remove columns from the worklist.
● You can search for the names of columns using the search field.
● You can choose Move Up or Move Down to change the order of the columns in the work-
list.
Choose Restore to restore the default.
6 Select An Item to Create Preliminary Select the document and choose Create The Manage Preliminary Billing Documents screen
Billing Document displays.

Appendix PUBLIC 69
# ments
7 In the Manage Preliminary Billing Docu- The preliminary billing document with ID Pxxxxxxxx has been created. The system generates a Preliminary Billing Docu-
ments App ment for billing.
8 Define Billing Settings Choose Billing Settings at the bottom and make the following settings:
● Automatically Post Billing Documents - OFF
● Display Billing Document after creation - ON
9 Select the Preliminary Billing Document to Select the Preliminary Billing Document you have created and choose Create Billing Document. The system generates an invoice for sales document
be Invoiced automatically.
Note If you finished the above steps and created both the preliminary billing document and billing document, then please skip the next step Create billing Document.
4.14 Process Preliminary Billing Approval (Optional)
Note Only relevant if below conditions are fulfilled:

1. Approval reason(s) is defined and assigned, details refer to the Define and Assign Approval Reasons chapter.
2. The Cloud BAdI that returns an approval reasons is implemented, details refer to the Implement Cloud BADI chapter.
3. Total amount of the order is not less than 500 USD.
4.14.1 Finalize the Preliminary Billing Document
Test Administration

Appendix PUBLIC 70
Purpose
This process step shows you how to send the preliminary billing document to approval process by finalizing the preliminary billing document.
Prerequisites
Automatically finalize preliminary billing documents after creation has not been turned on in Preliminary Billing Settings at Create Preliminary Billing App.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Billing Clerk. The SAP Fiori launchpad displays.
2 Access the App Open Manage Preliminary Billing Documents (F2875). The Manage Preliminary Billing Documents screen displays.
3 Navigate to Display Prelim- On the Manage Preliminary Billing Documents screen, enter the preliminary billing document number The Preliminary Billing Document displays.
inary Billing Document created in previous step in the Preliminary Billing Document and choose Go.
Screen
4 Finalize the Preliminary Highlight the Preliminary Billing Document by choosing the checkbox in front of the preliminary billing The preliminary billing document is finalized and goes into
Billing Document document number, choose Finalize. approval process if it meets approval criteria set in prelimi-
anry steps.
Note If Automatically finalize preliminary billing documents after creation is turned on in Prelimi-
nary Billing Settings at Create Preliminary Billing App, the document will set to Finalized status and
In Approval status automatically.
4.14.2 Rework from Approval
Test Administration

Appendix PUBLIC 71
Purpose
This process step shows you how to rework preliminary billing document from approval process.
Prerequisites
Preliminary Billing Document approver(s) have not made approval decision yet.
Procedure

Step # Comment
2 Access the App Open Manage Preliminary Billing Documents (F2875). The Manage Preliminary Billing Documents screen
displays.
3 Navigate to Display Sales On the Manage Preliminary Billing Documents screen, enter the Preliminary Billing Documents number cre- The Display Preliminary Billing Documents xxx:
Order Screen ated in previous step in the Preliminary Billing Documents and choose Go. Overview of items screen displays.
Choose the Preliminary Billing Documents line that displays and choose the arrow.
4 Rework Request In the menu bar at the top, choose Change and then choose Rework. The approval request is withdrawn.
The Change Preliminary Billing Document xxx:
Overview of items screen displays.
5 Change Preliminary On the Change Preliminary Billing Document xxx: Overview of items screen, make some changes and choose Approval status is changed to In Approval.
Billing Document Save.

Appendix PUBLIC 72
4.14.3 Approve/Reject/Rework Preliminary Billing Document
Test Administration
Purpose
This process step shows you how to make approval decision: release, reject or request rework.
Prerequisites
Approval status of the order is In Approval.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Billing approver you set in preliminary The SAP Fiori launchpad displays.
step.
2 Receive Notification Open My Inbox - All Items (F2097). The Inbox screen displays.
Note You can also choose Notifications icon on the top-right corner to navigate
to My Inbox screen.
4 Approve/Reject/Rework You receive the notification of the order. Choose one from the options on the bot- The Submit Decision dialog box displays.

Appendix PUBLIC 73
# ment
Order tom bar.

Option 1: Release
Option 2: Reject
Option 3: Request Rework
5 Sumbit Enter some comments and choose Submit. Based on above decisions, choose next steps accordingly:
• Release: this can be final status or document can send to approval again
by using rework
• Reject: the whole process ends, no subsequent step is needed.
• Request Rework: go to Rework Preliminary Billing Document chapter.
4.14.4 Rework Preliminary Billing Document

Only relevant if the workflow is set as Request rework previously.
Test Administration
Purpose
This process step shows you how to check the notifications.

Appendix PUBLIC 74
Prerequisite
Approval status of the preliminary billing document is to be reworked.
Procedure
# ment
2 Receive Notifica- Open My Inbox - All Items (F2097). The Inbox screen displays.
tion
Note You can also choose Notifications icon on the top-right corner to navigate to My Inbox
screen.
4 Check Inbox Check the inbox items with relative sales order. Preliminary billing documents which need to be reworked are dis-
played.
4.14.4.2 Change Preliminary Billing Document
Test Administration
Purpose
This process step shows you how to change preliminary billing document.

Appendix PUBLIC 75
Prerequisite
Approval status of the preliminary billing document is Rework.
Procedure

Step # Comment
2 Access the App Open Manage Preliminary Billing Documents (F2875). The Manage Preliminary Billing Documents screen displays.
3 Navigate to Display Pre-liminary On the Manage Preliminary Billing Documents screen, enter the respective prelimi- The Display Preliminary Billing Document xxx: Overview of items
Billing Document Screen nary billing document number created in previous step and choose Go. screen displays.
Click the arrow of the preliminary billing document line that displays.
4 Choose Change Choose Change. The Change Preliminary Billing Document xxx: Overview of items
screen displays.
5 Change Preliminary Billing Doc- Make the necessary changes to this preliminary billing document and save it. Approval status is changed to In Approval if the document amount is
ument higher than amount set in Imple-ment Cloud BADI chapter.
If amount >500 EUR, go to Approve/ Reject/ Rework Preliminary
Billing Document chapter.
4.15 Create Partial Billing Document (Optional)
Test Administration

Appendix PUBLIC 76
Purpose
In this activity, you create partial billing document. As described in 482506, partial billing does not support material with batch split.
Procedure
2 Access the App Open Create Billing Documents - VF01 (VF01). The Create Billing Document screen displays.
3 Input Delivery Number Make the following entry, and choose Selection List:
Document: <Delivery document>
4 Input Open Quantity Choose the item, change Open quantity to smaller quantity, then choose Copy.
5 Save Billing Document Choose Save. The system generates an invoice for billing.
4.16 Create Billing Document
Test Administration
Purpose
In this activity, you handle the billing.

Appendix PUBLIC 77
Create Billing Document
Table 3: Overview
Test Step Test Step Name Instruction Expected Result Pass / Fail /
# Comment
2 Access the App Open Create Billing Documents (F0798). The Create Billing Documents screen
displays.
3 Define Billing Set- Choose Billing Settings, you can make the following settings as below:
tings 1. Set billing date and type before billing: ON
2. Create separate billing document for each item of billing due list: OFF
3. Automatically post billing documents: ON
4. Display billing documents after creation: ON
5. Choose delivery items to be billed and select quantities: OFF
4 Search for billing In the search condition, use criteria if necessary. Sales document(s) display in the result.
due list
5 Select item(s) for Select row(s) of SD Document created previously and choose button Create Billing Documents. The Create Billing Document screen dis-
billing plays.
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 TMP
Date xxxxxx displays.
7 Save Billing Docu- On the Manage Billing Document screen, choose Save. The system generates an invoice for
ment The draft version billing document with TMP xxxxxx turns into a saved billing document with ID xxxxxxxx, make a note of billing.
the billing document number: __________.
Financial Postings
Table 4: Overview
Trading Good (HAWA) 17100003 41000000 none

Rcvbls Domestic US 3 Rev Domestic Prod
22001000

Appendix PUBLIC 78
Sales/Use Tax Accrue

22002000
22003000
22004000
21730000
(optional) Freight Clrg MM
Note When the bundling functionality in context of IFRS15 is tested you can see the financial document created in the IFRS ledger (Ledger Group 2L).
Manage Billing Documents
Test Step Name Instruction Expected Result Pass / Fail / Com-

ment
1 Access the App Open Manage Billing Documents (F0797). The Manage Billing Document screen displays.
2 Search Billing Document Enter the Billing document number recorded in previous step. Choose Enter. The billing document created in previous step displays
3 Display Billing document Select the billing document item, and choose Display. The billing document displays.
4 Check Output Condition Choose the last assignment block - Output Items. There is one entry in the item and the output type is
BILLING_DOCUMENT
5 Display Print Preview Choose Preview. Preview for PDF document displays.
6 Cancel Billing Document Select certain billing document and choose Cancel Billing Docs. Message Billing Document Canceled displays.
(Optional)
7 Update New Attachment (Op- In the Edit mode, add, delete and update the attachments. Save your changes by pressing Save button
tional) in the footer bar.
8 Update New Text (Optional) In the Edit mode, you can add, delete and update these texts. Save your changes by pressing Save
button in the footer bar.

Appendix PUBLIC 79
4.17 Create Attachment for Billing (Optional)
Test Administration
Purpose
This process step shows you how to create an attachment for a billing document.
Procedure

#
2 Access the App Open Manage Billing Documents (F0797). The Manage Billing Document screen dis-
plays.
3 Search Billing Make the following entry, and choose Enter:

Billing Document: <Billing Document Number Created Previously>
4 Choose Billing Number On the Manage Billing Documents screen, select your billing document created in the previous step, and choose Dis- The Billing Document screen displays.
play.
5 Edit On the Billing Documents screen, choose Edit.
6 Create Billing Attach- Scroll down and choose Upload in the ATTACHMENTS section. The Open File screen displays.
ment

Appendix PUBLIC 80
#
7 Import File In the Open window, select a local path or file and choose Open. The attachment is successfully created.
Choose Save.
8 Check Attachment In the ATTACHMENTS section, you can see the uploaded document. Choose the document you want to open.

Appendix PUBLIC 81
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:
Scope Item Business Condition
O59 - Accounts Receivable Posting a Customer Invoice in Accounting and so on.

Using the master data from this document, complete the following activities described in the test script:
• Accounts Receivable (Sections Posting a Customer Invoice in Accounting, Overdue Receivables, Display Customer Balances, Manage Customer Line Items)
5.2 Scheduling Job (alternative)
5.2.1 Job Scheduling for Delivery Creation (Alternative)
Test Administration

Appendix PUBLIC 82
Purpose
This process step shows you how to schedule a background job for creating outbound deliveries.
This app can be used as an alternative instead of the manual creation of outbound deliveries.
Procedure

Step # Comment
2 Access the App Open Schedule Delivery Creation (F2228). The Application Jobs screen displays. The app automatically shows the his-
tory of application jobs.
3 Create Delivery Creation Choose Create to define a new job. The New Job screen displays. The Job Template should be Schedule Deliv-
Schedule ery Creation for Sales Orders.
4 Job Parameters Define scheduling options and parameters for the batch job if necessary, then The system displays the message Go ahead and schedule the
choose Check. job.
5 Schedule Choose Schedule. A delivery creation job is scheduled. Screen goes back to Application Jobs.
6 Check Delivery Creation On the Application Jobs screen, after job item’s status turned to Finish, choose Sta- The job log details displays.
Job Log tus symbol in the Log column.
Note Choose the Magnifier, and the job list will refresh.
5.2.2 Job Scheduling for Goods Issue Deliveries (Alternative)
Test Administration

Appendix PUBLIC 83
Purpose
This process step shows you how to schedule a background job for goods issue posting with reference to outbound deliveries.
This app can be used as an alternative instead of the manual goods issue posting for outbound deliveries.
Procedure

Step # Comment
2 Access the App Open Schedule Goods Issue for Deliveries (F2259). The Application Jobs screen displays. The app automatically shows the his-
tory of application jobs.
3 Create Goods Issue Deliver- Choose New to define a new job. The New Job screen displays. The Job Template should be defaulted as
ies Schedule Schedule goods issue for Deliveries.
4 Job Parameters Define scheduling options and parameters for the batch job if necessary, then The system displays the message Go ahead and schedule the
choose Check. job.
5 Schedule Choose Schedule. A schedule goods issue for deliveries job is scheduled. The screen goes back
to Application Jobs.
6 Check Goods Issue Deliver- On the Application Jobs screen, after job item’s status turned to Finish, choose The job log details are displayed.
ies Job Log Status symbol in the Log column.

Appendix PUBLIC 84
5.2.3 Job Scheduling for Preliminary Billing Documents Creation (Alternative)
Test Administration
Purpose
This process step shows you how to schedule a background job for creating preliminary billing documents.
This app can be used as an alternative instead of the manual creation of preliminary billing documents.
Procedure
# ment
2 Access the App Open Schedule Creation of Preliminary Billing Documents The Application Jobs screen displays. The app automatically shows the history
(F4563). of application jobs.
3 Create Preliminary Billing Cre- Choose New to define a new job for preliminary billing creation. The New Job screen displays. Job Template defaultly should be Preliminary
ation Schedule Billing Document Creation.
4 Job Parameters Define scheduling options and parameters for the batch job if neces- The system displays the message You can go ahead and schedule
sary. the job.
Choose Check.
5 Schedule Choose Schedule. A preliminary billing creation job is scheduled. Screen goes back to Application
Jobs.

Appendix PUBLIC 85
# ment
6 Check Preliminary Billing Cre- On the Application Jobs screen, after job item’s status turned to Fin- The log details displays.
ation Job Log ish, choose Job Log.
Note Choose Go, and the job list will refresh.
5.2.4 Job Scheduling for Billing Creation (Alternative)
Test Administration
Purpose
This process step shows you how to schedule a background job for creation billing documents.
This app can be used as an alternative instead of the manual creation of billing documents.
Procedure
# ment
2 Access the App Open Schedule Billing Creation (F1519). The Application Jobs screen displays. The app automatically shows the history of

Appendix PUBLIC 86
# ment
application jobs.
3 Create Billing Creation Choose Create to define a new job for billing creation. The New Job screen displays. Job Template should default as Schedule Billing
Schedule Creation.
4 Job Parameters Define scheduling options and parameters for the batch job if necessary. The system displays the message Go ahead and schedule the job.
Choose Check.
5 Schedule Choose Schedule. A billing creation job is scheduled. Screen goes back to Application Jobs.
6 Check Billing Creation Job On the Application Jobs screen, after job item’s status turned to Finish, The log details display.
Log choose Job Log.
5.2.5 Job Scheduling for Billing Release (Alternative)
Test Administration
Purpose
This process step shows you how to schedule a background job for release billing documents to accounting.
This app can be used as an alternative instead of the manual release to accounting for billing documents.

Appendix PUBLIC 87
Procedure
# ment
2 Access the App Open Schedule Billing Release (F1518). The Application Jobs screen displays. The app automatically shows the history of
application jobs.
3 Create Billing Release Choose Create to define a new job for billing creation. The New Job screen displays. Job Template defaultly should be Schedule Billing
Schedule Release.
Choose Check.
5 Schedule Choose Schedule. A billing release job is scheduled. Return to Application Jobs.
6 Check Billing Release Job On the Application Jobs screen, after job item’s status turned to Finish, The log details displays.
Log choose Job Log.
Note Choose Magnifier, and the job list will refresh.
5.2.6 Job Scheduling for Billing Output (Alternative)
Test Administration

Appendix PUBLIC 88
Purpose
This process step shows you how to schedule a background job for when and how billing documents are sent to customer.
Procedure
# ment
2 Access the App Open Schedule Billing Output (F1510). The Application Jobs screen displays. The app automatically shows the history of
application jobs.
3 Create Billing Output Choose Create to define a new job for billing creation. The New Job screen displays. Job Template should default as Schedule Billing
Schedule Output.
Choose Check.
5 Schedule Choose Schedule. A billing release job is scheduled. Return to Application Jobs.
6 Check Billing Output Job On the Application Jobs screen, after job item’s status turned to Finish, The log details display.
Log choose Job Log.
Note Choose Magnifier, and the job list will refresh.

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

Sell from Stock (OD9_US) tion and notices.
Appendix PUBLIC 90

Od9 S4CLD2402 BPD en Us

Uploaded by

Copyright:

Available Formats

You might also like

Od9 S4CLD2402 BPD en Us

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

Od9 S4CLD2402 BPD en Us

Uploaded by

Copyright:

Available Formats

Test Script

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

Sell from Stock (OD9_US)

Sell from Stock (OD9_US)

Sell from Stock (OD9_US)

Sell from Stock (OD9_US)

2.1 System Access

Shipping Spe- SAP_BR_SHIPPING_SPE Shipping SAP_BR_SHIPPING_SPECIALIST

Sell from Stock (OD9_US)

Warehouse SAP_BR_WAREHOUSE_CL Inventory Processing SAP_BR_WAREHOUSE_CLERK

Billing Clerk SAP_BR_BILLING_CLER Billing SAP_BR_BILLING_CLERK

Credit Con- SAP_BR_CREDIT_CON- Credit Management SAP_BR_CREDIT_CONTROLLER

Master Data SAP_BR_BUPA_MASTER_ Master Data - Business Partners SAP_BR_BUPA_MASTER_SPECIALIST

Pricing Spe- SAP_BR_PRICING_SPE- Price Management SAP_BR_PRICING_SPECIALIST

Master Data SAP_BR_PRODMASTER_S Master Data - Products SAP_BR_PRODMASTER_SPECIALIST

2.3 Master Data, Organizational Data, and Other Data

Sell from Stock (OD9_US)

Material SM0001 Service Material 01

Material NS0002 Non-stock Material 02

Sell from Stock (OD9_US)

Ship-to Party 17100003 Domestic US Customer 3

Payer 17100003 Customer domestic 03

Storage Location 171A

Shipping Point 1710

Sales Organiza- 1710

BNF Create Product Master of Type "Trading Good"

Sell from Stock (OD9_US)

BND Create Customer Master

2YX Create Customer-Material Info Record

6N3 Create Customer Hierarchy

2.4 Additional Manual Configuration

2.5 Business Conditions

Scope Item Business Condition

Sell from Stock (OD9_US)

2.6.1 Set Initial Stock for Material

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

Test Step Test Step Name Instruction Expected Result Com-

Sell from Stock (OD9_US)

Note Only relevant for batch-relevant material.

9 Save Your Entries Choose Post.

Material Debited Accounts Credited Accounts

Trading Good (HAWA) 13600000 39912000

2.6.2 Set Relevant for Proof of Delivery in BP Master Data (Optional)

Sell from Stock (OD9_US)

5 Set POD - Relevant Select POD - Relevant checkbox.

6 Save Choose Save.

2.6.3 Create Template Item Proposal (Optional)

Sell from Stock (OD9_US)

Sales Document Type: PV

5 Enter Item Proposal Details In the Products tab, choose Create:

6 Save the Entry Choose Create.

2.6.4 Create Condition Records (Optional)

BET Create Sales Pricing Condition

Sell from Stock (OD9_US)

2.6.5.1 Extend Product Hierarchy Materials (Optional)

2 Access the App Open Create Material (MM01)

3 Search for materials Make below entries and choose Continue

Sell from Stock (OD9_US)