EHP4 for SAP ERP
6.0
June 2010
English
Customer Consignment
Processing (119)
Building Block Configuration Guide
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
Copyright
© 2010 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks
of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks
of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks
or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects
Explorer, and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of SAP France in the United States
and in other countries.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may
vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty
of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The
only warranties for SAP Group 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.
© 2010 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
© SAP AG
11
Page 2 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks
of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks
of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks
or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects
Explorer, and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of SAP France in the United States
and in other countries.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may
vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty
of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The
only warranties for SAP Group 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.
© SAP AG
11
Page 3 of
SAP Best Practices
Customer Consignment Processing (119): 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 AG
11
Page 4 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
Content
1
Purpose........................................................................................................................... 6
2
Preparation ..................................................................................................................... 6
2.1
3
Prerequisites ............................................................................................................ 6
Configuration .................................................................................................................. 6
3.1
Defining Sales Document Type................................................................................ 6
3.2
Consignment: Assigning Item Categories ................................................................ 7
3.3
Defining Item Category Determination in Deliveries ................................................ 8
3.4
Defining Order Reasons ........................................................................................... 9
3.5
Sales Documents: Copying Control ......................................................................... 9
3.6
Deliveries: Copying Control...................................................................................... 9
3.7
Assigning Sales Area to Sales Document Types .................................................... 9
3.8
Creating Condition Records for Output Type ......................................................... 10
© SAP AG
11
Page 5 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
Customer Consignment Processing
1
Purpose
This configuration guide provides you with the information you need to set up the
configuration of this building block manually.
If you do not want to configure manually and prefer an automated installation process using
BC Sets and other tools, refer to the SAP Best Practices Quick Guide.
2
Preparation
2.1 Prerequisites
Before you start installing this building block, you must install prerequisite building blocks. For
more information, see the building block prerequisite matrix
(Prerequisites_Matrix_[xx]_EN_FI.xls; the placeholder [xx] depends on the SAP Best
Practices version you use, e.g. BL refers to the SAP Best Practices Baseline Package:
Prerequisites_Matrix_BL_EN_FI.xls). This document can be found on the SAP Best Practices
documentation DVD in the folder ..\BBLibrary\General\.
3
Configuration
3.1 Defining Sales Document Type
Use
The purpose of this activity is to create a sales order type as the basis of consignment pickups and to change order type KB regarding the document pricing procedure.
Procedure
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. On the Change View “Maintain Sales Order Types”: Overview screen, choose Position.
3. Enter KA in the input field Sales Doc. Type in the Another Entry dialog box.
4. Choose Continue (Enter).
5. On the Change View: Maintain Sales Order Types: Overview screen, mark the line of
sales document type KA and choose Copy As…(F6).
6. On the Change View “Maintain Sales Order Types”: Details of Selected Set screen, enter
the value shown below (do not delete existing entries or overwrite them).
Field Name
User Action and Values
Sales Document Type
YBKA - Consignment Pick-up
© SAP AG
11
Page 6 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
Field Name
User Action and Values
Doc. pric. procedure
A
Shipping conditions
RE
7. Choose Continue (Enter).
8. Choose Yes in the Dependent Entries for Copying Control dialog box.
9. Choose
Back.
10. On the Change View “Maintain Sales Order Types”: Overview screen, choose Position.
11. Enter KB in the input field Sales Doc. Type in the Another Entry dialog box.
12. Choose Continue (Enter).
13. On the Change View: Maintain Sales Order Types: Overview screen, mark the line of
sales document type KB and choose Details.
14. On the Change View “Maintain Sales Order Types”: Details of Selected Set screen, enter
the value shown below (do not delete existing entries or overwrite them).
Field Name
User Action and Values
Doc. pric. procedure
A
15. Choose Continue (Enter).
16. Choose
Save.
17. Repeat step 11 to 17 for sales document type KR.
18. Choose
Back.
Result
Consignment pick-up sales order type is defined. Consignment fill-up sales order type has
been changed.
3.2 Consignment: Assigning Item Categories
Use
The purpose of this activity is to assign sales document item categories to sales document
types.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Item  Assign Item Categories
Transaction Code
SPRO
2. On the Change View “Item Category Assignment”: Overview screen, choose New Entries.
3. Enter the values shown below:
SaTy
ItCGr
DfItC
KB
YB09
KBN
© SAP AG
11
MltCa
MltCa
Page 7 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
SaTy
ItCGr
DfItC
KE
YB09
KEN
YBKA
YB09
KAN
YBKA
NORM
KAN
MltCa
MltCa
4. Save your settings.
5. Choose Back (F3).
Result
Item categories have been assigned.
3.3 Defining Item Category Determination in
Deliveries
Use
The purpose of this activity is to define the item category determination for deliveries. The
following applies:
If an order item or a schedule line is copied into a delivery, the item category is also copied.
For items independent of orders in the delivery (for example, packaging material that is
entered in the delivery) or deliveries without reference to an order, the item category is
determined by the SAP system by allocating the item category group to a delivery type.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
Logistics execution  Shipping  Deliveries  Define item
category determination in Deliveries
Transaction Code
0184
2. On the Change View “Delivery item category determination”: Overview screen, choose
New Entries.
3. On the New Entries: Overview of Added Entries screen, enter the values shown below.
DlvT
ItCG
Usg.
ItmC
ItmC
LF
NORM
CHSP
KBN
KBN
4. Save your settings.
5. Choose Back (F3).
Result
The item category determination in deliveries has been defined.
© SAP AG
11
Page 8 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
3.4 Defining Order Reasons
Use
The purpose of this activity is to define order reasons for consignment.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
Sales and Distribution  Sales  Sales Documents  Sales
Document Header  Define Order Reasons
Transaction Code
SPRO
2. On the Change View “Sales Document: Order Reasons”: Overview screen, choose New
Entries.
3. Enter the following values:
Order Reason
Description
YB2
Consignment pick-up: leftover
YB3
Consignment pick-up: closing of store
YB4
Consignment pick-up: change of prod line
4. Choose
Save.
5. Choose
Back.
Result
The order reasons are defined.
3.5 Sales Documents: Copying Control
You do not have to maintain the settings for copy control regarding document type YBKA
manually. The settings are created automatically during copying the sales document type KA
to YBKA (see 3.1).
3.6 Deliveries: Copying Control
You do not have to maintain the settings for copy control regarding document type YBKA
manually. The settings are created automatically during copying the sales document type KA
to YBKA (see 3.1).
3.7 Assigning Sales Area to Sales Document Types
Use
In this menu option, you allocate the allowed order types to each sales area.
Procedure
1. Access the activity using one of the following navigation options:
© SAP AG
11
Page 9 of
SAP Best Practices
Customer Consignment Processing (119): Configuration Guide
IMG Menu
Sales and Distribution  Sales  Sales Documents  Sales
Documents Header  Assign Sales Area To Sales Document Types
Transaction Code
SPRO
2. In the Choose Activity dialog box, choose Assign Sales Order Types Permitted for Sales
Areas.
3. On the Change View: Sales Documents. Allowed Order Types per Sales Org.: Overview
screen, choose New Entries and make the following entries:
Reference Sales
Organization
Reference Distribution
Channel
Reference Division
Sales Document
Type
1000
10
10
YBKA
4. Choose
Save.
5. Choose
Back.
Result
Sales document type for consignment pick-up is assigned to the relevant sales area.
3.8 Creating Condition Records for Output Type
Use
In this activity you create the condition records for output type BA00.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Logistics  Sales and Distribution  Master Data  Output 
Sales Document  Create
Transaction Code
VV11
2. On the Create Output – Condition Records: Sales screen, enter the output type BA00 and
choose Enter.
3. On the Create Condition Records (Order Confirmation): Fast Entry screen, make the
following entries:
Field Name
Description
User Action and Values
Sales
Organization
1000
Sales
Document
Type
KB
Function
SP
Comment
Partner
Medium
1
Date/Time
4
Language
© SAP AG
11
Page 10 of
SAP Best Practices
4. Choose
Save.
5. Choose
Back.
Customer Consignment Processing (119): Configuration Guide
Repeat the steps described above using the sales document type KE.
Result
You have created the output condition record for output type BA00 and sales document types
KB, KE.
© SAP AG
11
Page 11 of