S4 HANA Demo Guide 1610 PDF

SAP S/4HANA, On-Premise edition 1610 PUBLIC
February 2017 (V1.2)

English
SAP S/4HANA, On-Premise edition 1610 fully-activated software appliance:

Demo Guide with Suggested Walkthrough Scenarios
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.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they
appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
Document History
Revision Date Change
1.0 <2016-19-12> Release for customer
1.1 <2016-20-12> BI demo scenario added, minor updates
1.2 <2017-05-01> Updates to reflect period change to 2017 in FI/CO scenarios
3
Table of Contents
1 Introduction 7
1.1 Consumption of the trial and underlying software appliance 7
1.2 Pre-configured scope 7
1.3 Further information and support 7
2 Business Content & Demo Scenarios 8

2.1 Demo scenarios - Overview 8
2.1.1 Available Business Configuration and Master Data 8
2.1.2 Logon to Systems 8
2.2 Demo Story 1 - Order to Cash 13
2.2.1 Stock Availability 13
2.2.1.1 Check Stock Availability 13
2.2.1.2 Post Goods Movement 14
2.2.1.3 Open Inventory Management Period 16
2.2.2 Credit Management 16
2.2.2.1 Credit Management role for Business Partner (BP) 17
2.2.2.2 Create Sales Order with Credit Block 18
2.2.2.3 Sales Order Fulfillment Issue 19
2.2.2.4 Release Sales Order Credit Block 20
2.2.3 Manage Sales Orders 22
2.2.3.1 Create Sales Orders 22
2.2.3.2 Print Sales Order Confirmation 23
2.2.4 Advanced ATP (aATP) 24
2.2.4.1 Backorder Processing (BOP) Segments and Variant 25
2.2.4.2 Product Availability 28
2.2.4.3 Run BOP 29
2.2.4.4 Fulfilment Responsibilities 31
2.2.4.5 Last Minute Adjustments of Confirmed Quantities 32
2.2.4.6 Troubleshooting 35
2.2.5 Delivery 36
2.2.6 Picking 37
2.2.7 Goods Issue 38
2.2.8 Billing 39
2.2.8.1 Create Billing Documents 39
2.2.8.2 Print Preview for Billing Documents 40
2.2.9 Sales and Distribution (SD) Settlement 41
2.2.9.1 Maintain Business Partner (BP) 41
2.2.9.2 Create Condition Contract 42
2.2.9.3 Settle the Condition Contract 45
2.2.9.4 Post Incoming Payment 47
2.2.9.5 Manage Customer Line Items 49
2.2.10 Sales Analytics 49
2.3 Demo Story 2 - Procure to Pay with Extended Warehouse Management (EWM) Inbound Processing 54
2.3.1 Create Purchase Order 54
2.3.2 Create Inbound Delivery 55
2.3.3 Process Goods Receipt 55
2.3.4 Move Pallets from Staging Area to Handover Point 59
2.3.5 Putaway of Products from the Handover Point to the High Rack Pallet Buffer 62
2.3.6 Create Supplier Invoice with PO/GR relation 65
2.3.7 Check Inbound Delivery 66
2.4 Demo Story 3 - Order to Cash with Extended Warehouse Management (EWM) Outbound Processing 68
2.4.1 Create Sales Order 68
2.4.2 Delivery 69
2.4.3 Create Warehouse Tasks Manually 70
2.4.4 Check Warehouse Order 71
2.4.5 Pick Warehouse Order 72
2.4.6 Close the Shipping Handling Units (HU) 76
2.4.7 Stage Shipping Handling Units (HU) 78
2.4.8 Display Loading Overview 80
2.4.9 Load Shipping HU 81
2.4.10 Post Goods Issue 82
4
2.4.11 Check Outbound Delivery Status 83
2.4.12 Billing 83
2.5 Demo Story 4 - Cash Daily Operations Extended 85
2.5.1 Preliminary Steps: Define Payment Signatories for Bank Account 85
2.5.2 Bank Transfer Actions 86
2.5.2.1 Initiate Bank Transfer 86
2.5.2.2 Track Bank Transfer 86
2.5.2.3 Approve Bank Transfer 87
2.5.2.3.1 Approval by First Approver 88
2.5.2.3.2 Approval by Second Approver 88
2.5.2.4 Download File 89
2.5.2.5 Check Status – Check Cash Flow Items 91
2.5.2.6 Cash Position Details 92
2.5.3 Cash Pooling 93
2.5.3.1 Create Bank Account Group 93
2.5.3.2 Create Cash Pool 95
2.5.3.3 Run Cash Concentration 95
2.5.3.4 Approve Cash Concentration 97
2.5.3.4.1 Approval by First Approver 97
2.5.3.4.2 Approval by Second Approver 98
2.5.3.5 Check Cash Position 99
2.5.3.6 Download File 100
2.6 Demo Story 5 - Plan to Product 103
2.6.1 Preliminary Step - Create Initial Material Stock 103
2.6.2 Preliminary Step – Check stock levels 104
2.6.3 Create Planned Independent Requirements 105
2.6.4 Material Requirements Planning at Plant Level 106
2.6.5 Create Production Order for Subassembly 108
2.6.6 Release Production Order for Parts Production 109
2.6.7 Confirm Production for Semi Finished Product 110
2.6.8 Post Goods Receipt for Production Order 111
2.6.9 Create Production Order for Final Assembly 112
2.6.10 Release Finished Goods Orders 114
2.6.11 Pick Components 115
2.6.12 Confirm Production for Semi Finished Product 116
2.6.13 Post Goods Receipt for Production Order 117
2.6.14 Actual Overhead Calculation Production Order 118
2.6.15 Calculate Work in Process (WIP) 120
2.6.16 Production Variance Calculation 120
2.6.17 Settle Variances 121
2.6.18 Analyze Variances 122
2.6.19 Production Cost Analysis 123
2.7 Demo Story 6 – Investment 124
2.7.1 Creating Investment Order 124
2.7.2 Plan Internal Order 125
2.7.3 Copy Plan Data from BPC to ERP 127
2.7.4 Accounts Payable - Posting Invoice to Investment Order 129
2.7.5 Monitoring Order Progress 130
2.7.6 Asset under Construction Settlement (Collective Processing) 131
2.7.7 Creating Assets for Complete AuC Settlement 134
2.7.8 Maintaining Settlement Rule for Final Settlement 135
2.7.9 Final Settlement of the Investment Order (Collective Processing) 137
2.7.10 Internal Orders Plan/Actuals 138
2.7.11 My Spend 139
2.7.12 Completion of Investment Order 140
2.8 Demo Story 7 - Extensibility 141
2.8.1 Remove/re-position standard fields in the Manage Product Master Fiori app 142
2.8.2 Adding two custom fields to the Product Master Fiori app 144
2.8.3 Creating your own custom fields 146
2.9 Demo Story 8 - SAP Screen Personas 149
2.9.1 Preliminary Steps 149
2.9.2 Creating a Flavor 149
2.9.3 Sharing a Flavor 153
2.9.4 Assigning a Flavor 153
2.9.5 Copying a Flavor 154
2.9.6 Changing a Flavor 155
5
2.9.7 Deleting a Flavor 155
2.9.8 Working with Resources 155
2.9.8.1 Uploading an Image 155
2.9.8.2 Sharing Resources with Other Personas Developers 156
2.9.9 SAP Screen Personas 3.0 Screens 157
2.9.9.1 Initial Screen 157
2.9.9.2 Flavor Manager 157
2.9.9.3 Flavor Editing – Home 158
2.9.9.4 Flavor Editing – Insert 159
2.9.9.5 Flavor Editing – Table 159
2.9.9.6 Flavor Editing – Design 160
2.9.9.7 Flavor Editing – Release 160
2.9.9.8 Flavor Gallery 161
2.9.9.9 Flavor Sharing 161
2.9.9.10 Theme Gallery 162
2.9.9.11 Scripting Screen 162
2.9.9.12 Scripting Screen - Inspector 163
2.9.9.13 Scripting Screen - Logging 164
2.9.10 Appendix 164
2.9.10.1 Additional Resources 164
2.9.10.2 Demo Videos 164
2.10 Demo Story 9 – SAP BusinessObjects BI Platform 165
2.10.1 Prerequisite: BI platform in your trial landscape 165
2.10.2 Accessing the BI platform 165
2.10.3 Connecting the BI platform to SAP S/4HANA 167
6
1 Introduction
1.1 Consumption of the trial and underlying software appliance

This demo script has been written based on the software appliance of SAP S/4HANA, On-premise edition 1610 with pre-configured
SAP Best Practices.
You can deploy and use this software appliance in two ways:
1. Via SAP Cloud Appliance Library (30-day trial or longer lasting subscription).
This is the easiest way to set up and access the 30-day trial as outlined in the Quick Start Guide on
https://go.sap.com/cmp/oth/crm-s4hana/s4hana-on-premise.html.
An Amazon Web Service (AWS) or Microsoft Azure account is required, and the fees for it have to be paid by the user
of the appliance.
SAP software may be used under the provided default test & evaluation agreement for the first 30 days, afterwards a
dedicated license for SAP software is required.
2. Via download or Blu-Ray disc delivery that you install on your own on-premise hardware.
After receiving the download/discs, you have to extract it to your prepared hardware and configure some parameters
according to your IT landscape (with Adobe Document Services).
Please note:
 A valid SAP software license is required for this delivery.
 This task is typically done by a system administrator.
 This demo script can also be used with the locally installed appliance.
 Please see below for further information how to obtain the download or Blu-Ray discs.
1.2 Pre-configured scope

The trial for the SAP S/4HANA, on-premise edition 1610 and the underlying software appliance is based on the fully activated SAP
Best Practices for SAP S/4HANA, on-premise edition. SAP Best Practices provide preconfigured settings and supporting content
that enable business processes to be executed in a working system in a prescribed ‘best practices’ or commonly required
approach. These settings can be used in a demo environment, such as the appliance, or can be used to set up a new DEV system
for a new SAP implementation.
The scope of these SAP Best Practices is documented on http://service.sap.com/s4op. The end-to-end demo scenarios in this
document which were developed to help showcase the capabilities in the S/4HANA 1610 appliance system are largely based on the
preconfigured settings and demo data provided by an extensive library of 76 preconfigured scope items.
If you explore additional features of the SAP S/4HANA system beyond what is provided in the scripts, you might find functions or
processes that are not pre-configured and, hence, will not provide a meaningful system response. In this case, you need to
configure those scenarios or functions using SAP standard documentation (e.g. via transaction SPRO) to make them work. Future
functionality within SAP Best Practices will be documented on the page above and other related channels.
You might also find errors and bugs as you explore the appliance. In this case, please search for SAP Notes and corrections and
decide if you want to apply them. The system behaves like a regular customer system once you have your own instance.
1.3 Further information and support

Support for the 30-day trial is offered via the SAP Community.
More information on the trial and the underlying software appliance can be found in this overview blog
https://blogs.sap.com/?p=406099
You may also browse the SAP CAL community (http://www.sap.com/community/topic/cloud-appliance-library.html) or ask a
question in https://answers.sap.com/questions/metadata/24005/sap-cloud-appliance-library.html. The community of SAP
employees, customers and partners will do their best to help you, however, there is no guaranteed service level agreement
attached to it.
For support for appliances within the SAP CAL subscription license (i.e. appliances that are running longer than 30 days) or for
systems that have been installed locally via download or Blu-Ray shipment, please report an incident on components BC-VCM-CAL
(for SAP CAL & connectivity issues) or the sub-components of SV-CLD-… for functional issues.
7
2 Business Content & Demo Scenarios
2.1 Demo scenarios - Overview

This document provides the necessary information to demonstrate the business processes within the preconfigured SAP
S/4HANA, On-premise edition landscape. Using this document, you will be able to walk through end-to-end processes for the
following areas:
1. Demo Story 1: Order-to-Cash
Run an end-to-end sales process flow where Credit Management, Advanced ATP, Sales & Distribution (SD) Settlement and
Output Management for S/4H are exemplified.
2. Demo Story 2: Procure to Pay with Extended Warehouse Management (EWM) Inbound Processing
Run a basic purchasing process, including the execution of EWM tasks specific for inbound processing.
3. Demo Story 3: Order to Cash with Extended Warehouse Management (EWM) Outbound Processing
Run an end-to-end sales process flow where the outbound processing using EWM is exemplified.
4. Demo Story 4: Cash Daily Operations Extended
Run a detailed scenario where Bank transfers, Cash pooling, approval workflow and specific Cash reports are exemplified.
5. Demo Story 5: Plan to Product
Run a make to stock scenario for subassembly and finished goods manufacturing, followed by the execution of the month-
end activities related to finished goods valuation.
6. Demo Story 6: Investment
Run an end-to-end process flow from creation, planning, capitalization, and reporting of an investment project.
7. Demo Story 7: Extensibility
Run a scenario in which Fiori apps can be extended with standard and custom fields.
8. Demo Story 8: SAP Screen Personas
Run a scenario in which flavors are developed in order to reduce the complexity of transactions.
9. Demo Story 9: SAP BI Platform
Run a scenario where you can display data from the SAP S/4HANA system in the SAP BusinessObjects BI platform
2.1.1 Available Business Configuration and Master Data

The SAP Best Practices customizing and sample master data have been activated in client 100 of your SAP S/4HANA system. You
can run the demo flow in the company code 1710 (US company code).
For further information on SAP Best Practices for SAP S/4HANA, On-Premise edition, please refer to the following document:
www.service.sap.com/s4op, and look under the “Solution Scope” for “Data Management”.
Want to learn more?

If you have an SAP Service Marketplace ID (SAP customers, partners, and employees) and you would like a detailed overview of the
organizational structure and sample master data including Chart of Accounts and General Ledger, or demo data such as Materials,
Business Partners and more, please download the full package under the “Download Package” link on the page listed above.
Once you have downloaded the package, extract the zip file to an own folder locally and launch the file,
“start_BP_OP_ENTPR_S4HANA1611_...html”. From this page, you can find all scope item documentation.
Master data and organizational structure documentation is found at the bottom of the entry webpage page, listed under the topic,
“What you also need to know”.
2.1.2 Logon to Systems

Before you continue with this section, please make sure that you can connect to the system.
 If you are accessing the system via SAP Cloud Appliance Library (http://cal.sap.com), you can either use the integrated
MS Windows remote desktop or a browser / SAP GUI that is locally installed on your computer. See the ‘Quick Start Guide’
on https://go.sap.com/cmp/oth/crm-s4hana/s4hana-on-premise.html for details how to set up the system access from
SAP CAL.
8
 If you are accessing a system that was installed from download/Blu-Ray discs on your own premises, you can only access
it via locally installed browser / SAP GUI. See the latest version of the First Steps guide that is attached to SAP Note
2396478, (http://service.sap.com/sap/support/notes/2396478).
In the following steps, we assume that you logon to the SAP S/4HANA system with users & passwords that have been pre-defined
by SAP. If a system administrator or other power user provided the system to you, the credentials and system roles might be
different.
The main user interface of SAP S/4HANA is the SAP Fiori Launchpad (also used throughout this demo) but access via SAP Logon /
SAP GUI is also possible. Depending on your personal settings (e.g. SAP GUI visualization settings, browser settings), your system
might look slightly different as shown in this guide.
Note about system performance:

When you access the system for the very first time, you will need to wait some time (can be as much as a few minutes) until the
Fiori Launchpad or the SAP GUI show up. In addition, using system functions (e.g. the Create Sales Order Fiori tile) for the first time
will be significantly slower.
This is a normal behavior (since the system needs to be compiled in certain areas for first use after startup) and will improve
significantly if you continue working with the system (note to administrators: SGEN has been performed).
Also, if the system has been re-activated after a Suspend period (needs to be done by the administrator of the SAP CAL account),
the system response will be slower during the first clicks on applications.
Note about demo users:

The user BPINST (password Welcome1) has all business roles assigned, and has access to all apps and transactions, which makes
this user appealing since it ‘sees everything’.
However, the performance of the Fiori Launchpad will be significantly slower for BPINST due to the massive amount of browser and
backend data to load.
Hence, instead of using the BPINST user, you should use the individual application user named in the demo scenario (e.g. S4H_SD,
see the demo scenarios below) for launching the SAP Fiori Launchpad. You will get a selection of all apps relevant to this user,
which will make it easier and faster for you to identify the proper apps. Initial loading of the Fiori Launchpad will also be faster.
Note about browser security messages, pop-up blocker & security

When accessing the Fiori Launchpad for the first time, you will be prompted about missing / unsigned certificates that might be
rated as a security thread (exact message depends on the browser version). Please ‘ignore’ these messages and add the Fiori
Launchpad URL to the list of secure sites in your browser.
Some of the apps (the SAP WebGui or Web Dynpro ABAP apps to be precise) will open in a separate browser tab. If you have a pop-
up blocker activated, you might see an error message about blocker pop-ups. Please confirm that you always would like to open
pop-ups from vhcals4hci.dummy.nodomain.
What to Do What You Will See

Logon to SAP S4H backend system via SAP GUI (for the demo scenarios, this is an optional step. It is mentioned
in here for completeness only)
Select the SAP Logon icon.
Double-click your SAP

system.
9
Make the following entries
and hit Enter:
 Client: 100
 User: S4H_SD
(or any other valid user)
 Password: Welcome1
 Language: EN
Result: You are logged on to

the SAP GUI
Log on to the SAP Fiori Launchpad:

https://vhcals4hci.dummy.nodomain:44300/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?s
ap-sec_session_created=X#Shell-home
Note:
To make this link work on your local computer, you need to maintain you ‘hosts’ file.
If you access the trial via the included remote desktop, these settings have been maintained already on the
remote desktop.
Both methods are described in detail in the Quick Start Guide on https://go.sap.com/cmp/oth/crm-
s4hana/s4hana-on-premise.html.
Open an internet browser, as

for example Google Chrome.
Enter your SAP Fiori

launchpad address:
https://vhcals4hci.dummy.n
odomain:44300/sap/bc/ui5_
ui5/ui2/ushell/shells/abap/F
ioriLaunchpad.html
Note:
When you get a warning such
as ‘Your connection is
not private’, select
Advanced, and then choose
Proceed to
vhcals4hci.dummy.nodomain
(unsafe).
The detailed warning text may
vary depending on the
browser.
10
Depending on the demo
scenario (see section 2.2 –
2.9 in this document), you
should use different users.
Enter your User, Password,
and Client as mentioned in the
respective demo scenario to
access the SAP Fiori launch
page.
Language: EN - English
Client: 100 (throughout this
script).
Click Log On.
You can search for an app,

using the search field on the
SAP Fiori Launchpad
By clicking on the icon located

in the upper left corner, the
user can see his recently used
applications.
Also, you have the option to

search for additional
applications in the entire
catalog, adjust user settings
or edit the Home Page.
To return to the main SAP

Fiori Launchpad, select the
Home icon . In case

you lose the Home page while
executing certain apps, you
can open a separate browser
session for launching the SAP
Fiori Launchpad in its initial
state.
TIP: Sometimes, the SAP Fiori
app does not perform as
expected due to cached
entries in the browser cache.
In order to avoid this, you
should clear the browser
history from browser settings
11
(e.g. press CTRL-H in Chrome
and delete the cache
settings).
12
2.2 Demo Story 1 - Order to Cash
Background information:
This scenario describes the standard Sales and Distribution (SD) document flow and is integrated with the following business
functions:
 Credit Management
 Advanced ATP (aATP)
 SD Settlement Management
 Output Management for S4HANA
In order to highlight some of the main capabilities of these business functions, this demo story uses five different business
partners and three different stock materials. Everything has a well-defined purpose and for this reason, the recommendation
would be to go step by step through the process in order to make sure that all mentioned functionalities can be fully
tested/explored.
The process starts by making sure that the required stock is available, then six different sales orders are created out of which one
has a credit block. Once the credit block issue is solved, a Backorder Processing is executed and the results are afterwards
manually adjusted in the Release for Delivery app. Since the stock will not be enough for all the open orders, only five out of six
orders will be partially or completely delivered to the customers. Then, the picking and goods issue are executed followed by the
billing process, using the specified billing date in order to make the SD settlement possible. Once the settlement accounting
documents are successfully created, a payment is posted and finally the overview analytics are checked.
2.2.1 Stock Availability

As a main prerequisite for this demos story, make sure there is enough stock available for the materials, which are going to be used.
When you start the instance for the very first time, the stock will be already available as described in the following steps. However, if
the appliance has been running for some time, make sure to post the necessary goods movement in order to adjust the stock. Or
another option would be to check the aATP chapter and readjust the stock according to the logic explained there.
2.2.1.1 Check Stock Availability

Open the Fiori
Launchpad (see 2.1.2)
with user S4H_MM,
password Welcome1.
Navigate to the Stock
Monitoring group and
click the Stock Multiple
Materials app.
Press the Material
Number multiple
selection button.
13
In the new pop-up
which will be displayed,
search for material IDs
starting with MZ-TG-
Y.
Select the following:
MZ-TG-Y120
MZ-TG-Y200
MZ-TG-Y240
Press OK.
Additionally select the

following:
 Plant: 1710
 Storage Location:
171A
Press Go.
When you start the

instance for the very
Material ID Plant Storage Location Unrestricted Stock
first time, you will find
the stock quantities MZ-TG-Y120 1710 171A 698 PC
mentioned in the MZ-TG-Y200 1710 171A 214 PC
following table. If this is
MZ-TG-Y240 1710 171A 89 PC
not the case, post
goods receipts in order
to reach the specified
unrestricted stock.
Another option would
be to adjust the
available stock
according to the aATP
scenario.
2.2.1.2 Post Goods Movement

This step is optional and it is executed only if there is not enough Unrestricted Stock available as described in the previous step.
14
Open the Fiori
with user S4H_MM,
password Welcome1.
Navigate to the
Warehouse Processing
group and click the
Post Goods Movement
app.
In the header screen

make the following
entries:
 Executable
Action: Goods
Receipt
 Reference
Document: Other
 RE in.entry stk
bals: 561
In the item details

screen, Material tab,
make the following
entry:
 Material:
Material ID
Click Enter.
In the Quantity tab,

make the following
entries:
 Qty in Unit of
Entry: Qty
 UM: PC
Click Enter.
In the Where tab, make

the following entries:
 Plant: 1710
 Storage location:
171A
Click Enter.
15
In order to check the
document and post the
goods receipt, click
Check and then Post
buttons from the
header section of the
document.
If there are any errors regarding the posting period, make sure to open the current period in the
Inventory Management as described in the following step.
2.2.1.3 Open Inventory Management Period

In order to post any goods movements like goods receipts for procurement or goods issues for outbound processing, the inventory
posting period has to be the same with the goods movement date. The system only allows one open inventory posting period at a
time. With the Close Periods SAP Fiori app, you can define which period opens and implicitly which one closes
When you start the instance for the very first time, the open period is 12/2016 (i.e. December 2016) which reflects the last period
open at the close of the development of the SAP S/4HANA 1610 appliance master system. If you want to post goods receipts or
goods issues with the current period (e.g. July 2017), you have to first close all previous periods and open the period for the current
date. This action has to be performed sequentially and only once for each month.

Open the Fiori
with user S4H_MM,
password Welcome1.
Navigate to the Master
Data - Administration
group and click the
Close Periods app.
A new browser
tab/screen will open.
This has to be done
sequentially - starting
with period 01/2017 -
until you have reached
the current period.
Enter these values at
the first run
 From company
code: 1710
 To company
code: 1710
 Period (which
opens): 01
 Fiscal year: 2017 On the following logging screen, choose Back and repeat with 02/2017, 03/2017, etc. until
Click Execute. you have reached the current month.
2.2.2 Credit Management

SAP Credit Management checks the exposure against the current credit limit for the business partner. In the current scenario, the
business partner will have such a low credit limit that no matter what he will order the credit limit will be exceeded. The following
steps will highlight how the credit limit is set and how a sales order with a credit block can be released.
16
2.2.2.1 Credit Management role for Business Partner (BP)
As a prerequisite for the Credit Management scenario, make sure that the BP has activated the SAP Credit Management role.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Data – Business
Partner group and click
the Maintain Business
Partner app.
On the header screen

make the following
selections:
 Business Partner:
USCU_S04
 Display in BP
role: SAP
Credit
Management
Navigate to the Credit

Profile tab and check
 Rules: Standard
rule with no
automatic
calculation
 Risk Class:
Medium
Default Risk
 Check Rule: 01
Default – All
Checks Active
Navigate further to the
Credit Segment Data
by pressing the
corresponding button
in the header of the
screen.
17
In the Credit limit and
Control tab, check the
following entries:
 Limit Defined:
checked
 Limit: 5 USD
 Valid To: the end
of the next
year
In order to make any
changes to the BP
master data, switch to
change mode by
clicking on the Switch
Between Display and
Change. When
complete, press the
Save button.
2.2.2.2 Create Sales Order with Credit Block

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the My
Home group and click
the Manage Sales
Orders app.
A new browser
Click the Create Sales
Order button.
In the Create Sales

Document screen,
make the following
entries (value help or
manually):
 Order Type: OR
 Sales
Organization:
1710
 Distribution
Chanel: 10
 Division: 00
Click Continue.
18
In the Header screen
make the following
manually):
 Sold-To Party:
USCU_S04
 Customer
Reference: a PO
number for
e.g.
In the Item screen,

make the following
entries:
 Material: MZ-TG-
Y240
 Order Quantity:
10
 Un: PC
Click Enter.
Click Save.
Since the credit limit of

5 USD was exceeded, a
corresponding
message will pop up.
Press Continue.
A success message,
containing the number
of the order, will be
displayed. Note this
number for the
following step.
2.2.2.3 Sales Order Fulfillment Issue

The credit block from sales order level prevents any quantity confirmation at the schedule line item level. Both issues can be
analyzed using the Sales Order Fulfilment Resolve Issues app.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the Sales –
Sales Order Processing
group and click the
Sales Order Fulfillment
– Resolve Issues app.
19
In the search bar,
search for the sales
order number which
was created in the
previous step.
As soon as the order

line item will be
selected, several Reject Sales Order – closes the credit case and blocks the order so no further processing can be
buttons will be done. Not in scope of this demo story.
activated in the bottom Recheck Credit – rechecks if anything changed with regards to the credit limit exceeding.
side of the screen. Display Credit Decision – dispalys the Credit Case’s status.
Process Flow – displays the document flow.
Further processing
options are available
by pressing the sales
order’s smart link.
Choose Display Sales
Order and check if any
quantity confirmation
was done.
Select the item and

press the Schedule
Line for Item button.
Due to the credit block,

0 pieces were
confirmed.
2.2.2.4 Release Sales Order Credit Block

When authorized staff decides that a block order can be released, this can be done by using the Manage Credit Cases app.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the Credit
Management – Daily
Business group and
click the Manage
Credit Cases app.
20
Expand the access
node SAP Credit
Management - Credit
Case -> Cases, and
double-click
Documented Credit
Decision – Search.
Click the Search
button.
The system displays all

documented credit
cases. Select the credit
case that was last
created.
For more details press
the Details button
and check the sales
order number.
In order to release the

sales order and be able
to deliver it to the
customer, select the
line item and press the
Release button.
Confirm the system
prompt.
A confirmation log is
displayed.
As a result, the ordered
quantity is confirmed
at the schedule line
item level (see
previous step).
21
2.2.3 Manage Sales Orders
2.2.3.1 Create Sales Orders

In this step, several sales orders are being created. All of them are going to be relevant for the logic of this entire demo story.
Make sure to use the recommended combinations of Customer – Material – Ordered Quantity as described in the following table
or adjust them according to the Backorder Processing (BOP) logic described in the aATP chapter.
No. Customer ID Material Ordered Qty. Confirmed Qty. UM Plant Storage Location Sales Order
1 USCU_S11 MZ-TG-Y120 100 100 PC 1710 171A
2 USCU_S03 MZ-TG-Y120 100 100 PC 1710 171A
3 USCU_S01 MZ-TG-Y120 650 498 PC 1710 171A
4 USCU_S11 MZ-TG-Y200 215 214 PC 1710 171A
5 USCU_L02 MZ-TG-Y240 90 79 PC 1710 171A

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the My
the Manage Sales
Orders app.
A new browser
Order button.
In the Create sales

Document screen
which opens, make the
following entries (value
help or manually):
 Order Type: OR
 Sales
Organization:
1710
 Distribution
Chanel: 10
 Division: 00
Click Continue.

make the following
manually):
 Sold-To Party:
USCU_S11 for
e.g.
 Customer
Reference: a PO
22
number for
e.g.
In the Item screen,

make the following
entries:
Y120 for.eg
 Order Quantity:
100 for e.g.
 Un: PC
Click Enter.
Click Save.
A confirmation pops up
specifying the sales
order ID.
Repeat the sales order When completed, five different sales orders will be created in this step in addition to the order
creation steps for all which had the credit block. All six documents will be relevant further for the aATP and mainly BOP
Customer – Material processing. Make sure to use the recomanded ordered quantities for each customer and
combinations material.
mentioned at the
beginning of this
paragraph.
2.2.3.2 Print Sales Order Confirmation

This step exemplifies the standard functionality for printing documents using PDFs and the NAST Technique.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the My
the Manage Sales
Orders app.
In the Sales Order field,

type in any of the sales
order number
previously created.
Click Enter.
Click on the sales order

smart link and choose
Display Sales Order.
23
In the upper side of the
Sales Order document,
click on the Header
Output Preview button.
The pdf. format of the

order confirmation is
displayed.
2.2.4 Advanced ATP (aATP)

The Advanced ATP functionalities included in the scope of this demo story are mainly the Backorder Processing and last minute
adjustments made using the Release for Delivery app. All five new aATP confirmation strategies are also included and they are
briefly described below:
 Win - Processing priority is 2. Assigned requirements are fully confirmed on the requested date (or immediately, if their
requested material available date is in the past).
 Gain - Processing priority is 3. Assigned requirements retain, at least, their confirmation or, if possible, improve.
 Redistribute - Processing priority is 4. Assigned requirements can get a better, equal or worse confirmation.
 Fill - Processing priority is 5. Assigned requirements do not gain additional quantity or get an earlier confirmation date. They
get an equal or worse confirmation.
 Lose - Processing priority is 1. Assigned requirements lose their current confirmation and are not confirmed.
The following list describes which strategy will be applied to each of the sales orders previously created and how the BOP run will
affect the confirmed quantities. Since the current scenario follows the Best Practice example described in the S/4HANA Help
Portal, further details can be found on http://help.sap.com/s4hana.
Sales Conf. Qty. Conf. Qty. BOP Setup

Customer Sales
Order Material ID Before BOP After BOP
ID Order Qty. BOP Variant Priority
Number: Run Run Conf. Strat. BOP Segment Name
Name Run
USCU_S11 MZ-TG-Y120 100 100 48 (-52) MY_BOP_RUN Redistribute 4 ALL_OTHER_CUSTOMERS
USCU_S03 MZ-TG-Y120 100 100 0 (-100) MY_BOP_RUN Redistribute 4 ALL_OTHER_CUSTOMERS
USCU_S01 MZ-TG-Y120 650 498 650 (+152) MY_BOP_RUN Win 2 CUST_HAS_PROMO_EVENT
USCU_S11 MZ-TG-Y200 215 214 214 MY_BOP_RUN Gain 3 PREMIUM_CUSTOMER
USCU_L02 MZ-TG-Y240 90 79 79 (+0) MY_BOP_RUN Fill 5 DO_NOT_WANT_MORE

USCU_S04 MZ-TG-Y240 10 10 0 (-10) MY_BOP_RUN Lose 1 CUST_ON_CREDIT_BLOCK
For more details go to http://help.sap.com/s4hana - SAP S/4HANA 1610 - Product Assistance (open the EN or DE version) - SAP S/4HANA - Enterprise Business
Applications – Sales - Basic Functions and Master Data in SD Processing (SD-BF) - Available-to-Promise (ATP)
Note:
In order to have the Release for Delivery app working correctly, please apply the SAP Notes 2403037 and 2406228.
24
2.2.4.1 Backorder Processing (BOP) Segments and Variant
Check each BOP segment and BOP variant and make sure they are defined as described in the following steps.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the ATP –
Backorder Processing
group and click the
Configure BOP
Segment app.
Check that the

selection criterial for
the
CUST_HAS_PROMO_E
VENT segment to be
the following:
SOLDTOPARTY of the
ATPDOCUMENT is
equal to 'USCU_S01'
Check that the

the
PREMIUM_CUSTOME
R segment to be the
following:
SOLDTOPARTY of the
ATPDOCUMENT is
equal to 'USCU_S11'
and MATERIAL of the
ATPDOCUMENT is
equal to 'MZ-TG-Y200'
25
Check that the
the
DO_NOT_WANT_MOR
E segment to be the
following:
SOLDTOPARTY of the
ATPDOCUMENT is
equal to 'USCU_L02'
Check that the

the
CUST_ON_CREDIT_BL
OCK segment to be the
following:
SOLDTOPARTY of the
ATPDOCUMENT is
equal to 'USCU_S04'
Check that the

the
ALL_OTHER_CUSTOM
ERS segment to be the
following:
SUPPLYINGPLANT of
the ATPDOCUMENT is
equal to '1710'
Open the Fiori

Launchpad with user
S4H_SD, password
Welcome1.
group and click the
Configure BOP Variant
app.
26
Select the
MY_BOP_RUN variant.
Click on the green box
describing the global
filter parameters and
check the following:
 Add Remaining
Items to Strategy:
Active
 Strategy:
Redistribute
 Segment:
ALL_OTHER_CUS
TOMERS
Check the Win strategy

of the MY_BOP_RUN
variant:
 Strategy: Win
 Segment:
CUSTOMER_HAS_
PROMO_EVENT
Check the Gain

strategy of the
MY_BOP_RUN variant:
 Strategy: Gain
 Segment:
PREMIUM_CUSTO
MER
Check the Fill strategy

of the MY_BOP_RUN
variant:
 Strategy: Fill
 Segment:
DO_NOT_WANT_M
ORE
Check the Lose

strategy of the
MY_BOP_RUN variant:
 Strategy: Lose
 Segment:
CUST_ON_CREDI
T_BLOCK
27
2.2.4.2 Product Availability
Before running the BOP, check the stock confirmation status for each material by using the Monitor Product Availability app.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Requirement
Processing group and
click the Monitor
Product Availability
app.
Make the following

entries:
Y120
 Plant: 1710
 Checking Rule:
SP
Press Enter.
Click the All Details

button in the header of
the screen.
Check the confirmed
quantities for the MZ-
TG-Y120 material.
Two orders should be
fully confirmed and
one should be partially
confirmed.
In the Material field

change the selection to
MZ-TG-Y200 and
press Enter.
Check the confirmed
TG-Y200 material.
There should be one
order with partially
confirmed quantity.
28
In the Material field
change the selection to
MZ-TG-Y240 and
press Enter.
Check the confirmed
TG-Y240 material.
There should be one
order fully confirmed
and another order
partially confirmed.
2.2.4.3 Run BOP

The scope of the Backorder Processing run is to adjust the confirmed quantities from the sales order schedule line level according
to the logic defined by the variant, segments and the strategies checked in the previous step.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
group and click the
Schedule BOP Run
app.
Click the New button in

order to schedule the
execution of the
MY_BOP_RUN variant.
Make the following

entries:
 Job Template: ATP
 Start Immediately:
checked
 Variant Name:
MY_BOP_RUN
29
Click Schedule.
The job details are

going to be available in
the Application Job list.

group and click the
Monitor BOP Run app.
In order to check the

results of the
MY_BOP_RUN variant
run, click on the most
recent line item from
the BOP Run List
screen. Make sure that
the processing status
is not In Process. In
case the run is still in
process, the view can
be refresh by clicking
the search icon.
The Run Overview

screen shows the
results grouped by
Material ID and Plant.
Select each line in
order to check the
confirmation changes
made for each sales
order item.
30
Check the BOP results
for the MZ-TG-Y120
material.
The order with the Win
strategy is fully
confirmed now while
the orders with the
Redistribute
strategy are partially
confirmed or
unconfirmed.

for the MZ-TG-Y200
material.
The order with the
Gain strategy is
partially confirmed
since no additional
stock is available. If
new unrestricted stock
would have been
available during the
BOP run, the order
would have been fully
confirmed.

for the MZ-TG-Y240
material.
The order with the
Lose strategy is
unconfirmed now while
the orders with the
Fill strategy hasn’t
gain additional stock.
2.2.4.4 Fulfilment Responsibilities

In order to make last minute confirmation adjustments using the Release for Delivery app, a responsibility worklist has to be
defined and assigned to a specific user with a limited validity. When you start the instance for the very first time, the validity period
might be set until the end of 2016. Make sure to update it at least until 31.12.2017.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Order Fulfillment
Responsibility group
and click the Configure
Order fulfillment
Responsibility app.
31
Click Go and select the
PLANT_1710
responsibility name.
Make sure that the

following assignments
are correct:
 Assigned User:
S4H_SD
 Validity Start -
Validity End: to
include the
current
period
In order to change the

user assignment or
adjust the validity
period, click the Edit
button, make the
required changes and
Save.
2.2.4.5 Last Minute Adjustments of Confirmed Quantities

Last minute adjustments of the confirmed quantities can be made using the Release for Delivery app. Since the 1610 version of this
app has some limitations, this step is optional. However if you decide to use it, please keep in mind the following:
 Do not open the app before the BOP run. Once the app opens, a temporary block of about 30 minutes is set for each
material and this might impact the BOP run or other related processes like the delivery creation.
 Not all delivery documents are created at the moment of the order release. Make sure to manually create the missing
documents.
 Make sure to release for delivery all the items in order for the app to get refreshed. If this is still not enough and the app
does not get refreshed, see the troubleshooting section at the end of this chapter.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Requirement
click the Release for
Delivery app.
32
From the right upper
corner of the screen,
select the PLANT_1710
responsibility worklist.
In the Unprepared tab,

check all the orders
which need manual
processing before
being delivered.
The unprepared orders
are grouped by
Material and Plant. Go
through each of them
and make final
adjustments.
Open line item for the

MZ-TG-Y120 material.
Click on the Refresh
Worklist button in
order to check if new
unreserved stock is
available. Afterwards,
check the Legend
located on the right
upper side of the
screen; since there is
no additional stock
available for MZ-TG-
Y120 material, publish
the results by clicking
Publish and Next.
For the MZ-TG-Y240
material, there are 10
pieces available and
one unconfirmed
order. In order to
confirm the order by
using the mass
processing
functionalities click This action has caused an overconfirmation which is indicated by the red bar on the top right.
Confirm All – Force
Confirmations.
Sort the orders
ascending by
Confirmed Quantity.
Click the Sort button
and make the
following selections:
 Sorting Criteria:
Confirmed
Quantity
 Sorting Order:
Ascending
33
To fix the over
confirmation, click the
Unconfirm All –
Unconfirm from
Bottom.
As a result of the
previous step, one
order is fully
confirmed, a second
one is partially
confirmed and no
additional stock is
available for MZ-TG-
Y120.
Publish the results and

go to the next material.
For the MZ-TG-Y200

material there is one
partially confirmed
order. To recheck if
additional stock has
been recently released
click on the Refresh
Worklist button.
Click Publish and Next.
Check any additional Note: In order for the Release for Delivery app to get refreshed and most recently created orders
materials which might to be shown, make sure to Publish and Release all the orders which are currently displayed in the
exist in the Unprepared Unprepared tab. Furthermore, if this is not enough, check the troubleshouting chapter.
tab.
Once the orders were

published, they will be
listed in the Prepared
tab.
Go to the Prepared tab,
select all the materials
and press the Release
for Delivery button.
This action should
trigger the automatic
creation of the
deliveries documents
for all selected Note: Due to some limitations of the 1610 version of the app, some deliveries might not be
materials. created. This will be managed by manually creating the missing documents in the 2.2.5 Delivery
step.
Navigate to the
Released tab in order
to check all the
released orders.
34
2.2.4.6 Troubleshooting
Due to some limitations of the Release for Delivery 1610 version, the app is not refreshed with new requirements once the last
processed orders were release for deliveries. In such cases, the solution is to reassign the S4H_SD user to the Fulfillment
Responsibility object as described in the following steps:

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Order Fulfillment
Responsibility group
and click the Configure
Order Fulfillment
Responsibility app.
Click Go and open the
PLANT_1710
responsibility worklist
item.
Click Edit.
Select the user

assignment and click
Delete.
Click Save.
Click the Add button.
Make the following

entry:
 Assigned
User: S4H_SD
 Validity Start:
<current
date>
 Validity End:
<one year
later>
Click Save twice.
35
A confirmation
message is displayed.
2.2.5 Delivery
In this step the delivery documents, which were not created with the Release for Delivery app, are manually created.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Logistic Execution –
Outbound Deliveries
group and click the
Create Outbound
Deliveries app.
Make the following
entries:
 Planned Creation
Date: Today and
Tomorrow
Click Go.
In order to make sure
that the orders for
USCU_S11 Bike World
are not combined,
select all orders,
except the one with
214 pieces.
Click Create Deliveries.
Click the Display Log

button and check the
documents which were
created in the Delivery
Creation Log.
Repeat the create

delivery step for the
order with 214 pieces.
Display the Delivery
Creation Log.
36
2.2.6 Picking
In this scenario, the picking step is handled by using the Pick Outbound Delivery app. However, there are other options like the My
Outbound Delivery Monitor app.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Outbound Deliveries
group and click the
Analyze Outbound
Delivery Logs app.
Make the following
entry:
 Created on:
<Today>
Press Enter.
Select the Logs one by

one and make a note of
all created delivery
documents. Some
were created
automatically while the
orders were released in
the Release for
Delivery app and some
were created manually
in the Create Delivery
step.
Open the Fiori

Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Outbound Deliveries
group and click the
Pick Outbound
Delivery app.
Make the following
entries:
 Delivery:
delivery
document
number
Press Enter.
37
Select the item and
type in the Picking
Quantity. Make it the
same with the Delivery
Quantity.
Click Copy Picking
Quantity and Save.
The picking Quantity

Status changes to
Completely Processed.
Repeat the picking

step for all the delivery
documents.
2.2.7 Goods Issue

For this step to work, you need to be sure that the date of the goods movement falls into an open inventory management period. If
there are any errors during the post Goods Issue processing make sure to check 2.2.1.3 Open Inventory Management Period.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Outbound Deliveries
group and click the
Outbound Deliveries
app.
Make the following

selection:
 Overall Status:
Ready to Post
GI
Select all the
documents that are
completely picked.
Click Post GI.
Select the current

date and click OK.
38
The GI Posted
confirmation message
is displayed.
2.2.8 Billing
In this step the billing documents are created. Since two of the billing docs posted here will be relevant also for the settlement
scenario, make sure to use the billing date as recommended.
2.2.8.1 Create Billing Documents

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Billing Document
group and click the
Create Billing
Documents app.
Click the Billing
Settings button.
Switch ON all billing

settings and click OK.
Select first just one of

the deliveries
documents belonging
to Bike World
USCU_S11 customer
and click Create.
39
In the Create Billing
Documents pop up,
make the following
entries:
 Billing Type: F2
Invoice
 Billing Date:
<yesterday>
Click OK.
Select now the

remaining deliveries
documents and click
Create.

Documents pop up
make the following
entries:
Invoice
 Billing Date:
<today>
Click OK.
2.2.8.2 Print Preview for Billing Documents

In the S/4HANA 1610 appliance, the printing for the billing documents uses the New Output Management for S4HANA. The
prerequisite for using the New Output Management are the setup of Business Rules Framework (BRF) + and the installation of
Adobe Documents Server. Furthermore, the switch from the NAST Technique to the New Output Management can be done
anytime and it is optional.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Billing Document
group and click the
Manage Billing
Documents app.
40
Make the following
selections:
 Billing Date: from
yesterday
until today
Select any of the billing

documents and click
Display.
In the header screen of

the document, click the
Output Items tab.
Click the Preview
button.
The pdf form using the

new Output
Management for
S4Hana is displayed in
a new tab/window.
2.2.9 Sales and Distribution (SD) Settlement

The rebate settlement process previously used by SD in ERP has been replaced by Settlement Management’s in S/4 HANA. The
settlement process begins with an agreement between an SD supplier and their customer. The agreement is recorded in the
system using the condition contract. As soon as some billing documents have been created in the system, the supplier can run the
subsequent settlement in order to determine the sales rebate owed to the customer.
2.2.9.1 Maintain Business Partner (BP)

As a prerequisite for the Settlement run, check and change if necessary the required settings in the BP’s master data.
41
Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Data – Business
Partner group and click
the Maintain Business
Partner app.
Make the following
entries:
 Business Partner:
USCU_S11
 BP Role:
Customer
Click Sales and
Distribution button.
Click Switch Between
Display and Change
button.
In the Orders tab make
 Cust. Pric.
Procedure:
delete any
existing
entry
 Relevant for
Settlement
Management:
check
Click Save.
2.2.9.2 Create Condition Contract

The Condition Contract created in this step is a prerequisite for the subsequent settlement run. The contract will contain details as
the validity period, the combination of customer and materials which are entitled to discounts, the dates when the partial and the
final settlements are going to be executed (it is mandatory that they are included in the validity period of the contract) as well as the
condition rates and the scales which apply.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Settlement – Sales
Settlement
Management group
and click the Maintain
42
Contracts – Condition
Contracts app.
Click the Create
button.
Make the following

entry:
 Condition
contract type:
Sales Bonus
Based On
Billing
Documents
Click Continue.
Maintain the validity

period with the
following entries:
 From: <one day
before the
current date>
 To: <current
date>
In the Sales tab make

 Sales
Organization:
1710
 Distribution
Chanel: 10
 Division: 00
In the Business
Volume Selection
Criteria, click the Add
button twice and
Select BVCU field
combination.
Make the following

entry for the first item:
 Customer:
USCU_S11
Y120
Make the following
entry for the second
item:
 Customer:
USCU_S11
Y200
43
Navigate further to the
Settlement Calendar
tab.
Add one item with

 Settlement Date:
<one day
before the
current date>
 Settlement Date
Type: Partial
Settlement
Add a second item
with the following
entries:
<current
date>
 Settlement Date
Type: Final
Settlement
In the Condition area

(Second lower part of
the screen) select the
table field entry
Number I 0 entries
(second choice from
dropdown list box).
Chose and make the

following entry:
 Condition Type:
REBA
 Valid From: <one
day before
the current
date>
 Valid to:
<current
date>
In the conditions area,

change the Condition
Table field entry back
to the first choice from
dropdown list box.
Chose and make the

following entry:
 Condition Type:
REBT
44
 Valid From: <one
day before
the current
date>
 Valid to:
<current
date>
Select the REBT

condition line and
choose New Scale
Level to add each
scale line.
In the first scale line, enter 10% as your condition rate, 1000 as your scale and USD currency as
your scale unit.
Add a second scale line, enter 12% as your condition rate, 20.000 as your scale and USD currency
as your scale unit.
Choose Release from

the header screen.
The status of the
document changes
from Contract is
Inactive to Contract
is Active.
Save the condition

contract.
2.2.9.3 Settle the Condition Contract

The outcome of this step is the posting of one accounting document for each of the partial and final settlement run.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Settlement
Maintenance group
and click the Display
Business Volume app.
Make the following
entry:
 Condition
Contract: number
of the
condition
contract
previously
created
Choose Execute.
45
Check the Date for the
Partial Settlement and
the Date for the Final
Settlement.
Check also the BUVO
billing values for which
the settlement will
apply.
Navigate to the
Settlement
Maintenance group
and click the Settle
Condition Contract
app.
For the partial

settlement run make
<one day
before the
current date>
 Settlement Date
Type: 1
 Condition
Contract: number
of the
contract doc.
In the Program Run

Control section, you
can choose between
Check Run and Live
Run. Choose Live
Run for the settlement
to generate results.
Click Execute.
A successful log
An accounting
document was
created.
For the final settlement

run make the following
entries:
<current
date>
 Settlement Date
Type: empty
 Condition
Contract: number
of the
contract doc.
46
In the Program Run
Control section, you
can choose between
Check Run and Live
Run. Choose Live
Run for settlement to
generate results.
Click Execute.
A successful log
An accounting
document was
created.
2.2.9.4 Post Incoming Payment

In this step, a manual incoming payment will be posted for customer USCU_S11. The value of the of the payment will be less than
the value of the billing documents due to the accounting documents posted during the settlement run.

Open the Fiori
Launchpad with user
S4H_FIN, password
Welcome1.
Navigate to the My
the Post Incoming
Payments app.
Make the following
entries:
 Company Code:
1710
 Posting Date:
<current
date>
 Journal Entry
Date: <current
date>
 Value date:
<current
date>
 Journal Entry
Type: DZ
 G/L Account:
11001060
 House Bank /
Account ID:
USBK1/USAC1
 Amount:
25,555.20 USD
47
 Customer
Account:
USCU_S11
Click Propose Items.
Select the two billing

documents that were
created with one day
before date and with
the current date.
Select also the Click the Clear button for each relevant document.
accounting
document(s) that
was/were created
during settlement run.
Once the documents

were selected, make
sure that the Balance is
0.00 USD.
If this is not true, adjust
the Amount value from
the header details in
order to bring the
balance to zero.
Click Post.
A success message is
displayed.
Click Display.
The Journal Entry

document can be
checked in details.
48
2.2.9.5 Manage Customer Line Items
Check the customers recently closed items by using the Manage Customer Line Items app.

Open the Fiori
Launchpad with user
S4H_FIN, password
Welcome1.
Navigate to the My
the Manage Customer
Line Items app.
Make the following
entries:
 Customer:
USCU_S11 Click Go.
 Company Code:
1710
 Status: All
Items
 Posting Date:
Date Range
<one day before
the current date
– current date>
 Item Type:
Normal Items
Check the Cleared

documents.
Navigate further to any

of the documents by
using the smart links.
2.2.10 Sales Analytics

The Fiori Overview page for Order-to-Cash enables you to analyze the sales performance based on some of the key sales order
KPIs and it integrates several analytics into one view. This scenario highlights how filters and cards can be handled and how
selection values are copied when the user navigates to further apps by clicking any of the available cards.
49
Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the Order-
to-Cash Performance
click the Order-to-Cash
Performance Overview
app.
The Overview Page

launches successfully
and the following cards
display:
Sales Orders per
Month - Last 365 days
Sales Order Items per
Deliveries, Pickings,
Goods Issues per
Invoices per Month -
Last 365 days
Sales Order Totals -
Last 365 days
Sales Order Item
Totals - Last 365 days
Delivery Totals - Last
365 days
Billing Lead Time - Last
28 days
Sales Order Lead Time
- Last 28 days
Sales Order Item Lead
Time - Last 28 days
Delivery Lead Time -
Last 28 days
Global Filters can be

set in the Global Filter
bar and they will apply
to all cards on the
The content of the overview page will be refreshed according to the selection applied.
overview page.
Make the following
selection entries:
 Sales
Organization:
1710
 Sold-to party:
USCU_S11
50
Click Adapt Filter. In
the Adapt Filter pop
up, for the Order-to-
Cash Performance KPI,
click More Filters
button.
In the Select Filters

pop up, select
Created on and click
OK.
For the Order-to-Cash

Performance KPI, the
Created on selection
criteria is now
activated.
Click Go.
In the Global Filter bar,

click on the Created On
field.
Make the following

selection:
 Created On
 Between
Current Week
Click OK.
51
The cards get
refreshed base on the
current filtering
criteria.
Cards in the overview

page can be
customized through
Manage Cards button.
Click the User icon on
upper left side of the
screen and chose
Manage Cards.
In the Manage Cards
pop up the cards on
the overview page can
be re-arranged,
hidden and shown
again.
Make your changes
and press OK.
From the Overview

page you can navigate
to other apps, bringing
along the Global Filter,
Header or Line Item
information in the
main page. Click on
any of the cards in
order to navigate to
the corresponding
smart business app.
Click the Sales Order
Items per Month card.
In the header, you can
view the filtering
criteria carried from
the Overview Page
main screen.
52
Click the Add Analysis
Step button.
Click By Material.
Click Total by
Material.
Click Percentage
Stacked Bar Chart.
The detailed chart by

Material is displayed.
53
2.3 Demo Story 2 - Procure to Pay with Extended Warehouse
Management (EWM) Inbound Processing
2.3.1 Create Purchase Order

Manually create a purchase order for the products you want to purchase.

Open the Fiori Launchpad
with user S4H_MM,
password Welcome1.
Click on the Create

Purchase Order – Advanced
app.
Enter Head Data:

Order Type: Standard PO
Vendor : EWM17-SU01
Doc.date: <Current
date>
If the Header data is not
visible, choose Expand
Header.
Choose the Org. Data tab
page and enter the following
data:
Purchasing Org.: 1710
Purchasing Group: 002
Company Code: 1710
Enter the Item Data. If the

Item Overview is not
visible, choose Expand
Items.
Enter the following data:
Material: EWMS4-01
PO Quantity: 8
OUn: CAR
Plant: 1710
Storage Location: 171D
Choose the Save button

from the bottom-right part
of the screen.
Choose Enter to confirm
the message Can delivery
date be met?
Note down the PO number
for later use:
54
2.3.2 Create Inbound Delivery
Upon creation of the inbound delivery, the external delivery note IDN (ASN) is entered and later used as reference criterion for
Goods Receipt.

Open the Fiori Launchpad with
user S4H_MM, password
Welcome1.
Click the Create Inbound

Deliveries – Deliveries app
Enter following Data

Vendor: EWM17-SU01
Planned Dlv. Date:
Start Date = <Today - 1
Day>
End Date = <Today + 1
Month>
Choose Go.
Click on the purchase order you
have created.
Enter following Data:

ASN: For example, ASN-45-
####, where #### are the
last "significant" digits of the
corresponding Purchase Order
Mark the check box on the left
hand side of column Product.
Choose button Create Delivery.

Note the ID of the Inbound
Delivery and of the ASN from
the lower part of the screen, in
the Existing Deliveries area.
2.3.3 Process Goods Receipt

The warehouse operators at the inbound staging area are equipped with:
- an RF device
- a roll of pre-printed and barcoded HU labels
They are responsible for labeling and then posting goods receipt and creating subsequent putaway warehouse tasks in the system.
For our item, EWMS4-01, the Handling Unit with 8 CAR (= 1 PAL = 48 PC), will be put away in the storage type Y011, High Rack
Pallet Buffer.
55
Welcome1.
Open Log On to RF
Environment app.
Enter Data for RFUI:

Whse No: 1710
Resource: YREC-1
DefPresDvc: YE00
Choose Enter.
Choose the Menu for Goods

Receipt:
03 Inbound Processes
04 Receiving of Handling Units
04 Rec. HU by ASN
56
Enter the ASN number from the
previous step and choose Enter
twice.
Press F2 NewHU
Enter Goods Receipt Data for

the 8 CAR of EWMS4-01:
Prod.: 9783836214230
Press the Enter button after you
have entered the EAN before
you enter the other fields (a real
mobile device would do this
automatically).
ActQty: 8
UoM: CAR
Choose F1 Next
Note:
Alternatively, you can enter the
product: EWMS4-01 instead of
the EAN.
57
Enter the packaging material:
New P.Mat.: EWMS4-PAL00
Choose Enter.
Note the HU ID (SSCC

numbering) created.
Choose Enter.
Post Goods Receipt:

Choose F2 PGr.
Create Warehouse Task:

Choose F3 CrWT.
58
Press F7 four times to go back.
Press F1 Logoff.
Press F1 Save.
2.3.4 Move Pallets from Staging Area to Handover Point

Before pallets are finally put away to the Narrow Aisle High Rack Storage, an operator first has to move them to the handover point
(a handover point is an interim storage type physically located adjacent to or attached to the High Rack Storage).
The operator confirms the putaway warehouse tasks using the Radio Frequency environment. You use either a Queue or a Handling
Unit number to search for the putaway warehouse task.

Welcome1.
Click on Log On to RF
Environment app.
59
Whse No: 1710
Resource: YLLTR-1
DefPresDvc: YE00
Choose Enter.
Choose:
01 System Guided
02 System Guided by Queue
In the Queue field,

enter: YI-910-001
Choose Enter.
60
Enter the HU ID from the
previous step:
HU: 12345678#######
Choose Enter.
Confirm the destination bin field

by entering the same string of
numbers as the one you see on
the third group of the DstBin
field: 001.##.##
The confirmation data is
entered on the last cell of the
DstBin field and it has the same
values as the value on the
previous cell.
Choose Enter.
After you have processed the

HU, use function key F7 to go
back to previous screens.
Choose F1 Logoff.
Choose F1 Save.
61
2.3.5 Putaway of Products from the Handover Point to the High Rack
Pallet Buffer
The HUs are situated at the handover points of the different aisles. An operator (using a high-level truck) picks up the HUs at the
handover point and moves them to their destination bins in the upper level of the pallet rack.

Welcome1.
Click on Log On to RF
Environment app.
Whse No: 1710
Resource: YHLTR01-1
DefPresDvc: YE00
Choose Enter.
62
Choose:
03 Inbound Processes
03 Putaway
01 Putaway by HU
Enter the corresponding <HU

number> in the HU field.
Choose Enter.
If you don’t get the message

Warehouse order#######
not intended, you can skip this
step. In case the message is
displayed, follow these steps:
- Press F7
- Press F1 Logoff
- Press F1 Save
Start from the beginning of this
section using the following data
for the RFUI login:
Whse No: 1710
Resource: YHLTR02-1
DefPresDvc: YE00
Choose Enter.
63
Verify the Dst.Bin (Destination
Bin): 011.##.##.##
The confirmation data is
entered on the last cell of the
DstBin field and it has the same
values as the value on the
previous cell.
Choose Enter.
Logout by pressing F7
Press F1 Logoff
Press F1 Save
64
2.3.6 Create Supplier Invoice with PO/GR relation

The purpose of this activity is to create the supplier invoice with reference to the purchase order.

Welcome1.
Click on the Create Supplier

Invoice app.
Enter General Data:

Transaction: Invoice
Company Code: 1710
Gross Invoice Amount : XXX
Currency: USD
Invoice Date: <Today>
Posting Date: <Today>
Invoicing party: EWM17-SU01
Enter Purchase Order

Reference:
References Document
Category: Purchase
Order/Scheduling
agreement
Purchase Order: xxx
Choose the Create Invoice
Items button.
65
Check the selection of the
Purchase Order Items.
Confirm the warning messages.
Tax Code : I0
Check the invoice Balance.
Choose the Post button.
2.3.7 Check Inbound Delivery

Note upfront:
For this step to work, you need to ensure that the RFC destination S4HCLNT100 is working as the synchronization from EWM back
into the ERP inbound delivery processing uses this RFC destination. Since in the initial delivery state of the appliance, this
connection might not be configured properly, please check the following:
In the SAP GUI (BPINST/Welcome1, client 100), go to TCode SM59  ABAP Connections  double-click on entry S4HCLNT100 
click on Connection Test.
If the test is successful, you’re good to go.
If you receive a connection error, click the Display <-> Change icon. In the text field Target Host , replace the entry saphost with
the entry vhcals4hci. Click on Save (and confirm the Unicode pop-up), click on Connection Test to make sure that the connection
is working now.
User: S4H_MM
Password: Welcome1
In this step, you check the effect of the EWM processing on the inbound deliveries.
66
Open the Display Inbound
Delivery app.
On the Display Inbound Delivery

screen, choose F4 (Matchcode
Search).
In the Delivery (1) dialog box,
choose
External delivery number of
vendor: ASN-45-####
Choose Find
Choose Continue
On the Inbound Delivery

######## Display: Overview
screen, go to the Status
Overview tab page.
Check that the Total goods
movement status is set to C-
Completely (green background
color) for the Overall Status as
well as for the Delivery Item
Status
67
2.4 Demo Story 3 - Order to Cash with Extended Warehouse
Management (EWM) Outbound Processing
This scenario describes the standard Order to Cash document flow, which is also integrated with the Basic EWM processing for the
outbound activities.
The Order to Cash with EWM Outbound Processing demo story is a continuation of the Procure to Pay with EWM Inbound
Processing demo story. The Procure to Pay scenario documents how the EWMS4-01 product is procured and stored in the
warehouse while the Order to Cash scenario documents how customer EWM17-CU01 orders the EWMS4-01 product and how the
goods are being shipped from the warehouse and finally billed.
2.4.1 Create Sales Order

In this step, a sales order is created that is the basis for all subsequent shipping activities. The customer EWM17-CU01 is ordering a
quantity of 8 CAR of the EWMS4-01 material, which is the equivalent of 48 PC or 1, PAL.
As a prerequisite of the order creation step, make sure to procure the EWMS4-01 material first, as described in the Procure to Pay
with EWM Inbound Processing demo story.

Open the Fiori
with user S4H_SD,
password Welcome1.
Navigate to the My
the Manage Sales
Orders app.
A new browser
Order button.
In the Create Sales

Document screen,
make the following
manually):
 Order Type: OR
 Sales
Organization:
1710
 Distribution
Chanel: 10
 Division: 00
Click Continue.
68
make the following
manually):
 Sold-To Party:
EWM17-CU01
 Customer
Reference: a PO
number for
e.g.
In the Item screen,

make the following
entries:
 Material: EWMS4-
01
 Order Quantity: 8
 Un: CAR
Click Enter.
Click Save.
A pop up message
shows the number of
the created order.
2.4.2 Delivery
In this step, an outbound delivery document is being created.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Outbound Deliveries
group and click the
Create Outbound
Deliveries app.
Make the following
entries:
 Planned Creation
Date: Today and
Tomorrow
 Sales Document:
the sales
document
previously
created
Click Go.
Select the line item.
Click Create Deliveries.
69
Click Display Log.
Navigate to the
Deliveries tab and
check the delivery
document that was
recorded.
Navigate to the
Outbound Delivery
click the Display
Outbound Delivery
app.
Make the following

entry:
 Outbound
Delivery:
outbound
delivery
document
number
Press Enter.
Go to the All Items

section, select the line
item and click Item
Details button.
Click the Picking tab

and check the delivery
quantities.
2.4.3 Create Warehouse Tasks Manually

In this step the warehouse task for the EWM processing is being created by using the Run Outbound Process –Deliveries app.
70
Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –Outbound
group and click the
Run Outbound Process
Deliveries app.
Make the following
entry:
 Route Depart.
Date: <from
current day
until the day
next to the
current date>
Click Go.
Select the
corresponding
Outbound Delivery
Order and click Create
Tasks.
Make a note of the

Outbound Deliveries
Order Number, the
Warehouse Door and
the Route.
2.4.4 Check Warehouse Order

The Warehouse Monitor app provides a wide range of reports, which allow a complete monitoring of the EWM activities. In these
steps, the details of the outbound delivery order are being checked.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
click the Warehouse
Monitor app.
71
Click the Default
Values in the upper left
side of the screen.
Make the following

entries:
 Warehouse
Number: 1710
 Monitor: YE01
Click Execute.
In the hierarchy from

the left screen area,
choose Outbound >
Documents >
Outbound Delivery
Order > A dialog box
appears.
Make the following
entry:
 Outb. Delivery
Order: the
document ID
Click Execute.
Select the line item and

click the Warehouse
Order button.
Make a note of the

Warehouse Order
number and the
Queues ID.
2.4.5 Pick Warehouse Order

This step documents the EWM-related picking activities for the delivered goods. A resource with an ID similar to YHLTR0#-1 has to
be selected depending on the aisle where the source bin is located. The number 01 or 02 in the resource ID indicates the aisle in
which the resource is operating. The aisle is also reflected in the RF queues ID checked in the previous step.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
Execution group and
click the Log On to RF
Environment app.
72
Make the following
entries:
 Whse No: 1710
 Resource:
YHLTR01-1(along
with Queue YO-
N01-001) or
YHLTR02-1(along
with Queue YO-
N02-001)
 DefPresDvc: YE00
Click Enter.
Choose > 01 System

Guided.
Choose 02 System
Guided by Queue.
Make the following

entry:
 Queue: YO-N01-
001 or YO-N02-
001.The one
found in the
Warehouse
Monitor report.
Press Enter.
Click F4 Next.
73
Check that the DestHU
has a proposed value.
If that is not the case
go back one step by
pressing the F7 key
and click F2 Handl.
Once the DestHU field
has a value, make the
following entry:
 SBin: copy the
grey out
field and
paste it in
the editable
field.
Press Enter.
Make the following

entry:
 AQTy: copy the
grey out
field and
paste it in
the editable
field.
Press Enter.
Make the following

entry:
 DstBin: copy the
grey out
field and
paste it in
the editable
field.
Press Enter.
Make sure to logoff the

RFUI:
 Use function key
F7 to go back to
previous screens.
 Choose F1 Logoff.
Choose F1 Save.
Open the Fiori

Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
74
click the Warehouse
Monitor app.
choose Outbound >
Documents >
Outbound Delivery
appears.
Make the following
entry:
 Outb. Delivery
Order: the
document ID
Click Execute.
In the Outbound
Delivery Order area,
select the line item and
click the Handling Unit
button.
Make a note of the HU.
In the Outbound
click the Warehouse
Task button.
Select the line that has

the Status field empty.
Click the More
Methods button and
choose Confirm WT in
Background.
A success message
pops up.
75
All tasks are confirmed
now.
2.4.6 Close the Shipping Handling Units (HU)

Closing the ship HU at the Packing Work Center means to document that they can be prepared for shipping. With closing the HU,
you initiate the printing of the Shipping HU labels and the HU content list.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
Execution group and
Environment app.
Make the following
entries:
 Whse No: 1710
 Resource:
YPACK-1
Click Enter.
Choose 04 Outbound
Process.
Choose 02 Packing.
76
Scroll down to the
second screen by
pressing the down
arrow button.
Choose 08 Maintain
HU.
Make the following

entries:
 Work Ctr.: Y831
Click Enter.
Make the following

entries:
 SHU: source HU
Click Enter.
Click F2 Close.
A completion message
is displayed.

RFUI:
F7 to go back to
previous screens.
Choose F1 Save.
77
2.4.7 Stage Shipping Handling Units (HU)
In this step, the HU is moved from the Packing Work Center to the Outbound Staging Area.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
click the Warehouse
Monitor app.
choose Outbound >
Documents >
Outbound Delivery
appears.
Make the following
entry:
 Outb. Delivery
Order: the
document ID
Click Execute.
In the Outbound
click the Warehouse
Task button.
Make a note of the

Queue ID that belongs
to the uncompleted
Warehouse Order.
In the Outbound
click the Handling Unit
button. Make a note of
the Storage Bin.
Navigate to the
Warehouse –
Execution group and
Environment app.
78
Make the following
entries:
 Whse No: 1710
 Resource:
YLLTR-1
Click Enter.
Choose 01 System
guided.
Choose 02 System-
guided By Queue.
Make the following

entry:
 Queue: YO-831-
920
Press Enter.
Make the following

entry:
 HU: HU’s ID
Press Enter.
Make the following

entry:
grey out
field and
paste it in
the editable
field
Press Enter.

RFUI:
F7 to go back to
previous screens.
Choose F1 Save.
79
In the Warehouse
Monitor report all
Warehouse Task
belonging to the
corresponding
Outbound Delivery
Order will have the
status C, confirmed.
2.4.8 Display Loading Overview

In this step the shipping clerk can get an overview of all HUs that are ready for loading in the Loading Workload by Route warehouse
monitor node.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
click the Warehouse
Monitor app.
choose Outbound >
Processes > Loading >
Loading Workload per
Route.
the dialog box, enter:
 Route: TR0001
 Route Departure
Date: <from
current date
to next day
after the
current date>
Choose Execute.
In the Loading
Workload per Rout
area, select the line
item and press the
Handling Unit button.
Check the Loading

Workload per HU
details.
80
2.4.9 Load Shipping HU

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
Execution group and
Environment app.
Make the following
entries:
 Whse No: 1710
 Resource:
YLLTR-1
Click Enter.
Choose 04 Outbound
Processes.
Choose 03 Loading.
Choose 05 Loading by
HU.
Make the following

entry:
 HU: HU’s ID
Click Enter.
81
Make the following
entry:
grey out
field and
paste it in
the editable
field
Click Enter.

RFUI:
F7 to go back to
previous screens.
Choose F1 Save.
2.4.10 Post Goods Issue

In this step the goods issue movement is posted referencing the outbound delivery order.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Warehouse –
Outbound group and
click the Run Outbound
Process Deliveries app.
Make the following
entry:
 Route Depart.
Date: <from
current date
to the day
next after
the current
date>
Click Go.
Select the
corresponding
Outbound Delivery
Order line item. Click
the Goods Issue
button.
A confirmation
82
2.4.11 Check Outbound Delivery Status

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Navigate to the
Outbound Delivery
click the Display
Outbound Delivery
app.
Make the following

entry:
 Outbound
Delivery:
delivery
number
Press Enter.
Navigate to the Status

Overview tab.
The Overall Goods
Movement status is
Complete.
Only Billing step is
missing.
2.4.12 Billing
In this step, a billing document is posted and the print preview of the document is issued. In this appliance, the printing for the
billing documents uses the New Output Management for S4HANA.

Open the Fiori
Launchpad with user
S4H_SD, password
Welcome1.
Billing Document
group and click the
Create Billing
Documents app.
Click the Billing
Settings button.
83
Switch ON all billing
settings and click OK.
Select the delivery

document line item.
Click Create.

Documents pop up
make the following
entries:
Invoice
 Billing Date:
<current
date>
Click OK.
In the header screen of

the Invoice document,
click the Output Items
tab.
Click the Preview
button.
The pdf form using the

new Output
Management for
S4Hana is displayed in
a new tab/window.
84
2.5 Demo Story 4 - Cash Daily Operations Extended
This scenario walks you through a detailed scenario where Bank transfers, Cash pooling, approval workflow and specific Cash
reports are exemplified.
Cash daily operation provides a consistent view for actual cash position and short-term cash forecast. Rich analysis dimensions
provide better insights for the cash manager. Good drill-down features are provided for line items and detailed transactions.
2.5.1 Preliminary Steps: Define Payment Signatories for Bank Account

In this step, you make sure the payment signatories have been maintained for two existing bank accounts:
- Bank Account 33333, bank key 011000390, country US; House Bank USBK1, Account ID USAC1
- Bank Account 25800611, bank key 820800001, country US; House Bank USBK1, Account ID USAC2

Open the Fiori
Launchpad with
user BPINST,
password
Welcome1.
Click the Manage

Bank Accounts
Overview and
Maintenance app.
Search for Bank

Account 33333,
bank key
011000390,
country US.
Click on the bank
account number.
Choose Payment
Signatories tab and
verify the users
assigned to
Signatory groups.
The users defined
here will do the
payment approval
process.
Search for Bank

Account
25800611, bank
key 820800001,
country US and
click on bank
account number.
Choose Payment
Signatories tab and
verify the users
assigned to
Signatory groups,
who will do the
approval process.
85
2.5.2 Bank Transfer Actions
This section describes the steps to make bank transfer between two house bank accounts. For example, there is a deficit of a
current bank account; the cash manager makes a decision to make a bank transfer from another bank account.
2.5.2.1 Initiate Bank Transfer

with user BPINST,
password Welcome1.
Click the Make Bank

Transfers app.
Make the following entry:

 From: 25800611
 To: 33333
 Amount: 200 USD
 Payment Method:
1 bank
Transfer
Press Enter.
Click on each bank account

and select Make Bank
Transfer in the lower right
corner of the screen.
Insert a Note and click on

Submit.
Bank Transfer is initiated

successfully. Click OK.
2.5.2.2 Track Bank Transfer
In this step, the cash manager or bank accountant can trace the status of a specific bank transfer.
For the bank transfer created earlier, the status should be “New”, as batch waits for the first approval.
86
with user BPINST, password
Welcome1.
Click the Track Bank

Transfers app.
Choose the New tab. The

bank transfer you made
previously is now displayed
here.
To check the detailed

information, select the bank
transfer. Click on Payment
details.
The Check Cash Flow Items

app will open and the
payment details will be
displayed.
Click on Settings button and

change the layout.
Select Batch Item Status

and Batch Status and click
OK.
Scroll to the right. For the

payment document created
previously, its status should
be Payment Batch Created.
2.5.2.3 Approve Bank Transfer
The creation of the Cross-Payment run in bank communication management (BCM Batch) is done automatically after the payment
is initiated via Bank Transfer.
87
In the S/4HANA system, a BCM batch should be approved by two approvers according to the approval pattern in preconfiguration.
After the approval process is done, the payment medium is created automatically.
2.5.2.3.1 Approval by First Approver

with user S4H_FIN,
password Welcome1.
Click on Approve Bank

Payments app.
Choose the For Review tab.
Select the payment batch
for approval.
Choose Submit.
On the dialog box Confirm,

enter a Note and click OK.
The first approval step is

executed. To review it,
choose the Processed tab.
2.5.2.3.2 Approval by Second Approver

with user S4H_CASH,
password Welcome1.
Open Approve Bank

Payments app.
88
Choose the For Review
tab.
for approval.
Review to ensure if the
batches are correct.
Choose Approve.
On the dialog box Approve

Batch, enter a Note and
click OK.
The second approval step

is executed. To review it,
2.5.2.4 Download File
After the BCM batch is approved, the payment medium file will be created and it can be downloaded locally to be send to bank.

with user BPINST,
password Welcome1.
Click the Administrate

Data Medium app.
89
On the Data Medium
Administration screen,
enter the following entries
and choose Overview (F8).
Paying company code:
1710
Run Date: <current
date>
On the next screen, mark

the right payment run
identification for which
you need to download
payment medium file, and
select Choose (F2).
On the Data Medium

Attributes screen, you can
see the data Medium
details, eg. Reference
number.
Choose
Download…(Shift+F6).
On the dialog box File

Name, enter the path and
file name in field File Name
(for example: Z:\ACH),
and choose Download.
90
An information dialog will
appear. Click OK.
File was saved

successfully in the
indicated location.
In the upper section of the

screen, go to More  GUI
Actions and Settings 
WebGUI File Browser
Select the file and click on

Export to native file
system button.
File is downloaded locally

on your computer. Open
the file to see the payment
details. In the 1610
appliance this is not
integrated with a bank, but
in a SAP customer system,
this XML file could be
communicated to a bank
using SAP FSN or
whatever integration
method has been
configured.
2.5.2.5 Check Status – Check Cash Flow Items
In this step, the cash manager, bank accountant or AR/AP accountants can check the status of each single outgoing payment that
is merged in a BCM batch.
91
with user S4H_CASH,
password Welcome1.
Click on Check Cash Flow

Items tile.
Enter the <current

date>, Company Code
1710 and click Go.
Click on Settings
button and change the
layout.
Select Batch Item Status

and Batch Status and click
OK.
Scroll to the right. For the

payment document
created previously, its
status should be Payment
Medium Created. This
means the Batch
successfully completed
the approval process and
the payment medium is
created.
2.5.2.6 Cash Position Details
In the Cash Position details app, consistent views for actual cash position and short-term cash forecast are provided. Furthermore,
rich analysis dimensions provide the Cash Manager with better insight and a good drill down feature to access detailed
transactions.

Open the Fiori
Launchpad with user
S4H_CASH, password
Welcome1.
Click the Cash Position
Details app.
Enter the following
search criteria:
Value date: <current
date>
Company code: 1710
Bank country: US
and choose Go.
92
Expand the hierarchy
until you reach the
lowest level.
2.5.3 Cash Pooling
2.5.3.1 Create Bank Account Group
In this step, a cash pool based on a bank account group structure is created and cash concentration is used to centrally manage
your cash. In the 1610 appliance, the Bank Account Group and Cash Pool is already created for your company code, so proceed to
go to step 2.5.3.3 – Run Cash Concentration. However, if the below steps prior to 2.5.3.3 demonstrate how to create these.

with user BPINST, password
Welcome1.
Open the Manage Bank

Accounts app.
Choose Create, located near

Bank Account Group Views.
Enter the Bank Account

Group Name: eg. Cash
Pool 1710.
If you would like it to be
visible to other users (Cash
Manager – S4H_CASH),
choose Visible to Defined
Users, and then choose
Manage Visibility.
93
On the dialog box Manage
Visibility, choose New, and
enter in field Username
S4H_CASH and choose OK.
Choose New Node in section

Bank Account Group. On the
dialog box Node Name,
enter 1710 and choose OK.
In section All Available Bank

Accounts, choose account
33333 and 25800611.
In section Bank Account
Group select Cocd 1710 you
just created in previous
step, then choose Add to
Bank Account Group.
Choose Save.
94
2.5.3.2 Create Cash Pool

Open the Fiori
Launchpad with user
BPINST, password
Welcome1.

Accounts app.
Choose the bank

account group Cash
Pool 1710.
Choose Cash Pool 
Create Cash Pool.
On the Create Cash

Pool screen, enter the
following data:
Cash Pool ID: CP 1710
Cash Pool Name: Cash
Pool 1710
Cash Pool Usage: U
Org. Unit ID: 50000050
House Bank: USBK1
Account ID: USAC1
Pymt Method: 1
Select checkbox for

Acct No. 25800611
(account ID USAC2 in
House Bank USBK2)
Planned Bal.: For
example, 1000 USD
Minimum Amount: For
example, 500 USD
Payment Method (PM):
1
Choose Save
2.5.3.3 Run Cash Concentration
95
with user BPINST,
password Welcome1.

Accounts app.
Choose the Bank Account

Group Cash Pool 1710.
On the dialog box Cash
Pool, choose
Concentration.
Choose the Cash Pool

1710 and then choose OK.
Enter the amount you

want to transfer: eg. 500
USD and choose Create
Payment Request.
Payment request will be

created and a
confirmation message will
appear on the screen.
Click OK.
96
Scroll down in current
screen until you see
section Open Payment
Requests. Click on Refresh
button, so the newly
created payment will
appear on the screen.
Mark the payment request

just created (no.7), and
then choose Release.
Payment request was

released. Click Continue.
In the section Open

Payment Requests,
choose Refresh.
After the release, the
Check-box Rel.f.paym is
selected.
In the section Open

Payment Requests,
choose the payment
request just released and
then choose Pay.
A confirmation message
appears on the screen.
2.5.3.4 Approve Cash Concentration
2.5.3.4.1 Approval by First Approver
97
with user S4H_FIN,
password Welcome1.
Open Approve Bank

Payments app.
Choose the For Review tab.
for approval.
Choose Submit.
On the dialog box Confirm,

enter a Note and click OK.
The first approval step is

executed. To review it,
2.5.3.4.2 Approval by Second Approver
98
with user S4H_CASH
password Welcome1.
Click on Approve Bank

Payments app.
Choose the For Review

tab.
for approval.
Review to ensure if the
batches are correct.
Choose Approve.
On the dialog box Approve

Batch, enter a Note and
click OK.
The second approval step

is executed. To review it,
2.5.3.5 Check Cash Position
99
Open the Fiori
Launchpad with user
S4H_CASH password
Welcome1.
Open Cash Position
Details app.
Enter the following
search criteria:
Value date: <current
date>
Company code: 1710
and choose Go.
Expand the hierarchy

until you reach the
lowest level.
2.5.3.6 Download File

Open the Fiori
Launchpad with user
BPINST, password
Welcome1.
Click Administrate Data

Medium app.
On the Data Medium
Administration screen,
enter the following
entries and choose
Overview (F8).
Paying company code:
1710
Run Date: <current
date>
100
On the next screen, mark
the right payment run
identification for which
you need to download
payment medium file,
and select Choose (F2).
The Data Medium

Attributes screen is now
displayed.
Choose
Download…(Shift+F6).
On the dialog box File

Name, enter the path
and file name in field File
Name and choose
Download.
101
An information dialog
will appear.
File was saved

successfully in the
location indicated.
Go to More  GUI
Actions and Settings 
WebGUI File Browser
Select the file and click

Export to native file
system.
The file is downloaded

locally on your
computer.
Open the file to see the

payment details.
102
2.6 Demo Story 5 - Plan to Product
In this demo scenario, the planning and production of a batch managed and serial numbered finished good will be produced using
several raw materials and semi-finished goods. The material descriptions are generic to convey the nature of the material (e.g.,
QM/Batch/Serial# managed, FIFO, MRP types such as PD in this demo story, and more). The finished good that is produced could
be an item such as a computer, medical equipment, bicycle or such.
2.6.1 Preliminary Step - Create Initial Material Stock

In a real business case, the materials are usually purchased from external vendors; in that case, that process is covered by the
standard purchasing or subcontracting processes. For the purpose of this test, we post initial stock directly to the storage
locations.

with user S4H_MM,
password Welcome1.
Click the Post Goods

Movement app.
Choose Goods Receipt-

Other
Movement type: 561
Specify the Materials
according to the list
provided below the screen
shot.
Specify Quantity: 100 PC
Plant: 1710
Storage Location: 171B
Materials that need initial RM12, SG22, RM16, RM17, RM18, RM120, RM122, RM128, SG23, RM13, RM14, SG25,
stock postings: RM124, RM20, RM27
Use the Check button. The

following message will be
displayed.
Confirm the message with
Enter.
103
Post the transactions by
using the Post button on
the lower left corner.
A confirmation message
will be displayed.
2.6.2 Preliminary Step – Check stock levels

It is recommended to check the stock for SG124. You can check this using the app Check Material Coverage available for the
Production Planner role. If there is sufficient stock, just remove some stock, or no plan orders will be generated later on. After
removing some stock, run the test again.
The stock for FG126 should also be checked according to the following procedure;

Open the Fiori
Launchpad with
user S4H_MM,
password
Welcome1.
Open the Check

Material
Coverage app.
104
Complete the
following details
on the pop-up
window:
Material: FG126
Plant: 1710
Press OK.
Note the total

value of the
existing stock
and of the
existing
production
orders.
2.6.3 Create Planned Independent Requirements

Open the Fiori
Launchpad with
user S4H_MM,
password
Welcome1.
Open the Manage

PIRs app.
105
On the Manage
PIRs screen,
enter material
FG126 as a filter.
Click Go
Click the material

item to display
the Draft PIRs
field.
Add a quantity
that exceeds by
100 the total
quantity of stock
plus production
orders recorded
at the end of the
‘check stock
levels’
preparatory
activity.
Click Save Draft

(bottom right).
Click Release
PIRs (bottom
right).
If the Delete PIRs

in Past is
displayed,
choose Yes.
2.6.4 Material Requirements Planning at Plant Level

Welcome1.
Click the Schedule MRP Runs

app.
106
Choose New (middle right
section).
Make the following entries:

Job Template: Material
Requirement Planning
(MRP)
Job Name: MRP for FG126
Start Schedule Immediately: X
Plant: 1710
Material: FG126
BOM Components: X
Planning Mode: 1
Choose Add more scheduling

options.
In the Scheduling Information

screen, make the following
entries:
Start Schedule Immediately: X
Recurrence: Make sure it is
unselected.
Choose OK.
Choose the Schedule button.
107
To check the status of the job
you created, choose Go at the
top right section of the screen.
Choose Go again, until the
status of all the job has changed
to Finished.
2.6.5 Create Production Order for Subassembly

Welcome1.
Click the Monitor Material

Coverage – Net / Individual
segments app.

Material: SG124 (click on the
matchcode and select the
product from the list)
Choose Go
Mark the checkbox for the
material, and choose Manage
Materials.
Click on the PldOrd XXX .
108
Choose the Change Order
button.
Choose Change Order on the

PldOrd dialog box, choose
Convert to Production Order,
and confirm with OK.
The Production Order will be
created.
Note down the Production

Order number.
2.6.6 Release Production Order for Parts Production

Welcome1.
Open the Change Production

Order segments app.
109
Enter the Production order
number and choose Continue.
Choose Release Order .
A confirmation message will be

displayed.
Save the changes.
2.6.7 Confirm Production for Semi Finished Product

Welcome1.
Click the Confirm Production

Order Operation app.
110
Order: Order number
Operation: 10
Confirm your entries with Enter.
Choose Actual Data

Confirm. type: Final
confirmation
Change the Machine time to a

new value: 11
Choose Goods Movements.
Choose Post to save.

displayed.
Repeat the steps above for operation number 020 and save your entries, without changing the machine time.
2.6.8 Post Goods Receipt for Production Order

Welcome1.
Open the Post Goods

Movement app.
111
On the top left frame, enter
Goods Receipt and Order.
Order : <Production order
number>
GR goods receipt: 101
Document date: default
Posting date: default
On the Where tab, choose the

storage location: 171A.
Set Item OK indicator.
Choose Check.
Choose Post.
2.6.9 Create Production Order for Final Assembly

Welcome1.
Open the Monitor Material

Coverage – Net / Individual
segments app.
112
Material: FG126 (click on the
matchcode and select the
product from the list)
Choose Go.
Mark the checkbox for the
material, and choose Manage
Materials.
Click on the PldOrd XXX.
Choose the Change Order

button.
Choose Change Order on the

PldOrd dialog box, choose
Convert to Production Order,
and confirm with OK.
The Production Order will be
created.
113
Note down the Production
Order from the bottom of the
page.
2.6.10 Release Finished Goods Orders

Welcome1.

Order app.
Enter the Production order

number and choose Continue.
Choose Release Order.

displayed.
114
Save the changes.
2.6.11 Pick Components

The released production order is now ready for picking. Only those materials that are not in the service stock at the assembly aisle
are to be picked. For picking, the warehouse manager selects the specific picking list that can be called up directly with the
production order number. The warehouse manager has a series of further selection options to allow for optimal worklist selection.

Welcome1.

Order segments app.
Make the following entries.

Profile: 000002
Production Order: <Your
Production Order number>
Choose Execute.
Select all the reservations by

clicking on each line while
holding the Control key and
choose Picking.
115
Some materials are
management by batch, for
example: RM122.
Select the RM122 line item and
choose Batch Determination.
Choose Copy.
Modify the quantity for one

item. For example, choose 110
in the Quantity field for RM120.
Select all the lines.
Choose Post to post the goods

movements.
2.6.12 Confirm Production for Semi Finished Product
116
Welcome1.
Click the Confirm Production

Order Operation app.

Order: <Order number>
Operation: 10
Confirm your entries with Enter.
Choose Actual Data

Confirm. type: Final
confirmation
Change the Machine time to a

new value: 11
Save your entries.
In case the Execute trigger

point function message is
displayed, choose No.

displayed.
Repeat the steps above for operation number 020 to 0040 and save your entries, without changing the machine time.
2.6.13 Post Goods Receipt for Production Order
117
Welcome1.
Click the Post Goods Movement

app.
On the top left frame, enter

Goods Receipt and
Order: <Production order
number>
GR goods receipt: 101
Document date: default
Posting date: default
On the Where tab, choose the
storage location: 171A.
Set Item OK indicator.
Choose Check.
Choose Post.
2.6.14 Actual Overhead Calculation Production Order

In this activity, you post the actual overhead to production orders,

user S4H_CO, password
Welcome1.
Access the SAP Fiori App: Run

Overhead Calculation -
Production Orders
118
Plant: 1710
With Production Order: Select
With Process Order: Select
With Product Cost Collectors:
Select
With QM Orders: Select
With Order for
Projects/Networks: empty
With Orders for Cost Objects:
empty
Combined Orders Only: empty
Parameters
Period: 12
Fiscal Year: 2016
Processing Options
Background Processing:
Deselect
Test Run: Deselect
Detail List: Select
Dialog Display: Deselect
Check the result.
119
2.6.15 Calculate Work in Process (WIP)
In this activity, you calculate work in progress (WIP). This step is executed in the same manner for partially delivered production
orders as for (totally) delivered production orders.

Welcome1.
Access the SAP Fiori App:

Calculate Work in Process-
Orders Collective.
WIP to Period: <current
period> eg. 12
Fiscal Year: <current year>
for example 2016
RA version: 0
Plant: 1710
Deselect
(WIP/Results Analysis)
Processing Options:
Deselect
Test Run: Deselect
Log Information messages:
Deselect
Output Options:
Output Object List: Select
Display Orders with Errors:
Select
Hide Orders for which WIP=0:
Displayed Currency: Comp.
Code Cur.
Layout:
Summary
Including Combined Orders:
Select
Combined Orders Only:
No Combined Orders:
2.6.16 Production Variance Calculation

In this activity, you calculate production and process order variances.
120
Welcome1.
Run Variance Calculation
Orders-By Period
Plant: 1710
Select
Parameters
Period: <current period>
Fiscal Year: <current year>
All Target Cost Version: Select
Selected Target Cost version:
Processing Options
Deselect
Test Run: Deselect
Detail List: Select
2.6.17 Settle Variances

In this step, you settle the production variances to Financial Accounting and Profitability Analysis.

Welcome1.

Settle Orders Optimized
Plant: 1710
Select
With QM Orders: Select
With Order for
Projects/Networks:
With Orders for Cost Objects:
Deselect
Combined Orders Only:
Parameters
Settlement Period: 12
Posting Period: No entry
Fiscal Year: 12
Processing type: Automatic
121
Processing Options
Deselect
Test Run: Deselect
Detail List: Select
Check Trans. Data: Deselect
2.6.18 Analyze Variances

SAP system offers several reports for analyzing production variances. We recommend using the summarization hierarchy and the
line item report for the single order

Welcome1.

Analyze Summarized Hierarchy

CO Summarization
Report Object:
Hierarchy: YBMF0001
Subhierarchy: 17101710YBM1
Time Frame:
Limited Period:
From Period: 12
To Period: 12
Report Parameters:
Plan Version: 0
122
2.6.19 Production Cost Analysis

In this step you can analyze production/process order target vs actual cost.

Welcome1.

Production Cost Analysis

Plant: 1710
Material: FG126
Target Cost version: 0
Period From:
Period to:
Company code: 1710
123
2.7 Demo Story 6 – Investment
This scenario demonstrates an end-to-end process flow from creation, planning, capitalization and reporting of an investment
project, which is an asset under construction. Assets under Construction (AuC) are a special form of tangible assets. They are
usually displayed as a separate balance sheet item, requiring separate account determination and their own asset classes. During
the construction phase of an asset, all actual postings are assigned to the AuC. Once the asset is completed, a transfer is made to
the final fixed asset.
Investment orders are used to capture the costs of AuC during the construction phase. Once the AuC is completed, the final asset
is created in the appropriate asset class, and the investment order is set to complete. The next settlement transfers the AuC asset
value to the completed asset.
2.7.1 Creating Investment Order

This activity creates an investment order.

Welcome1.
Search for the app Manage

Internal Orders or as an
alternative, navigate to the
Controlling – Master Data group
and click the app.
A new browser tab/screen will

open (allow pop-ups in browser if
necessary) from where you can
Create/Copy/Edit an Investment
Order.
Click Create
A new browser tab/screen
displays: Internal Order : New
 Controlling Area: A000
 Order Type: Y6SC
Choose Continue and make the

following entries:
 Description (untitled, next to
order number): *
 Currency: USD
 Company Code: 1710
 Functional Area: YB20
 Profit Center: YB110
124
 Cost Center Responsible:
17101301
You can also use another

Functional Area, Cost Center or
Profit Center but you must make
sure that you use a consistent
combination. You should use the
same assignment of Cost Center
/ Profit Center for the asset and
the investment order.
Scroll down up to the

Investments Section and make
entries for :
 Investment Profile: 000001
Save Investment Order.
Write down the number of the

order after saving it.
2.7.2 Plan Internal Order

In this process, the planning via spreadsheet can be done for internal orders by cost element. To execute this step, Microsoft Office
Analysis must be installed on your desktop.

Log into Microsoft Office Analysis
by:
 Open the Blank workbook
 Select the FILE
125
 Select Analysis tab

 Select Open Workbook
 Choose Open workbook
from the SAP NetWeaver
platform window,
 Select Client S4H

 Click Next
A login window will appear :
 Client: 100
 User: S4H _CO
Select OK
In the Open Document screen;
 In the Search enter *
 Select
 Select Internal Order
Planning on Periods
/ERP/SFIN_A11_WB01
 Select OK
In the Prompt window select:

 Fiscal Year: 2016
 Category: PLN
 Company Code:1710
 Internal Order Range: range
<[]>
 Internal Order Range: range
<100000 - 199999>
 G/L Hierarchy: YCOA
Select OK
126
 Order: 600060 created in

above
 G/L Account: ex: 65000500
 G/L Account Row - Period
6-12: ex: 10000 for
each period
Choose Recalculate.
Total plan for 2016 is calculated.

If there are LY actuals, the last
column shows the difference
from plan to LY actual.
 Internal Order: For

example 600060, the
one you are planning
 G/L Account: For
example, 65150000
 G/L Account Row - Period
1-12: For example,
100 for each period
Choose
The GL account is added to the
plan.
Choose
2.7.3 Copy Plan Data from BPC to ERP

In this step, Planned Data from Analysis Office can be transferred back to your ERP system

Log into Microsoft Office See step 2.7.2
Analysis
127
 User: S4H_CO
In Open Document:
 In the Search enter *
 Select
 Select Plan Data
Transfer for
Internal Orders -
/ERP/SFIN_A19_WB01
 Select OK
In the prompt window make the

following entries:
 Fiscal Year: For
example, 2016
 Posting Period : The one
you are planning
 Category: For example,
PLN
 Version : 0
 Internal Order : For
example, the one you
are planning 600060
Choose OK.
 Choose: Copy IBP to

ERP
Choose
128
2.7.4 Accounts Payable - Posting Invoice to Investment Order
In this step, you can enter a supplier invoice without reference to a purchase order. You will find the Create Supplier Invoice app in
Supplier Invoice Processing group.

user S4H_FIN, password
Welcome1.
Open the Create Supplier

Invoice app (search for it, use
the app groups or simply
navigate to it in the Fiori
Launchpad).
If the Data from Previous Entry

Exists screen displays, select
No.
Make the following entries in

the General Data:
 Invoice type : Invoice
 Company Code : 1710
 Gross Invoice Amount :
<Total invoice
amount including
tax>
 Currency: USD
 Invoice Date: <Your
posting date>
 Posting Date: <Your
posting date>
 Reference: <any>
 Invoicing Party: 17300001
In Header section, select G/L

ACCOUNT ITEMS
Press Add G/L account items
In the G/L Account Items

section, choose Enter:
 Debit/Credit: Debit
 G/L Account: for example,
65000500
 Amount: <Net invoice
amount>
NOTE: This excludes taxes
129
Press
The More Details section will
appear
 Tax Code : <input tax
code> for example,
I0 or I1
 Tax Jurisdiction : for
example CA0000000
NOTE: Cost Center dependent
 Order: For example
600060
NOTE: Tax session data will be

automatically updated/calculated
based on the above data.
Click in order to see if

data is ok
Click
Click
Invoice number will be
generated.
2.7.5 Monitoring Order Progress

This activity monitors the order progress. You will find the Analyze Production Order app in Controlling – Reporting group.

Welcome1.
Click the Analyze Production

Order app.
130
Make the following entries and
choose Execute:
 Order: <Your
investment order
created in previous
step>
 Time Frame: Cumulated
Select
The Target/Actual - Comparison
report is displayed
2.7.6 Asset under Construction Settlement (Collective Processing)

In contrast to assessment, you cannot perform settlement across fiscal year boundaries. The system automatically determines the
posting date from the posting period/fiscal year using the last day of the posting period. There are three processing types defined
for settlement:
 Automatic: The system selects all the distribution rules for a sender.
 Periodic: All distribution rules with settlement types PER and AuC are selected. PER rules are applied first. In investment
measures, this is followed by settlement to assets under construction.
 Partial capitalization: Use this processing type if you want to partially capitalize an investment measure, which is not yet
complete, that is, if you want to settle part of the overall cost to finished assets.
With this process step, a periodic settlement is executed. All costs collected on the investment order will be settled to the
automatically created AuC.
This activity monitors the order progress. You will find the Run Actual Settlement Internal Orders app in Controlling – Period End
Processing group.

Welcome1.
Open the Run Actual Settlement
Internal Orders app.
Select Selection Variant
a pop-up window will appear,

from where we select the
variant (if is created)
131
If is not created, select

Selection Variant to the right of
the selection variant field.
 Variant YBLMF_6SC
 Select Create
The Edit Variant screen

appears. Make the following
entries:
Variant <Your
description> YBLMF_6SC
 with selection of order
type Y6SC
 Company Code 1710
Select Attributes
Insert Description: <Your
description>
132
Select
The variant is saved
Run the Settlement Orders by:

 Selection variant
YBLMF_6SC
 Settlement period:
<Current period>
 Fiscal Year: <Current
fiscal year>
 Posting Period: <Current
period>
 Asset Value Date:
<Today's date>
 Processing Type: 1
Automatic
 Test Run: Selected For
the first run(check for
possible errors
 Detail List: Selected
Select Execute
Settlement execution status
will be displayed(check if we
have error message )
Click
A Detail List screen with settled
values will appear.
133
2.7.7 Creating Assets for Complete AuC Settlement
In this activity, you can create a new asset main data, which is necessary for AuC Settlement. You will find the Create Asset Master
Record app in Master Data group.

user S4H_FIN, password
Welcome1.
Open the Create Asset Master

Record app

and press Enter:
 Asset Class: 3210
 Number of similar
assets: 1
 Post-capitalization:
<Only required if
you want to use
this master record
to post a post-
capitalization>
Press Enter and the General tab

is displayed.
 Description: <Your
asset description>
 Capitalized on: <Your
capitalization date>
134
Choose the Time-dependent

 Cost Center: 17101301
Note: You should use the same

assignment of Cost Center for
the asset and the investment
order.
Choose the Deprec. Areas tab.

 Enter, check or adapt the
Depreciation Parameters
Select
The asset master record of
6000007-0 is created.
2.7.8 Maintaining Settlement Rule for Final Settlement

In this process step the settlement rules for the final settlement are maintained and the status of the investment order will be set to
technically completed, which allows the final settlement of the .
You will find the Manage Internal Orders in the Controlling - Master Data group.

Welcome1.
Open the Manage Internal

Orders app.
Make the following entries and

choose GO:
 Company Code : 1710
 Order Type: Y6SC
135
 In the Manage Internal

Orders list, select the
relevant order number,
600060
 Select Edit
The Internal Order main screen

appears.
Select Maintain Settlement

Rule.
Under the Distribution Rules,
section choose Insert.
A new ID002 Settlement rule

will be created.
ID 002 , make the following

entries:
 Category: Asset
 Settlement Receiver:
<Asset no. created
in previous step>
 %: <Portion of AUC
APC that can be
capitalized, e.g.
100>
 Settlement Type: Full
Settlement
136
Select Done.
The Internal Order screen
appears.
Choose Save.
2.7.9 Final Settlement of the Investment Order (Collective Processing)

The final settlement transfers the costs from the AuC asset to the completed asset and to the cost center as specified in the
settlement rules. After the final settlement, the balance of the investment order and of the AuC is zero.
You will find the Run Actual Settlement Internal Orders app in Controlling – Period End Processing group.

Welcome1.
Open the Run Actual Settlement

Internal Orders app.
 Selection Variant :
YBLMF_6SC
 Settlement period:
<Current period>
 Fiscal Year: <Current
fiscal year>
 Posting Period: <Current
period>
 Asset Value Date:
<Today's date>
 Processing Type: 4 Full
Settlement
 Test Run: Deselected
For the first run, flag this field
to check for possible errors.
 Detail List: Selected
137
Choose
Choose
Costs have been transferred
from the AuC asset to the
completed asset
2.7.10 Internal Orders Plan/Actuals

In this step, you can view internal orders using the Internal Orders Plan/Actual app, found in the Controlling – Reporting group.

Welcome1.
Open the Internal Orders

Plan/Actual app.
The Internal Orders –

Plan/Actuals screen displays
 Fiscal Year: 2016
 Category : <Your
selection>
138
Select
The Internal Orders report is
displayed.
2.7.11 My Spend
With this report, you can track the budget and spending status for your investment in an easy way.

Welcome1.
Click on the My Spend app.
Adjust the reporting period to

fiscal year 2016 (with the
default value ‘month-to-date’,
you won’t see sample data):
 Click on the Me icon
 Click on App Settings
 Choose Time Period 
Other Time Periods
 Year  Fiscal
Year 2016
 Click OK
On the My Spend App – screen,

select the following:
 Category: Project
 Type: Budget
139
Access the view for Budget/
Actual:
 Choose the Select
Icon
 View the results
including Budget and
Actual spend figures.
2.7.12 Completion of Investment Order

In this process step, the investment order is closed by changing its status to Closed.

Welcome1.
Open the Manage Internal
Orders app.
 Order Type : Y6SC
Select
 In the Manage Internal
Orders list, select the
relevant order number
600060
 Select Edit
140
In the Status section, choose

Change System Status.
Select Complete and then

Close.
System Status now is

Settlement rule
created, Closed
Select Save.
2.8 Demo Story 7 - Extensibility

Background information:
This scenario describes how to extend Fiori apps with custom fields that can be defined by customers and partners. The need for
additional fields will vary by customer or project, e.g. in case SAP does not deliver necessary customer-specific fields as part of the
standard product.
In this scenario, you will:
1. Remove & re-position existing standard fields in the ‘Product Master’ Fiori app
2. Add two custom fields (those are already part of the trial appliance) to this app to enable the maintenance of attributes
that are not covered in the SAP standard
141
3. Create a new custom field that can be added following the procedure described in step 2.
For more information on the Fiori extensibility, please see

https://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/1a93686c176845f0832a2a73221dd90b/1610%20000/en-
US/frameset.htm?d0d669bdb75a4762910524b30fc6fc32.html.
This page can also be reached via navigating to http://help.sap.com  Enterprise Management  SAP S/4HANA  SAP
S/4HANA 1610  General Functions for Key Users  Extensibility  Extensibility Scenarios  Creating Extension Items and
Transporting Them
2.8.1 Remove/re-position standard fields in the Manage Product Master

Fiori app
At the current time of publishing this document, only a limited number of Fiori apps have been enabled for extensibility. The
Manage Product Master app (Fiori tile is called Product Master Create/Change/Display) is one of them.
To begin, open the Fiori Launchpad in your browser with user S4H_EXT, password Welcome1.
https://vhcals4hci.dummy.nodomain:44301/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?

Open the Fiori
with user S4H_EXT,
password Welcome1.
Click on the Product

Master (Create /
Change / Display) app.
In the Search field,

enter bike to display
the material master
items and click on the
line with the C900
BIKE to display the
product master
information of it.
142
In the Manage Product
Master View, click on
the Me area for the
user Eric Extent (user
ID S4H_EXT).
Click on Adapt UI.

Note:
this function is only
available to users who
have the right
authorizations
assigned (typically an
IT user or a business
power user).
The black bars on top

and bottom indicate
that you are now in the
extensibility mode for
this app.
You can now move the

existing fields via Drag
& Drop.
Use your mouse to
hover over the field
Base Unit of Measure
and click on it.
Afterwards, drag it to
its new place on the
bottom of the column. Drag &
Drop
Note:
Depending on your
computer operating
system and browser
(e.g. Win10 & Chrome),
you might encounter
143
problems with drag &
drop. Either use a
different browser or
use the Remove and
Add features (see next
step).
Right-click on the field

‘Division’ and choose
Remove.
Your changes take

effect without saving if
you click on Exit in the
top bar.
You can undo changes
or reset all your
changes (going back to
the SAP standard
delivery) by using the
respective icons in the
top and bottom bars.
2.8.2 Adding two custom fields to the Product Master Fiori app
In this step, you will add two custom fields to the Product Master Fiori app (one is a checkbox, one is a free-text field).
The field definitions are part of the S/4HANA 1610 appliance shipment already, but you can also define your own fields and even
custom code extensions (the latter requires some coding knowledge).
Please see the Fiori extensibility documentation on http://help.sap.com that is mentioned above.

Navigate to the Adapt
UI mode for the Fiori
Product Master as
described above
(C900 BIKE as
product).
Right-click on Base
Unit of Measure and
choose Add Field.
144
In the list of available
fields, select the two
custom fields.
Click OK.
The two fields are

added to the app and
can be re-positioned /
removed as seen
before.
Click Exit to save your

changes and get back
into the non-extension
mode of the app.
Let’s fill our new fields

with content:
Back in the app, click
on Edit.
145
Click the checkbox
‘High Risk’ and enter a
comment in ‘Risk
reason’.
Important:
After entering the
short text, press the
Enter key.
Afterwards, click Save.
Note:
If you save without Hit ‚Enter‘ key !
pressing Enter, you will
get an HTTP error (still
a bug in the product
when the appliance
was produced).
Result:
You have adapted the
standard Fiori fields,
have added additional
fields and filled them
with data.
2.8.3 Creating your own custom fields

In this step, you create your own custom field.
146
Open the Fiori
with user S4H_EXT,
password Welcome1.
Click on the Custom

Fields & Logic app.
The two existing

custom fields are
already listed.
Click on + to add
another custom field
As Business Context
choose Product Master
General (this will
determine in what app
you can see these
fields).
The other fields are

description and field
type you can choose
them freely
Click Create and Edit.
In the upcoming
screen, click on Enable
Usage for the app
areas where you want
the custom field to be
visible (e.g. ‘Product
Basic Data’).
Check the Search

Relevance box.
Click on Save.
147
After the attribute has
been saved, click on
Publish.
Be patient, this will take

several minutes
(status will be
‘Publishing’)
Result:
You have created a
new custom field that
now can be used in the
Product Master app
(see above how to add
a field to the app).
148
2.9 Demo Story 8 - SAP Screen Personas
The purpose of this section is to describe the best practices for general configuration steps required to create a flavor in SAP
Screen Personas 3.0.
The goal of SAP Screen Personas is to reduce complexity of the transaction by reducing the number of screen elements, the
number of mouse clicks, make the screen more ergonomic, personalizing the screen with relation to the user and the company
branding. Standard documentation for development activities for SAP Screen Personas is available in the SAP Help Portal.
2.9.1 Preliminary Steps
Before you start developing a flavor there are a number of preliminary steps that you should progress through to determine user
requirements and design a user interface that meets these requirements:
 Get familiar with the application or transaction, referencing for example, a SAP Best Practices process flow as a basis.
 Consult with a business user of the transaction or application, and determine their requirements.
 Consult with a UI/UIX Designer to make design decisions for the flavor.
 Determination of needed/required screen elements for processing like:
- Buttons
- Input/output fields
- Descriptions
- Data fields
- Tables
- Tabs
- Others
 Determination of unused, not needed and disabled screen elements
 Grouping screen element to be displayed by theme or functionality
 Get familiar with UI design guidelines and company branding rules
Once you have gone through these preparatory steps, you can start developing the flavor using SAP Screen Personas.
2.9.2 Creating a Flavor
Procedure
1. Logon to the S/4HANA 1610 Trial system, client 100, using SAP GUI (see 2.1.2 for more details):
User: S4H_PERS
Password: Welcome1
Select “URL – Personas” and start the SAP Screen Personas. You will have to logon again. (Use Google Chrome as Browser).
149
2. You can create a favor for any SAP Transaction code such as VA01 – Create Sales Order. Enter VA01 into the command field
and press Enter.
3. Choose SAP Screen Personas button to open the Flavor Manager (see note below).
Note: The SAP Screen Personas button is visible after rolling over the blue header line at the top of the screen. The button will
appear in the center at the top of the browser window. It is displayed as an icon with the SAP Screen Personas logo:
This icon has the tooltip SAP Screen Personas.
4. Choose Create New Flavor to create your own flavor.
150
5. In the Create New Flavor dialog box, enter the name and description for your flavor.
6. Choose Create.
7. The new flavor opens in edit mode.
151
8. Double click on the ‘Order Type’ entry field and you will get a pop-up screen. Enter ‘OR’ in the Data field and press Done. This
will give the entry filed a default value of ‘OR’.
9. Select a screen element of the GUI, all possible actions or changeable attributes are enabled in Screen Personas menu bar. For
example you can do the following for the selected element:
o Hide items
o Drag and drop an item to a different screen area
o Add custom text to a button by double clicking into to the button and enter the new button text.
o Resize the screen element by stretching the frame or entering values into the positioning field of the menu bar
o Change Font attributes for labels and fields
10. Select the Insert tab to insert additional screen elements to the flavor, for example:
o Labels
o Group Boxes
o Images
o Buttons
o Boxes
o Fields
Note: You can use a Group Box to optically arrange screen elements. In order to do this, create a Group Box and place the screen
elements into this Group Box.
11. Switch back to the Home tab for further editing of the added screen element
12. Select the Tables tab to edit a table on the screen. The possible actions on table columns are:
o Hiding
o Moving
o Changing header text
13. Select Release tab for administrational activities, such as
o Changing the flavor name
o Changing the flavor description
o Displaying the history
o Creating a new version of the flavor
14. To save the flavor, choose Save Changes or Exit.
Note: The Save options are visible at the top right of the browser window of the flavor editor. The options are placed adjacent to
each other as two icons:
152
The option Save Changes keeps the flavor editor open and you can continue with further editing activities; the option Exit closes the
flavor editor and returns to execution mode.
Recommendation: Due to time-out issues with the browser session, SAP recommends adopting a “Save early and save often”
approach: you save the flavor regularly during your editing activities. Do not wait until you have completely edited the flavor before
saving the flavor.
Recommendation
The SAP GUI screen elements that should not be displayed can be set invisible using the hide functionality. You can do this in edit
mode in the Home tab using the Hide command.
If Screen elements are created via SAP Screen Personas functionality on Insert tab and should no longer be visible this elements
should be deleted. You can do this in edit mode in the Insert tab using the Delete Objects command.
2.9.3 Sharing a Flavor
Use
Once you have created a flavor, this flavor is available for you to edit and execute. In order to allow other users to either edit or
execute the flavor, you must share the flavor with the user or assign the flavor to a role to which the user is assigned.
Recommendation: In order to allow another user to edit a flavor, it is recommended that you share the flavor directly with the user.
Procedure
1. Logon to the system using SAP Logon.
2. Access the transaction using the following navigation path:
Transaction Code /PERSONAS/FLAVORS
3. Enter your search criteria for the required flavors in the options in the SAP Screen Personas Flavor Maintenance screen; for
example, in the selection field Flavor Name enter <flavor name>.
4. Choose Search.
5. In the SAP Screen Personas Resource Maintenance – Display “<flavor name>” screen, choose Change.
6. In the Sharing/Assignment section, choose Insert Row. This is the icon positioned directly above the column User.
7. Enter <User> in User.
8. Select Assign.
9. Choose Save.
Results
You have shared the flavor with another user. The user can execute the flavor, and if they have the authorization to edit flavors, can
also edit the flavor.
2.9.4 Assigning a Flavor
Use
Once you have created a flavor, this flavor is available for you to edit and execute. In order to allow other users to either edit or
execute the flavor, you must share the flavor with the user or assign the flavor to a role to which the user is assigned.
Recommendation: In order to allow another user to execute a flavor, it is recommended that you assign the flavor to a role to which
the user is assigned.
Pre-requisite
The role must already be added for SAP Screen Personas.
153
Note: Management of the roles is an administration task. For further information on this, refer to section Authorization and Roles in
the configuration guide Administration Guide for SAP Screen Personas (building block UPG).
Procedure
3. Enter your search criteria for the required flavors in the options in the SAP Screen Personas Flavor Maintenance screen; for
example, in the selection field Flavor Name enter <flavor name>.
4. Choose Search.
5. In the SAP Screen Personas Resource Maintenance – Display “<flavor name>” screen, choose Change.
6. In the Sharing/Assignment section, choose Insert Row. This is the icon positioned directly above the column Role.
7. Enter <Role> in Role.
8. Select Assign.
9. Choose Save.
Results
You have assigned the flavor to a role. Users who are assigned to this role can execute the flavor, and if they have the authorization
to edit flavors, can also edit the flavor.
2.9.5 Copying a Flavor
Sometimes it may be necessary to make a copy of a flavor because you want to try something or you want to have a setup point or
fall back when developing the flavor further on.
There are two options to do this:

1. Using the browser
The following steps create a copy of a flavor:
 Select the flavor to be copy,
 Choose Create New Flavor on Screen Personas Menu bar
 In the input field Name, enter <flavor name>.
 In the input field Description, enter <description text>.
 Check base on flavor <source flavor name> checkbox and choose Create.
2. Using SAP GUI administration

The following steps create a copy of a flavor
 Logon to the system using SAP Logon.
 Access the transaction using the following navigation path:
 Enter your search criteria for the required flavors in the options in the SAP Screen Personas Flavor Maintenance
screen; for example, in the selection field Flavor Name enter <flavor name>.
 Choose Search.
 In the SAP Screen Personas Resource Maintenance – Display “<flavor name>” screen, choose Copy.
 Confirm the flavor creation (copy action).
 A new flavor with “<flavor name> (COPY)” is created.
 Afterwards you can change the flavor name.
We recommend using the second option, to ensure that a consistent copy/version of the flavor is created.
154
2.9.6 Changing a Flavor
Procedure
1. Logon to the development system using a web browser.
2. Start the transaction for which you want to change a flavor.
3. Choose SAP Screen Personas button to open the Flavor Manager.
Note: All flavors to which you are assigned for the transaction are displayed in the flavor bar.
4. Choose the flavor that you wish to edit.
5. Choose Edit Flavor.
Results
You can edit an existing flavor.
Note: You can edit any flavor to which you are assigned, not just those that you created. Likewise, any user who has Personas editor
authorizations and also has the flavor assigned to them can edit a flavor that you have created.
2.9.7 Deleting a Flavor
Procedure
2. Start the transaction for which you want to delete a flavor.
Note: All flavors to which you are assigned for the transaction are displayed in the flavor bar.
4. Choose the flavor that you wish to delete.
5. Choose Delete Flavor.
6. In the dialog box Delete Flavor, choose Yes.
Results
You have deleted a flavor so that this is no longer displayed in the flavor bar. The flavor can no longer be chosen to be edited or
executed.
Note: The flavor has not been deleted in the backend system. Instead, a deletion flag has been set for the flavor and this action can
be reversed. In order to irretrievably remove the flavor the backend system, the system administrator must complete the activity to
permanently delete the flavor. For further guidance on this, refer to Permanently Delete Flavors, Resources, or Themes in the
configuration guide Administration Guide for SAP Screen Personas (building block UPG).
2.9.8 Working with Resources
Use
A resource refers to an object that is uploaded to the Mime repository of the system for use in SAP Screen Personas, for example,
images uploaded as .jpg or .png files. You can upload the image in the Personas editor tool
2.9.8.1 Uploading an Image

Procedure
2. Start the required transaction for the flavor.
155
4. Choose the flavor that you wish to edit.
5. Place your cursor on the area of the screen where you wish to add an image.
6. Choose Insert  Image.
7. In the Insert Image from Image Gallery dialog box, choose Upload Image.
8. In the Upload Image from File dialog box, select Choose Files.
9. Choose the file that you want to upload from your local drive or server.
10. In the Upload Image from File dialog box, choose Upload Image.
Results
You have uploaded an image and can use this in your flavors, for example as a background picture.
2.9.8.2 Sharing Resources with Other Personas Developers

Use
When you upload an image, this is only available for you to include in a flavor, unless you make this resource public. If the image is
not made public, the image is visible to all end users who use the flavor that you have developed, but it does not appear in the list of
images to use for other developers when they insert images into flavors that they are developing. This may result in one image
being uploaded several times by different developers.
Procedure
Transaction Code /PERSONAS/RESOURCES
3. Enter your search criteria for the required flavors in the options in the SAP Screen Personas Resource Maintenance screen; for
example, in the selection field Resource Owner enter your user name.
4. Choose Search.
5. In the SAP Screen Personas Resource Maintenance – Mass Maintenance screen, select a resource.
6. Choose Open.
7. In the SAP Screen Personas Resource Maintenance – Display “<resource name>” screen, choose Change.
8. In the Resource section, select Public.
9. Choose Save.
Results
You have shared the resource with all other developers in this system, and they can use the image when creating their own flavors.
156
2.9.9 SAP Screen Personas 3.0 Screens
2.9.9.1 Initial Screen
1) SAP Screen Personas Icon
2.9.9.2 Flavor Manager
1) Tile for Original Screen – Standard GUI

2) Tile for New Flavor – other Flavor for same transaction
3) Tile for New Flavor – active/displayed
4) Create new Flavor Button
5) Help Button
6) Pin Flavor Manager
7) Exit (Close) Flavor Manager
8) Edit Flavor
157
9) Open Script Editor
10) Open Themes Gallery
11) Delete Flavor
12) Open Flavor Gallery
13) Scroll Flavors
14) Share Flavors
2.9.9.3 Flavor Editing – Home
1) Font Properties: Font Type, Font Size, Font Style, Font Color, Text Alignment
2) Actions: Fill Color, Border Style, Format Copy, additional Options
3) Actions: Hide, Arrange (Bring/Send to Background/Foreground), Group Objects, Align Objects
4) Layout: Positioning – Top, Left, Width, Height
5) Image Actions: Assign Image, Upload, Alignment, Stretch
6) Status Information: Selected screen element
7) Help Button
8) Save Button
9) Exit Button
158
2.9.9.4 Flavor Editing – Insert
1) Create Screen Elements: Image, Label, Sticky Note, Group Box, HTML Viewer, Tooltip, Toolbar Separator
2) Create Complex Buttons: Transaction Button, Website Button, Menu Item Button, Script Button, Clickable Area
3) Create Simple Buttons: Radio Button, Check Box, Drop-down List, Text Field
4) Events & Bindings: Highlight Bindings, Script Events, Screen Events
5) Delete Objects, Clone Control
2.9.9.5 Flavor Editing – Table
1) Table Layout: Hide Column, Change Column Header Text

2) Column Layout: Move Left, Move Right, Move to Fixed Area, Move to Scrollable Area
3) Table Formatting: Conditional Formatting
159
2.9.9.6 Flavor Editing – Design
1) Design Actions: Add Template, Add Shapes, Quick Styles
2.9.9.7 Flavor Editing – Release
1) Flavor Properties: Flavor Name, Flavor Description

2) File Compressing: Compress Function for Flavor Versions, Lock/Unlock Flavor
3) Versioning: Create New Version, History
160
2.9.9.8 Flavor Gallery
List of created and available Flavors.
2.9.9.9 Flavor Sharing
1) Sharing Flavor assigned to SAP Roles

2) Sharing Flavor assigned to users
161
2.9.9.10 Theme Gallery
List of available Themes for Flavor creation.
2.9.9.11 Scripting Screen
1) Undo/Redo
2) Execute script
3) Validate script
4) Start Recording
5) Create New Script
6) Current Scripts, all available scripts displayed in drop-down list
7) Change Script Name
8) Save Script
162
9) Delete Script
10) Inspector
11) Logging
12) Move Script View on screen up or down
13) Exit Scripting without saving script
14) RFC Tool
15) Script Screen, Edit screen area for manual script editing actions
16) Protocol Screen for Inspector/Logging/RFC
2.9.9.12 Scripting Screen - Inspector
1) Flavor
2) Scripting Area
3) Inspector
4) Object Selector
5) Object Type Selector for display
6) Search
7) Object Type
8) Help Documentation
9) Object Information
163
2.9.9.13 Scripting Screen - Logging
1) Logging
2) RFC Tool
3) Information
4) Delete Logs
5) Log Information/Details
2.9.10 Appendix
2.9.10.1 Additional Resources

When you are working with SAP Screen Personas, you may find the following resources helpful for you:
 SAP Community Network SAP Screen Personas
 SAP Screen Personas – Getting Started: SAP Screen Personas 3.0
 SAP Help Portal: SAP Screen Personas
2.9.10.2 Demo Videos

SAP has published a series of demo videos for SAP Screen Personas, of which the following are particularly relevant if you are
developing SAP Screen Personas flavors:
 SAP Screen Personas 3.0 getting started demo
 SAP Screen Personas 2.0 to Personas 3.0 Flavor Migration Demo
164
2.10 Demo Story 9 – SAP BusinessObjects BI Platform
This scenario demonstrates how to access pre-configured business intelligence reports that are populated with data from an SAP
S/HANA 1610 system.
2.10.1 Prerequisite: BI platform in your trial landscape

If you are running this scenario via SAP CAL (i.e. hosted in AWS or Azure):
As default, the BI platform will be deployed as part of your landscape.
However, during the creation of your system instance, you can deactivate the deployment of the BI platform to save hosting costs.
This can be done in the Advanced Mode of the instance creation process via de-selecting a checkbox in the Virtual Machines
section of the instance creation wizard. If this flag has been de-selected, you need to create a new instance with the BI platform
deployed (if you are unsure if the BI platform has been deployed, please check in the instance details screen if you have IP
addresses for the BI platform assigned).
If you have the BI platform deployed and are using a local browser to access the BI platform, please map your hosts file as
described in the Quick Start Guide for setting up the trial on https://www.sap.com/cmp/oth/crm-s4hana/s4hana-on-
premise.html (step 10). You will need a mapping between the bihost alias and the IP address of your BI platform.
If you are using the remote desktop within SAP CAL, this mapping will be done automatically.
If you are running this scenario on your own hardware (i.e. you received the appliance via download or Blu-Ray):
There is no BI landscape contained in the local shipment so you need to import the BI reports (lcmbiar file) into a BI platform
provided by you and make the connection into your locally installed SAP S/4HANA system.
Please see the ‘SAP Best Practices for analytics with SAP S/4HANA’ package on https://rapid.sap.com/bp/#/BP_S4H_ANA
(scope item Integration between SAP S/4HANA and SAP BI) how to obtain the reports and configure your BI system.
2.10.2 Accessing the BI platform

This activity shows you how to access the BI platform and display reports with data from the SAP S/4HANA backend.
Note:
Not all of the reports will display (sensible) data, namely in Cost Center Plan/Actual and Profit Center Plan/Actual, you might
receive a ‘No data available’ message.

Open the BI launch pad
http://bihost:8080/BOE/BI
System bihost:6400
User BPINST
Password Welcome1
165
From the Home  My Recently
Viewed Documents tile, choose
some of the reports e.g. the
Rejected Sales Orders
Note: the list of recently viewed

documents might vary
The report(s) will show up in a

separate tab in the BI launch pad.
Depending on the type of report,

you have to enter some
attributes before executing the
report.
Also, there are different ways to
filter or drill-down inside the
reports.
If you want to explore the list of

all reports, navigate to
Documents  Folders  Public
Folders  S/4HANA
166
2.10.3 Connecting the BI platform to SAP S/4HANA
The following sections briefly describe how the connection to the SAP S/4HANA is defined. The aforementioned ‘SAP Best
Practices for analytics with SAP S/4HANA’ package (https://rapid.sap.com/bp/#/BP_S4H_ANA) explains this in detail.
The connection into SAP

S/4HANA is defined in the BI
Central Management Console
(http://bihost:8080/BOE/CMC)
System bihost:6400
User Administrator
Password Welcome1
Choose Organize  OLAP

Connections.
Right click on the S4HANA
connection and choose Organize
 Edit
The pre-defined connection into

SAP S/4HANA is displayed.
If you want to connect your own
SAP S/4HANA system, please
maintain them accordingly.
Depending on your network
setup, you might also need to
maintain the hosts file on the
(Linux) server where the BI
platform is running to make the
connection work.
Use the Connect button to test
your setup.
167
168

S4 HANA Demo Guide 1610 PDF

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

S4 HANA Demo Guide 1610 PDF

Uploaded by

Copyright:

Available Formats

SAP S/4HANA, On-Premise edition 1610 PUBLIC

February 2017 (V1.2)

SAP S/4HANA, On-Premise edition 1610 fully-activated software appliance:

Type Style Description

Example Emphasized words or expressions.

Revision Date Change

1.0 <2016-19-12> Release for customer

1.1 <2016-20-12> BI demo scenario added, minor updates

1.2 <2017-05-01> Updates to reflect period change to 2017 in FI/CO scenarios

2 Business Content & Demo Scenarios 8

1.1 Consumption of the trial and underlying software appliance

1.2 Pre-configured scope

1.3 Further information and support

2.1 Demo scenarios - Overview

2.1.1 Available Business Configuration and Master Data

Want to learn more?

2.1.2 Logon to Systems

Note about system performance:

Note about demo users:

Note about browser security messages, pop-up blocker & security

What to Do What You Will See

Select the SAP Logon icon.

Double-click your SAP

Result: You are logged on to

Log on to the SAP Fiori Launchpad:

Open an internet browser, as

Enter your SAP Fiori

You can search for an app,

By clicking on the icon located

Also, you have the option to

To return to the main SAP

Home icon . In case

2.2.1 Stock Availability

2.2.1.1 Check Stock Availability

What to Do What You Will See

Additionally select the

When you start the

2.2.1.2 Post Goods Movement

In the header screen

In the item details

In the Quantity tab,

In the Where tab, make

2.2.1.3 Open Inventory Management Period

What to Do What You Will See

2.2.2 Credit Management

What to Do What You Will See

On the header screen

Navigate to the Credit

2.2.2.2 Create Sales Order with Credit Block

What to Do What You Will See

In the Create Sales

In the Item screen,

Since the credit limit of

2.2.2.3 Sales Order Fulfillment Issue

What to Do What You Will See

As soon as the order

Select the item and

Due to the credit block,

2.2.2.4 Release Sales Order Credit Block

What to Do What You Will See

The system displays all

In order to release the

2.2.3.1 Create Sales Orders