408_BB_ConfigGuide_EN_DE.doc

EHP5 for SAP ERP 6.0

June 2011

English

Common Settings for SD + MM (408)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Common Settings for SD + MM (408). Configuration Guide

Copyright

© 2011 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, SAP BusinessObjects Explorer, StreamWork, 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 Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

© SAP AGPage 2 of 10


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.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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.



Contents

1 Purpose........................................................................................................................................ 62 Preparation................................................................................................................................... 6

2.1 Prerequisites.............................................................................................................................. 63 Configuration Settings.................................................................................................................. 6

3.1 Material Management (MM)..................................................................................................63.1.1 Creating Purchasing Group............................................................................................6

3.2 Sales and Distribution (SD)...................................................................................................73.2.1 Define Item Category Groups.........................................................................................73.2.2 Define Incompleteness Procedures...............................................................................73.2.3 Configure Global Shipping Data.....................................................................................83.2.4 Setting Up Partner Determination: Account Groups - Function Assignment..................9

3.2.4.1 Assign SD Conditions to CO-PA Value Fields......................................................10



1 Purpose This configuration guide provides 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 the SAP Best Practices Installation Assistant and other tools, refer to the SAP Best Practices Quick Guide.

2 Preparation2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix (Prerequisites_Matrix_[xx]_[yy]_ [zz].xls; the placeholder [xx] depends on the SAP Best Practices version you use, e.g. GTM refers to the SAP Best Practices for Global Trade Management, [yy] depends on the language version, e.g. EN for English language, and [zz] depends on the country version, e.g. DE for Germany: Prerequisites_Matrix_GTM_EN_DE.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\[xx]_[zz]\Documentation\; ([xx] depends on the SAP Best Practices version and [zz] depends on the country version).

3 Configuration Settings3.1 Material Management (MM)

3.1.1 Creating Purchasing Group

UseIn this step you create purchasing groups. A purchasing group can be an individual or a group of individuals.

Procedure1. Access the activity using one of the following navigation options:

IMG Menu Materials Management Purchasing Create Purchasing Groups

Transaction Code OME4

2. On the Change View “Purchasing Groups”: Overview screen, enter the following data:

Purchasing group Desc. Pur. Grp Tel. No. Pur. Grp Fax number Tel. Ext.

YN1 Trade Contract Grp

770 840 9421 770 840 9000 9

3. Choose Save.



3.2 Sales and Distribution (SD)3.2.1 Define Item Category Groups

Use This activity will create item category groups for item category determination.

Procedure 1. Access the activity using one of the following navigation options:

IMG Menu Sales and Distribution → Sales → Sales Documents → Sales Document Item → Define Item Category Groups

Transaction Code SPRO

2. Choose New Entries.3. Make the following entries:

Field Name User Action and Values Comment

ItCGr YNDP Drop Shipment

ItCGr YNSS Stock Shipment

4. Choose Save.5. Choose Back.

Result The item category group is defined.

3.2.2 Define Incompleteness Procedures

UseThis activity will define Incompleteness Procedures.


IMG Menu Sales and Distribution Basic Functions Log of Incomplete Items Define Incompleteness Procedures

Transaction Code OVA2

2. Select the row with Group A (Sales - Header) and then double-click Procedures.3. Choose Display Change.4. Choose New Entries.5. Make the following entries:

Field name Description User action and values Comment

InProc YN

Description Sales Order for TC



6. Choose Save.7. Select the YN row and then double-click Fields.8. Choose New Entries.9. Make the following entries:

Tables Field name Screen Status Group

VBAK AUDAT KKAU 01

VBAK WAERK KKAU 03

VBKD INCO1 KDE3 04

VBKD PRSDT KKAU 04

VBKD ZTERM KDE3 03

10. Choose Save.

Result The incompleteness procedure is defined.

3.2.3 Configure Global Shipping Data

Use This activity will activate the document flow parameter for inbound deliveries.


IMG Menu Logistic Execution Shipping Basic Shipping Functions Configure Global Shipping Data


2. Make the following entries:


Document Flow Update Yes Activate the document flow para

3. Choose Save.4. Choose Back.

Result The document flow parameter has been set.

3.2.4 Setting Up Partner Determination: Account Groups - Function Assignment

This step only applies if you have SAP Best Practices Baseline Package V1.605 already activated in your system and you like to use the baseline account group YB02.



UseIn this activity, you define the rules that should be used to perform automatic partner determination.

ProcedureCarry out the following steps:1. Access the activity using one of the following navigation options:

IMG Menu Sales and Distribution Basic Functions Partner Determination Set up Partner Determination

Transaction Code SM34 (customizing object VC_TPAR_KU)

2. On the View Cluster Maintenance: Initial screen, enter the view cluster VC_TPAR_KU and choose Maintain.

3. In the Choose Activity dialog box, double-click Set Up Partner Determination for Customer Master.

4. On the Change View “Partner Determination Procedures”: Overview screen, double-click Account Groups – Function Assignment.

5. Choose New Entries.

6. In the Account Groups – Function Assignment table, enter the following data:

Partn.Funct Account Grp

1B YB02

1C YB02

1D YB02

AA YB02

AF YB02

SP YB02

AW YB02

BP YB02

PY YB02

SB YB02

SO YB02

SH YB02

3.2.4.1 Assign SD Conditions to CO-PA Value Fields

UseAll revenues, sales deductions and other values (such as transfer prices) are defined as conditions in SD. In this step, you assign these conditions to the corresponding CO-PA value fields.




IMG Menu Controlling Profitability Analysis Flows of Actual Values Transfer of Billing Documents Assign Value Fields Maintain Assignment of SD Conditions to CO-PA Value Fields


2. If the Set Operating Concern popup screen appears, enter following data and choose Continue.


Operation Concern <Operating Concern> e.g. 10DE

Costing-based X

3. To create a new data, choose New Entries. 4. Make the following entries for the new data:


Ctype GSSP

Val.fld ERLOS4. Save your entries and go Back.

ResultYou have assigned the SD Conditions to CO-PA Value Fields.
