Presentation is loading. Please wait.

Presentation is loading. Please wait.

Assortment Management

Similar presentations


Presentation on theme: "Assortment Management"— Presentation transcript:

1 Assortment Management
Best Practices for mySAP Retail

2 Assortment Management/Listing
Article Listing Assortment- Module A Assortment Assortment- Module B Listing conditions An assortment is an object in SAP Retail to which articles are assigned, that is, listed for a certain validity period. The assignment of articles to assortments determines which assortments, and therefore which articles, a store can buy and sell. Articles are assigned on the shelf using assortment modules. The assignment results in listing conditions, which serve as the basis for subsequent business processes. Articles can be assigned to assortments automatically during article or assortment maintenance. Alternatively, you can assign articles to assortment modules manually and then assign the modules to the assortments.

3 Assortment Management /Listing
user Article Listing Assortment- Module A Customer Kunde Assortment Assortment- Module B M:1 DC 1:M Listing conditions Assigning an assortment user to an assortment makes the articles available for the users concerned for use in the various different business functions.  The most important assortment user in retail is the retail site. The assortments for a site include all articles that are involved in the site's economic activities. In addition to assigning individual general assortments to assortment users, it is also possible to define reference sites and to assign them to sites in a 1:M ratio. Only sites that are not assigned to a reference site can be assigned to an assortment. Sites assigned to reference sites are assigned to assortments via their reference sites. A reference site cannot be assigned to a customer. The big advantage of reference sites is the one-time assignment of general assortments. All dependent sites (sites assigned to the reference sites) automatically take on all the assortments assigned to the reference site. This pointer function means that changes to general assortments and changes to the assignments of general assortments to reference sites are also copied automatically. If a site is already assigned to assortments, it can only be assigned to a reference site if the reference site contains these assignments. The main use for this n:m multiple assignment and reference sites is in assortment management for stores. It is, however, also possible to assign a reference site to a distribution center. We recommend the exclusive use of dummy reference sites so that you can maintain certain listing conditions for each of your operative stores, independently of your regular reference handling. (Example: You want to create an assortment for certain articles and release it for certain sites only. If one of these sites was a reference site, the data would automatically be passed on to all the sites assigned to it.) If the assignment of a site to a reference site is deleted, all assortments assigned to the reference site will be deleted for the site Verteilzentrum Reference site Filiale Store

4 Assortment Management /Listing
user Article Listing N:M Assortment- Module A Customer Kunde Assortment Assortment- Module B M:1 DC Listing conditions In many retail companies, assortments for a distribution chain or for a certain region, for example, are often identical or differ only slightly. It therefore makes sense to define only a few general assortments and then to assign these to a group of assortment users. In Release 4.70, you can decide whether you want a 1:1 assignment of assortments to sites or whether you want to construct an n:m assignment. This new function is similar to the multiple assignment of customers to assortments of assortment type C, which was already available prior to Release This new assignment option has simplified assortment management significantly. Multiple assignment can also considerably reduce the number of listing condition records in the database since, among other things, a very large number of sites can be assigned to a general assortment. This results, above all, from the fact that articles are listed for assortments and not for sites and therefore the listing conditions created are valid for all the sites assigned to the assortment. Unlike with local assortments, which are not maintained in assortment maintenance and therefore cannot be assigned to sites or customers, it is now possible to assign general assortments (assortment type C) to any number of sites or customers (n:m multiple assignment of sites to assortments is activated in Customizing). Exclusion modules can still be used for local assortments. This enables you to generate exceptions for certain articles and subsequent listings. Exclusion modules can, of course, also be defined for general assortments. Verteilzentrum Reference site Filiale Store

5 Listing using the LayoutWB
Mit der Listung über Layout kann jetzt garantiert werden, dass für einen neuen Artikel erst einmal Platz im Warenträger geschaffen wird und dann der Artikel in den Sortimenten gelistet wird, denen der betreffende Warenträger zugeordnet ist. Neuen Artikeln wird also zuerst in der Layoutbausteinversion eine Platzierung zugewiesen. Gelistet werden nur die platzierten Artikel im Warenträger; d.h. die Artikel in einer Layoutbausteinversion, die ein Facing > 0 besitzen. Der Listungszeitraum eines Artikels entspricht dabei dem Gültigkeitszeitraum der entsprechenden Layoutbausteinversion. In SAP Retail kann jeweils nur die erste zukünftige Layoutbausteinversion gelistet werden. Sobald diese dann aktuell wird, können für die nächste zukünftige Version Listungskonditionen erzeugt werden. Unabhängig davon können jedoch beliebig viele zukünftige Layoutbausteinversionen gebildet werden. Strukturierte Artikel wie z.B. Lots oder Displays werden dann nebst allen Komponenten gelistet, wenn mindestens einer dieser Komponenten im Warenträger platziert ist. Ein Artikel kann dabei in einem Warenträger nicht gleichzeitig als Einzelartikel und als Komponente eines strukturierten Artikels gelistet werden. Die Listung über Layout erfolgt anhand von Sortimentsbausteinen des speziellen Typs ,Regalbaustein" (siehe ). Diese werden aus den zu listenden Layoutbausteinversionen in Verhältnis 1:1 generiert: Der Regalbaustein enthält einen direkten Verweis auf eine Layoutbausteinversion und besitzt dessen zeitliche Gültigkeit. Ferner sind dem Regalbaustein die Sortimente zugeordnet, denen der Layoutbaustein zugeordnet ist

6 Listing via Manual Planning
Executed during dialog planning Menu items for listing execution listing jobs display and listing conditions display In Merchandise and Assortment Planning in SAP Retail, listing conditions for newly defined articles can be created from manual planning. To do this, a planning scenario is defined that determines the structure of the planning process and the scope of planning. Planning steps represent the significant elements of a planning scenario. Different planning step methods are provided. The most important method is manual planning. Using manual planning, plan data for selected key figures and planning levels can be entered and plan data can be calculated in freely definable entry screens (planning layouts). The planning characteristics article and assortment must exist to create listing conditions. The listing attributes, in particular, the attribute listing date can be used to determine the listing time period. The listing period is found from the Customizing settings for defining interfaces (planning horizon or planning attribute), whereby the listing period can also be entered directly.

7 Manual Maintenance of Listing Conditions
Creation/Change of listing conditions of ONE article Only possible for one assortment Change validity Create new Conditions When creating listing conditions manually the missing article master is generated automatically. Creation of listing conditions is only possible for one assortment and a single article.

8 Reposting After Incorrect Article Master Generation
Creating article master data (MARC/MBEW/MARD) during the listing process leads to errors Log entry made in the Sys.Log. If flagged in Customizing Display article segments that cannot be generated Generate article segments Check reference article Automatic generation of article master data during the listing process may fail if no suitable copy pattern can be found for the new article master segments. Most errors occur if the reference article of the merchandise category is not maintained sufficiently or the selected sites for listing are not maintained properly. These errors are logged in the Syslog and can be handled with 2 functions: Display article master segments that cannot be generated Edit article master segments that cannot be generated A treatment is only useful if the respective reference articles have been corrected. For the state of the reference article use the function consistency check for reference article (see also Unit 9).

9 Relisting via Changes of Master Data
Select range of assortment Select master data change area Select date, listing options amd listing procedure for each change area Read change documents matching the selection criteria Affectetd articles are listed /discontinued Execute Changes in the master data for an assortment (for example, when an assortment grade is changed or a merchandise category is added or deleted) means that the relevant article listing also has to be corrected. Automatic assortment correction is triggered by the following changes to master data: Changes to the supplying sites assigned to an assortment via its assortment users Changes to the source of supply key for an article Changes to the assortment/merchandise category master Changes to assortment classification data Changes to the layout of the assortment or of the articles in the assortment or users assigned to the assortment Automatic assortment correction is not currently triggered by changes to listing data in the article master. If, for example, you change the assortment grade of an article and do not list the article manually in article maintenance afterwards, the article assortments will not be adjusted.

10 Article maintained in site Function Module USER_EXIT_NACHLISTUNG
Subsequent Listing Goods Receipt Subsequent listing No No Subsequent listing Article maintained in site Manual Decision Yes Function Module USER_EXIT_NACHLISTUNG Goods receipt can be posted Articles may arrive in a site for which they are not listed. E.g a supplier ships a newer article instead of an older one which he no longer carries. Or a promotional article is listed in the DC and shipped to a store. On site level you can specify how such receipts are handled: either allow the article and the system generates automatically the listing conditions and the master data disallow the article and return the shipment to the sender manual decision for each case This handling can be specified in the site master or the company structure in Customizing. The function module for subsequent listing is maintained in the Customizing.

11 Listing Data Model (1:1- Assignment)
WRF1 Site Data WRS1 Assortment Data WRSZ Assortment User Site Assortment WRF6 Site/Merch. Cat. WRS6 Merch. Cat. in Assort. If n:m assignment is active in the system, assignments of merchandise categories to sites are not transferred to the local assortment. This means that the assignment of merchandise categories to assortments (table WRS6) is independent of the assignment of sites (table WRF6). If the assignment of a merchandise category to a site is deleted, it is not copied to the local assortment. With n:m assignment it is possible to assign sites to reference sites. This means that a site has the same assignments to assortments as a reference site. If the assignment of a reference site to an assortment changes, this has repercussions on all other sites that reference the reference site.

12 Listing Data Model (N:M- Assignment)
The listing data model for 1:1 assignment of sites to assortments differs from n:m assignment in two fundamental ways: 1.) If n:m assignment is active in the system, assignments of merchandise categories to sites are not transferred to the local assortment. This means that the assignment of merchandise categories to assortments (table WRS6) is independent of the assignment of sites (table WRF6). If the assignment of a merchandise category to a site is deleted, it is not copied to the local assortment. 2.) With n:m assignment it is possible to assign sites to reference sites. This means that a site has the same assignments to assortments as a reference site. If the assignment of a reference site to an assortment changes, this has repercussions on all other sites that reference the reference site.

13

14

15 Copyright 2003 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com 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 in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.


Download ppt "Assortment Management"

Similar presentations


Ads by Google