345 Erp606 Bb Configguide en It

September 2012

English

Advanced Returns from

Store to Warehouse (345)

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf

Germany

Copyright

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

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

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Icons

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables. EXAMPLE TEXT Names of elements in the system. These include report names,

program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT _{Keys on the keyboard, for example, function keys (such as F2) or the} ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG

Contents

Advanced Returns from Store to Warehouse...5

1 Purpose... 5

2 Preparation... 5

2.1 Prerequisites... 5

3 General Configuration... 6

3.1 Configuration of Store Return / Return Plant to Plant...6

3.2 Assigning Partner Determination Procedure to Delivery Type...6

3.3 Configuration of Movement Types 671...7

3.4 Configuration of Work Area for Movement Types 671...7

3.5 Customization of Follow-up Document Types for Store Returns...8

3.6 Assigning Goods Receiving Points for Inbound Deliveries...8

3.7 Setting the Default Order Type for Delivery Type...9

3.8 Specifying Copy Controls for Deliveries...9

4 Creating Master Data... 10

Advanced Returns from Store to Warehouse

1 Purpose

This configuration guide provides the information you need to set up the configuration of this building block manually.

2 Preparation

Prerequisites

Before you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix

(Prerequisites_Matrix_[xx]_EN_IT.xls; the placeholder [xx] depends on the SAP Best

Practices version you use, for example, CP_WSD_ERP606 refers to the SAP Best Practices for Consumer Products and Wholesale Industries Package for this edition:

Prerequisites_Matrix_CP_WSD_ERP606_EN_IT.xls). This document can be found on the SAP Best Practices documentation DVD in the folder

../../CP_WSD_ERP606_IT/Documentation.

3 General Configuration

Configuration of Store Return / Return Plant to Plant

Use

In this step, you define shipping-specific data for store returns, which is the return delivery of goods from one plant to another.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Materials ManagementPurchasingPurchase

OrderReturns OrderStore Return / Return Plant to Plant 2. On the Change View ”Store returns” :Overview screen, make for example the following

entries:

Cat Type SPlt Del. type Del.Ty.Ret

F UB2 1000 Blank LLR

F UB2 1100 Blank LLR

F UB2 1010 Blank LLR

© SAP AG

Assigning Partner Determination Procedure to

Delivery Type

Use

In this activity, you define the rules that should be used to perform automatic partner determination.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Logistic ExecutionShippingBasic Shipping

FunctionsPartnersSet Up Partner Determination for Deliveries

2. On the Change View “Partner Determination Procedures”: Overview screen, choose Partner Determination Procedure LF, and double-click Partner Determination Procedure Assignment.

3. Make the following entries:

Dlv. Type Name Part.Det.Proc

ELR IC Returns Delivery LF

4. Choose Save.

Configuration of Movement Types 671

Use

The SAP R/3 System uses movement types to process movements in Inventory Management (for example, goods receipt for a purchase order or goods issue to a cost center). When the system recognizes a movement as being relevant for Warehouse Management, it assigns this movement to a WM movement type by means of a table.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Logistics ExecutionShippingPickingLean WMDefine Movement Types

with Warehouse No. 100 and Movement Type 671. 3. Choose Details.

4. On the Change View “Movement Types in Lean WM”: Details screen and make the following entries:

Field name Description User actions and values Note

Src+Cat 902

Src+ Stor. Bin IN-ZONE

Shipment Type E

TO creation screen 1

Scr. TO confirmation 1

Print Code 01

TO item can be confirm

immed. Selected

5. Choose Save.

Configuration of Work Area for Movement Types 671

Procedure

1. Access the activity using one of the following navigation options:

Transaction code OMJJ

IMG menu Materials Management Inventory Management and Physical InventoryMovement TypesCopy, Change Movement Types

2. On the popup window Field Selection, select Movement Type, Choose Continue. 3. On the popup window Determine Work Area: Entry, enters movement type 671, and

chooses Enter.

4. On the Change View “Movement Type”: Details screen, double-click Allowed Transactions.

5. Choose New Entries and make the following entries:

Field name Description User actions and values Note

MvT 671

TCode VL32N

© SAP AG

Customization of Follow-up Document Types for Store

Returns

Use

In this IMG activity, you specify the purchase order types ( purchasing document types of

purchasing document category F Purchase Order) that the system uses to automatically create logistical follow-up documents in Advanced Returns Management for store returns depending on the logistical follow-up activity you specify in the Material Inspection in Warehouse transaction. You assign these purchase order types to the initial purchase order types for store returns.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Logistics - GeneralAdvanced Returns

ManagementGeneral SettingsAutomatic Creation of Follow-Up DocumentsMapping Document Types and Return ReasonsSpecify Follow-Up Document Types for Store Returns

2. On the New Entries: Overview of Added Entries screen, make the following entries:

Store Ret. RTV Store Ret. cc

StoreRet STO cc STO

UB2 NB2 UB2 NB2C UB NB

3. Choose Save.

Assigning Goods Receiving Points for Inbound

Deliveries

Use

In this IMG activity, you assign one or several goods receiving points to the combination plant/storage location. If you assign several, you can specify a priority.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Logistics ExecutionShippingBasic Shipping FunctionsShipping Point and Goods Receiving Point Determination Assign Goods Receiving Points for Inbound Deliveries

Setting the Default Order Type for Delivery Type

Use

In this IMG activity, you assign the default order type to delivery type.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Logistics ExecutionShippingDeliveriesDefine Delivery Types

2. Select the item with delivery type ELR, and choose Details. 3. Enter DLRE in the field of Default ord.ty.

4. Choose Save.

Specifying Copy Controls for Deliveries

Use

You define control data for the document flow of deliveries.

Procedure

1. Access the activity using one of the following navigation options:

Transaction code VTLA

IMG menu Logistics ExecutionShippingCopying ControlSpecify Copy Control for Deliveries

2. On the Display View Header: Overview screen, choose Display <> Change (Ctrl+F1). 3. Choose Position… to find the entry with delivery type ELR and sales document type

DLRE.

4. Select the entry item and choose Details. 5. Make the following entries:

From SalesDo c Type Target deliver y type Order requirem ents Combination requirmt Heade r Data Heade r Data Ext. Sys Handlin g Units Copy item numbe r DLRE ELR 301

6. Make the following entries for Item:

Item

category Order requirements Item data Item Ext. System Business data Update document flow Pos./neg. quantity ELLR 302 + © SAP AG Page 9 of 10

8. Choose Back.

Result

Controls are copied.

4 Creating Master Data

Creating Output Condition Record for PO

Procedure

1. Access the activity using one of the following navigation options:

SAP ECC menu LogisticsMaterials ManagementPurchasingMaster DataMessagesPurchase OrderCreate

Transaction code MN04

2. On the Create Output-Condition records: Purchase Order screen, enter output type NEU and choose Enter.

3. In the Key combination dialog box, select Purchasing Output Determination: Document Type and choose Enter.

4. On the Create Condition records (Purchase Order): Fast Entry screen, enter the following values and choose Enter:

Doc. Type Funct Partner Medium Date/Time

UB2 DP 1 4

5. Choose Communication.

6. On the Create Condition records (Purchase Order): Communication screen, make the following entries:

Field name Description User actions and values Note

Output Device LP01 Number of messages 1 Print Immediately Selected 7. Choose Save.

Result

The condition records are created. For output type NEU the system automatically generates an output message.