R/3 System
Release 4.6C
Author:
Uta Zielke
26.06.2002
IRT100 Retail Process
Overview
Instructor Guide
Level 2
Key to icons in the Instructor Guide:
Timing
Next Slide (s)
Instructor
Demonstration
Exercises
Activity
Summary
Objectives
Business Scenario
Hints and Tips
Warning or Caution
Internal Note
Note: Please check from time to time for changes to the Instructor Guide or important
notes regarding IRT100 in SAPNet, alias ibsci under Groups
Knowledge
SAP Contacts...4
Walldorf... 4
Course Details...4
Duration... 4
Course Materials and Other Materials...4
Country-Specific Units... 4
Course Instructor Profiles...5
Level of Knowledge Required...5
Courses Recommended as Preparation...5
Online Help Recommended as Preparation...5
Hints on Preparing This Course...5
Training System...6
Hotline System Support: +49 6227...6
Data Required... 6
Training ID... 6
User ID and Passwords for Course Participants...6
Preparation ID... 6
Example ABAPs... 6
CATTs... 6
Technical Hints... 7
Preparation for the Course...8
Goals and Objectives...9
Course Structure and Flow...9
Course Schedule...10
Day One... 10 Day Two... 11 Day Three... 12 Day Four... 13 Day Five... 14Important Notes (Regarding the Rest of This Instructor Guide)...15
Information on IRT100...16
Unit 1: Course Overview...18
Unit 2: Navigation...19
Unit 3: Basic Concepts...23
Topic: Organizational Structures...24
Topic: Sites, Customers and Vendors...26
Topic: Merchandise Categories...28
Topic: Articles... 29
Unit: Requirements Planning and Warehouse Deliveries...33
Topic: Requirements Planning and Purchase Orders...34
Topic: Shipping Notification/ Goods Receipts...40
Topic: Invoice verification:...43
Topic: Subsequent Settlement...46
Topic: Perishables Planning...49
Unit: Sales and Delivery to Stores...53
Topic: Process Overview and Replenishment...54
Topic: Merchandise Distribution...58
Topic: SAP Retail Store... 63
Unit: From Planning to Execution...65
Topic: Process Overview... 65
Topic: Goods Issue Processes...70
Unit: Analysis and Promotions...74
Topic: Process Overview... 74
Topic: Promotion Planning...80
Topic: Promotion Subsequent Processing...83
Unit: Warehouse Returns...86
Topic: Store Returns...87
Topic: Returns Allocation Table...90
Unit: Selling To Customers on the Internet...93
Topic: Online Store...94
Topic: Sales Order/Purchase Requisition/Purchase Order...97
Topic: Settlement of a Third-Party Transaction...102
APPENDIX: Accompanying Overheads for Demonstration...104
I) Requirements Planning and Warehouse Deliveries: Planning Run and Invoice Verification Demonstrations... 104
II) Sales and Delivery to Stores: Replenishment and Merchandise Distribution Demonstrations... 106
III) From Planning to Execution: Demonstrations of Planning and Goods Issue Processes ... 107
IV) Analysis and Promotions: Demonstrations of Promotion Planning and Goods Issue Processes... 108
V) Warehouse Returns: Store Returns Demonstration...109
VI) Selling To Customers on The Internet: Sales Order to Billing Document Demonstrations ... 110
SAP Contacts
Walldorf
Uta Zielke, (Barbara Wessela)
Course Details
Duration
5 days
Course Materials and Other Materials
Participant Handbook:
PowerPoint Slides (including notes)
Exercises and Solutions
Appendices (Performance Map, Best Practices)
Country-Specific Units
Course Instructor Profiles
Level of Knowledge Required
1. Knowledge of the main logistical workflows in retail (and wholesale)
2. Knowledge of the contents of the Level 3 courses in the Retail curriculum (for contents: see Training Catalog or SAPNet), especially the differences between course IRT100 and the Level 3 courses.
3. Basic knowledge of the SAP modules Materials Management (MM), Sales and Distribution (SD), and Logistics Execution (LE).
Courses Recommended as Preparation 1. IRT100 Retail Process Overview 2. IRT310 Retail Master Data
3. LO020 External Procurement Processes 4. LO140 Logistics Execution Processes 5. LO150 Sales and Distribution Process
6. LO925 Cross-Application Business Processes in SD and MM
The course contents are described in the curriculum for components MM, SD, and LE (Training Catalog or SAPNet)
Online Help Recommended as Preparation
Read the component descriptions and process descriptions for the SAP Retail Industry Solution; the relevant descriptions for this course are Purchasing, Merchandise Logistics and
Sales.
Hints on Preparing This Course
Instructors who have not taught this course previously should do the following to prepare for the course:
Read this Instructor Guide carefully
Work through the notes and demonstrations for the individual chapters as described in the participant handbook. The instructor guide does not contain notes on all the slides; in most cases, the notes on the slides themselves will be sufficient to explain them.
Work through the individual demonstrations in the system.
Work through the exercises based on the specified activities and solution paths in the system.
If you do not completely understand the process or individual process steps described in a unit, read through the corresponding section in the online documentation for SAP Retail. The course only covers partial aspects of a process or a simple run through a process chain. When you read the documentation, you will learn about other process chains and possible areas of use for the individual functions.
Training System
The Training Management group will allocate a training system to you once the course has been registered.
Hotline System Support: +49 6227
Training Systems: 42887
Demonstration Systems: 47070 Data RequiredOfficial Retail training systems at SAP AG in Walldorf are systems that are copied from the Retail master system, DMR, when required for courses. They contain all the master data (articles, vendors, customers, sites, volume-rebate agreements, and so on) required to hold IRT100. This includes:
Data for the system demonstrations given by the instructor (number 00),
Exercise data for up to 30 participant groups (numbered 01 through 30) Use the CATT listed below to generate the necessary transaction data.
If you want to hold this course in a separate system, we recommend that you import a copy of master client 400 from system DMR into the system in question. In this case, please contact Gary Kilo (Training System Management) in good time.
Training ID
There is a separate instructor user available for all instructors. User ID: TRAINING. The initial password is sent to every instructor once a month (“Password for the month”).
User ID and Passwords for Course Participants
Reference user ID: IRT100
The standard format for user IDs is the course ID plus the group number (##) – so for this course: IRT100-##
The initial password is INIT.
Use transaction ZUSR to create these user IDs as copies of the reference user ID.
Preparation ID
As an instructor, you can prepare for the course in system DPR (server iwdf0109, system number = 00), client 400. User ID: TRAINING; the password is the “Password for the month” that is sent to the instructor.
Example ABAPs
None
CATTs
For each IRT100 course in the system, you have to run CATT ZT_IRT100 in the assigned training client at the beginning of each week in which the course will be held.
This CATT runs the following two CATTs:
ZT_IRT120_01 (transaction data)
ZT_IRT120_02 (sales)
The lead instructor of the course is responsible for running the CATTs.
However, if the course will be held in a system assigned by Training Management and has been officially registered, System Management in Walldorf will start the CATT in good time
before the start of the course.
Should you encounter any problems, please contact Georg Kirst (Training System
Management on 06227 760568). In order to prepare for a course or should other exceptional circumstances arise, you can also send a mail to the DL ITC-CATTS team if you need the CATT to be started even earlier.
Before you start the CATT ZT_IRT100 yourself, please check that you have not selected any views when entering the article master (transactions MM41, MM42 or MM43).
Only the Logistics: Distribution Center view may be selected, if really necessary.
Technical Hints
Preparation for the Course
Perform the following tasks in the assigned training client of the system before the course starts:
1. Start the period closing program (TA MMPV), if necessary 2. Create users as copies of the reference user IRT100 (TA ZUSR) 3. If necessary, run CATT ZT_IRT100 (TA SCAT)
4. Save your favorites:
Retail Store: http://igttr.wdf.sap-ag.de:1080/sap/its/homepages/sapstore.htm Online Store: http://wdf.sap-ag.de:1080/sap/its/homepages
5. Enter SLS indicators: (TA MM42)
Articles R100000 and R100008, Basic data – Additional data – Additionals – R100043, method SLS
6. Generate an assortment list (TA WDBI) for: Sales organization R300
Distribution channel R5 Customer no. R300 Assortment list type R
then display the assortment list (TA WBBS) and note down the validity period 7. Create purchase orders for "Requirements Planning for Perishables" (TA
ME21N)
a) Stock transfer order UB, Supplying site R300 to Site R310 with a Delivery date within the validity period you noted above
Possible articles: R100008, R100007 and R100031 Purchasing organization R300
Purchasing group R30 Company code R300
additional purchase orders to sites R311 to R316 are also possible
b) Standard PO NB, Vendor R3000 to Site R300 with a Delivery date within the validity period noted above
Possible articles: R100008, R100007 and R100031 Purchasing organization R300
Purchasing group R30 Company code R300
Additional purchases orders from vendors R3001 and R3002 to DC R300 are also possible
8. Convert the SAP Online Store for Courses in English
You now have to convert the SAP Online Store to the English version:
IMG: Logistics – General IACs Product Catalog and Online Store
Online Stores
Goals and Objectives
The goal of this course is to teach the participants important business processes in retail and their implementation in the SAP Retail system.
The participants can work through various goods procurement and distribution processes in the system. They learn the basic functions of SAP Retail, such as requirements planning, purchasing, and shipping, along with the necessary master data configuration.
Course Structure and Flow
Course IRT100 consists of the following units:
Course Overview
Navigation
Basic Concepts
Requirements Planning and Warehouse Deliveries
Sales and Delivery to Stores
From Planning to Execution
Analysis and Promotions
Warehouse Returns
Selling To Customers On The Internet
Summary
The Course Overview is an introduction to the course. It introduces the course objectives and provides an overview of the course contents.
The Summary repeats these and also provides information on other SAP courses. The Navigation and Project Implementation with ASAP units are standard units that are contained in all level 2 courses. As a result, they are not dealt with in detail in this instructor guide.
Basic Concepts deals with the most important organizational structures and master data for
SAP Retail. It makes sure that all the course participants have the same understanding of the SAP Retail terminology.
The remaining chapters make up the actual contents of the course. They all have a very similar structure. The slide entitled Overview Diagram shows the processes that are dealt with in the respective chapter, including the parties involved in these processes and the flow of merchandise. The business scenario is then described in words. This is followed by a detailed, step-by-step examination of the same process (Process Overview slide).
Any differences between these process steps and other retail processes are shown in an extra Process Overview slide and are then explained.
Course Schedule
Day One
Approximate Duration
Content: Units and Topics
See the details under the relevant chapters for the activities for the instructor and participants.)
30 min Welcome
Information regarding the course schedule (start/end times each day), along with general organization of the course and the Training Center (how to get there, parking, lunch, phones/cell phones, and so on)
Introduction of the Instructor and Participants
Course Overview
10 min General introduction to the course
Retail curriculum and course concept
Course structure and business scenario
Explanation of appendixes
Navigation
30 min Navigation unit (with demonstration)
20 min Navigating in SAP Retail exercises (from the Basic Concepts unit)
Unit 3 Basic concepts
20 min Topics: Organizational structures, Sites, Customers, Vendors 20 min Site master demonstration
20 min Site master exercise
60 min Lunch break
10 min Topic: Merchandise categories
10 min Merchandise categories hierarchy demonstration
40 min Topic: Article
20 min Article master demonstration
30 min Article master in SAP Retail exercises
Unit 4 Requirements Planning and Warehouse Deliveries
10 min Process overview Requirements Planning and Warehouse Deliveries and topic Supply
and Demand
30 min Topic: Requirements planning
10 min Possibly the first part of the Requirements planning run demonstration Additional notes:
Day Two
Approximate times
Contents: Units and topics
30 min Repetition of topics and answering any questions from the previous day 45 min Topic: Purchase order
30 min Demonstration of planning and ordering (divided up if you wish) 40 min Planning and ordering exercises (divided up if you wish)
60 min Lunch break
30 min Topic: Shipping notification and goods receipt (may be divided up)
30 min Shipping notification and goods receipt demonstration (may be divided up)
30 min Shipping notification and goods receipt exercises (may be divided up)
10 min Topic: Logistics Invoice Verification
20 min Logistics Invoice Verification demonstration
30 min Logistics Invoice Verification exercises
10 min Topic: Subsequent settlement
20 min Subsequent settlement demonstration
20 min Subsequent settlement exercises
5 min Topic: Requirements planning/particular procedures 10 min Topic: Investment buying
10 min Topic: Perishables planning 10 min Perishables planning demonstration
5 min Topic: Online Planning
5 min Online Planning demonstration
Additional notes:
Day Three
Approximate times
Contents: Units and topics
30 min Repetition of topics and answering any questions from the previous day
Unit 5 Purchasing and delivery to stores
45 min Process overview Sales and Delivery to Stores and topic: Replenishment 35 min Replenishment and creating target stock demonstrations
40 min Replenishment exercises
30 min Topic: Merchandise distribution
30 min Merchandise distribution demonstration
60 min Lunch break
40 min Merchandise distribution exercises
15 min Topic: SAP Retail Store
15 min SAP Retail Store demonstration
20 min Store goods receipt exercises (with SAP Retail Store)
Unit 6 From Planning to Execution
40 min Process overview From Planning to Execution and topic MAP 20 min Planning in MAP demonstration
30 min Planning in MAP exercises
Additional notes:
Day Four
Approximate times
Contents: Units and topics
30 min Repetition of topics and answering any questions from the previous day 25 min Topic: Allocation table
15 min Allocation table exercises
20 min Topic: Goods issue
20 min Goods issue demonstration
30 min Goods issue exercises
60 min Lunch break
Analysis and Promotions
40 min Process overview Analysis and Promotions and topic Business Information Warehouse 30 min Demonstration in the BW
20 min Topic: Promotions
20 min Promotion planning demonstration 20 min Promotion planning exercises
20 min Topic: Subsequent processing for promotions and allocation table 30 min Subsequent processing for promotions exercises
10 min Topic: Article discontinuation 10 min Topic: Archiving
Additional notes:
Day Five
Approximate times
Contents: Units and topics
30 min Repetition of topics and answering any questions from the previous day
Unit 8 Warehouse Returns
15 min Process Warehouse returns, topic Store returns 15 min Store returns demonstration
20 min Store returns exercises
10 min Topic: Returns allocation table
10 min Returns allocation table demonstration
20 min Returns allocation table exercises
Unit 9 Selling To Customers On The Internet
30 min Process overview Selling to customers on the Internet and topic Online Store as demonstration
60 min Lunch break
20 min Online Store exercises
10 min Product catalog demonstration
20 min Topic: Sales orders and purchase orders
20 min Demonstration of promotion order and purchase order (divided up if you wish) 20 min Promotion order, Purchase order exercises
10 min Topic: Third-party business
20 min Invoice Verification, Billing demonstration
20 min Invoice verification, Billing exercises
10 min Conclusion and goodbye Additional notes:
Important Notes (Regarding the Rest of This Instructor Guide)
1
In the following detailed descriptions of the individual units and topics only those specific slides for which information, hints, or suggestions are provided in addition to the information already in the slide notes are mentioned explicitly in this Instructor Guide.
For all other slides (just as for the slides cited explicitly): The instructor conveys the information described in the notes.
2
All system demonstrations list the appropriate transactions, paths and instructions. You can also use the solutions to the exercises for the corresponding units/topics for more information.
3
The menu paths in the system demonstrations always start with
SAP menu Logistics Retail
4
The demonstrations often involve creating or changing data. Most of the time, you will demonstrate parts of the exercises for the course participants. To do this, use the data from an available group number – for example, ## = 00, 20 to 30.
Because some exercises are based on data from previous exercises, you should use the same group number for demonstrating all the exercises.
5
Coffee breaks are not scheduled explicitly because they highly depend on your judgement of how the course is going and how well the participants are absorbing the information.
It is up to you to decide when you and your students need a break.
6
If the Training Management group at SAP AG in Walldorf manages this course in the ISP system, please have the participants fill out an Online Course Evaluation in SAPNet. Inform the participants of this on the morning of the last day of the course and show them how to use the Online Course Evaluation tool.
If you have any questions about the Online Course Evaluation, contact Bernd Jungbauer (745752) and for technical questions contact Kai Kübler (766243).
Information on IRT100
10 min
mySAP Retail
Briefly explain the structure of the mySAP Retail curriculum. Be sure to mention the following:
There are two level 2 courses, SAP 20/SAP01 and IRT100, which deal with the core processes of a retail company. This course is a prerequisite for all level 3 courses.
All level 3 courses cover specific functions in mySAP Retail, and deal with both the functionality and control (Customizing) of these functions.
For your information, here is the description of the mySAP SCM curriculum from the Training Catalog:
The level 2 course IRT100 Retail Process Overview covers the core processes of a retail company. Starting from in-store sales, the course shows how the store and the distribution center are replenished with merchandise. The course explains the special features involved in the promotion and returns processes, as well as handling orders over the Internet.
Course IRT310 SAP Retail Master Data covers the specific master data used in SAP Retail. This course is a prerequisite for all other level 3 courses.
Course IRT320 SAP Retail Pricing and Promotions explains how to maintain and configure prices and promotions in SAP Retail.
Course IRT300 SAP Retail Buying deals with merchandise procurement and the associated parameters.
Course IRT340 Retail Supply Chain Management explains the settings and options available for configuring supply chain management processes for a distribution center.
Course IRT350 SAP Retail BW / MAP teaches about the components for merchandise and assortment planning, as well as how they interact.
Course IRT360 SAP Retail Store Connection deals with the processes for supplying stores with data and for processing the data that the stores send back to the central Retail system.
Course IRT370 SAP Retail Store teaches how to configure and use the SAP Retail Store.
Level 3 courses from the areas MM and SD are also recommend for reinforcement. Please point out that these courses do not deal with industry-specific topics.
Supplementary courses from the mySAP CRM Curriculum
The courses listed here are mainly application oriented but they also contain parts on Customizing. The courses are heavily dependent on the release; substantial changes in the architecture take place between Releases 2.0c and 3.0. For administration, there are the technical Basis courses (CR310, CR5XX).
Supplementary courses from the mySAP BW Curriculum
The BW courses shown here are divided up as follows:
BW200 is an overview course. The fundamentals (level 2) of the BW are covered in BW205 and BW210. Course BW205 is intended for power users, the user
department and technicians, as it deals mainly with the reporting level. BW210 is intended for BW administrators and technicians as it introduces and explains the data models.
Unit 1: Course Overview
10 min Contents of Unit Course Goals Course Objectives Contents Overview Diagram Main Business ScenarioPutting the Unit in Context
This unit represents the introduction to the course.
It provides an initial overview of the course structure, explains the basic concept of the course and how it fits into the overall SAP Retail curriculum.
Overview Diagram
Use this slide to explain the course structure (also see slide entitled Contents). This slide shows the individual processes of the course together with the partners involved (vendors, sites, and customers) and the corresponding merchandise flows (orange arrows).
The slide is added to throughout the presentation and shows the processes in the order in which they are handled during the course. The Basic Concepts frame refers to the first course-specific unit and appears at the end of the sequence.
This slide is the tie that binds the entire course. It appears in each unit with the appropriate frame highlighted.
Main Business Scenario
Make sure you stress: As of Release 4.5B our business scenario (sites, vendors, customers) is based in the USA. Therefore, if you are using a non-English language system, it is possible that English texts will appear in some documents and
messages.
Unit 2: Navigation
50 min
Contents of Unit
User Guide
User-Specific Settings Navigation in the Workplace
Putting the Unit in Context
Show the different ways of navigating in an R/3 System
Name the configuration options for your personal menu and your default data This is a standard unit for level 2 courses.
The slides are designed to be used as a reference for the participants after the course; the instructor should show the contents directly in the system.
You will not be able show anything about the Workplace as the workplace is not set up in the training system.
Demonstration: Navigating in mySAP Retail
30 min
1. Log on to the system: Client: 400 User: IRT100-## Password: INIT Language: EN
You may want to demonstrate multiple logons; these are logged as of Release 4.6
2. Explain the screen elements:
Menu bar
Standard toolbar (such as Options) Title bar
Application toolbar Status bar
Command field
You may want to demonstrate entering transaction /nspro to reach Customizing; show the path as an alternative.
Input field / radio buttons / tabs / checkboxes / pushbuttons for example, in
System User profile Own data
3. Explain F1 help and F4 help
for example in the Start menu field on the Defaults tab page:
[F1]
[F4] explanatory text: *Retail*; remove the maximum number of hits
Advise the participants to use these help functions frequently.
4. Configure mySAP Retail as the start menu and maintain the user profile (in:
System User profile Own data)
Tab page Defaults: Field StartMenu: W10T Tab page Parameters:
Use F4 help to search for the company code
(To do this, click on the small button to expand the restrictions, enter company
code as the short text, and press [Enter])
Enter the following in the table (parameters must be in capital letters): CCD R300, PCO R300, PCG R30, SLO R300, DTC R1, DIV R1 User Save
Button [Start SAP Easy Access] 5. Create and delete a new session
by following the path System Create or Delete session and by using the
pushbuttons
6. Display the system status
System Status, briefly explain the most important data
7. SAP Easy Access Menu: Explain structure and create favorites
Show the Structure of the SAP Easy Access menu (new as of Release 4.6) Adding favorites: We recommend selecting an executable node
Favorites Add (to copy the path)
or using Drag&Drop and
Favorites Change (to change the text)
Favorites Insert folder
For example, add a new folder called “Article master maintenance” and insert the transactions “Display article” and “Change article.”
8. Set up favorites for subsequent units Favorites Insert folder
Insert a new folder called “Retail Store” using the transactions
"http://igttr.wdf.sap-ag.de:1080/sap/its/homepages/sapstore.htm"
Favorites Insert folder
Insert a new folder called “Online Store” using the transactions
"http://igttr.wdf.sap-ag.de:1080/sap/its/homepages"
9. Switch history on and off
Local layout Options Local data
The entries are stored and proposed under the relevant input fields 10. F4 help settings
Help Settings F4 Help
If there is only one search result, the cursor automatically returns to the input field.
You can set the maximum number of hits to be displayed here. 11. Display the menu of an activity group
(Note: This option is dependent on the user’s authorization and will not be possible for the participants.)
Menu Display menu of an activity group (or use the [Other menu] button)
Enter restrictions:
Activity group SAP_ISR* [Enter]
For example, select SAP_ISR_LO_MD_ASSORTMENT Expand the menu [Back] to the SAP Easy Access menu 12. Explain the SAP Library
Help SAP Library, SAP Library Logistics SAP Retail
Scroll
Explain the index and search function
Search for a term like “Company code” (set the “Search titles only” flag). 13. Demonstrate the SAP Help Portal
(Internet Explorer) http://help.sap.com (external page, accessible to anyone) 14. You may also want to show the SAP Service Marketplace and Expert Knowledge Corner
as an SAP employee: SAPNet: alias Retail Expert Knowledge Corner
for customers and partners: http://service.sap.com/retail Expert Knowledge Corner.
15. SAP GUI XT
www.guixt.com (external page, anyone can access it). This tool can be used locally by each user. It enables the user to customize the user interface (fields, buttons, default values etc.). The tool is activated using the layout settings in the SAP
System. You do not need to carry out any Customizing in the SAP System itself. It is provided by the company Synactive Components, LLC.
Exercises: Navigating in mySAP Retail
20 min
If you have covered the Navigation unit, you should have the class perform the exercises at this point. The exercises are located in Unit 3: Basic Concepts.
Unit 3: Basic Concepts
170 min
Contents of Unit
Organizational Structures for mySAP Retail Sites
Customers/Vendors Merchandise Categories Articles
Listing/Assortment Lists
Putting the Unit in Context
This unit introduces the basic concepts for the whole course: It explains the most important organizational structures and master data in mySAP Retail. At the same time, important terminology is defined to ensure that all the participants are talking the same language.
Name the main organizational structures in mySAP Retail
Explain the structure and the function of sites
Explain the basic concepts of articles in mySAP Retail
Basic Concepts: Overview
This slide shows the relationship between organizational structures and master data in mySAP Retail:
Distribution centers and stores are the units (sites) that plan and manage stocks and therefore have their own storage locations.
When articles are ordered for a site, a purchasing organization is always
responsible. The purchasing group groups the MRP controllers who carry out this process.
When a sale is made to a customer, this always occurs through a distribution chain. The sales organization is responsible for this transaction.
The article represents the object that is being traded. Different article data can be managed at organizational structure or site level – for example, purchasing data at the purchasing organization level, sales prices at distribution chain or site level.
Topic: Organizational Structures
In the following, the organizational structures are always explained theoretically based on a slide. The next slide usually shows the corresponding relationships at our model company Smart Retailer Inc.
Please point out that the client numbers in the slides were selected at random in the model company examples.
If your participants include experienced consultants for the SAP Standard System, you should also explain that SAP Retail primarily involves Materials Management (MM) and Sales and Distribution (SD) and also creates new connections between these areas that were not previously available. (For example, the link between purchasing and sales through the collective purchase order.)
You should also refer to the multilevel nature of mySAP Retail. Normally, SAP R/3 represents one level of the value chain. In this case, a company has a purchasing organization and a sales organization. In retailing (especially centrally controlled chain retail stores), however, more than one level of the chain is modeled. As a result, we have sales from the warehouse to a retail site (parallel to wholesale customers) as well as sales from the retail site to the consumer. This is reflected in the different distribution chains for these two levels.
There are also two types of distribution chains: wholesale and retail (see also Sites slide: Site Categories and Distribution Chain Categories.)
Franchise partners are always modeled as separate retail sites (logistics) and with a
separate company code (settlement).
IDES Retail (Internet Demonstration and Education System)
Our model company (sites, vendors, customers) is based in the USA. This means that English texts will appear in some documents and messages and the VAT system used in Europe is not taken into consideration. This model company is currently being extended to include a German sector, however, it is not yet complete and therefore cannot be used for training.
Additional slides have been added to the overview slides describing our model company, which illustrate its organizational structures. The list is not exhaustive. It is simply intended to help the customer better understand the organizational structures.
Organizational Structures in Purchasing
The setup of the purchasing area means it is unnecessary to create lots of purchasing organizations (PurOrg).
Purchasing areas do not represent a data retention level and are only evaluated in the RIS (Retail Information System).
The reference purchasing organization can be used as a shared data retention level for multiple purchasing organizations, for example, by having them access the conditions of the reference purchasing organization.
Inventory Management at IDES Smart Retailer Inc.
Please explain that the distribution center in this example has several storage locations because several different processes in the storage area can be/have to be handled. Point out that you are not able to explain at this point why this is the way it is, but that this fact will become clear later in the course.
Organizational Structures in Sales
Point out that the distribution chain in SAP Retail is used in a similar way to the distribution chain in the SD module. Briefly explain that the sales area consists of the sales organization, distribution channel, and division, and that the division is set to a dummy value in SAP Retail. Explain that whenever you go into the
sales/distribution area, you will always be asked for the sales area.
Point out the importance of the distribution chain and emphasize that it can be used in SAP Retail to control sales prices – for example, different sales prices can be valid in a consumer distribution chain than in a wholesale distribution chain.
The assignment between purchasing organization and sales organization is usually determined through the site in which the sale takes place. The RIS (Retail
Information System) is updated through the documents that contain the site.
Internal Note:
You can also assign a purchasing organization to a sales organization in
Customizing. Please note, however, that this assignment is only used in SAP Retail in pricing if you are performing the costing for a distribution chain, and no reference site has been assigned to this distribution chain.
Topic: Sites, Customers and Vendors
Site: Master Data
This slide shows the screen structure of the site master. Point out at this stage that there are differences in the screen structure between the distribution center and the store. This is controlled using the site profile, which you have to enter when you create the site master. You can reconstruct this in the administration data
information button.
Site: Definition and Control
Emphasize at this point that a site can consist of multiple segments. The site category is an attribute of the site profile.
Sites are always created with reference to a site profile.
Site profiles are intended to simplify maintenance, since unneeded fields (etc.) are not displayed at all.
The site profile is also associated with the template site and the account groups and templates for the customer and vendor segments. As a result, a great deal of data is proposed automatically when a new site is created.
No Customizing settings are associated with the site profile.
Distribution chain types Wholesale and Distribution Center are identical as of Release 4.5.
Internal/External Customer/Vendor
This slide should make clear the main differences between a distribution center and a store. The distribution center acts as an internal customer when it is supplied by an external vendor. However, it also takes on the role of an internal vendor when it gives merchandise to the stores belonging to the company. These stores can be seen as internal customers and contrast with the external customers, which can also be supplied by the distribution center. These do not belong to the company.
Demonstration: Site Master in SAP Retail
20 min
1. Enter the site master (TA WB02)
Master data Site data Site Display or Change
Site R314 (Store)
2. General data
Tab page Organization/Calendar, organizational dependence on distribution chain R300/R1,
Button [Distribution chains - site] = the distribution chains used for delivery by the site.
Briefly explain the tab pages Address, Valuation/Inv. mgmnt, and any others if you have time and the individual fields.
3. Merchandise Categories
Button [Merchandise categories], assignment to departments, you may want to use F1 help on column M (merchandise category-based inventory management) to show that you can enter a supplying site for each merchandise category. 4. Departments
Button [Departments]; receiving points can be entered here 5. Receiving points
Button [Receiving points], assignment to unloading points 6. Supplying site
Button [Supplying sites], a distribution center is maintained here 7. Customer segment
Button [Customer], indicates above all sales area data: Distribution chains through which the store can be supplied.
8. Change to a distribution center for the vendor segment ( TA WB02 )
Site Display or Change
Site R300 (DC)
Button [Vendor]
Refer to the purchasing organization data (assignment to PurOrg)
Exercise: Site Master in SAP Retail
Topic: Merchandise Categories
Merchandise Categories
The merchandise category from SAP Retail is also referred to as the base merchandise category.
Point out that the R/3 System can use copy templates at many different places in the system, and that SAP recommends that customers use these templates as often as possible. Therefore, it is important to maintain the template data carefully and thoughtfully.
Merchandise Categories and Hierarchies: Definitions
For characteristic inheritance to be free of conflicts, the merchandise category hierarchy must be a true hierarchy, not a grouping.
Point out the importance of setting the “Used for forming variants” indicator for characteristics that will be used to form collective articles.
Demonstration: Merchandise Category Hierarchy
10 min
1. Enter merchandise category data ( TA WG24 )
Master data Merchandise category data Merchandise Category Display
Merchandise category R1121
Button Merchandise category basic data
Here explain the merchandise category article, the merchandise category reference article and the arrangement of the merchandise categories in the merchandise category hierarchy
[Back],
explain the buttons Merchandise category reference article, Merchandise category
article and Article overview
2. Merchandise category hierarchy display ( TA CL6C )
Master data Merchandise category data Environment
Classification system Display hierarchy
Class R1100
Class type 026
Display Subordinate classes and (if necessary) Graphical display
Topic: Articles
If the time is available, we recommend holding a brainstorming session (using a flip chart or cards) to introduce this topic. Have the participants name the data that they think should belong to the article master. You can group this data according to how it is connected or by validity level (with regard to the views).
Article master data 1/3 to 3/3:
Point out that these are the standard views. They can be configured user-specifically using the configurable article master (see IRT310 for more information).
Also be sure to point out the importance of templates.
Describe the difference between the template site used to create a new site master and the template site for each distribution chain (which is important for the article’s logistics data). At this point, you can also mention the fact that the system can detect alternate article data that has been maintained.
For more information on this topic, see the online documentation under Article:
Templates.
Article: Units of measure
As of Release 4.6, the units of measure can also be defined hierarchically in the article master. For more information, see the online documentation under Article:
Maintaining the Unit of Measure in Accordance with the Packing Hierarchy.
Please note, however, that this activity does not create any stocks for the individual units of measure in SAP Retail. This is done with the concept of logistical variants. For more information, see the online documentation under Article: Logistical
Variant
Article: Data Retention Levels
This slide shows the different levels of the article master and navigation between these levels:
Explain that you can see which data retention level you are on in the header area of the article master.
If you do not enter a site in the views Logistics DC and Logistics Store, the reference site is opened in the background and all its settings apply to all sites. If you want to enter data explicitly for each site, you need to switch to site level by entering a site.
Demonstration of the article master in SAP Retail
20 min
1. Enter the article master ( TA MM42 )
Master data Article data Article Display or Change
Article R100000
Purchasing organization R300
Sales organization R300
Distribution channel R1
Possible: Button [Validity area default settings] Select all views
Possible: Button [Views default settings] 2. Basic Data
Explain units of measure (for example, F1 help on sales unit of measure, different units of measure possible for each distribution chain).
(Note: as of Release 4.6, the alternative unit of measure no longer has to be calculated from the base unit of measure but can also be calculated from another, previously defined alternative unit of measure.
Example: PC = 1 PC / BOX = 20 PC / LAG = 4 BOX / PAL = 5 LAG)
F1 help on EAN (EAN always refers to a specific unit of measure)
Merchandise category
Article type: controls whether internal or external number assignment is
used, the number range intervals, selection of views, and whether inventory management is value-based or quantity-based
and possibly the minimum shelf life, and so on. 3. Listing
Assortment level (1 is entered here) Basic procedure (F4 help)
Listing period Explain sales period Button [Assortment] 4. Purchasing
Validity area Vendor data
Button [Conditions], you may want to briefly show that you can enter article-specific conditions for a vendor by specifying a condition type and an amount 5. Sales
Validity area
Sales price calculation based on the purchase price Possibly explain the button [SP calculation] Explain the Save calculated price flag 6. Logistics DC
Generally explain that the data for requirements planning, forecasting, physical inventory, and storage location is saved here
7. Logistics Store
8. POS
Flags for cash register control, receipt texts
9. Article category and article type during article creation ( TA MM41 )
Article Create
Article type: F4 help, briefly mention several of the control functions (type of number assignment, field selection, valuation, quantity and value update) Article category: F4 help
10. Layout Workbench (optional, TA WLWB )
Master data Assortment/listing Layout Layout Workbench
Customer R314
[Execute] button or [F8]
Button [Expand all]
Press button [0000] under Version to see the article in the layout module (= shelf)
You can branch to an external space management system by choosing Goto
Space maintenance.
Article master in SAP Retail exercises
Listing (1-5)
Point out that when a store or a DC is created, an assortment with the same number is automatically generated in the background. These assortments can only be displayed; they cannot be maintained manually. The relationship between the site and the assortment is always 1:1.
Assortments for wholesale customers are created manually and manually assigned to these customers.
Explain SAP’s recommendation of using the automatic listing (for article maintenance) instead of the manual module formation. In addition to
performance reasons, manual module formation is extremely time-intensive when the assortments are short-lived, because the modules always have to be manually maintained afterwards.
Name the basic listing procedure and explain the merchandise category/assortment level checks using an overhead you draw yourself.
Point out that any combination of basic procedures can be used for a listing procedure, and that a customer exit (user exit) can be used to define additional, customer-specific procedures.
Briefly mention the possibility of listing using the Layout Workbench or external space management programs (see SAP Library for SAP Retail, Layout Workbench and IRT310).
Assortment Lists: Definition
The assortment list is used to inform stores about changes to the assortment (new/obsolete articles, price changes, promotions, for example). Assortment lists can be configured differently for every situation and assortment and they can be prepared in different media.
Unit: Requirements Planning and Warehouse Deliveries
390 min
Contents of Unit
Requests and Quotations Planning Purchase Order Shipping Notification Goods Receipt Invoice Verification Subsequent Settlement
Special Requirements Planning Procedures
Putting the Unit in Context
The distribution center/head office plays the main role in this initial process.
In a distribution center, you want merchandise requirements to be planned and an order to be placed with an external vendor automatically whenever possible. To do this, we will now examine the two most important MRP procedures for retail (reorder point planning and time-phased materials planning) in more detail. The result of requirements planning is a purchase requisition.
In the next step, we will explain the conversion of the purchase requisition into a purchase order, together with the associated optimization options.
The goods receipt is posted when the merchandise is delivered to the warehouse. Possible preliminary steps include advance information by the vendor (such as a shipping notification, for example) and a rough goods receipt.
If the vendor sends an invoice for the delivered merchandise, that invoice is recorded and verified in the system. Differences between the target invoice (purely fictitious invoice created automatically by the system) and the actual invoice (vendor invoice) can be corrected. Subsequent settlement (rebate processing) is explained as an extension of this process.
This unit also covers investment buying, perishables planning and online planning as possible starting points.
Procure merchandise from a vendor for a distribution center in SAP Retail.
Perform the following activities in particular:
Trigger forecast run and planning run; create vendor purchase orders manually; create shipping notifications; post (rough) goods receipts; create and check vendor invoices, settle volume-rebate arrangements with vendors
Topic: Process Overview
Requests and Quotations: Linking
Additional information: Two business scenarios in which the request/quotation functionality could be used are:
Adding a new article to an assortment (to find a reasonably-priced vendor for this new article)
Elimination of the regular vendor of an article, for example, due to poor quality (in this case, a replacement vendor or new regular vendor has to be found)
Topic: Requirements Planning and Purchase Orders
Requirements Planning: Targets
Additional information: In contrast to manufacturing, it is critical that
consumption-based planning is used in retail (as opposed to material requirements planning).
Requirements Planning: Procedure
Additional information: The (overall) planning run should be scheduled as a periodic background job by the R/3 system administrator, taking any other required
predecessor runs (such as the forecast run, for example) into account.
Requirements Planning: Overview
Additional information: The RP type plays a key role in requirements planning. It controls whether a forecast should be generated or not.
Requirements Planning: Methods and Types
Additional information: Different requirements planning methods are useful for retailers. The main ones are time-phased and reorder point planning.
Time-phased materials planning can be combined with reorder point planning. You can specify in the system, for example, that an article is always ordered for a
distribution on Mondays (RP frequency), as well as whenever the stock of that article in the distribution center falls below a defined reorder point.
The benefit of combining these two procedures will become clear after you explain the next two slides.
After slide Requirements Planning: Time-Phased Planning Demonstration of master data involved in requirements planning
10 min
1. Site master ( TA WB03 )
Master data Site data Site Display
[Enter]
Field Requirements planning must be active in tab Listing/MRP 2. Article master ( TA MM43 )
Master data Article data Article Display
Article TA03##
Select views Logistics, Distribution center
[Enter]
Explain the requirements planning parameters, especially fields MRP type, MRP
lot size, Forecasting model, and Period indicator
Show the additional requirements planning and forecast parameters using button
[MRP/forecast data]
Be sure to point out the Past periods and Forecast periods fields.
Press [F3] to go back to the logistics data overview, and show the RP frequency (= ordering day) and delivery frequency (= delivery day) there.
If necessary, display the logistics data of your distribution center T7## (button
[Validity area]).
Explain that the frequencies have to be defined and activated in Customizing, as calendars for each warehouse – this means periods have to be generated for the calendars.
Show the consumption and forecast values
[Consumption values] [Forecast values]
Demonstration of requirements planning run to the purchase order
15 min
3. Start requirements planning and trace the process ( TA MDW1 )
Purchasing Requirements planning Requirements planning Plan by vendor
Vendor/invoicing party TS1##
Purch. org. R300
Site T7##
[Enter], [Enter]
Select articles TA03## and TA04##
Requirements planning Interactive planning
Note: If at this point a planned order is suggested instead of the purchase requisition, go back to the selection and select:
Create purch. req.: 1 (fundamental purchase requisition)
Explain the following fields:
Current stock: Column Avail. quantity into line Stock
Required quantity: Column Receipts/requirements in line Purch. req. Number of generated purch. req:
Purch. req.
Delivery date for purchase requisition:
Column Date into line Purch. req.
Explain the requirements determined using the master data for the article: (RP/delivery frequency, forecast values)
If requirements planning for the distribution center is performed on a Monday, it is calculated as follows: the current stock of 490 PC will last until the coming Friday. The order day is Monday and this will be kept. The planned delivery time of 3 days is still within the planning cycle. 510 PC is calculated; the delivery date is the first Friday following the Monday. You want to stock up to the delivery date after next, therefore a quantity of 1000 PC needs to be available at this date.
Planning Save for the first article Planning Save for the second article
4. Display current stock/requirements list ( TA MD04 )
Purchasing Requirements planning Requirements planning Planning file entry Stock/requirements list
Article TA03##
Site T7##
5.
Display purchase requisition ( TA ME53 )
Purchasing Requirements planning Purchase requisition Display
Purchase requisition ...
6. Convert purchase requisition into purchase order ( TA ME59 )
Purchasing Purchase order Purchase Order Purchase Order Create Automatically via purchase requisitions
Purch. org. R300
Vendor TS1##
Site T7##
Program Execute
By double clicking on the purchase order number you can see the corresponding purchase requisitions
7. Display the purchase order and the purchase order document ( TA ME23N )
Purchasing Purchase order Purchase Order Display
Purchase order Other purch. order
Enter the purchase order number [Enter]
Goto Print preview
8. Display current stock/requirements list ( TA MD04 )
Purchasing Requirements planning Requirements planning
Planning file entry Stock/requirements list
Site T7##
9. Create another purchase order (for the collective purchase order) ( TA ME21N )
Purchasing Purchase order Purchase Order Create
Vendor/Supplying Site Known
Order type Standard PO
Vendor
TS1##
Purch. org.
R300
Purchasing group
R30
Company code
R300
Article:
TA03##
25 CAR
TA04##
100 CAR
Delivery date
Two weeks from today
Site
T7##
Storage location
0001
This purchase order is the basis of the demonstrations for the entire process.
Purchase Order: Structure (1/4 to 4/4)
Explain the structure of the Enjoy SAP purchase order with the help of this slide. Point out that it is divided into three sections: Header, Item overview and Item details.
Note: There is no connection between a line selected in the Item overview and the Item details. The index tabs in the Item details section have their own input fields. Also explain that there are dynamic index tabs in the Item details, for example, for purchase order history. This index tab only appears when a goods receipt is posted to an order item.
Purchase Order: Load Building
Additional information: When load building is used, NO new purchase order
is generated. Instead, the individual purchase orders remain as such in the
system, and are merely assigned a common order/delivery date in the load
building dialog if necessary.
The following must be true:
Today common delivery date earliest delivery date of all PO items
Common purchase order date
common delivery date.
Accordingly, the purchase order headers of all purchase orders in a load building process are individually sent to the vendor again, in accordance with the
configuration of the output.
After slide Purchase Order: Load Building Demonstration of load building
1. Load building ( TA WLB5 )
Purchasing Purchase order Order Optimizing PO-Based Load Building Manual Load Building
Vendor/invoicing party TS1##
Site T7##
Site category B
Also released purchase orders Set
Point out that a restriction profile (0001) that has been assigned to the vendor was determined.
The weight restriction contained in the profile is also displayed: minimum 2000 lb., maximum 40000 lb.
Test whether the first purchase order fulfils these criteria:
Select first purchase order and choose Edit Update Restrictions
As the first purchase order is not sufficient, highlight the second purchase order as well.
Alternatively, you can also expand a purchase order (double-click on the purchase order number, but at most, change something in the first purchase order)
Edit Update Restrictions
The red traffic light changes to green, which means all the restrictions have been met.
Enter the common requested delivery date (earliest date of the two purchase orders)
Purchase order Save, answer the confirmation prompt with Yes
Write down the collective number (status line) 3. Check purchase order ( TA ME23N )
Purchasing Purchase order Purchase Order Display
possibly also Purchase order Other purch. order
Enter the number of the second purchase order (created manually), [Enter] Show the collective number in the purchase order: Header data, tab page
Additional data
Indicate the new delivery date (=common required delivery date from the load building): Item data
Point out that the collective number can be printed on the purchase order document, and that the dialog for displaying the purchase order can be supplemented with the collective number.
Requirements planning and purchase orders exercises
40 min
the relevant demonstration.
Purchase Order: Price determination (1/6 to 6/6)
If the time is available, we recommend holding a brainstorming session (using a flip chart or cards) to introduce this topic. Have the participants name demands that they think could influence price determination. You can use this data to explain the concepts of condition types, access sequences, condition tables and calculation schemas and use an example in the system to demonstrate this more clearly.
Purchase Order: Confirmation Control
Show the confirmation control key in the Item details of your purchase order and explain which entries you will shortly expect in the Confirmations index tab. Indicate whereabouts in the system the confirmation control key can be predefined.
Purchase Order: Methods and Times of Sending
Additional information: The message that is related to sending a purchase order has type NEW, and is found automatically in the purchase order header through output determination (similar to the condition technique). In this case (like with conditions), a suitable message record for type NEW must be available in the system.
Topic: Shipping Notification/ Goods Receipts After slide Shipping Notification
Demonstration of the confirmation control key, shipping notification, rough goods receipt
20 min
1. Show confirmation control key and Confirmation index tab ( TA ME22N )
Branch to your purchase orders and select the Confirmations tab page.
ConfContrK = shipping notification/rough goods receipt (0003), that is, a
shipping notification and a rough goods receipt is expected (see F4 help) 2. Enter a delivery notification with number 2304## ( TA VL31N )
Announce the inbound delivery for the day after tomorrow at 3:00 p.m. Enter the delivery notification for the purchase order (number of the delivery notification (2304##)) to identify the document.
Merchandise logistics Goods receipt Inbound delivery Create
Vendor/invoicing party TS1##
Button Select purchase orders, select according to articles TA03## and TA04## by holding down the Ctrl key, select the manually created order items
[Enter]
Delivery date Day after tomorrow, 3:00 p.m.
Ext. identification 2304##
Inbound delivery Save
Explain that this step is not normally performed manually, and that you are only doing so now for demonstration purposes. Usually, we assume that the delivery notice reaches the SAP Retail system via EDI, especially when shipping units are contained in the delivery, and the delivery notice lists the contents of the shipping units (individual articles with quantities).
The main information item here is the delivery notification number, which we use later on in the process.
3. Enter the rough GR with reference to shipping notification ( TA VL41 )
Merchandise logistics Goods receipt Rough GR Create
Vendor/invoicing party TS1##
Site
T7##
Ext. identification
2304##
[Enter]
Delivery note no. 4711##
Rough GR Save
Point out that the delivery note quantities are entered at this point.
This information can be used to find mistakes later in invoice verification, since the vendor usually sends an invoice for each delivery.
Goods Receipt: Alternatives and Process
Make sure you stress: If a storage location is not managed in WM, then you can only find out which quantity of any given article is currently located in any given storage location of a site (distribution center in this case) and which stock type is involved. You cannot, however, find out which storage bin (aisle, shelf, and so on) within the storage location is involved.
If you need to extract information about the storage bin, you will have to integrate the corresponding storage location with WM.
Rough Goods Receipt: Use and Functionality
Additional information: When a rough goods receipt is entered, the vendor’s delivery note number (if known) can be entered in the R/3 System. This option should be used whenever possible.
We highly recommend using an overhead to trace the entire process of the following demonstration. There is a template available for this in Appendix II) Requirements
Planning for Warehouse Deliveries Planning run and Invoice verification demonstrations
Putaway: Structures in WM (1/2)
Additional information: A type CHAR(10) field is available for identifying the storage bins. The template used here, nn-mm-rr and consisting of three numeric coordinates, is just one example of how the ten places of this field can be used. The goods receipt for generic articles cannot be posted with the ENJOY goods receipt transaction in Release 4.6C (also see the online documentation).
After slide Putaway: Structures Goods receipt demonstration
10 min
1. Goods receipt ( TA MB0A )
Goods receipt with reference to the rough GR (identified by the vendor’s delivery note number (4711##))
Merchandise logistics Goods receipt Goods receipt for other reference
Movement type
101 (Goods receipt for PO to warehouse)
Site
T7##
Vendor
TS1##
Delivery note no.
4711##
[Enter]
Edit Item(s) Copy Goods receipt Post
2. Display article document ( TA MB03 )
Merchandise logistics Inventory management Article document
Display [Enter]
3. Display the purchase order history ( TA ME23N )
Purchasing Purchase order Purchase Order Display Purchase order Other purchase order
Enter the number of the manually created purchase order
[Enter]
Item details subscreen, tab page Purchase order history:
The number of the GR document (article document) is available, which means the goods issue for this item has taken place.
3. Display stock overview ( TA RWBE )
Merchandise logistics Goods receipt Environment Stock
Article
TA03## or TA04##
Site
T7##
[Enter]
Point out that the stocks in the distribution center have increased. 4. Display current stock/requirements list ( TA MD04 )
Purchasing Requirements planning Requirements planning
Planning file entry Stock/requirements list
Article
TA03## or TA04##
Site
T7##
[Enter]
Point out that the available stock has increased.
Delivery notification and goods receipt exercises
