Merchandising Range Management Course (Part 1 - General Information) V2.1_BR4.5

July 2011 Version 2.1 – BR4.5 Copyright © by Woolworths Limited

SAP Master Data for Merchandising

Range Management

Part 1 - General Information

Reference Guide

Range Management | Part 1 - General Information

July 2011 - Version 2.1 – BR4.5 Page 2

Version Control

Version Date Change Author

1.2 27/04/11 Convert to new template Vicki Korb

1.2 06/05/11 Text updates Vicki Korb

2.0 17/05/11 Final Vicki Korb

2.1 27/07/2011 Align Article Type and Category with BM/AA Materials & text correction updates.

David Windle

Approval

Name Position Signature Date

Nandi Iyer Solutions Architect Verbal sign off 06/11/11

Training Material Changes

Session Section Page No Change Details

Legend 6 Update Legend to include Transaction symbols

2 2.3 19 Update Characteristics information

2 2.7 20 Update Merchandise Category Maintenance Form

7 7.2 117 4 new diagrams to explain Listing & Ranging process

7 7.2 117 Ammendment to the Ranging diagrams and explanation.

5 5.2 – 5.3 68 – 69 Replaced with the Tables from the BM/AA material.



Contents

Contents ................................................................................................................................. 3

Legend .................................................................................................................................... 6

Module Information ................................................................................................................ 7

Course Objectives ............................................................................................................... 7

How To Use This Workbook ................................................................................................ 7

Session 1 – Introduction – SAP Master Data for Merchandising ........................................ 8

1.1 – Woolworths SAP Approach - „Adopt & Adapt‟ ............................................................. 8

1.2 – Why SAP Retail .......................................................................................................... 8

1.3 – SAP Merchandising System Supporting Our Service Delivery .................................... 9

1.4 – SAP Master Data Structures ....................................................................................... 10

1.5 – Distribution Chains ..................................................................................................... 10

1.6 – Site (Store or DC) ....................................................................................................... 11

1.7 – Site Groups ................................................................................................................ 12

1.8 – Customers .................................................................................................................. 13

1.9 – Vendor ........................................................................................................................ 13

1.10 – Ranging .................................................................................................................... 14

Ranging Summary .......................................................................................................... 15

Important Note on Business Rules .................................................................................. 15

Session 2 - Introduction to Merchandise Category Hierarchy ............................................ 16

2.1 – Objectives ................................................................................................................... 16

2.2 – Master Data ................................................................................................................ 16

2.3 – Merchandise Category Hierarchy (MCH) Overview .................................................... 17

2.4 – Characteristics ............................................................................................................ 19

2.5 – Characteristic Values .................................................................................................. 20

2.6 – Request new Merchandise Category or new Merchandise Category Hierarchy Level 20

2.7 – Merchandise Category Maintenance Form – New Hierarchy Level Request ............... 20

2.8 – Reference Article ........................................................................................................ 24

2.9 – Process of Re-classifying a Merchandise Category .................................................... 24

2.10 – Standard Transactions .............................................................................................. 24

2.11 – WG24 – Display Merchandise Category ................................................................... 25

2.11.1 – Demonstration – WG24 – Display Merchandise Category ................................. 25

2.11.2 – Exercise – WG24 – Display Merchandise Category .......................................... 29

2.12 – WGUS – Merchandise Category Usage.................................................................... 29

2.12.1 – Demonstration – WGUS – Merchandise Category Usage ................................. 29

2.12.2 – Exercise – WGUS – Merchandise Category Usage ........................................... 33

2.13 – Business Policies ...................................................................................................... 34

2.14 – Session Summary .................................................................................................... 34

Session 3 - Site ...................................................................................................................... 35

3.1 – Objectives ................................................................................................................... 35

3.2 – Standard Transactions................................................................................................ 35

3.3 – WB03 – Display Site ................................................................................................... 35

3.3.1 – Demonstration – WB03 – Display Site................................................................. 36



3.3.2 – Exercise – WB03 – Display Site .......................................................................... 43

3.4 – Vendor Zone Pricing Site Groups Overview ................................................................ 44

3.5 – WB86 – Display Sites assigned to a Site Group ......................................................... 44

3.5.1 – Demonstration – WB86 – Display Sites assigned to a Site Group ....................... 45

3.5.2 – Exercise – WB86 – Display Sites assigned to a Site Group ................................ 49

3.6 – WB87 – Display Site Groups assigned to a Site ......................................................... 50

3.6.1 – Demonstration – WB87 – Display Site Groups assigned to a Site ....................... 50

3.6.2 – Exercise – WB87 – Display Site Groups assigned to a Site ................................ 54

3.7 – Business Policies ........................................................................................................ 54

3.8 – Session Summary ...................................................................................................... 54

Session 4 – Vendor Introduction and Maintenance ............................................................. 55

4.1 – Objectives ................................................................................................................... 55

4.2 – Vendor ........................................................................................................................ 55

4.3 – Vendor Sub-range ...................................................................................................... 55

4.4 – Vendor Introduction Process ...................................................................................... 56

4.5 – Vendor Maintenance Process – Non Trading Terms Changes ............................... 56

4.6 – Vendor Maintenance Process – Trading Terms Changes ...................................... 57

4.7 – Super Remit to Vendor ............................................................................................... 57


4.9 – XK03 – Display Vendor to a Site ................................................................................. 58

4.9.1 – Demonstration – XK03 – Display Vendor to a Site .............................................. 58

4.9.2 – Exercise - XK03 – Display Vendor ...................................................................... 65

4.10 – Forms ....................................................................................................................... 65

Vendor Maintenance Form .............................................................................................. 66


4.12 – Session Summary .................................................................................................... 67

Session 5 – Article Processes and Forms ........................................................................... 68

5.1 – Objectives ................................................................................................................... 68

5.2 – Article Category .......................................................................................................... 68

5.3 – Article Type ................................................................................................................ 69

Sales Set Overview......................................................................................................... 71

Pack Breakdown Overview ............................................................................................. 72

CASS vs SAP Article Numbers ....................................................................................... 73

Display Units Overview ................................................................................................... 75

5.4 – System Landscape Diagram (SMART / CASS / SAP) ................................................ 76

5.5 – New Article Creation Workflow Process ...................................................................... 77

5.6 – Workflow Overview ..................................................................................................... 79

5.7 – Agent Determination Overview ................................................................................... 79


5.9 – MM43 – Display Article ............................................................................................... 80

5.9.1 – Demonstration – MM43 – Display Article ............................................................. 80

5.9.2 – Exercise – MM43 – Display Article ...................................................................... 105

5.10 – New Article Forms .................................................................................................... 106

Forms required for each Article Scenario ........................................................................ 107

5.11 – GS1 Overview .......................................................................................................... 107

5.12 – PRICAT Overview .................................................................................................... 108




5.14 – Session Summary .................................................................................................... 108

Session 6 – Searching Hints and Tips and Additional Information .................................... 109

6.1 – Objectives ................................................................................................................... 109

6.2 – Searching in SAP ....................................................................................................... 109

Site Search – WB03 ........................................................................................................ 110

Article Search – MM43 .................................................................................................... 111

Assortment Search – WSOA3 ......................................................................................... 112

Vendor Search – XK03 ................................................................................................... 113

6.3 – Setup Favorites in SAP ............................................................................................... 114

6.4 – Setup Parameter IDs (PIDs) ....................................................................................... 114

6.5 – Difference between Layouts and Variants................................................................... 116

6.6 – Session Summary ...................................................................................................... 116

Session 7 – Listing and Ranging Theory ............................................................................. 117

7.1 – Objectives ................................................................................................................... 117

7.2 – Listing vs Ranging ...................................................................................................... 117

7.3 – Assortment and Types ................................................................................................ 119

What is an assortment? .................................................................................................. 119

Types of Assortments ..................................................................................................... 120

7.4 – Standard Transactions ........................................................................................... 121

7.5 – WSL10 – Listing Conditions for an Assortment ........................................................... 121

7.5.1 – Demonstration – WSL10 – Listing Conditions for an Assortment ......................... 121

7.5.2 – Exercise – WSL10 – Listing Conditions for an Assortment .................................. 125

7.5.3 – Demonstration – WSL11 – Evaluation of Listing Conditions ................................ 125

7.5.4 – Exercise – WSL11 – Evaluation of Listing Conditions ......................................... 131

7.6 – WSOA3 – Display Assortment .................................................................................... 131

7.6.1 – Demonstration – WSOA3 – Display Assortment .................................................. 132

7.6.2 – Exercise – WSOA3 – Display Assortment ........................................................... 137

7.7 – Ranging and Source of Supply (SoS) ......................................................................... 137

7.8 – Article Scenarios displaying how SoS is Determined .................................................. 141

7.9 – Session Summary ...................................................................................................... 146

Module Summary ................................................................................................................... 147

Relevant Links ..................................................................................................................... 147

Need More Help? ................................................................................................................ 147



Legend

The following symbols represent:

Objectives and Summary

Indicates a Session Objective or a Session Summary

Activity

Activity led by the Facilitator, for example a group discussion, which aims to explain theory or concepts.

Demonstration

Indicates a practical demonstration is required by the Facilitator or a relevant subject matter expert. The steps in the demonstration are listed underneath.

Exercise

Participants work through a live transaction in the training client on their own. If they require support they should refer to the Work Instruction before receiving assistance from the Facilitator.

Question

Indicates a question that the participant is required to answer in their workbook.

Important Note

Indicates important information that needs to be highlighted to the participant.

Transaction symbols

R/O/C

SAP Field Table Entries

R = Required

O = Optional

C = Conditional

Alert

Indicates a warning / alert for current step and what to do

Function Information

Indicates helpful hint / information regarding a particular step or function

Attention

Important point that must be read regarding current step or function



Module Information

Course Objectives

The objective of this course is to understand and use SAP transactions to perform the business processes that make up the business processes that the Merchandise / Space Analyst are responsible for:

At the end of this module, you will be able to:

Understand the Merchandise Category structure

Enquire on Merchandise Category information

Enquire on a Site

Understand the Vendor Process

Understand the Article Introduction Process

Search for master data information using different search methods

Setup favourites for transactions used regularly

Setup Parameter IDs

Understand how layouts and variants are used

How To Use This Workbook

The purpose of this workbook is to provide a roadmap of the module including:

Module Overview

Business Procedures

Business Policies

Scenarios for Demonstrations and Exercises

Session and Module Summaries



Session 1 – Introduction – SAP Master Data for Merchandising

1.1 – Woolworths SAP Approach - ‘Adopt & Adapt’

Woolworths have selected SAP (Systems Applications and Product) as our core merchandising system that will support our future business growth and expansion

SAP will be implemented as a standard tool with minimal customisation - referred to as a Vanilla approach

Standard SAP functionality will be adopted, with business processes adapted where required

Business processes may require redesign to support standardisation to ensure one solution for all

Any processes which cannot be supported by SAP standard functionality will be met by custom developments

1.2 – Why SAP Retail



1.3 – SAP Merchandising System Supporting Our Service Delivery

PRODUCTS• Add new products

• Understand best sellers

STORE RANGING• Ensure the right products are

available, based on customer

preference

STOCK AVAILABILITY• Order and deliver stock to

stores

• Provide information to ensure

the right amount of stock, in

the right place, at the right

time

CUSTOMER PURCHASES• Ensure prices are competitive

• Process sales information

• Order more stock every time

a product is sold

PROMOTIONS• Offer

customers

the best

prices and

promotions

PERFORMANCE• Report on sales

and profit

• Provide

shareholder

information

• Monitor the success

of the company for

customers

and shareholdersCUSTOMER

The SAP Merchandising

System provides us with

the information and

ability to offer our

customers a better shopping experience

each time they shop with

us

SAP for Woolworths Current and Future



1.4 – SAP Master Data Structures

Organisational Building Blocks

Distribution Channels

(Distribution Chain)

The method by which items are sold to a customer, for example

Retail Sales.

Sales Districts & AreasThese can be used to group multiple stores for the analysis of

sales. e.g. Regions and Sales Districts

Sites

(Stores & Distribution Centers)

Store: location where a product is sold to a customer.

Distribution Centres: location where products are distributed

from. Distribution centers are reccognised as part of the retail

org structure as they not only represent sites, but other master

data objects as well. This is also applicable to stores.

Company CodeThe top tier of an organisational structure. Defines the

organisation as an individual legal entity.

This is the high level management of inventory and

procurement across the business.Purchasing Org

The sales org. manages the sale and distribution of products

throughout the different business units (Divisions). Sales Organisations

(Distribution Chain)

1.5 – Distribution Chains

Australia FLP – Existing Homeshop Model

WOW HomeshopCo Code 1040Sales Org 1040

WOW PetrolCo Code 1000Sales Org 1020

Co

nsu

me

rs

Thomas DuxCo Code 1000Sales Org 1025

BWSCo Code 9020/1000Sales Org 1010

WOW SmktCo Code 1000Sales Org 1005

20

–O

n-l

ine

DCsCo Code 1000Sales Org 1005

40 - Wholesale

Customer

Dan MurphyCo Code 9020/1000Sales Org 1015

30

-D

istr

ibutio

n

10

-R

eta

il

Banners

Sales Organisations

Distribution Channel

Banners

Sales Organisations


Big W DCsCo Code 1000Sales Org 1050

30

–D

istr

ibu

tion

Big W StoresCo Code 1000Sales Org 1050

10

–R

eta

il

Con

su

me

rs

Distribution Chains

1005/30 For DCs to Stores

1005/10 For Smkt stores selling to consumers

1005/40 For DCs wholesaling to consumers

1040/20 For Homeshop selling to consumers with

warehouse fulfilment

1010/10 For BWS (WOW and ALH owned stores)

selling to consumers

1015/10 For Dan Murphy (WOW and ALH owned

stores) selling to consumers

1020/10 For WOW Petrol selling to consumers

1025/10 For Thomas Dux selling to consumers

1050/30 For Big W DCs to Stores

1050/10 For Big W stores selling to consumers

Distribution Chains

1005/30 For DCs to Stores

1005/10 For Smkt stores selling to consumers

1005/40 For DCs wholesaling to consumers

1040/20 For Homeshop selling to consumers with

warehouse fulfilment

1010/10 For BWS (WOW and ALH owned stores)

selling to consumers

1015/10 For Dan Murphy (WOW and ALH owned

stores) selling to consumers

1020/10 For WOW Petrol selling to consumers

1025/10 For Thomas Dux selling to consumers

1050/30 For Big W DCs to Stores

1050/10 For Big W stores selling to consumers



New Zealand

NZ DCs

Co Code

2030

Sales Org

2030

Distribution Chains

2030/30 For NZ DCs to sell to stores

2030/40 For NZ DCs to sell to franchises

2010/10 For Countdown stores to sell to

consumers

2015/10 For Gull Petrol Stations to sell to

consumers

9050/10 SuperValue to sell to consumers

9060/10 Fresh Choice to sell to consumers

10

-R

eta

il

30

-D

istr

ibutio

n4

0 -

Who

lesa

le

CASS Divisions

Sales Organisations


CASS Divisions

Sales Organisations


Countdown

Co Code 2000

Sales Org 2010

Gull Petrol Outlets

Co Code 2000

Sales Org 2015

SuperValue

Franchises

Co Code 2020

Sales Org 9050

Fresh Choice

Franchises

Co Code 2020

Sales Org 9060C

on

su

mers

1.6 – Site (Store or DC)

A Site includes both Stores and Distribution Centres (Internal and External) and the Site numbers are the same as CASS today.

A site must operate as a customer to allow for the purchase of goods (DC purchasing from a vendor) or the purchasing of stock (Stores purchasing from the DC or another store).

All trading locations (Stores & DCs) in CASS will be set-up as Sites in SAP.

Cost centres that are locations in CASS will remain as cost/profit centres in SAP but will not be set up as Sites.

Leading number reference to the state that site belongs to will remain (eg. NSW starts with 1, systems recognise leading digit and association with NSW).

There are two types of sites:

The management of Sites within SAP will be centralised.



1.7 – Site Groups

Site groups are used to logically group sites together. Site Groups allow us to manage Cost Prices for Zone pricing (i.e., Sub State Pricing).

In CASS, Location Profile Groups are similar to Site Groups.

Site Groups can be used for several purposes:

We will mainly be using them to manage vendor costs and variations (zone pricing) including for reporting purposes.

Site Groups will be used if the same vendor supplies the Article with different costs to different site groups.

There are two different purposes for Site Groups, these are:

Site Groups to reflect all sites in a Sales Organisation and District (State) for reporting purposes.

Site Groups to reflect all sites that tie up to a particular Zone Cost Price for a Vendor.

There are site groups set up similar to CASS states.

Naming conventions of site groups will be used to help identify group purpose and are managed centrally.



1.8 – Customers

In SAP, a customer can be one of two entities:

1.9 – Vendor

Vendor Objects in CASS are known as Partner Functions in SAP.

CASS SAP

Multiple

Vendor

Records

Parent Vendor

Remit to Vendor

Brokerage

Buy From Vendor

Location Supplied

Procurement Release

Master Data Release

Vendor (VN)

and

Invoicing Party (PI)

Order Address (OA)

and

Goods Supplier (GS)

and

Broker (ZB)

One

Single

Vendor

Record

Cost Vendor has no equivalent in SAP



1.10 – Ranging

Listing and Assortments

Listing - Article is linked to an Assortment – this procedure is referred to as „listing‟

An Assortment can be viewed as a container that relates Articles and Sites

A General Assortment can have many Users (Sites)

A Local Assortment only has one User (Site Specific)

Ranging = Listing + Valid SoS (DC or Vendor) + Price List

CASS to SAP Tip

An Assortment in SAP is

different to what an

Assortment was in CASS.

CASS to SAP Tip

An Assortment in SAP is

different to what an

Assortment was in CASS.

Sell

Pric

e

So

urce o

f S

up

ply

Ran

gin

g

Store

Ranged

CASS

Sell

Pric

e

So

urce o

f S

up

ply

Lis

tin

gStore Ranged

SAPvsS

ell P

ric

e

So

urce o

f S

up

ply

Ran

gin

g

Store

Ranged

CASS

Sell P

ric

e

So

urce o

f S

up

ply

Lis

tin

gStore Ranged

SAPvs

Listing

Listing is a procedure where Article is linked to an Assortment.

An Assortment is a container that relates Articles and Sites.

Therefore Listing determines which sites can perform, for an Article, transactions such as ordering, returning and supplying.



Whilst SAP supports a multitude of Listing options the recommendation is to use one of the following:

Range from Planogram (RFP)

Lists articles to sites based on the applicable planogram in SMART (recommended)

Range from Virtual Planogram (RFVP)

Lists Articles to sites based on a partially complete planogram in SMART (no Apollo layout) (recommended)

Manual Assortment Listing in SAP

Lists Articles to Sites based on a list of Articles and Sites contained in an Assortment. (only where no Apollo layout is required and where all the Articles are ranged to all Stores in the group)

Ranging Summary

All Business Processes surrounding the introduction of new Articles into the WOW Network will be ranged by either RFP, RFVP or Manual.

The desired process is to RFP (Range from Planogram) and interface to SAP.

DC Ranging will be managed using General Assortments for National ranges i.e. “Ambient RDC” or “Chilled RDC”, and Local Assortments for site specific articles.

Custom reports have been developed for the Merchandise Analysts to check the proposed listing in SAP to Planogram.

Any ranging for Franchise sites (ie.Gull) will be executed by Manual Listing.

The SAP term “Listing” refers to the process of assigning Articles to a site. Unlike the ranging process in CASS, there is no requirement for a valid supply chain in order to execute Listing in SAP.

Important Note on Business Rules

CASS is being backfilled until all downstream systems are fed directly by SAP (approx 2014). This means ALL CASS rules still exist even if SAP does NOT enforce them:

Forecast derived reference numbers CAN NOT be delisted

PI CAN NOT be Y for standard items – J and LN only

Relationships such as pack breakdown / prepacks CAN NOT be created until items are STORE ranged

Cost Qty CAN NOT be changed without notification

Costs CAN NOT be loaded if we cannot load SCU/SVTU‟s



Session 2 - Introduction to Merchandise Category Hierarchy

2.1 – Objectives

At the end of this session, participants will be able to:

Understand the structure of the Merchandise Category Hierarchy

Understand the difference between the Merchandise Category Hierarchy and a Merchandise Category

Understand the Characteristic and Attributes

Understand the relationship with CASS‟s Hierarchy Structure (Coarse, Fine and Sub-section)

2.2 – Master Data

Field Division Value

Company Code

Big W Stores 1000

BWS 1000 / 9020

Dan Murphy 1000 / 9020

Distributions Centres (AU) 1000

Thomas Dux 1000

WOW Homeshop 1040

WOW Supermarkets 1000

WOW Petrol 1000

Countdown 2000

Distribution Centres (NZ) 2030

Gull Petrol Outlets 2000

SuperValue Franchises 2020

Fresh Choice Franchises 2020



Field Division Value


Retail 10

Online 20

Distribution 30

Wholesale 40

Purchasing Organisation Australia 1000

New Zealand 2000

Sales Organisation

Big W Stores 1050

BWS 1010

Dan Murphys 1015

Distribution Centres (AU) 1005

Thomas Dux 1025

WOW Homeshop 1040

WOW Supermarkets 1005

WOW Petrol 1020

Countdown 2010

Distribution Centres (NZ) 2030

Gull Petrol Outlets 2015

SuperValue Franchises 9050

Fresh Choice Franchises 9060

2.3 – Merchandise Category Hierarchy (MCH) Overview

The Base Merchandise Category is the lowest Single Hierarchy of items within SAP. This is the main hierarchy that drives functionality in SAP eg Purchase Cost, Ranging, Sell Price, Workflow and Inventory Balance.

The hierarchy plays a similar role to the Coarse, Fine and Subsection departments in the CASS system. It allows the business to create categories to range and sell products by assigning the article to a Merchandise Category.

Merchandise Categories can be grouped into Merchandise Category hierarchy levels. Merchandise Category levels will then be assigned to higher hierarchy levels.



A level in the hierarchy is a grouping that links an article to a business segment; for example Diet Coke 1.25 may have a hierarchy as follows:

Food

Beverages

Beverages Non Alcoholic

Drinks Carbonated

Drinks Carbonated

Each stage of this example represents a level in the hierarchy.

The Merchandise Category Hierarchy is not assigned the function of reporting. Instead an alternative structure, called the Article Hierarchy will be introduced at a later date that will provide the means for reporting.

The Merchandise Hierarchy and Merchandise Category are logical groupings of articles that behave the same way from a SAP system perspective.

There are four hierarchies available in the Woolworths Limited structure:

Food (1)

Hard goods (2)

Soft Goods (3)

Everyday Needs (4)

Key notes:

There are 4 layers of Hierarchy and 1 Base Merchandise Category level

Each articles is assigned to only one Merchandise Category

1 x Merchandise Hierarchy for each major segment of goods across ALL Divisions (Inc BIG W) ie: Food, Hard Goods, Soft Goods and Everyday Needs.



Key Rule:

Merchandise Categories are wholly owned by one Business / Category Manager within a Sales Organisation.

There is no intention to change the Smart categories at this stage.

A new Merchandise Category can be created if a new article is accepted into our business that is unrelated to a current category. However, strict rules and standards will need to be adhered to prior to introducing any new Merchandise Categories.

2.4 – Characteristics

Characteristics can be used to capture additional information on the article master. Examples include flavour, size, colour, style, etc.

They can be assigned to profiles or merchandise categories

Profiles are a collection of characteristics

They can be assigned to a merchandise category or hierarchy level

Characteristics can be inherited down hierarchy levels

Characteristics are assigned to a Merchandise Category and they are used to determine the structure that is most suitable for an article.

A merchandise category characteristic is the detail of an item that links it to a level in the Merchandise Category Hierarchy. For example, a characteristic of an article would be the colour and size of a specified product.

MCH Level 4

MCH Level 3

MCH Level 2

MCH Level 1

Merchandise Category



2.5 – Characteristic Values

An attribute expands on the characteristic of the article. For example, if the characteristic item were ladies jumpers and the jumper came in various sizes and colours, the attribute would be the actual size or colour of the jumper.

Value example, Colour: Red and Size: 10

Note: Characteristics are only used for Liquor articles. These types of articles have more than one variant eg: sparkling wine, red wine, white wine, fortified wine.

2.6 – Request new Merchandise Category or new Merchandise Category Hierarchy Level

To create a new Merchandise Category or Merchandise Category Hierarchy level refer to the following process steps:

1. The Merchandising Team completes the Merchandise Category Maintenance Form

2. The completed form is emailed to BSS.

Address: [email protected] (you can search for this email address by typing “BSS” in your outlook address search field)

3. BSS process request and confirm agreement across all Divisions

4. BSS advise stakeholders

2.7 – Merchandise Category Maintenance Form – New Hierarchy Level Request

There are 5 levels in the Merchandise Category Hierarchy – Merchandise category and 4 levels parent levels above as shown in the diagram on page 51.

Merchandise Category Maintenance contains 3 types:

1. New Hierarchy Level – Creating a new node in a level (Merchandise Hierarchy Maintenance)

2. Merchandise Hierarchy Classification (Merchandise Hierarchy Reclassification)

3. Merchandise Category Creation (Merchandise Category Maintenance)

Key Reasons For Using Form

To create and maintain all levels of the Merchandise Category and Hierarchy and to ensure that, as a new business process all fields are covered.





Merchandise Category Maintenance Form – Create Merchandise Category



Merchandise Category Maintenance Form – Change Merchandise Hierarchy Level Request



2.8 – Reference Article

In SAP, each Merchandise Category will have a reference article assigned to it:

A Reference Article could be assigned to multiple MC‟s as long as it is relevant.

It should be created as part of the Merchandise Category process.

It is not a sellable article but used to copy the common or MC specific default values to a new article created for this MC.

2.9 – Process of Re-classifying a Merchandise Category

The following process will be used when re-classifying a Merchandise Category:

1. The Merchandising Team completes the Merchandise Category Maintenance Form.

2. The completed form is emailed to BSS. Address: [email protected] (you can search for this email address by typing “BSS” in your outlook address search field).

3. BSS process request and confirm agreement across all Divisions.

4. BSS advise stakeholders.

Note: It is extremely unlikely that a Merchandising Team will change a Merchandise Hierarchy, rather it is more likely that a New Merchandise Category will be created.

2.10 – Standard Transactions

Transaction Code Description

WG24 Display Merchandise Category

WGUS Display Merchandise Category Hierarchy Breakdown



2.11 – WG24 – Display Merchandise Category

The Merchandise Category Hierarchy plays a similar role to the Coarse, Fine and Subsection departments in the CASS system. This transaction is used to display the Merchandise Category levels within a specific Merchandise Category Hierarchy.

2.11.1 – Demonstration – WG24 – Display Merchandise Category

Demonstration Scenario: Display the Merchandise Category Hierarchy for 124010106. After you have viewed the Merchandise Category levels within the Merchandise Category Hierarchy, return to the initial screen and display the list of Articles assigned to the Merchandise Category Hierarchy.

For demonstration data refer to the Data Sheet provided.

Purpose

These instructions are applicable to:

All Business Teams and BSS Teams that wish to display a merchandise category.

Use this procedure to:

Display the merchandise category. This transaction can also be used to display all articles within a merchandise category.

Menu Path:

SAP menu > Logistics > Retailing > Master Data > Merchandise Category Data > Merchandise Category > WG24 - Display

Transaction Code: WG24

Helpful Hints:

When searching for a merchandise category, the description must be entered in UPPERCASE, otherwise the search will be unsuccessful.

To view all articles within the merchandise category, click the button on the Merchandise category Display: Initial Screen.



Procedure

1. Start the transaction using the menu path or transaction code.

Merchandise category Display: Initial Screen

2. As required, complete/review the following fields:

Field R/O/C Description

Merchandise category R Enter the Merchandise Category. A Merchandise Category is a Grouping of Articles. Each article is assigned to only one merchandise category. This assignment is valid throughout the company. Merchandise categories can be grouped into merchandise category hierarchy levels.

Merchandise category hierarchy levels can, in turn, be assigned to higher hierarchy levels. Organizing and structuring an assortment is easily done by maintaining merchandise categories. Merchandise Category is a Key that you use to group together several Articles or Services with the same attributes.

Example:

124010106

3. Click the icon to continue.

Note: The Merchandise Category hierarchy levels assigned are displayed in the Val.-Only Artl Assgmt area.



Merchandise category Display: basic data

4. Scroll down using the arrow to display additional merchandise categories.

5. Click the icon to exit the transaction.


6. Click the button to view all articles within the Merchandise category.



Display Articles for Merchandise Category 124010106

7. Click the icon to close the pop-up window.



Result

You have displayed a merchandise category and also displayed all the articles within the merchandise category.



2.11.2 – Exercise – WG24 – Display Merchandise Category

This exercise allows you to practice displaying the Merchandise Category levels within a specific Merchandise Category Hierarchy.

Exercise Scenario:

Display the Merchandise Category Hierarchy for 408010101. After you have viewed the Merchandise Category levels within the Merchandise Category Hierarchy, return to the initial screen and display the list of Articles assigned to the Merchandise Category Hierarchy.

Transaction Code: WG24

Menu Path: SAP menu > Logistics > Retailing > Master Data > Merchandise Category Data > Merchandise Category > WG24 - Display

For exercise data refer to the Data Sheet provided.

2.12 – WGUS – Merchandise Category Usage

The transaction WGUS is used to display a Merchandise Category Hierarchy breakdown and associated sites, characteristics and articles assigned to the Merchandise Category.

2.12.1 – Demonstration – WGUS – Merchandise Category Usage

Demonstration Scenario: Display the Merchandise Category Hierarchy 119 to display the Merchandise Category levels, Articles and Sites within the Merchandise Category Hierarchy.

Note: If you want to display the entire Merchandise Category Hierarchy, enter *

in the Merchandise Category field.




Purpose


Merchandise / Space Analyst, Merchandise Teams and BSS Team


Find the associated Merchandise Category Hierarchy objects and determine where they are used in the Merchandise Category Hierarchy structure. For example, where a Merchandise Category is used at a Site.

Menu Path:

Use the following menu path(s) to begin this transaction:

SAP menu > Logistics > Retailing > Master Data > Merchandise Category Data > Environment > WGUS - Merchandise Category Where Used List

Transaction Code: WGUS

Helpful Hints:

The Merchandise Category number consists of 9 digits. The subsequent levels within the Hierarchy reduce by 2 digits each level. For example, the number of digits for each level in the Merchandise Hierarchy are as follows:

Level 4 = 1 digit

Level 3 = 3 digits

Level 2 = 5 digits

Level 1 = 7 digits

Merchandise Category = 9 digits

Reference Article = 9 digits

The Woolworths Limited Merchandise Category Hierarchy highest level (L4) nodes are identified as:

Food (incl Beverages)

Softgoods (e.g., Apparel, Manchester)

Hardgoods (e.g., Toys, Electrical)

Everyday Needs (e.g., Shampoo, Nappies)

Note: Avoid using search criteria for Level 4 Merchandise Category types to reduce your search time.

You can also reduce your search times by selecting the following checkbox items in the Options section on the Use of Merchandise Categories screen:

Select checkbox to omit articles from the search results.

Select checkbox to omit Sites from the search results.



Procedure


Use of Merchandise Categories



Merchandise category object

R Enter the Merchandise Category object number.

Example:

119

In the Options section you can select checkbox to omit Articles from

your search results, or select to omit Sites from you search results.

3. Click the icon to execute the search query.




4. Click the option beside the required merchandise category to expand the hierarchy tree.


5. Click the icon to expand the Merchandise Category Hierarchy tree.

When the Merchandise Category Hierarchy tree is expanded all objects are displayed. The example shown on this screen displays both the Article and the associated Site objects.

You can click on the hierarchy node to view the sites associated with the Merchandise Category.


6. Click icon collapse all branches of the merchandise category hierarchy tree.





Result

You have now displayed a Merchandise Hierarchy tree.

2.12.2 – Exercise – WGUS – Merchandise Category Usage

This exercise allows you to practice how to display a Merchandise Category and the associated objects within the Merchandise Category Hierarchy.

Exercise Scenario:

Display the Merchandise Category Hierarchy 102 to display the Merchandise Category levels, Articles and Sites within the Merchandise Category Hierarchy.

Transaction Code: WGUS

Menu Path: SAP menu > Logistics > Retailing > Master Data > Merchandise Category Data > Environment > WGUS - Merchandise Category Where Used List




2.13 – Business Policies

The following business rules apply to Merchandise Category Hierarchy and Merchandise Categories:

If all articles in a Merchandise Category are being re-assigned to another Merchandise Category, it is mandatory that all "discontinued" lines in the Merchandise Category are included in the re-org.

When moving an article from a Merchandise Category that has characteristics attached, the new Merchandise Category will need to have the same characteristics as the old one to successfully move the articles.

All users within SAP regardless of Distribution Chain will use the Merchandise Category Hierarchy. SAP does not link a buyer to a group of products; however we can associate people with Merchandise Categories using SAP workflow.

An Article can only be assigned to one Merchandise Category. The Article can be used across multiple sales organisations.

There is another hierarchy called Article hierarchy which is designed for Sales reporting, this can vary by Sales Organisation and will be introduced in a later release.

National Merchandise Department, State Merchandise Department, Buying Department, and Trading Department will be mastered centrally in CASS. These entities are not yet introduced to SAP.

Note: The article hierarchies will be constructed in a subsequent SAP release. We will continue to manage Coarse, Fine and Sub-Sections in CASS until CASS is decommissioned.

2.14 – Session Summary

You are now able to:

Understand the structure of the Merchandise Category Hierarchy

Understand the difference between the Merchandise Category Hierarchy and a Merchandise Category

Understand the Characteristic and Attributes

Understand the relationship with CASS‟s Hierarchy Structure (Coarse, Fine and Sub-section)



Session 3 - Site

3.1 – Objectives


Understand what a Site is

Understand how to display site information

Understand how to display a site group



WB03 Display Site

WB86 Display Sites assigned to a Site Group

WB87 Display Site Groups assigned to a Site

3.3 – WB03 – Display Site

A Site includes both Stores and Distribution Centres (Internal and External) and the Site numbers are the same as CASS today.

Site Categories are as follows:

Stores are assigned a Site Category (Category of Sites) of A

Distribution Centres are assigned a Site Category of B

A site (Store or DC) must operate as a customer as follows:

to allow for the purchase of goods (DC purchasing from a Vendor) or

the purchasing of stock (Stores purchasing from the DC or another store)

Transaction WB03 enables you to display a Site and determine which Merchandise

Categories are assigned to the Site. These Merchandise Categories are assigned by

the reference site when the site is being created by BSS.



3.3.1 – Demonstration – WB03 – Display Site

Demonstration Scenario: Display the details for a Site. Review the Supplying Sites, Opening Times and Contact person at the Site.


Purpose


Merchandise / Space Analyst, Merchandising Team, DC & Network Ranging

Use this procedure to find a Site or to display the Merchandise Category for a particular site and the supplying Distribution Centre details.

Prerequisites:

The Site must exist.

Menu Path:


SAP menu > Logistics > Retailing > Master Data > Site Data > Site > WB03 - Display

Transaction Code:

WB03

Helpful Hints:

A Site is a master record in SAP and it has 2 category types A and B. The Site category breakdown is as follows:

Site CategoryA represents a Store

Site Category B represents a Distribution Centre

You can use this transaction to find the store trading hours of operation and related articles for a single Site.



Procedure


Site Display: Initial Screen



Site R Enter the Site. An equivalent of Location (trading or non-trading) in Wow terminology. SAP term equating to WOW term = Location (Trading or non-trading).

Example:

1087

Hint: If you do not know the Site number, you can search for the Site details by clicking on the matchcode button to perform a search enquiry.

The best search option to use is the Sites in Distribution Chain.


The Site Additional Details area holds the GPS coordinate details which are used in the Woolworths website Store Locator for mapping details. It also holds the Liquor License details for Liquor stores.

The Organizational data area displays the organizational data, e.g., Company Code, Purchasing Organization, Sales Organization, Distribution channel, etc.



Store Display: Site General

4. Click the icon to display the operations trading times.

Opening times can also be accessed from the Extras menu, Opening times. Alternatively, press Ctrl + F10.

This screen is important as it displays the date the store is closing in the Closing date field.

Opening Hours





`

6. Click the button to display the Merchandise Categories that are assigned to the Site.

For Liquor departments, the Supplying sites are attached to the Merchandise Category.

The Supplying Sites display supplying Distribution Centres for the select

Merchandise Category. The values are populated from an interface in SOM.

Store Display: Merchandise categories

7. Click the option to select the Merchandise Category to view the Supplying sites.

8. Click the button to display the Supplying sites for the selected Merchandise Category.



Store Display: Supplying site/merchandise category, time-dependent

9. Click the icon to return to the previous screen.

Store Display: Merchandise categories

10. Click the icon to cancel out of the screen and return to the Store Display: Site General screen.




11. Click the button to display the sites that have supplying Distribution Centres (DCs). The Supply sites details are populated from an interface in SOM.

The supplying DC's for the Site are listed. The S... column displays the Supplying Site priority.

Store Display: Supplying site, central, time-dependent

12. Click the icon to return to the previous screen.




13. Click the button to display the contact details.

Store Display: List selec. Customer

14. Select the checkbox beside the Contact person.

15. Click the icon to display the details for the Contact Person at the Site.



Customer Display: Contact person

16. Click the icon to exit the screen.

Store Display: List selec. Customer


Result

You have displayed a Site to view the specific details for the site.

3.3.2 – Exercise – WB03 – Display Site

This exercise allows you to practice displaying a Site.

Exercise Scenario: Display the details for a Site. Review the Supplying Sites, Opening Times and Contact person details of the Site.

Transaction Code: WB03

Menu Path: SAP menu > Logistics > Retailing > Master Data > Site Data > Site > WB03 – Display




3.4 – Vendor Zone Pricing Site Groups Overview

If changes to the cost price occur for a particular store or group of stores, Vendor Zone Pricing Site Groups need to be created.

For example, a Vendor may supply DSD (Direct Store Delivery) to all Queensland stores at one cost price, but charge a different price for Far North Queensland stores, due to distance.

3.5 – WB86 – Display Sites assigned to a Site Group

Site Groups are used to logically group Sites together, in SAP, they are no longer managed by State.

Site Groups will be used if the same vendor supplies the Article with different costs to different site groups, allowing us to manage Cost Prices for Zone pricing (i.e., Sub State Pricing).

In CASS, Location Profile Groups are similar to Site Groups.

There are two different purposes for Site Groups, these are:

Site Groups to reflect all sites in a Sales Organisation (Division) and District (State). This may be used by the MA/SA for manual listing purposes.

Site Groups to reflect all sites that tie up to a particular Zone Cost Price for a Vendor.

Transaction WB86 is used to display all Sites assigned to a nominated Site Group.



3.5.1 – Demonstration – WB86 – Display Sites assigned to a Site Group

Demonstration Scenario: Display a Site Group to verify the Sites assigned to it.


Purpose


Merchandise / Space Analyst, Merchandising Team and BS&S Team members


Display the associated site assignments for a site group or relevance of the group of stores by district or by sales organisation.

Trigger:

Perform this procedure when you wish to display sites assigned to a site group.

Prerequisites:

The Site Group must exist.

Menu Path:


SAP menu > Logistics > Retailing > Master Data > Site Data > Grouping > Other > Maintain Assignment > WB86 - Sites in Classes


Helpful Hints

The data object 030 Site Grouping is referred to a class. The class type represents the site group.

From this transaction you can drill down to CL24N to the Assign Objects/Classes to Class screen.



Procedure

This is the first screen that displays when this transaction is accessed.

Note: Only Class Type 030 Site Grouping is used at this stage.

Class Type (1) 2 Entries found

1. Click the icon to accept the entry.

Site Group Allocation table and: Maintain sites in class

2. Click the button to display the Assign Objects/Classes to Class screen.

Note: In this work instruction scenario, you accessed transaction WB86 Display Site Group to display the site grouping details.

Once you click on the Maintain sites in class button, the Assign Objects/Classes to Class screen is displayed. The transaction code changes to CL24NAssign Objects/Classes to Class screen.



Assign Objects/Classes to Class



Class R Numeric or alpha-numeric identifier for a site group or site hierarchy.

Example:

SUPAUSNSW

If you do not know the Site group details, click the matchcode and enter the search criteria for the Site Group details.

4. Click the icon to display all the site assignments for Supermarkets NSW.

All sites that are part of the selected site group are displayed.

Note: This screen displays all the sites that have been assigned to the SUPAUSNSW Site Group.

When 1 is displayed in the status column and there is a green tick next to the assigned site, this indicates the site has been released and is active.



Display Objects/Classes to Class





6. Click the icon to close the window and return to the SAP Easy Access SAP Retail screen.

Result

You have successfully displayed a site group and the assigned sites.

3.5.2 – Exercise – WB86 – Display Sites assigned to a Site Group

This exercise allows you to practice displaying the Sites assigned to a specific Site Group.

Exercise Scenario: Display a Site Group to verify the Sites assigned to it.


Menu Path: SAP menu > Logistics > Retailing > Master Data > Site Data > Grouping > Other > Maintain Assignment > WB86 - Sites in Classes




3.6 – WB87 – Display Site Groups assigned to a Site

Transaction WB87 enables you to display the Site Groups that a Site is assigned to. This also includes Zone Pricing Site Group details.

3.6.1 – Demonstration – WB87 – Display Site Groups assigned to a Site

Demonstration Scenario: Display the Site Groups attached to a Site.


Purpose


Merchandise Teams, Merchandise/Space Analyst and BSS Team.


Enquire on a Site and find the relevant Site Groups that the Site is attached to. The Site Group ID is used on the Woolworths Price Form (WPF) to identify a changed zone price relevant to the new Site and is required by the Vendor when completing the form.

This transaction is also used by BS&S when a request for new Site creation has been received and they need confirmation from the Business Team that the like store they have chosen is correct. This then enables them to assign the new Site to the correct Site Group(s).

Trigger:

Perform this procedure when you want to view the Site Groups a Site is attached to. This not only shows the Site Group, for example SUPAUSNSW, but also Zone Pricing.

Perform this procedure when zone pricing is required to be entered on the WPF and the Vendor needs to determine the relevant Site Group to enter.

Prerequisites: Site and Site Group exist.

Menu Path:

SAP menu > Logistics > Retailing > Master Data > Site Data > Grouping > Other > Display Assignment > WB87 - Site to Classes


Helpful Hints:

A Site Group identifying a Zone Price is identified by the first two characters of ZP followed by the Vendor number, followed by set of characters to identify the group. For example: ZP54956001_QLD0021.

Ensure that you click and not the Enter icon to continue.



Procedure


This is the first screen that displays when this transaction is accessed.

Note: Only Class Type 030 Site Grouping is used at this stage.


2. Click the icon to accept the entry.

Site Group Allocation table and: Display site to classes

3. Click the button to continue.



Assign Object to Classes



CustomerNoSite R Enter the Site number. This is a key used in SAP to uniquely identify the Site as the customer.

Example:

3101

5. Click the icon to display the Site Groups the Site is assigned to in the Assignment area of the screen.

The Assignments area displays the Zone Pricing Group(s) and Site Group(s) the Site is assigned to.



Display Object to Classes

6. Click the Vertical scrollbar to display additional values.



8. Click the icon to close the window.

Result

You have identified the Site Groups that a Site is assigned to.



3.6.2 – Exercise – WB87 – Display Site Groups assigned to a Site

This exercise allows you to practice displaying the Site Groups assigned to a specified Site.

Exercise Scenario: Display the Site Groups assigned to a Site.


Menu Path: SAP menu > Logistics > Retailing > Master Data > Site Data > Grouping > Other > Display Assignment > WB87 - Site to Classes



Sites will belong to Divisions / Sales Organisations as they do today.



Understand what a Site is

Understand how to display site information

Understand how to display a site group allocation table



Session 4 – Vendor Introduction and Maintenance

4.1 – Objectives


Understand the concept of Vendor and Vendor Sub-Range

Understand the process for Vendor Introduction

Understand the process for Vendor Maintenance

Understand the Vendor Maintenance Form

Understand standard vendor transactions

4.2 – Vendor

A vendor in SAP is usually represented by the CASS Remit to Vendor. There are approximately 70 vendors where this is not the case. Refer to the Super Remit to Vendor topic below, i.e., 4.6.

In this SAP release, there are no vendor entities in SAP that represent CASS Cost Vendors, Buy From Vendors or Depots.

4.3 – Vendor Sub-range

A vendor Sub Range is a subdivision of a vendor's overall product range. The sub range can hold some trading term cost conditions (Warehouse allowance, Distribution allowance and Quantity Buy allowances) that apply to a category of articles.

For example; a Vendor could supply articles from Frozen, Chilled and Ambient parts of our business and may require different trading terms for each business segment.

This can be managed via a Vendor Sub-Range.

The vendor Sub-range is approximately the equivalent of a CASS Trading Category, except that Vendor Sub-ranges do not need to be replicated by source of supply (i.e., Direct and Warehouse).

If a vendor only has one set of trading terms that applies to all articles that the vendor supplies, the vendor record does not require any vendor sub-ranges.

A Vendor Sub-Range will be created if Warehouse, Distribution or Quantity Buy Allowances differ across a product set.

The Vendor sub-range is connected to the article by the PIR (Purchase Information Record) which is on the Purchasing view of the article record.

For example, Ingham‟s has two vendor sub ranges, one for Deli and one for Fresh Meat. The cost condition type will be applied based on the vendor‟s assignment of articles to the relevant Sub Range.



4.4 – Vendor Introduction Process

1. The Business Manager / Category Manager will negotiate a vendor Contract. Prior to a vendor starting to trade with Woolworths Limited, original completed forms and attachments are sent to BM/CM. These are then reviewed and authorised and passed to Trading Terms Team.

2. The Trading Terms Team to check if vendor record exists.

3. The Trading Terms Team to review paperwork.

4. The BSS Vendor Administrators load Base Vendor Record, Financial Attributes, Trading Term Attributes, and enable Vendor Sub Ranges in both CASS and SAP.

5. The Trading Terms Team to print and send Trading Terms to the Vendor.

4.5 – Vendor Maintenance Process – Non Trading Terms Changes

1. The Business Manager / Category Manager is to organise with the vendor for updated paperwork, original completed forms and attachments are sent to the Merchandising Team who will review and authorise then pass on to BSS Vendor Administrators.

2. The BSS Vendor Administrators will action the change in both CASS and SAP.



4.6 – Vendor Maintenance Process – Trading Terms Changes

1. The Business Manager / Category Manager is to negotiate with the vendor the new trading terms in conjunction with the Trading Terms Team.

2. The Trading Terms Team to review the negotiation and if approved, complete the paperwork. They then pass the paperwork to the BSS Vendor Administrators.

3. BSS Vendor Administrator will action the authorised Trading Terms changes in both CASS and SAP.

4. The Trading Terms Team send updated Trading Terms to the Vendor for them to sign and approve the changes.

4.7 – Super Remit to Vendor

There are examples where CASS Parent Vendors have several Remit to Vendor Numbers; where all remit to vendor numbers have the same:

ABN (Australian Business Number)

payment terms

payment method (including bank details) and

off remittance rebates.

Note: If all of the above points are the same, there is no need to create multiple Remit to Vendors.

Normally, every CASS remit to vendor would be loaded as a different SAP vendor number, but it is not optimal to have multiple vendors in SAP for effectively the one vendor, which is why the super remit to vendor concept is introduced.

The high level of maintenance involved in consolidating all the CASS item records to one CASS remit to vendor is also another reason for the introduction of the Super remit to vendor in SAP.

There are approximately 70 vendors that will be super remit to vendors in SAP

The advantages of the super remit to vendor are:

Only one vendor record in SAP to allow for simpler vendor reporting and simpler article records

Less records to clean up in CASS prior to migration of the category

Less WAF and WPF forms that the vendor will need to complete, as there is only one vendor number used in SAP

The system allows for Finance to still manage the Remit To Numbers separately as CASS still has separate remit to vendors.





XK03 Display Vendor

4.9 – XK03 – Display Vendor to a Site

A vendor in SAP is usually represented by the CASS Remit to Vendor. However, there are a few vendors where this is not the case. See 4.2 – Vendor on page 55 for further information.

Transaction XK03 is used to display Vendor information such as contact numbers,

email addresses, Purchasing Information, postal addresses, FCR (Freight Cost

Recovery) agreements and any other vendor related information.

4.9.1 – Demonstration – XK03 – Display Vendor to a Site

Demonstration Scenario: Display the Vendor details.


Purpose


To identify the Vendor Master details and assigned DC/Vendor combination. This transaction can also be utilised to identify the remit to vendor number for vendors when completing the WPF (Woolworths Price Form) and the WAF (Woolworths Article Form).

Menu Path:


SAP menu > Logistics > Retailing > Master Data > Vendor Data > Edit Vendors > Vendor > Display > XK03 - Central

Transaction Code: XK03

Helpful Hints:

In the following scenario you will search for a Vendor and select the Purchasing Data view from the DisplayVendor Master transaction to review the specific DC/Vendor combinations.



Procedure

1. Start the transaction from the SAP Easy Access screen.

Display Vendor: Initial Screen

2. Click the Vendor field.

3. Click the icon to open the Vendor search screen.

Vendor Account Number (1)

4. Click the Name field.



Use the * (asterisk) wildcard to refine your search results. For example, enter an asterisk before and after your search criteria. In this scenario, any vendor names in the database which have an exact match to *stuart alexander* will display on the search results screen.



Name R Enter a Person's or Company's name

Example:

*stuart alexander*

6. Click the icon to continue the search.

Vendor Account Number (1) 10 Entries found

7. Select the appropriate vendor when more than 1 vendor name displays in the search results. For example, select vendor:

.





`



Company Code R Independent accounting unit; in most cases is a legal entity. You can prepare a balance sheet and income statement for each company code. Several company codes can be set up to manage the accounts of independent companies simultaneously.

Example:

1000

Purch. Organization R An Organization unit in Logistics, subdividing an enterprise according to the requirements of Purchasing.

Example:

1000

You must enter the Company Code and Purchasing Organisation details in order to locate the Vendor details. The Vendor master record is linked to the Company Code and Purchasing Organisation in the database.

10. Click the check box .

Select the Purchasing data checkbox to display the Vendor Master - Purchasing data view.

Note: You only need to choose this option from the Display Vendor - Initial Screen.to find the Stock Planner details (previously known as the Re-Buyer).




Display Vendor: Purchasing data

12. Click the button to display all the Sites and Vendor Sub Range details.

Display Vendor: Different data

13. Click the line item to select a single line item to review the specific DC/Vendor combination.

14. Click the button to display the Stock Planner code.



Display Vendor: Dif. Purch. Data

15. Click the icon to return to the Display Vendor: Different data screen.

To view what other partner functions the vendor has click the

button. For example, you can view the invoicing party.

Review the Stock Planner code details for the specific DC / Vendor combination as required.

Display Vendor: Different data

16. Click the icon to return to the Display Vendor: Purchasing data screen.

To find the Sub Range ID click the Sub-ranges button.



Display Vendor: Purchasing data

17. Click the button to show WOW details for the vendor and contact details.

To display the Freight Cost Recovery agreement click on the FCR Rate Maintenance button.

Display Vendor: General Data (Enhanced)

18. Click the icon to return to the Display Vendor: Initial screen.





Result

You have completed this transaction.

4.9.2 – Exercise - XK03 – Display Vendor

This exercise allows you to practice displaying the details for a Vendor.

Exercise Scenario: Display the details for a Vendor.

Transaction Code: XK03

Menu Path: SAP menu > Logistics > Retailing > Master Data > Vendor Data > Edit Vendors > Vendor > Display > XK03 – Central


4.10 – Forms

The Vendor Maintenance Form is used to introduce a new Vendor or change existing vendor details. The form is initiated by Vendors through the Woolworths Vendor Website and sent to the Merchandising Team. BSS Vendor Administrators will adjust the records in both CASS and SAP.

There is no workflow available for the maintenance of Vendor Records. The Trading Terms team should notify all applicable Merchandising Teams on trading term changes.



Vendor Maintenance Form




The following business rules apply to Super Remit to Vendors

Remit to Vendor numbers can only be consolidated within a single Parent Vendor number. It cannot be done across Multiple Parent Vendors.

A Super Remit to Vendor is Product Set variation applicable, NOT Source of Supply variation applicable.



Understand the concept of Vendor and Vendor Sub-Range

Understand the process for Vendor Introduction

Understand the process for Vendor Maintenance

Understand the Vendor Maintenance Form

Understand standard vendor transactions



Session 5 – Article Processes and Forms

5.1 – Objectives

At the end of this session, participants will be able to understand:

New Article Process

Types of Articles and their application

Pack Breakdown

Order units and Sales Units

Sales Sets

The function of applicable Forms and GS1

5.2 – Article Category

Each Article must have an Article Category, once assigned it cannot be changed.

Article Description

Single This article has its own purchase and sales price. For example, Standard line, Pack Breakdown, Item Linkage.

The majority of Articles will be Single Articles. Items in a Price Family (CASS Assortment) are also loaded as Single Articles.

Sales Set This article is a combination of two or more articles bought individually but are sold together as a single item. This item is sold but not ordered.

For example, bottle of wine and 2 wine glasses, Bakery instore manufactured cake, Quarter of a Chicken sold behind deli counter.

Display

This article is a combination of articles that are bought together from the Vendor, but are sold separately. Ordered as one combined unit but sold as separate units.

For example, Pre-packed unit of batteries or Rainbow pallets. Known as Displays in CASS.

Generic A generic article is used for apparel items to group all combination of size and colour together. It is not ordered or sold, but an entity that holds common information for all of the variants of the generic.

Sales Sets, Generics and Displays are structured articles that are attached to other articles. In order to create these structured articles the individual to be attached must be created first.



5.3 – Article Type

Article Types are similar to an item type in CASS. An article type determines the article attributes that belong to an article. When the Article Type is assigned, this determines the fields that will be applicable to the article.

For example all meat scale items will require tare weights and scale labels.

Article Types are listed as follows:

Article Type

HAWA Trading / Packaged goods (6 digits) This article type is used for any article that is packaged and is fully bar-coded ready for sale to the customer. This does not include articles that are labelled in stores via store scales. Most articles will have this article type assigned.

Example - 193145 HOMEBRAND NOODLE CUPCHICKEN 70G

MODE Apparel items (7 digits single articles)

This article type will be used to capture all apparel articles.

Example - KING GEE DRILL PANT STEEL TUF

VERP Packaging (6 digits)

This article type will be used to capture all packaging related articles (e.g. plastic meat tray, soaker etc...) & within the distribution process (e.g. pallets etc…). This is to be mapped in CASS to item type „E‟ – Expense.

Example - 247666 BAG PLASTIC LARGE CHECKOUT CTN1000

ROH Ingredients(6 digits)

This article type will be used to capture all ingredient (food) articles that are ordered into stores to make a finished good but are not sold to the customer. E.g. all ingredients used in the manufacturing of in store Bakery articles.

Example - 323929 KP FLOUR DUSTING PLAIN 12.5KG

DIEN Service item

This article type will be used to cover the articles which are sold to the customer, but the article does not need to be ordered and there is no physical stock on hand in the store. E.g. Gift cards, Phone recharge cards, carpet cleaning hire, dry cleaning articles etc.

Example - 171768 RUG DOCTOR HIRE OVERDUE PENALTY

ZMEA Meat Scale item

This article type will be used for articles that are cut and packed in store and labelled using the meat scale. This article type will contain additional fields used in the labelling of the article that are not available to non scale article types and will include the collection of meat tare fields specific to meat.

Example - 290819 NZ BEEF RUMP STEAK T610

ZBAK Bakery Printer item

This article type will be used for articles that are packed in store and labelled using the bakery printer. This article type will contain additional fields used in the labelling of the article that are not available to non scale article types and will include the NIP data and the ingredients data.

Example - 007927 DONUT CINNAMON 6PK



Article Type

ZDEL - Deli / Seafood / Serviced Meat scale item

This article type will be used for articles that are packed in store and labelled using the deli / seafood / serviced meat scales. This article type will contain additional fields used in the labelling of the article that are not available to non scale article types and will include the NIP data and the ingredients data.

Example - 293344 BLUE COD FILLETS SKINNED/BONED FRESH

ZBUL - Bulk foods (sold by PLU at checkouts)

This article type will be used for all non- produce articles sold by PLU through the POS. For example, Bulk (nuts and confectionary), and Seafood (mussels) articles.

Example - 346606 BULK CONFECTIONERY CHOC PREM UNWRAPPED

ZPRD - Produce items (only capturing minimal data)

This article type will be used for all produce items and only basic data will be captured that will reserve the article numbers, and consumer units EAN‟s. The full maintenance of produce articles will occur in a later release.

Example - 133211 BANANA

ZPCA – Pricat Core Article

This article is an incomplete article that only holds basic information for the article.

An article contains both Vendor supplied information and Woolworths supplied information.

A Core article is created once the Vendor supplies their information and the article becomes a complete article once it is enriched with Woolworths information.

A Core Article is an incomplete article that only holds basic corporate information. It contains both Vendor supplied information and Woolworths supplied information. The Core article is created once the Vendor supplies their information and it becomes a complete article once it is enriched with Woolworths information.



Sales Set Overview

Sales Set is the process by which whole items are sourced and then broken down in store and sold as a smaller portion. For example: Whole, Half and Quarter Roast Chicken.

Sales Set is an item relationship that consists of a parent item and a child item(s).

The parent item is ordered by AutoStockR and may or may not be sold to the customer.

A child item is not ordered but is sold to the customer.

The sales set allows for all the sales of the children item(s) to be rolled up to the parent item so that AutoStockR orders enough stock to sell the product in its different forms. Sales Set is a similar relationship to Pack Breakdown as it connects items together for the purposes of store replenishment.

All Sales Set articles are loaded as separate articles in SAP, where the parent item will be assigned to the single article category (this allows the item to be ordered and sold) and the child item/s will be assigned to the sales set article category (allows items to only be sold). For example, shaved ham and sliced ham, 1kg bag of prepacked prawns and loose prawns sold behind seafood counter.

All child items participating in a CASS item linkage will be loaded as Sales Sets. All the parent items in a CASS item linkage will be single articles in SAP but connected to a sales set as a component.



The following is an extract from the Basic view of the Sales Set article. This is a Self Service Extra Large Chicken.

This is an extract from the Components section access from the Basic view of the Sales Set article. This shows the connection of the component item (ordering) to the Sales set article (selling).

Pack Breakdown Overview

Pack Breakdown is the process by which items are broken down from the carton into inner packs and single items where the carton, inner pack and single item can all be sold to the customer. For example: Case of beer, 6 pack of beer, single bottle of beer.

In SAP it is no longer required to have multiple reference numbers loaded for Pack Breakdown Articles.

The Article that is loaded into SAP represents the lowest UOM for the pack breakdown which is the lowest child item in CASS. E.g single bottle of beer.

The other components of the pack breakdown eg 6 pack of beer & carton of beer, will be loaded as multiple selling UOMs under the one SAP article.

Note: As CASS is still communicating to store level systems (Replenishment systems and SMART) the MA/SA will need to still use the three CASS reference number for ranging from POG only in SMART. If ranging in SAP, the ranging of the SAP article number will result in ranging of all pack breakdown items in CASS.



CASS vs SAP Article Numbers

In the example below, the cigarette packets and the sleeves have two CASS reference numbers, however, in SAP only the article number for the packet (base UoM) is used.

Existing CASS articles will be migrated in SAP and a migrated program will ensure that the base UoM article number is the main SAP article number.

The others will be known as „Additionals‟.

1 SAP Article 65157

2 CASS Articles 65157

and 140671

B&H Blue

1 SAP Article 65154

2 CASS Articles 65154

and 140674

B&H Maroon

1 SAP Article 65155

2 CASS articles 65155

and 140673

B&H Silver

For Pack Breakdown relationships, the EAN number against an EAN category of Z2 will indicate the equivalent CASS reference number.

Note: Article number 192873 has the description relating to the lowest child item which is the Winfield Sky Blue 20pk (single packet). The Sell price for this single packet is represented by the EA UOM. As this article number is the same in both CASS and SAP, there is no need to do any article number translation between the two systems.

The CA1 UOM represents a sleeve of 10 single packets of cigarettes. This CA1 UOM acts not only as a selling UOM to sell the 10 packets of cigarettes, it is also used to as a delivery/issue UOM to issue the inner pack from the DC to the store.



Below is an Extract from the Basic view of the Winfield Sky Blue 20pk

This is an Extract from the Additional EANs view of the Winfield Sky Blue 20pk showing the Z2 CASS reference number for the sleeve of cigarettes being 192874.

This is an Extract from the POS view of the Winfield Sky Blue 20pk article showing the descriptions for each of the selling UOMs.



Display Units Overview

Displays are defined as a group of items that we currently sell and re-order under individual item numbers, which are then grouped together in a carton display pack or pallet display configuration and are used to build a display.

A Display (They are known as Pre-Packs in CASS) can be defined as:

Order Multiple (OM) on a Pallet of stock (Stock arrives at the DC as a pallet of stock and sent to stores in OMs).

Pallet of stock (Stock arrives at the DC as a pallet and is sent to stores as a pallet).

There are two types of items:

Primary Item – this is the carton display pack or pallet display sent to stores and used to build a display.

Secondary Item – these are items that are currently ranged to stores. New secondary items are to be built and store ranged as separate saleable.

A Pre-pack is loaded as a sales set Article.

One Article is loaded for the Primary Item e.g., Display Unit and the Secondary Items are loaded within that Article e.g existing standard articles.

This will allow the store to receive the Primary Article and record inventory against the Secondary Items within the store.



5.4 – System Landscape Diagram (SMART / CASS / SAP)

Interface 1: is the existing SMART to CASS range from POG Interface. POGs will still not be able to be activated until there are no source of supply issues in CASS. This interface will continue to only send to CASS for standard sales statuses (prefixes) until the last category is migrated to SAP.

Interface 2: Once ranging has been successfully established in CASS via Interface 1, this interface will send the RFP listing from SMART to SAP (from both non standard and standard sales statuses (prefixes)).

Interface 3: For manually listed articles in SAP, this interface will send ranging to CASS. Any ranging that cannot be established in CASS due to source of supply issues will be reported on a SAR report. This Interface will continue to only send to CASS for standard sales statuses (prefixes) until last category is migrated to SAP.

Interface 4: SMART will need to turn on the RFP flag at Article level and to interface it to SAP, prior to ranging a new article or migrated article in SAP via Planogram.

Integrity 4: is the existing SMART – CASS weekly integrity that is run every Sunday comparing CASS with SMART POGs.

Integrity 5: is the new SAP – CASS weekly integrity for manually listed articles in SAP that is run weekly every Sunday at the same time as Integrity 4.

Integrity Report 6: is a report that shows the discrepancies between RFP listing in SAP and the SMART POG. This just reports the differences, but does not fix the differences.

Note: Range from Planogram is being maintained at an Article level in SMART .

Interface 4

Set RFP = Y

Interface 2



5.5 – New Article Creation Workflow Process

The steps below outline the process for creating an article for the total organisation. It does not include the DC Ranging process or the Store Ranging process.

The new Article Creation process is as follows:

BM/CM finalises range review decisions.

BM/CM advises the Vendor of which item submissions were successful and which were not.

BM/CM reviews article submission summary paperwork (WNAS).

The BM/CM captures internal WOW article information on the WNAS form and submits to BSS (as well as the AA/CA).

The Vendor submits the new article submission electronic forms.

This information is received electronically in SAP (in PRICAT (Price Catalog area) (WAF & WPF).

BSS creates the Article in SAP and add WOW details (from the WNAS) such as Article Description, Merchandise Category, etc.

BSS release the article via workflow to the AA/CA.

AA/CA enriches the Corporate Data of the Article(s). (This includes acceptance / rejection of the Cost price and enriching Basic and Purchasing view of the Article.)

AA/CA will receive a new workflow to capture the Districts (States), SoS information and defines the fixed Vendor for the Article.

This creates the Logistics store views for the relevant Logistics REFSITES. (This is explained later in Part 2 of the Listing and Ranging Participant Guide).

AA/CA will receive a new workflow to capture the Sales Data of the Article(s) (including the sell price from the WNAS) and POS data.

This is the Sales and POS views of the article. Note: For a Direct article this is the stage that the MA/SA can add the article into a POG or complete the listing procedure in SAP.

SCIT receives reports to load the article in CASS.

If the SoS of the article is warehoused; then the following workflow is triggered:

If item is internationally replenished (INDENT) then the PDC (Product Dimension Co-Ordinator) will apply the appropriate TI HI for destuffing for containers.

DC ranging will classify the DCs that the article will be supplied into.

If the carton is too heavy or the pallet is too high, SH&E Manager will receive a workflow and will review the Risk Assessment Form (which is attached to the article by BSS) and if approved will progress the workflow further.

If not approved, the workflow will go back to the BM.



DC ranging will list the article to the DC and also maintain any DC source lists where required. Note: For a DC article this is the stage that the MA/SA can add the article into a POG or complete the listing procedure in SAP.

DC Inventory for each listed DC will be sent a workflow requesting them to approve that there is available space in the warehouse to house the article.

Once all DC Inventory have accepted the article into the DC, the workflow will go to the Replenishment Administration (for locally approved articles) or International Replenishment Administration (for INDENT articles).

Workflow is progresses to the applicable DCP/VRP.

Inventory planner receives the workflow to plan the article in the replenishment systems.



5.6 – Workflow Overview

Workflow is used to handle tasks and receive information, a system similar to receiving email. Workflow messages arrive into the SAP Business Workplace by using Agent Determination.

There are six processes that trigger a workflow for a Merchandising Team:

Introduce a New Article to Woolworths

Extend an Article to a New Sales Organisation or District

Purchase Price Changes

Sell Price Changes

Article Discontinuation

Article Changes

5.7 – Agent Determination Overview

To support each workflow process, Agent Determination uses rules and validations to direct an item to the correct User ID.

Workflow determines Business Team ownership of an Article for the purposes of sending messages for the introduction of new Articles or maintenance ie Cost Price increases or Change to an Article.

Prime Business Manager

Determined by the largest sales organisation introducing the Article

Management of costs and Article changes for an Article for all Sales Organisations in the same Distribution Chain

Distributed Business Manager

Business Managers of any remaining sales organisations ranging the Article

Receives an information message informing of cost changes initiated by the Prime Business Manager

Responsible for managing all Sell Prices and Store Ranging within their Sales Organisation

Associated Business Manager

Accept costs for Private Label items (Ambient and Perishable items only, excluding Milk)

Are advised of any Sell Price changes made by the category BM/CM for Private Label Articles

Can introduce Articles if they wish





MM43 Display Article

5.9 – MM43 – Display Article

There are four types of Articles; Single, Sales Set, Display and Generic.

Transaction MM43 is used to display the attributes for an Article. Within this

transaction you can display Basic details (i.e., Coarse, Fine and Sub-section), Store

Logistics details, POS details, Sales details, Listing details and Purchasing details.

5.9.1 – Demonstration – MM43 – Display Article

Demonstration Scenario: Display the details for an Article and verify all of the details contained within the master record.


Purpose


Merchandise / Space Analyst, Merchandise Teams, DC & Network Ranging and BS&S team


Display the attributes of a article master record.

Trigger:

Perform this procedure when you need to verify the details contained in an article master record.

Menu Path:


SAP menu > Logistics > Retailing > Master Data > Article Data > Article > MM43 - Display

Transaction Code: MM43



Helpful Hints:

The article master record is split into different views. This allows you to select all views, or alternatively only select the relevant views that are required. The table below lists the views within the article master records.

View Description

Basic data Global article data such as order units, EANs, WOW Core fields (Coarse, Fine, Sub-section).

Listing Data for assortment management, listing procedures, distribution chains, listing and sales periods. This view also displays if the article is listed in RFP.

Purchasing Vendor-specific data such as purchase prices, order units, purchasing groups, delivery lead times.

Sales Sales specific data for each distribution chain, site such as sales unit, sales prices and sales price calculation.

Logistics: Distribution Center

Site specific data for distribution centres such as requirements planning, replenishment parameters, and warehouse data.

Logistics: Store Site specific data for stores such as requirements planning replenishment parameters, accounting data.

POS Determines article data sent to the POS.

Articles can be searched using different search criteria. For example, you can search for articles by the Vendor.

The following table outlines that relevant tabs that are applicable to each of the Business users:

Business Role Relevant Tabs (View)

DCP/VRP Logistics: DC

BM/CM and AA/CA Basic data, Listing, Purchasing, Sales, Logistics: Store, POS

MA/SA Basic data, Listing, Purchasing, Sales, Logistics: Store, POS

BS&S Basic data, Listing, Purchasing, Sales, Logistics: Distribution Center, Logistics: Store, POS

DC & Network Ranging Basic data, Listing, Purchasing, Sales, Logistics: Distribution Center, POS

Within the article master record, the following details / actions are also available:

Trigger workflow

View deletion status and validity date



Procedure


Display Article (Initial Screen)



Article R Enter the Article number. An article is a unit that can be procured and sold to site. The Article Master record contains the purchasing and sell details in SAP.

Example:

357363

When the Purchasing Org. field is completed, SAP will display the Vendor for the Article. This field can be left blank, if required.

If a Vendor does not exist, an information message displays in the Status bar, i.e., bottom of the screen.



Purchasing Org. R An organisational unit within Logistics, subdividing an enterprise according to the requirements of Purchasing. The form of procurement is specified through the assignment of the purchasing organisation to plant/site codes.

Example:

1000




Sales Org. R Enter the sales organisation. A sales organisation is an organisational unit that structures the company according to its sales requirements.

Example:

1005

Distr. Channel R Enter the distribution channel. The distribution channel is the channel through which saleable materials or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.

Example:

10


4. Click the button to select all the views.

If you do not want to select all views, you can select the specific view within the Views area, by clicking button to the left of the view name.





This pop-up window displays as the Purchasing view was selected and multiple Vendors supply the article.

If there was only one Vendor, the Vendor number defaults into the Vendor field and the following message displays in the Status bar: 'Purchasing data is automatically determined'.

Vendor (2) 2 Entries found






The Units of measure/EANs/dimensions section contains the item linkage details.

Note: The base and sales unit of measure are set to EA (Each), and the order and delivery unit of measure are set to CAR (Carton).

The weights and dimension details for an article will be reviewed by SH&E Manager to ensure guidelines and rules are not violated. In addition, DC Ranging and Merchandise / Space Analyst can determine the article size and weight details for storage and handling requirements.

Display Article 357363 (Basic Data)

8. Scroll across using the arrow to display further details.




Note: The POS Image column displays the date the image was sent to the Store.

9. Scroll down using the down arrow to display further details of the article in the Basic data tab.

The Fresh Food section contains the details relating to Scales group, labels and special instructions relating to label printing.

Note: The Temperature field holds the details for the temperature conditions in which the article should be stored. In this example, the Temperature indicator is set at 03 (0-4 degrees), which indicates that the article requires refrigeration.


10. Click the button to view NIP details.



The NIP panel is only used for articles that are labelled in Store. This tab displays the following details:

Maintained NIP fields

Storage and handling instructions

Product warnings.

These details also contribute to labelling and legal requirements for fresh food items.

The Country of Origin field displays the country the article was either manufactured in or packed in.

The Nutritional Informational Panel contains the article quality characteristics.

Display Article 357363 (Fresh Food Sensitive Fields)

11. Click the button to return to the Basic data tab.


12. Click the button to view all PLU's associated with the article.



Display Article 357363 (Short Text)

13. Click the tab to view additional Units of Measure (UoM).

All PLU's for the article are displayed.

Note: To identify the difference between an internal and external EAN, the internal PLU reference has a prefix of 0.

Display Article 357363 (Additional EANs)

14. Scroll across using the arrow to display further details.

The Vendor provides details on whether an article has packaging that can be displayed as a Shelf Ready Tray, and advised the minimum number of facings on the SRT. This information is displayed in the SRT Facings field.

15. Click the button to return to the Basic data tab.




16. Click the tab to view if the Article has been ranged from Planogram.

The Range From Planogram indicator determines if the article is from a Planogram.

Display Article 357363 (Listing)

17. Click the tab to view details about the Vendor.

Y = Ranged

C = Not complete in RFP

Blank = Not Ranged



The vendor displayed is the main vendor for the article.

If you wish to view the article with purchasing details relevant to a different supplying vendor, enter the vendor on the Display Article screen or by selecting the "Validity Area" button.

The current net price for the article is displayed.

Note: If a distribution chain or site specific areas are not entered in the Display Article initial screen, the Net Price value displayed is at the corporate level.

Display Article 357363 (Purchasing)

18. Click the button to view the Source List details.

Areas of Validity





Site R Enter the Site. An equivalent of Location (trading or non-trading) in Wow terminology. SAP term equating to WOW term = Location (Trading or non-trading).

Example:

3939

Areas of Validity


Display Source List: Overview Screen

21. Click the button to return to the Purchasing tab.




22. Click the button to view the Purchasing Information Record (PIR) details.

Display Info Record: General Data





24. Click the button to display the article conditions.

Order Units (Purchasing)

25. Click the Unit of Measure field to display the conditions for that UoM. For example, select

.




Overview of Condition Types

27. Click Condition Type field to select the condition type details. For example, select .

Overview of Condition Types





29. Click the tab to view all Sales pricing data.

This screen displays the price condition for the article. This includes the amount and the validity period.

Display Gross Price Condition (PB00) : Condition Supplements


The DChain-spec. field is used to enter a reason code when an article is delisted from a Sales Organisation. The Valid from field will be populated with the date the reason code was applied.



Display Article 357363 (Sales)

31. Click the DChain-spec. field.

32. Click the button to display the DChain-spec. options list.

This list displays the list of valid reason codes used when an article is delisted from a Sales Organisation.

Distribution-chain-specific article status (2) 5 Entries fou

33. Click to close the pop-up window.



Display Article 357363 (Sales)

34. Click the tab to display the Logistics: DC details.

Stock planner - this is the ID of the stock planner for the article. If this field is blank, workflow messages to the DCP/VRP will fail and be delivered to the Replenishment Administrator.

Supply Source - Indicator that identifies if the article is Direct or DC supplied.

1 = Articles supplied to the Store direct from the Vendor

2 = Articles supplied to the Store from the DC.

P-S artl status - this field identifies the reason why an article is unavailable for a period of time from the supplier. This is the Warehouse Planned Confirm Date (WPCD) in CASS.



Display Article 357363 (Logistics: Distribution Center)

35. Click the button to display the P-S artl status options.

This screen displays the list of valid P-S article status codes.

Site-Specific Article Status (1) 9 Entries found




Display Article 357363 (Logistics: Distribution Center)

37. Click the tab to display the Logistics: store details.

Sales Status - this field is used to determine if the article is Standard or Non-standard for replenishment. The value of this field will change the default value of the P-S artl status field in the Logistics: DC tab.

Perpetual Inventory - this is perpetual inventory the is only for articles not on Range from Planogram (RFP). This indicates if an article requires capturing of inventory.

SRT Display - this field indicates the Shelf Ready Tray display indicator. This is only if the carton is to be utilised.

Deletion Status - this field is used to delist an article from a Sales organisation. This will be populated once actioned in the Workflow.

Supply Source - Indicator that identifies if the article is Direct or DC supplied.

1 = Articles supplied to the Store direct from the Vendor

2 = Articles supplied to the Store from the DC.

P-S artl status - this field is used for identifying the reason why an article is unavailable for a period of time from the supplier.



Display Article 357363 (Logistics: Store)

38. Click the button to display the Deletion Status options list.

The valid Deletion Status options are displayed. This information is entered by the BM/CM or AA/CA when and article is to be discontinued. The Deletion Status field is populated with the relevant selected value.

This screen displays the list of valid Deletion status' that is automatically updated when the BM/CM delists an article.

Deletion Status (1) 3 Entries found





40. Click the button to specify a distribution chain or site view.

Areas of Validity



Sales Org. R Enter the sales organisation. A sales organisation is an organisational unit that structures the company according to its sales requirements.

Example:

1005




Distr. Channel R Enter the distribution channel. The distribution channel is the channel through which saleable materials or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.

Example:

10

Areas of Validity

42. Click the Store field.

43. Click the button to display the Store list options.

Only sites associated with the article will be displayed.

Note: Logistics REFSITES are identified by a prefix of "L".

Purchasing REFSITES are identified by a prefix of "P".

Store reference sites are identified by a prefix of "R".

Store (1) 203 Entries found

44. Scroll down using the arrow to view more Stores.

45. Select the site line item. For example, select L011.



Store (1) 203 Entries found


Areas of Validity


The validity area is now populated with the distribution chain and site details selected. ie Logistics Smkt NSW REFsite

The Logistics: store view now displays details relevant to your selection and NOT corporate or distribution chain level.




48. Click the tab to view the POS details.

Display Article 357363 (POS)

49. Scroll down using the down arrow to display further detail on the POS tab.

All sellable units of measure are displayed in the POS tab.



Display Article 357363 (POS)

50. Click the button to exit the transaction.

Result

You have now displayed the attributes of an article master record.

5.9.2 – Exercise – MM43 – Display Article

This exercise allows you to practice displaying the details for an Article master record.

Exercise Scenario: Display the details for an Article.

Transaction Code: MM43

Menu Path: SAP menu > Logistics > Retailing > Master Data > Article Data > Article > MM43 – Display




5.10 – New Article Forms

Many forms that are currently in use will be phased out with the introduction of Woolworths Limited‟s specific electronic forms for submission of Article and cost price information. The following forms will start to come into effect as of the end of October 2010, with the exception of Produce articles.

New Form Purpose Previous Form

WNAS

(Woolworths New

Article Summary)

Manually loaded data.

Used to introduce minimal data for new lines prior to submitting the Woolworths Article Form.

This form is dual purpose:

1. It provides the BM/CM with new line information to aid decision making in range reviews

2. The BM/CM completes additional Wow specific data to the CRT and AA/CA to enable the article to be loaded into SAP

Australia and New Zealand – Miscellaneous Spreadsheets

WAF

(Woolworths Article

Form)

Electronically loaded data

For the submission of new and existing product information.

This form provides information such as product details and classification, key dates, GST, pack details, store labelling and nutritional information.

Australia – UISF©, eUBF©, eCRI, GST Advice Rate, Nutritional Information, WOW Logistics.

New Zealand – UBF, iLab

WPF

(Woolworths Price

Form)

Electronically loaded data

For the submission of new and existing price information.

This form provides information such as retail price and pricing information based on geographies, source of supply, list price, invoice cost and temporary deals (i.e. not promotional deals).

Australia – UPC©.

New Zealand – Price List Template.

Core Article Form

Manually loaded data

Request for a new core article to be created for Internationally Procured Articles or Produce Articles.

Ref held

Sales Set

Maintenance Form

Manually loaded data

Request for existing articles to be linked together to create a new sellable article e.g. Deli Platters.

N/A

Note: For International Generic / Variant articles the existing BOI form is to be used. For non International Generic / Variant articles the WAF is to be used.



Other new forms required for new article introduction, in addition to the Barcode Verification Report, MSDS, Sample Submission Specification form (SSS), Quality Assurance and Risk Assessments that are supplied today, can be found below.

Forms required for each Article Scenario

Scenario GS1 WNAS WAF WPF Core Article Form

Indent Order Form (BOI)

Generic Article Form

Sales Set Form

Locally Supplied Single Article (Vendor GS1 enabled)

Locally Supplied Single Article (Vendor NOT GS1 enabled)

Locally Supplied Generic Article (Apparel,

Footwear & Underwear)

International Single Article

(Core form required for supplementary information not available on Indent Order Form)

International Generic

(Core form required for supplementary information not available on Indent Order Form)

Sales Set (In-store manufactured articles, eg. Bakery, Deli Platters, Liquor Gift Packs)

Produce Article

5.11 – GS1 Overview

GS1 is an article catalogue administered by an international association. In a future SAP release. Vendors that subscribe to GS1 will be able to submit article information to Woolworths Limited via GS1 Net will not be required to complete the WAF or the WPF.

GS1 enables Vendors to maintain all product records in a catalogue format which can be made available to all Retail partners electronically.

Forms and processes have been designed to support non-GS1 vendors. ie Woolworths Article Form (WAF). With the introduction of GS1, the term GTIN (Global Trade Item Number) will start to replace other acronyms such as EAN and barcode.



5.12 – PRICAT Overview

The function of the Price Catalogue (PRICAT) is to prepare external data for entry to, this is also known as the PRICAT staging area.


Once the Article category is setup in SAP it is unable to be changed i.e., if the article is loaded as a sales set this cannot be changed to another article category (e.g., single).

Existing naming conventions apply to all article descriptions.

Existing process still applies of checking whether an article already exists before loading a new article i.e., enter GTIN (Global Trade Item Number) first and then a description search.

Any articles that are submitted via the WAF form will not have the GST rate checked by GS1. There will also not be the internal process of getting article paperwork checked by the GST team for questionable categories. Reports will be run to verify GST code accuracy but diligence is required to ensure that the GST Rate is correct in the system for new articles.

The CASS Article number will always be the same as the SAP article number, with the exclusion of apparel items which may have up to 10 digits in their article number in SAP.

In SAP, there will only be one article number for all pack breakdown relationships. The one article can have multiple selling units of measures (which represents the multiple items in CASS).

The pack breakdown article number will be the lowest child in the relationship.

In this release, no systems other than CASS are connected to SAP. Systems like SMART, Store systems and Replenishment systems are still working off the CASS Article numbers.


You are now able to understand:

New Article Process

Types of Articles and their application

How Pack Breakdown / Sales Set articles are loaded in SAP

The function of applicable Forms and GS1



Session 6 – Searching Hints and Tips and Additional Information

6.1 – Objectives


Search for Sites

Search for Articles

Search for Assortments

Search for Vendors

Setup Favorites

Setup Parameter ID‟s

Understand the difference between Layouts and Variants

6.2 – Searching in SAP

In SAP, information can be searched on using a wildcard search, i.e., *.

The wildcard replaces characters in the search criteria.

The more information entered in the search criteria the less number of entries matching the search criteria is displayed.

When searching for specific master data objects, for example Merchandise Category, the search functionality is case sensitive and must be entered in CAPITALS, otherwise the search will be invalid and no results will display.



Site Search – WB03

The diagram below displays the different search criteria that can be used when searching for a Site(s)

The table below lists the best search criteria to use.

Search Criteria Description

Sites, general This allows you to search by the Site name and numbers.

Sites in distribution chain This allows you to search by Sales Organisation and Distribution Channel.



Article Search – MM43

The diagram below displays the different search criteria that can be used when searching for an Article(s).



Article by vendor‟s article number

This allows you to search by the Vendor number and display all Articles supplied to Woolworths Limited by the Vendor.

Article by merchandise category

This allows you to search for all Article numbers within a Merchandise Category. This is useful when the Merchandise Category is know, however the Article number is unknown.

Note: If the Merchandise Category is extensive, you can search by searching for Description within a Merchandise hierarchy. This is a search that must be in UPPERCASE.

Article by EAN (International Article Number)

This allows you to search for the SAP Article linked to the CASS Parent Item number. This is useful when a Vendor has sent a form with the EAN, however the Article number is not known.



Assortment Search – WSOA3

The diagram below lists the different search criteria that can be used when searching for an Assortment(s).



Assortments by Assortment Type and Dimensions

This allows you to search for Assortments by entering the Assortment Type, e.g., MANS for Manual Store Listing or MAND for Manual DC Listing.

Assortments in Distribution Chain by Merchandise Category

This allows you to search for Assortments by entering the Sales Organisation, Distribution Chain and Merchandise Category.



Vendor Search – XK03

The diagram below displays the different search criteria that can be used when searching for a Vendor(s)



Vendors (General) This allows you to search by the Vendor name and address details.

Vendors by Article This allows you to search by the Article number to find the Vendor who supplies the Article to Woolworths Limited.



6.3 – Setup Favorites in SAP

Finding a transaction is SAP using through the menu may present some challenges. For this reason SAP provides the ability to setup Favorites for transactions that are used on a regular basis.

Within the Favorites option in SAP, you can complete the following:

Add

Change

Delete

SAP also allows you to create folders within the Favorites folder. This allows you to organise transactions into task folders. For example, you may have specific SAP transactions that are required to be completed daily.

For further information on Favorites, refer to the NAV101 SAP Navigation eLearning module.

6.4 – Setup Parameter IDs (PIDs)

Default values within SAP can be stored. This saves data entry time and also populates the value into the screen, where ever the field name displays. For example you can have the Sales Organisation and Distribution Chain setup so these values will always default. To be able to store the value you need to identify the PID and save against your User ID.

To obtain the PID, complete the following steps:

1. Access the transaction code, e.g., MM43 for Display Article.

2. Identify the field within the transaction code and press F1, e.g., Sales Org. field.



3. Click the icon to display the technical details.

4. Take note of the Parameter ID. In this example, the PID is VKO.

5. Close the window.

6. Select the menu path: System > User Profile > Own Data. The Maintain User Profile screen is displayed.

7. Click the Parameters tab to enter the PID.

8. Enter the PID into the Parameter ID column, e.g., VKO.

9. Enter the value into the Parameter value column, e.g., 1005.

10. Press Enter to verify the details entered.

11. Click the icon to save the PIDs.

The next time you access any screen that has the Sales Organisation field in it, 1005 will automatically default.

Note: Even though values default, you are able to overtype these values if required.

For further information on Favorites, refer to the NAV102 Navigation Advanced eLearning module.



6.5 – Difference between Layouts and Variants

Layouts

Layouts refer to the way the information is displayed within a report or list in SAP. Default layouts have been predetermined. In some reports and lists, SAP allows you to change the way information is displayed.

Once the layout has been changed, you have the option of saving it. This allows you to retrieve the layout and view the information as preset.

Variants

A variant in SAP allows you to enter specific selection criteria on the initial screen and save the details. This saves data entry time and only minimal data is required to be changed once you access the report or list again.

For further details on Favorites, refer to the NAV102 Navigation Advanced eLearning module.



Search for Sites

Search for Articles

Search for Assortments

Search for Vendors

Setup Favorites

Setup Parameter ID‟s

Understand the difference between Layouts and Variants



Session 7 – Listing and Ranging Theory

7.1 – Objectives


Understand the difference between Listing and Ranging.

Understand what Assortments are and how they will be used by Woolworths.

Understand and action the process steps for Listing and Ranging.

7.2 – Listing vs Ranging

Listing is the SAP term similar but not the same as WOW Term = Ranging.

Listing is simply the assigning of an Article to a Store or DC (as done in SMART today for Stores). When Listing is created in SAP, a Listing Condition is created which is simply the link between an Assortment, a Store and an Article.

Ranging is Listing, plus the ability to order and sell. Ordering requires the listing plus source of supply; selling requires the additon of the sell price list being assigned to the relevant Article‟s Mecrhandise Category at the listed store.

Supply Source (SoS) is The Supply Source is either the DC that is supplying an Article to a Store, or the direct Vendor that is supplying the Article to the Store. It is determined through the setting up of Source Lists, Purchase Information Records (site or general specific), and Supplying Sites (which is the Store connection to DCs and the DC sequence).

Note:

The Majority of all Articles are ordered and sold; therefore we need Listing + SoS + PL to complete ranging. Some Articles however are only ordered and some are only sold. In those cases the elements of ranging as described above will vary.

Assortment Site Article + + = Listing Condition

Listing

Listing Condition

Assortment Site Article + + + SoS DC or Direct

= Ranged Price List (sell)

+



Source Lists

If an Article is supplied by more than one vendor in a Country, a Source List is used to specify the Article + Vendor + Site relationship.

Purchase Information Record (PIR)

The PIR is the connection between the Vendor and the Article that the Vendor supplies into a Purchase Organisation (Country ie AUS / NZ)

The Cost Price that the Vendor charges is managed at a National AU level and is held against the PIR.

If NZ also carry the same Article, there would be a separate PIR for Purchase Organisation 2000 NZ, as the cost would be different (NZ$).

The Purchase Information Records can be viewed through the Purchasing view of the Article.

Please Note:

A Supply Source cannot be established for a Site that has a Supply Source Indicator of 1 (order directly from Vendor) unless a valid PIR exists.

If the cost needs to vary by State or because the Source of Supply is different eg DSD vs DC, then this is managed via a PIR or Site Groups.

Vendor

Article Vendor + Site +

Vendor A

Vendor B

Vendor C

Multiple Vendors

can supply Article

Source List is needed to specify Article, Vendor & Site relationship

Article + PIR is required to specify the Vendor & Article relationship



Note: All of the above is valid for Site aswell as DC. eg If more than one vendor supplies an article within a Purchase Organisation when SOS is 2 (DC) a Source List is required.

7.3 – Assortment and Types

What is an assortment?

This is different to what we understand of assortments in CASS.

A SAP assortment is an entity that allows articles to be listed to stores or DCs.

An Assortment has stores assigned to it (referred to as Users in SAP).

When an Article is listed to an assortment, all stores attached to the assortment will be listed to the article.



By assigning stores to assortments this controls which articles a store can be

listed to. A store cannot purchase or sell an article that is not contained in one

of its assortments.

Types of Assortments

General Assortment – Can have many sites attached and is manually maintained (by the MA/SA).

General Assortments have been created for each District (State) within a Sales Organisation, as Ranging decisions are made by Districts (States).

Local Assortment – Only has one site attached and is created by SAP when the site is created. Note: the local assortment number is always the site number.

Listing

Whilst SAP supports a multitude of listing options, the recommendation is to use the following combinations:

Range from Planogram (RFP) - lists articles to stores based on the applicable Planogram in SMART. Planograms in SMART can be real space managed Planograms, (contain the articles, stores and space management data properties are correct) or they can be virtual Planograms where the articles and stores are correct, but the space management data is dummy data. This is the preferred method of listing wherever possible.

Manually Range in SAP - lists articles to stores using listing to general or local assortments.





WSL10 Listing Conditions for an Assortment

WSL11 Evaluation of Listing Conditions

WSOA3 Display Assortment

7.5 – WSL10 – Listing Conditions for an Assortment

A SAP assortment is an entity that allows articles to be listed to stores or DCs. As Assortment is similar to a POG in SMART, it is an entity similar to a SMART POG that has stores assigned to it as well as articles.

This transaction allows you to display listing information for an assortment (General or Local) or a range of assortments.

7.5.1 – Demonstration – WSL10 – Listing Conditions for an Assortment

Demonstration Scenario: Display listing conditions for an Assortment and Merchandise Category.


Purpose


Merchandise / Space Analyst and Merchandise Teams


Display all articles that have been listed to a Site or range of Sites. This will also display the relevant Planogram where applicable.

Trigger:

Perform this procedure when you want to display the articles that have been listed to a Site or a range of Sites.

Prerequisites: The articles must be listed to the site.

Menu Path: SAP Menu > Logistics > Retailing > Master Data > Assortment/Listing > Evaluations > For Assortments > WSL10 - Article per Assortment



Transaction Code: WSL10

Helpful Hints:

To view all articles within specified Merchandise Categories that have been listed to all Sites, leave the Assortment (i.e., Site) field blank and enter the Merchandise Category(s).

Do not enter * in both the Merchandise Category and Assortment fields. SAP will search for all articles within all Merchandise Categories which will reduce the effectiveness of the system.

To enter multiple values, e.g., Assortments, click the icon to the right of the fields to enter multiple selections.

Procedure


Listing Conditions per Assortment



Assortment R Enter the Assortment number in the field. An assortment in SAP is completely different then an assortment in CASS. The SAP term "Assortment" can be thought of as a container that holds Articles and Sites and is valid for a specified period of time.

Example:

4332




Merchandise Category

R Enter the Merchandise Category. A Merchandise Category is a Grouping of Articles.

Each article is assigned to only one merchandise category. This assignment is valid throughout the company.

Merchandise categories can be grouped into merchandise category hierarchy levels. Merchandise category hierarchy levels can, in turn, be assigned to higher hierarchy levels. Organizing and structuring an assortment is easily done by maintaining merchandise categories.

Merchandise Category is a Key that you use to group together several Articles or Services with the same attributes.

Example:

124010105


3. Click the icon to display the results.

The standard layout for this screen has been changed to remove blank fields.

You can customise the view in layouts.

Please refer to SAP Nav Advanced for how to maintain report layouts.

This screen displays the articles within the Merchandise categories that are listed for that Site (i.e., Store).

The LS (Listing Source) column displays the type of assortment for each Article.

L = Layout module (POG)

3 = Local Assortment

7 = General Assortment




To export the results, complete the following:

a) From the List menu, select Export

b) Click Local file

c) Select the Spreadsheet option

d) Select the Directory to save the file

e) Enter a Name for the file

f) Click Generate

4. Click the icon to exit the screen.


5. Click the icon to exit the transaction and return to the SAP Easy Access SAP Retail screen.

Result

You have successfully displayed all articles for a Site or a range of Sites.



7.5.2 – Exercise – WSL10 – Listing Conditions for an Assortment

This exercise allows you to practice displaying listing conditions for an assortment or a range of assortments.

Exercise Scenario: Display the listing conditions for all Assortments assigned to a Merchandise Category.


Menu Path: SAP Menu > Logistics > Retailing > Master Data > Assortment/Listing > Evaluations > For Assortments > WSL10 - Article per Assortment


7.5.3 – Demonstration – WSL11 – Evaluation of Listing Conditions

Purpose:

This transaction is used when enquiring on all listings against a nominated article/s.

This is the main listing enquiry screen that should be used.

This demonstration shows you how to display listing conditions for an assortment or a

range of assortments.

Demonstration Scenario:

Display the listing conditions for an Article to verify the assortments the article is listed to.


Purpose


Merchandise / Space Analyst, Merchandising Teams and DC & Network Ranging


View the current listing conditions for a store/article/merchandise category combination.

Trigger:

Perform this procedure when you need to view the current listing conditions for a store / article/ merchandise category combination.

Prerequisites:

The listing must exist in SAP (otherwise the return is blank as opposed to negative).



Menu Path:


SAP menu > Logistics > Retailing > Master Data > Assortment/Listing > Evaluations > For Article > WSL11 - Tree Display of Listing Conditions


Helpful Hints:

Enter the relevant Sales Organization, and Distribution Channel e.g., 1005 for Woolworths Smkt and 10 for Retail. This ensures that only listing conditions for either Stores or Distribution Centres display in the results. Any of the other fields can be completed as required.

The more selection criteria entered in the initial screen, the quicker SAP will respond and display the results.

If you leave the selection criteria too broad SAP will slow down or timeout.

Do not enter * in both the Article and Assortment fields. SAP will search for all articles within all Merchandise Categories which will reduce the effectiveness of the system.

Click the icon to the right of the fields to enter multiple selections.

Procedure


Evaluation of Listing Conditions





Article R Enter the Article number. An article it a unit that can be procured and sold to site. The Article Master record contains the purchasing and sell details in SAP.

Example:

166510

To view all articles within a Merchandise Hierarchy, ensure that Merchandise Category field and Customer Number for Site fields are completed.

The more selection criteria entered, the quicker SAP will display the results.



Sales Organization R Enter the Sales Organization. The Sales Organization manages the sale and distribution of Articles throughout the different Business units (Divisions).

Example:

1005

Distribution Channel R Enter the Distribution Channel. The Distribution Channel is the method by which Articles are sold to a Customer.

Example:

10


4. Click the icon to display the results.




5. Click the icon to change the breakdown of the details.

Define Sort Order

This table allows you to define how the details are displayed in the previous screen.

Within this table you can complete the following:

Hide columns, e.g., Assortment

Display columns, e.g., Article Description

Move the order of the Columns that display



Define Sort Order

6. Click the Sort criteria to hide. For example, click the Assortment label.

Define Sort Order

7. Click the option to move the selected label to the Column Set table. The column will not display on the previous screen.



Define Sort Order

8. Click the option to move the order of the columns.

Define Sort Order

9. Click the icon to confirm the changes.


10. Click the option to expand the tree structure.




11. Click the icon twice to exit the transaction.

Result

You have successfully viewed the listing conditions for an article/site and Merchandise Category combination.

7.5.4 – Exercise – WSL11 – Evaluation of Listing Conditions

This exercise allows you to practice displaying listing conditions for an assortment or a range of assortments.

Exercise Scenario: Display the listing conditions for an Article to verify the assortments the article is listed to.


Menu Path: SAP menu > Logistics > Retailing > Master Data > Assortment/Listing > Evaluations > For Article > WSL11 - Tree Display of Listing Conditions


7.6 – WSOA3 – Display Assortment

Transaction WSOA3 is used to display an Assortment. The information displayed in

the Assortment will show you the listing procedures, e.g., Z3 for Manual Store listing

and the Assortment Users (i.e., Sites) assigned to the Assortment.



7.6.1 – Demonstration – WSOA3 – Display Assortment

Demonstration Scenario: Display the details for an existing General Assortment to display the Assortment Users assigned to this Assortment.


Purpose


Merchandise / Space Analyst and Merchandise Teams


Display a General Assortment to view the details of the General Assortment as well as the Sites assigned to the General Assortment.

Trigger:

Perform this procedure when you want to verify the details of a General Assortment.

Prerequisites:

The General Assortment exist.

Menu Path:


SAP menu > Logistics > Retailing > Master Data > Assortments/Listing > Assortment > General Assortment > WSOA3 - Display

Transaction Code: WSOA3

Helpful Hints:

When searching for an Assortment, the best search option to select is the Assortment by Assortment Type and Dimensions. This allows you to enter the Assortment Type of MANS for Manual Store Listing or MAND for Manual DC Listing.



Procedure


Display Assortment: Initial

2. Click the icon to display the Assortment search options.

Assortment (1)

3. Click the icon to display the list of possible search options.



Assortment (1)

4. Select the Assortments by Assortment Type and Dimensions search option.

Restrict Value Range





Assortment Type R Enter the Assortment Type. Assortment attribute that enables you to control the strategic content of the assortment and how it is handled in assortment definition, planning, and procurement.

Example:

MANS

6. Click the icon to view General Assortments created for Manual Store listing.

Assortment (1) 1 Entry found

7. Click on the relevant General Assortment number. For example, 3.


Display Assortment: Initial




Display Assortment: Basic Data

10. Click the tab to review the CustomerNoSites (i.e., Stores) assigned to the General Assortment.

Display Assortment: Assortment User


Result

You have displayed a General Assortment.



7.6.2 – Exercise – WSOA3 – Display Assortment

This exercise allows you to practice displaying the details of an Assortment.

Exercise Scenario: Verify the Assortment users that are assigned an existing General Assortment.

Transaction Code: WSOA3

Menu Path: SAP menu > Logistics > Retailing > Master Data > Assortments/Listing > Assortment > General Assortment > WSOA3 - Display


7.7 – Ranging and Source of Supply (SoS)

In CASS, to Range an item, not only does the item need to be assigned to the store, the store needs a source of supply. Some of the entities required in CASS to establish SOS are State Consumer Units, State Vendor Traded Units, Sell Price Group Assigned and DC SOM Links.

Likewise in SAP, for Ranging to be established there needs to be Listing + SoS.

SAP Ranging = Listing + Valid SoS (DC or Vendor) + Price List Assignment to Store.

The entities in SAP used to determine SoS are:

1. SoS indicator on the Logistics: store view in the article master record.

2. Purchase Information Records (PIRs) – connection between the Vendor and the Article that the Vendor supplies.

3. Source Lists – connection between the Article, Vendor and Site (i.e., Store or DC).

4. Supplying Sites – assignment of DCs that can supply a store.

Source of Supply Indicator on the Logistics: Store view of the Article Master

Record

For every Store that is listed to an article, there needs to be a Logistics: store view created for the article.

When the Article is listed to a store, the system automatically creates a Logistics: store view for the store.

When the Article is listed to a DC, the system automatically creates a Logistics: DC view for the DC. The Source of Supply indicator is the mandatory field required to create this view.



The Source of Supply indicator can be 1 of 2 values.

1 – Standard – this indicates that the Site is ordering the article directly from the vendor. For example, for a store, the article would be a DSD article ordered directly from the Vendor. All DCs will always have a 1 as the SoS indicator, as a DC always orders from a Vendor.

2 – Stock Transfer – this indicates that the Site is ordering the article from the DC. The entities used to establish the SoS differ on whether the SoS is 1 or 2.

In the following example, the Supply Source indicator (on Logistics: store tab) for the Double Bay store is 2.

This indicates that the store is ordering the Article from a DC.



Purchasing Information Record (PIR)

The PIR is the connection between the Vendor and the Article that the Vendor supplies into a Purchase Organisation (Country – AUS / NZ). The cost price that the Vendor charges is held against the PIR. The Purchase Info Records can be viewed through the Purchasing view of the Article.

A Supply Source cannot be established for a Site that has a Supply Source Indicator of 1 (order directly from vendor) unless a valid PIR exists.

The following example displays a PIR for a cigarette Article for the Vendor British American Tobacco for Purchase Organisation 1000.

Source Lists

If an article is supplied by more than one vendor, within a Purchasing Organisation, then source list are required for all sites that have a SoS Indicator 1 (order direct from Vendor).

A Source List is the connection between the Article and the Vendor and Store / DC.

A Source List is used by the system to determine exactly which Vendor is supplying a Site when the system has more than 1 PIR to choose from.

For example, Stores 1131, 1134 &1138 are supplied Hasting Tasty Cheese 1kg directly by “Wauchope Cheese Co.”, but stores 1895, 1997 & 1756 are supplied by a local distributor “Barry‟s Dairy Group”.



Source L ist 1

Store 1131, 1134, 1138

Vendor - W auchope Cheese

C o.

Source L ist 2

Store 1895, 1997, 1756

Vendor –Barry‟s D a iry G roup

Note: Source Lists should be created whenever a new vendor is introduced within the same Purchasing Organisation for an existing article.

When a secondary vendor is loaded to SAP it is the responsibility of the BSS team to create a Source list for the existing Vendor.

For new Vendors, it is the responsibility of the MA/SA to maintain all subsequent source lists for stores ordering direct from the vendor.

This will avoid errors appearing on the Range Check Error Report (ZMAS0026).

The following example displays a Source List for a poultry article for a DC and displays the Vendor supplying the article to the DC (extract from the me0m Source List enquiry screen).



7.8 – Article Scenarios displaying how SoS is Determined

The below diagrams show different article scenarios and what source of supply entities are used by SAP to determine Source of Supply.

If any of these source of supply elements are not established, then the article

will appear on the range check error reports for the listed Stores or DCs.

Direct to Store

Single Vendor



Direct to Store

DSD Workbench

2 Vendors



DC Ranged

Single Vendor



DC & Direct Ranged

Single Vendor



DC & Direct Ranged

DSD Workbench

2 Vendors





Understand the difference between Listing and Ranging.

Understand what Assortments are and how they will be used by Woolworths.

Understand and action the process steps for Listing and Ranging

DC Ranged

2 Vendors



Module Summary

You are now able to understand and use SAP transactions to perform the business processes that make up Merchandise / Space Analyst Part 1 - General Information.

The following sessions have been covered:

Merchandise Categories

Site

Vendor Overview

Article Processes and Forms

Helpful Hints and Tips

Listing and Ranging Theory

Relevant Links

Links

The following information allows you to view the forms that have been covered in this material.

Forms

Name Location

All Forms SAP Central / Forms

Glossary

New Terminology http://wownet/sites/ss/sap/Shared%20Documents

SAP%20Terminology%20v%201.0.pdf

Need More Help?

Online Help on SAP Central

Transaction documentation including help cards and reference guides can be accessed through the following link:

http://nnorsogfas112.woolworths.com.au/gm/folder-1.11.86714?mode=EU

Business and Technology Services

A Support team is available. Ensure you have consulted the documentation in this Training Guide, SAP Online Help and spoke to a colleague prior to emailing BSS – Central Mailbox.

http://wownet/sites/ss/sap/Share

http://nnorsogfas112.woolworths.com.au/gm/folder-1.11.86714?mode=EU