assortment bp

7/28/2019 Assortment Bp

http://slidepdf.com/reader/full/assortment-bp 1/33

EHP6 for SAP ERP6.0

June 2012

English

Assortment Operations(713)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Business Process Documentation



SAP Best Practices Assortment Operations: (713): BPD

Copyright

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,SAP HANA, and other SAP products and services mentioned herein as well as their respective logos aretrademarks 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 astheir respective logos are trademarks or registered trademarks of Business Objects Software Ltd. BusinessObjects is an SAP company.

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

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG inGermany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained 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 itsaffiliated 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 onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.

© SAP AG of 33




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 andoptions.

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 keywords 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 asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

© SAP AG of 33




Contents

1 Purpose...................................................................................................................................... 5

2 Prerequisites............................................................................................................................... 72.1 Master Data and Organizational Data..................................................................................7

2.2 Checking User Parameters..................................................................................................8

2.3 Roles.................................................................................................................................... 8

3 Process Overview Table.............................................................................................................8

4 Process Steps ............................................................................................................................ 9

4.1 Assortment Management Basic...........................................................................................9

4.1.1 Defining Fixtures (optional)............................................................................................9

4.1.2 Creating a General Assortment.................................................................................. 11

4.1.3 Creating a Layout Module Version and Assigning a Fixture........................................13

4.1.4 Assignment of Articles to Layout Module Version........................................................ 15

4.1.5 Assignment of Assortment Users to the Assortment (layout module)..........................20

4.1.6 Releasing the Layout Module Version and Creating Listing Conditions.......................21

4.2 More Features of the Layout Workbench...........................................................................25

4.2.1 Copying Layout Module Versions................................................................................25

4.2.2 Article Replacement.....................................................................................................26

4.2.3 Where-used List of Articles..........................................................................................29

4.2.4 Space Management.....................................................................................................304.3 Deleting Layout Listing Conditions.....................................................................................32

© SAP AG of 33




Assortment Operation

1 Purpose

The aim of assortment management is to define which articles are to be listed for a store group. Articles are listed based on a validity period. The assortments of a site consist of all the articlesin which it trades. By assigning assortments to sites you control which assortments — and whicharticles — a store can purchase or sell. A site cannot purchase or sell an article that is notcontained in one of its assortments.

A site can have different assortments – it always has one local site-specific assortment and itcan also be assigned several general assortments, if multiple assignments between site andassortment have been activated. Multiple assignment means that a site may have severaldifferent assortments, and that an assortment may be assigned to several different sites.

The assortment management demands of retailers differ greatly. Some require identicalassortments in all areas, while others demand assortments unique (for example) to each store.Some have mainly non-replenishable seasonal merchandise and thus require frequent

assortment changes, while others have mainly replenishable basics and thus assortments thatare subject to fewer changes. Assortment management takes account of these differences andoffers a variety of tools for making the assignment of articles to assortments and the assignmentof assortments to assortment users.

With SAP ERP 6.0 the integration of assortment planning in BW and assortment management inERP was realized. You can now plan assortments and their assignments to sites in BW and thenrelease this data for detailed assortment planning or operational use to ERP.

Fashion articles typically have a short life cycle and long lead times. As a result, the articles areplanned once, ordered and sent to the stores (“first push scenario”). To obtain the best possiblemerchandise distribution among the stores, you can hold stock in reserve at the distributioncenter, and then have the stores requisition supplies as needed. This allows you to account for different sales rates at different stores during the season (“then pull scenario”).

With Operational Assortment Planning and Control (OAPC), you can specify the articles andquantities you wish to order, both for delivery to the stores and putaway quantities for thedistribution center. The Operational Assortment Planning and Control is situated in ERP. Thetarget quantities for the OAPC are planned in BW and released to the OAPC in ERP.

For more information about the assortment management for fashion (seasonal) articles usingOAPC see business process 720 – Plan-driven Procurement .

There are two options for the handling of the assortment management of basic articles: one isthe integrated process with BW and one is the ad hoc process which takes place only in ERP.

Integrated process:

In the integrated process the results of the assortment planning process in BW can be used as abasis for the assortment management in ERP. The process assortment planning for basicmerchandise in BW contains the planning of assortments, assortment versions and theassignment of assortments to stores. The assignment of the assortments to sites can be doneautomatically or manually for specific periods of time. You can use assortment dimensions tomake these assignments with which you group similar sites. In this case, the system canautomatically assign sites to assortments. In the customizing of ECC6.0 EHP5 it can be definedthat the assortments of an assortment type represent a layout module and therefore anassortment version represents a layout module version.

The planned master data is then released to ECC6.0 EHP5 via the release workbench.

© SAP AG of 33




The steps of the assortment management in ERP that follow the assortment planning in BWcould then be as follows:

Creation of planned assortments etc. (inbound process, triggered by the release process in

BW)

Maintenance of the (internal) capacity of assigned fixtures (if necessary)

Assignment of articles to layout module versions (Shelf optimization)

Maintenance of placement data

Capacity check (internal capacity)

Maintenance of the flag for the OAPC

Release of a layout module version (status)

Ad hoc process

The ad hoc process takes place entirely in ERP (without the integration to BW) and uses thelayout concept.

In this scenario the focus is on the ad hoc process for assortment management of basicarticles, i.e. the process that takes place entirely in ERP (without the integration to BW) and usesthe layout concept.

The layout concept allows you to optimally structure the sales area of your stores in connection

with your assortment. At the same time, it forms the basis for using external space managementsystems.

The Layout Workbench is the main entry point for all functions relating to space managementand layout. One of its functions is that it can be used to create and change layout modules whichrepresent a specific area in a store (for example, a shelf).

You can use several versions of a layout module with different validity periods, for example,because planning is to take effect on shelves at a future date rather than immediately. The layoutmodule version assigns articles to a layout module for a certain time period, therefore enablinglayout modules to be scheduled. Each layout module version has a specific validity period whichcannot overlap that of any other version of that layout module.

To facilitate the assignment of the articles a number of different selection criteria are available

and it is also possible to create new articles (core master records) from the Layout Workbench.

The Layout Workbench also allows you to select articles that you would like to transfer to theOAPC (Operational Assortment Planning and Control) for further procurement activities.

A fixture is an optional enhancement to the layout concept that allows you to arrange your assortments on a placement-oriented basis. Fixtures are used to present goods in the sales areaavailable. Examples of fixtures are shelves, rounder or freezers.If you define fixtures and their capacity and assign them to the layout module version then thesystem automatically makes a capacity check when the article assignments to the layout moduleversion are saved.

Once the layout module versions are defined for the assortments/layout modules and the articleshave been assigned, the next step is to define which sites are able to use this assortment.

There is a user-friendly assortment assignment tool available for assigning sites to generalassortments. This tool allows you to sort the displayed sites, for example, according to region, or to select sites that are not yet assigned or new sites that have been created. The system

© SAP AG of 33




displays a list of the general assortments and their already assigned sites as well as a list of sitesfor which assignments are still possible. You then simply drag and drop the selected sites to thedesired assortment.

When the objects; article – layout module – general assortment – store have been assigned toeach other and thus the stores’ assortments have been defined as required the creation of thelisting conditions can be triggered from the layout workbench.

2 Prerequisites

2.1 Master Data and Organizational Data

For Customizing Settings take a look at 721 BB Config.-guide.

Default Values

Essential master and organizational data was created in your ERP system in the implementationphase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and

customers.

The business process is enabled with this organization-specific master data, examples areprovided in the next section.

Additional Default Values

You can test the scenario with other SAP Best Practices default values that have thesame characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Fashion Hardgoods Food

HIERARCHYNODE 1

B11200 (Men) B13100 (Home) B12600 (Sweets)

HIERARCHY

NODE 2

B11252 (Ties) B13154 (Accessories) B12631 (Mints)

ARTICLE 1 PCS-02-ART141 PCS-01-ART424 PCS-01-ART325

ARTICLE 2 PCS-02-ART144 PCS-02-ART421 PCS-01-RET323



MERCHAN-DISECATEGORY1

MC11451 MC14201 MC13202

VENDOR 1 PCS-V141 PCS-V421 PCS-V321

© SAP AG of 33




2.2 Checking User Parameters

Use

In this step, check the user parameters and the default settings.

Procedure

1. On the SAP Easy Access screen, choose Customize Local Layout (Alt+F12), and selectOptions….

2. In the Options dialog box, select Interaction Design → Visualization & Interaction.

3. Make sure the field of Show keys in All Dropdown Lists is selected.

4. Choose OK .

5. Access the transaction choosing one of the following navigation options:

Toolbar menu System → User Profile → Own Data

Transaction code SU3

6. On the Defaults tab, make the following entries:

Field name Description User actions and values Comment

Start menu W10T

Decimal Notation 1.234.567,89

Date Format 1 DD.MM.YYYY

7. Save the entries.

2.3 Roles

Use

The following roles must have already been installed to test this scenario in the SAP Netweaver Business Client (NWBC). The roles in this Business Process Documentation must be assignedto the user or users testing this scenario. You only need these roles if you are using the NWBCinterface.

Prerequisites

The business roles have been assigned to the user who is testing this scenario.

Business Role Technical Name Process StepRetail AssortmentPlanner

SAP_NBPR_ASSORTMENT_RT_S Various

Retail SeasonalPurchaser

SAP_NBPR_SEASONALBUYER_RT_S Various

3 Process Overview Table

Process StepExternalProcessReference

BusinessCondition

Business RoleTransactionCode

ExpectedResults

Define Fixtures Retail Assortment

WLMF

© SAP AG of 33




Process StepExternalProcessReference

BusinessCondition

Business RoleTransactionCode

ExpectedResults

Planner

Creating a

generalassortment

Retail

AssortmentPlanner

WSOA1

Creating alayout moduleversion andassigning afixture

Retail AssortmentPlanner

WLMVN

Assignment of articles tolayout moduleversion


WLWBN

Assignment of assortmentusers to theassortment(layout module)


WSOA6

Release thelayout moduleversion andcreating listingconditions


WLWBN

Copying layoutmodule

versions

Retail Assortment

Planner

WLMVN

Articlereplacement


WLWBN

Where-usedlist of Articles


WMSBA

Spacemanagement


WPLGN

Delete layoutlistingconditions


WLCN

4 Process Steps

4.1 Assortment Management Basic

4.1.1 Defining Fixtures (optional)

Use

© SAP AG of 33




A fixture is an optional enhancement to the layout concept that allows you to arrange your assortments on a placement-oriented basis. Fixtures are used to present goods in the sales areaavailable. Examples of fixtures are shelves, rounders or magazine racks.If you define fixtures and their capacity and assign them to the layout module version then thesystem automatically makes a capacity check when the article assignments to the layout moduleversion are saved.

Prerequisites

Fixture categories have to be defined. They describe the general appearance for a group of fixtures for example, rounder, shelf sections, or magazine racks. The actual fixtures are thendefined in more detail in the fixture maintenance (for example, shelf 4 m).

If the message: WLMF Flag for use of fixtures is not set appear, ran report(transaction) WLMVC to convert first fixture first.

Procedure

1. Access the transaction choosing one of the following navigation options:Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics→ Retailing → Master Data → Assortment/Listing →

Layout → Fixture Maintenance

Transaction code WLMF

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Retail Assortment Planner

(SAP_NBPR_ASSORTMENT_RT_S)

Business role menu Master Data → Assortment Layout → Fixtures→ Fixture

Maintenance

2. On the Fixtures Maintenance – Display screen, choose Display Change.

3. Choose New Entries.

4. On the Fixtures Maintenance - Change screen, make the following entries:

Field name Description User action and values Comment

Fixture SH_2M Enter

Description Shelf, width 2m

5. Choose Enter.

6. Make the following entries:Field name Description User action and values Comment

Fixture Categ. BPSH Shelf

Default Capacity 100

Dimension 01 Number

Hght. 1

Width 2

Depth 0,500

Unit of meas. M Meter

7. Choose Save.

© SAP AG of 33




8. The message: Fixture was generated successfully , displays and chooses Enter.

9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).

Or

Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).

4.1.2 Creating a General Assortment

Use

An assortment is an object to which articles are assigned for a specific time frame (validityperiod). The assignment of the individual articles to assortments is recorded in what are calledlisting conditions. An assortment user must be assigned to an assortment before it can use thearticles in that assortment for its various business functions. Assortment users can be either customers or sites.

There are two types of assortments: local assortments and general assortments. Localassortments are assortments that can only be assigned to sites. They are subdivided into twodifferent assortment categories: assortment category A is for stores and B for distribution

centers. General assortments are assortments for customers and have assortment category C.

Each site has one local, site-specific assortment that is automatically created by the systemwhen the site is created. In addition it can also be assigned to several general assortments if youhave activated multiple assignments of assortments to sites.

Multiple assignment means that a site may have several different assortments, and that anassortment may be assigned to several different sites, so it is a n:m assignment. Older releasesof the ERP system restricted you to a 1:1 assignment of assortments to sites. That is, each storecould have exactly one assortment, and each assortment could be assigned to exactly one store.Now you can choose between the old 1:1 assignment and the new n:m assignment. Take intoaccount that once you have activated multiple assignments in the productive system, you can nolonger switch back to the 1:1 assignment restriction.

Multiple assignments can significantly reduce the number of listing condition records in thedatabase. These results from the fact that articles are listed for assortments and not for sites andtherefore, the listing conditions created for an assortment are valid for all the sites assigned tothe assortment.

Prerequisites

Assigning several assortments to the same site is only possible if multiple assignments of assortments were activated in Customizing. (If multiple assignments is not active, each site hasexactly one local assortment, and no other assortments can be assigned to it.)

Procedure


Option 1: SAP Graphical User Interface (SAP GUI)


Assortment → General Assortment → Create

Transaction code WSOA1




Business role menu Master Data → Assortment Master Data → Assortment → Create

Assortments2. On the Create Assortment: Initial screen, make the following entries:

© SAP AG of 33





Assortment ASSORT1

Assortment Type BASI Basic Assortment

3. Choose Enter.

4. On the Create Assortment: Basic Data screen, make the following entries:


Assortment Description <description> (Field name is notdisplayed on thescreen)

Sales Organization 1000

Distribution Channel 10 Store Sales

Listing Conditions, Assortment

Set flag

Hierarchy B1

Hierarchy Node <Hierarchy node 1>

B11200 – Fashion

B13100 - Hardgoods

B12600 - Food

Enter the appropriatevalue from themaster data table(See 2 Prerequisites)

Space Select any value, for example, S1

50 sqm

Space profitability Select any value, for example, P3

low

Assortment dimensions are used to group sites with similar characteristics together so they can use the same assortment. Which assortment dimensions can be used isdefined by the assortment type. In this example the dimensions ‘Space’ and ‘SpaceProfitability’ were defined for the assortment type ‘BASI’.

An assortment can use up to three assortment dimensions.

5. Choose Save.

6. The message: Assortment XXX has been created , appears.

In the settings of the assortment type (BASI), which was used here for the creationof the general assortment, three flags were set that impact assortments of this typeas follows:

• the assortment can be assigned a layout module (flag ‘ Assign layout

module‘)

• the system automatically creates a layout module when a new assortment is

created (flag ‘Create layout module‘)

• the key for the layout module is always the same as that of the assortment

(flag ‘LayoutModule Not InpRdy ‘)


Or


© SAP AG of 33




8. Check the creation of the layout module. Access the transaction choosing one of thefollowing navigation options:



Layout → Layout Module Maintenance – New

Transaction code WLMMN




Business role menu Master Data→ Assortment Layout → Layout Module → Layout

Module Maintenance

9. On the Display Layout Module Maintenance screen, make the following entries:


Layout Module Enter the same key youused for the assortment

(for example, ASSORT1)

10. Choose Enter .

11. The new layout module that the system has automatically created for your assortment isdisplayed.

Field Ref. Customer : A layout module can be assigned to a number of layouts, andtherefore to a number of sites/customers (see general site maintenance in Retail).Space management is then carried out using a reference customer. The layout

module concerned must be assigned to the reference customer. This parameter isonly needed for external space management.


Or


4.1.3 Creating a Layout Module Version and Assigning aFixture

Use

Layout modules represent a specific area in a store. For every layout module, several versionswith different validity periods can be used. Within a layout module, the validity period of eachversion is unique and the versions cannot overlap. Due to the scheduling of layout modules inversions, seasonal variations, for example, for a shelf, can be planned.

At the layout module version level, there is also the special feature of layout module variants.Layout module variants each relate to one specific layout module version and are used to portrayregional or even store-specific differences in layout modules. The layout module variants haveexactly the same validity period as the version to which they refer. They contain only the delta of the articles from the layout module version, that is, only the additional articles and the articleswhich are to be excluded. This avoids redundant data retention. The variants are assigned toassortments. If multiple assignments of assortments to sites is activated, you can only assign thevariants to the local assortments, otherwise they would automatically affect all sites to which the

assortment concerned is assigned.

© SAP AG of 33




Prerequisites

A layout module was created.

Procedure




Layout → Layout Module Version Maintenance - New

Transaction code WLMVN




Business role menu Master Data→ Assortment Layout → Layout Module →

Maintenance of Layout Module Version

2. On the Maintenance of Layout Module Versions screen, make the following entries:


Layout Module ASSORT1

3. Choose Execute.

4. On the Layout Module Version Maintenance – Display screen, choose Display →Change. If

necessary, confirm all messages.

When a new layout module is created an initial layout module version with thenumber 0000 is automatically created for it. It has the status ’02 Released’, thecreation date of the layout module as the Valid From date and the 12.31.9999 as theValid To date.

The original version 0000 can never be deleted.

5. On the Layout Version Maintenance - Change screen, make the following entries for thelayout module version 0000:


Valid To <last day of thisyear>

6. Choose New Entries.

7. On the Layout Version Maintenance - Change screen, make the following entries:


Status Planned

Valid From <Jan 1st of nextyear>

Valid To <Jan 31st of nextyear>

8. Choose Enter.

© SAP AG of 33




A new version of the layout module is created with number 0001. Whenever thesystem creates a new version it automatically assigns the next available versionnumber.

For the creation of a new layout module version you can also copy an existingversion. The system copies the existing article assignments and all placement datafrom the existing version to the new version. If necessary, you can also copy allexisting layout module variants (but without their assignments to local assortments).

You can also cross-copy layout modules to copy a version to an existing version(this overwrites existing article assignments in the target version) or to a newlycreated version of another layout module.

9. Choose Save.

10. Select the new planned version 0001.

11. Choose (NWBC: More… →) Edit → Assignment to Fixtures.

12. Select the fixture you have created earlier.

13. Choose Assign Fixture.

14. Choose Back.

15. Choose Save.

16. In the overview of layout module versions the number of fixtures assigned to layout moduleversion 0001 has now changed from 0 to 1.


Or


4.1.4 Assignment of Articles to Layout Module Version

UseOnce the layout module versions are defined you can plan the articles to include.

To facilitate the assignment of the articles to a layout module version a number of differentselection criteria are available for the articles in the Layout Workbench and it is also possible tocreate new articles (core master records) from the Layout Workbench.

The Layout Workbench is the main entry point for all functions relating to space managementand layout.

Prerequisites

To permit the creation of a new article from the layout workbench a suitable maintenance group

has to exist.If you want to use the option of transferring articles from the layout workbench to the OAPC(Operational Assortment Planning and Control) this process has to be allowed, i.e., the relevantindicator in Customizing must have been set.

Also, the necessary settings for the OAPC need to be in place, for example:

• valid combinations of seasons, season years and rollouts

• active key figures for assortment type ‘BASI’

• article hierarchy level relevant for OAPC for assortment type ‘BASI’

(For more details regarding OAPC see Building Block 720 – Plan-driven Procurement )

Procedure

© SAP AG of 33







Layout → Layout Workbench – New

Transaction code WLWBNOption 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role



Business role menu Master Data → Assortment Layout → Layout Workbench →

Layout Workbench

2. On the Space Management: Layout Workbench screen, select Start: Layout Modules tabpage, and make the following entries:



Selection Date <Today>

3. Choose Execute.

4. Choose Expand All (F5 ).

5. Select your new planned layout module version 0001.

6. Choose Assign Articles

To select articles various selection options are available such as articles By Vendor ,By Layout , By Article Hierarchy or all the usual article selection criteria such asmerchandise category, article category, article type or article list for example (viaMultiple selection in tabstrip By Article).

Choose the By Article Hierarchy tab.

7. Make the following entries:


Hierarchy B1

Validity Date <Today>

Hierarchy Node <HIERARCHY NODE 1>

B11200 – Fashion

B13100 – Hardgoods

B12600 - Food

Enter the appropriatevalue from the master data table (See 2Prerequisites)

8. Choose Continue (Enter).

9. The system displays all articles that match the entered selection criteria that is, that areassigned to the article hierarchy node you entered. You can use a filter to restrict thedisplayed articles. Apply the filter to eliminate all articles with a unit of measure other than‘PC’ from the result list.

10. Choose Set Filter …

11. In the screen Define Filter Criteria under 1st step: Define the Filter Criteria choose Display Unit/Measure (which is displayed on the right side under the heading Column Set)

© SAP AG of 33




12. Choose the Add filter criterion (left pointing arrow) button. The column name now appears onthe left side under the heading Filter criteria.

13. On the Define Filter Criteria screen, under the 2nd step: Determine Values for Filter Criteria, choose the Filters button.

14. In Determine values for filter criteria screen, make the following entries:


Display Unit/Measure PC

15. Choose Execute (Enter).

16. Sort the list that was now reduced to only articles with UoM ‘PC’ by article numbers: Selectthe column Product .

17. Choose the Sort in Ascending Order button.

18. Select <Article 1>, <Article 2> and <Article 3> according to your product line (see 2.Prerequisites), press button CTRL (Control) on your keyboard to select all these articles inone step.

19. Choose the Assign Selected Articles button.20. Next define the placement data for the articles you assigned to the layout module. In

subscreen Mainten. of Article Assignm. make the following entries for the first article:


Facing 1

Fixture Number Using the F4-Helpselect SH_2M

Front 2

Max.qty 40

Opt.qty 30

Pres. qty 10

OAPC select flag via F4help

Transfer to OAPC

You have the possibility to transfer articles from the layout workbench to OAPC(Operational Assortment Planning and Control) for further processing. (See also4.1.6 Releasing the Layout Module Version).

You can manually select the articles that are to be transferred by setting the OAPCflag. If the articles are to be selected automatically according to a customer-specificlogic then you can use a BAdI that was provided for this requirement.

21. Make entries for the other two articles. You can copy the value of each field you maintainedfor the first article by selecting the cell and choosing Adopt For All.

22. Choose Save. (The status for the articles changes from yellow (new record) to green(processed record).)

23. Message: An over-reservation of fixture assignment 0000000XXX was found, is (possibly)displayed and choose Enter .

When you save the assignment of articles to a layout module version to which a

fixture has been assigned then the system automatically makes a capacity check.

© SAP AG of 33




In this example the capacity of the fixture was defined as 100 and if the maximumquantity of the assigned articles exceeded this quantity then the system issues themessage above. The message is only a warning which you can confirm by choosingContinue (Enter).

24. Choose Back

25. On the Layout Workbench: Entry Using Layout Module(s) screen choose Article Entry tocreate a new (core) article and assign it to the layout module.

In the background the system automatically selects a maintenance group thatdefines which article fields can be maintained when you are creating the core article.

26. In the Maintain Article dialog make the following entries:


Template Use the F4-Help to selecttemplate T1 under folder Layout workbench

You can maintain one or more templates for a maintenance group where you enter default data, for example, for the initial screen for core article master dataprocessing (for example, article type, article category, etc.) and the article creationstatus for core articles.

27. A number of fields get filled with default entries from the template. Check/make the followingentries:


Article number (Leave field blank) The system will

automaticallygenerate a number

Article Type HAWA Trading Goods

Mdse Catgry <MerchandiseCategory 1>

MC11451 – Fashion

MC14201 – Hardgoods

MC13202 - Foods


Artl Category 00 Single article

Purchasing Org. 1000

Vendor <Vendor 1>

PCS-V141 – Fashion

PCS-V421 – Hardgoods

PCS-V321 - Foods


Info Type 0

Sales Org. 1000

Distr.Channel 10

Site (Leave field blank)

Article (Leave field blank)

© SAP AG of 33




Template defaulted - do notchange

28. Choose Continue (Enter).

29. On the Maintain Article xx screen, select Definition /HEAN (under article master views Unitsof Measure), confirm and make the following entries:


AUn PC

LUn PC

BUn X

OUn X

SUn X

D/I X

Ct IE Instore GTIN (int.

assignment possible)

30. Next select Measurements/Volumes and make the following entries:


Length Enter a value

Width Enter a value

Height Enter a value

Unit M

31. Then select Descriptions and make the following entries:


Language EN

Article Description Enter a description Replace the default

32. Continue with Basic Data (under view Other Field Groups) and confirm, and make thefollowing entries:


Status 03 Procurement

Season 0000 No season

Season Year <next year>

Tax class. 1

Purch. Group 100

The field Status refers to the article creation status. Creation status 03 was set up toidentify core articles created in the layout workbench. You need to complete the corearticle at a later stage to make it an article that can be used in all relevantapplications. You can use the article monitor (transaction WRFMATMON) to do thefollow-on processing of the core articles and there you can select articles using thecreation status.

33. Now select Sales, confirm the message, and make the following entry:


© SAP AG of 33




Sales Org. 1000

Distr.Chl 10

ItemCatGrp NORM

34. Finally select Article Hierarchy and make the following entry:


Hierarchy Node <Hierarchy node 2>

B11252 (Ties) – Fashion

B13154 (Accessories) –Hardgoods

B12631 (Mints) – Foods


35. Choose Save and Exit.

36. Now maintain the placement data for the new article. To do so, select your new article andchoose Assign

37. Maintain the following entries in the subscreen Mainten. of Article Assignm.


Facing 2

Fixture Number Using the F4-Helpselect SH_2M

Front 1

Max.qty 10

Opt.qty 8

Pres. qty 3

OAPC NO flag

38. Choose Save. (If a message relating to an over-reservation appears just confirm it.) Thestatus of the article changes to green. Leave the layout workbench.


Or


4.1.5 Assignment of Assortment Users to the Assortment(layout module)

Use

An assortment user has to be assigned to an assortment before it can use the articles in thatassortment for its various business functions. Assortment users can be either sites (internalcustomers) or external customers. External customers can only be assigned to assortments inthe assortment transactions (for example, WSOA2) whereas sites can be assigned either in theassortment transactions or using the new assortment assignment tool (WSOA6). The tool offersan overview of the assigned sites and the unassigned sites and new assignments can bemaintained easily by choosing sites from the list of unassigned sites and then using drag anddrop. When you assign the assortment users – in this case sites – to assortments you canmaintain validity dates for the assignment.

Procedure

© SAP AG of 33







Assortment → General Assortment → Assign Assortment User

Transaction code WSOA6Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role



Business role menu Master Data → Assortment Master Data → Assortment →

Assortment Maintenance Tool

2. On the Assortment Assignment Tool screen, make the following entries:



3. Choose Execute.

4. On the Assortment Assignment Tool screen, select the following sites from the list of available sites on the right side of the screen: M011, M012, M013 and M014 and assignthem to the assortment by dragging and dropping them to the assortment (layout module) onthe left side of the screen. (Alternatively you could use the button Assign Sites to an Assortment to make the assignment.)

5. To maintain the validity period of the assignment of a site first select the site(s), for example,M011.

6. Choose Maintain period .

7. On the Maintain Assignment Period screen, make the following entries:


Valid from <Jan 1st of nextyear>

8. Choose Transfer Assignment Period (Enter ).

9. Choose Save.

10. The message: Creating Article Segments appears.

11. Choose Update Process to generate the article segments immediately.

12. The message: Data was saved , appears.


Or


4.1.6 Releasing the Layout Module Version and CreatingListing Conditions

Use

The listing conditions define the periods of time during which an article can be purchased,received and sold by an assortment owner. The system uses a listing procedure to create thelisting conditions. Listing procedures determine which checks the system makes when making

the assignment of articles to assortments (and thereby to the stores, distribution centers or customers using those assortments). SAP delivers a number of predefined listing procedures

© SAP AG of 33




which contain different kinds of checks, for example, a merchandise category check or a layoutcheck.

A layout module version has to be released before listing conditions can be created. Thereleasing of the layout module version triggers the transfer of the selected articles to OAPC.

PrerequisitesTo be able to use the listing functions via the layout, exactly one listing procedure must bedefined in Customizing as the standard listing procedure for the Layout Workbench. In thestandard delivery, the field in the listing procedure “B3 – Basic procedure: layout check” is set asdefault. If this parameter is not set in any of the listing procedures used, listing via layout cannottake place.

Only the articles positioned on the shelf, that is, articles assigned to a layout module version witha facing > 0, are listed.

Prerequisite for transferring selected articles to the OAPC is that you have allowed such atransfer to take place and that all settings required for working with the OAPC have been made.

Procedure1. Access the transaction choosing one of the following navigation options:




Transaction code WLWBN





Layout Workbench

2. On the Space Management: Layout Workbench screen, select the Start: Layout Modules tab.

3. On the Space Management: Layout Workbench screen, make the following entries:



4. Select Execute.

5. Select Expand All.

6. For version 0001 click on the status Planned .

7. Confirm the message: Change the status? with Yes.

8. The status has changed to Released .

9. To create the listing conditions, select your layout module version.

10. Choose (NWBC: More …→ ) Edit from menu bar.

11. Choose Create Assortments. Confirm the message if it appears.

12. The system displays the assortment that is assigned to the layout module version and a redtraffic light to indicate that the listing has not taken place yet.

13. Choose Continue.14. A dialog box, Result is displayed, which informs you that listing started.

© SAP AG of 33




15. Confirm the message with Continue (Enter ), and leave the layout workbench.

16. There are various options for displaying the created listing conditions. Choose the treedisplay of listing conditions under the evaluation transactions for the assortments. Accessthe transaction choosing one of the following navigation options:


Or





Evaluations → For Article → Tree Display of Listing Conditions

Transaction code WSL11

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business RoleBusiness role Retail Assortment Planner


Business role menu Master Data → Assortment Master Data → Listing condition →

Evaluation of Listing conditions

2. On the Evaluation of Listing Conditions screen, make the following entries:


Article *

Assortment ASSORT1

3. Choose Execute.

By default the overview has the breakdown Article – Site – Assortment. You canchange it by choosing Change Breakdown and using the arrows to change theposition of the sort criteria, for example, to Assortment – Site – Article, which might

lead to a clearer overview.

Amongst other things the list contains the following information: the articles listed for the assortment, the sites that are assigned to the assortment, the validity of the

listing conditions (validity of the layout module version) and the listing source (L –Layout workbench).

The number of the assortment module is also displayed. This number is not to beconfused with the layout module number. Each assortment consists of the contentsof the assortment modules assigned to it. Listing conditions can be generated by avariety of functions but assortment modules are always used. There are varioustypes of assortment module depending on the way they are created. An assortmentmodule is generated automatically, for example, when articles are listed from thearticle maintenance, the system creates the profile modules, or when articles arelisted during promotion processing then promotion modules are created. Other assortment modules are created manually, for example, the exclusion module(module that cancels the listing for the articles contained in it), the rack jobber module (module with articles for which a vendor handles the delivery andpresentation in the stores), or the standard module (module containing a freelydefinable selection of articles).

© SAP AG of 33




The assortment module that is created when articles within a layout module versionare listed has the assortment module type shelf module. This type of assortmentmodule cannot be maintained manually.

4. When you set the status of the layout module version to released, this automatically triggersthe transfer of the articles to the OAPC. (The transfer only takes those articles into accountthat you have specifically selected for this process by setting the flag ‘OAPC’ under theassignments).

When assigning a site to an assortment, article segments may need to be createdfor the site. This is a time intensive process. You can either create the articlesegments in the update or you can define a separate job for it (see message detailsfor more information).

There is also the option of manually starting the transfer in case the automatictriggering does not take place by using the button Trigger OAPC Transfer.

5. To check if the transfer was triggered go back into the Layout Workbench, access thetransaction choosing one of the following navigation options:









Layout Workbench

6. On the Space Management: Layout Workbench screen, select the Start: Layout Modules tab.




8. Select Execute.

9. Select your layout module.

10. Select Display OAPC Log to check if the transfer was successful (green symbol). If theselected items were transferred successfully note the number of the purchasing listdisplayed in the log.

11. To access the purchasing list, choose one of the following navigation options:



Operational Assortment Planning and Control → Maintain

Purchasing List

Transaction code WRFAPC02

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business RoleBusiness role Retail Seasonal Purchaser

© SAP AG of 33




(SAP_NBPR_SEASONALBUYER_RT_S)

Business role menu Purchasing → Seasonal Purchase Management → Purchasing

List → Operational APC: Change

12. On the Operational Assortment Planning and Control: Change screen, make the following

entries:Field name Description User action and values Comment

Purchasing list <Number> Number from the log inthe LWB

13. Choose Enter.

14. If no purchasing list exists for the relevant period to which the transferred articles can beadded then the system creates a new purchasing list. In this case the system needs you tomaintain the assignment of the new purchasing list to a purchasing organization and apurchasing group before you can display it.

15. In case a dialog box appears asking you to make such an assignment, make the followingentries:


Purchasing Org. 1000

Purch. Group 100

16. Choose Enter.

17. You can see the transferred articles (the three you selected for transfer in 4.1.4) as well asthe planned quantities for your new assortment for the key figure Fixed Allocation of InitialBuy (IF).

Planning inside the OAPC for assortment type BASI you have less functionalitiesthen for assortment type FASH . For assortment type BASI, you plan only for the keyfigure IF (Fixed Allocation of Initial Buy) but not IV (Reallocation of Initial Buy) asbasic articles are subject to a pull process for replenishment and thus there is noneed to plan a reallocation.

For IF the system determines the planned quantity by using the Optimal quantity youhave maintained for the article in the Layout Workbench.

Optionally you can also plan quantities for the key figure PA (Putaway) that is, theamount of articles that are automatically stored at the distribution center. The systemdoes not propose a quantity for it.

For more details regarding the purchasing list see Building Block 720 – Plan-driven

Procurement.18. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).

Or


4.2 More Features of the Layout Workbench

4.2.1 Copying Layout Module Versions

For the creation of a new layout module version you can also copy an existing version. Thesystem copies the existing article assignments and all placement data from the existing version

to the new version. If necessary, you can also copy all existing layout module variants (butwithout their assignments to local assortments).

© SAP AG of 33




You can also cross-copy layout modules to copy a version to an existing version (this overwritesexisting article assignments in the target version) or to a newly created version of another layoutmodule.

Procedure

1. Access the transaction choosing one of the following navigation options:Option 1: SAP Graphical User Interface (SAP GUI)


Layout → Layout Module Version Maintenance - New

Transaction code WLMVN




Business role menu Master Data→ Assortment Layout → Layout Module →

Maintenance of Layout Workbench Version

The maintenance of layout module versions can also be accessed from the layoutworkbench via (NWBC: More… )GoTo Version Maintenance

2. On the Maintenance of Layout Module Versions screen, make the following entries:



3. Choose Execute.

4. Choose Display

Change.5. Select the version you have created earlier (0001).

6. Choose Copy with Articles.

7. Confirm the Prompt: Copy the layout module version? with Yes.

8. The system generates version 0002 with status Planned and a Valid From date that beginsthe day after the Valid To date of the previous version and a Valid To date of 12.31.9999.

9. Choose Save. The number of assigned fixtures changes to ‘1’ as not only the articles werecopied from the other layout module version but also the assignment to the fixture with theplacement data.


Or


4.2.2 Article Replacement

Procedure

1. You can replace an article in an existing layout module version in the layout workbench.There is also a separate transaction for article replacement.




© SAP AG of 33










Layout Workbench

3. On the Space Management: Layout Workbench screen, select Start: Layout Modules tabpage.




5. Choose Execute.

6. Choose Expand All .

7. Select layout module version 0001.

8. Choose Article Assignments.

9. Select <Article 3>.

10. Choose Assignments.

11. On the Mainten. of Article Assignm. sub screen, select the article.

12. Choose Replace Article.

13. On the Article Replacement screen, make the following entries:


Article New <ARTICLE 4> Choose Enter

Unit of Meas.New PC Choose enter beforeentering UOM

14. Choose Replace Article.

15. The status of the old article changes to red (deleted data record) and the new article isdisplayed with status yellow (new data record). The article assignments are copied from theold article to the new article.

16. Choose Save. Confirm the message. The status of the new article changes to green (datarecord was processed) and the old article disappears from the screen.


Or


Since you have replaced an article in a layout module version that was alreadyreleased, the listing conditions that were created at the time of the release no longer reflect your current situation as you would want the new article to be listed for theperiod of the layout module version instead of the previously assigned article. Whenyou use listing via layout you can use the report RWSPORT07L to check if anylayout relevant changes have occurred and then to adapt the listing based on these

changes. Prerequisite for using this mass maintenance transaction for listing is thecreation of change documents. The report would be scheduled and executed daily in

© SAP AG of 33




batch. You can also trigger this automatic relisting manually, however, by followingthe next steps.



Mass Maintenance → From Change Documents → Relist

Automatically by Changing Layout Master Data

Transaction code WSM4L





Automatic Relisting of Layout Data

1. On the Automatic Relisting by Changing Layout Data screen, make the following entries:


Assortment ASSORT1

Layout/Assortment Changes

Select

Layout Module Changes Select

Layout Module VersionChanges

Select

Layout Module Variant Changes

Select

Article Assignment

Changes

Select

Time limit: DocsSince Last Successful Run

Select

Date from (today’s date isdefaulted)

2. Choose Execute.

3. Confirm the dialog box with Enter, which states when the report was last run.

4. The log displays the number of changes that were carried out.

5. Leave the transaction and go to the assortment evaluation to check that the listing conditionswere updated correctly. Access the transaction choosing one of the following navigationoptions:



Evaluations → For Assortments → Article per Assortment

Transaction code WSL10




Business role menu Master Data → Assortment Reports → Evaluations → Articles in

© SAP AG of 33




Assortment

6. On the Listing Conditions per Assortment screen, make the following entries:


Assortment ASSORT1

7. Choose Execute

The system displays all articles that are listed for the assortment and the validityperiod of the listing conditions. To display the listing conditions you could also haveused various other transactions listed in the menu under the evaluations, for example, WSL11 (Tree Display of Listing Conditions) or WSL1 (Listing Conditions).The results are displayed a little differently in each one – select the one that suitsyou best.


Or


4.2.3 Where-used List of Articles

You can use this function to determine which layout module versions contain which articles.

Procedure




Layout → Where-Used List of Articles

Transaction code WMSBA




Business role menu Master Data → Assortment Layout → Article→ Article Where-

Used List

2. On the Where-Used List for Article screen, select the By Article Hierarchy tab.

3. Make the following entries:


Hierarchy B1

Hierarchy Node <HIERARCHY NODE 1> Enter the appropriatevalue from themaster data table(See 2 Prerequisites)

Validity Date of Version <Jan 1st next year>

4. Choose Execute.

5. The system displays the layout modules and versions it has determined for the selectedarticles (articles of the specified hierarchy node) and for the validity date. It also displays thedetails of the assignments.

© SAP AG of 33





Or


4.2.4 Space Management

There are several space management programs available that manage store merchandiseplacement. They determine the optimum location for articles within shelves and calculate theappropriate amount of space to be allotted to the articles, based on a number of factors such assales volume, margins, and so on. You can integrate these external programs with the SAPsystem, with data flow in both directions.

The following data can be transferred from the SAP system to the external space managementprogram:

• Article number & article short text

• Units of measure

• Article dimensions (size)

• EAN/UPC

• Article type

• Merchandise category

• Manufacturer / vendor

• Prices (cost and retail)

• Stock quantities

• Sales quantities

• Placement information

o Multiple placement indicator (article is on display in more than one place in a

site) and number of placements for these articles

o Facings (number of articles placed next to each other in the shelf)

o Fronts (number of articles placed above each other in the shelf)

o Shelf and location within the shelf

o Optimum shelf quantity (optimum quantity of an article that fits in the shelf

section)

o Maximum shelf quantity (maximum quantity of an article that fits in the shelf

section)

A space management profile that is assigned to the site master of a store defines which data isexported. You can specify whether the purchase prices, sales prices, the sales data and thestock data are read for the articles. Sales data and stock data can either be read from the LIS or from the SAP BW.

The space management profile also contains an identifier of a function module which calls theexternal space management program. There are a number of different function modulesavailable to handle different approaches when calling the external space management programand exporting data. For more information about the available function modules see the helpdocumentation in the space management profile and the function module documentation. Thesefunction modules serve only as templates for creating customer-specific function modules. Thismeans that when using the interface, one of the function modules has to be copied and adaptedto meet the customer’s own requirements.

The following data can be transferred from the external space management program to the SAPsystem:

© SAP AG of 33




• Article dimensions (size)

• Shelf and location within the shelf

• Facings (number of articles placed next to each other in the shelf)

• Fronts (number of articles placed above each other in the shelf)

• Presentation quantity (minimum amount of positioning units for an article that is always

to be stored in a particular shelf for strategic visual and sales reasons)

• Optimum shelf quantity (optimum quantity of an article that fits in the shelf section)

• Maximum shelf quantity (maximum quantity of an article that fits in the shelf section)

For importing data from the space management program back to SAP the posting BAPIBapi_Sitelaymod_Change is used. The following data is updated in SAP:

• Layout module versions, that is, assignment/deletion of articles to/from a layout

module version

• Article placement data in the layout module

• Creation of listing conditions

• Layout module variants and their assignment to the local assortments of the stores

• Article dimensions

For more information on the functions of the BAPI, see the function module documentation.

The following report displays all article master data and movement/transaction data that can beused for an external space management program. From the report, the space management planassigned to the layout module version can also be displayed, and the data can be exported.

Procedure




Layout → Space Management

Transaction code WPLGN




Business role menu Master Data → Assortment Layout → Article → Space

Management

2. On the Space Management: Display Articles in Layout Module screen, make the followingentries:


Customer M014


Layout Module Version 0001

Price Determination Date Use the defaultdate

3. Choose Execute.

© SAP AG of 33




4. Select Enter to confirm the warning message that M014 is not the reference customer for thelayout module.

5. The system displays all article master data and movement/transaction data for the selectedlayout module version.

By choosing the button Space Management the communication with the externalspace management program would then be started if such a program was installed.The assortment can then be optimized in the external program, that is, the optimumlocation for articles within shelves is determined and the appropriate amount of space to be allotted to the articles is calculated, and this optimized data can then beimported into the SAP system again.


Or


4.3 Deleting Layout Listing Conditions

Use

If you have created listing conditions using the layout listing you can use a special transaction todelete all listing conditions of a layout module if they are no longer required.

Procedure



SAP ECC menu Logistics→ Retailing → Master Data → Assortment/Listing → Layout → Deletion of Layout Listing Conditions → Deletion of

Layout Listing Conditions Using Layout Module

Transaction code WLCN





Delete Listing Conditions from LM

2. On the Delete All Listing Conditions From Layout Module screen, make the following entries:Field name Description User action and values Comment


Test run Select

3. Choose Execute.

4. The system displays the assortment module (shelf module) that would be deleted along withits listing conditions if you started the transaction without the Test run flag.


Or


© SAP AG of 33




The system also displays the number of entries that would be deleted from thevarious listing tables. If you have deleted layout listing conditions by mistake you canalways return to the layout workbench and list the layout module including all theassigned articles again. If you enter the layout workbench using the Start:

Assortments tab then you can see at a glance which layout module versions of theassortment are listed or not, as next to each layout module version the systemdisplays a traffic light based on the listing.

Deleting listing conditions does not have the same consequences asdiscontinuation. The deletion of listing conditions has no impact on the article master as such – it remains active but the article cannot be ordered if no listing conditionsexist. Discontinuation has greater implications as it removes the article master record from the database eventually (after a specified time interval), along with alldata for that article, including the purchasing and listing conditions.

(For details on discontinuation see Building Block 711 – Item Management ).