demo script - sap ui · pdf filedemo script supply chain highlights – cycle count ......

Golden Demo Supply Chain Highlights - Cycle Count

SAP Business ByDesign Reference Systems

Demo Script

Supply Chain Highlights – Cycle Count

Classification: Internal and for Partners

Version: 20171218


Document Version: 20171218 2

Disclaimer

This demo script is based on the ByD Reference System for the Almika model company. There are several country versions

of the Almika ByD implementation available. The content is similar but deviates especially with respect to language support,

names and object descriptions. Sample data used in this demo script relates to the US country version – for other country

versions different data samples might be relevant.

A prerequisite for being able to fully understand this demo script and run the demo, is a sound system knowledge on SAP

Business ByDesign. General assumption is that you are familiar with the Learning Center content available in your ByD

system at: Home Self-Services – Learning Center.

Although the script has been tested carefully you might nevertheless encounter different system behavior when running a

demo in an actual Almika demo tenant.

Release Statement

This version of the demo script is released for the following country versions of the ByD Reference System for the Almika

model company:

• US – United Stated, as of demo release ByD 1705

• DE – Germany, as of demo release ByD 1705

• UK – United Kingdom, as of demo release ByD 1705

• FR – France, as of demo release ByD 1705

• AT – Austria, as of demo release ByD 1705

• CH – Switzerland, as of demo release ByD 1705

• NL – Netherlands, as of demo release ByD 1705

• CA – Canada, as of demo release ByD 1705

• MX – Mexico, as of demo release ByD 1705

• AU – Australia, as of demo release ByD 1705

• CN – China, as of demo release ByD 1705

• IN – India, as of demo release ByD 1705

The demo release basically is determined by the time when the demo tenant has been provisioned for demo usage, a demo

tenant provided between mid of March and mid of June 2018 is part of the demo release ByD 1802.

As of demo release ByD 1802 the release status of your ByD demo tenant can be identified in the Company-Specific-Help:

You can find a help entry “ByD <nnnn> Demo Guides <CC>” under Help – Company-Specific-Help. <nnnn> specifies the

demo release of your ByD demo tenant, e.g. ‘1802’ – released in February 2018. <CC> specifies the country version of your

demo tenant, e.g. ‘US’ – Almika US country version. The version-controlled demo guides provided in this help entry match to

the demo release and the country version of your ByD demo tenant. Please be aware that the demo guides are not specific

to the country version, only the version of the demo guide is specific to your ByD demo tenant.



Table of Content

1 Demo Script Overview ................................................................................................................................... 4

1.1 Demo Overview ...................................................................................................................................... 4

1.2 Intended Audience.................................................................................................................................. 4

1.3 Protagonists ........................................................................................................................................... 4

1.4 Business Pain Points .............................................................................................................................. 4

1.5 Key Messages and Value Proposition ..................................................................................................... 5

1.6 Story Flow Summary .............................................................................................................................. 5

2 Technical Requirements ................................................................................................................................ 6

2.1 System Access Information ..................................................................................................................... 6

2.2 User Accounts ........................................................................................................................................ 6

3 Demo Steps .................................................................................................................................................... 7

3.1 Prerequisite: Stock Overview .................................................................................................................. 7

3.1.1 Check Stock Overview ............................................................................................................... 7

3.2 Create new Cycle Count ......................................................................................................................... 8

3.2.1 Create New Product Count ........................................................................................................ 8

3.2.2 Create Count Task .................................................................................................................... 9

3.3 Execute Cycle Count ............................................................................................................................ 10

3.3.1 Confirm Count Task ................................................................................................................. 10

3.3.2 Approve Count Result .............................................................................................................. 11

4 Scenario Quick Guide and Key Master Data ................................................................................................ 13



1 Demo Script Overview

1.1 Demo Overview

This demo scenario describes how you can create and execute a new product count supported by count tasks. The

warehouse manager creates a count document based on all cycle-counted products; the system automatically creates the

respective count tasks. Each count document can contain a number of count tasks, which an assigned warehouse operator

accesses from physical inventory task folders. This helps to organize the counting-related work in your warehouse. You can

monitor the counting process and preview detailed information about the progress and status of count items and count

documents. You can view the counting results, including any differences when compared to the book values. With this

detailed information, you can quickly see and react to deviations as they occur and initiate appropriate follow-up actions,

such as requesting recounts. Once you approve a count document, the system updates the inventory and the inventory

records of your finance department.

This scenario includes features such as:

Cycle Counting

Creation of count tasks

Monitoring of count documents

React to deviations in quantity and value

1.2 Intended Audience

SAP internal: New hires

SAP external: CEO, CIO, CFO, Logistics Management, partner presales

1.3 Protagonists

Warehouse Manager

Typical KPI’s

Inventory Accuracy

Fill rate

Resource Utilization

1.4 Business Pain Points

Inaccurate inventory levels impact many aspects of a business

• Lost sales and lost customers

• Late deliveries

• High freight costs

• Expediting costs

• Write-offs at year end



1.5 Key Messages and Value Proposition

Grow the Business – improve inventory accuracy to ensure commitments are met

Ensure Profitability – eliminate lost sales due to inaccurate inventory levels

Stay Customer Centric – meet customer commitments

Overview

Give companywide visibility to accurate inventory levels

Ensure commitments and profitability through integration to supply chain and financials

Ensure true customer centricity through a complete and consistent view of all information

Key Features and Associated Benefits

Automatic Proposals of items to count

o Ensures you count the correct mix of high/med/low value items

Count Monitoring

o Visibility to the status of the cycle counts

Count Approval

o Approvals are required before inventory adjustments are posted

1.6 Story Flow Summary

This demo covers the business processes depicted in the orange boxes:

Create new Cycle Count

Check Stock Overview

Confirm Count Task

Approve Count Results



2 Technical Requirements

2.1 System Access Information

To run the demo, you need access to a ByD demo tenant for the Almika model company, which is available in different

country versions.

2.2 User Accounts

The following user accounts for ByD Almika implementation are to be used to run the demo:

Predefined User ID User Name Password Component

WAREHOUSE01P Luther Loblanski Welcome1



3 Demo Steps

3.1 Prerequisite: Stock Overview

3.1.1 Check Stock Overview

Introduction

Prior to beginning the demo you need to check the on-hand stock in order to get an overview which quantities have to

be entered during the product count.

What to Do

WoC Physical Inventory Select: Access Common Tasks Stock Overview Product ID: Click on More Filters

and enter the Products P100101, P100110, P100111

Site ID: P1100

Logistics Area ID: Click on More Filters. Exclude logistics areas P1100-30-10 and P1100-50 from the selection

Click Go

Export the on-hand stock to MS Excel and save it on your desktop for reference in order to enter suitable values

during cycle count

What you Should See



3.2 Create new Cycle Count

3.2.1 Create New Product Count

What to Say

Introduction

The Warehouse Manager creates a new physical inventory count document for selected products that are to be

counted in a certain cycle maintained in the material master data. Additionally the warehouse manager excludes

logistics areas from the count.

Key Features and Advantages

Items due to be counted can be automatically selected, ensuring the correct mix of items.

Count tasks can be split by various criteria, to optimize the count execution.

Value Statement

Cycle Counting greatly improves the ability to identify and fix inaccurate data, such as misplaced, mislabeled, or lost

stock.

It also improves the supply chain operations through more accurate inventory data.

What to Do

WoC Physical Inventory Select Access Common Tasks New Product Count

Storage Location ID: P1100

Mark Only Cycle-Counted Products indicator

Click Go

Select products P100101, P100110 and P100111 for counting

Click Next



What you Should See

3.2.2 Create Count Task

What to Say

Introduction

After selecting the scope of the count with regards to products and logistics areas, the count task is created

automatically.

What to Do

Exclude the following logistic areas from the product count: P1100-30-10

Click Finish.

Click Close.



What you Should See

3.3 Execute Cycle Count

3.3.1 Confirm Count Task

What to Say

Introduction

The automatically created count tasks are used to execute the product count. The warehouse manager can also print

the count task in order to get a list of all products and logistics areas to be counted. The count results are recorded

and confirmed in the count task.


Count sheets can be used for ‘Blind Counts’, where the book value is not displayed, or confirmation of book values.

Value Statement

Optimized count sheets allow greater efficiency in Cycle Count execution.

What to Do

WoC Physical Inventory Task Control

Show Tasks Not Started

Select your new created count task in the step before

Click Confirm

Product Actual Quantity: <Enter the on-hand stock from the Excel export for the three items; enter a quantity

variance of e.g. 2 EA for product P100111>

Click Finish All Items



3.3.1 Confirm Count Task

Click Close

What you Should See

3.3.2 Approve Count Result

What to Say

Introduction

The warehouse manager monitors the physical inventory counting process and is enabled to prioritize and quickly

access all current count documents that might require your attention due to variances in quantity and value. By

approving the count results the inventory gets updated automatically.


Exception Monitoring of tasks gives visibility to items with variances.

Items can be submitted for re-count quickly, to confirm variance is accurate before making adjustments.

Value Statement

Rapid visibility to variances helps identify and correct receiving, shelving, ordering, packaging, labeling, returns, and

fulfillment errors.

What to Do

WoC Physical Inventory Monitoring: By PI Count Document

Show PI Count in Process

Click Edit



3.3.2 Approve Count Result

Go to tab Count Items and check the variances in quantity and value

Click Approve All Count Items

Click Save

Click Close

What you Should See



4 Scenario Quick Guide and Key Master Data

Steps Summary

Path Data to Use/Enter Activity

Step 1 – Check Stock Overview

WoC Physical Inventory

Select: Access Common

Tasks Stock Overview

Products: P100101, P100110, P100111 Select the products to be counted and

check the on-hand stock

Export to MS Excel

Step 2 – Create New Product Count


Select: Access Common

Tasks New Product Count

Storage Location ID: P1100

Only Cycle-Counted Products

Products: P100101, P100110, P100111

Select the scope of products to be

included in the cycle count

Step 3 – Create Count Task

Exclude logistics areas: P1100-30-10,

P1100-50

Select the logistics areas to be

counted

Step 4 – Confirm Count Task


Task Control

Filter Tasks Not Started

Click Confirm

Product Actual Quantity: <Enter the on-

hand stock from the Excel export for the

three items; enter a quantity variance for

one item>

Click Finish All Items

Step 5 – Approve Count Result


Monitoring: By PI Count

Document

Filter PI Count In Process

Click Edit

Physical Inventory Count

Tab Count Items

Check variances in quantity and value

Click Approve All Count Items

Click Save

Click Close



Copyright

© 2017 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 affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its

distributors contain proprietary software components

of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation

or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the

materials. The only warranties for SAP or SAP affiliate company products and services are those that are

set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this

document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any

related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or

platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at

any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to

deliver any material, code, or functionality. All forward-looking statements are subject to various

risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to

place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing

decisions.

SAP and other SAP products and services mentioned herein as well as their 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 companies. See http://global.sap.com/corporate-en/legal/copyright/index.epx

http://global.sap.com/corporate-en/legal/copyright/index.epx

demo script - sap ui · pdf filedemo script supply chain highlights – cycle count ......

Documents