Sap retail master data workbench for direct store delivery

1

SAP for RetailDSD Master Data WorkbenchERP2005 EhP4

2

© SAP 2008 /

At the end of this unit, you will be able to:Describe the functionality of the DSD Master Data WorkbenchLocate the transaction in the SAP Easy Access MenuKnow the handling of the different screen areasPerform a selectionDisplay / maintain supply relationshipsDisplay / maintain purchasing info record dataDisplay / maintain pricing data

Remark: Additional information is provided in the notes section of the slides

Objectives

3

© SAP 2008 /

1. Purpose of the Workbench2. Start the Workbench

2.1. Locate the Workbench in the SAP Easy Access Menu2.2. Start the Workbench with its Transaction Code

3. Selection4. Tree Areas & Personal Settings

4.1. Selected Objects Area4.2. Supply Relationships Area4.3. Personal Settings

5. Working Areas5.1. Purchasing Info Records Area5.2. Pricing Area

Agenda

4

© SAP 2008 /

Manufacturer: Provides suppliers/distributors with DSD articles

DSD Supplier: Provides several stores with DSD articles

Store: Receives DSD articles from several DSD suppliers

DSD Article: Transferred from DSD supplier directly to the storesA4A3

A1 A2

Legend

A3

A2

A4

A1

A2

A4

A1A3

Direct Store Delivery: Supply Network

Direct Store Delivery (DSD) is a business process to sell and distribute goods (articles) via distributors (suppliers) directly to the retailer's store, typically bypassing the retailer's warehouses.The DSD process is specific for articles of a certain range of merchandise categories, i.e. alcoholic beverages, carbonated soft drinks, bread, snacks and dairy products. These products all have extremely high shelf turnover (product velocity) and limited shelf life.The direct business relationships exist between the retailer and the distributors which act as vendors. All product, quantity, price, etc. negotiations in detail will be done with the distributors. As a result there is a contract between a distributor and the related set of stores which can be delivered by this distributor for a given set of articles. The contract may cover purchase price agreements, deals (discounts) and promotions.The manufacturer determines the regional coverage responsibilities of the concerned distributors. A distributor is allowed to deliver to a given region only. A store belonging to another delivery region needs to be delivered by another distributor. Frequently the regional delivery responsibilities of a distributor are subject to change.Between the distributors and the category managers of a retailer detailed cost (purchase price) negotiations take place. Based on federal, county and city specific tax laws (especially for North America) and logistical conditions (e.g. special transportation costs) the category manager may get very different costs for a given set of stores for the same article. The aim of the category manager is to maximize the margin for these articles and therefore a store specific sales price needs to be derived. The change of the regional delivery responsibilities of a distributor forces the retailer to change the business relationship to a given distributor. Based on those circumstances, new articles are added to or existing articles are removed from the shelf assortment, stores are added to or removed from certain distributors or distributors are added to or removed from stores. These changes apply in general to several articles and several stores (mass changes). The price data of some articles could be similar for a group of stores. There is a need to copy most of the price data in case a new assignment or a reassignment for distributors, stores or articles is necessary.For a single article and a given store there is exactly one delivery strategy: DSD or distribution center based delivery. In the case of DSD the category manager defines a supply relationship; for example, each store can get its own distributor for a given article. On the basis of this supply relationship (distributor-store-article) the distributor is authorized to deliver only the specified articles to the given store.

5

© SAP 2008 /

An intuitive, user friendly solution which facilitates DSD processing from a master data perspective needs to support the following issues:

Providing a data model to store the supply relationship related master data(vendor-store-article relationships; store specific purchasing, sales and promotion prices)Mass maintenance user interface (UI) for the category manager to create and change the supply relationships in one stepDecision cockpit for the category manager to review related master data

Business Requirements

An intuitive, user-friendly software solution which facilitates DSD processing from a master data perspective needs to support the following issues:

Using a data model to store the supply relationship related master data

vendor-store-article relationships

store specific purchase prices

store specific sales and promotion prices

Mass maintenance user interface for the category manager to create and change the supply relationships

Easy assignment of stores to vendors based on a given set of articles

Easy reassignment of any relationships (e.g. reassigning stores to a new vendor, reassigning articles to a different vendor)

Decision cockpit for the category manager to review related master data

Overview about all pricing related information to enable the category manager to drive his business decisions concerning the sales price

6

© SAP 2008 /

Use Cases

To create the relationships between a vendor and a group of stores for a given set of articles, and to maintain these relationships on a regular basis, a specific maintenance UI is needed . Based on the created relationships, the pricing information needs to be maintained in an streamlined and efficient way.

From a business point of view the new workbench supports the following master data related business processes.

Article based processesNew article introductionArticle reassignmentArticle removal

Store based processesNew store distributionStore reassignmentStore distribution termination

Vendor based processesNew vendor introductionVendor reassignmentVendor removal

Pricing data maintenance

Article based processes

New article introductionBased on negotiations with the vendor the category manager plans to add new articles to the store assortment.

Article reassignmentBased on negotiations with the vendors the category manager plans to move articles from a vendor to another vendor for the related set of stores as delivery responsibilities are changed.

Article removalBased on negotiations with vendors the category manager plans to remove some articles from vendors for the related set of stores

Store based processes

New store distributionBased on negotiations with vendors the category manager plans to associate a new store to existing vendors with already assigned articles for a similar store.

Store reassignmentBased on negotiations with vendors the category manager plans to replace a vendor with another vendor (same articles) for a given store (or set of stores).

7

Store distribution terminationBased on negotiations with a vendor the category manager plans to remove a store (set of stores) from a current vendor

Vendor based processes

New vendor introductionBased on negotiations with the new vendor the category manager plans to add this vendor to a store (set of stores)

Vendor reassignmentBased on negotiations with vendors the category manager plans to replace a vendor with a new vendor for all stores (same articles)

Vendor removalBased on negotiations with a vendor the category manager plans to remove a vendor for all stores

Pricing data maintenance

Based on negotiations with vendors the category manager plans to maintain pricing data for vendor-store-article relationships

8

© SAP 2008 /

Current Maintenance Capabilities

In the existing ERP Retail system we have to maintain several data in different transactions to reflect the supply relationship related master data :

Purchasing info recordListing co

ndition

Sourcelist

Article

Store Vendor

Promotionprice Sales

price

Purchaseprice

In order to carry out the necessary maintenance a lot of different transaction need to be called. Some of them are not able to process more than one article/store/vendor at a time. So it is a really time consuming activity.

9

© SAP 2008 /

The New DSD Master Data Workbench

The DSD Master Data Workbench offers the following capabilities to fulfill the business requirements:It uses existing data models provided by SAP for Retail, no additional master data have been introduced to store the supply relationship related master data. In detail we have:

vendor-store-article relationships represented by source list records, purchasing info records and listing conditionsstore specific purchase pricesstore specific sales and promotion prices

Mass maintenance user interface for the category manager to create and change the supply relationships

Easy assignment of stores to vendors based on a given set of articlesEasy reassignment of any relationships (e.g. reassigning stores to a new vendor, reassigning articles to a different vendor)

Decision cockpit for the category manager to review related master dataOverview about all pricing related information to enable the category manager to drive his business decisions concerning the sales price

The DSD Master Data Workbench collects several existing master data maintenance transactions in one common application to have a single point of entry. For more detailed information the user is able to navigate to existing applications to have additional maintenance capabilities.

10

© SAP 2008 /

DSD Master Data Workbench: Related Master Data Objects

Master Datarelevant for theread process

Master Datawhich needsto be createdor changed

Easy to use UI

Master data for articles, stores and vendors are stored in the existing SAP for Retail master data models based on article, site and vendor. There are no DSD specific master data enhancements required. If necessary the manufacturer can be created as an additional vendor. He can be linked to the vendors for example via a special partner function.The prerequisite is that the basic master data (for articles, stores and vendors) has been created in advance. Especially the article master data for an article should be set up by one of the standard maintenance transactions. The basic setup includes besides basic data also sales, logistic and POS data. The creation of the purchasing data in advance is possible with standard transactions but could also be done later if the relations to all vendors are known.For the creation of vendor-store-article relationships the existence of listing conditions is not required. The following process variants are possible:

The listing conditions have been created in advance via the existing assortment planning applications.This process variant can be reasonable if the assortment is very similar for most of the stores. Based on that global assortments will be used. The listing conditions will be created after the creation of the relationships via the existing assortment planning applications.This process variant is comparable to the process variant where the listing conditions have been created in advance. In addition follow-up operations (e.g. ordering) can be prevented by the missing listing conditions even if the master data relationships still exist.The listing conditions will be created automatically via the new application as local assortments. This process variant can be reasonable for articles which will be sold only in single stores or which will be introduced as test articles.

11

For the creation of vendor-store-article relationships the existence of purchase and sales prices is not required. The following process variants are possible:

The prices have been created in advance via the existing price maintenance applications.This process variant can be reasonable if the prices are very similar for most of the stores and therefore they will be stored on a higher data retention level. Existing prices maintained on higher level and/or on store level will be displayed in the new application. The user can maintain store specific prices. Prices on higher data retention levels cannot be changed.The prices have not been created in advance.This process variant can be reasonable if the prices are individual for each store and therefore they will be stored on store level. The new application allows the mass maintenance of these store-specific prices.

12

© SAP 2008 /






Agenda

13

© SAP 2008 /

DSD Master Data Workbench: Start via SAP Easy Access Menu

The application ca be found in the following SAP Easy Access menu:

SAP menu -> Logistics -> Retailing -> Master Data -> Plant Data ->Environment

SAP menu -> Logistics -> Retailing -> Master Data -> Vendor Data -> Environment

SAP menu -> Logistics -> Retailing -> Master Data -> Material Data -> Environment

The transaction code is WDSD_WB

Note: If the tree Retailing beneath Logistics is missing in the SAP Easy Access Menu check if menu W10T is set as the “Start menu” for the user (Transaction SU3 tap strip ‘Defaults’).

14

© SAP 2008 /

DSD Master Data Workbench: Screen Areas

Selected Objects Area

Supply Relationships Area

Purchasing Info Record / Pricing Area

Application Log Area

The screen of the DSD Master Data Workbench is split into 4 main areas:

"Selected Objects" areaAll vendors, stores and articles determined by the selection are displayed in this area. This area may also be called “Work List” area, because it contains the master data objects upon which the DSD Master Data Workbench will work.

“Supply Relationships” AreaAll existing supply relationships for the selected objects are displayed here. In change mode new relationships can be created in this area by copy or drag & drop functionality. It is used to navigate through the supply relationships determined by the selection.

"Purchasing Info Records" area / "Pricing" areaYou can switch between purchasing info record data and pricing data by pressing the corresponding switch buttons. When creating new supply relationships for vendor –article combinations where no purchasing info record exists a new purchasing info record needs to be created first. This area may also be called “Work” area.

Application Log AreaMessages which will be issued during the processing are displayed in this area. Some messages have an additional long text description to provide more detailed background information.

15

© SAP 2008 /






Agenda

16

© SAP 2008 /

DSD Master Data Workbench: Simple Selection

According to the selection criteria the master data objects (vendors, stores, articles) will be shown in the "Selected Objects" area and all existing supply relationships (source list entries) for these master data objects and the specified key date are displayed in the “Supply Relationships” area of the DSD Master Data Workbench.

Required fields for selection:

The fields ‘Purch. Organization’ and ‘Key date’ are mandatory fields. ‘Key date’ is the validity date for the selection of time dependant data like supply relationships (source list entries), pricing (purchase and sales) and listing.

At least one of the fields ‘Vendor’, ‘Store’, ‘Article’ must be filled.

17

© SAP 2008 /

DSD Master Data Workbench: Simple Selection Results

2

1

3

The selection was carried out with the following data:

Purchase Organization: R001

Vendor: HAWKER to PEDDLER

Store: DS01

Article: BEER01

Key date: 12.10.2008

The key date and the purchasing organization are displayed in the upper area of the workbench (1)

The following master data has been found and is displayed in the "Selected Objects" area (2):

Vendor: HAWKER, MERCHANT and PEDDLER

Store: DS01

Article: BEER01

And for these master data objects only one supply relationship exists for the specified key date and is displayed in the "Supply Relationships" area (3):

HAWKER – DS01 – BEER01

18

© SAP 2008 /

DSD Master Data Workbench: Advanced Selection

According to the selection criteria the master data objects (vendors, stores, articles) will be shown in the "Selected Objects" area and all existing supply relationships (source list entries) for these master data objects and the specified key date are displayed in the "Supply Relationships" area of the DSD Master Data Workbench.

Required fields for selection:

The fields ‘Purch. Organization’ and ‘Key date’ are mandatory fields. ‘Key date’ is the validity date for the selection of time dependant data like supply relationships (source list entries), pricing (purchase and sales) and listing.

At least on of the fields ‘Vendor’, ‘Store’ and ‘Article’ must be filled.

Depending on the specified master data selection criteria the selection will be carried out according to the following rules:

If the fields ‘Vendor’, ‘Store’ and ‘Article’ are filled, all master data objects which match the selection criteria will be displayed in the "Selected Objects" area and all existing supply relations for these master data objects will be displayed in the "Supply Relationships" area. There are some site, store and article categories which will be filtered out during selection:

Sites which are a distribution center, industry plants and department stores are excluded from the selection.

Only articles with article category ‘Single article’, ‘Generic article’ and ‘Display’ are selected. Articles belonging to other article categories are excluded from the selection e.g. sets, prepacks, value only articles or reference articles.

19

If not all of the fields ‘Vendor’, ‘Store’ and ‘Article’ are filled, at first all master data objects which match the selection criteria will be examined with the same constrains mentioned above. In addition the source list entries for the so far retrieved master data objects will be read and for the master data selection criteria not maintained in the selection screen all values are retrieved from these source list entries and checked against the constrains mentioned above. In the selected objects not only the master data objects retrieved according to the selection criteria for ‘Vendor’ and/or ‘Store’ and/or ‘Article’ are displayed, also the master data objects retrieved by reading the source list entries are displayed.E.g. a vendor and a store are entered in the selection screen. The field for article is left empty. The vendor master data and the store master data is retrieved, then the supply relationships for these master data combinations are retrieved and all found articles are displayed in the "Selected Objects" area and the existing supply relationships are displayed in the "Supply Relationships" area.

Additionally, if no supply relationships can be found for the specified selection criteria (independent of the fact that all fields (vendor, store and article) or just one or two of these selection fields have been filled) the purchasing info records for the read vendors or/and articles are searched and the found articles and vendors based on the existing purchasing info records are displayed in the selected objects.E.g. a vendor and a store is entered in the selection area. There are no source list entries for this vendor and store. All purchasing info records for the vendor are selected and all articles resulting from these purchasing info records are displayed in the "Selected Objects" area as addition.

20

© SAP 2008 /

DSD Master Data Workbench: Advanced Selection Results

1

2

3

4

The selection was carried out with the following data:

Purchasing Organization: R001

Vendor: HAWKER, MERCHANT, PEDDLER, TRADER

Store: DS01 to DS20

Article:

Key date: 12.10.2008

The key date and the purchasing organization are displayed in the upper area of the workbench (1).

In the "Selected Objects" area the 4 vendors and the 20 stores are displayed and in addition 3 articles (2).

Because no articles are specified in the selection the articles are retrieved based on the existing supply relationships. The found supply relationships are displayed in the "Supply Relationships" area (3).

The application log informs about the action carried out (4).

21

© SAP 2008 /

DSD Master Data Workbench: Selection of Additional Master Data Objects

1

2

The initial selection was carried out with the following data:

Purchase Organization: R001

Vendor: HAWKER

Store: DS01

Article: APPLE-PIE01, BEER01

Key date: 12.10.2008

In addition vendor PEDDLER is selected.

22

© SAP 2008 /

DSD Master Data Workbench: Additional Selection Results

1

2

3

The vendor PEDDLER is now listed in the "Selected Objects" area (1).

In the "Supply Relationships" area all supply relationships existing for the complete set of selection criteria are displayed (2).

The “select additional master data” functionality can be used repeatedly and all selection criteria are stored. In order to check the selection criteria entered so far click the “Selection” button (3).

Selection criteria can be saved as selection variants for future reuse.

23

© SAP 2008 /






Agenda

24

© SAP 2008 /

DSD Master Data Workbench: Status Information for Selected Objects - Vendor

Purchasing block status

Deletion Flag

In the "Selected Objects" area additional information is displayed for vendors.

There are two indicators which show the purchasing block status and the deletion flag for vendors.

The indicator “Purchasing block status” for the vendor is

Green, if the vendor is not blocked at all or the vendor is not blocked for the selected purchasing organization.

Red, if the vendor is blocked for the selected purchasing organization or for all purchasing organizations.

The indicator “Deletion flag” for the vendor is

Green, if the vendor has no deletion flag at all or the deletion flag is set for another purchasing organization.

Yellow, if the deletion flag is set for all purchasing organizations or the selected purchasing organization.

25

© SAP 2008 /

DSD Master Data Workbench: Status Information for Selected Objects - Article

Purchasing block status

Deletion flag

In the "Selected Objects" area additional information is displayed for articles. There are two indicators which show the purchasing block status and the deletion flag for articles.The indicator “Deletion flag” for an article is

Green, if no deletion flag is set for the article or the deletion flag is set for the article but in customizing the category for this message is set to “no message”.Yellow, if the deletion flag is set and in customizing the category for this message is set to “warning”.Red, if the deletion flag is set and in customizing the category for this message is set to “error”.The path to the customizing is: SAP IMG -> Materials Management -> Purchasing -> Environment Data -> Define Attributes of System Messages: Message Application Area = ME, No. = 051

The indicator “Purchasing block status” for an article isGreen, if

the cross site article status is not setthe cross-site article status is set with valid from date in the futurethe cross-site article status is set with initial valid from date and in the customizing the purchasing message is set to “no message”the cross-site article status is set with valid from date is in the past or today and in the customizing the purchasing message is set to “no message”

26

Yellow, if the cross-site article status is setwith initial valid from date and in the customizing the purchasing message is set to “warning”

With valid from date in the past or today and in the customizing the purchasing message is set to “warning”

Red, if the cross-site article status is set with initial valid from date and in the customizing the purchasing message is set to “error”

with valid from date in the past or today and in the customizing the purchasing message is set to “error”

The path to the customizing is: SAP IMG -> Logistics – General -> Material Master -> Settings for Key Fields -> Define Material Statuses

Note: Please remember that ‘Purchasing block status’ for articles is time dependant and rely on the ‘Key date’ which you specified in the selection screen.

27

© SAP 2008 /

DSD Master Data Workbench: Status Information for Supply Relationships

Listing Condition

Purchasing Info Record

In the "Supply Relationships" area additional information is displayed for articles.

There are two indicators which show the purchasing info record and the listing condition status for articles.

The indicator “Purchasing Info Record” is

Green, if there exists a purchasing info record on level vendor-article.

Yellow, if there exists no purchasing info record on level vendor-article.

The indicator “Listing Condition” is

Green, if valid listing conditions for the article-store relationship based on the local assortment or any global assortment related to the store exists.

Yellow, if there exists no valid listing condition.

Note: Please remember that the status of the ‘Listing Condition’ is time dependant and rely on the ‘Key date’ which you specified in the selection screen.

28

© SAP 2008 /

DSD Master Data Workbench: Context Menu for Selected Objects (1)

Switch to “Full screen” mode /

Switch to “Normal” mode1

4

3

2

The "Selected Objects" area can be expanded to occupy the left side of the DSD Mater Data Workbench by pressing the “Switch to full screen mode” button (1). It can be reduced back with the same button.

For all master data objects the “Show master data” menu function is available in the context menu (press right mouse button and choose according to (2) or (3)). The system will switch to the appropriate master data transaction:

Vendor: Transaction XK03 (Display Vendor) will be started; the vendor master data can be displayed.

Store: Transaction WB03 (Site Display) will be started; the store master data can be displayed.

Article: Transaction MM43 (Display Article) will be started; the article master data can be displayed.

For vendors and stores additionally the “Show store/vendor location map” menu function is available (4). In order to display the address data and its location in the map the BAdIWDSD_BADI_UI_ENHANCEMENTS_E (Method IF_WDSD_BADI_UI_ENHANCEMENTS_E~CREATE_URL_FOR_BROWSER_CALL) needs to be implemented by the development team and the address data of the vendor/store must be maintained.

29

© SAP 2008 /

DSD Master Data Workbench: Context Menu for Selected Objects (2)

1

2

3

To locate an article in the "Selected Objects" area the “Find” button can be used (1). The tree will be expanded, if necessary, and the object is highlighted.

There are two ways to select additional objects:

With the toolbar function “Additional Selection” (2) you are able to select any kind of these 3 master data objects.

In the context menu for the node of a single master data object (3) you are able to select additional master data objects of this kind. This example shows the context menu for the article node. The context menu is also available for store and vendor nodes.

30

© SAP 2008 /

DSD Master Data Workbench: Personal Settings

The DSD Master Data Workbench uses parameters (General Settings) which have a major impact on the processing behavior of the workbench. Each user can set his own preference in the “Personal Settings”. These personal settings are stored on database.

Overwrite overlapping future relationshipsDefault value: Yes

Controls whether existing overlapping future relationships (source lists, listing conditions) will be overwritten or whether the new relationship will not be created.

Source list records for each new vendor-store-article relationship will be created starting with the "key date" you entered and ending with 12/31/9999. This setting determines whether future source list records will be deleted; if they cannot be overwritten, an error message will be displayed.If the “Create missing listing conditions for local assortments“ indicator is set the requisite listing conditions will be created for the store-article relationship you provided, starting from the entered "key date" and ending with 12/31/9999. This setting determines whether future listing conditions will be deleted; if they cannot be overwritten, an error message will be displayed.

Copy purchase pricesDefault value: Yes

Controls whether purchase prices shall be copied or not to new relationships.

Only purchase prices on store level will be copied. If the source supply relationship does not have a purchase price on store level no data can be copied.Additionally, if new purchasing info records need to be created because a new vendor-article relationship is created, the purchase price on vendor level is also copied to this purchasing info record depending on this setting. In general a copy of the purchase price on vendor level is possible if existing supply relationships are copied to a new vendor or to a new article, or if existing supply relationships are reassigned to another vendor. In this case, there is a source purchasing info record which provides the purchase price for the copy process.

31

© SAP 2008 /

DSD Master Data Workbench: Personal Settings (Contd.)

Copy sales prices

Default value: Yes

Controls whether sales prices will be copied or not if either existing supply relationships (that is, source list records) are copied to new supply relationships, or if existing supply relationships are reassigned to another store.

Only sales prices on store level will be copied. If the source supply relationship does not have a sales price on store level no data can be copied.

Create missing listing conditions for local assortments

Default value: No

Controls whether listing conditions for local assortments shall be created if there are new supply relationships for a given store and article.

The listing conditions will only be created if there doesn’t exist valid listing conditions for the article-store relationship based on the local assortment or any global assortment related to the store.The new listing conditions based on the local assortment will be created starting with the entered "key date" and ending with 12/31/9999. If there exists an overlap with future listing conditions of local assortments the indicator “Overwrite overlapping future relationships” has to be set to delete future listing conditions. Otherwise anerror message will be displayed.

32

© SAP 2008 /

DSD Master Data Workbench: Maintenance of Supply Relationships

Change/Display Mode

Maintenance of Supply Relationships can be performed with drag & drop

The following relationships stored in the SAP for Retail data model are relevant for the DSD Master Data Workbench:

Vendor/Article relationshipBased on the purchasing info record the article needs to be assigned to all possible vendors which play the role of a vendor. Here the general purchasing parameters can be defined for each vendor. There is no need to create store specific purchasing info records.Vendor/Store/Article relationshipThe supply relationship between a vendor and a store for a given article is stored in the source list. This relationship is time-dependent which supports the maintenance of future reassignments.Store/Article relationshipThe assortment within a store is defined based on the listing conditions. This defines the ability of the store to order or sell a given article (the “authorization”). This relationship is time-dependent to control the order and selling period of the article in the store.

In the "Supply Relationships" area of the workbench all above mentioned relationships are displayed explicitly or the existence of the relationship is displayed via an indicator.

The vendor/store/article relationship (supply relationship) is displayed explicitly in the tree of the "Supply Relationships" area. The nodes are arranged in the tree by vendor, store, article. This ordering cannot be changed. For all objects listed in the "Selected Objects" area all existing (time dependant) supply relationships are reflected in the tree structure. The existence of the vendor/article relationship (purchasing info record) is indicated by a green rectangle (if not existent with an yellow triangle) in the “Purchasing Info Record” column for each vendor/article combination. The existence of store specific info records is neither checked nor relevant.The existence of store/article relationship (listing condition) is indicated by a green rectangle (if not existent with an yellow triangle) in the “Listing Condition” column for each store/article combination.

33

© SAP 2008 /

DSD Master Data Workbench: Creation of Supply Relationships With Drag & Drop

1

43

2

New vendor – store – article relationships can be created in different ways:Drag objects from the "Selected Objects" area and drop them in the "Supply Relationships" area.Reassign objects with drag and drop functionality in the "Supply Relationships" area.Use context menu “Copy to…” functionality.

Drag objects from the "Selected Objects" area to the "Supply Relationships" areaSelect the object(s) you want to drop to the “Supply Relationships” area by pressing left mouse button in the highlighted area in the “selected Objects” area and drop the object(s) into the “Supply Relationships” area. A vendor can only be dropped at the tree node “Supply Relationships”. A store node can be dropped either on a single vendor node or on the node “Supply Relationships”. In this case the store is assigned to all vendors in the tree. An article can be dropped on a store node, on a vendor node (gets assigned to all stores assigned to this vendor) or on the “Supply Relationships” node (gets assigned to all stores under the available vendors).

Note: When dropping several objects and some of them cannot be assigned a message indicating the reason is displayed in the “Application Log” area, but all other assignments are done.

Note: Instead of drag & drop the button “Copy” in the “Selected objects” area toolbar and button “paste” in the “Supply Relationships” area can be used. This is useful if several pastings should be done.

34

The screenshot shows the DSD Master Data Workbench in “Change mode” after some drag & drop operations have been done. The red rectangle shows a newly inserted relationship, which has not been saved so far, which is indicated by a plus sign in the pictogram.

In a first step the 4 vendors were dropped to the “Supply Relationships” node in the "Supply Relationships" area. An error message is issued for 2 vendors because they already exist in the tree. The third info message informs about the number of vendors added to the tree (1).

In the next step store DS02 was dropped on the vendor node PEDDLER. The application log indicates the number of stores inserted (2).

Then article LEMONDAE01 was dropped on the “Supply Relationships” node and should therefore be assigned to all existing stores in the tree. But for store DS01 beneath vendor HAWKER the supply relationship already exits (HAWKER – DS01 –LEMONADE01). This is indicated by an error message (3). Another error message indicates that a relation exists starting on 12.10.2008 which overlaps with the new one. This message is triggered by the fact that when trying to assign the article to store DS01 beneath vendor MERCHANT the existing assignment HAWKER - DS01 –LEMONADE01 is found. A single article may only be delivered by one vendor for a certain store.

The only possible assignment is PEDDLER – DS02 – LEMONADE01 and the info message indicates that one record was added to the "Purchasing Info Record" area. The warning message indicates that this purchasing info record has to be created (also shown by the yellow flag in the "Supply Relationships" area) that means the missing but not optional fields must be maintained by the user before the workbench can save the new supply relationship (4). Another info message indicates that a new supply relationship was inserted.

As there is no assignment of stores to vendor TRADER, this relation will be deleted from the "Supply Relationships" area during save.

Note: A store can be delivered with an article from only one vendor at a certain time.

35

© SAP 2008 /

DSD Master Data Workbench: Creation of Supply Relationships by Reassignment


Reassign objects with drag and drop functionality in the "Supply Relationships" areaThe left upper screenshot shows the initial state of the "Supply Relationships" area. The store DS01 beneath vendor PEDDLER was dropped on vendor HAWKER, to do a reassignment. As the store was already assigned to vendor HAWKER only the articles assigned to DS01 are reassigned. One info message indicates that 1 supply relationship was inserted and 1 is terminated. One info message indicates that the existing purchasing info record for the new supply relationship has been inserted in to the “Purchasing Info Record” area for display. You can reassign stores and articles by

drop articles on a store or vendor node.drop stores on a store or vendor node. drop vendor nodes on another vendor node.

Note: The flag ‘Copy purchase prices’ in personal settings defines if the purchase price should be copied from the source to the destination relationship or whether no price is created (price needs to be maintained afterwards manually).Note: Instead of drag & drop the button “Copy” in the “Selected objects” area toolbar and button “paste” in the “Supply Relationships” area can be used. This is useful if several pastings should be done.

36

© SAP 2008 /

DSD Master Data Workbench: Creation of Supply Relationships by Copy to … (1)

Supply Relationships

Selected Objects

3

4

5

1

2


Context menu ‘Copy to…’ functionalityThis functionality allows to create copies of articles and copies of stores along with their assigned articles. When using the ‘Copy to…’ functionality for a store new assignments are created for the target stores in all paths of the source stores. When using the ‘Copy to…’ functionality for an article new assignments are created for the target articles in all paths of the source article.‘Copy to…’ functionality for storesThese screenshots illustrate the process of ‘Copy to…’ functionality for two stores. In the “Selected Objects” area we have stores DS01, DS02 and DS03 (1). Supply relationships only exist for store DS01. DS01 is provided with articles from vendor HAWKER and PEDDLER (2). In the "Supply Relationships" area store DS01 is marked in both paths (2). The context menu function ‘Copty to…’ is selected and a “Copy Dialog” popup is raised (4). All stores from the “Selected Objects” area without the source store are available for selection (4). In this case all stores have been selected. The result is shown in (5).Note: Depending on the personal settings ‘Copy purchase prices’ and ‘Copy sales prices’ the pricing data of the source assignments are copied to the new assignments. This is purchasing info record price, purchase price on store level and sales price on store level.

37

© SAP 2008 /

DSD Master Data Workbench: Creation of Supply Relationships by Copy to … (2)

4

Selected Objects

Supply Relationships

5

32

1

New vendor – store – article relationships can be created in different ways:

Drag objects from the "Selected Objects" area and drop them in the "Supply Relationships" area.

Reassign objects with drag and drop functionality in the "Supply Relationships" area.

Use context menu “Copy to…” functionality.

‘Copy to…’ functionality for article

This picture illustrates the process of ‘Copy to…’ functionality for an article. There are 4 articles in the “Selected Objects” area (1). Supply relationships for article APPLE-PIE01 exist for vendor MERCHANT and stores DS01, DS02 and DS03 (2). In the "Supply Relationships" area article APPLE-PIE01 is marked in all paths for vendor MERCHANT. This is done by context menu function ‘Select these materials for vendors…’. The context menu function ‘Copy to…’ is selected and an additional popup is raised (4). All articles from the “Selected Objects” area but the source article are available for selection (4). In this case article CHEESECAKE01 has been selected. The result is shown in (5).

38

© SAP 2008 /

DSD Master Data Workbench: Saving of Supply Relationships

1

3

2

4

Saving of newly created supply relationships and depending dataThe newly created relationship MERCHANT – DS01 – LADY-FASHION01 has a yellow indicator for ‘Purchasing info record’ in the "Supply Relationships" area (1). The application log contains the corresponding warning message ‘1 purchasing info records have to be created’ (2) and in the “Purchasing Info Record” area the new purchasing info record is shown (3). The system tries to fill as many fields as possible with proposal values for the new purchasing info record. There is a check button in the “Purchasing Info Record’ area in order to check the screen values (4). Missing data needs to be entered manually.

Depending on the personal settings and the procedure that was used to created the new relationship additional data will be created during save (purchase prices, sales price on store level, listing condition, logistic data). Missing logistic data on article-store level will lead to the fact, that a supply relationship cannot be saved, depending on the personal settings. In detail:

If the personal setting ‘Copy purchase prices’ was flagged and the new supply relationship was created as a copy of another supply relationship or via reassign.

If there is no purchasing info record existing for the vendor/article combination of the new supply relationship, the purchasing info record price will be copied from the purchasing info record of the source vendor/article combination and presented as a proposal value in the ‘Purchasing Info Record’ area.

39

If there exists a purchase price on store level, this price will be copied to the new supply relationship independent of the fact if there already exists a purchase price on store level or not. The copied price will be valid from ‘Key date’ until 12/31/9999. Prices starting before ‘key date’ will be terminated with a ‘valid-to’ value of ‘Key date’ -1. All future prices will be deleted.

If the personal setting ‘Copy sales prices’ was flagged and the new supply relationship was created as a copy of another supply relationship or via reassign.

If there exists a sales price on store level, this price will be copied to the new supply relationship independent of the fact if there already exists a sales price on store level or not. The copied price will be valid from ‘Key date’ until 12/31/9999. Prices starting before ‘key date’ will be terminated with a ‘valid-to’ value of ‘Key date’ -1. All future prices will be deleted.

If the personal setting ‘Overwrite overlapping future relationships’

was flagged, future source list records for the new supply relationships will be deleted.

was not flagged and there are future listing conditions that need to be overwritten because the flag ‘Create missing listing conditions for local assortments’ is set the new assignment cannot be created.

was not flagged and future source list records for the new supply relationships exists an error message will be displayed and the new supply relationship cannot be created.

If the personal setting ‘Create missing listing conditions for local assortments’

was flagged, listing conditions will only be created if there doesn’t exist valid listing conditions for the article-store relationship based on the local assortment or any global assortment related to the store. The new listing conditions based on the local assortment will be created starting with the entered ‘Key date’ and ending with 12/31/9999.

was flagged and future listing conditions for the local assortment have to be deleted in order to create the new listing conditions, the personal setting ‘Overwrite overlapping future relationships’ has to be flagged, otherwise an error message will be displayed and the assignment cannot be created.

Note: If the listing condition is missing indicated by the yellow triangle and the personal setting ‘Create missing listing conditions for local assortments’ is not flagged the saving of the new supply relationship could lead to an error message because the logistic data of this article – store – combination is missing. Create the logistic data via maintenance or set flag ‘Create missing listing conditions for local assortments’which creates the logistic data as part of the listing creation.

40

© SAP 2008 /

DSD Master Data Workbench: Termination of Supply Relationships

Terminate/deleteUndo

In order to terminate supply relationships mark the articles and use either the ‘Terminate/delete’ functionality in the context menu or the ‘Terminate/delete’ button from the toolbar. Also store or vendor nodes can be selected if all articles under a store or all articles under a vendor should be terminated.

The following changes are made during save:

The current source list entries will be terminated (valid-to = ‘Key date’ – 1). Future source list entries will be deleted.

Current purchase prices on store level will be terminated (valid-to = ‘Key date’ – 1). Future purchase prices on store level will be deleted.

Purchasing info records will not be deleted.

Sales prices on store level will not be deleted.

Note: Next to the ‘Terminate/delete’ button is the ‘Undo’ button. As long as no data have been saved this can be used to undo the changes step by step.

42

© SAP 2008 /

DSD Master Data Workbench: Pricing Data -Overview

Combined Info Record/ pricing conditions maintenance area

Depending on the situation the application chooses automatically which maintenance area is display. Manual switch is also possible.

The DSD Master Data Workbench allows price maintenance in the following extent:

Purchase price maintenance on store/article level, which is maintenance of store specific purchase price, is provided in the ‘Pricing Data’ area.

Sales price maintenanceon store/article level, which is maintenance of store specific sales price, is provided in the ‘Pricing Data’ area.

Promotion prices can only be displayed. Promotion prices on store level will be shown by default in the “Pricing Data” area. Promotion prices on other data retention levels will be displayed when switching to detailed view with the ‘Show/hide Details’ button.Sales and purchase prices on other data retention levels (distribution channel, price list level and vendor level) can be displayed when switching to detailed view with the ‘Show/hide Details’ button.Notes:Concerning the purchase conditions only the gross purchase price (PB00 or a customer specific derivation) will be supported, additional conditions or discounts are not covered.Concerning the sales conditions only the gross sales price (VKP0 or a customer specific derivation) will be supported, additional conditions or discounts are not covered.The sales conditions are independent from the vendor but as each article can have only one vendor in a given store the sales price relationship is unique for a single store-article relationship.Concerning the promotion conditions only the promotion price (VKA0 or a customer specific derivation) will be supported, additional conditions or discounts are not covered.

43

© SAP 2008 /

DSD Master Data Workbench: Display of Purchasing Info Records

12

3

Purchasing info records can be displayed for the marked supply relationship objects of the “Supply Relationship” area when pressing the ‘Price maintenance’ button (1) and pressing ‘Switch To Purchasing Info Record Data’ (2).

More details for purchasing info records can de displayed with the ‘Show/hide Details’button (3).

44

© SAP 2008 /

DSD Master Data Workbench: Creation of Purchasing Info Records

For new assignments purchasing info records must be created if they are not yet available. The column ‘Purchasing Info Record’ in the "Supply Relationships" area indicates which ones are missing by a yellow triangle. All missing purchasing info records are displayed in the ‘Purchasing Info Record’ area. The following fields are maintainable for new purchasing info records.Field | input required |===================================================Order Unit | X |Vendor Material number | - |Vendor Material Group | - |Purchasing Group | X |Planned Delivery Time | - |Tax Code | - |Min. Rem. Shelf Life | - |Currency | X |Pricing Date Control | - |Net Price | X |Order Price Unit | X |Price Unit | X |The system searches for proposals in existing vendor and article master data.These proposals can be overwritten. After the purchasing info records have been saved no further maintenance of purchasing info records is possible in the DSD Master Data Workbench. Only display functionality is available.The input can be checked with the button ‘Check’ before saving.Note: It is not possible to switch to pricing data unless the new purchasing info records have been saved.

45

© SAP 2008 /

2

1

7

4

5

6

3

DSD Master Data Workbench: Display of Pricing Information

8

Display pricing data in the "Pricing" areaPricing data can be viewed for selected assignments of the "Supply Relationships" area. In this screenshot 3 assignments (MERCHANT – DS06 – BEER0, MERCHANT – DS07 – COKE01, PEDDLER – DS11 – JUICE01) have been marked and in order to display the pricing data in the "Pricing" area of the DSD Master Data Workbench the ‘Price maintenance’ button (1) in the toolbar has been pressed. Choosing the context menu function ‘Price maintenance’ (2) or double clicking on an assignment also shows the pricing data in the "Pricing" area. Selecting a higher node in the tree brings all assignments beneath this tree into the "Pricing" area. Purchase, sales and promotion prices along with their currency and valid-to date are displayed based on data retention level store in the “Pricing” area.

Toolbar functions in the "Pricing" areaTo remove pricing information from the "Pricing" area use the ‘Remove Record(s)’button (3). If no rows are selected all pricing data records are removed from the "Pricing" area.

The master data details can be displayed (4) for a selected row. All underlined fields in the grid will launch the appropriate master data display transaction when clicking this field.

46

Display Vendor Master Data (Transaction XK03)

Display Material Master Data (Transaction MM43)

Display Store Master Data (Transaction WB03)

Display Source List (Transaction ME03)

Display Purchase Price Conditions (Transaction MEK3 )

Display Sales Price Conditions (Transaction VK13 )

Display Promotion Price Conditions (Transaction VK13 )

Display Purchase Price Overview (Transaction MEKA)

Display Sales Price Overview (Transaction VKP2)

The prices of components can be displayed (5) for a selected row. This function is only available for articles with article category ‘Generic article’ and ‘Display’.

Predefined display variants of the view can be selected (6).

View by Vendor/Store/Material

View by Vendor/Material/Store

View by Material/Store/Vendor

View by Material/Vendor/Store

View by Store/Vendor/Material

View by Store/Material/Vendor

More details can be displayed (7)

■Concerning master data objects the following addition information will be displayed in the details view

Name/description for vendor, store and article are displayed

Article category

■Concerning pricing data the following addition information will be displayed in the details view

Sales organization, Distribution Channel and Price List

Purchase price per vendor with its currency and valid-to date

Sales price along with its currency and valid-to date for the following level of data retention: Distribution Chain, Pricelist

Promotion price along with its currency and valid-to date for the following level of data retention: Distribution Chain, Pricelist

With the Export data functionality (8) pricing data can be exported to an csv-file in order to be able to maintain the prices in an excel offline and import them later again.

47

© SAP 2008 /

DSD Master Data Workbench: Maintenance of Pricing Information

2 3

1

4 5 6

7

Price maintenance for store specific purchase and sales prices is available when being in change mode (1). The purchase prices (2) and sales prices (3) on store level are maintainable in the "Pricing" area. If there already exists a store specific purchase or sales price it will be displayed along with its corresponding currency and valid-to date.

There are several possibilities to change the price:

Enter/change the price for a certain assignment direct in the pricing field in columns ‘PP Store’ (2) and ‘SP Store’(3).

Select a row(s) and column(s) and use the functionality of the ‘Price Mass Maintenance’ button (4)

Increase/decrease by percentage

Increase/decrease by absolute amount

Copy to same Stores/Materials

Copy values of one row with ‘Copy Row to Clipboard’ (5) and insert the values with ‘Paste Clipboard to rows’ (6) on all selected rows.

To hide the “Selected Objects” area and "Supply Relationships" area when maintaining prices press ‘Show/Hide tree’ (7).

The application log shows information about the actions taken so far.

48

© SAP 2008 /

DSD Master Data Workbench: Maintenance of Pricing Information With ‘Copy and Paste’

The screenshots show how to copy the prices from assignment MERCHANT – DS06 –BEER01 to the assignments MERCHANT – DS07 – BEER01 and PEDDLER – DS11 –BEER01 with copy/paste to/from clipboard:

1. Mark assignment MERCHANT – DS06 – BEER01 and press ‘Copy row to Clipboard.

2. Mark assignment MERCHANT – DS07 – BEER01 press <CTRL> and mark assignment PEDDLER – DS11 – BEER01.

3. Mark the column(s) which should be copied, in this case only PP Store should be copied, by pressing <CTRL> and the columns header ‘PP Store’.

4. Then press ‘Paste Clipboard to Rows’ button in the toolbar.

The purchase price on store level was copied from MERCHANT – DS06 – BEER01 to the assignments MERCHANT – DS07 – BEER01 and PEDDLER – DS11 – BEER01.

49

© SAP 2008 /

DSD Master Data Workbench: Maintenance of Pricing Information With ‘Copy to Same …’

Copy to same Materials

On the previous slide we copied data to the same article in all stores. This can be done easier with one of the ‘Price Mass Maintenance’ functions:

1. Select the row and the column(s) to be copied: MERCHANT – DS06 – BEER01 and column ‘PP Store’

2. Choose ‘Copy to same Materials’ from the ‘Price Mass Maintenance’ selection menu.

Hint: Selecting multiple columns can be done by holding the <CTRL> key on the keyboard while marking rows and columns with the mouse. In order to copy the sales price per store as well, press <CTRL> and mark ‘SP Store’ with the mouse before choosing ‘Copy to same Materials’. Only one row can be selected as source for copy when using ‘Copy to same Material/Store’ functionality.

50

© SAP 2008 /

DSD Master Data Workbench: Maintenance of Pricing Information With ‘Increase/Decrease’

Increase/decrease by Percentage/absolute Amount

1. Select the row(s) and the column(s) to be changed.

2. Choose ‘Increase by Percentage’ from the ‘Price Mass Maintenance’ selection menu. Enter the value for percentage.

All selected prices have been increased by 10 %.

Hint: Selecting multiple rows and columns can be done by holding the <CTRL> key on the keyboard while marking rows and columns with the mouse.

51

© SAP 2008 /

DSD Master Data Workbench: Offline Maintenance of Pricing Information

Work offline with pricing data

The pricing data can be exported to a csv-file, modified offline, and the modified csv-file can be imported again. The export will always export all rows of the data in the “Pricing”area.

The import can also be used to create new assignments:

1.Create new lines with unique key combinations ‘Vendor’, ‘Plant’, ‘Material’ and maintain the columns ‘Purchase Price Store‘ and / or ‘Sales Price Store‘.

2.Import the csv-file and the new assignments appear in the „Supply Relationship“area.

3.If purchasing info records need to be created, maintain them and save.

4.Save your data in order to create the new assignments. The former imported pricing data for new assignments disappears.

5.Import the csv-file again in order to import the pricing data for the assignments created in step 4.

6.Save your data.

Note: The csv-file must contain at least the fields ‘Vendor’, ‘Plant’, ‘Material’, ‘Purchase Price Store‘ and ‘Sales Price Store‘.

52

© SAP 2008 /

This unit covered how the DSD Master Data Workbench will make life easier for category managers.

The practice allows you to Name the SAP for Retail master data objects involved in the DSD Master Data WorkbenchName the relationships between the master data object used by the DSD Master Data WorkbenchDisplay and maintain relationships and pricing data in the DSD Master Data Workbench

Lesson Summary

Thank you for attending this learning unit.

53

© SAP 2008 /

Copyright 2008 SAP AGAll rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

Sap retail master data workbench for direct store delivery

Documents

Transcript of Sap retail master data workbench for direct store delivery