IRT100 4.6C Instructors Guide Coll22
Short Description
IRT100 4.6C Instructors Guide Coll22...
Description
R/3 System Release 4.6C Author: Uta Zielke
IRT100 Retail Process Overview Instructor Guide
26.06.2002
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 Management KM Retail Training Quicklink to IRT100.
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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............................................................................................................................. 14
Important 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: Process Overview.................................................................................................... 34 26.06.2002 Page 2
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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
26.06.2002 Page 3
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 None
26.06.2002 Page 4
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 5
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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:
Demonstration Systems:
42887 47070
Data Required Official 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 26.06.2002 Page 6
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 None
26.06.2002 Page 7
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Choose store R200, view Product presentation, and set the Variant field to 001.
26.06.2002 Page 8
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 9
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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: Planned time frame: 09.30 – 16.30 (300 minutes)
26.06.2002 Page 10
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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: Planned time frame: 08.30 -16.30 (380 minutes)
26.06.2002 Page 11
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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: Planned time frame: 08.30 -16.30 (360 minutes)
26.06.2002 Page 12
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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: Planned time frame: 08.30 -16.30 (340 minutes)
26.06.2002 Page 13
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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: Planned time frame: 08.30 -15.00 (300 minutes)
26.06.2002 Page 14
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Important Notes (Regarding the Rest of This Instructor Guide) In the following detailed descriptions of the individual units and topics only those specific slides for which information, hints, or suggestions are provided 1 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. All system demonstrations list the appropriate transactions, paths and instructions. You can also use the solutions to the exercises for the 2 corresponding units/topics for more information.
3
The menu paths in the system demonstrations always start with SAP menu Logistics Retail
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 4 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. 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 5 absorbing the information. It is up to you to decide when you and your students need a break. 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 6 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).
26.06.2002 Page 15
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 industryspecific topics.
26.06.2002 Page 16
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 17
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Unit 1: Course Overview 10 min
Contents of Unit Course Goals Course Objectives Contents Overview Diagram Main Business Scenario Putting 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. Also note, the European VAT system is not portrayed.
26.06.2002 Page 18
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 26.06.2002 Page 19
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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
26.06.2002 Page 20
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 26.06.2002 Page 21
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 22
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 23
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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. 26.06.2002 Page 24
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 25
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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. 26.06.2002 Page 26
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 20 min
26.06.2002 Page 27
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Show navigation in the hierarchy tree
26.06.2002 Page 28
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 userspecifically 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 Find vendor using F4 help: Creditors for article (R3000) 26.06.2002 Page 29
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 articlespecific 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 Similar structure to Logistics DC, plus replenishment parameters
26.06.2002 Page 30
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 30 min
26.06.2002 Page 31
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 32
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 timephased 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
26.06.2002 Page 33
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Site
T7##
26.06.2002 Page 34
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
[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: Column Data for RP element into line 26.06.2002 Page 35
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Article TA03## 26.06.2002 Page 36
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Vendor Purch. org. Purchasing group
Company code Article: Delivery date Site
Storage location
Standard PO
TS1## R300 R30 R300 TA03## 25 CAR TA04## 100 CAR Two weeks from today T7## 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 5 min 26.06.2002 Page 37
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Note: You can also split up this exercise and carry out each part straight after 26.06.2002 Page 38
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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.
26.06.2002 Page 39
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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. Rough GR Save
4711##
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.
26.06.2002 Page 40
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Site Vendor Delivery note no. [Enter]
101 (Goods receipt for PO to warehouse) T7## TS1## 4711##
Edit Item(s) Copy Goods receipt Post Note the number of the goods receipt document
26.06.2002 Page 41
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
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 Site [Enter]
TA03## or TA04## T7##
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 Site [Enter]
TA03## or TA04## T7##
Point out that the available stock has increased. Delivery notification and goods receipt exercises 30 min
26.06.2002 Page 42
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Invoice verification:
(Logistics) Invoice Verification: Invoice verification types Make sure you stress: The background invoice verification types are essential for dealing with the mass volumes of objects that are created in retail. Usually, the R/3 system administrator will schedule invoice verification as a periodic background job that runs at suitable intervals. After slide Logistics Invoice Verification: Correction Options Demonstration of invoice verification 20 min 1. (Actual) invoice entry for background verification ( TA MIRA) The invoice is entered based on the printed invoice in the exercises. The reference to the delivery note number also appears here. Purchasing Logistics Invoice Verification Document creation Create inbound invoice for invoice verification in background Invoice date Today Company code R300 Amount 4525,00 In the Reference document category field, select: Delivery note 4711## Invoice document Schedule verification in background
2. Check in background (TA SE38) System Services Reporting Program RMBABG00 Program Execute Vendor/invoicing party TS1## Program Execute Result: The invoice contains errors. 3. Invoice overview of all of a vendor's incorrect invoices ( TA MIR6) Purchasing Logistics Invoice Verification Additional processing Invoice overview Do not change the selection criteria, [Execute] Double-click on the document number or [Change] in the Item column. The invoice has a difference of USD50.00. 4. Determined differences in the vendor invoice: Article Shampoo (TA03##) Vendor invoice amount 1475 26.06.2002 Page 43
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
(Scroll to the right in the Item overview) Amount from invoice verification 1425 (actual invoice) 5. Invoice reduction due to vendor error: We now assume that the vendor has made a mistake and set the value of the Correction ID field for the article shampoo (TA03##) to Vendor error: Reduce invoice (Scroll to the right in the item overview) You can now correct the error in the condition screen: [Vendor conditions] Change the value of PB00 from 57 to 59 [Back] Confirm the two confirmation prompts with [Enter], which means the correction should only affect one item. The difference is now: 0 Edit Accept and post 6. View the follow-on documents for the invoice Select the rows in the Invoice overview Environment Follow-on documents (Note: To get to the overview from the SAP Easy Access menu, proceed as follows: Purchasing Logistics invoice verification Further Processing Invoice Overview Selection criteria: Select Invoice status posted.) 7. Notification to the vendor (TA MIR 90) Because a vendor error was determined in the invoice, a complaint for the vendor is automatically generated. Purchasing Logistics invoice verification Further Processing Output Messages Output type REKL Sorting 01 Processing mode 1 Invoice document number Invoice number Fiscal year Current year Company code R300 Program Execute Select the document Goto View Invoice verification exercises 30 min
26.06.2002 Page 44
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Subsequent Settlement Subsequent Settlement (Purchasing): Volume-rebate arrangements
Technically, volume-rebate arrangements are groupings of conditions that – in contrast to document conditions – are NOT settled directly with a specific document or document item (such as the gross price), but instead within the scope of partial/interim/final settlement. After slide: Subsequent Settlement (Purchasing): Volume-rebate arrangements Demonstration of volume rebate arrangement 5 min 1. Display a vendor rebate arrangement (TA MEB3) Purchasing Subsequent settlement Volume-rebate arrangement Arrangement Display Position the cursor in the Rebate arrangement field and use [F4] help to search Enter the vendor in tab Rebate agreements for condition granter: Condition granter TS1## [Enter] Select a valid rebate arrangement Press [Enter] twice. Explain the individual fields of the volume-rebate arrangement, especially the calendars used Arrangement calendar AJ Settlement calendar AM 2. Main conditions and period-specific conditions Goto Conditions Double-click on A001 Main conditions 6% Goto Period-specific conditions 3. Scales for the main conditions [Back] to the Volume-based rebate overview Goto Scales
26.06.2002 Page 45
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
After slide Subsequent Settlement: Example Demonstration of evaluations for arrangement and settling arrangements 10 min 1. Sales for volume-rebate arrangement (TA MEB6) Purchasing Subsequent settlement Volume-rebate arrangement List display Sales data Enter the arrangement number Program Execute The Sales a/c to statistics column contains the sales recorded in the statistics to date. This is the sum of the two purchase orders created for vendor TS1##; the arrangement type has been configured such that the statistics are updated in the purchase order. In the column Provisions amounts, you can view the accruals that have been created; from a business standpoint, these are the carryforwards or expected amounts. The accruals are created when the goods receipt is posted, and therefore only involve the second purchase order. Go [Back] to the Easy Access menu. 2. Overview of individual documents involved in the sales ( TA MEB8) Purchasing Subsequent settlement Volume-rebate arrangement List display Single item Enter the arrangement number, Condition records: Enter the validity period of the current month Program Execute Go [Back] to the Easy Access menu 3. Simulation of arrangement settlement through a report ( TA MEB4) Purchasing Subsequent settlement Vendor rebate arrangements Rebate Arrangement Create Settlement Document Via Report Rebate arrangement Arrangement number Condition granter TS1## Settlement date First day of the following month Posting date Today Program Execute The amount pending for settlement is the condition value of the current value with regard to total sales (that is, both purchase orders). Go [Back] to the Easy Access menu
After slide Subsequent Settlement: Example Demonstration of creating arrangement (optional) 5 min 26.06.2002 Page 46
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
1. Create an arrangement (quantity discount) (TA MEB1) Purchasing Subsequent settlement Vendor rebate arrangements Rebate Arrangement Create Agreement type 2000 [Enter] Purch. organization R300 Purchasing group R30 [Enter] Condition granter TS1## Currency USD From January first of next fiscal year To December 31 of next fiscal year Sales comparison necessary Final settl. 2. Create conditions Goto Conditions Article Amount Unit Per Unit of measure Goto Scales
TA03## 0.10 USD 1 PC
Scale quantity Scale quantity Amount [Enter] and [Back] Article Amount Unit Per Unit of measure Goto Scales
100 1000 0.15
Scale quantity Scale quantity Amount Agreement Save
100 1000 0.15
TA04## 0.10 USD 1 PC
Subsequent settlement exercises 20 min Topic: Perishables Planning
Requirements Planning: Special Methods This overview slide shows which alternative requirements planning procedures are still available and which documents are created in these procedures. The purchase 26.06.2002 Page 47
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
order is the central follow-on document or purchasing document. After slide: Perishables Planning: Initial Screen Demonstration of planning requirements for perishables 10 min 1. Prerequisites: 1a. Change lead time for assortment list type (TA SPRO): Logistics General Assortment list Assortment list type For the assortment list type R, set the lead-time 3 to blank. 1b. Generate the assortment list (TA WDBI): Master data Assortment/listing Assortment list Generate Initialization Use the variant IRT100 and start the initialization. 1c. Display assortment list (TA WBBS): Master data Assortment/listing Assortment list Display Use the variant IRT100 and display the assortment list. Make a note of the validity period for the last complete version. 1d. Create purchase orders (TA ME21N): Purchasing Purchase order Purchase order Create purchase order Create several vendor purchase orders (NB) for distribution center R300 for articles R100007, R100008 and R100031, vendor is R3000. Create several warehouse orders (UB) from distribution center R300 to stores R310 to R316. Use articles R100007, R100008 and R100031 for this too. Note: Make sure that the delivery date for each purchase order is within the validity period of the assortment list that was generated. 2. Enter perishables planning (TA WDFR): Purchasing Requirements planning Requirements planning for perishables You can work with the variant IRT100 or make the following settings manually: Distribution center R300 Sales org. R300 Distribution channel R5 Assortment list type Returns item Processing procedure Purchase order Deliv. date Two days from today Procurement period From delivery date To (delivery date +1 day) Purch. org. R300 Purchasing group R30 26.06.2002 Page 48
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Delivery date Issue period
Three days from today From Delivery date To (delivery date +1 day) Purch. org. R300 Distribution channel R1 Settings: Use assortment list (Note: If the assortment list is generated too late, you will have to set the dates to a few more days in the future (try this out first). We recommend saving the data as a selection variant, just to be sure. Please make sure that the delivery date of the warehouse order you created above lies within the issue period for the stores.) [Execute]
Note: In the error log for perishables planning, messages can appear telling you that certain storage locations are not maintained for the article. These messages will not prevent perishables planning being carried out but may be unwanted. In order to avoid them, you can post goods receipts beforehand with the movement type 501 for the article in the respective storage locations and then cancel them again with 502. 3. Execution Tabstrip Information: The remaining quantity (F1) is calculated from the current stock + purchase orders at the vendor – purchase orders of the stores in the warehouse. (The warehouse orders are displayed in column StoreOrders) Tabstrip MRP: Select an item (R100031/R3000) Goto Recipient to go to the issue list Maintain a couple of Purchase order quantities in the Issue list (existing store orders plus any additional random quantities), [Enter] (you may have to press it twice) The sum of the entered quantities is displayed as the Delivery quantity (screen module Issue), Enter this figure in field Purchase order quantity (screen module Issue), [Back] (The purchase order quantity is now copied to the requirements planning overview).
Plan material requirements Save MRP list A purchase order flag appears in front of the item. In this case, both the purchase order with the vendor and any missing warehouse orders were created.
Goto Logs Confirmation Display confirmation logs you can also see the purchase order numbers here: the first number is the vendor purchase order (make a note of this) Exit the perishables planning list.
4. Display purchase order (TA ME23N) 26.06.2002 Page 49
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Purchasing Purchase order Purchase order Display
Show the number of the vendor order, as well as a warehouse order if time permits.
After slide Planning Workbench: Initial Screen Demonstration of Planning Workbench (optional) 10 min 1. Enter the Planning Workbench (TA WWP1) Purchasing Requirements planning Planning workbench Applications Briefly explain the selection options and settings for the worklist, for example, Selecting the distribution center, for which the order is placed
Limiting to certain vendors
Selecting the articles, for example, using planning cycle (order cycle)
Sorting the worklist Create a worklist for the Planning Workbench. You can use variant IRT100 or enter the following selections manually: Site T7## Site category B Purch. org R300 Purchasing group R30 Vendor TS1## (and/or R3000) Program Execute Mention the Internet and email addresses in the worklist that you can branch to directly. 1a. Enter Online planning: Select a purchase order for your vendor by double clicking on it (or New Entry). Explain the advantages of Online planning, for example, Articles from the vendor are suggested to you,
Order quantity proposals can be generated
Proposals are generated from existing forecast data using the Create order quantity proposals (calculator) button. Consumption and forecast data is maintained for article R100002. Select a row, display consumption and forecast data, then generate order quantity proposal. Specify target range as 5 days. Purchase order quantity is calculated. Newly created purchase orders can then be checked against the vendor’s restrictions. For more information on the Planning Workbench, see the SAP Retail documentation, topic Purchasing Requirements planning Planning Workbench.
26.06.2002 Page 50
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
26.06.2002 Page 51
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Unit: Sales and Delivery to Stores 270 min
Contents of Unit Store Sales Uploading POS data and generating warehouse orders Using collective purchase orders to procure merchandise Inbound delivery and distribution in the distribution center Store goods receipt using SAP Retail Store Putting the Unit in Context Starting from a sale in a store, you will explain replenishment of the sold merchandise. In the underlying scenario, we assume that the stores send their sales to the head office as a cash register upload. The cash register data is processed in the head office. Subsequently, the replenishment process is started for all the stores, and the result of this process is warehouse orders by the stores at a distribution center. Because we will not be dealing with the warehouse (distribution center) in this process, the store orders are used to generate collective purchase orders from an external vendor. The merchandise is delivered to the distribution center pre-picked for each store, routed through the distribution center via cross-docking, and ultimately delivered to the store.
Explain automatic requirements planning for stores and display the basic steps involved in delivering merchandise to a store from the distribution center Explain the basic principles of the Replenishment and Store order functions Name the most important steps for generating a collective purchase order
Name the advantages of using cross-docking and flow-through
26.06.2002 Page 52
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Process Overview and Replenishment
Payment Processing at POS The slide shows a typical purchasing situation: A customer pays for their goods at the cash desk in a store. This sale is documented by a register receipt that shows the articles sold with quantity and price. A cash flow also takes place with the payment process at the cash register. The register receipt and payment (or means of payment) are the main information items that are forwarded to the central SAP Retail system. Store Connection to an SAP Retail System Additional information: Additional scenarios, such as Internet and ALE scenarios, exist beyond the three IT scenarios described here. However, these scenarios are not covered in this course. Whether or not to equip the stores with their own, separate systems and have them perform their own retail functions depends largely on the retail company’s philosophy. Choices range from stores with strict centralized management (usually discounters), which may only have a cash register system to record the sales, to independent (do-ityourself) warehouses with their own retailing systems. After slide Replenishment: Parameter Overview Demonstration of replenishment 20 min 1. Display parameter overview for replenishment ( TA WR60) Sales Replenishment Overview Parameters Recipient T2##; Articles R100000 and R100008 [F8] Point out the following information: MRP type (= RP = Replenishment planning)
Set the Replenishment-based inventory management and Correct TO with document quantity for replenishment-based inventory management for article R100008. This means: The (full) MM inventory management is used for article R100000 for replenishment in store T2## The (reduced) MM replenishment-based inventory management is used for article R100008 for replenishment in store T2## Because MM inventory management for article R100008 in store T2## is only merchandise category-specific (if necessary, show this by double-clicking on store T2##, merchandise category R1121), this is the only way to automatically plan R100008 in T2## ( advantage of replenishment-based inventory 26.06.2002 Page 53
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
management) 2. Display stock overview (TA RWBE) Merchandise logistics Inventory management Environment Stock Stock Overview Store T2##; Articles R100000 and R100008 [F8] Because of the MM inventory management for article R100000 a stock of 70 PC is displayed in store T2##, in the simplified procedure for article R100008, no stock is displayed. 3. Carry out replenishment (TA WRP1) Sales Replenishment Replenishments Planning Execute Recipient T2##; Articles R100000 and R100008 [F8] Explain the determined requirements Generate the follow-on documents: Replenishment requirements Generate follow-on documents Call up the replenishment monitor in the dialog box Double-click on the order (purchase order number) Point out the following information: Order type: UB (stock transfer order)
Supplying site: T7## (found through supply source determination)
Order quantities: are specified in warehouse issue units (if necessary, show this in the article master (Environment Article/Basic data) with conversion factors)
After slide Replenishment: Creating Target Stock Demonstration of creating target stock 15 min 1. Automatic creation of target stock through forecasting (optional, TA WR60) Return to the parameter overview of article R100000 in store T2## Sales Replenishment Overview Parameters Recipient T2##; Articles R100000 and R100008 [F8] ... and explain how automatic creation of target stock is controlled by the following fields: Target range of coverage Number of forecast periods
Min. target stock
Target stock (lower forecast value limit)
Max. target stock
Target stock (upper forecast value limit)
26.06.2002 Page 54
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Show that these fields are maintained in the article master: To do this, navigate from the parameter overview to the article master (double-click on R100000), Logistics store view for T2## and point out the general forecast master data (forecast model, period indicator).
Tell the participants that when they are doing the exercises they should not jump from the parameter overview to the article master, as this may prevent other participants from performing replenishment planning. For more information, see the SAP Retail online documentation, topic Replenishment: Forecasting. 2. Master data (replenishment) at article/requirement group level (optional TA MM42, WB02) If relevant, show the relationship between the requirement group in the product and in the merchandise category using a hand-drawn overhead. Show the allocation of the requirement group to the site/merchandise category and point out that requirement group 02 (= large) is set for merchandise category R1111 in store T2##, which means that “large” replenishment requirements exist. Show the replenishment data for article R100000 and requirement group 02 (in the article master under Extras) The participants can now see what a “large” requirement means (e.g. for the target stock). Show the replenishment master data and control parameters for article R100000 and store T2## (in change mode) To do this, use an extra session and verify that the replenishment master data/control parameters displayed at the article (R10000)/requirement group (02) level above have been inherited to the article/site level. 3. Create a stock transfer order (optional, TA ME21N) In addition to the order generated above, you can also manually create a stock transfer order in SAP Retail: Purchasing Purchase order Purchase Order Create Vendor/Supplying Site Known Order type: Stock transport order Supplying site: T7## Header data: Purchasing org.: Purchasing group: R30 Company Code: R300 Item overview: Article/Quantity/BUn R100000 R100008 40 CRT Delivery date: next workday Site: T1## Storage location: 0001
R300
80 CAR
26.06.2002 Page 55
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
After slide Supply Source Determination Replenishment exercises 40 min As a result of enqueue management for the article, the purchase order from the replenishment run may not be complete for all participants . Please be sure to complete any incomplete orders. The stock transfer orders have to contain the following items: R100000 143 BOX R100008 100 CRT If you omitted the third part of the above demonstration, create the stock transfer order now as the instructor, as this order is required later as the second purchase order for a collective purchase order for an external vendor. Store Order and Subsequent Processes Store orders generate different types of documents, depending on the system settings. Note: Replenishment planning generates a requirement for the store and passes this on to the store order functions. Alternatively, requirement quantities for each article can be passed on to the store order using the interface. According to the system settings, these are then copied to the relevant document. Third-party business: If you want a follow-on document from the store order of type NB to be created instead of type UB, you need to make the following changes: R100000 Logistics store T2## SS = 3 R100008 Client level SS = 3 Note: You must not set the variable BUn indicator for article R100000 in the purchasing view. Restart replenishment planning. A vendor order (NB) is created for external vendor R3000 with the order of 143 CAR and 100 CRT for articles R100000 and R100008.
26.06.2002 Page 56
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Merchandise Distribution
Merchandise Distribution: Overview (1/3 to 3/3) Additional information: The push procedure always involves an allocation table, while the pull procedure always involves a collective purchase order. Both procedures have the following in common: the recipient documents (warehouse orders, sales orders) already exist when the merchandise is received in the distribution center, which means the corresponding data (quantity of articles for each store) is already known in the system. Planning Merchandise Distribution: Pull Additional information: You can optimize logistical units of measures during the generation of collective purchase orders. Planning Merchandise Distribution: Push Additional information: When an allocation table is used, procurement planning is always performed by the head office (for the stores as well). Therefore, the head office decides which quantities of an article are sent to which store, regardless of whether a store order exists. The store order can be generated as a follow-on document from the allocation table. Processing Merchandise Distribution: Overview Emphasize that: All the listed processing procedures (with the exception of putaway) are cross-docking procedures; this means no putaway takes place, and the final destination of the merchandise is already known when the goods receipt takes place. Cross-docking itself is the procedure that requires the least effort, as the merchandise is not repacked, but instead is routed through the warehouse in complete packing units. Additional information: In Release 4.5 cross-docking was only possible when no packing material was involved (entire palettes of an article); as of Release 4.6, prepicked orders can also now be modeled in the system. In the following demonstration, create a process overview using an overhead on which you write down the individual documents with numbers, articles, and quantities. This will make it easier for the participants to follow the process. A template for this is provided in the appendix: 1) Sales and Delivery to Stores: Replenishment and Merchandise Distribution Demonstrations.
26.06.2002 Page 57
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
After slide Merchandise Distribution: Control Demonstration of merchandise distribution 30 min 1. Assign distribution profile in the site (TA WB02) Master data Site data Site Change Site T7## [Enter] On the Purchasing/Distribution tab page, enter the distribution profile 002 Note: This distribution profile is configured to allow manual adjustment after the goods receipt (for demonstration purposes) and generate deliveries automatically after adjustment. 2. Show entry for pre-packing in the article master ( TA MM43) Master data Article data Article Display Article R100000 View Basic Data Button Additional data Tab page Additionals, show entry R100043 with method 0005
3. Create collective purchase order (TA WF10) Merchandise logistics Merchandise distribution Collective purchase order Create Distribution center T7## Purch. org. R300 Processing types Select all Procurement period Today until the end of next week Schedule line interval 1 [F8] Select a line and press [Details] to display the corresponding stock transport orders. Select both lines and have the system determine the vendors: Edit Find source of supply Create the collective purchase order: Collective purchase order Generate Entire worklist Make a note of the order number on the process overview Display the collective purchase order (TA ME21N) Merchandise logistics Merchandise distribution Collective purchase order Display Purchase order Other purch. order; Order number of the collective purchase order
Item overview: Point out the receiving site (T7##) and the determined
26.06.2002 Page 58
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
storage location (0003 = cross-docking)
If you have set pre-packing for the article (see prerequisites and show in the article master if you wish), you can now see the subitems in the purchase order. In the Item details (tab page SLS), you can see the recipients and quantities for each main item.
4. Goods receipt for the collective purchase order ( TA MB01) Merchandise logistics Goods receipt Goods receipt for purchase order Movement type 101 Purchase order Number of the collective purchase order [Enter], [Adopt + details] If necessary, enter the date of production for article R100000 (for example, a week ago today) [Post], make a note of the document number on the process overview 5. Check merchandise distribution (TA WF30) Merchandise logistics Merchandise distribution Distribution Monitor First enter the merchandise distribution monitor without a display variant and then explain the Report viewer. Then enter the monitor again, this time with the display variant /IRT100, shown as a list. Distribution center T7## Purchase order number Purchase order number of the collective purchase order Document types Leave all checked Program Execute Expand all items Explain that no adjustment has taken place yet, since the Act. quantity for both articles is still 0. 6. Adjust the distribution (TA WF50) Show the adjustment using [Adjust]) or in a second session Merchandise logistics Merchandise distribution Distribution Adjust Distribution center T7## Purchase order number Purchase order number of the collective purchase order Goods receipt Above GR document [F8] Explain that this step is only necessary in case of an overdelivery or underdelivery. The distribution profile can also be configured for automatic adjustment during goods receipt, provided the GR quantity does not vary too much from the order quantity (percentage in the article distribution profile). Show the distribution: The cross-docking for each warehouse order item appears in the CD quantity column. You can now distribute this quantity (or subquantities) through flow-through. Save the distribution with Distribution Save Total 26.06.2002 Page 59
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Check the adjustment in the distribution monitor Return to the first session and choose Distribution Refresh: The Act. quantity field is now filled 7. Check deliveries in the warehouse order (TA ME23N) The deliveries that are generated when you post the adjustments appear in the purchase order history for the warehouse orders: Purchasing Purchase order Purchase Order Display
Purchase order Other purch. order Purchase order Purchase order number of the warehouse order The delivery number is displayed in the Item details on the Order history tab page; double-click on it to display the delivery view Enter the delivery number in your process overview. Point out that the delivery is not relevant for picking (the P column is blank). As a result, the goods issue can be posted immediately. Note: This is even more apparent in the item details for the delivery
8. Post goods issue via delivery monitor (TA VL06G) Merchandise logistics Logistics Execution Goods issue process Goods issue for delivery Goods issue posting Collective processing via delivery monitor Planned merch. mov. date Today until next Friday Edit All selections Created by the respective user ID (e.g. IRT100-##) [F8] Select all the deliveries and [Post goods issue] 9. Show the delivery document (optional) Select a delivery in the delivery monitor and choose Follow-on functions Delivery messages Then select the delivery and choose Goto Display Briefly explain the structure of the delivery document, for example, show the purchase order number of the warehouse order in the header of the delivery document 10. Check the process using the purchase orders ( TA ME23N) Go to the collective purchase orders and warehouse orders and illustrate the process again based on the purchase order history. While you are doing this, also doublecheck your process overview (overhead). Purchasing Purchase order Purchase Order Display
Purchase order Other purch. order Purchase order
Respective purchase order number
You can see the follow-on documents in the Item details on the Order history tab 26.06.2002 Page 60
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
page. Note: The article document for the goods receipt appears in the purchase order history for the collective purchase order; the delivery and the article document for the goods issue appears in the purchase order history for the warehouse orders. 11. Display stock (TA RWBE) The stock in transit belongs to the store after the goods issue has been posted and is open stock. Branch to the Stock overview for the distribution center and for the store: Merchandise logistics Inventory management Environment Stock Article R100000 or R100008 Site T7## and T2## Also select stock commitments flag this box On the stock line for store T2##, double-click on the stock and branch to the individual list. Show the stock in transit. After slide Merchandise Distribution: Control Merchandise distribution exercises 40 min
26.06.2002 Page 61
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: SAP Retail Store
The Functions of SAP Retail Store Additional information: There are currently between 12 and 15 live customers including Esso worldwide and Migros in Switzerland with approximately 200 stores. SAP Retail Store was introduced in Release 4.5B. After slide SAP Retail Store: Sample Usage Demonstration of SAP Retail Store 15 min 1. Set up Retail Store (TA /n) Favorites Add other objects Web address or file Text: SAP Retail Store Web address: http://igttr.wdf.sap-ag.de:1080/sap/its/homepages/sapstore.htm Note: You can also let the participants set up this menu path themselves as an exercise at the beginning. 2. Log on to SAP Retail Store Log on in English using the training system and training client. Name IRT100-## Password Password Language English Store T2## 3. Display information Information Open goods receipts
Document date today Article R100000 [Find] (You may need to expand the Explorer screen in order to make all the input fields visible). A list appears containing the warehouse orders that have been created and the deliveries belonging to them. You cannot tell from this list that a delivery belongs to a warehouse order. Navigate in the SAP Retail Store using the control elements on this page (blue, round button) and not the browser elements. [Back]
4. Stock overview Stock overview This takes you to the familiar initial screen of the stock overview. 26.06.2002 Page 62
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Article R100000, R100008 Site T2## Flag Also select stock commitments [Enter] 5. Post goods issue at the store Inventory management Goods receipt Reference document identification Reference document [Edit items]
For delivery Delivery number
Enter a goods receipt quantity. You also need to enter a production date for the article item R100000. Also set the Completed indicator. It corresponds to the delivery completed indicator. Then post the goods receipt in the store.
Store Goods Receipt via Retail Store exercises 20 min
26.06.2002 Page 63
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Unit: From Planning to Execution 200 min
Contents of Unit Planning in Merchandise and Assortment Planning (MAP) Allocation Table Picking Labeling Putting the Unit in Context In this scenario, we assume that planning is carried out at different levels and is therefore performed by different people/departments. Depending on which group of people starts the planning, the data is aggregated/deaggregated and then passed on to other levels. There are generally two stages to planning: Merchandise planning and assortment planning. This scenario shows an example of assortment planning at article level, that is, at a detailed level. An allocation table is generated from planning, which copies the plan data from the MAP and passes it on to the allocation table. The allocation table distributes the merchandise to the stores in a site group. In the process, the warehouse is to be cleared. As a result, warehouse orders are generated as follow-on documents for the allocation table.
Look at planning in Merchandise and Assortment Planning (MAP)
Create an allocation table and trigger its subsequent functions
Name the most important functions for allocation tables
Topic: Process Overview
MAP in a Planning Scenario Example scenario: The purchase begins with planning and takes into account business volume data at merchandise category level. This data is aggregated at board level, so that they are able to make a statement about the business volume for each distribution channel. An aggregation therefore takes place at a less detailed level. This can again be the initial position for the sales person, who wants to plan the business volume for each store in a distribution channel on the basis of this data. The plan data is therefore disaggregated again amongst a (large) number of stores. MAP in a Planning Scenario We generally distinguish between a merchandise plan and assortment planning. The merchandise plan is concerned with the question: Which articles/merchandise categories (or generic article level) should attain which business volume and in 26.06.2002 Page 64
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
which time frame? At this point in time it is not yet decided which store(s)/store groups are affected and what quantities they should receive. A grouping break-down does not take place until the assortment planning stage. That is, you go from the less detailed level (merchandise category) to the store level. This data can be passed on to the allocation table, where it is then disaggregated again to article level. After slide Definition: Planning Hierarchy Demonstration of Planning in the MAP 20 min 1. Preparations for the course participants 1a. Run report (TA SE38) System Services Reporting Report ZSENQOFF The report unlocks the Customizing activities and enables several users to access the same table at the same time. 1b. Add the entry to Merchandise and Assortment planning to your favorites ( TA SPRO) Tools AcceleratedSAP Customizing Edit Project Logistics General Merchandise and assortment planning Planning Integrated maintenance using network Demonstrate the transaction code WXPN2 and point out that it will be used a lot in the following exercises. Advise the course participants to save this transaction code in their favorites.
2. Enter the planning scenario (TA WXPN2) Planning Scenario: IRT100map Button [Change] Explain the structure of the planning scenario and the user-friendly navigation in the network. Show the planning step(s) on the left hand side in the display area and explain the navigation window. The right hand side shows the details and definition screen. Depending on whether you are at planning scenario or planning step level, you will see the tab pages Basic settings, Documents or also the tab pages for the Planning levels, the Key figures, Manual planning and possibly also Automatic planning. 2a. Planning step IRT100S1 Double click on the planning step IRT100SI in the display area. Tab page: Basic sett. Button: Planning hierarchy Make the following settings: from specific level: PlanHierarcVersion:
Purch. organization R300 S01
26.06.2002 Page 65
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
[Enter] Open the tree structure on the left-hand side down to the lowest (article) level. Explain that these are the planning hierarchies that have been created. In our example, two articles are to be planned for a purchasing organization and a concrete distribution chain (R300/R5) for the store group ##. The planned unit of measure is PC. The distribution of the planned quantities is specified by the relative proportional factors. This is 1:1. 2x[Back] Tab page: Plng levels Show the selected levels from the whole supply. Tab page: Key figs Show the selected key figure(s) from the whole supply. Tab page: Manual plng Layout: AUFTEILER (Allocation table) Display the planning layout by positioning the cursor on the layout and pressing the [Display] button. Explain the layout and point out the column Qty Store grp $FG, which is created in such a way that it will be ready for input later in manual planning. At a later stage in planning, the data for the year 2002, for example, will be entered here. The column Actual data shows the business volume data for the year 2001. The adjoining columns show the relative deviations and again as a percentage. The layout is intended for planning two articles, that is according to the settings that you have already seen in the planning hierarchy. [Back] Tab page: Manual plng Layout: AUFTEILER (Allocation table) Button [Layout details] In the interface area, you will see that the interface is set up for the allocation table. Continue with the [Maintain interface] button. An allocation table of type 0008 with the organizational data R300/R30 is provided for. Note: The delivery phases have to be entered manually. This is not included in the exercises. Press [Back] twice 2b. Start manual planning Tab page: Manual plng Layout: AUFTEILER (Allocation table) Button [Man. planning] Start manual planning with the following entries: Article 1: TA11## Article 2: TA12## Store groups: 50 + ## Version: T## 26.06.2002 Page 66
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Fiscal year:
2002
[Overview screen] Branch to the plan data for each month using the [Period screen] button. Enter your plan data. You can use the actual data for 2001 as a reference. Use the button [Next combination] (black triangle pointing downwards) to move to the next article. (Note: Depending on the SAP GUI it is possible that this button will not appear in the display. If this is the case the customer can use the Overview screen button to move on to the second article). Finally, return to the overview screen and check the cumulated plan data. Select the Qty Store grp## column and
Extras Interfaces Create allocation table
maintain the following extra parameters in order to create the MAP allocation table: Name: MAP Allocation table IRT100 group ## Distribution center: T7## Delivery phase: Date type: 1 Delivery date: 01. of next month Percent: 100 [Create allocation table]
Extras Interfaces Last allocation table
Show the allocation table you have created (using Allocation table Display, if the database has not finished being updated) and check the sites, articles and quantities and the delivery date at the sites. In the details screen for the sites, the planned quantities in the planned unit of measure PC are converted into the stockkeeping unit of issue. Rounding using the rounding profile is not provided for at this point because it can lead to large discrepancies between the rounded and the planned quantities. Therefore you may get decimal numbers in the stockkeeping unit of measure CAR for the article TA11##. 2c. Manual planning with unequal distribution (optional, TA WXP53) The relative proportional factor for quantity distribution to the stores needs to be changed: In the SAP Easy Access SAP Retail menu: Info system/Planning Merchandise and assortment planning Master Data Store Groups Create/change Store Group Assignments Merchandise category: R1132 [Enter] Site: T1## and T2## Store groups: 50 + ## Enter a different distribution here, for example, 0.3 or 0.7. [Save]. Then do the same as for manual planning and check your result in the second, 26.06.2002 Page 67
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
automatically generated allocation table. 3. Follow-on documents for the allocation table (TA WA03) Purchasing Allocation table Allocation table Display The position type F controls the business transaction stock reduction. Select the items and choose Allocation table Generate follow-on documents Warehouse orders Indicate the split criteria. Separate documents can be created according to delivery date, distribution center, sites and processing methods.
Allocation Tables: Possible Business Transactions Mixed transactions are also possible, for example, half of the stores are supplied by third parties and half by the distribution center. (Or half the goods from third parties and half from the distribution center). When the appropriate item categories are used, you can specify more than one source of supply for each item in the allocation table, as well as specify the respective planned quantities. Allocation table and allocation table follow-on documents exercises 15 min
26.06.2002 Page 68
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Goods Issue Processes
Handling Units Once the delivery is picked, the goods can be packed, and this process can be documented in the system, or, in other words, handling units (used to be known as shipping units) are created. The rest of the process can then be carried out not at the level of individual articles (as items in the delivery) but at handling unit level (for example, goods issue posting). The topic Packing is explained at this stage in the training course, as it belongs to the goods issue processes. You would not use this functionality for delivering goods to stores (as described in our scenario) but you could use it for supplying customers in wholesale. For more information on this topic, see the documentation Logistics Execution, topic Shipping Packing
After slide “Goods Issue” Goods issue processes demonstration 30 min Start all goods issue process activities with: Logistics Retailing Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery 1. Creating outbound deliveries from the warehouse orders (TA VL10B) Select by purchase order number from distribution table follow-on processing …Delivery Create Collective processing for complete documents Purchase orders Shipping Point R300 Deliv.creation date and CalcRuleDefltDlvCrDt (rule for calculating the delivery creation date) delete tab page Purchase orders Purchasing document PO number
Program Execute
Select all items Radio button [Create delivery in background] Radio button [Delivery creation log] (Ctrl + F10) Position the cursor on the group number Goto Documents Two outbound deliveries are generated (one for each ship-to party). Write the 26.06.2002 Page 69
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
numbers down on the process overview slide. 2. Display the outbound deliveries (TA VL02N) Position your cursor on the outbound delivery number Environment Display document
For example: Goto Header Processing Explain field group Appointments Picking date (and time) Planned goods issue date (and time) [Back] to the SAP Easy Access menu
Warning: write this down.
3. Outbound Delivery Monitor (TA VL06O) There are several options here. In order not to confuse the customers too much, you can use the outbound delivery monitor to prevent the customer having to keep looking for the menu paths for the goods issue processes. ...Outbound Delivery Lists and Logs Outbound Delivery Monitor For picking Shipping Point R300 Picking date Planned goods issue date – see above Created by IRT100-## Program Execute Select both deliveries. Create TO in background Adopt pick. quantity 1 The lines in the two deliveries then go green. [Back] to outbound delivery monitor. 3b. Confirmation ... Outbound Delivery Monitor For confirmation Shipping Point Picking date Created by Program Execute
R300 Planned goods issue date – see above IRT100-##
Select both deliveries. Confirm in background Adopt pick. quantity 1 The lines in the two deliveries then go green. [Back] to outbound delivery monitor. 3c. Post goods issues ... Outbound Delivery Monitor For goods issue Shipping Point Picking date Created by
R300 Planned goods issue date – see above IRT100-##
26.06.2002 Page 70
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Program Execute
Select both deliveries. Post goods issues Actual goods movement date Today The lines in the two deliveries then go green. [Back] to outbound delivery monitor. 4. Display picking status in the outbound delivery (TA VL02N) ...Outbound Delivery Change Single Document Enter outbound delivery number, [Enter] Overview Header Display entire status consisting of picking, WM activities, confirmation, goods issue all show status C (picking complete). [Back] 4b. Display document flow in the outbound delivery (TA VL02N) ...Outbound Delivery Change Single Document Enter outbound delivery number, [Enter] Environment Document flow Entire processing status complete. [Back] 5. Create delivery note for outbound delivery (TA VL02N) ...Outbound Delivery Change Single Document Enter outbound delivery number, [Enter] Follow-On Functions Messages from Deliveries Output type: LD00 Program Execute Select the deliveries [View] 3x [Back] (until you get back to the SAP Easy Access Menu).
6. Display stock overview (TA RWBE) Merchandise logistics Inventory management Environment Stock Stock overview Article TA11## Site T1## or T2## Also select stock commitments x [Execute] Once the goods issue has been posted, the goods belong to the store and appear in the on-order stock. 26.06.2002 Page 71
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
7. Post store goods receipt (TA MB0A) You can only post the goods receipt to the store using Goods receipt for other reference not using Goods receipt for purchase order . This means that you require the outbound delivery as the reference document. Merchandise logistics Goods receipt Goods receipt for other reference Movement type Site Delivery [Enter] Goods receipt Post [Back]
101 T1## or T2## Delivery number
Goods issue processes exercise 30 min
26.06.2002 Page 72
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Unit: Analysis and Promotions 270 min
Contents of Unit Reporting in the Business Information Warehouse Promotions Allocation Table Additionals Discontinuation and Archiving Putting the Unit in Context The scenario includes an exception analysis, which helps inform the sales manager about sales problems in certain stores, for example. A promotion is then created and scheduled, and the merchandise is distributed to the stores in a site group using an allocation table. In the process, the warehouse is to be cleared. As a result, warehouse orders are generated as followon documents for the allocation table. The goods issue processes take place in the same way as in the previous unit. Finally this scenario is used to tackle the problem of discontinuation and archiving.
Looking at reports in BW
Create a promotion and trigger subsequent functions
Name the most important functions for allocation tables
Explain how to use additionals
Describe discontinuation and archiving in SAP Retail
Topic: Process Overview Structure of the Business Information Warehouse The architecture can be described using three levels: extraction, data storage and data analysis/presentation. Both SAP systems and non-SAP systems can be used as data sources. Extraction is triggered, monitored and controlled by the BW system. Data transfer is almost completely automatic. The BW system works with its own database in which both meta data (information on the application data, for example, the InfoObjects available) and application data from the different source systems is saved and prepared. InfoCubes are multi-dimensional, relational tables in which data is aggregated. The ODS (Operational Data Store) contains data at document level, for example, data that should not be aggregated (for example, prices). The PSA (Persisting Staging Area) contains data at document level (raw data) that is used for updating in the ODS or 26.06.2002 Page 73
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
InfoCubes. The Administrator Workbench helps to extract and manage the data. The data is transferred to the reporting level, which can either contain Microsoft Excel or indeed other tools for presentation. The data can also be evaluated using a Web browser. Proposed Solution: Business Content Business Content is shipped for different areas of a company and for industry solutions, including Retail. Compare the SAP Library with the Business Information Warehouse. The aim is to provide the customer with a number of instruments for data extraction, administration and evaluation with which the implementation of BW can be made easier. Business Content: Retail Example Reporting Level: You can call the previous as well as the current query view in the Business Explorer Analyzer. You can save the query view as a workbook. A certain query view can be saved as a workbook for the end user either for access using the Bex browser or using a Web browser. This can be done by storing the workbook in the Bex browser and the end user is then given access to the evaluation. You can restrict the authorization for the end user so that he or she can only navigate and can no longer change the query definition. If the end user is assigned to a role, he or she can see all the workbooks for this role. The end user does not normally create the definition for queries in the BEx Analyzer. It is a “superuser” who does this. From InfoCube to Workbook The slide explains how data is supplied from the InfoCubes. When queries are defined (programs for evaluating BW data), InfoObjects (key figures and characteristics) are selected from the InfoCube. By filtering the data in the Business Explorer, a selection of data is determined from the query definition. When a query is executed (or refreshed), all the data that was selected is determined from the InfoCube. In the IDES landscape there is a BW Master and a demo and test system. In this test system a query and a worksheet have already been set up for the demo. You can/must set up the relevant system in your SAP Logon or start your demo using the WTS server. The BW demo only functions fully if the SAP Logon 620 has been installed. 1a. Entering the BW System using the SAP Logon: SAP Logon 620 Server DEN / 700 (Message server: iwdf9152.wdf.sap-ag.de) 1b. Entering the BW System using the WTS server: SAPNet http://wts.wdf.sap.corp:1080 CORP ICA Desktop 6.20 Window View Log on again using your D-user and start the SAP Logon. Set up the DEN message server here.
26.06.2002 Page 74
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
In the following demo description the definitions/settings for the query, exceptions and so on are all listed for safety reasons in case the system settings should be lost and you need to make the settings again. Everything should already be available (meaning the query ZRT_C02_Q0100 with the two exceptions of good and bad article sales, and the template ZRT_C02_T0100) and you do not have to make any more settings. Check this before running this course. After slide Result in Worksheet Demonstration of an exception in the Business Information Warehouse 40 min This demo is to be used to start off the topic of reports in the Business Information Warehouse. 1. Logging on to the System: DEN / 700 (iwdf9152.wdf.sap-ag.de) is the standard demo system (warning: no training system, that means: no support!). user: TRAINING password: retail 2. Display the result in the worksheet and query SAP Menu Business Information Warehouse Business Explorer Business Explorer Analyzer Entry [BW_00_700] Radio button [Open] Queries Radio button [Find] Technical name of the query: ZRT_C02_Q0100 The initial screen is saved in the favorites for the result on the worksheet (RRMX article sales). You can choose and display the “normal” way using the Business Explorer Analyzer. Both ways lead to the article sales query that was already created. Explain the result of the worksheet. Refresh the query (button [Refresh query]). Make the changes on the worksheet, for example: Position your cursor on plant (column header in results area), and right-click the mouse: Plant Display as Description
Place your cursor on the user-definable characteristics CalYear/Month, and right-click the mouse: Expand Vertical.
Position your cursor on material (column header in results area), and rightclick the mouse: Change Material with CalYear/Month.
Place your cursor on the user-definable characteristics CalYear/Month, and right-click the mouse: Delete drilldown Position your cursor on Gross Sales/Sales Value w. Tax (column header in results area) and right-click with mouse: Sort Ascending SalesVal.w.Tax
Position your cursor on Gross Sales/Sales Value w. Tax (column header in results area) and right-click with mouse: Currency Conversion Target Currency: USD, conversion type MEANTODAY, [Execute]
26.06.2002 Page 75
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Cancel the last step by choosing [Back] in the BEx Analyzer menu bar
Place your cursor anywhere in the results area and right-click the mouse: Back to start takes you back to the initial screen Features of the query display (for example, column widths after refreshing and so on): Place your cursor anywhere in the results area and right-click the mouse: Properties
(Note: You can only access the query from the BEx browser indirectly using a workbook that you saved. Authorizations suffice to prevent a user changing the query definition in this way. Go to Change the query definition (global) and explain the structure of the query. You can see the key figures and characteristics of the cube on the left side of the screen and the characteristics are displayed under the individual dimensions. The structure of the query is defined by adding the characteristics and key figures to the areas filter, user-definable characteristics and columns. (Note: The columns and rows form the drilldowns that are displayed when the query is called. User-defined characteristics are not displayed but the user can expand the workbook to see them. Filters are used to restrict data that cannot be used for navigation. All characteristics and key figures can also be filtered. Variables are used for user-specific data selection (for example, months) before executing a query. Key figures can be calculated using formulas without them necessarily having to be updated in the cube.) The query is created in the following way: Filter: Copy the characteristic calendar year (from time dimension) to the selection and right-click on the mouse: Restrict, select year 2001 Copy the characteristic distribution channel (from distribution chain dimension) to the selection and right-click on the mouse: Restrict, select department store Copy the characteristic sales organization (from distribution chain dimension) to the selection and right-click on the mouse: Restrict, select Retail USA User-Defined Characteristics: Copy characteristic CalYear/Month (from time dimension) to the selection Columns: Copy key figure Gross Sales/Sales Value with Tax to the selection Rows: Copy characteristic material (Article dimension) and characteristic plant (from the plant dimension) to the selection. 3. Display and activate exceptions Using the radio button [Exception] you can explain the definition of exceptions. Explain the meaning of this exception and show that the indicator Activated has not been set. This means that the exception can/must only be activated in the workbook at a later stage. The exceptions were defined as follows: Description: Exception: Poor article sales Key figures: Gross Sales/Sales Value with Tax Tab page Exception values: Pushbutton [New] From 0 to 100 alert level Poor 9, Pushbutton [Adopt] From 100 to 200 alert level Medium 5, Pushbutton [Adopt] 26.06.2002 Page 76
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Tab page Cell restrictions: Automatic operator to be used: All Pushbutton [New] Fields below: Select material, plant and everything except results, pushbutton [Adopt] Pushbutton [OK] Description: Exception: Good article sales Key figures: Gross Sales/Sales Value with Tax Tab page Exception values: Pushbutton [New] From 5000 to # alert level Good 1, pushbutton [Adopt] Tab page Cell restrictions: Automatic operator to be used: All Pushbutton [New] Fields below: Select material, plant and everything except results, pushbutton [Adopt] The exceptions can also be started from the result of the worksheet. Navigate to this using the pushbutton [Layout]: Display Exceptions. You activate the exception by double clicking. 4. Start the Query in the Web Browser Use the menu path Tools Start in Web Browser Query (Standard View) You can also display the query. If you do not want to display the whole table, select Expand in the columns in row GM Store 310. Then select an article by clicking the mouse on an article (for example, R100000) and then right-click on this article: Filter and drilldown according to calendar year/month. A new table is displayed and you select the GM Store 310 by clicking once on it. Then you select Keep filter value by right clicking on the mouse. A new table is displayed which you can also display as a linear graph. Use the pushbutton [Table] to return to the initial screen. 2. Start the Web Application Designer Start Programs Business Explorer Web Application Designer Depending on the system settings, you may not be able to access the Web Application Designer this way. It may be necessary to access it from the worksheet to the query using the menu path: Business Explorer Web Application Designer and open it up this way. The Web Application Designer is used to design the layout of the query for Web reporting. You create placeholders for the different areas (characteristics, graphics, results area, and so on). Explain the general method of doing this by displaying the selection of Web items in the top left of the screen; the Data Provider and the reference to the queries are set in the bottom left. The actual cockpit is on the right side of the screen and you use this to model the Web items. 26.06.2002 Page 77
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
By opening this, the history is displayed where you can select the template that was created Article sales cockpit (technical name ZRT_C02_T0100) and you can navigate to the actual display using the pushbutton Execute in the Browser. Explain that the Web Application Designer is normally used for creating (possibly user-specific) templates. These are then started from the Web browser. Exception Reporting in the Business Information Warehouse Note: In addition to key figures from the InfoCubes, key figures in the query can also be defined and they are derived, for example, from formulas or using conditions from other key figures. You can also define exception conditions for combinations of key figures this way. For example, the sales are less than $1,000 AND the stock is more than 1,000 PC. Promotion Assignments Both conditions of purchase and sales conditions can be created for a promotion. Alternative sales prices can be defined for individual sites (within the framework of price activation during subsequent processing for promotions) in addition to the sales prices at site group level. Subsequent Processing for Promotions: Additionals Mention that the control of the additionals is dependent on the procedure for additionals, which describes both their location and which data is generated. Explain that the additionals can be assigned both in the article master and during subsequent processing for promotions. (Background: (Note that separate additionals IDocs have to be generated in the latter case, while the additionals information is sent with the assortment list IDoc in the former case). Selling Promotional Merchandise Coupons and bonus buys are initially completely independent of the promotion, but can be assigned to one later. Coupons are articles that only have the views basic data, listing, and POS. The costs can be distributed to a maximum of three cost objects. Conditions, discounts, or free goods can be defined to redeem these articles, using the bonus buy. For more information, see IRT320 Prices and Promotions.
26.06.2002 Page 78
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Promotion Planning Promotion: Scope of functions It is easier to interpret the individual functions if you group them together into “Logistics” (to the right), “Presentation” (lower left), and “Promotion prices” (upper left). To help the participants understand the transactions and keep track of the documents generated during the demonstrations for promotions and stock allocation, we recommend writing down the information listed in Appendix IV) Promotion Planning to Goods Issue Processes Demonstrations. After slide “Promotion: Prerequisites” Demonstration of promotion planning 20 min 1. Create promotion for sales promotion (TA WAK1) Master data Edit promotions Promotion Create Promotion type: 0002 (promotional agreement) (Note: In the exercises, promotion type 0001 is incorrect) 1a. Enter the data: The promotion number is assigned internally (leave the field blank). Promotion “Fun and Games ##" Currency: USD ConsumerSaleFrom and To: From 1 to 15 of the month after next. Tab page Fast entry: TA11## 1440 PC TA12## 300 PC [Enter] Reduce the prices by USD 2 (TA11##) and USD 10 (TA12##), respectively. 1b. Header data Goto Header data; tab page Planning, POrg Purchasing group [Back] Promotion Save
R300 R30
Write down the promotion number 1c. Create a site group and assign sites Promotion Change, [Enter] Tab page Site groups Environment Maintain site groups Create site group Class Class type [Enter]
BGAK## 030
26.06.2002 Page 79
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Name “Site group ## for promotion”. [Save] Enter site group BGAK## in the table Environment Maintain site groups Assign sites Confirm the information message indicating that no assignments exist yet for this class Edit New assignments Choose Plant in the dialog box that appears Enter sites T1## and T2## in column CustomerNoSite [Save] 1d. Quantity planning Tab page Quantity planning Environment Allocation table Create Allocation rule type Purchasing organization Purchasing group [Enter] Allocation table number Name Column Base site group Select an item Goto Sites
0001 R300 R30 ARAK## “Allocation table ## for promotion” BGAK##
Assign two quotas to site T1## Allocation table Save Confirm the message that the allocation rule has been set. Explain that fixing the allocation table means that the site group is now maintained differently than its quotas in the classification system. In the Quantity planning tab page, enter the data for each item in the promotion: Allocation quantity Like the planned quantity Unit of measure PC Allocation table ARAK## Item category F (stock reduction) – explain. 1e. Promotion Save. Promotion planning exercises 20 min
26.06.2002 Page 80
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Promotion Subsequent Processing
Promotion Subsequent Processing The source determination process should be performed before the allocation table and before price activation. Point out that source determination is independent of the item category of the allocation table. Point out that there is no workflow for this. After slide "Promotion Uses Allocation Tables" Demonstration of subsequent processing for promotions 20 min 1. Subsequent processing for promotions (TA WAK5) Master data Edit promotions Promotion Subsequent processing Promotion number: See above 1a. Listing (create a promotion module) Button [Listing] Start the listing with the [Listing] button Confirm both messages The number of the assortment module is displayed Promotion Save 1b. Supply Source Determination Button [Supply source determination] Select items in column S Button [SSD suggest.] In the table that appears, select the button [Change SSD] for each item and then check the vendor column if the distribution center T7## is defaulted. If this is not the case, enter the relevant data. [Back] Promotion Save 1c. Price activation Button [Price activation] Select an item in column S Press the [Site data] button Show that alternative prices can be maintained at site level here. Select items in column S Press the [Activate] button Press [Background calculation] in the dialog box that appears Promotion Save
26.06.2002 Page 81
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
1d. Assign additionals (label to affix in the store) Button [Additionals] Select both items Button [Additionals] Column Additionals R100041 Column Method 0004 Select a line Additionals Assign Select the sub-tree of the site group. (Important: This makes it possible to assign different additionals to different site groups.) Select Back twice Promotion Save 1e. Generate allocation table, display allocation table ( TA WA03) Button [Allocation table] Select all items Button [Allocation rule] Number of lead days: 0, confirm message Write down the allocation table number Promotion Save 1f. Promotion announcement for the stores (notification) Button [Promotion announcement] Button [Notification] Position the cursor on T1## Edit Select sub-tree
Promotion announcement Notification
Confirm the message, [Back] Promotion Save. Go Back to the Easy Access menu. Promotion Promotion announcement Send Screen (TA WAKV) Enter the promotion number and site Program Execute
b. Change allocation table follow-on documents from promotion (TA WAK2) c. Show that the planned quantities from the promotion have been included in the allocation table Promotion Change, [Enter]
Environment Allocation table
Allocation table Display For each item: Select the item
26.06.2002 Page 82
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Goto Sites Sites for item Planned quantities [Back]
b. Generate the follow-on documents for the allocation table ( TA WA03) (in the allocation table display:) Edit Select Select all
Allocation table Generate follow-on documents Warehouse orders The follow-on document type depends on the item category for the allocation table
Edit Generate warehouse orders A warehouse order is generated for both stores. Write down the number and double-click to go to the purchase order.
Subsequent processing for promotions exercises 30 min Reducing the Dataset There are different tables that can become very large after production startup. Once they reach a certain size, archiving these tables can become very difficult. The option to archive is dependent upon the system (UNIX, NT, etc.). Archiving Archiving is done in two steps. A) The data is written from the R/3 database to an archiving file. This process is carried out by the archiving and write programs. This process is carried out by the archiving and write programs. If a document is produced, a residence time is determined for each document type. This determines whether, when and how a document of this document type should be archived. The sequence in which documents are archived is also important. Example: In Purchasing, purchase order, goods receipt and invoice documents are generated. However, these documents are archived in the opposite sequence.
26.06.2002 Page 83
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Unit: Warehouse Returns 90 min
Contents of Unit Store Returns Returns with Returns Allocation Table Vendor Returns Putting the Unit in Context The fifth process deals with the processing of returns. In one case we assume that a store wants to return certain articles (including one generic article), for example, because they can no longer be sold. To do this, a stock transfer order with returns indicator is used to generate a delivery with the appropriate item category; the physical goods issue from the store is posted based on the purchase order, while the physical goods receipt in the distribution center is posted based on the delivery. To do this, a stock transfer order with returns indicator is used to generate a delivery with the appropriate item category; the physical goods issue from the store is posted based on the purchase order, while the physical goods receipt in the distribution center is posted based on the delivery. In the second case, a returns allocation table is used to model a recall action in which all stocks of an article are to be taken out of the stores of a certain site group. To accomplish this, a separate allocation strategy (function module) that determines the store stocks and uses them as planned quantities has been written.
Create a returns allocation table
Generate a stock transfer order
Generate a returns delivery
Post a goods issue as a negative goods receipt in the store
Post a goods receipt as a negative goods issue in the distribution center
Like in the preceding units, you should use an overhead to keep track of the demonstrations below (see Appendix IV) Warehouse Returns: Demonstration of store returns
26.06.2002 Page 84
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Store Returns After slide “Post goods issues in the store with goods receipts in DC” Demonstration of store returns 15min 1. Display the stock overview for article TA06## (TA RWBE) Master data Article data Article Display Article number TA06## View Basic data Environment Stock overview Position the cursor on the unrestricted use stocks for each site Goto Variant split Distribution center T7## should have a certain number of vacuum cleaners, and store T1## should have 6 deluxe and 4 basic vacuum cleaners. 2. Create stock transport order (TA ME21N): Purchasing Purchase order Purchase Order Create Vendor/Supplying Site Known Order type Stock transport order Supplying site T7## Header data, tab page Org.data: Purchasing organization R300 Purchasing group R30 Company code R300 Item overview: Article TA06## Purchase order quantity 10 Delivery date Three working days from today Site T1## Storage location Lean WM SL [Enter] Set returns indicator: Returns item [Enter] Item detail, tab page Variants Variant quantities: De luxe ++ (red) 6 Basic (green) 4 Purchase order Save Write down the purchase order number on the process overview slide. 3. Generate the delivery for the purchase order in the background ( TA VL10B) Merchandise logistics Logistics execution Goods issue process 26.06.2002 Page 85
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Goods issue for delivery Delivery Create Collective processing for complete documents Purchase order Shipping point/receiving pt R300 Delivery creation date Delete CalcRuleDefltDlvCrDt 3 (Ship-to party T1## Tab page Purchase orders, Purchasing document See purchase order Choose [Execute] Select both items Push button [Create delivery in background] You can display the documents through the delivery creation log: Button [Delivery creation log] Select the group number Goto Documents Write down the document numbers on the process overview slide. Point out the item category NLRN in the delivery. 4. Post the store goods issue as a negative goods receipt ( TA MB01) Retailing Merchandise logistics Goods receipt Goods receipt for purchase order Movement type 101 Purchase order See above Site T1## Storage location 0001 Point out movement type 161 (returns) and the V sign of the goods movement (negative = reduction). Goods receipt Post Write down the document number on the process overview slide. 5. Post the goods receipt in the distribution center as a negative goods issue ( TA VL02N) Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Change Single Document Outbound delivery number See above Tab page Picking Make sure column Storage location is 0001 Select the item Edit Post goods receipt 6. Repeat the stock overview process (TA RWBE) Master data Article data Article Display Article number View Basic data
TA06##
26.06.2002 Page 86
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Environment Stock overview
Position the cursor on the unrestricted use stocks for each site Goto Variant split The stock in store T1## is now 0, and the stock in distribution center T7## has been increased by the store stock
Store returns exercises 20 min
26.06.2002 Page 87
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Returns Allocation Table After slide “Returns to Vendor” Demonstration of returns allocation table 10 min 1. Create a returns allocation table for article TA01## (TA WA01) a. Create the allocation table Purchasing Allocation table Allocation table Create Alloc. tbl type 2004 Purchasing organization R300 Purchasing group R30 [Enter] Name Returns group ## Site delivery date Two working days from today DC delivery date Three working days from today Article TA01## Site group R_PROM_01 Distribution center T7## [Enter] => Planned quantity: The returns quantity is determined from the store stocks as a result of the allocation strategy in the allocation table type b. Assign the vendor to which the merchandise will be returned Select the item Goto Distribution centers Distribution centers for item Vendor/invoicing party [Back]
TS1## (default value)
c. Examine the quantities per store Select the item Goto Sites Sites for item d. Save the allocation table Allocation table Save Write down the allocation table number on the process overview slide. 2. Generate the warehouse order as a follow-on document of the allocation table ( TA WA01) Allocation table Change or Display, do not press [Enter]
Allocation table Generate follow-on documents Warehouse orders Pushbutton [Gen. warehouse orders] Write down the order number on the process overview slide.
26.06.2002 Page 88
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
3. Generate the delivery for the purchase order in the background (optional) ( TA VL10B) Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Create Collective Processing of Documents Due for Delivery Purchase Orders Shipping point/receiving pt R300 CalcRuleDefltDlvCrDt 3 Ship-to party R310 to R315 Tab pages Purchase orders, Purchasing document See above Choose [Execute] Select an item Push button [Create delivery in background] Pushbutton [Delivery creation log] Select the group number Button [Documents] Write down the document number on the process overview slide. 4. Post the store goods issue as a negative goods receipt ( TA MB01) (optional) Retailing Merchandise logistics Goods receipt Goods receipt for purchase order Movement type 101 Purchase order See above Site R310 Storage location 0001 [Enter] Point out movement type 161 (returns) and the V sign of the goods movement (negative = reduction). Goods receipt Post 5. Post the goods receipt in the distribution center as a negative goods issue ( TA VL02N) (optional) Merchandise logistics Logistics execution Outbound Process Goods Issue for Outbound Delivery Outbound Delivery Change Single Document Outbound delivery number see tab page above Picking, column Storage location: 0001 Select the item Edit Post goods receipt 6. Prepare returns to the external vendor (optional) a. Vendor order as follow-on document of the allocation table (TA WA03) Allocation table Change or Display, do not press [Enter]
Allocation table Generate follow-on documents Vendor orders Pushbutton [Gen. vendor orders]
26.06.2002 Page 89
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Write down the order number on the process overview slide. b. Display order number in the allocation table (TA ME23N) Double-click on the purchase order number, or: Allocation table Display Select the item Goto Sites Sites for item Select the item Goto Sites Details Tab page Administrative data, button [Display vendor order] (returns indicator)
Returns allocation table exercises 30 min
26.06.2002 Page 90
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Unit: Selling To Customers on the Internet 170 min
Contents of Unit Creating a sales order (using the SAP Online Store) Converting a sales order into a purchase order Inbound delivery of merchandise to customers Sending a vendor invoice to vendors Billing a sales order to the customer Putting the Unit in Context The last unit in the course deals with the wholesale sector. In addition to the different ways of getting started in this process (customer purchases from the Online Store, entry of a sales order), the third-party case is also covered here – that is, an external vendor delivers the merchandise to an external customer. In this context, you will explain the control through the item category and schedule line category in the sales order. Settlement is carried out by the retail company’s head office: the vendor sends an invoice, which is entered and verified in SAP Retail. In turn, the retail company sends an invoice (customer billing document) to the customer.
Procure merchandise from a vendor for a (wholesale) customer in SAP Retail.
Perform the following activities in particular: Create a sales order in SAP Retail and using the Online Store Generate vendor orders from a sales order Bill sales orders
You now have to convert the SAP Online Store to the English version: IMG: Logistics – General IACs Product Catalog and Online Store Online Stores Choose store R200, view Product presentation, and set the Variant field to 001.
26.06.2002 Page 91
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Online Store Procedure: This process starts with the demonstration. The most important concepts are then repeated using the slides. After slide SAP Retail Store: New Customer Registration Demonstration of Online Store 15 min 1. Access the Online Store in the Microsoft Internet Explorer URL: http://igttr.wdf.sap-ag.de:1080/sap/its/homepages Select language English and the training system in which your course is carried out. [Start SAP Online Store] Select Online Store R200 Online Retail IRT100
Customer number Password [Logon]
TCA## Group##
2. Navigation in the Online Store Demonstrate several options for searching for articles and ordering articles. a. Searching for an article with the article number Keyword or product number R100061 (Phone “Ultrapol 633”) Search in All shops [Find] Select R100061 and enter the following data in the screen that appears: Quantity 20 [Add to shopping basket] Press [Back] twice b. Keyword search
Keyword or product number Search in [Find]
*battery* All shops
[Add to shopping basket] c. Promotions [Promotions] [Promotion of the week] [Add to shopping basket] d. Check the results in the shopping basket and adjust [Shopping basket/Orders] in the menu bar Check and correct if necessary 26.06.2002 Page 92
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
“Ultrapol 633” "Replacement battery" "RX-T2-Micro"
R100061 R100060 R100054
20 PC 20 PC 50 PC
e. Request a quotation and send the order [Quotation] The SAP Retail system now simulates a sales order and displays it as a quotation in Microsoft Internet Explorer. In particular, this determines the current prices (customer-specific where relevant) [Order] This creates the order in the SAP Retail system. The customer is sent the order number and delivery date as confirmation. Make a note of the order number on the process overview slide 3. Display sales order (TA VA03) Display the sales order that was created in the SAP Retail system: Sales Sales order Order Display
Select button [F4] and search help Sales documents for customers. Partner TCA## Press [Enter] twice Point out the following details: In the header details/tab page Sales: Order type AA (set in Customizing)
The sales area (determined from the customer)
PO number: Point out ITS
Billing: Creating Invoices Additional information: When you create invoices from the billing due list, you have to select whether you want to bill order-related or delivery-related document items. Order-related items are (sales order) items for which no delivery takes place (from the R/3 System), such as rental contracts or items that are sent directly from the vendor to the customer. The quantity and prices from the sales order item is used for such items. Delivery-related items are (sales order) items for which a delivery takes place (from SAP Retail), such as merchandise orders that are shipped from your own distribution center. The quantity for such items is taken from the delivery item, but the prices are taken from the sales order item. The “Relevant for billing” field in Customizing for the item category determines whether a sales order item is to be billed order-related or deliveryrelated. In contrast, Customizing for the sales order type determines which billing document type to use for the individual items. After slide Billing: Billing Document Structure Online Store exercises 20 min
26.06.2002 Page 93
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Sales Order/Purchase Requisition/Purchase Order
Order: Prerequisites Additional information: The times used in scheduling are determined as follows: Transit time From the route of the sales order item Lead time From the route of the sales order item Loading time From the shipping point of the item (may also take the route and loading group of the article into account) Pick/pack time From the shipping point of the item (may also take the route and weight group of the article into account) Whether or not the loading time and/or pick/pack time is dependent on the route is determined from the means of transport specification in the route. Each item can have several allowed item categories and a single default item category. Which item category is actually used is configured in Customizing and is dependent on The sales document type
The item category group of the article (sales view of the article master)
Item use (text item, free goods, and so on)
Item category of the higher-level item The item category determines, among other things, whether the corresponding item will be billed on an order-related or delivery-related basis (Customizing). Also see the additional information for slide Billing: Creating Invoices. The schedule line category determines how the article is actually procured for the customer, and is determined from the combination of article item category and article MRP type. Slide SAP Online Store: Displaying Layout Area Hierarchies Demonstration of the product catalog 10 min 1. Show the SAP Retail Store in the R/3 System (TA WWM3): IMG: Logistics – General IACs Product Catalog and Online Store Online Stores Show the most important profiles and the product catalog used (RET0000001) in Online Store R200. 2. Display product catalog (TA WWM3) 26.06.2002 Page 94
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Master data Edit product catalogs Product catalog Display Catalog RET0000001 [Basic data] Briefly point out the sales area and explain the versions (dependent on the language and/or currency) [Layout] Show the layout area hierarchy and the maintenance of documents and texts for the articles (parallel to the SAP Online Store in the Microsoft Internet Explorer; for example, in Electric appliances Consumer electronics Complete sets for article R100054)
We highly recommend using an overhead to trace the entire process of the following demonstration. You will find a template in Appendix V) Selling To Customers On The Internet: Sales order to Billing document demonstrations Sales Order Slide: Promotion Determination (2/2) Demonstration of promotion order 10 min Note: The Online Store may be temporarily unavailable. In this case (and only in this case), please enter the sales order directly in the R/3 System. 1. Manually enter the sales order (optional, TA VA01) Sales Sales order Order Create Order type AA Sales organization R300 Distribution channel R4 Division R1 Sold-to party TCA## PO number: 2304## Requested delivery date: One week from today [Enter] R100054 50 PC R100060 20 PC R100061 20 PC [Enter] Confirm any warning messages that are displayed Confirm the proposed schedule lines with the [Full delivery] button Sales document Save 2. Display sales order (TA VA03) Sales Sales order Order Display
Select button [F4] and search help Sales documents for customers. 26.06.2002 Page 95
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Partner
TCA##
Press [Enter] twice 3. Explain promotion determination Point out the following information: Promotion determination for article R100054 in field Promotion:
Promotion number: 200000001
Promotional price (net price): 199 USD Go to the conditions for the item of article R100054 ... Select the item Goto Item Conditions ... … and point out the two list prices (sales price and promotion sales price) Slide Schedule Line Category for Third-Party Order Processing Demonstration of purchase order from order 10 min 1. Explain how third-party order processing is controlled in the order ( TA VA03) Sales Sales order Order Display Enter the order number [Enter] Explain the item categories and their meanings: R100054 TAN Standard item R100060 TAS Third-party item R100061 TAS Third-party item Show the following in tab page Procurement: Sched. line cat. Delivery requirement SLCat DelReq R100054 CV Yes (011) R100060 CS No R100061 CS No Explain that the distribution center delivers article R100054 with item category TAN and schedule line category CV. Explain that R100060 and R100061 trigger an order from an external vendor, which is controlled by item category TAS and schedule line category CS. 2. Check the purchase requisition Environment Status overview [Expand completely] 26.06.2002 Page 96
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Point out the following information: Delivery status (total order) Not delivered Order confirmation status Not yet confirmed The item status overview already contains the purchase requisition numbers for two articles; Write down these numbers in the process overview Note: Show the additional process in a separate session so you can always go back and check the order. 3. Convert the purchase requisition into a purchase order ( TA ME21N) [Back] to the SAP Easy Access menu Purchasing Purchase order Purchase Order Create Vendor/Supplying Site Known [Document overview on] [Selection variant] Select purchase requisitions: Site R300 Purchasing organization R300 Purchasing group R30 [Execute] Select purchase requisition in the document overview. [Copy] Purchase order Save 4. Check purchase order (TA ME22N) Purchase order Change
Purchase order Other purch. order Enter purchase order number from above [Enter] Item details subscreen, tab page Delivery: Do not set the GR indicator in the GR/InvVer control field group, because no goods receipt is expected in the distribution center, since the merchandise is sent direct to the customer. Show that the customer’s delivery address appears in the purchase order: Tab page Delivery address
5. Print output, display messages Goto Print preview Point out the delivery address and the customer address (Please deliver to ...). 6. Check order (TA VA03) Go back to the session containing the order display: Environment Status overview 26.06.2002 Page 97
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
[Expand completely] Point out the following information: Delivery status (total order) Not delivered Order confirmation status Not yet confirmed But you can now see the PO number The item status overview now also contains the purchase order numbers for two articles; Write down these numbers in the process overview After slide Schedule Line Category for Third-Party Order Processing Promotion order, Purchase order exercises 20 min
26.06.2002 Page 98
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
Topic: Settlement of a Third-Party Transaction After slide Billing: Integration With Financial Accounting Demonstration of invoice verification, billing document 20 min Briefly explain the scenario: The vendor has delivered the correct articles to the customer and sends the invoice for the articles. 1. Create the vendor invoice (TA MIRO) Purchasing Logistics invoice verification Document creation Add incoming invoice Invoice date Today Company code R300 Gross invoice amount 2500 Purchasing document Purchase order number [Enter] Invoice document Post 2. Check the order Go back to the session containing the order display: Environment Status overview [Expand completely] Point out the following information: Overall status: Not billed
Delivery status (total order) Not delivered Order confirmation status All items confirmed Invoice receipt status Complete invoice received Goods receipt status No goods receipt(!) The item status overview now also contains the invoice document numbers for two articles; Write down these numbers in the process overview
3. Issuing the invoice for the customer (customer billing document, TA VF04) Point out that you will now use the billing due list (mass processing) for demonstration purposes, even though you are only generating one invoice for one customer. Sales Billing Billing document Edit billing due list Billing date to Sold-to party Order-related
Today TCA##
Billing document Display billing list Billing document Save 26.06.2002 Page 99
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
4. Display billing document (TA VF03) Billing document Display Briefly show the Financial Accounting documents that are the follow-on documents of the billing document. 5. Check order (TA VA03) Go back to the session containing the order display: Environment Status overview [Expand completely] Point out the following information: Overall status: Not delivered
Delivery status (total order) Not delivered Order-related billing status Fully billed The item status overview now also contains the billing document number for two articles; Write down the number in the process overview Point out the following information: R100054 has not been billed yet, because this article has not been delivered to the customer yet. To be able to bill for article R100054, you need to run the following shipping activities (in the same way as exercise 3-2-4): - Create a delivery - Create a transfer order - Confirm a transfer order - Post goods issue After slide Document Flow in R/3 Invoice verification, Billing exercises 20 min
26.06.2002 Page 100
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
APPENDIX: Accompanying Overheads for Demonstration I) Requirements Planning and Warehouse Deliveries: Planning Run and Invoice Verification Demonstrations Requirements planning (MRP Run)
Purchase requisition
Purchase requisition
1000............
1000............
TA03##
310 PC
TA04##
580 PC Manually
Purchase order
Purchase order
45000............
45000............
TA03## TA04##
15 CAR 58 CAR
TA03## TA04##
25 CAR 100 CAR
Collective number
000000.......... Shipping Notification
1800000..........
Ext. ID 2304##
Rough goods receipt
1870000..........
Delivery note no. 4711##
Goods receipt
5000000.......... TA04##
1 CAR returns
Invoice
510560....../2000
26.06.2002 Page 101
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
II) Sales and Delivery to Stores: Replenishment and Merchandise Distribution Demonstrations Replenishment Manually Warehouse Order (T2## with T7##)
Warehouse Order (T1## with T7##)
45000............
45000............
R100000 R100008
143 CAR 100 CRT
R100000 R100008
80 CAR 40 CRT
Adjustment
Collective PO (T7## with R3000)
45000............ R100000 R100008
223 CAR 140 CRT
Goods receipt
5000000......... Delivery
Delivery
800......... 800.........
800.........
Goods issue
Goods issue
26.06.2002 Page 102
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
III) From Planning to Execution: Demonstrations of Planning and Goods Issue Processes Planning for store group 50 + ## TA11## 1200 PC TA12## 1200 PC Allocation table
....... Store group 50 + ## rel. proportional factor: 1:1 (T1## 600 PC T2## 600 PC) Warehouse Order (T1## and T2## with T7##)
45000......... TA11## TA11## TA12## TA12##
50 CAR 50 CAR 600 PC 600 PC
T1## T2## T1## T2##
Delivery for T1##
Delivery for T2##
8000.........
8000.........
Planned GI date: ..................
Planned GI date: ..................
Transfer order
Transfer order
0000.........
0000.........
Confirmation
Goods issue
Confirmation
Goods issue
26.06.2002 Page 103
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
IV) Analysis and Promotions: Demonstrations of Promotion Planning and Goods Issue Processes Promotion
20000............ TA11## TA12##
1440 PC 300 PC
Allocation table
....... Site group BGAK## Allocation rule ARAK## (T1## 2 quotas T2## 1 quota) Warehouse Order (T1## and T2## with T7##)
45000......... TA11## TA11## TA12## TA12##
80 CAR 40 CAR 200 PC 100 PC
T1## T2## T1## T2##
Delivery for T1##
Delivery for T2##
8000.........
8000.........
Planned GI date: ..................
Planned GI date: ..................
Transfer order
Transfer order
0000.........
0000.........
Confirmation
Goods issue
Goods issue
26.06.2002 Page 104
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
V) Warehouse Returns: Store Returns Demonstration Stock transport order (T1## to T7##)
45000............ TA06##001 TA06##002
6 PC 4 PC
Returns Returns
Delivery (T7## to T1##)
8000............ TA06##001 TA06##002
6 PC 4 PC
Returns Returns
Negative store goods receipt
45000............ TA06##001 TA06##002
6 PC 4 PC
minus minus
Negative distribution center goods issue TA06##001 TA06##002
6 PC 4 PC
minus minus
26.06.2002 Page 105
SAP AG
IRT100 Retail Process Overview APPENDIX: Accompanying Overheads for Demonstration
VI) Selling To Customers on The Internet: Sales Order to Billing Document Demonstrations Sales order
............ R100054 R100060 R100061
50 PC 20 PC 20 PC
TAN TAS TAS
automatic
Purchase requisition (DC at external vendor)
1000............ R100060 R100061
20 PC 20 PC
Purchase order
45000.........
Invoice
510560.........
Billing document
9001.........
26.06.2002 Page 106
View more...
Comments
