Merchandise Distribution - EN - CUST - V147

Best Practices for mySAP Retail
Version 1.47
Customizing Guide Scenario

Merchandise Distribution
SAP AG
Neurottstrasse 16
69190 Walldorf, Germany
Copyright
Copyright  2003 SAP AG. All rights reserved.
No part of this document 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.
WinNT Microsoft
SAP, R/3, SAP Retail SAP AG
Key:
<XXX>  Variable entries
'XXX'  Fixed entries
[XXX]  Pushbutton
Merchandise Distribution Scenario Page 3 of 51

Table of Contents
CUSTOMIZING GUIDE MERCHANDISE DISTRIBUTION.....................................................5
1 INTRODUCTION.............................................................................................................. 5
2 PRECONDITIONS...........................................................................................................6
2.1 General Basic Data Settings................................................................................6
2.1.1 Customer Grouping for Allocation Table.............................................................6
2.1.2 Configure Article for Merchandise Distribution....................................................7
2.2 Basic Data for SLS Subitems and EDI Communication.....................................9
2.2.1 Vendor Classification for SLS Prepacking...........................................................9
2.2.2 Customer Article Info for SLS Prepacking.........................................................10
2.2.3 Maintain Additional for Customer......................................................................11
2.2.4 Maintain Additional for Vendor..........................................................................12
2.2.5 Maintain Output Condition Records in Sales (at the Vendor)............................13
2.2.6 Maintain Output Condition Records in Purchasing............................................14
2.2.7 Maintain Partner Profiles...................................................................................15
3 CUSTOMIZING.............................................................................................................. 16
3.1 WM Warehouse Structures.................................................................................16
3.1.1 Define Additional Storage Types.......................................................................16
3.1.2 Create Storage Location Reference..................................................................17
3.1.3 Define Movement Types...................................................................................18
3.1.4 Set LE-WM Interface for Inventory Management..............................................19
3.2 Lean WM Structures for Merchandise-Driven Flow-Through..........................20
3.2.1 Copy Warehouse Number.................................................................................20
3.2.2 Maintain Control Parameters and Number Ranges for Warehouse Number....21
3.2.3 Define Storage Type.........................................................................................22
3.2.4 Define Shipment Types.....................................................................................23
3.2.5 Define Movement Types in Lean WM...............................................................24
3.2.6 Define Movement Types for Distribution Orders...............................................25
3.3 Merchandise Distribution...................................................................................26
3.3.1 Define Site Profiles for Merchandise Distribution..............................................26
3.3.2 Define Adjustment Profiles per Processing Method..........................................27
3.3.3 Define Distribution Profile of Article in DC.........................................................28
3.4 Purchase Order...................................................................................................29
3.4.1 Define Screen Layout of the Purchase Order...................................................29
3.5 Allocation Table for Customer...........................................................................30

3.5.1 Assign Class Type to Application......................................................................30

3.5.2 Copy Sales Document Type..............................................................................31
3.5.3 Assign Incompleteness Procedures to the Sales Document Types..................32
3.5.4 Copy Item Categories of Allocation Table.........................................................33
3.5.5 Copy Allocation Table Types.............................................................................35
3.6 SLS Subitems for Cross-Docking......................................................................37
3.6.1 Maintain SLS Profile..........................................................................................37
3.6.2 Adjust Item Category Determination for Sales Documents...............................38
3.7 Automatic Generation of Transfer Orders........................................................39
3.7.1 Create Transportation Groups...........................................................................39
3.7.2 Define Route.....................................................................................................40
3.7.3 Set Route Determination...................................................................................41
3.7.4 Maintain Condition Tables.................................................................................42
3.7.5 Maintain Access Sequence...............................................................................43
3.7.6 Maintain Output Determination 'WMTA'............................................................44
3.7.7 Set Lock Logic for Warehouse Number............................................................45
3.8 Connect the Warehouse to a Site (DC)..............................................................46
3.8.1 Define Storage Location in the DC....................................................................46
3.8.2 Assign Warehouse Number to Site/Storage Location.......................................47
3.8.3 Define Storage Conditions................................................................................48
3.8.4 Define Control of "Site/Storage Location – Warehouse Number" Assignment..49
3.8.5 Define Degree of Activation of Warehouse Management.................................50
3.8.6 Assign Storage Location Determination with Situation......................................51

Customizing Guide Merchandise Distribution

1 Introduction
This Customizing Guide describes the application and customizing settings in your SAP R/3
System that are required for carrying out the “Merchandise Distribution” scenario.
In this scenario, you can choose to plan merchandise distribution using an allocation table
(push method) or a collective purchase order (pull method). The goods are then either
placed in storage or moved through the distribution center by means of processing
methods, such as cross-docking or flow-through.
Head office uses the allocation table to plan, control, and monitor the procurement and
allocation of goods to stores or customers.
In the case of collective purchase orders, however, procurement starts at the recipient. The
recipient’s procurement documents are bundled to form a collective purchase order in the
distribution center and the goods are then distributed to the stores or customers.
Different processing methods are used in the distribution center to distribute articles from
the allocation table and collective purchase order.
 Putaway: The goods are placed in a storage bin from the time they are received until
the time they are issued.
 Cross-docking: The goods are brought from goods receipt directly to goods issue
without being picked or repacked.
 Flow-through: Between goods receipt and goods issue, the goods are transported to
a repacking zone and are picked there.
In order to implement these functions, you need to make settings for the following topics:
 WM warehouse structures (see the “Distribution Center Logistics with Warehouse

Management (WM)” scenario)
 Lean WM warehouse structures for merchandise-driven flow-through
 Merchandise distribution
 Process specifications.
These topics are described in detail in the Customizing Guide. Unless otherwise stated, the
guide describes the settings for the fashion, hard goods, and food sectors. Any sector-
specific differences will be discussed where relevant.

2 Preconditions
2.1 General Basic Data Settings
2.1.1 Customer Grouping for Allocation Table

PRECONDITIONS :
The class type must be maintained.
PATH:
1. SAP Menu  Logistics  Retailing  Master Data  Site Data  Grouping 

Allocation Table (WB50-WB52)
2. SAP Menu  Logistics  Retailing  Master Data  Site Data  Grouping 
Allocation table  Maintain Assignment  Sites in a Class (WB56)
PROCEDURE :
For 1.: Class type ‘011’, [COPY] pushbutton

Class ‘PCS-CUTOMER01’, [ENTER] pushbutton
For 2.: Class type ‘011’, [COPY] pushbutton
[...ASSIGNMENTS] pushbutton
Customer/Class: ‘PCS-C301’, ‘PCS-C302’
PARAMETER SETTINGS :
BACKGROUND :
Enter the class type and class if you want to use the customers (‘PCS-C301’ and ‘PCS-C302’) for
sales orders that are generated directly from the allocation table.
You must select a valid combination of class type and class.
REMARKS :

2.1.2 Configure Article for Merchandise Distribution

PRECONDITIONS :
The articles of category '01' are set up for the merchandise distribution functionality.
PATH: (MM41-MM43)
SAP Menu  Logistics  Retailing  Master Data  Article Data  Article
PROCEDURE :
1.: Select the ‘Basic Data’ view, [ENTER] pushbutton

2.: 'Additional Data' view (in the 'Basic Data' view), 'Additionals' tab
3.: ‘Purchasing Org.’ field: ‘E001’
Fashion: ‘Vendor’ field: ‘PCS-V131’, ‘PCS-V132’ (CD with SLS)
Hard goods: ‘Vendor’ field: ‘PCS-V411’, ‘PCS-V412’ (CD with SLS)
Food: ‘Vendor’ field: ‘PCS-V201’ (stock placement), ‘PCS-V311’ (CD and FT),
‘PCS-V202’ (CD with SLS)
Select the ‘Purchasing’ view, [ENTER] pushbutton
4.: Select the ‘Basic Data’ view, [ENTER] pushbutton
5.: ‘Warehouse Mgmt’ view (in the ‘Logistics: Distribution Center’ view)
For 1.: Maintain the following entries:

Field Stock Plcmt. CD CD with SLS FT Rec. FT Art.
Stor.Conditions W FT
Trans. Group 0001 0003 0003 0003 0001
Artl Grp Pckmat WVT1
For 2.: Maintain the following entries (CD with SLS only):
Sequence Number Sales Unit Additionals Procedure
1 PC PCS-10-ART305 0005

Conf. Control PCS1 PCS1 PCS1 PCS1 PCS1

Distr. Profile A01 CD1 CD1 FT2 FT1
Stor. Location 0003 0006 0006 0004 0005


View Stock Plcmt. CD CD with SLS FT Rec. FT Art.
Warehouse Mgmt Necessary Necessary Necessary Necessary Not nec.
BACKGROUND :
The field settings enable an article to be either placed in storage or moved through the
distribution center by means of cross-docking or flow-through.
The SLS is technically an additional with its own article master. This service (Article: ‘PCS-10-
ART305’) is assigned to all the articles that are to be prepacked by the vendor and is connected
to the procedure for additionals '0005'.
Mass maintenance is available to enable services to be assigned to multiple articles efficiently:
SAP Menu  Logistics  Retailing  Sales  Additionals  Mass Maintenance 
Additionals/Articles  Maintain (WTAD_VKHM_MAINTAIN).
REMARKS :
You require the settings for (2) for SLS prepacking only.

2.2 Basic Data for SLS Subitems and EDI Communication
2.2.1 Vendor Classification for SLS Prepacking

PRECONDITIONS :
The class type and class must be maintained.
PATH: (CL24N)
SAP Menu  Logistics  Retailing  Master Data  Vendor Data  Environment  General
Classification  Assignment  Maintain  Assign Objects/Classes to Class
PROCEDURE :
Class: ‘PCS-VZ’
Class type: ‘030’
[...ASSIGNMENTS] pushbutton
Site/Class: ‘LZ01’
BACKGROUND :
The site group created here is used to control the SLS service profiles (see Section 3.6.1).
REMARKS :

2.2.2 Customer Article Info for SLS Prepacking

PRECONDITIONS :
PCS master data must be created.
PATH: (VD51-VD53)
SAP Menu  Logistics  Retailing  Master Data  Edit Customers  Environment 

Customer-Art. Info
PROCEDURE :
Customer: ‘PCS-C381’ (Fashion) ‘PCS-C382’ (Food), ‘PCS-C383’ (Hard goods)

Sales organization: ‘V00L’
Distribution channel: ‘V3’
[EXECUTE] pushbutton, [INFO RECORD DETAILS] pushbutton to branch to the detail view
Material No. Cust. Material Item Usage
PCS-07-ART411 PCS-07-ART411 SLSV
BACKGROUND :
The customer article number must be decoded into the vendor article number. For this reason,
article information is maintained for the normal article and the corresponding SLS.
You set the ‘SLSV’ indicator for sales documents when you determine the item categories (see
Section 3.6.2).
REMARKS :

2.2.3 Maintain Additional for Customer

PRECONDITIONS :
PATH: (WTAD_FMCU_CHANGE)
SAP Menu  Logistics  Retailing  Sales  Additionals  Mass Maintenance 

Method/Customer  Maintain
PROCEDURE :
Customer: ‘PCS-C381’ (Fashion) ‘PCS-C382’ (Food), ‘PCS-C383’ (Hard goods)

Sales organization: 'V00L'
Distribution channel: 'V3'
'Procedure for Additi' tab
Proc. for additional: '0005'
Ext. proc. for additionals: '0005'
[EXECUTE] pushbutton, [SAVE] pushbutton
BACKGROUND :
Because customers generally have other descriptions for these procedures for additionals than
those used internally, the description of the customer (external) must be assigned to the
description used internally.
REMARKS :

2.2.4 Maintain Additional for Vendor

PRECONDITIONS :
PATH: (WTAD_SUP_FM_CHANGE)
SAP Menu  Logistics  Retailing  Sales  Additionals  Mass Maintenance 

Method/Vendor  Maintain
PROCEDURE :
Purchasing organization: 'E001'

Vendor: 'PCS-V132' (Fashion), 'PCS-V202' (Food), 'PCS-V412' (Hard goods)
Procedure for additionals '0005', [EXECUTE] pushbutton, [SAVE] pushbutton
BACKGROUND :
Because not all vendors generally support all procedures for additionals, the possible procedures
for additionals for each vendor are entered in a table by means of mass maintenance.
REMARKS :

2.2.5 Maintain Output Condition Records in Sales (at the Vendor)

PRECONDITIONS :
The output type must be created.
PATH:
1. SAP Menu  Logistics  Retailing  Master Data  Edit Customers  Messages 

Sales Document (VV11-VV13)
2. SAP Menu  Logistics  Retailing  Master Data  Edit Customers  Messages 
Shipping (VV21-VV23)
PROCEDURE :
For 1.: Output type 'BA00', [ENTER] pushbutton

'Sales Organization' field: 'V00L'
'Customer' field: 'PCS-C381' (Fashion) 'PCS-C382' (Food), 'PCS-C383' (Hard goods)
[EXECUTE] pushbutton
For 2.: Output type 'BA00', [ENTER] pushbutton

'Sales Organization' field: 'V00L'
'Customer' field: 'PCS-C381' (Fashion) 'PCS-C382' (Food), 'PCS-C383' (Hard goods)

Customer PartF Medium Date/Time Language
PCS-C381 SP 6 4 DE
PCS-C382 SP 6 4 DE
PCS-C383 SP 6 4 DE

Customer PartF Medium Date/Time Language
PCS-C381 SH 6 4 DE
PCS-C382 SH 6 4 DE
PCS-C383 SH 6 4 DE
BACKGROUND :
The output type determines the use of an electronic form, such as an order confirmation (‘BA00’)
or an inbound delivery (‘LAVA’), that is sent to the retailer.
REMARKS :

2.2.6 Maintain Output Condition Records in Purchasing

PRECONDITIONS :
If the transfer of prepacking information is to be shown in an integrated scenario by means of

SLS, including the processing of IDocs in goods issue and receipt, comprehensive EDI
communication must first be established. This is described in detail in the Customizing Guide for
the “EDI” scenario.
PATH: (MN04-MN06)
SAP Menu  Logistics  Retailing  Purchasing  Purchase Order  Master Data 

Messages  Purchase Order
PROCEDURE :
Output type 'NEU', [ENTER] pushbutton

Key combination 'Purchasing Output Determination: Purch. Org./Vendor for EDI', [CHOOSE]
pushbutton
'Purch. Organization field': 'E001'
'Vendor' field: 'PCS-V132' (Fashion), 'PCS-V202' (Food), 'PCS-V412' (Hard goods)
Vendor PartF Medium Date/Time Language

PCS-V132 VN 6 4 EN
PCS-V202 VN 6 4 EN
PCS-V412 VN 6 4 EN
BACKGROUND :
The output type determines the use of an electronic form, such as a purchase order, that is sent
to the vendor.
REMARKS :

2.2.7 Maintain Partner Profiles

PRECONDITIONS :
See Section 2.2.6.
PATH: (WE20)
SAP Menu  Tools  Business Communication  IDoc Basis  Administration  Partner

Profile
PROCEDURE :
1.: Open 'Partner Type KU'

Customer: 'PCS-C381' (Fashion) 'PCS-C382' (Food), 'PCS-C383' (Hard goods)
[DETAILSCREENOUTB.PARAMETER] pushbutton, 'Message Control' tab
2.: Open 'Partner Type LI'

Vendor: 'PCS-V132' (Fashion), 'PCS-V202' (Food), 'PCS-V412' (Hard goods)
[DETAILSCREENOUTB.PARAMETER] pushbutton, 'Message Control' tab

Partn.Type Partn.Funct. Mess. Type Message Va… Appl. Mess. Type Proc. Code
KU SP ORDRSP V1 BA00 SD10
KU SH DESADV 2 V2 LAVA DELV

Partn.Type Partn.Funct. Mess. Type Message Va… Appl. Mess. Type Proc. Code
LI VN ORDCHG EF NEU ME11
LI VN ORDERS EF NEU ME10
BACKGROUND :
The field settings enable documents to be exchange correctly between the two partners, vendor
and retailer, during EDI communication.
REMARKS :

3 Customizing
3.1 WM Warehouse Structures

3.1.1 Define Additional Storage Types

PRECONDITIONS :
Warehouse number.
PATH:
IMG  Logistics Execution  Warehouse Management  Master Data  Define Storage

Type
PROCEDURE :
[NEW ENTRIES] pushbutton or copy existing entries, [DETAIL] pushbutton to branch to the detail
view
WhN Typ Put. Strat. Stock Plc. Mixed Stor.Addn..St. Stck..Strat. Stock Rmv.Neg. Stock Post.
PC1 001 C x X X F x
PC1 702 X X F x x x
PC1 802 X X F x x
PC1 902 X X x x
PC1 916 X X x
PC1 921 X X x
BACKGROUND :
The storage types extend the structure of the WM-managed warehouse ‘PC1’ to include those
storage types that are also required for executing the cross-docking and flow-through processing
methods.
Stock placement control:
The system uses the putaway strategy ‘C’ to automatically search for an article that is suitable for
a stock putaway in a storage type, such as ‘Putaway general FT art.’ (‘001’). The confirmation of
putaway results in the transfer order items having to be confirmed when stock is placed in this
storage type. Mixed storage enables you to store several quants in a storage bin in this storage
type. An addition to existing stock means that the existing stock in a storage bin with a particular
article is increased by a quant of the same article of the same type.
Stock removal control
The system uses the stock removal strategy (‘F’) to automatically search for an article in a
storage type, such as ‘GR Area External Rcpts’ (‘802’), for a stock removal. The confirmation of
removal results in the transfer order items having to be confirmed when stock is removed from
this storage type. When the Allow Negative Stock indicator is set, the system lets you post
negative quants. Transfer posting means that no shipments should be made for transfer postings
but that the article can be relabeled on site if required.
REMARKS :
3.1.2 Create Storage Location Reference

PRECONDITIONS :

Warehouse number.
PATH:
IMG  Logistics Execution  Warehouse Management  Interfaces  Inventory

Management  Define Storage Location Control  Storage Loc. Ref.
PROCEDURE :
[NEW ENTRIES] pushbutton or copy existing entries
WhNo Storage Loc. Ref. Stor. Loc. Reference Descr.

PC1 CD Cross Docking
PC1 FT Flow-Through
BACKGROUND :
You can set these indicators ('CD' and 'FT') to influence the storage type search within the
transfer order as well as interface determination of the IM posting, depending on the storage
location.
REMARKS :

3.1.3 Define Movement Types

PRECONDITIONS :
Warehouse number.
PATH:
IMG  Logistics Execution  Warehouse Management  Activities  Transfers  Define

Movement Types
PROCEDURE :
Select entry, pushbutton [Copy as...]
PARAMETERS – SETTINGS :
Copy from Warehouse Number 'PC1', Movement Type '101':

Movement Type 901, 'Goods Receipt CD':
Change fields: Src: '802', TO Confirmation: blank, TO Display: blank
Movement Type 901, 'Goods Receipt FT rec.':
Change fields: Src: '702', TO-Confirmation: blank, TO Display: blank
Copy from Warehouse Number 'PC1', Movement Type '601':
Movement Type 911, 'Goods Issue Del. CD':
Change fields: Src: '802', Requirement Type: 'R (Customer)', TO Display: blank,
Print code: '01', TO items can be confrmd immed: blank, Consider Pre-Alloc. Stock: 'X'
Movement Type 912, ' Goods Issue Del. FT rec.':
Change fields: Src: '702', Requirement Type: 'R (Customer)', TO Display: blank,
Print code: '01', TO items can be confrmd immed: blank, Consider Pre-Alloc. Stock: 'X'
BACKGROUND :
The WM Movement types control the stock posting in the warehouse.
REMARKS :

3.1.4 Set LE-WM Interface for Inventory Management

PRECONDITIONS :
Warehouse number.
PATH:

Management  Define Movement Types  LE-WM Interface to Inventory Management
PROCEDURE :
WhN R... SpStlnd M... S.. MTy TR Imme...

PC1 101 B CD 901
PC1 101 B FT 902
PC1 312 913 X X
PC1 641 1 L 601 X A
PC1 641 1 L CD 911 X A
PC1 641 1 L FT 912 X A
BACKGROUND :
Every movement type of the inventory management system ('901-912') that is relevant to the
warehouse management system is assigned a reference movement type ('101-641') that the
system can use to determine the movement type in the warehouse management system. The
reference movement type can be used to group inventory management movement types that
result in the same transaction in the warehouse management system.
You can use the stock indicator (‘1’) to distinguish between different processes (such as posting
the goods receipt to unrestricted-use stock or to stock in quality inspection) by means of a
movement type (‘601-912’). The movement indicator specifies the type of document that forms
the basis of the movement, for example, purchase order (‘B’) or delivery note (‘L’).
The indicator for the transfer requirement (‘X’) specifies that a transfer requirement is created for
the article document item. The indicator for the transfer order, however, controls whether transfer
orders are created in the background (‘A’) or by you by means of a transaction (‘X’) once an
article document has been created in inventory management (IM).
REMARKS :

3.2 Lean WM Structures for Merchandise-Driven Flow-

Through
3.2.1 Copy Warehouse Number

PRECONDITIONS :
PATH:
IMG  Enterprise Structure  Definition  Logistics Execution  Define, Copy, Delete,

Check Warehouse Number  Copy/Delete/Check Warehouse Number
PROCEDURE :
[COPY ORG.OBJECT] pushbutton
From warehouse number: '100' ('Lean WM (without stocks)')

To warehouse number: 'PCF' ('PCS Flow-Through (lean)')
BACKGROUND :
The copied warehouse number forms the basis for defining a warehouse. It is easier to use a
copied warehouse number than to create a completely new warehouse.
REMARKS :
The description of the warehouse number should then be changed:

IMG  Enterprise Structure  Definition  Logistics Execution  Define, Copy, Delete, Check
Warehouse Number  Define Warehouse Number (SPRO).
Warehouse number description 'PCF': 'Flow-Through PCS (Lean)' (enter any description)

3.2.2 Maintain Control Parameters and Number Ranges for Warehouse

Number
PRECONDITIONS :
Lean WM warehouse number.
PATH:
IMG  Logistics Execution  Shipping  Picking  Lean WM  Define Control Parameters

and Number Ranges f. Warehouse No. Define Control Parameters and Number Ranges f.
Warehouse No.
PROCEDURE :
Maintain entries, [DETAILS] pushbutton to branch to the detail view
WhN Lean WM Active Weight Unit Volume Unit Transfer Order Gr. No.
PCF x KG M3 01 01
Maintain units of measurement as required.
BACKGROUND :
Number ranges are maintained for transfer orders and reference numbers. The number for the
transfer order (‘01’) indicates a number range that is used to assign consecutive numbers for the
warehouse management reference numbers. The reference number (‘01’) refers to a number
range that you require in order to assign consecutive numbers for the warehouse management
reference numbers.
If lean WM is not activated, you cannot use the ‘Flow-Through Art.’ processing method.
REMARKS :

3.2.3 Define Storage Type

PRECONDITIONS :
PCF warehouse number.
PATH:
IMG  Logistics Execution  Shipping  Picking  Lean WM  Define Storage Type
PROCEDURE :
[NEW ENTRIES] pushbutton or copy existing entries, [DETAILS] pushbutton to branch to the
detail view
WhN Type Storage Type Name Stock Rmvl Requires Confirmation

PCF FTM Flow-Through PCS x
BACKGROUND :
The storage type maps the general structure of the warehouse.

To enable quantity differences to be entered during the picking process (confirmation of the
transfer order), the confirmation requirement has to be activated for stock removal transfer orders.
REMARKS :
Additional storage types can be added in the same way.

3.2.4 Define Shipment Types

PRECONDITIONS :
PCF warehouse number.
PATH:
IMG  Logistics Execution  Shipping  Picking  Lean WM  Define Shipment Types
PROCEDURE :
WhN Shipment Type Text for Shipment Type

PCF A Stock rmvl
BACKGROUND :
Key for the type of goods movement in the warehouse.

You can use the shipment type to classify the individual movements, such as stock removal (‘A’).
REMARKS :

3.2.5 Define Movement Types in Lean WM

PRECONDITIONS :
PCF warehouse number and storage type.
PATH:
IMG  Logistics Execution  Shipping  Picking  Lean WM  Define Movement Types
PROCEDURE :
detail view
WhN MTy Description Cat Shipm. Type TO Creat. Scr. Scr. TO Conf.
PCF 930 FT art. drv. FTM A 2 2
BACKGROUND :
The movement type (‘930’) for lean WM supplies the information that is required for stock
removals, such as the destination storage type (‘FTM’).
REMARKS :

3.2.6 Define Movement Types for Distribution Orders

PRECONDITIONS :
Warehouse number and FRM movement type.
PATH:
IMG  Logistics – General  Merchandise Distribution  Movement Types for Distribution

Orders
PROCEDURE :
Maintain entries
WhN FRM Movement Type

PCF 930
BACKGROUND :
This default movement type is used to create the lean WM transfer orders (distribution orders) for
floor-ready merchandise (FRM).
REMARKS :

3.3 Merchandise Distribution
3.3.1 Define Site Profiles for Merchandise Distribution

PRECONDITIONS :
PATH:
IMG  Logistics – General  Merchandise Distribution  Site Profiles for Merchandise

Distribution
PROCEDURE :
1.: [NEW ENTRIES] pushbutton or copy existing entries, [DETAILS] pushbutton to branch to the
detail view
2.: Select the distribution profile, select the 'Control Data for Each Business Process' subtree,
select the existing entry, [NEW ENTRIES] pushbutton or copy existing entries, [DETAILS]
pushbutton to branch to the detail view

Distr. Prof. of Site Description CD Poss. FT Possible
VPF Distribution profile CD/FT x x

Business Process Description Adjustment Point
01 Push Goods receipt
02 Pull Manual (using separate trans.)
BACKGROUND :
This profile (‘VPF’) is a central control profile for the merchandise distribution process at
distribution center level. In this process, articles are procured under the condition that on
procurement the recipients to which the articles are to be distributed are clearly specified.
You can use different processing methods in the distribution center to distribute articles to the
individual stores or customers. You can use both the cross-docking and flow-through methods .
The indicator for the time of adjustment controls when a given merchandise distribution is to be
adjusted for each business process, that is, for each allocation table (‘01’) or collective purchase
order (‘02’).
REMARKS :
This profile is assigned under Purchasing/Distribution, ‘Distribution profile’ field in the site master
of the distribution center.

3.3.2 Define Adjustment Profiles per Processing Method

PRECONDITIONS :
PATH:
IMG  Logistics – General  Merchandise Distribution  Adjustment Profiles per Processing

Method
PROCEDURE :
detail view
Adjustm .Pr. Description Busin. Proc. Proc. Meth. Rem. Dist

A01 PCS stock placement 01 1 3
A01 PCS stock placement 02 1 3
AP1 PCS distr. proportional 01 2 3
Enter distribution algorithms in the detail view (for example: ‘W_FRM_DISTR_PROPORTIONAL’).
BACKGROUND :
In this step, you define how planned distributions should be brought into line with the quantities
actually delivered. You can either use the allocation table or generate a collective purchase order
to create a planned distribution.
Each business process, that is, each allocation table (‘01’), collective purchase order (‘02’), or
processing method, is controlled individually. Business processes include stock placement (‘1’),
cross-docking (‘2’), flow-through (‘3’), cross-docking/flow-through (‘4’), and cross-docking/stock
placement (‘5’).
In the event of overdeliveries and underdeliveries, you define algorithms to adjust the distribution
of merchandise. If, following adjustment, stock remains, the system provides different methods for
further processing this remaining stock, for example, equal distribution (‘3’). mySAP Retail uses
function modules for this purpose and provides standard processes in function group ‘WFR4’.
You can, however, also include non-standard processes by assigning a function module you
have created.
REMARKS :
The additional standard SAP algorithm is: ‘W_FRM_DISTR_SCHEDULE’.

3.3.3 Define Distribution Profile of Article in DC

PRECONDITIONS :
A suitable profile in the site master data and the adjustment profile for each processing method.
PATH:
IMG  Logistics – General  Merchandise Distribution  Distribution Profile of Article in DC
PROCEDURE :
detail view
Distr. Prof. Description Proc. Method Distr. Meth. Adjustm. Prof.

A01 PCS FTP Allocation 1 1 A01
CD1 PCS VTP CD 2 2 AP1
FT1 PCS VTP FT Merch.-drv. 3 2 AP1
FT2 PCS VTP FT Recipient-drv. 3 1 AP1
OP1 PCS VTP CD/FT 4 2 AP1
OP2 PCS VTP CD/Putaway 5 2 AP1
BACKGROUND :
You use the distribution profile to specify in detail how a specific article is to be distributed in the
distribution center (for example, exactly which processing method should be used, as opposed to
the site profile that only specifies which methods are basically possible).
The distribution method controls how merchandise is distributed by each processing method, that
is, recipient-driven (‘1’) or merchandise-driven (‘2’).
REMARKS :
This profile is assigned to the article under Logistics/DC, ‘General Control Parameters’ field.

3.4 Purchase Order
3.4.1 Define Screen Layout of the Purchase Order

PRECONDITIONS :
PATH:
IMG  Materials Management  Purchasing  Purchase Order  Define Screen Layout at

Document Level
PROCEDURE :
Select the field selection 'ME21N', [DETAILS] pushbutton to branch to the detail view
Double-click the field selection group 'Deadline monitoring'
Field label Opt. Entry

Indicator: Requisition Closed x
BACKGROUND :
This setting is required to enable you to select the indicator for relevance to the allocation table in
the item view of a vendor order.
REMARKS :

3.5 Allocation Table for Customer
3.5.1 Assign Class Type to Application

PRECONDITIONS :
PATH:
IMG  Logistics – General Basic Data Retail  Applications
PROCEDURE :
Application Description Class Type Description

03 Allocation table and 011 Customers
BACKGROUND :
For the allocation table and activity (‘03’), this site group application is used to ensure that a
group of customers is supplied with merchandise, for example. This group is represented by the
class type.
REMARKS :

3.5.2 Copy Sales Document Type

PRECONDITIONS :
PATH:
IMG  Sales and Distribution  Sales  Sales Documents  Sales Document Header 
Define Sales Document Types
PROCEDURE :
[COPY AS...] pushbutton
From sales document type: 'OR' ('Standard Order')

To sales document type: 'ZTAA' ('Standard Order Alloc.')
BACKGROUND :
The sales document types represent the different business transactions in Sales and act as a
central control mechanism for the entire selling procedure.
REMARKS :

3.5.3 Assign Incompleteness Procedures to the Sales Document Types

PRECONDITIONS :
Sales document type exists.
PATH:
IMG  Sales and Distribution  Basic Functions  Log of Incomplete Items  Assign
Incompleteness Procedures Assign Procedures to the Sales Document Types
PROCEDURE :
Maintain entries
SaTy Description
ZTAA Standard Order Alloc.
Remove the incompleteness procedure assignment (‘11’).
BACKGROUND :
The system uses the incompleteness procedure to determine which fields are displayed in the
incompleteness log if the user leaves this blank when processing a sales order. In Customizing
for SD, you can define an incompleteness procedure for each sales document type.
REMARKS :

3.5.4 Copy Item Categories of Allocation Table

PRECONDITIONS :
Sales document type exists.
PATH:
IMG  Logistics – General  Merchandise Distribution  Allocation  Allocation Table  Item

Categories of Allocation Table
PROCEDURE :
1.: [COPY AS...] pushbutton, [DETAILS] pushbutton to branch to the detail view, copy item
category ‘C’ to 'AAF1' and 'AUK1’
2.: [COPY AS...] pushbutton, [DETAILS] pushbutton to branch to the detail view, copy item
category ‘F’ to 'AAFA' and 'AUKA’

Item Cat. Description ShipToParty VO St. Trans. Pro. Me. Ord. Type Sal. Ord. Type
AAF1 PO via DC (Store Order) 1 1 0 NB
AUK1 PO via DC (Sasles Order) 1 3 0 NB ZTAA
Item Cat. Description ShipToParty VO St. Trans. Pro. Me. Ord. Type Sal. Ord. Type
AAFA Use whse stock (Store Order) 1 0
AUKA Use whse stock (Sales Order) 3 0 ZTAA
BACKGROUND :
The item category in the allocation table controls the logistics process from the procurement of an
article to its receipt in the distribution center.
The item category proposes parameters, for example, for the type of
Purchase order
You use the indicator for the ship-to party of the vendor order to control whether a vendor order is
to be generated (‘1’) or not (‘blank’) as well as who the ship-to party is. For the item categories
‘AAF1’ and ‘AUK1’, the ship-to party is the distribution center, for example. In this case, the
standard purchase order (‘NB’) is the order type.
Stock transfer
Here, you specify whether stock is to be transferred from the distribution center to the recipient in
the system by means of store orders (‘1’) or sales orders (‘3’), for example.
The relevant processing method for distributing stock in the distribution center is defined on the
basis of the article master (‘0’), to which the relevant distribution profile is assigned.
REMARKS :

3.5.5 Copy Allocation Table Types

PRECONDITIONS :
The parameters for the item category, notification category, check schema, application, and
number range interval have to be maintained.
PATH:
IMG  Logistics – General  Merchandise Distribution  Allocation  Allocation Table 

Allocation Table Types
PROCEDURE :
1.: [COPY AS...] pushbutton, [DETAILS] pushbutton to branch to the detail view, copy allocation
table type ‘0001’ to 'AAF1' and 'AUK1’
table type ‘0002’ to 'AAFA' and 'AUKA’
table type ‘0005’ to 'AAF2' and 'AUK2’

Alloc. Tbl Type Description Item Category Notification
AAF1 Standard alloc. tbl AAF1 C
AUK1 Standard alloc. tbl (SO) AUK1 A
AAFA PO/sub-cont.ord. ref AAFA C
AUKA PO/sub-cont ref (SO) AUKA A
AAF2 Contract reference AAF1 C
AUK2 Contract ref (SO) AUK1 A
BACKGROUND :
The allocation table type defines various parameters for an allocation table, including default
data, such as the item category or notification category.
The notification category in the allocation table controls the exchange of information between
head office and the stores, and between head office and the distribution centers. The system is
configured in such a way that head office first informs the stores of the allocation tables and,
therefore, the quantities and delivery data of the articles to be distributed. This information is then
confirmed by the stores and the required quantity is specified. This is controlled by notification
category ‘C’ (‘Request notification’). Customers, however, do not receive any notification because
notification category ‘A’ (‘No notification’) is set.
REMARKS :

3.6 SLS Subitems for Cross-Docking
3.6.1 Maintain SLS Profile

PRECONDITIONS :
The relevant site groups must be created and the required sites assigned.
PATH:
IMG  Logistics – General  Merchandise Distribution  Supplementary-Logistics-Services:

Maintain Service Profile
PROCEDURE :
Select the procedure for additionals, select the 'Control Table for Sales Orders' subtree, select
the existing entry, [NEW ENTRIES] pushbutton or copy existing entries
Proc. Event S... SD Doc. Cat. Sales Doc.Type Class Type Class Follow-Up A
0005 Create 1 Order Standard Order 030 PCS-VZ SLS: Pre...
0005 Create 2 Standard Order 030 PCS-VZ SLS: Pre...
0005 Change 1 Order Standard Order 030 PCS-VZ SLS: Pre...
0005 Change 2 Standard Order 030 PCS-VZ SLS: Pre...
BACKGROUND :
If an article is assigned a prepacking service (technically an additional) with the procedure for
additionals '0005', the follow-up actions are determined using this control table.
The sales document type is set to blank when you access the control table for the sales order,
which means that you have to make the entry described above.
Enter the class type and class if you want to limit the site in which the follow-up action is carried
out. An additional is generally assigned once in one DC (in our case 'LZ01').
REMARKS :
The methods and an SLS article (additional) must be assigned to the article master of the article
that is to be prepacked ('Basic Data'/'Additional Data'/'Additional' tab).
The DC of the vendor that carries out prepacking must be assigned the class ’PCS-VZ’ (see
Section 2.2.1).

3.6.2 Adjust Item Category Determination for Sales Documents

PRECONDITIONS :
PATH:
IMG  Sales and Distribution  Sales  Sales Documents  Sales Document Item  Assign
Item Categories
PROCEDURE :
[NEW ENTRIES] pushbutton or copy existing entries and add to existing entries ('TAM | NORM |
| |’), [DETAILS] pushbutton to branch to the detail view
SaTy ItCGr Usg. HLevltCa DfltC MltCa MltCa MltCa

OR NORM TALS TAUL
OR SAMM SLSV TAG TALS
OR SAMM SLSV TAG TAN TAS TAB TAUL
OR SAMM SLSV TALS TAUL TAS TAB TAN
BACKGROUND :
So that you can enter the SLS items in a sales order, you have to determine the corresponding
item categories, in particular for the use of generic articles.
 'TA | NORM | ...' Entry:
'TALS' must also be permitted as an item category in the key combination without ‘SLSV’
because ‘SLSV’ is not determined in the automatic generation of sales orders from
'ORDERS' receipt.
 'TA | SAMM | ...' Entry:
You have to make these entries for generic articles and the SLS in combination with sales
orders. This applies to both the manual creation of sales orders ('TAG' for head item,
'TAN' or 'TAUL' for variants) and the automatic generation of order IDocs (without head
item, 'TALS' for variants, 'TAUL' for SLS subitems).
REMARKS :

3.7 Automatic Generation of Transfer Orders
3.7.1 Create Transportation Groups

PRECONDITIONS :
PATH:
IMG  Logistics Execution  Transportation  Basic Transportation Functions  Routes 

Route Determination  Define Transportation Groups
PROCEDURE :
Trans. Grp Description

0003 CD/FT
BACKGROUND :
WM transfer orders are generated automatically using the combination of transportation groups
and routes. The transportation group is assigned in the article master and analyzed in the route
determination.
REMARKS :

3.7.2 Define Route

PRECONDITIONS :
PATH:

Define Routes  Define Routes And Stages
PROCEDURE :
Route Description
R_WMTA Route cross-docking/flow-through
BACKGROUND :
and routes. Transfer orders are created automatically for all outbound deliveries on this route.
REMARKS :

3.7.3 Set Route Determination

PRECONDITIONS :
Transportation groups and routes are maintained.
PATH:

Route Determination  Maintain Route Determination
PROCEDURE :
Choose the departure country, select the 'Route Determination Without Weight Group (Order)'
subtree, select the existing entries, [NEW ENTRIES] pushbutton or copy existing entries
CDep Name SC Tgroup Proposed

Route
DE Germany 01 0003 R_WMTA
BACKGROUND :
and routes. All the delivery items that include articles with transportation group '0003' are
outsorted in route 'R_WMTA'.
The shipping condition (‘01’) is a general shipping strategy that you use to deliver goods from the
vendor to the recipient.
REMARKS :

3.7.4 Maintain Condition Tables

PRECONDITIONS :
PATH:
IMG  Logistics Execution  Shipping  Basic Shipping Functions  Output Control 

Output Determination  Maintain Output Determination for Outbound Deliveries  Maintain
Condition Tables  Maintain Output Condition Table for Deliveries
PROCEDURE :
Table '502’, [ENTER] pushbutton

The condition tables that are shipped in the standard SAP system should remain unchanged. If
you want to make any changes, you should create new condition tables. To do so, copy an
existing, similar condition table and make the necessary changes to the copy.
Description: ‘Delivery Type/Route’

Subscreen: ‘Selected Fields’
Fields: ‘Delivery Type’ and ‘Route’
[GENERATE] pushbutton
BACKGROUND :
In the condition table, define the combination of fields for which you want to create output
condition records.
REMARKS :
Enter the condition table in the access sequence. This enables you to establish a link between
the output condition record, access sequence, and output condition record.

3.7.5 Maintain Access Sequence

PRECONDITIONS :
Condition tables maintained.
PATH:
IMG  Logistics Execution  Shipping  Basic Shipping Functions  Output Control 

Access Sequences
PROCEDURE :
Select the access sequence, select the 'Accesses’ subtree, select the existing entry, [NEW
ENTRIES] pushbutton or copy existing entries
AcSq Description AcNo Tab

0013 Delivery type/Route 1 502
BACKGROUND :
The access sequence is a search strategy that the system uses to search for valid output
condition records.
REMARKS :

3.7.6 Maintain Output Determination 'WMTA'

PRECONDITIONS :
Access sequence maintained.
PATH:
IMG  Logistics Execution  Shipping  Basic Shipping Functions Output Control 

Output Types
PROCEDURE :
Select the output type, [DETAILS] pushbutton to branch to the detail view, 'General Data' tab,
[DISPLAY <-> CHANGE] pushbutton, maintain entries
Output Type Name Access Seq. Acc. to Cond. Partner-Indep.Output

WMTA Automatic TA 0013 x x
BACKGROUND :
In the SAP system, the output type is used to map different output, such as the automatic transfer
order.
When you set the output as partner-independent, the partner and role specifications in the
system become invalidated.
REMARKS :

3.7.7 Set Lock Logic for Warehouse Number

PRECONDITIONS :
PCS warehouse number.
PATH:
IMG  Logistics Execution  Warehouse Management  Master Data  Define Control

Parameters for Warehouse Number
PROCEDURE :
[DETAILS] pushbutton to branch to the detail view, maintain entries
WhN Region Code Meth. Weight Unit 1st Def. 2nd Def. SU Manag. Act.
PC1 Germany B KG L A x
BACKGROUND :
It is typical for multiple deliveries to be created for the same article. Because the transfer orders
are created automatically immediately after the deliveries, using a blocking logic that is too
restrictive can cause problems. With method ‘B’, several users can work with the same bin at the
same time. Bin stock is synchronized by means of data-carrying blocks; for example, a specific
article is only blocked in the storage bin for the quantity that is currently being processed.
REMARKS :
Check whether or not the delivery output 'WMTA' should be processed with the batch job
'RSNAST00'. This job can be planned in minutes. The creation mode 'Immediate' uses dialog
processes in the system, which can lead to performance problems when mass processing is
carried out.

3.8 Connect the Warehouse to a Site (DC)
3.8.1 Define Storage Location in the DC

PRECONDITIONS :
At least reference DC ('P100') must have been created.
PATH:
IMG  Enterprise Structure  Definition  Materials Management  Maintain Storage

Location
PROCEDURE :
Site 'P100’, [CONTINUE] pushbutton, [NEW ENTRIES] pushbutton or copy existing entries
SLoc Description
0004 PCS FT Recipient
0005 PCS FT Article
0006 PCS Cross-docking
BACKGROUND :
The warehouse number is found via the site/storage location combination. Further storage
locations are used to split stock for inventory management.
REMARKS :
You have to finish customizing the reference DC ('P100') before you can create further sites.
Alternatively, you also have to maintain settings manually for 'VZ01'. This customizing setting is
copied from the reference site when you create sites.

3.8.2 Assign Warehouse Number to Site/Storage Location

PRECONDITIONS :
Warehouse number and reference site must have been created.
PATH:
IMG  Enterprise Structure  Assignment  Logistics Execution  Assign Warehouse Number

to Site/Storage Location
PROCEDURE :
Site SLoc WhN Warehouse No. Description

P100 0004 PC1 Central whse PCS (WM)
P100 0005 PCF PCS flow-through (Lean)
P100 0006 PC1 Central whse PCS (WM)
BACKGROUND :
A lean WM ('PCF') for merchandise-driven flow-through is connected to storage location '0005'.
REMARKS :

3.8.3 Define Storage Conditions

PRECONDITIONS :
PATH:
IMG  Logistics Execution  Shipping  Picking  Determine Picking Location  Define

Storage Conditions
PROCEDURE :
[New Entries]
Maintain the following entries:

SC Description
FT FT customer
BACKGROUND :
The storage condition is maintained in the article master and enables different picking locations to
be used under the same conditions.
REMARKS :

3.8.4 Define Control of "Site/Storage Location – Warehouse Number"

Assignment
PRECONDITIONS :
Warehouse numbers and storage locations exist.
PATH:

Management  Define Storage Location Control  Control of Assignment “Site / Stor.Loc. –
Whse Number”
PROCEDURE :
Maintain entries
Site Stor. Loc. WhNo Standard Stor. Loc. … Storage Loc.

Ref.
P100 0003 PC1 x
P100 0004 PC1 FT
P100 0005 PC1
P100 0006 PC1 CD
BACKGROUND :
Here, you specify that several storage locations are managed for one warehouse number. If
several storage locations are managed for one warehouse number, you now also have to enter
the storage location, whereas before you only had to enter a site for warehouse management
transactions.
The standard storage location can also be specified for each site.
REMARKS :

3.8.5 Define Degree of Activation of Warehouse Management

PRECONDITIONS :
PCS warehouse number, storage location, and storage types exist.
PATH:
IMG  Logistics Execution  Shipping  Picking  Lean WM  Control "Site/Storage

Location/Warehouse No." Assignment
PROCEDURE :
Site Stor. Loc. WhNo Degree of Activatio... Stor.Type For Picking in

Le…
P100 0005 PCF 2 FTM
BACKGROUND :
Key that controls the use or degree of activation of warehouse management for a storage
location.
This controls whether bin inventories are to be managed normally or whether, as in this case,
lean WM for FRM (degree of activation ‘2’) is to be chosen.
REMARKS :

3.8.6 Assign Storage Location Determination with Situation

PRECONDITIONS :
Reference DC; storage locations for the different processes.
PATH:
IMG  Logistics – General  Plant Master  Control Data  Storage Location Determination
PROCEDURE :
Site 'P100’, [CONTINUE] pushbutton, [NEW ENTRIES] pushbutton or copy existing entries
The entry for situation '03' is for cross-docking. The entries for situations '04-06' are for flow-
through.
Situation Description Stor.Conditions Stor.Loc. Description

03 Cross-docking (CD) 0006 PCS Cross-docking
04 Flow-through (FT) 0005 PCS FT Article
04 Flow-through (FT) FT 0004 PCS FT Recipient
05 Merch-driven FT 0005 PCS FT Article
06 Consumer-driven FT 0004 PCS FT Recipient
06 Consumer-driven FT FT 0004 PCS FT Recipient
BACKGROUND :
SAP recommends determining the storage location on the basis of the situation in order to obtain
the right storage location for each different processing method in goods receipt.
REMARKS :
Finish customizing the reference site ('P100') before creating other sites or transfer the settings to
all the DCs that already exist ('VZ01'). These settings will be copied from the reference site when
new sites are created.
The storage condition ‘FT’ must be entered in the basic data of the article master of the article
intended for 'FT recipients'.

Merchandise Distribution - EN - CUST - V147

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

Merchandise Distribution - EN - CUST - V147

Uploaded by

Copyright:

Available Formats

Best Practices for mySAP Retail

Customizing Guide Scenario

Copyright  2003 SAP AG. All rights reserved.

The information contained herein may be changed without prior notice.

SAP, R/3, SAP Retail SAP AG

Merchandise Distribution Scenario Page 3 of 51

Merchandise Distribution Scenario Page 4 of 51

3.5.1 Assign Class Type to Application......................................................................30

Merchandise Distribution Scenario Page 5 of 51

Customizing Guide Merchandise Distribution

 WM warehouse structures (see the “Distribution Center Logistics with Warehouse

 Lean WM warehouse structures for merchandise-driven flow-through

Merchandise Distribution Scenario Page 6 of 51

2.1.1 Customer Grouping for Allocation Table

The class type must be maintained.

1. SAP Menu  Logistics  Retailing  Master Data  Site Data  Grouping 

For 1.: Class type ‘011’, [COPY] pushbutton

Merchandise Distribution Scenario Page 7 of 51

2.1.2 Configure Article for Merchandise Distribution

SAP Menu  Logistics  Retailing  Master Data  Article Data  Article

1.: Select the ‘Basic Data’ view, [ENTER] pushbutton

For 1.: Maintain the following entries:

For 3.: Maintain the following entries:

For 4.: Maintain the following entries:

Merchandise Distribution Scenario Page 8 of 51

For 5.: Maintain the following entries:

Merchandise Distribution Scenario Page 9 of 51

2.2 Basic Data for SLS Subitems and EDI Communication

2.2.1 Vendor Classification for SLS Prepacking

The class type and class must be maintained.

Merchandise Distribution Scenario Page 10 of 51

2.2.2 Customer Article Info for SLS Prepacking

PCS master data must be created.

SAP Menu  Logistics  Retailing  Master Data  Edit Customers  Environment 

Customer: ‘PCS-C381’ (Fashion) ‘PCS-C382’ (Food), ‘PCS-C383’ (Hard goods)

Merchandise Distribution Scenario Page 11 of 51

2.2.3 Maintain Additional for Customer

SAP Menu  Logistics  Retailing  Sales  Additionals  Mass Maintenance 

Customer: ‘PCS-C381’ (Fashion) ‘PCS-C382’ (Food), ‘PCS-C383’ (Hard goods)

Merchandise Distribution Scenario Page 12 of 51

2.2.4 Maintain Additional for Vendor

SAP Menu  Logistics  Retailing  Sales  Additionals  Mass Maintenance 

Purchasing organization: 'E001'

Merchandise Distribution Scenario Page 13 of 51

2.2.5 Maintain Output Condition Records in Sales (at the Vendor)

The output type must be created.

1. SAP Menu  Logistics  Retailing  Master Data  Edit Customers  Messages 

For 1.: Output type 'BA00', [ENTER] pushbutton

For 2.: Output type 'BA00', [ENTER] pushbutton

For 1.: Maintain the following entries:

For 2.: Maintain the following entries:

Merchandise Distribution Scenario Page 14 of 51

2.2.6 Maintain Output Condition Records in Purchasing

If the transfer of prepacking information is to be shown in an integrated scenario by means of

SAP Menu  Logistics  Retailing  Purchasing  Purchase Order  Master Data 

Output type 'NEU', [ENTER] pushbutton

Vendor PartF Medium Date/Time Language

Merchandise Distribution Scenario Page 15 of 51

2.2.7 Maintain Partner Profiles

See Section 2.2.6.

SAP Menu  Tools  Business Communication  IDoc Basis  Administration  Partner

1.: Open 'Partner Type KU'

2.: Open 'Partner Type LI'