SAP S/4HANA
November 2015
English
Debit Memo Processing
(BDR)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Debit Memo Processing (BDR): 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 13
SAP Best Practices
Debit Memo Processing (BDR): 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, pushbuttons 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 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
Content
Debit Memo Processing ............................................................................................................ 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
Defining Sales Document Type................................................................................ 6
3.2
Assigning Text Determination Procedure ................................................................ 7
3.3
Assigning Incompletion Procedure .......................................................................... 7
3.4
Assigning Partner Determination Procedure ............................................................ 7
3.5
Assigning Item Category .......................................................................................... 8
3.6
Copying Control: Sales Document to Debit Memo (Header) ................................... 9
3.7
Copying Control: Sales Document to Debit Memo (Item) ...................................... 10
3.8
Copying Control: Invoice to Sales Document(Header) .......................................... 11
3.9
Copying Control: Invoice to Sales Document (Item) .............................................. 11
© SAP SE
Page 4 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
Debit Memo Processing
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 and content – PC and OP are required

For the public cloud scope and 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>.

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.
© SAP SE
Page 5 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
3 Configuration - On-Premise
3.1 Defining Sales Document Type
Use
This activity will define the sales document type.
Procedure
1. Access the transaction 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. On the Change View “Maintain Sales Order Types”: Overview screen, choose New
entries.
3. Make the following entries:
Field Name
User Action and Values
Comment
Sales Document Type
CBII
Invoice Increase Req
SD Document Categ
L
Indicator
D
No.range.int.assgt
15
No.rang.ext.assg.
16
Item no. increment
10
Sub-item increment
10
Reference mandatory
M
Output Application
V1
Read info record
Selected
Screen sequence grp
GA
Credit/Debit Memo
Transaction group
0
Sales order
Doc.pric.procedure
A
Display Range
UALL
FCode for Overv. Scr.
UER2
Order-rel.bill.type
L2
Billing plan type
92
Billing Block
Y9
Propose deliv. Date
Selected
Debit Memo
4. Save your entries.
5. Choose Back.
Result
© SAP SE
Page 6 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
The sales document type is defined.
3.2 Assigning Text Determination Procedure
Use
In this activity, you assign the text determination procedure to sales document type CBII.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Basic Functions  Text Control  Define
and Assign Text Determination Procedures
Transaction
Code
SPRO
2. On the Customizing Text Determination screen, select Sales Document – Header and
choose Change.
3. In the Dialog Structure pane, double-click Text procedure assignment.
4. For the sales document type CBII enter the text determination procedure T3.
5. Save your entries.
Result
The text determination procedure is defined.
3.3 Assigning Incompletion Procedure
Use
This activity will assign the incompletion procedure to the sales document type.
Procedure
1. Access the transaction by choosing one of the following navigation options:
IMG Menu
Sales and Distribution  Basic Functions  Log of Incomplete Items 
Assign Incompleteness Procedures  Assign procedures to the sales
documents types
Transaction
Code
VUA2
2. For the row with Sales Doc Type (SaTy) CBII, in the Proc column, enter 15 (Debit Memo).
3. Save your entries.
4. Choose Back.
Result
The incompleteness logic has been defined for the sales document type.
3.4 Assigning Partner Determination Procedure
Use
© SAP SE
Page 7 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
In this activity, you assign the partner determination procedure to the sales document type.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Basic Functions  Partner Determination 
Set Up Partner Determination
Transaction
Code
SPRO
2. In the Choose Activity dialog box, double-click Set Up Partner Determination for Sales
Document Header.
3. In the Dialog Structure pane, double-click Partner Determination Procedure Assignment.
4. For Sales Doc. CBII, enter the partner determination procedure SO02.
5. Save your entries.
6. Choose Back.
Result
The partner determination procedure has been assigned.
3.5 Assigning Item Category
Use
This activity defines logic to assign item categories.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Item  Assign Item Categories
Transaction
Code
VOV4
2. Choose New Entries.
3. Make the following entries:
Field Name
User Action and Values
Sales Doc.Type
CBII
Item cat.group
NORM
Item usage
Blank
ItemCat-HgLvItm
Blank
Item Category
G2N
Manual Item Cat
L2N
Sales Doc.Type
CBII
Item cat.group
CBNA
Item usage
Blank
© SAP SE
Page 8 of 13
Comment
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
Field Name
User Action and Values
ItemCat-HgLvItm
Blank
Item Category
G2N
Manual Item Cat
L2N
Sales Doc.Type
CBII
Item cat.group
CBUK
Item usage
Blank
ItemCat-HgLvItm
Blank
Item Category
G2N
Manual Item Cat
L2N
Comment
4. Save your entries.
5. Choose Back.
Result
Item categories have been assigned to sales document types.
3.6 Copying Control: Sales Document to Debit Memo
(Header)
Use
This activity will define copying control logic in creation of Debit Memo L2 out of Sales Order
CBII from header level.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Billing  Billing Documents  Maintain
Copying Control for Billing Documents  Copying Control: Sales
Document to Billing Document
Transaction
Code
VTFA
2. On the Display View Header”: Overview screen, choose Display <> Change.
3. Choose New Entries.
4. Make the following entries:
Field Name
User Action and Values
Comment
Target Bill. Type
L2
Debit Memo
From SalesDoc Type
CBII
Copying requirements
001
Copy Item Number
Selected
Header/order-related
5. Choose Save.
Result
© SAP SE
Page 9 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
Copy control from CBII to L2 is created
3.7 Copying Control: Sales Document to Debit Memo
(Item)
Use
This activity will define copying control logic in creation of Debit Memo L2 out of Sales Order
CBII from item level.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Billing  Billing Documents  Maintain
Copying Control for Billing Documents  Copying Control: Sales
Document to Billing Document
Transaction
Code
VTFA
2. On the Display View Header”: Overview screen, choose Display <> Change.
3. On the Change View “Header”: Overview screen, choose Position.
4. On the Another Entry dialog box, make the following entries:
Field Name
Description
User Action and Values
Billing Type
L2
SalesDoc Type
CBII
Comment
5. Choose Continue (Enter).
6. Select the line of Tgt L2 and Source CBII and double-click Item in the Dialog Structure.
7. Choose New Entries.
8. Make the following entries:
Field Name
User Action and Values
Comment
Item Category
G2N
Request
Copying requirements
002
Item/order-related
Data VBRK/VBRP
002
Ord-rel.credit memo
Billing quantity
A
Pos./neg. quantity
+
Pricing type
D
9. Save your entries.
10. Repeat steps 7 to 9 for the following data:
Field Name
User Action and Values
Comment
Item Category
L2N
Request
Copying requirements
002
Item/order-related
Data VBRK/VBRP
002
Ord-rel.credit memo
Billing quantity
A
© SAP SE
Page 10 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
Field Name
User Action and Values
Pos./neg. quantity
+
Pricing type
D
Comment
11. Save your entries.
12. Choose Back.
Result
Copy control logic is defined.
3.8 Copying Control: Invoice to Sales
Document(Header)
Use
This activity defines copying control logic in creation of Sales Order CBII out of the original F2
invoice from header level.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Maintain Copy
Control for Sales Documents  Copying Control: Billing Document to
Sales Document
Transaction
Code
VTAF
2. On the Display View Header”: Overview screen, choose the Display <> Change button.
3. Choose New Entries.
4. Make the following entries:
Field Name
User Action and Values
Comment
Target Sales Doc type
CBII
Source Bill. Type
F2
DataT
052
Billing doc.header
DataT
103
Bill.bus.header data
DataT
003
Bill.header partner
Copying requirements
021
Billing header
Copy item number
Selected
5. Choose Back.
Result
Copy control from F2 to CBII is defined
3.9 Copying Control: Invoice to Sales Document (Item)
Use
© SAP SE
Page 11 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
This activity defines copying control logic in creation of Sales Order CBII out of the original F2
invoice from item level.
Procedure
1. Access the transaction using one of the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Maintain Copy
Control for Sales Documents  Copying Control: Billing Document to
Sales Document
Transaction
Code
VTAF
2. On the Display View Header”: Overview screen, choose the Display <> Change button.
3. On the Change View “Header”: Overview screen, choose Position.
4. On the Another Entry dialog box, make the following entries:
Field Name
Description
User Action and Values
SalesDoc Type
CBII
Billing Type
F2
Comment
5. Choose Continue (Enter).
6. Select the line and double-click Item in the Dialog Structure.
7. Choose New Entries.
8. Make the following entries:
Field Name
User Action and Values
ItemCat Proposal
G2N
2ndItemCatProposal
L2N
Item Category
TAN
DataT
153
Item from bill.doc.
DataT
104
Bill.bus.item data
DataT
004
Bill.item partner
Update document flow
X
Copying requirements
303
Pricing type
F
2nd pricing type
D
ItemCat Proposal
G2N
2ndItemCatProposal
L2N
Item Category
CB1
DataT
153
Item from bill.doc.
DataT
104
Bill.bus.item data
DataT
004
Bill.item partner
Update document flow
X
© SAP SE
Comment
Always an item
Page 12 of 13
SAP Best Practices
Debit Memo Processing (BDR): Configuration Guide
Field Name
User Action and Values
Comment
Copying requirements
303
Always an item
Pricing type
F
2nd pricing type
D
ItemCat Proposal
G2N
2ndItemCatProposal
L2N
Item Category
CB2
DataT
153
Item from bill.doc.
DataT
104
Bill.bus.item data
DataT
004
Bill.item partner
Update document flow
X
Copying requirements
303
Pricing type
F
2nd pricing type
D
ItemCat Proposal
G2N
2ndItemCatProposal
L2N
Item Category
CBAB
DataT
153
Item from bill.doc.
DataT
104
Bill.bus.item data
DataT
004
Bill.item partner
Update document flow
X
Copying requirements
303
Pricing type
F
2nd pricing type
D
Always an item
Always an item
9. Save your entries.
10. Choose Back.
Result
Copy control logic is defined.
© SAP SE
Page 13 of 13