Test Script

SAP S/4HANA Cloud - 14-07-22

Sales Scheduling Agreements (3NR_GB)

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

3 Preliminary Steps
3.1 Maintain Customer-Material Info Record (Optional)
3.2 Set Initial Stock for Material
3.3 Create Condition Records (Optional)

4 Overview Table

5 Test Procedures
5.1 Create Sales Scheduling Agreement
5.2 Maintain Planning Delivery Schedule Instruction (Optional)
5.3 Check Incoming Delivery Schedules in AIF (Message Dashboard) - EDI relevant
5.4 Update Scheduling Agreement for Forecast Delivery Schedule Manually (Optional)
5.5 Update Scheduling Agreement for JIT Delivery Schedule Manually (Optional)
5.6 Generate Planning Delivery Schedule (Optional)
5.7 Check Planning Delivery Schedule (Optional)
5.8 Create Delivery
5.9 Execute Picking
5.10 Post Goods Issue
5.11 Send Advance Shipping Notice- EDI Relevant (Optional)
5.12 Check Advanced Shipping Notice in AIF (Message Dashboard) - EDI Relevant (Optional)
5.13 Create Preliminary Billing Document (Optional)
5.14 Create Billing Document
5.15 Send Invoice – EDI Relevant
5.16 Check Invoice in AIF (Message Dashboard) - EDI relevant

6 Appendix
6.1 Process Integration
6.2 Preceding Processes
6.3 Succeeding Processes

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 2
1 Purpose

The sales scheduling agreement is an outline agreement between the buyer and supplier. Forecast and JIT (Just-in-Time) delivery schedules are sent via EDI. These delivery schedules contain the de -
livery dates and quantities. The whole communication is based on cumulative quantities between buyer and supplier.
Planning delivery schedules can be generated to smooth the demand handed over to production.
The shipping specialist creates deliveries based on open quantities in the delivery outbound monitor.
After the completion of picking, the shipping specialist posts goods issue. This posting 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.
Advanced shipping notifications are sent via EDI to the buyer.
Once goods are delivered, you can invoice the delivery. An EDI invoice message is sent to the buyer.
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.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 3
2 Prerequisites

This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.

Caution Testing in a 3-System Landscape

In a 3-system landscape (with SAP Central Business Configuration as your configuration environment), changes to software and business configuration are applied to your systems indepen-
dently of one another. It is therefore your responsibility to manage the active business configuration in your systems and synchronize configuration data in your SAP S/4HANA Cloud system
landscape. A synchronization is required, for example, after you've enhanced the scope, extended configuration, or adopted new or changed content from content updates or upgrades. For more
information, refer to the product assistance in the SAP Help Portal.
Before testing, if you want to use all software features described for the process steps, reports, or items in this document, we recommend the Business Process Configuration Expert in your or-
ganization has upgraded the configuration content and deployed the configuration data to your system landscape.
If the decision is not to upgrade the configuration content in your test or production system, you can run regression tests of software changes using the procedures in the previous test script ver-
sion (see the following ).

2.1 System Access

System Details

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

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

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

Internal Sales Representative SAP_BR_INTERNAL_SALES_REP Internal Sales Representative SAP_BR_INTERNAL_SALES_REP

Shipping Specialist SAP_BR_SHIPPING_SPECIALIST Shipping Specialist SAP_BR_SHIPPING_SPECIALIST

Warehouse Clerk SAP_BR_WAREHOUSE_CLERK Warehouse Clerk SAP_BR_WAREHOUSE_CLERK

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 4
 Name (Role Template) ID (Role Template) Name (Launchpad Space) ID (Launchpad Space)

Billing Clerk SAP_BR_BILLING_CLERK Billing Clerk SAP_BR_BILLING_CLERK

Configuration Expert - Business Network Integration SAP_BR_CONF_EXPERT_BUS_NET_INT

Material Planner - External Procurement SAP_BR_MATL_PLNR_EXT_PROC Material Planner - External Procurement SAP_BR_MATL_PLNR_EXT_PROC

2.3 Master Data, Organizational Data, and Other Data

The organizational structure and master data of your company have been created in your system during activation. The organizational structure reflects the structure of your company. The master
data represents materials, customers, and vendors, for example, depending on the operational focus of your company.
Use your own master data or the following sample data to go through the test procedure.

Data Sample Value Details Comments

Material TG11 Trading Good for Reg. Trading (MRP planning) See sections Business Conditions and Preliminary Steps.
no Serial no.; no batch

Sold-to Party 11100003 Domestic Customer GB 3 Payment Card Data in Business Partner.
One-time payment card customer.

Ship-to Party 11100003 Domestic Customer GB 3

Payer 11100003 Domestic Customer GB 3

Plant 1110 Plant 1 GB

Storage Location 111A

Shipping Point 1110

Sales Organization 1110

Distribution Channel 10

Division 00

For more information on creating master data objects, see the following Master Data Scripts (MDS)

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 5
 Table 1: Master Data Script Reference
Master Data ID Description

BNF Create Product Master of Type "Trading Good"

BND Create Customer Master

2YX Create Customer-Material Info Record

2.4 Additional Manual Configuration

Before you can test this scope item, you must have completed the additional configuration steps that are described in the Set-Up Instructions for this scope item. These configuration steps are specific
for your implementation and include mandatory settings that are not delivered by SAP and must be created by you. For more information, refer to the Set-Up Instructions for this scope item on SAP
Best Practices Explorer (https://rapid.sap.com/bp/#/browse/scopeitems/<enter the scope item ID>).

2.5 Business Conditions

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

Scope Item Business Condition

BNZ - Create New Open MM You have completed the step described in the Create New Open MM Posting Period (BNZ) master data script. Additionally, ensure that posting period is up to date. You need Buyer sys-
Posting Period tem to fetch the POs for sales order creation and to check whether the whole process flow is working.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 6
3 Preliminary Steps

3.1 Maintain Customer-Material Info Record (Optional)

Purpose

This process shows you how to maintain the customer-material info record to run through this scope item.

Note If the customer-masterial info record already exist, or you want to maintain the customer material manually when creating the scheduling agreement, please skip the step.

Procedure

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

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

2 Access the App Open Manage Customer Materials (F2499).

3 Access the Creation of Customer Material Choose Create. The Customer Material screen displays.

4 Enter Basic Customer-Material Information Value Map- Make the following entries: Basic customer-material information is main-
pings ● Customer: 11100003 tained.

● Product: TG11
● Sales Organization: 1110
● Distribution Channel: 10
● Customer Material Description: RM129

5 Save Choose Save. The Customer Material is successfully saved.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 7
3.2 Set Initial Stock for Material

Purpose

This process shows you how to enable materials in stock to run through this scope item.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to the SAP Fiori launchpad as a Warehouse

Clerk.

2 Access the App Open Post Goods Movement (MIGO). The Goods Receipt Other screen displays.

Note It will be displayed this way only if it was your last transaction. So the action for the
user should be to select the Reference Document for MIGO Transaction Other field.

3 Enter the Movement Type Select the following options and then choose Enter.
● Goods Receipt - Executable Action in Transaction
MIGO
● Other - Reference Document for MIGO Transaction

4 Make Entry in the Goods Receipt Under Goods Receipt Other Screen: Material tab, make
Other Screen: Material Tab the following entry and choose Enter.
● Material: <Material Number>

5 Make Entry in the Goods Receipt Under Goods Receipt Other Screen: Quantity tab, make
Other Screen: Quantity Tab the following entry and choose Enter.
● Qty in Unit of Entry: <Quantity in UOM>
● Unit of Entry: <PC>

6 Make Entry in the Goods Receipt Under Goods Receipt Other Screen: Where tab, make the
Other Screen: Where Tab following entry and choose Enter.
● Movement Type: 561- Receipt per ini-
tial en-try of stock balances into
use

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 8
 Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

● Plant: <Plant>
● Storage Location: <Storage Location>

7 Make Entry in the Goods Receipt Under Goods Receipt Other Screen: Batch tab, make the Only relevant for batch-relevant materials.
Other Screen: Batch Tab following entry and choose Enter.
● Date of Manufacture: <Current Date or a
past date>

8 Save Choose Post.

3.3 Create Condition Records (Optional)

Purpose

In case you have finetuned 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
Master Data ID Description

BET Create Sales Pricing Condition

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 9
4 Overview Table

This scope item consists of several process steps provided in the following table.

Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other apps not included on the homepage using the search bar.
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.

Process Step Business Role Transaction/App Expected Results

Create Sales Scheduling Agreement [page ] 12 Internal Sales Representa- Manage Sales Scheduling Agreements (F3515) Create scheduling agreement.
tive

Maintain Planning Delivery Schedule Instruction Internal Sales Representa- Change Sales Scheduling Agreements (VA32) Maintain planning delivery schedule instruction.
(Optional) [page ] 14 tive

Check Incoming Delivery Schedules in AIF (Mes- Configuration Expert - Message Dashboard - SAP Application Interface Frame- The message (Forecast Delivery Schedule and/or JIT Delivery Schedule) is
sage Dashboard) - EDI relevant [page ] 15 Business Network Integra- work (/AIFX/WDA_MSG_MONITOR) checked in dashboard.
tion

Update Scheduling Agreement for Forecast Deliv- Internal Sales Representa- Change Sales Scheduling Agreements (VA32) Manually maintain the forecast delivery schedule.
ery Schedule Manually (Optional) [page ] 16 tive

Update Scheduling Agreement for JIT Delivery Internal Sales Representa- Change Sales Scheduling Agreements (VA32) Manually maintain the JIT delivery schedule.
Schedule Manually (Optional) [page ] 17 tive

Generate Planning Delivery Schedule (Optional) Internal Sales Representa- Change Sales Scheduling Agreements (VA32) Manully generate planning delivery schedule.
[page ] 18 tive

Check Planning Delivery Schedule (Optional) Internal Sales Representa- Display Sales Scheduling Agreements (VA33) Check planning delivery schedule.
[page ] 19 tive

#unique_19 Material Planner - External Monitor Material Coverage (Deprecated) - Net / Individ-
Procurement ual Segments (F2101)

Create Delivery [page ] 20 Shipping Specialist My Sales Order Schedule Lines - Due for Delivery Outbound delivery is created.
(VL10E)

Execute Picking [page ] 21 Shipping Specialist Outbound Deliveries for Picking (VL06P) The picking process involves taking goods from a storage location and stag-
ing the right quantity in a picking area where the goods are prepared for ship-
ping.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 10
 Process Step Business Role Transaction/App Expected Results

Post Goods Issue [page ] 23 Shipping Specialist Outbound Deliveries for Goods Issue (VL06G) An advanced shipping notification is sent to the Buyer system.

Send Advance Shipping Notice- EDI Relevant (Optional) [page ] 24 ASN is automatically sent to the Buyer system.

Check Advanced Shipping Notice in AIF (Message Configuration Expert - Message Dashboard - SAP Application Interface Frame- The message (ASN) is checked in dashboard.
Dashboard) - EDI Relevant (Optional) [page ] 24 Business Network Integra- work (/AIFX/WDA_MSG_MONITOR)
tion

Create Preliminary Billing Document (Optional) Billing Clerk Create Preliminary Billing Documents (F2876) The system generates an invoice for sales document automatically.
[page ] 25

Create Billing Document [page ] 27 Billing Clerk Create Billing Documents (F0798) Invoice is created and sent from the SAP S/4HANA system (supplier side) to
the buyer system.

Send Invoice – EDI Relevant [page ] 28 Supplier Invoice is automatically sent to the buyer system.

Check Invoice in AIF (Message Dashboard) - EDI Configuration Expert - Message Dashboard - SAP Application Interface Frame- The message (Invoice) is checked in dashboard.
relevant [page ] 29 Business Network Integra- work (/AIFX/WDA_MSG_MONITOR)
tion

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 11
5 Test Procedures

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

5.1 Create Sales Scheduling Agreement

Purpose

This process step shows you how to create a Scheduling Agreement.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 12
Procedure

Test Step Test Step Name Instruction Expected Result Comments

#

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 Scheduling Agreements (F3515).

3 Navigate to Create Scheduling Agree- On the Manage Sales Scheduling Agreements screen, choose Create Scheduling Agreements.
ment Screen

4 Enter Data On the Create Scheduling Agreements screen, make the following entries and choose Continue:
● Sched. Agreemt Type: choose from LZ,
● Sales Organization: 1110
● Distribution Channel: 10
● Division: 00

5 Enter Scheduling Agreement Details On the Create Sched. Agr. w/Rel: Overview screen, make the following entries:
● Sold-To Party: 11100003
● Ship-To Party: 11100003
● Customer Reference: Purchase scheduling agreement number from customer
● Material Number: TG11
● Customer Material: RM129

6 Save Document Choose Save.

Make a note of the scheduling agreement number: __________.
If you have created a scheduling agreement with the same data in your system and you use material TG11 and customer
11100003, the following warning may appear:
There is already a scheduling agreement with this same data.
To skip this warning, choose Enter.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 13
5.2 Maintain Planning Delivery Schedule Instruction (Optional)

Purpose

This process step shows you how to maintain planning delivery schedule instruction.

Note The step is only relevant that if you want to create planning delivery schedule according to forecast delivery schedule. Planning delivery schedule only relevant to the forecast delivery
schedule based on week or Month.

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

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 Change Sales Scheduling Agreements (VA32).

3 Choose Scheduling Agreement On the Change Scheduling Agreements screen, make the following entries and choose Enter:
● Scheduling Agreement: <Created in previous step>

4 Navigate to Item level On the Change Sched.Agr.w/ Rel.XXXXXXXX: Overview screen, choose the Item line, and choose Display Item
Details

5 Enter Planning Delivery Schedule Instruci- On the Change Sched.Agr.w/ Rel.XXXXXXXX: Item Data screen, choose Call Control Parameter and make the
ton following entries:
● PlanDS instruction: SAP1

6 Save Document Choose Save.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 14
5.3 Check Incoming Delivery Schedules in AIF (Message Dashboard) - EDI relevant

Purpose

The forecast delivery schedule or JIT delivery schedule has been created and released from Buyer System and send via EDI to the Supplier. They are automatically processed if no error occurs. This
process step shows you how to check the message status.

Prerequisites

The forecast delivery schedule or JIT delivery schedule has been created and released from Buyer System.
This step is only relevant to EDI relevant delivery schedules.

Procedure

Test Step Test Step Name Instruction Expected Re- Comments

# sult

1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Network Integration.

2 Access the App Open Message Dashboard - SAP Application Interface Framework (/AIFX/WDA_MSG_MONITOR).

3 Choose Date And Namespace/Inter- On the Interface Monitor screen, choose correct time period entries and choose Search.
face Choose the line of /SDSAR, Inbound Scheduling Agreement Processing and choose All Messages.

4 Check Detail Messages On the Monitoring and Error Handling screen, expend the messages in the left side of the screen, and choose the corresponding scheduling
agreement number in Buyer system.
Double choose the message to see the detail information on the right side of the screen.

5 Reprocess Messages Choose Reprocess if needed.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 15
5.4 Update Scheduling Agreement for Forecast Delivery Schedule Manually (Optional)

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This process step shows you how to manually create the forecast delivery schedule in predefined scheduling agreement.

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative.

2 Access the App Open Change Sales Scheduling Agreements (VA32).

3 Choose Scheduling Agreement On the Change Scheduling Agreements screen, make the following entries and choose Enter:
● Scheduling Agreement: <Created in previous step>

4 Choose Forecast Delivery Schedule On the Change Sched.Agr.w/ Rel. XXXXXXXX: Overview screen, choose the line Item and choose Fore. DlSch.

5 Enter the Forecast Delivery Schedule On the Change Sched.Agr.w/ Rel. XXXXXXXX: Item Data screen, make the following entries and choose Enter.
● Dlv. Schedule: 0 (Del.sched.no. must be different from the previous one, so in case of existings ones choose previous no. +1)
● Dlv. Sched. Date: <Today>
● Date Type: W
● Date: <Today>
● Order Quantity: <6>
Create similar entries for next 3 weeks.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 16
 Test Step # Test Step Name Instruction Expected Result Comments

6 Save Document Choose Save to save your changes.

5.5 Update Scheduling Agreement for JIT Delivery Schedule Manually (Optional)

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This process step shows you how to manually create the JIT delivery schedule in predefined scheduling agreement.

Note JIT delivery schedule is an optional step. How schedule lines are handled in MRP is depending on the predefined settings. In this scenario following settings are predefined: within the JIT
delivery schedule horizon the JIT delivery schedule is relevant for MRP, and delivery-outside the JIT delivery horizon the forecast delivery schedule is relevant for MRP and delivery.

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

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 Change Sales Scheduling Agreements (VA32).

3 Choose Scheduling Agreement On the Change Scheduling Agreements screen, make the following entries and choose Enter:
● Scheduling Agreement: <Created in previous step>

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 17
 Test Step # Test Step Name Instruction Expected Result Comments

4 Choose JIT Delivery Schedule On the Change Sched.Agr.w/ Rel. XXXXXXXX: Overview screen, choose the line Item and choose JIT DlSch.

5 Enter the Forecast Delivery Schedule On the Change Sched.Agr.w/ Rel. XXXXXXXX: Item Data screen, make the following entries and choose En-
ter.
● DIv.schedule:99
● Dlv. sched.date: <Today>
● JIT hor.: <Today-1>
● Order Quantity: 2
Add additional schedule lines and choose Enter.
● Order Quantity: 3
● Order Quantity: 4

6 Save Document Choose Save to save your changes.

5.6 Generate Planning Delivery Schedule (Optional)

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This process step shows you how to generate plannig delivery schedule manually.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 18
Prerequisite

Planning delivery schedule instruction has been set. Forecast delivery schedule has been created manully with date type week or month. For delivery schedule generated via EDI, planning delivey
schedule will generate automatically.

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative.

2 Access the App Open Change Sales Scheduling Agreements (VA32).

3 Choose Scheduling Agreement On the Change Scheduling Agreements screen, make the following entries and choose Enter:
● Scheduling Agreement: <Created in previous step>

4 Navigate to Item level On the Change Sched.Agr.w/ Rel.XXXXXXXX: Overviewscreen, choose the Item line, and choose Display Item Details.

5 Enter Planning Delivery Schedule Instruci- On the Change Sched.Agr.w/ Rel.XXXXXXXX: Item Datascreen, choose Planning Delivery Schedule, and choose Generate
ton plan. Dlv.sched.

6 Save Document Choose Save.

5.7 Check Planning Delivery Schedule (Optional)

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 19
Purpose

This optional process step shows you how to check plannig delivery schedule.

Prerequisite

Planning delivery schedule is generated.

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

1 Log On Log on to the SAP Fiori launchpad as an Internal Sales Representative.

2 Access the App Open Display Sales Scheduling Agreements (VA33).

3 Choose Scheduling Agreement On the Display Scheduling Agreements screen, make the following entries and choose Enter:
● Scheduling Agreement: <Created in previous step>

4 Navigate to Item level On the Display Sched.Agr.w/ Rel.XXXXXXXX: Overview screen, choose the item line, and choose Display Item De-
tails.

5 Enter Planning Delivery Schedule Instruciton On the Display Sched.Agr.w/ Rel.XXXXXXXX: Item Data screen, choose Planning Delivery Schedule.

5.8 Create Delivery

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 20
Purpose

This process step shows you how to log on to the SAP S/4HANA system to create an outbound delivery for the previously received delivery schedule (scheduling agreement).

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

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

2 Access the App Open My Sales Order Schedule Lines - Due for Delivery (VL10E). The Sales Order Schedule Lines screen
displays.

3 Search Scheduling Agree- On the Sales Order Schedule Lines screen, make the following entries and choose Continue:
ment ● Shipping Point: 1110
● Selection Date: <Shipping date>
● CalcRuleDefltDlvCrDt: <Blank>
On the Sales Orders tab:
● SD Document: <Scheduling Agreement number created previously>
Choose Execute.

4 Create Delivery On the Activities Due for Shipping “Sales Order Schedule Lines” screen, choose Sales Sched. Agr. No. created in previ-
ous step, and choose Dialog.

5 Save Delivery Choose Save, make a note of the delivery number. Creation of a delivery is triggered.

5.9 Execute Picking

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Sales Scheduling Agreements (3NR_GB

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

Purpose

The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods are prepared for shipping. This process step shows you how to pick
deliveries, if the items is not relevant for picking please exclude this step execution : Example Consignment

Procedure

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

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

2 Access the App Open Outbound Deliveries for Picking (VL06P) .

3 Enter Shipping Point Make the following entries, and choose Execute.
● Shipping Point: 1110
● Select Only Picking Without WM option
● Picking Date: <Current Date +1>

4 Choose Delivery On the Day’s Workload for Picking screen, choose the Delivery document created in previous step, and choose Change Outbound De-
liveries.

5 Enter Picked Quan- On the Delivery XXXXXXX Change: Overview screen, go to the Picking tab and enter quantity equal to delivery Qty in Picked Qty
tity field for picking related item(s).

6 Choose Enter Choose Enter.

7 Save Choose Save. The delivery is picked

now.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 22
5.10 Post Goods Issue

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This process step shows you how to post goods issues for delivery in the SAP S/4HANA system (supplier side).

Procedure

Test Step # Test Step Name Instruction Expected Result Comments

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

2 Access the App Open Outbound Deliveries for Goods Issue (VL06G).

3 Open Outbound Delivery On the Outbound Deliveries for Goods Issue screen, make the following entries and choose Execute.
Monitor ● Shipping Point: 1110
● Pland Gds Mvmnt Date: <Current Date + 1>

4 Choose Outbound Delivery On the Goods issue for Outbound Deliveries to be Posted screen, choose the outbound delivery document created in previous step, and
choose Change Outbound Deliveries.

5 Post Good Issue On the Delivery XXXXXXXX Change: Overview screen, choose Post Goods Issue. The goods issue is
posted.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 23
Financial Posting

Material Debited Accounts Credited Accounts Cost Element / CO Object

Trading Good (HAWA) 51600000 13600000 none

Consptn Trde Gds Inventory TradingGd

5.11 Send Advance Shipping Notice- EDI Relevant (Optional)

Purpose

This process step shows you how ASN is sent to the Buyer system.

Prerequisites

Goods issue must have been posted in the SAP S/4HANA system (supplier side).
This step is only relevant to EDI relevant deliveries schedules.

Procedure

This step is automatically generated.

5.12 Check Advanced Shipping Notice in AIF (Message Dashboard) - EDI Relevant (Optional)

Purpose

The advanced shipping notification is sent via EDI to the Customer. They are automatically processed if no error occurs. This process step shows you how to check the message status.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 24
Prerequisites

The outbound delivery has been created and goods issue has been posted.

Procedure

Test Step # Test Step Name Instruction Expected Re- Comments

sult

1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Network Integration.

2 Access the App Open Message Dashboard - SAP Application Interface Framework (/AIFX/WDA_MSG_MONITOR).

3 Choose Date and Namespace/Interface On the Interface Monitor screen, choose correct time period entries and choose Search. In the Result List, choose the line of /LEEDI
and choose All Messages.

4 Check Detail Messages On the Monitoring and Error Handling screen, expend the messages in the left side of the screen, and choose the corresponding deliver-
ing number.
Double choose the message to see the detail information on the right side of the screen.

5 Reprocess Messages Choose Reprocess if needed.

5.13 Create Preliminary Billing Document (Optional)

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 25
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

Test Step Test Step Name Instruction Expected Result Comments

#

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 The Sales Document is displayed in the result.
input help to choose a value.

4 Define Preliminary Billing Settings Choose Preliminary Billing Settings at the top 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 three tabs (Columns, Sort, 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
worklist.
Choose Restore to restore the default.

6 Select An Item to Create Preliminary Billing Select the document and choose Create The Manage Preliminary Billing Documents screen
Document displays.

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

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 26
 Test Step Test Step Name Instruction Expected Result Comments
#

9 Select the Preliminary Billing Document to Select the Preliminary Billing Document you have created and choose Create Billing Docu- The system generates an invoice for sales document
be Invoiced ment. 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.

5.14 Create Billing Document

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

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

Purpose

This process step shows you how to create invoices in SAP S/4HANA system.

Procedure

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

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 Billing Documents (F0798). The Create Billing Documents screen dis-
plays.

3 Define Billing Settings Choose Billing Settings in the bottom bar, you can make the following settings:
● Set billing date and type before billing: ON

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 27
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

● Create separate billing document for each item of billing due list: OFF
● Automatically post billing documents: ON
● Display billing documents after creation: ON
● Choose delivery items to be billed and select quantities: OFF

4 Choose Individual Billing Docu- Select row of delivery document created previously and choose Create. The Create Billing Document screen dis-
ment plays.

5 Maintain Billing Date Choose billing type F2 Invoice and maintain billing date, for example current date, then choose OK New billing document is created.
and Save.

6 Display Billing Document The billing document appears automatically. The system generates an invoice for billing.

Financial Postings

Example

Material Debited Accounts Credited Accounts Cost Element / CO Object

Trading Goods (HAWA) 11100003 41000000 none

Domestic Customer GB 3 Rev Domestic Prod
22001000
Sales Tax Accrued
21730000 (optional)
Freight Clrg MM

5.15 Send Invoice – EDI Relevant

Purpose

This process step shows you how to send invoice to the Buyer system.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 28
Prerequisites

Billing Document must have been created in the SAP S/4HANA system (supplier side).

Procedure

This step is automatically generated.

5.16 Check Invoice in AIF (Message Dashboard) - EDI relevant

Purpose

The customer invoice is sent via EDI to the Buyer. They are automatically processed if no error occurs. This process step shows you how to check the message status.

Prerequisites

The billing document has been created.

Procedure

Test Step Test Step Name Instruction Expected Re- Comments

# sult

1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Network Integration.

2 Access the App Open Message Dashboard - SAP Application Interface Framework (/AIFX/WDA_MSG_MONITOR).

3 Choose Date and Namespace/Inter- On the Interface Monitor screen, choose correct time period entries and choose Search. In the Result List, choose the line of /SDEDI, Out-
face bound Invoice Processing and choose All Messages.

4 Check Detail Messages On the Monitoring and Error Handling screen, expend the messages in the left side of the screen, and choose the corresponding billing num-
ber created in previous step.
Double choose the message to see the detail information on the right side of the screen.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 29
 Test Step Test Step Name Instruction Expected Re- Comments
# sult

5 Reprocess Messages Choose Reprocess if needed.

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 30
6 Appendix

6.1 Process Integration

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

6.2 Preceding Processes

If you want to process the EDI relevant steps, you must have completed the following processes and conditions before you start with the test steps:

Process Business Condition

BMR- Scheduling Agreements in Procurement Sections Creating Scheduling Agreement,

Maintain Delivery Schedule,
Create Supplier Invoice, etc.

6.3 Succeeding Processes

After completing the activities in this test script, you can continue testing the following business processes:

Scope Item Business Condition

J59 - Accounts Receivable Posting a Customer Invoice in Accounting, etc.

Using the master data from this document, complete the following activities described in the test script:
● Account Receivable (Sections Posting a Customer Invoice in Accounting, Overdue Receivables, Display Customer Balances, Manage Customer Line Items.)

Sales Scheduling Agreements (3NR_GB

Purpose PUBLIC 31
 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 .

© 2022 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-

Sales Scheduling Agreements (3NR_GB tion and notices.
Purpose PUBLIC 32