SAP S/4HANA
November 2015
English
Return to Vendor(BMO)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
Copyright
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting
an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any
time for any reason without notice. The information in this document is not a commitment, promise, or
legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 2 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, buttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP SE
Page 3 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
Content
Return to Vendor ....................................................................................................................... 5
1
Purpose .............................................................................................................................. 5
2
Preparation ......................................................................................................................... 5
3
2.1
Prerequisites ............................................................................................................ 5
2.2
Deployment Options ................................................................................................. 5
2.3
Configuration ............................................................................................................ 5
Configuration - On-Premise................................................................................................ 6
3.1
Delivery Item Category............................................................................................. 6
3.1.1
Defining Delivery Item Category .......................................................................... 6
3.1.2
Defining Sales Document Types ......................................................................... 6
3.1.3
Specify Copy Control for Deliveries ..................................................................... 8
3.1.4
Delivery Item Category Determination for Delivery ............................................. 8
3.2
Schedule Line Categories ........................................................................................ 9
3.2.1
Define Schedule Line Categories ........................................................................ 9
3.2.2
Assign Schedule Line Categories ...................................................................... 10
© SAP SE
Page 4 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
Return to Vendor
1
Purpose
The purpose of this document is to describe the general configuration steps required to
manually set up the configuration within the system landscape that has already been installed
using the corresponding installation or configuration guides for installation.
If you do not want to configure manually and prefer an automated installation process using
BC Sets and other tools, refer to the Configuration Guide – Getting Started of your SAP rapiddeployment solution that is attached to the SAP Note.
This document supplements the existing Customizing documentation in the Implementation
Guide (IMG) and provides additional information where required.
2
Preparation
2.1 Prerequisites
Before you start installing this scenario, you must install the prerequisite building blocks. For
more information, see the Building Block Prerequisites Matrix.
2.2 Deployment Options
The configuration guide provides the implementation content for the different deployment
options/SAP Products S/4HANA

Public cloud (PC) – minimal scope & content

On-premise (OP) – full scope and content coverage
Depending on the use case/deployment option/ S/4HANA product version, you need to
implement the required scope/content starting with the Public cloud chapter and proceed with
the next required chapters.

For the full scope of the on-premise scope & content – PC and OP are required

For the public cloud scope & content – PC is required; OP is not required
2.3 Configuration
The following section describes the complete settings for this building block. These settings
can be divided into three main groups:

Prerequisite settings that have to be checked and which were delivered by SAP (as part
of the standard delivery)
The term Check refers to these prerequisite settings.

Settings defined by the customer (in the customer namespace and customer-specific):
The system uses automation to request individual customer settings during the
personalization process. These settings can be initial or reused from existing SAP ERP
layers and are indicated in the text by <your value>.
© SAP SE
Page 5 of 10
SAP Best Practices

Return to Vendor (BMO): Configuration Guide
Additional settings that need to be made, covered either by automation or manual
configuration (in the customer namespace).
The term Create refers to these additional settings in the text.
3
Configuration - On-Premise
3.1 Delivery Item Category
3.1.1 Defining Delivery Item Category
Use
In this activity, you define the delivery item category.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
Logistics Execution → Shipping → Deliveries → Define Item
Categories for Deliveries
Transaction
Code
0VLP
2. Choose New Entries.
3. Make the following entries:
Field Name
Description
User Action and Values
Comment
Item Category
RLN
Returns Order
Document cat
J
Delivery
ItemCat.stat.group
1
Check quantity 0
A
Note about the situation
Check overdelivery
Relevant for picking
Selected
StLocation required
Selected
Determine SLoc
Selected
AutoBatchDeterm
4. Save your entries.
5. Choose Back.
Result
The delivery item category is defined.
3.1.2 Defining Sales Document Types
Use
This activity defines settings for sales document types.
Procedure
© SAP SE
Page 6 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
1. Access the activity using one of the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Header  Define Sales Document Types
Transaction
Code
VOV8
2. Choose New Entries.
3. Make the following entries:
Sales Document Type
DL
SD document categ.
C
Sales document block
X
Number range – internal assignment
01
Number range – external assignment
02
Item number increment
10
Sub-item increment
10
Reference mandatory
Check division
Check credit limit
Item division
Read info record
Output application
Screen Sequence Group
AU
Incompl.proced.
Transaction Group
0
Doc.Pric.Procedure
A
Display Range
UALL
FCode for overv. Scr.
UER1
ProdAttr.messages
Delivery type
Shipping conditions
Billing block
Delivery-related billing type
F2
Order-rel.bill.type
F2
Intercomp.bill.type
IV
CndType line items
Billing plan type
Paymt guarant. proc.
Paymt card plan type
Checking group
© SAP SE
Page 7 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
Propose Delivery Date
Billing request
Subseq.order type
4. Save your entries.
5. Choose Back.
3.1.3 Specify Copy Control for Deliveries
Use
In this menu option, you define control data for the document flow of deliveries.
Procedure
1. Access the activity using the following navigation options:
IMG Menu
Logistics Execution  Copying Control  Specify Copy Control for
Deliveries
Transaction
Code
VTLA
2. On the Change View “Header”: Overview screen, select New Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following data:
Field Name
User Action and Values
Target delivery type
RL
From SalesDoc Type
DL
Header Data
301
Comment
4. Double clock on Item (dialog structure on the left)
5. On the Change View “Item”: Overview screen, choose New Entries.
6. On the New Entries: Overview of Added Entries screen, enter the following data:
Field Name
User Action and Values
Item category
RLN
Item Data
302
Pos./neg. quantity
+
Comment
7. Save your entries.
Result
Copy Control is maintained.
3.1.4 Delivery Item Category Determination for Delivery
Use
The purpose of this activity is to determine delivery item category for delivery type NL.
Procedure
1. Access the activity using the following navigation options:
© SAP SE
Page 8 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
IMG Menu
Logistics Execution  Shipping  Deliveries  Define Item Category
Determination in Deliveries
Transaction
Code
0184
2. In the Delivery item category determination screen, enter the following information:
Field Name
Description
User Action and Value
DlvT
Delivery type
RL
ItCG
Item category group from material master
NORM
Usg
Item usage
V
ItmC
Item category of the higher-level item
ItmC
Default item category for delivery
RLN
3. Save your entries.
4. Choose Back.
3.2 Schedule Line Categories
3.2.1 Define Schedule Line Categories
Use
The SAP system can only copy those items of a sales document to a delivery for which
schedule lines exist. Control of the schedule lines depends on the schedule line category.
Procedure
1. Access the activity using the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Schedule
Lines Define Schedule Line Categories
Transaction
Code
VOV6
2. On the Change View “Maintain Schedule Line Categories”: Overview screen, select New
Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following data:
Field Name
User Action and Values
Sched. line cat.
RN
Description
Return w/o plan
Movement Type
161
Comment
Movement Type 1-Step
Item rel.f.dlv.
4. Save your entries.
Result
Schedule line category is created.
© SAP SE
Page 9 of 10
SAP Best Practices
Return to Vendor (BMO): Configuration Guide
3.2.2 Assign Schedule Line Categories
Use
In this step, you assign schedule line categories to item categories.
Procedure
1. Access the activity using the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Schedule
Lines Assign Schedule Line Categories
Transaction
Code
VOV5
2. On the Change View “Assign Schedule Line Categories”: Overview screen, select New
Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following data:
Field Name
User Action and Values
Item category
RLN
PropSchdLneCat.
RN
Comment
4. Save your entries.
© SAP SE
Page 10 of 10