Presentation is loading. Please wait.

Presentation is loading. Please wait.

In-Store Merchandise and Inventory Management

Similar presentations


Presentation on theme: "In-Store Merchandise and Inventory Management"— Presentation transcript:

1 In-Store Merchandise and Inventory Management
SAP Best Practices for Retail (RU)

2 Purpose, Benefits, and Key Process Steps
These components of the SAP SAP ECC Retail System are used in the store. Together with the central SAP ECC, they form a complete retailing system. Procurement, goods movement and sales postings make up the mass business of a store. With In-Store Merchandise and Inventory Management, these postings can be executed by employees directly in the store. Benefits Low running costs and hardware requirements Use of standard technologies Intuitive, easy-to-use user interface Business processes designed for store needs Integration into central merchandising & accounting system

3 Purpose, Benefits, and Key Process Steps
Purchasing Store to store stock transfer Physical inventory count Goods movements Goods receipt Inventory Lookup

4 Required SAP Applications and Company Roles
SAP enhancement package 5 for SAP ERP 6.0 Company Roles Retail Masterdata Manager Retail Store Manager Retail Warehouse Specialist Retail Promotion Planner Retail Buyer Purchaser Billing Administrator

5 In-store Merchandise and Inventory Management
Process Flow Diagram In-store Merchandise and Inventory Management Retail Sales Person Create stock transport order Change delivery Retail Store Manager Create Delivery for store order Retail Walrehouse Specialist Post goods issue Purchaser Create Store Order Store order (direct) External Purchase order Return purchase order Post goods return Create store order (stock transfer) Store order & vendor determined by system Stock transfer purchase order

6 In-store Merchandise and Inventory Management
Process Flow Diagram In-store Merchandise and Inventory Management Retail Store Manager Create goods receipt for PO Stock transfer Misc. goods movement Sales order Create goods receipt for delivery With reference (Article document) Initial entry of inventory data Create goods receipt without reference documents With reference (PO) Create document in in-store merchandise & inventory management Difference values - purchasing Create goods receipt with reference documents Create return delivery without reference doc. Entering count Editing differences

7 In-Store Merchandise and Inventory management - Landscape
IDES Smart Retailer Inc. at night: article and price EAN Sales data cashier statistics converter MIM vendor POS Server purchasing activities inventory management customer order management promotion

8 Purchasing process of the store
Vendor Head Office DC Purchase requisition, purchase or delivery delivery picking goods issue invoice Order data

9 Planning by visual inspection
Replenishment in MIM Head Office Purchase requisition Replenishment run SAP Retail Store Quantity Quantity proposal Stock Open receipts Material 10,00 10,000 0,000 100,000 R100013 9,000 90,000 R100014 8,00 8,000 R100015 Store Planning by visual inspection

10 Goods receipt in MIM Head Office Vendor Store delivery delivery
goods receipt date Store delivery DC delivery picking goods issue invoice

11 Goods movements in the store
normal stock promotion stock store stock store 2 xxx xxx Store Head Office Other Store

12 Inventory in MIM counting articles Store Head Office inventory result
physical inventory count scanner inventory count inventory book inventory xxx inventory result = ? Store Head Office xxx

13 Sales process delivery sales order order Store Head Office Vendor DC

14 Promotion information
Price calculation volume-rebate arrangements conditions order processing goods issue inventory management goods receipt order requirements planning POS incoming outgoing promotion free-goods discount assortments catalog processing additional coupons bonus buy Business Information Warehouse external systems

15 Legend Symbol Description Usage Comments Symbol Description
Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role. The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario. Role band contains tasks common to that role. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario. Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow. Connects two tasks in a scenario process or a non-step event Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario Does not correspond to a task step in the document Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario Corresponds to a task step in the document Process Reference: If the scenario references another scenario in total, put the scenario number and name here. Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond. Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution Symbol Description Usage Comments To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page Hardcopy / Document: Identifies a printed document, report, or form Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Financial Actuals: Indicates a financial posting document Budget Planning: Indicates a budget planning document Manual Process: Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed. Diagram Connection <Function> External to SAP Hardcopy / Document Financial Actuals Business Activity / Event Budget Planning Unit Process Manual Process Process Reference Sub-Process Reference Existing Version / Data Process Decision System Pass/Fail Decision

16


Download ppt "In-Store Merchandise and Inventory Management"

Similar presentations


Ads by Google