EXP - 0004 Sales & Delivery Store

0
Sales and Delivery to Stores
Contents:
 Process overview
 Store sales
 Uploading POS data and generating warehouse orders
 Using collective purchase orders to procure merchandise
 Merchandise delivery and distribution in the distribution center
 Delivery of merchandise in the store
 Planned requirements for perishables
 Unit summary
 SAP AG 1999
© SAP AG IRT100 4-1

0.2
Sales and Delivery to Stores:
Unit Objectives
At the conclusion of this unit, you will be able to:

 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 concepts behind the functions
replenishment, store orders and planned requirements
for perishables
 List the most important steps for generating a collective
purchase order
 List the advantages of using cross docking and flow
through
 SAP AG 1999

0.3
Overview Diagram
Sales to customers
via Internet
Requirements planning
Vendor
Vendor and warehouse deliveries Customer
Customer
Warehouse
Sales and Delivery returns
to Stores
Distribution
Distribution center
center
Central
SAP Retail
System
Analysis and
promotions Store
Store
Basic Concepts
Consumer
Consumer
 SAP AG 1999

0.4
Sales and Delivery to Stores: Business Scenario
 A customer buys an article in a store.

 A purchase order is generated for the article that
has just been sold and placed with a warehouse -
this is done by uploading the sales data and using
the replenishment/store order functions.
 Different articles are procured externally from
different vendors before they are then delivered to
the warehouse through which they are moved
using cross docking.
 The article is delivered to the store from the
warehouse.
 A different procedure is used for procuring
perishables.
 SAP AG 1999

0.5
Sales and Delivery to Stores: Process Overview
Collective
Collective PO
PO Generation
Generation of
of
store
store orders
orders
4 3 Sales
Sales data
data upload
upload
5
Store
Store sales
sales
Delivery
2
Delivery and
and GR
GR
in distribution
in distribution 6
center
center 7 1
Cross
Cross docking
docking and
and
goods
goods issues
issues
Delivery
Delivery and
and GR
GR
Merchandise flow
in
in store
store
Information flow
 SAP AG 1999

0.6
Payment Processing at POS
1
Store sales
Smart
Smart
Store - New York

Cash register 12 02/29/2000
5 Yogurt 3.45
2 Margarine 2.38
1 3-pack Pizza 9.79
Fresh meat 26.87
--------
42.49
Thank you for shopping with us.
 SAP AG 1999

0.7
Store Connection to an SAP Retail System
2
Sales data upload
SAP Retail
ALE / EDI Intermediate doc. (IDoc)
Conversion
Head
Head office
office
Communication
SAP Retail
(Remote
SRS access)
POS server
Store
Store
 SAP AG 1999
 Most store retailing systems can be linked to SAP Retail, for example:
 POS server with retailing functions
 In-store retailing systems
 The in-store systems are linked to SAP Retail as follows:
 Using a certified converter or communication interface combined with the POS interface in SAP
Retail (as recommended by SAP)
 Using a customer-specific converter / communication interface combined with EDI and
SAP IDocs (Intermediate Documents)
 Some data can be downloaded directly to the retailing systems using SAP Standard ALE. SAP Retail
applications allow you to transfer messages with EDI as standard.
 Access to the central SAP Retail system can be provided using a remote connection via a store
terminal.

0.8
POS Inbound Processing
2
Sales data upload
POS
Stock update
Inbound
Head
Head office
office processing
POS interface MM
Replenishment- inventory
based management
inventory
Electronic management
transfer of POS data
(POS converter)
Transfer of
payment data to
POS server financial accounting
(for example, credit cards,
customer cards,
cash sales)
POS
sales
Store
Store
 SAP AG 1999
 The sales entered at the store POS server are sent to the POS interface in the central SAP Retail
System using a POS converter.
 Here, POS inbound processing is run.
 The stocks of the articles sold in the stores are updated at POS inbound processing. According to
the replenishment procedure chosen, POS inbound processing is done in replenishment-based
inventory management or in material management based inventory management.
 Additionally, payment data (for example, credit card data, payment card data, cash sales) that has
been gathered is forwarded to Financial Accounting.

0.9
Replenishment: Standard Procedure
3
Generation of
Trigger replenishment planning for store orders
• Stores
• Planning horizon
Read stock MM
inventory
Calculation per article
management
Calculate expected issues and
receipts LIS ATP server
S130
Expected Reorder point

stock
Target stock
Calculate replenishment
requirements - expect. stock
Replenishment
requirements
Call store order
Warehouse order Replenishment

quantity
 SAP AG 1999
 Procurement in the replenishment process can be triggered online and in the background. If
replenishement is to be run online, users enter the store (or store group) for which replenishment is to
be run as well as an approximate procurement time for the merchandise (planning horizon).
 In the standard procedure, the current stock for all the relevant articles is read from MM inventory
management as well as the expected issues and receipts within the planning horizon. The system
uses info structure S130 for forecasting the issues and the ATP (available to promise) server for
calculating receipts. The following equation can be used for calculating the stock that is to be
expected at the end of the planning horizon:
expected stock = current stock + expected receipts - expected issues.
 If the expected stock is less than the target stock and the reorder point that has been calculated for
the relevant store and article, the system then uses the following equation to calculate the
replenishment requirement:
replenishment requirement = target stock - expected stock
 The resulting quantity is then sent to the Store order function. After supply sources have been
determined and purchase order quantities optimized (for calculating the actual replenishment
quantity based on the replenishment requirement), a warehouse order is generated by the
replenishment quantity.

0.10
Replenishment: Simplified Procedure
3
Generation of
Trigger replenishment planning for store orders
• Stores
• Planning horizon
Replenishment-
Read stock based
inventory
Calculation per article
management
Post anticipated goods

receipts
Current
stock Reorder point
Target stock
Calculate replenishment
requirements - current stock
Replenishment
requirements
Call store order
Warehouse order Replenishment

quantity
 SAP AG 1999
 Replenishment is triggered in the same way for both the simplified procedure and in the standard
procedure.
 In the simplified procedure, the current stock for all relevant articles is read out of replenishment-
based inventory management. In the simplified procedure, the expected stock is set as being equal to
current stock.
 Replenishment requirements and replenishment quantities are calculated in the same way as in the
standard replenishment procedure.
 In the simplified procedure, only the expected goods receipts are posted in replenishment-based
inventory management

0.11
Creating a Collective Purchase Order
4
Collective PO
Selection
Selection
Warehouse order
45..
Warehouse order Purchase order 45..
Vendor DC: R300order
45..
Warehouse
Distribution center Vendor: R3001
Vendor DC: R300
45.. Recipient
Vendor DC: R300 Vendor
Articles
...
Procurement period
Schedule line interval
-------------------------------------------------
Process modes:
 Cross docking
Flow through
Putaway
Cross docking / flow through
Cross docking / putaway
Block of the processed

items for delivery-due list
 SAP AG 1999
 Collective purchase orders can be used to group customers’ requirements that exist as warehouse
orders or sales orders in your system, so that a single order can be placed with your vendor.
 When creating collective purchase orders, you can enter criteria so that schedule lines for issue
documents are taken into consideration. The following are possible criteria that you could define:
distribution center, recipient, relevant time period and issue document type. From the selected
articles, the system only takes those articles into consideration that have been assigned a processing
mode using the distribution profile, in the article master. Existing warehouse stock and open
purchase orders can be considered as merchandise that has already been procured.
 The system uses the settings that you make to select the relevant issue document items and their
schedule lines, and groups their quantities for each article and distribution centers into possible
collective order schedule lines. Possible collective PO items are then created using one or more
collective PO schedule lines.
 You can process possible collective PO items singularly in detail or using a worklist, and then make
changes as required. This is how you can, for example, assign supply sources or change the quantity
of collective PO schedule lines.
 When a collective PO has been created, items for transfer purchase orders are locked out of the
delivery-due list.

0.12
Processing by Vendor
5
Delivery and GR in
Purchase order
distribution center
45...
Vendor: R3001
Vendor
Vendor Head
Head office
office
Store Store Store Store

R311 R311 R312 R313
Distribution
Distribution center
center
 SAP AG 1999
 The units that have been created for each store by the vendor are delivered to the relevant
distribution center.

0.13
Merchandise Distribution: Cross Docking
6
Cross docking
goods issues
Goods receipt
High rack
storage
1 1 area
Distribution Picking
zone area
Cross docking Goods issue
 SAP AG 1999
 The merchandise arrives at goods receipt for the distribution center and posted to a cross docking
storage location. Deliveries are then generated, and picking is not required.
 In the case of non-mixed packages, the recipients may not always receive complete packages. It is
therefore possible that the vendor prepicks merchandise, thereby creating packages that contain
different articles.

0.14
6
Cross docking
goods issues
Goods receipt High rack

storage
area
2a Distribution
Picking area
zone
Cross docking
Goods issue
 SAP AG 1999
 Shipping units are not repacked between processing at goods receipt and goods issue in cross
docking.

0.15
6
Cross docking
goods issues
High rack
Goods receipt storage
area
Distribution
Picking area
zone

2b
 SAP AG 1999
 The shipping units are then passed to goods issues without any additional processing. The goods
issue is then posted for the deliveries that were generated previously.

0.16
From Distribution Center to Store
7
Delivery and GR in
store
Distribution
Distribution center
center
Store Store
R311 R312
Store
Store R311
R311
 SAP AG 1999
 The cross docking merchandise is sent to the stores together with additional articles.

0.17
Processing at Store GR
7
Delivery and GR in
store
POS Store goods receipt

Inbound
Head
Head office
office processing
Find or regenerate
reference documents
POS interface
Update
order development
Electronic
(POS converter) Error
and exception processing
triggered
Store retailing system if necessary
Create
goods receipt
Store
Store POS
POS monitor
monitor
 SAP AG 1999
 The delivery from the distribution center arrives at the store.

 Store goods receipt is one SAP Retail functionality with which a goods receipts created in a non-
SAP retailing system can be posted in a central SAP System. A prerequisite of this is that inventory
management is run for the relevant store in the central SAP Retail system.
 Store goods receipts are generally created and processed as follows:
 Goods receipts are created in the store: the merchandise that has been received is counted and
checked. The goods receipt items are assigned to the relevant reference documents (deliveries or
purchase orders) in the external retailing system. The data that is created here is then sent to the
central SAP Retail system in an IDoc via the POS converter.
 Inbound (IDoc) processing is done in the central SAP Retail system. A purchase order is found as
a reference document in the chain of processes described here (purchase orders can be regenerated
at a later date if additional data is delivered separately). The development of the purchase order
can be updated and error processing can be triggered using the POS Monitor. Exception handling
can also be triggered by the workflow.

0.18
Process Steps in Detail
Collective
Collective PO
PO Generation
Generation of
of
store
store orders
orders
Sales
Sales data
data upload
upload
Store
Store sales
sales
Delivery
Delivery and
and GR
GR
in distribution
in distribution
center
center
Cross
Cross docking
docking and
and
goods
goods issues
issues
Delivery
Delivery and
and GR
GR in
in
Merchandise flow store
store
Information flow
 SAP AG 1999

0.19
Sales: Prerequisites
Store sales
The following article master data must
be maintained in your system:
• Article number
• Merchandise 
category
• EAN
Head
Head office
office
• Retail price
• POS receipt texts Download master

data
The articles must be listed for the (POS outbound)
store.
The following store master data must

• POS outbound profile

Store
Store
 SAP AG 1999
 You can send the following SAP Retail business data to a store retailing system or an in-store POS
server using the POS outbound interface:
 Article master data
 Article retail prices
 EAN assignments
 Customer data
 Exchange rates
 Product data
 Taxes
 Merchandise categories
 Label data
 Physical inventory data
 Assortment lists

0.20
POS Inbound: Prerequisites
Sales data upload

Following store master data must
• POS inbound profile
What form of inventory Head

Head office
office
management is to be used?
How are sales, returns and Upload sales data

goods receipts to be posted (POS inbound)
(movement type) ?
How are sales to be billed ?
Control
Store
Store
 SAP AG 1999
 You can send the following business data to SAP Retail from store retailing systems or in-store POS
server using the POS inbound interface:
 Merchandise movement data
 Sales data (as on POS receipt)
 Sales data (aggregated)
 Payment types
 Financial transactions
 Cashier data
 Physical inventory data
 Changes made to article data/EAN assignments
 Prices and conditions
 Customer data

0.21
Store Order: Prerequisites
Generation of
Following article master data must store orders
MRP parameters Replenishment

• MRP type parameters
• Re-order point • Target stock
• Safety stock • Inventory management
Source of supply Replenishment /

store order
Following store master data must

• POS inbound profile Warehouse order
Where and how is merchandise to be ordered ? Purchase

requisition
How can the procurement process be optimized ?
Purchase order
Control
 SAP AG 1999
 Store orders can generate different types of documents according to the settings that have been
made in your system.
 Theses documents are normally:
 Purchase requisitions if the system could not clearly identify a vendor
 Purchase orders for procuring merchandise from an external vendor for a distribution center or
store
 Warehouse orders for procuring merchandise from a distribution center
 Store orders are used in the same way for both external customers and stores
 The following documents are exceptions but can be generated nonetheless:
 Purchase order copies if the store has placed an order directly with the vendor
 If there is not sufficient merchandise available in the DC to fulfill a warehouse order, the order
can be sent to different DCs (delivery sites for the store in question) or to a specific external
vendor (third-party purchase order).
 You can optimize procurement by:
 Running supply source determination without searching for an outline contract, by not searching
for the most cost-efficient supply source and by not using additional requirements planning
procedures (for example, allocation table quantities).

0.22
Replenishment: Inventory Management Types
Generation of
store orders
Replenishment-
based MM
inventory inventory
management management
• available stock only • different stock types

• only goods issues • all relevant merchandise
(and anticipated goods movements
receipts) • documents for
• no documents merchandise movements
Simplified procedure Standard procedure
Replenishment parameters
for article R100000, store R314
 Replenishment-based inventory man.

 Include goods issues only
 SAP AG 1999
 Replenishment gives you the option of accessing detailed MM inventory management or a

simplified form of replenishment-based inventory management that reduces the necessary level of
maintenance and offers improved performance.
Replenishment-based inventory management also enables you to use inventory management on an
article basis for articles that can normally only be created on a merchandise category level in MM
inventory management for the relevant stores.
 Two procedures are available when running replenishment: the standard procedure and the
simplified procedure. The simplified procedure has been conceived for a simplified system
environment; it is based solely on the sold quantities recorded at POS and can therefore be used
without involving additional goods movements.
The simplified procedure can only be used in conjunction with replenishment-based inventory
management. The standard procedure should only be used with MM inventory management.
 To run replenishment for an article in a store, the article master (store logistics view) must contain
master data for requirements planning and replenishment. The reorder point is only used in the
standard procedure.
To choose between the standard procedure and the simplified procedure, use the switch Include
goods issues only. Use the Replenishment-based IM switch to choose the type of inventory
management that you wish to use.

0.23
Replenishment: Creating Target Stock
Generation of
store orders
Replenishment requirement = target stock - expected stock
Manually Automatically
• Create target stock • Create forecast data in
manually in the the replenishment
replenishment master data
master
data • Run forecast
today
400
300
200
100 238
Replenishment master data for article R100002, merchandise category R1122

Customer Max. targ. Target Safety Max. targ. ...
stock stock ... stock stock
R312 300
R310 500 288 + 50 100
 SAP AG 1999
 The target stock used for calculating the replenishment requirement of an article in a store (or for a
customer) can be maintained in two ways:
 Manually
A figure is entered in the system as the target stock in the master data for replenishment for the
article and store in question (or the relevant customer) - the figure that is entered is based on
previous experience.
 Using forecasting
To use this procedure you must first enter the requirements planning, forecasting and
replenishment paramters for the article and store (or customer) in question in the article master
data (store logistics view). When this is complete, the consumption forecast can be run. Here, the
system automatically calculates the total consumption for the periods that are to be included in the
forecasting proceure, and then increases this figure by the safety stock that has been defined for
the relevant article and stoire (or customer). The end figure from this calculation is then used as
the target stock. A minimum and maximum target stock figure limits this value from undercutting
or exceeding certain levels.
If forecasted data is used to define the target stock, it is recommended that this be done at regular
intervals (for example, every four weeks).

0.24
Store Order: Creation and Processing
Generation of
store orders
POS Store order
Inbound
Head
Head office
office processing
• Create additional order data
• Find source of supply
• Optimize order quantities
POS interface • ...
Electronic
(POS converter) Warehouse order
Store
Store retailing
retailing
system
system Purchase
requisition
Create Purchase order

requirement
and
Store
Store order data
 SAP AG 1999
 A store order is an SAP Retail functionality in which requirements created in a non-SAP retailing
system can be posted in a central SAP Retail system and used for further processing.
 Store orders can be entered directly in SAP Retail (online processing) or they can be entered in a
distributed retailing system first before they are then sent to SAP Retail using the POS interface
(offline processing). IDocs are used for exchanging data. The data from the distributed retailing
system is stored in the IDoc and then sent to the SAP Retail system where it undergoes further
processing.
In the SAP Retail system, inbound processing is run for the IDoc. A store order is generated at this
stage and the following functions can be run:
Supply source determination Purchase order copy
Quantity optimizing Sourcing
Order data enhancement Purchase order check
 Orders generated using Replenishment, Requirements planning for perishables, Additionals,
Automatic load building, Investment Buying and Purchase order split are sent to the dispatcher
before being sent to store order processing.

0.25
Supply Source Determination
Quota Generation of
arrangements store orders
60% 40%
Source of
Vendor
Vendor 11 Vendor
Vendor 22 supply
Find external supply sources

only using
• Outline agreements
• Purchasing data
• Regular vendors
Source list Find internal supply sources
Source list
only using
• Stock transport
schedules
• Supplying site
Determine internal sources

Site
Site before external source or
vice-versa
 SAP AG 1999
 Possible supply sources are defined by the system with the following priority and then displayed on
the screen as suggestions:
 The system checks if a quota arrangement exists and if its period of validity actually covers the
delivery date stated in the purchase requisition. If a quota arrangement does exist, the system
calculates the vendor that should be used for procuring the article, using the quote arrangements
that have been defined for the vendor in question as the selection criterion.
 If no quota arrangement does exist, the system uses the source list to identify a suitable supply
source: if the source list contains neither a vendor nor an outline agreement item, the system
attempts to locate a contract or a scheduling agreement for the article in question. Any outline
agreements that exist for the article in question are suggested as possible supply sources.
 The Supply source field in the article master is analyzed if no supply source has been determined
up to this point. The following options can then be chosen:
The system uses outline agreement and info records to search for an external supply source;
The system uses stock transfer scheduling agreements or delivery sites to determine a supply
source;
Both methods can be used one after another.
 If a supply source is determined by the system, the supply region can also be taken into
consideration. This means that the site and the supply source must be assigned to the same supply
region.

0.26
Merchandise Distribution: Overview
PLANNING
Collective PO Collective PO
or
Head
Head office
office Delivery and GR in
allocation table
distribution center
TO 45... TO 45...
TO 45...
Vendor
SalesDC:
order Vendor: R3000
Vendor
R300 DC:
Vendor DC: Cross docking and
R300 TO 45...
R300 TO 45...
TO 45... Vendor: R3001 Goods issues
Vendor
StoreDC:
order
Vendor
R300 DC:
Vendor DC:
R300
R300 Assignment
Issue documents Procurement documents
PROCESSING
Distribution
Distribution center
center
Goods receipt Goods issues
Cross docking
Flow through
 SAP AG 1999
 Merchandise distribution enables you to plan, control and process merchandise flow from the
vendor to the recipient (store or customer) via the distribution center.
 The merchandise distribution process is broken down into planning and processing phases.
 Planning for merchandise distribution is done centrally, either using an allocation table or a
collective purchase order. Distribution data is updated during planning. The data generates
assignments between procurement and issue documents.
 Merchandise distribution is processed in the distribution center. The distribution data is adjusted to
match the actually available quantities at goods receipt. The merchandise is then distributed to
recipients using different processes or placed in storage, as required. The merchandise is then moved
to the goods issue zone where the goods issue is then booked.

0.27
Processing Merchandise Distribution: Goods
Receipt
Delivery and GR in
Collective PO distribution center
or
allocation table
Head
Head office
office
Goods Receipt: Adjusting Article Quantities

Distribution
Distribution center
center
Processing procedure
Cross docking Recipient Article Putaway
oriented oriented
Flow through Flow through
Deliveries Deliveries Dist. order
Picking
Deliveries
Goods issues
 SAP AG 1999
 The processing procedure for merchandise distribution defines how the merchandise in the
distribution center is handled after goods receipt and which follow-on documents are then generated.
 Cross docking: merchandise is moved from goods receipts to goods issue without being placed in
temporary storage. Deliveries are generated, and picking is not required.
 Recipient-oriented flow through: deliveries are generated for recipients after goods receipt.
Picking is then carried out for these deliveries (also known as Customer-driven flow through).
 Article-oriented flow through: picking is carried out for merchandise in the distribution center
based on distribution orders. A delivery containing the contents of the handling unit (for example,
a pallet) is generated when a handling unit has been filled. This procedure can only be used in
conjunction with lean warehouse management (also known as Merchandise-delivery flow
through).
 Storage: merchandise is only posted to one storage location. Deliveries are then generated and
used when merchandise is removed from storage at a later date.
 To be able to use different units of measure (for example, pallets and cartons) and also use
procurement for large handling units, you can use optimized procurement methods. The optimized
methods are combinations of existing methods, such as cross docking / flow through and cross
docking / storage.

0.28
Merchandise Distribution: Control
Cross docking and
Goods issues
How is merchandise to be processed
after goods receipt (processing
Following article master data procedure)?
Control
must be maintained in your
system:
How should quantity deviations affect
• Distribution profile
GR?
Should cross docking and/or flow

through be available at DC?
Following site master data
Control
must be maintained in your When should quantity variances be

system: allocated?
• Distribution profile
When should follow-on documents
for additional processing at DC be
generated?
 SAP AG 1999
 The article distribution profile defines the processing method and the quantity adjustments that are
made at goods receipt. The assignment of the distribution profile to the article (logistics data view) is
a prerequisite for handling the article within merchandise distribution.
 You can also define the percentage variance between the planned quantity and the actual delivered
quantity so that the planned quantities to be distributed can be automatically adjusted at goods
receipt.
 The site distribution profile is used for defining the basic characteristics of a site for merchandise
distribution:
 Do you plan to use cross docking for handling merchandise in your site?
 Do you plan to use flow through for handling merchandise in your site?
 Do you want to use picking for deliveries in cross docking?
 You can define the times for adjusting distribution data and follow-on document (delivery,
distribution order) generation for each business process (push, pull, returns), for example:
 Automatically at goods receipt
 Automatically with quantity variance adjustment
 Manually

0.29
Planning Merchandise Allocation: Pull Concept
Vendor
Vendor
Head office Collective

Head office
PO
Distribution
Distribution center
center
Store
Store Customer
Customer
Recipient requirements
trigger merchandise
movements
 SAP AG 1999
 Issue documents (sales orders or warehouse orders) for the recipients normally exist for the pull
concept. Collective purchase orders are created as procurement documents in which the issue
document quantities are totaled for each article and distribution center. Distribution data is also
updated in the system when collective purchase orders are generated. The data is then used to control
and oversee the distribution of merchandise to the recipients when using the pull concept.

0.30
Planning Merchandise Allocation: Push Concept
Central planning
triggers goods movement and
generates the documents
Allocation
Head
Head office
office Vendor
Vendor
table
Distribution
Distribution center
center
 SAP AG 1999
 Planning for merchandise distribution - also known as the push method - is carried out using
allocation tables. The procurement documents (vendor orders) and issue documents (warehouse
orders or deliveries) are generated as follow-on documents for the allocation table.
 The distribution data is updated in the system when follow-on documents are generated. This data is
then used to control the merchandise flow in the distribution center after goods receipt. If the
allocation table is created with a link to a purchase order or a delivery notification, a procurement
document already exists, meaning that issue documents are generated as follow-on documents.

0.31
Planning Requirements for Perishables: Objectives
At the conclusion of this topic, you will be able to:
 Explain the procedure for planning requirements for

perishables in SAP Retail as a variation of planning
requirements for replenishment
 Identify uses for the perishables planning list
 SAP AG 1999

0.32
Planning Requirements for Perishables: Process
Overview
Planning
Planning requirements
requirements
for
for perishables
perishables and
and
collective
collective PO
PO
4’ 3’ Sales
Sales data
data upload
upload
5
Store
Store sales
sales
Delivery
2
Delivery and
and GR
GR
in distribution
in distribution 6’
center
center 7 1
Flow
Flow through
through
and
and goods
goods issues
issues
Delivery
Delivery and
and GR
GR in
in
Merchandise flow
store
store
Information flow
 SAP AG 1999

0.33
P
er
ish
abl
e s
:Us
age
3
P la
nne
d
r
equi
rementsf
or
p
erish
abl
e s
F
ru
it&
veg
et
abl
e s
V
e
V
en
d
no
d
or
r1
1
V
e
V
en
d
no
d
or
r2
2
D
ai
ryp
ro
duc
ts
W
h
W
ho
l
les
a
s
al
e
e
M
ea
t&f
ish
I
m
Imp
or
t
twa
r
ae
ho
ou
se
F
low
er
s
S
APA
G19
99
 Perishable products are articles that normally have very short shelf lives and can be procured from
different vendors who, in turn, have limited delivery capacities. To ensure that perishables sell well,
the merchandise must look fresh when it is on display for customers. It is therefore very important
that the time period between the merchandise being picked and being sold is as short as possible.
Ideally, this time period should not exceed 24 hours.
 As well as for normal perishable products, you can use the functionality described here for other
articles that can be procured from more than one vendor.
 The special functions and procedures for requirements planning, procurement and distribution of
perishables enable you to use efficient, optimized logistics processes. They enable you to analyze
requirements and the current market situation quickly, help you make decisions and enable you to
order articles efficiently and speedily.

0.34
Planning Requirements for Perishables: Procedure
3
Quality? Planned requirements
Price? for perishables
Quantity?
Procurement Issue
Vendor
Vendor
Store
Store 11
DC
DC
“Purchase order"
order"
Wholesale
Wholesale
Store
Store 22
"Allocation table"
table"
Import
Import warehouse
warehouse “Collective PO" Store
Store 33
 SAP AG 1999
 There are three different variations of perishables processing at your disposal:

 Purchase order: this variant can be used centrally and decentrally in stores for procuring and
distributing perishables. Thanks to manual access, this variant provides you with the maximum
influence over the entire process. You can use this transaction to forecast quantities, create cost
prices, calculate retail prices, and order perishables.
Follow-up functions at posting are sales orders, allocation tables and collective purchase orders.
 Allocation table: this variant was conceived to fulfill the specific requirements at head office.
This variant uses the allocation table to distribute the total quantity of an article that has been
ordered to stores (push concept).
 Collective purchase order: this variant is used at head office when handling merchandise using
the pull concept. It generated order quantities using existing store orders (the follow-on documents
for the store orders). This data is then used to generate collective purchase orders.

0.35
Req uir
e mentsP
la
nnin
gfo
rPe
ris
hab
lesL
ist:
In
itia
lS cr
e e
n
3
P
la
n ne
dre q
uir
e men
ts
fo
rperis
hable
s
A sso
rtm
ent
lis
t P
roc
e s sin
g pro c
edu re
:
Sto
reo
rDC R
300 Pu rchaseo rder
Allo ca
tiontable
Co llec
tiv
eP O
A
sso
rtm
entlis
tty
peR
P
roc
ure
m e
ntp
erio
d 0
3/0
1-0
3/0
2
Is
suep
erio
d 0
2/0
1-0
3/0
1
R
equ
ire
m e
ntsP
la
nnin
gfo
rPe
ris
hab
lesL
ist
A
rtic
les V
end
or P
O q
uan
tity N
etp
ric
e ...
A
pple
s
A
llfre
sh 1
0BO
X 1
.29U
SD
O
mniu
m 2
0BO
X 1
.43U
SD
O
ra
nge
s
A
llfre
sh 1
5CA
R 2
.13U
SD
...
SA
P A
G 1
999
 The assortment list for the relevant site is used as the basis for the perishables planning list. The
articles must be listed for the site. You can call further functions for the procurement and distribution
of perishable articles from the perishables planning list. You can, for example, change existing
purchase orders.
 The functions Allocation tables and Collective purchase orders do not use the prices contained in the
perishables planning list - they calculate the prices themselves independently. It is therefore not
possible to enter cost prices in the perishables planning list when using this processing procedure.

0.36
Requirements Planning for Perishables List:
Generation
3
Planned requirements
POS sales period 01/02 - 06/02 for perishables
RIS
Current stock
+ vendor purchase orders Sales
- store orders
Requirements Planning for Perishables List

Remaining Sold
Article Vendor PO quantity Net price Retail price qty ...
qty
Apples
Allfresh 10 BOX 1.29 USD / lb 2.29 USD / lb 98 lb 536 lb
Omnium 20 BOX 1.43 USD / lb 2.49 USD / lb 103 lb 229 lb
Oranges
Allfresh 15 CAR 2.13 USD / lb 3.99 USD / lb 59 lb 427 lb
...
 SAP AG 1999
 The system can calculate the remaining quantity for each article, thus making it easier to identify the
quantities that should be ordered. The simple equation shown in the slide above is used to calculate
quantities. You can replace this equation with an equation of your own choice in a user exit.
 If you want to use the perishables information system to calculate forecast quantities, you have to
activate updating for perishables info structure S160 (Customizing).
 The POS sales period is used as the comparison time period when calculating the quantity of
merchandise that has been sold.

0.37
Requirem en tsPlanningforP erishablesList:
Functional andB ranchO ptions
3
P lanned
Tele-purchasing require mentsfor
(changingve ndor perish ables
prices)
PO
R equirem ents document
planninglist for
wholesa les
procurem ent
Pricing
Cha ngingstore Req uirem ents
ordersand p lann ingfor
schedu lelines p erish ables
list Issueslist
S imulated
purchasing
procedu re Articlemaster
Information Vendormaster
system
SAPAG1999
 You can use SAPPhone to create a direct link between the perishables buyer and the perishables
vendor so that they can discuss purchasing business directly by telephone. (for more information
about this, see the SAP Retail documentation for Tele-Purchasing for Perishables).
 You can generate a requirements planning list specifically for wholesale procurement.
 You can simulate the posting procedure to test the settings that you have made. A comprehensive
error log is available to help you in doing this.
 Pricing and the perishables information system are linked.
 You can use the interactive issues list to define the quantities and delivery data for the individual
recipients, as well as change the data created by the system.
 For more information about this, see the SAP Retail documentation for the Perishables planning list.

0.38
Create Collective PO Using Requirements Planning
for Perishables
4
Collective PO
Requirements planning
Warehouse order
for perishables list
45..
Warehouse order Purchase order
Vendor DC: R300order
45..
Warehouse 45..
Vendor DC: R300
45.. Vendor: R3001
Purchase order
Vendor DC: R300 Process method: 45..
Vendor: R3002
Collective PO
Processing method:
PO
Warehouse order
45..
Warehouse order
Vendor DC: R300
45..
Vendor DC: R300
 SAP AG 1999
 In the collective purchase order procedure, perishables planning calls up the collective purchase
order when data is saved. A collective purchase order is then generated for each vendor using the
warehouse orders in perishables planning.
 The purchase order procedure can use existing warehouse orders to calculate order quantities.
Furthermore, you can generate warehouse orders for stores that have not entered any purchase orders
in perishables planning.
All warehouse orders are then transfered to the collective purchase order function so that collective
purchase orders can be generated by the relevant vendor.

0.39
Processing by Vendor
5
Delivery and GR in
Purchase order 45..
distribution center
Vendor: R3001
Vendor
Vendor Head
Head office
office
Distribution
Distribution center
center
 SAP AG 1999
 The vendor delivers the ordered merchandise and it is then distributed to the individual stores in the
distribution center.

0.40
Running Merchandise Distribution:
Flow Through (Recipient-oriented) 1/3
6’
Flow through
and goods issues
Goods receipt
High rack
storage
1 area
Distribution Picking area

zone
=>
 SAP AG 1999
 At flow through, merchandise is transported to a repackaging bin after goods receipt, where it is then
repacked. The merchandise is then transported to goods issues.
 Two variants of flow through exist: recipient-oriented flow through and article-oriented flow
through.

0.41
6’
Flow through
and goods issues
Goods receipt
High rack
storage
area
2 Picking area
Distribution
zone
 SAP AG 1999
 Recipient-oriented flow through: merchandise is posted to a storage location for recipient-oriented

flow though immediately upon its arrival at goods receipt. The merchandise distribution data is
analyzed and the relevant deliveries generated for the recipients.

0.42
6’
Flow through
and goods issues
Goods receipt High rack

storage
area
Picking area
Distribution
zone
3 Goods
Cross docking
issue
 SAP AG 1999
 Picking is then carried out for the deliveries that have been generated. Merchandise is sent to goods
issues and posted as being delivered.

0.43
Flow Through (article-oriented) 1/4
6’
Flow through
and goods issues
Goods receipt
High rack
storage
1 => area
Distribution
zone
Picking area
Recip. 1 Recip. 2 Recip. 3
 SAP AG 1999
 Article-oriented flow through can only be used in conjunction with lean warehouse management.

0.44
6’
Flow through
and goods issues
Goods receipt
High rack
storage
area
2a Distribution
zone
Picking area
 SAP AG 1999
 In article-oriented flow through, merchandise is transported to a distribution zone after goods receipt.
Distribution orders are generated for picking.
 Distribution orders are transfer orders without a link to a preceding document. The distribution
orders are used as distribution lists.

0.45
6’
Flow through
and goods issues
Goods receipt
High rack
storage
area
Distribution
zone
Picking area
2b
 SAP AG 1999
 The distribution area is used for picking merchandise based on the contents of the distribution orders
and placing the picked merchandise on the handling units that are available for the relevant
customers (for example, pallets). Picking is stopped as soon as each handling unit has been filled and
a delivery is generated for that picking unit. Deliveries are then marked as not requiring picking as
the process has already been completed by this point.

0.46
6’
Flow through
and goods issues
Goods receipt
High rack
storage
area
Distribution
zone
Picking area
3 Goods issues
Cross docking
 SAP AG 1999
 Merchandise is sent to the goods issue area where the goods issues are then posted.

0.47
Planning Requirements for Perishables: Standard
Analysis Procedure
Purchase order
S160
Purchase order
Order volume
Goods receipt
Goods
receipt Goods issues
Stock transfer
Sales variance
Sold
quantity Sales order
...
Generation
of list
 SAP AG 1999
 The standard analysis procedure for perishables planning provides data that enable you to run
controlling for the perishables process.
 The data is based on info structure S160 that contains all important characteristics and key figures at
article level for today's date and which are needed for the perishables processing and controlling.
 The data generated can then be used to analyze purchase orders, goods receipts, stock transfers in the
distribution centers to the stores, as well as the sales figures that are recorded at POS.
 This covers the needs of both retailers and wholesalers, and means that key figure about sales order
volumes, delivery volumes and billing volumes can also be analyzed.
 You can also analyze characteristics for single articles and generic articles.

0.48
Unit Summary
You are now able to:

 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 concepts behind the functions
Replenishment, Store orders and Planning
requirements for perishables
 Name the most important steps for generating a
collective purchase order
 Name the advantages of using Cross docking and
Flow through
 SAP AG 1999

Exercises
Unit: Sales and Delivery to Stores

Topic: Replenishment
After completing these exercises, you will be able to:

 Name the master data that is required for replenishment
 Run replenishment in SAP Retail and control the documents
that are generated
In the future, you want to generate purchase orders automatically

in your warehouse, based on the sales data that has been recorded
in your system.
1-1 You plan to supply store T2## with merchandise centrally, using the replenishment
function. Use the parameter overview to see the articles that are procured for
Recipient T2## using replenishment:
1-1-1 Which RP type do articles R100000 and R100008 have?
1-1-2 Which replenishment master data has been maintained for the following
articles?
R100000 R100008
Stock
Target stock
Reorder point
Safety stock
1-1-3 How do you know if an article is active for replenishment-based inventory

management?
1-1-4 Which articles are active for replenishment-based inventory management?
1-1-5 How can you find (function key) a definition for Reorder point?

1-1-6* Go to the site master for customer T2## and check if inventory management
on merchandise category basis is scheduled for merchandise category
R1121 (Perishables), and which value-only article is going to be used to
post the stock. Note: you can do this by choosing Extras → Merchandise
categories in the site master.
What does activating inventory management for a merchandise category do?
1-2 Trigger procurement for articles R100000 and R100008 for customer T2## by
running replenishment planning.
1-2-1 What article quantities have been suggested for procurement?
R100000 R100008
Replenishment
requirements
1-2-2 Generate the follow-on documents and view the results in the replenishment
monitor.
Go to the generated document view.
Which type of follow-on document has been generated? Order type
Which supplying site was found by the system?
Make a note of the purchase order number.

1-2-3 Which article quantities do you want to order?
R100000 R100008
PO quantity
1-2-4 Which article master data was used to calculate these PO quantities? (To
find this information, go the article master for both articles and check the
units of measure).
1-3 You now want to find out how the replenishment master data detailed under 1-1-2
was found for article R100000. To do this, go to the replenishment parameter
overview for customer T2##.
1-3-1 Which requirements group in store T2## is assigned to merchandise
category R1111?

1-3-2 Has replenishment master data been maintained for any of the requirement
groups for article R100000?
1-3-3 According to the replenishment master data for article R100000 in store
T2##, what is the:
Target stock:
Reorder point:
Safety stock:
Compare your data with the data determined for 1-1-2!
1-4 Before continuing with the remaining exercises in this unit, create a new purchase
order (stock transfer) using the following data:
1-4-1 Supplying site: T7##
Order type: UB
Purchasing organization: R300
Purchasing group: R30
Delivery date: next working day
Site: T2##
Storage location: 0001
Purchase order items: R100000 80 CAR
R100008 40 CRT
PO number:
This purchase order is now used as the basis for the remaining exercises in
this unit!

Sales and Delivery to Stores Exercises

Topic: Merchandise Distribution
After completing these exercises, you will be able to:

 Create a generic purchase order for cross-docking deliveries
 Process the purchase orders for your stores from shipping to
goods issue in cross-docking
Before procuring merchandise, you group the stock transfer

orders from your stores to a generic purchase order for an
external vendor. When goods are received in the distribution
center, the article quantities are divided into stock transport
orders and sent to goods issue immediately, together with the
relevant documents.
2-1 The purchase orders for your stores need to be grouped into a collective purchase
order for an external vendor in merchandise distribution.
2-1-1 You need to add a distribution profile to your distribution center site master
record. Assign distribution profile 002 in the Purchasing / distribution view
for site T7##.
2-1-2 Create a collective purchase order for distribution center T7## and
purchasing organization R300. You want to run procurement for all articles
that have to be delivered to your store by this Friday. The merchandise
should be in your distribution center for a maximum of one day. You should
therefore select the schedule line interval 1.
Which articles does your system suggest for procurement?
How can you find out which stock transport orders should be used to
calculate the purchase order quantity?

2-1-3 Let your system suggest a vendor for the article items. Your system may
already have found a vendor - see column Vendor.
Which vendor did your system find?
Generate the purchase order and make and note of the number:
2-1-4 Display the purchase order in your system.

To which site is the article delivered?
In which storage location do you want to process goods receipt?
2-2 After goods receipt at the distribution center, the received quantities are distributed
to the individual stock transfer orders for the stores. They are then moved to goods
issue area immediately, together with the relevant delivery documents.
2-2-1 The merchandise is delivered to distribution center T7## and you post the
goods receipt for your (collective) purchase order. Enter today's date minus
seven days as the date of production for article R100000.
Make a note of the article document number.
2-2-2 Go to the merchandise distribution monitor screen. Display merchandise
distribution data for distribution center T7## and the PO number for your
collective purchase order. How can you see that no adjustments have yet
been made?
2-2-3 In a second session, adjust the goods receipt in distribution center T7## to
match the purchase order that was displayed by the system in 2-1-3.
Which article quantities have been planned for cross-docking?
R100000
R100008
Save the merchandise distribution and then refresh the merchandise
distribution in your other session.
2-2-4 The follow-on documents for delivering items from the distribution center
to the stores are also created when merchandise distribution is adjusted.
Find the document type and document number using the purchase order
history for the items in the stock transfer order that you created (see 1-4-1).
Document:
Number:

2-2-5 Display the delivery in your system.
Which storage location has been found for picking the individual items?
Which picking status do the article items have?

Picking status:
How does this affect processing of the delivery?
2-2-6 Use the delivery monitor to post goods issue for all of your deliveries that
are to be posted.
2-2-7* You want to add a delivery note to your delivery. Create a delivery note for
your delivery. Display the delivery note in your system before it is printed.
2-3* You want to add more information to the documents that you have created.
2-3-1 Display the PO history for the items in your vendor purchase order and your
stock transport order. Which follow-on documents are displayed?
Follow-on documents for vendor purchase orders:
Follow-on documents for stock transport orders:

Solutions

Topic: Replenishment
All the steps detailed in these solutions start from the

Retailing screen:
SAP standard menu  Logistics  Retailing
1-1 Sales  Replenishment  Overview  Parameters
Field name or data type Values

Recipient T2##
Articles R100000 and R100008
Program  Execute or choose [F8]
1-1-1 The RP type is found in the RP Type column. Articles R100000 and
R100008 have the RP type RP.
1-1-2 The following values have already been maintained in the system:
R100000 R100008
Stock 70 0
Target stock 1,500 1,000
Reorder point 300 700
Safety stock 250 250
1-1-3 Replenishment-based inventory management has been activated for the
articles for which the fields for Replen. IM and the Correct RS function
have been selected.
1-1-4 Replenishment-based inventory management has been activated for article
R100008.
1-1-5 For the definition of the reorder point, place the cursor on the Reorder point
field and select [F1].

1-1-6* Double-click on field T2##
Extras  Merchandise categories
Inventory management for a merchandise category has been activated for
merchandise category R1121 (the relevant field in column M has been
selected). Stock is posted to merchandise category article R1121 (column
MC article).
As you have made this setting in your system, inventory management is no

longer run on a value and quantity basis for the articles in your stock.
Inventory management is now only to be run on a value basis for the total of
all articles in the relevant merchandise category.
1-2 Sales  Replenishment  Replenishment planning  Execute

Recipient T2##
Program  Execute
1-2-1
R100000 R100008
Replenishment 1,430 PC 1,000 lb
requirements
1-2-2 Replenishment requirements  Generate follow-on documents

Confirm the dialog box that appears by selecting [Enter].
Double-click on Pur. Order (purchase order number)
Order type: UB (stock transport order)
Delivery site: T7##
1-2-3
R100000 R100008
PO quantity _______ CAR ________ CRT
1-2-4 Select an item and go to the article master by selecting Environment 

Article. In the article master, select the Basic data view and press [Enter].
The warehouse unit of issue (D/I column) is used for the stock transport
order. You can calculate the purchase order quantity by dividing the
replenishment quantity by the total number of base units of measure in the
warehouse unit of issue.

1-3 Sales  Replenishment  Overview  Parameters

Recipient T2##
Program  Execute
1-3-1 Double-click on field T2##
Extras  Merchandise categories
The requirements group (Large) 02 has been defined for merchandise
category R1111.
Return to the parameter overview.
1-3-2 When you are in the parameter overview, double-click on field R100000,
select the Basic data view, press [Enter], press the [Additional data] button
and choose the tab Requirement groups. The requirement groups 01, 02 and
03 have been maintained for article R100000.
1-3-3 Requirement group 02 was assigned to store T2## for merchandise category
R1111. The requirement group contains the following data:
Target stock: 1,500
Reorder point: 300
Safety stock: 250
The values for article R100000 in store T2## are defined using this data.

1-4 Purchasing  Purchase order  Purchase order  Create  Stock transfer
1-4-1

Supplying site T7##
Order type UB
Purchasing organization R300
Purchasing group R30
Delivery date: Next working day
Site T2##
Storage 0001
location
[Enter]

Articles R100000
PO quantity 80
Articles R100008
PO quantity 40
[Enter]
Purchase order  Save
Confirm the warning by selecting [Enter].

Sales and Delivery to Stores Solutions

Topic: Merchandise Distribution
2-1
2-1-1 Master data  Site data  Site  Change

Site T7##
[Enter]
Tab: Purchasing / Distribution
Distribution profile 002
Site  Save
2-1-2 Merchandise logistics  Merchandise distribution
 Collective purchase order  Create

Distribution center T7##
Purchasing organization R300
Processing types Select all
Procurement period From today until Friday
next
Schedule line interval 1
Retain all other settings

[Execute] or [F8]
Articles: R100000 and R100008
Mark the lines and then select

Goto  Display details
[Back]

2-1-3 Mark the lines and then select:
Edit  Find supply source
Vendor R3000
Collective purchase order  Generate  Total worklist

The Document number column contains the purchase order number.

Collective purchase order  Display
Enter the number found in 2-1-3 and press [Enter]
Site: T7##
Storage location: 0003
2-2 Merchandise logistics  Goods receipt  Goods receipt

2-2-1

Purchase order See 2-1-3
[Enter]

Date of production (for A week ago today
R100000)
Select Item ok for both items. Choose [Post].

Distribution  Monitor
Distribution center T7##
PO number See 2-1-3
Document types Select all
Program  Execute
Expand the individual items
No adjustment has yet taken place as the Act. Quantity for the individual
items has not yet been displayed (they still have the value 0).

2-2-3 System  Create session
Merchandise logistics  Merchandise distribution  Distribution 
Adjust

Site T7##
PO number See 2-1-3
Goods receipt See 2-2-1
[Execute] or [F8]
Display the distribution for an additional article by selecting Goto  Next
Procurement Item.
The column CD quantity contains the cross-docking quantities for each of
stock transport items for the article concerned.
Distribution  Save  Total

Switch to the other session to view the merchandise distribution display
Edit  Refresh
2-2-4 Purchasing  Purchase order  Purchase order  Display
Enter the purchase order number from exercise 1-4-1.
[Enter]
Select item.
Item  Statistics  PO history
A delivery was generated.
2-2-5 Double-click on the document number.
Choose the Picking tab.
Storage location: 0003 (CD storage loc.)

Picking status (column Picking): not relevant for picking
(Note: this information is also available in the detailed item view:
select the item and then press the button [Item detail].)
Goods issue can be posted for this delivery immediately. No picking is

needed in the warehouse for this delivery.

2-2-6 Merchandise logistics  Logistics Execution  Goods Outbound Process
 Goods issue for Outbound delivery  Post Goods issue
 Collective processing via outbound Delivery Monitor

Plan d gds mvmnt date From today until next
Friday
Edit  All selections
Created by IRT100-##
Program  Execute
Select deliveries.
Subsequent functions  Post goods issue
Confirm the dialog box concerning the actual merchandise movement date by
selecting [Enter].
2-2-7* Select delivery
Subsequent functions  Output from deliveries
Confirm processing mode Initial processing by selecting [Enter].
Confirm that your delivery is in the delivery field, [Execute].
Select delivery
Goto  Print preview
2-3 Purchasing  Purchase order  Purchase order  Display purchase order

2-3-1 Enter the numbers of the stock transport order and the vendor order. Mark
the items.
Item  Statistics  PO history
The following are displayed as the follow-on documents:
For the vendor order: Article document (goods receipt)

For the stock transport order: Article document (goods issue)
Delivery

EXP - 0004 Sales & Delivery Store

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EXP - 0004 Sales & Delivery Store

Uploaded by

Copyright:

Available Formats

0

Sales and Delivery to Stores

© SAP AG IRT100 4-1

At the conclusion of this unit, you will be able to:

© SAP AG IRT100 4-2

© SAP AG IRT100 4-3

 A customer buys an article in a store.

© SAP AG IRT100 4-4

© SAP AG IRT100 4-5

Store - New York

Thank you for shopping with us.

© SAP AG IRT100 4-6

ALE / EDI Intermediate doc. (IDoc)

© SAP AG IRT100 4-7

© SAP AG IRT100 4-8

Expected Reorder point

Warehouse order Replenishment

© SAP AG IRT100 4-9

Post anticipated goods

Warehouse order Replenishment

© SAP AG IRT100 4-10

Block of the processed

© SAP AG IRT100 4-11

Store Store Store Store

© SAP AG IRT100 4-12

Cross docking Goods issue

© SAP AG IRT100 4-13

Goods receipt High rack

© SAP AG IRT100 4-14

Cross docking Goods issue

© SAP AG IRT100 4-15

© SAP AG IRT100 4-16

POS Store goods receipt

 The delivery from the distribution center arrives at the store.

© SAP AG IRT100 4-17

© SAP AG IRT100 4-18

• POS receipt texts Download master

The following store master data must

• POS outbound profile

© SAP AG IRT100 4-19

Sales data upload

• POS inbound profile

What form of inventory Head

How are sales, returns and Upload sales data

How are sales to be billed ?

© SAP AG IRT100 4-20

MRP parameters Replenishment

Source of supply Replenishment /

Following store master data must

• POS inbound profile Warehouse order

Where and how is merchandise to be ordered ? Purchase

© SAP AG IRT100 4-21

• available stock only • different stock types

Simplified procedure Standard procedure

 Replenishment-based inventory man.

 Replenishment gives you the option of accessing detailed MM inventory management or a

© SAP AG IRT100 4-22

Replenishment requirement = target stock - expected stock

Replenishment master data for article R100002, merchandise category R1122

© SAP AG IRT100 4-23

Create Purchase order

© SAP AG IRT100 4-24

Find external supply sources