assortment operations

Download Assortment Operations

Post on 12-Oct-2015

11 views

Category:

Documents

1 download

Embed Size (px)

DESCRIPTION

Assortment Operations

TRANSCRIPT

BB Configuration Guide

EHP5 for SAP ERP 6.0June 2011EnglishEnglish

Assortment Operations (713)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBuilding Block 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.

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

IconMeaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type StyleDescription

Example textWords 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 textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames 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 textScreen 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 TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Contents

5Assortment Management: Configuration Guide

51Purpose

52Preparation

53Configuration

53.1Assortment

53.1.1Maintain General Control for Assortments

73.1.2Maintain Assortment Dimensions

83.1.3Maintain Assortment Types

93.2Layout

93.2.1Maintain Fixture Categories

103.2.2Maintain Settings for Layout Workbench Connection

113.2.3Setting System Messages

113.2.4Creation Status for Core Articles

123.2.5Maintain a Maintenance Group for Core Articles

143.2.6Maintain Space Management Profiles

153.2.7Assign Space Management Profile to Site

153.2.8Maintain annual seasons

Assortment Management: Configuration Guide

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 BC Sets and other tools, refer to the installation guide of this building block.2 Preparation

Before you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix located on the Documentation DVD on the Content Library page under Technical Information (on the left navigation pane).

3 Configuration

3.1 Assortment3.1.1 Maintain General Control for AssortmentsUse

In the transaction WSS1 (General Control, Retail Master Data) you define some basic master data related parameters that affect several application areas in SAP Retail. Relevant for this building block are the settings that are related to assortments, which are grouped in subscreen Control, Assortments. Here you define: Which interface module you want to use between Assortment and Integrated Article Maintenance (Using a module other than the available standard module is a massive deviation from the standard and should not be done lightly.) If you want to work with without listing conditions (As listing conditions are a prerequisite for POS download and assortment list generation this indicator should not be set). The function module which performs subsequent listing/master data creation in cases where the article master data is missing in a transaction involving stock for a target site and subsequent listing is allowed for it. Whether you want an entry to be made in the system log if during the creation of article master segments in assortment maintenance functions no reference can be found and thus the article segments can not be created fully. If when processing the errors reported in the system log for missing article master segments, the system determines that some errors still cannot be solved, another entry is made in the log. Number of days that the log records for missing segments would remain in the system (if you have chosen to create such log entries). The function module with which you can carry out any further checks to see whether an article is allowed in a sales order or delivery (User-Exit). If multiple assignment of sites and assortments is active. When multiple assignment is active, a site can be assigned several assortment of type 'C' besides its own local site-specific assortment. If it is not active, there is a 1:1 assignment ratio between site and assortment, meaning every site has its own local assortment and cannot be assigned any other assortments. If the local (site-specific) assortments are taken into account in listing when using the mass listing processes (WSM4, WSM8). If you want to use time-dependent assignment of sites to assortments

Procedure

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

Transaction CodeWSS1

IMG MenuIMG( Logistics - General ( Basic Data Retail ( General Control, Retail Master Data

2. On the Retail Master Data General Control screen, check that the following entries exist:Field nameDescriptionUser action and valuesNote

FM AssortmentInt.art.maint.ASSORTMENT_VERSION_ALL

Work Without Listing Conditionsnot set

FMod Subs. listingUSER_EXIT_NACHLISTUNG

Log missing article segmentsSet flag

Error log, multipleSet flag

Log records retention (days)10

FMod Any listing checkASSORTMENT_VERSION_GHC

Multiple Assignment Is ActiveSet flag

Local Assort-ments ListingSet flag

Time-Dep. Assignm.Set flag

3.1.2 Maintain Assortment Dimensions

Use

Assortment dimensions are used to group plants with similar characteristics together to use one assortment. The assortment dimensions to be used are defined by the assortment type. An assortment can use up to three assortment dimensions.

In this step, you defi