720 Scen Overview en US

8/3/2019 720 Scen Overview en US

http://slidepdf.com/reader/full/720-scen-overview-en-us 1/18

Plan-driven Procurement

SAP Best Practices for Retail (US)

SAP Best Practices



Scenario Overview ² 1

Purpose

With Operational Assortment Planning and Control (OAPC), articles and

quantities will be specified for ordering, both for delivery to the stores and put

away quantities for the distribution center.

Benefits

Permanent matching with the target values from the assortment plan

The result of the whole planning process is the purchasing list

with articles to be ordered

Key process flows covered

Determination of the product mix for the different store cluster

Determination of the store allocation; initial buy, flow through, put away

Quantity planning and prepack definition at color and sizes

(one or two) level

Purpose and Benefits:



Scenario Overview ² 2

Required SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows Retail Seasonal Purchaser

Retail Seasonal Purchaser ± Power User

Retail Assortment Planner

SAP Applications Required:



Process Flow Diagram

Version 1 ± Retail Seasonal Procurement

R e t a i l S e a s o n a l P u

r c h a s e r

Release ReportExecution

Display Master Data for PlannedArticles for the

fashion process

Synchronizebetween PO andallocation table

OAPC ± CreatePurchasing List

ReleasePurchasing List

item

Add new order listitem

Create GroupedPurchase Order

Document

Allocation table listSubsequentProcessing

E v e n t

Generate theallocation table

(based on detailedassortment

planning

Ungrouping anitem in a grouped

purchase order document

Create PurchaseOrder Document

OTB-Monitoring OTB-ProcurementCreate Purchase

Order: positivOTB-Check

Create PurchaseOrder: negativ

OTB-CheckOTB-Procurement

R e t a i l

S e a s o n a l

P u r c h a s e r

± P o w e r

U s e r Special Release -

Accepting

MAP



Process Flow Diagram

Version 1 ± Retail Seasonal Procurement

OAPC

R e t a i l

S e a s o n a l

P u r c h a s e r

DisplayTransportation

Times

R e t a i l

A s s o r t m e n t

P l a n n e r

Create a generalassortment

DisplayTransportation

Chain

Create a layoutmodule versionand assigning a

fixture

Assign articles tolayout module

verison procedure

Assign assortmentusers to the

assortment (layoutmodule)

Release the layoutmodule version

E v e n t

LayoutWorkbench

Purchasing



Overview

Scenario ² Seasonal ProcurementThis scenario is made up of several building blocks containing the preconfiguration requiredfor the Seasonal Procurement scenario. Building blocks can help you to implement thesolution and put into production quickly.

To illustrate the scenario presented in this overview document, the business view, the

interaction view, and the component view, provide three different perspectives on thebusiness scenario.

Business View

The business view shows the business partners participating in the Seasonal Procurementscenario, the entire scope of the business processes, and the benefits for the parties involved.

Component View

The component view shows the processes and technical components that are involved in theSeasonal Procurement scenario.



Operational assortment planning and control

(OAPC)

Features (1/2)

Determination of the product mix for the different store cluster

Permanent matching with the target values from the assortment

plan

Determination of the store allocation

Initial Buy/Flow Through

Put away

Quantity planning and prepack definition at color and sizes

(one or two) level

The result of the whole planning process is the purchasing list

with articles to be ordered



Operational assortment planning and control

(OAPC)

Features (2/2)

Target values are shown and aligned (e.g. sales volume)

Usage of planned articles (article shells), existing articles, pricat

Include colors, plan colors

Up to 3 characteristics can be used (e.g. size, length, width)

Usage of quota-scales

Scheduling

Rough calculation of prices

Transfer of planned data to the purchasing processes

Monitoring of the follow up processes



Operational assortment planning

and control - process

masterdata allocation

Purchase order

management

BW

planning of the articles that should beavailable in the stores

planning of article shells

planning of the quantities

quantity details at color/size level (prepacks)

prepack-assignment

detailled planning of articles

R e p o r t s

OAPC

targets from merchandise plan capacity plan

R e p o r t s

strategic assortment planning

pre-agedprocesses

ERP



Seasonal Procurement

Features

Efficient and user-friendly workplace for a purchaser with a

widespread work area

Integration with planning process

Fast data entry for further line items and the possibility, to order new article without complex article creation

Integration of contract processes

Calculation of timelines for individual articles

Control of conditions, messages, additionals, order dates «

The operative purchasing processes is linked to the planned

budgets (OTB buckets) coming out of the merchandise planning



Seasonal Procurement: Purchase order

handling

Order monitoring LogisticAllocation

Planned purchasing list items

Order Manager (Workbench)

ERPGeneration Order List

Update

Order ListGrouped

order documentPurchase order

OTB CHECK



OTB-Check

Features

Budget planning on different key figures

Budget control in season

Special Release



ERP

OTB Procurement (Workbench)

Workflow

to supervisors

Deadline change

Quantity change

Purchase orders with

insufficient OTB

Price change

Purchase

Order changeSpecial

Release

OTB Check NOT successful!

OTB: Overview of OTB Procurement



Purchase order monitoring (Scheduling)

Features

Tracking and tracing from order date and move time

Follow up activity (deadline shift,

reminder, cancellation)

Means of transport change within active merchandise control

Order monitoring until goods receipt



Purchase order monitoring (Scheduling)

ERP

Supplier performance

trackingOrganisationVendor compliance

Order Monitoring (Workbench)

Purchase Order

Scheduling

Monitoring of scheduling

target/actualcomparison(documents)

Actingview

Reaction of schedulevariance(Status)

Date shift Reminder Cancellation threat Cancellation

Reactingview



Allocation

Features

Based on operational assortment planning and procurement, the

goods can be allocated per color and size on a quantity basis to

the stores

Initial buy allocation based e.g. on historical sales data

Assignment to the follow-on logistics processes like delivery creation,

goods issue etc.

Allocation is used at head office for planning, controlling and

monitoring site (stores, DC) supplies.

Allocation can be used to:

Allocate articles to sites for the first time;

Allocate promotional merchandise;

Allocate stock;

Allocate imported merchandise that has been procured centrally.



Integration of Allocation, purchase order generation and

operational planning

Order Processing

Order List

Grouped Order Document

OTB Check

Purchase Order creation /

maintenance

Operational Assortment Planning and Control

Purchasing List

preliminary planning processes

Status updateStatus update

Line Itemsof Purchasing List

Generation of AT on basisof PO´s with reference

to Purchasing List

Allocation Table

Allocation

Monitoring of

Procurement dates

Scheduling

f o r w a r d s

b a ck w ar d s

Synchronisation



Copyright 2008 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior

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

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z,System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ® , World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may bechanged by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, tex t, graphics, links, or other items contained within this

material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

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

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

720 Scen Overview en US

Documents

Transcript of 720 Scen Overview en US