scm scen overview en br

8/6/2019 SCM Scen Overview en BR

1/38

ECR Compliant

Procurement Processes

SAP Best Practices for Retail(Brazil)

SAP Best Practices


2/38

Scenario Overview - 1

Version 1 - Buyer-Managed Inventory

Purpose

The scenarios presented in SAP Best Practices for Retail deal with the retailer`s

procurement processes, which include buyer-managed inventory and vendor-

managed inventory.

Benefits

efficient merchandise control which fulfills the requirements of ECR-compliantprocurement processes

more efficient communication between retailer and manufacturer/vendor

Key process flows covered Process purchase order in the retailer system

Process sales order in the vendor system

Check purchase order confirmation in the retailer system Process delivery in the vendor system

Perform goods receipt with reference to shipping notice in the retailer system

Create billing document in the vendor system

Carry out invoice verification in the retailer system

Purpose and Benefits:


3/38


Version 2 - Vendor-Managed Inventory

Purpose

The scenarios presented in SAP Best Practices for Retail deal with the retailer`s

procurement processes, which include buyer-managed inventory and vendor-

managed inventory.

Benefits

efficient merchandise control which fulfills the requirements of ECR-compliantprocurement processes

more efficient communication between retailer and manufacturer/vendor

Key process flows covered

Transfer the stock data of the retailer to the manufacturer

Carry out replenishment planning with resulting sales order in the manufacturer

system Generate the purchase order automatically in the retailer system with a report to

the manufacturer

Purpose and Benefits:


4/38


Version 1 and Version 2

Required

SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows

Retail Purchaser

Manufacturer

SAPApplications Required:


5/38

Process Flow Diagram

Version 1 - Buyer-Managed Inventory

Create PurchaseOrder

Generation ofPurchase

Display BillingDocument

Perform GoodsReceipt withReference of

Shipping Notice

Create Sales Order Create DeliveryPicking and Postingof the Goods Issue

Create Invoice

Manufa

cturer

Retail

Purchaser

IDoc ORDERS

INVOIC

DESADV

IDoc ORDERSP


6/38

Process Flow Diagram

Version 2 - Vendor-Managed Inventory

Transfer the stockdata of the Retailerto the manufacturer

Display IDocORDCHG

Display IDocPROACT

Display receivedstock

ExecuteReplenishment

Display IDoc ORDSP

Manufa

cturer

Retail

Purchaser

Display Sales Order


7/38

ECR Compliant Procurement Processes

Introduction

Between Retailers and Manufacturer of the German textile and apparelindustry, cooperatively concepts within the framework of procurement,marketing and using of information and communication technology aredeveloped.

Between Retailers and Manufacturer of the German textile and apparel

industry, cooperatively concepts within the framework of procurement,marketing and using of information and communication technology aredeveloped.

Collaboration concepts, like Efficient Consumer Response (ECR), earn onimportance. The new technologies open small and middle comanies thepossibility to accomplish the structure change and also to reinforce theircompetitive strength.

Collaboration concepts, like Efficient Consumer Response (ECR), earn onimportance. The new technologies open small and middle comanies thepossibility to accomplish the structure change and also to reinforce theircompetitive strength.

SAP offers a software solution within the framework of the SAP BestPractices Version, which reflects the new requirements of ECR conformableprocurement processes.

SAP offers a software solution within the framework of the SAP BestPractices Version, which reflects the new requirements of ECR conformableprocurement processes.


8/38

ECR Compliant Procurement Processes

Introduction

With SAP software you have the possibility to build up the manufacturer andalso the retailer side. We will show you here the procurement processes onthe retailer side.

With SAP software you have the possibility to build up the manufacturer andalso the retailer side. We will show you here the procurement processes onthe retailer side.

The ECR conformable procurement processes embrace the price catalog, the

buyer managed inventory and also the vendor managed inventory.

The ECR conformable procurement processes embrace the price catalog, the

buyer managed inventory and also the vendor managed inventory.


9/38

Price catalog: PRICAT

PRICAT

Is an EANCOM standard message type

Area of master data

Enables pricing and catalog-related data for goods and services to be transferred from a

vendor to a buyer

Complete listing of all products

Notification of changes

Information relevant for all customers

Customer-specific information

Data supplied to a central article database


10/38

Price catalog: Supply of a data pool

Vendor Retailer

Master DataMaster Data

Data Pool

f. e. Sinfos

XIXI Inbound processingof PriceCatalogue Idoc

Inbound processing

of PriceCatalogue Idoc

BAPI/ALE

Generate of

PriceCatalogue Idocs

Generate of

PriceCatalogue Idocs

Sender Recipient

XIXI


11/38

Price catalog inbound: process flow

Simulation of IDoc

Inbound processing

Display Header Data

(catalog)

List of article

Adopt Profile

Process Price catalogmanual / automatical

Process not existing article data in the

Customer system (EANs) /

Creating article

Process available article data in the

customer system (EANs) /

Update of article


12/38


13/38

Price catalog inbound: preparation

q Preparation before catalog transfer

s Assignment of ILN to SAP vendor, purchasing group

s Assignment of merchandise categories to SAP merchandise categories (for

each ILN)

s Assignment of SAP merchandise categories to purchasing groups

q Workflow preparation

s Assignment of buyers (SAP users) to organizational units, to which the

relevant purchasing groups are assigned (transaction PFOM)


14/38

Price catalog inbound: accessing catalog

maintenance

Header data

q Set catalog status

s After processing, the catalog status is automatically set to 'processed'

s Catalog status can be manually set to 'closed'

q Set test indicator

q If you want to process the catalog you have to enter always the

purchasing group

q Price catalog could be processed manually or automatically


15/38

Price catalog inbound: accessing catalog

maintenance

List of article

q In the list of article you will find now the article (items) of the new

price catalogq Items are distributed among several views according to their status

q New items have no entra in the field article and you can find this

items in tabstrip to be processed (article can not be assigned)

and all entries


16/38

Price catalog inbound: assignment of EAN to

an article

q The assignment of EAN to an article occurs automatically when a

catalog is created (unique EAN)

q Manually in catalog maintenances Assigned article is stored in price catalog

s Can be entered at a later date

s If the EAN is not unique, all possible EANs are displayed

s For assignment, articles are also displayed with the vendor article

number from the catalogs New articles need template articles (proposed from the merchandise

category)


17/38

Price catalog inbound: transferring catalog

data to article data

Adopt profile

q The transfer of catalog data to article data could be done with an

adopt profileq The adopt profile enables the simultaneous display of catalog data

and article data

(or in the case of new data, the template article)

q Required data must be explicitly transferred from the catalog to the

article side, either manually or by using a transfer profileq Adopt profiles could be stored and used again

q The article fields can be edited


18/38

Price catalog inbound: assignment of EAN to

unit of measure

q Automatically

s By mapping the EANCOM packaging type to alternative unit of measure in the

converters During R/3-R/3 data interchange

q Manually in catalog maintenance

s Can be changed at a later date

q New units of measure must be explicitly transferred

s It is possible to transfer all units of measure from the catalog


19/38

Price catalog inbound: updating to article

q What can be updated:

s Basic data

s

Textss BOMs (new)

q What cannot be updated:

s Characteristics

s Generic article/prepack

s BOM changess Conditions

s Material


20/38

Buyer managed inventory (BMI)

SAP ERP offers for communication the possibility of the generation of socalled IDocs. An IDoc is an electronic document in SAP standard format.

SAP ERP offers for communication the possibility of the generation of socalled IDocs. An IDoc is an electronic document in SAP standard format.

SAP offers furthermore the possibility, with help of XI (open integrationtechnology of SAP) to process all notification formats (like SEDAS, UN,EDIFACT, XML ).

SAP offers furthermore the possibility, with help of XI (open integrationtechnology of SAP) to process all notification formats (like SEDAS, UN,EDIFACT, XML ).

For the more efficient communication between the retailer and thevendor, documents like purchase orders, order confirmations, deliverynotifications and invoices are relayed electronically.


21/38

Scenario BMI: process flow


22/38

Scenario BMI: process flow


23/38

BMI: process flow

Lieferant

RetailerRetailer

1. Purchase order

Filiale Verteilzentrum2. PO confirmation

3. Shipping notif.

4. InvoiceStore DC

Manufacturer


24/38

BMI: purchase order handling

Create

PurchaseOrder

Check PO

confirmation

Retailer

Generation ofIDoc

ORDRSP

ORDERS

Create

SalesOrder

Generate PO

confirmation

Manufacturer


25/38

BMI: goods processing

DESADVShippingnotification

Post goods

receipt

Retailer

CreateDeliveries

Articles to

Retailer

Manufacturer

EDI-Interface


26/38


27/38

BMI: conclusion

Retailer system IDoc IDoc Vendor system

Create purchase order ORDERS

Customer order is created

ORDRSP Process customer order

Order is entered into pur-chase order.

DESADV Create delivery

Delivery note is created

Process goods receipt for

delivery note

INVOIC Create invoice

Create incoming invoice,invoice ferification takes

place


28/38

Vendor managed inventory (VMI)

Vendor managed inventory means, that the manufacturer will make thedisposition of his products (as a service for the retailer), which arerepresented in the stores of the retailer

Vendor managed inventory means, that the manufacturer will make thedisposition of his products (as a service for the retailer), which arerepresented in the stores of the retailer

This requires, that the manufacturer knows the actual stock and sales data ofhis products in the retailer stores. The manufacturer could then make aprognosis of the sales data of his products and also an effectivesreplenishment would be possible.

This requires, that the manufacturer knows the actual stock and sales data ofhis products in the retailer stores. The manufacturer could then make aprognosis of the sales data of his products and also an effectivesreplenishment would be possible.


29/38

VMI: process flow


30/38

VMI: transfer of stock data

Manufacturer

Maintains stock data of his

products at the retailer site

Tracks sales history

Retailer Sends stock and sales

data at a regular basis

to the manufacturer

Stock Data


31/38

VMI: transfer of stock and sales data

Sending of

stock andsales data

Retailer

Generation of IDoc Actual Salesdata will be

updated in the

information

structure S130

Stock data

will be written

in the table

WRPT

Manufacturer

PROACT


32/38

VMI: sending stock and sales data to the

manufacturer

Done by report for selected supplier and stores

interactiv or in batch processing

Generation of IDoc PROACT

Article and data selection is controlled by profiles in the vendor master

stock and on-order quantity sales history


33/38

VMI: planning of replenishement

Manufacturer

calculates replenishment

requirements

generates sales order

Order Response


34/38

VMI: planning of replenishment

Retailer

Generation of IDoc

ViareplenishmentP

lanning acustomer orderwill be created

Manufacturer

ORDRSP

Purchase order

will becreated


35/38

VMI: Planning of replenishment

Manufacturer updates sales order with PO

number from retailer system

Order changes

VMI l i f l i h t


36/38

VMI: planning of replenishment

Retailer

Generation of IDoc

Purchase order

number from theretailer will be

insert into the

customer order

Manufacturer

ORDCHG

Purchase

order changenotice will be

created


37/38

Legend

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts PayableClerk or Sales Representative. This band can also

identify an organization unit or group, rather than aspecific role.

The other process flow symbols in this table go intothese rows. You have as many rows as required to coverall of the roles in the scenario.

Role band containstasks common to

that role.

External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.

Flow line (solid): Line indicates the normal sequence ofsteps 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 tasksin a scenarioprocess or a non-step event

Business Activity / Event: Identifies an action that eitherleads into or out of the scenario, or an outside Processthat happens during the scenario

Does notcorrespond to a taskstep in thedocument

Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario

Corresponds to atask step in thedocument

Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.


Sub-Process Reference: If the scenario references anotherscenario in part, put the scenario number, name, and thestep numbers from that scenario here


Process Decision: Identifies a decision / branching point,signifying a choice to be made by the end user. Linesrepresent different choices emerging from different partsof the diamond.

Does not usuallycorrespond to a taskstep in thedocument; Reflectsa choice to be madeafter step execution

Symbol Description Usage Comments

To next / From last Diagram: Leads tothe next / previous page of the

Diagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines

Financial Actuals: Indicates a financialposting document


Budget Planning: Indicates a budgetplanning document


Manual Process: Covers a task that ismanually done

Does not generally correspond to atask step in a document; instead, it isused to reflect a task that is manuallyperformed, such as unloading a truckin the warehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond to atask step in a document; instead, thisshape reflects data coming from anexternal source; this step does nothave any incoming flow lines

System Pass / Fail Decision: This blockcovers an automatic decision made bythe software

Does not generally correspond to atask step in the document; instead it isused to reflect an automatic decisionby the system that is made after a stephas been executed.

External

toSAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

ProcessDecision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProcess

ExistingVersion /

Data

SystemPass/FailDecision

C i ht 2009 SAP AG


38/38

Copyright 2009 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 PowerPointare registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,

z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,

PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere,

Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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 MultiWinare 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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services

mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP

company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product

specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without

representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are

those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

scm scen overview en br

Documents