134 bb configguide en us stock transfer with delivery

EHP4 for SAP ERP 6.0

March 2010

English

Stock Transfer with Delivery (134)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Stock Transfer with Delivery (134): Configuration Guide

Copyright

© Copyright 2010 SAP AG. All rights reserved.

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

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

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

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

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

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

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

© SAP AG of 14


Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

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 TEXTKeys 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 of 14


Contents

Stock Transfer with Delivery (134)..................................................................................................5

1 Purpose................................................................................................................................... 5

2 Preparation.............................................................................................................................. 5

2.1 Prerequisites.................................................................................................................. 5

3 Configuration........................................................................................................................... 5

3.1 Define Document Type UD for Purchase Order............................................................5

3.2 Define Allowed Item Categories....................................................................................6

3.3 Link Purchase Requisition - Document Type.................................................................6

3.4 Set up Stock Transport Order - Plant............................................................................7

3.5 Assign Delivery Type/Checking Rule.............................................................................9

3.6 Define Shipping Data for Plants - Order Types for Stock Transport............................10

3.7 Delivery Item Category Determination for Delivery......................................................11

3.8 Define Default Values for Document Type...................................................................11

3.9 Define Texts for Purchase Order.................................................................................12

4 Master Data........................................................................................................................... 14

4.1 Creating Message Condition for PO Type UD.............................................................14

© SAP AG of 14


Stock Transfer with Delivery (134)

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

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide, located on the SAP Note.

2 Preparation

2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for Baseline. The matrix (an Excel file) is linked on the solution's DVD/website in one of the following two locations:

Content Library

Site Map

3 Configuration

3.1 Define Document Type UD for Purchase Order

UseThe purpose of this activity is to define document type UD for purchase order.

Procedure1. Access the activity using the following navigation options:

IMG Menu Materials Management Purchasing Purchase Order Define Document Types

Transaction Code SPRO

2. Copy the order type UB Stock transport ord. to UD StockTranspOrderDel for the stock transfer with delivery.

3. Select the document type UB and copy (F6).

4. Enter the new type UD and the document type description StockTranspOrderDel.

5. Choose Enter.

6. Confirm the question about objects to be copied with copy all.

© SAP AG of 14

SAP Best Practices Stock Transfer with Delivery (134): Configuration Guide 7. The three dependent entries should be copied with the following entries:

Field name User action and values

Type UD

Doc. type description StockTranspOrderDel

Item number interval 10

Number range in the case of internal number assignment 45

Number range in the case of external number assignment 41

Update group for statistics update SAP

Field selection key UBF

Control indicator for purchasing document type T

3.2 Define Allowed Item Categories




2. Select the line created for item category UD, double-click on Allowed item categories, and check the entries:

Allowed item categories for type UD


Item category U

Text item category Stock transfer

3. Choose Back (F3).

3.3 Link Purchase Requisition - Document Type




2. Select the line created for item category UD, double-click on Allowed item categories, and check the entries:

First entry

© SAP AG of 14



Document type NB

Description Purchase requisition

Item category in purchasing document (1) No entry

Text for item category (1) Standard

Item category in purchasing document (2) U

Text for item category (2) Stock transfer

Dialog indicator X

Second entry


Document type NB

Description Purchase requisition





Dialog indicator No entry

ResultThe order type UD StockTranspOrderDel is defined.

3.4 Set up Stock Transport Order - Plant

Use The purpose of this activity is to maintain the customer number for the receiving plant. This

customer number is used in SD shipping to identify the goods recipient (ship-to party) if it has been specified in Customizing that a stock transfer is to be effected with an SD delivery.You make the following settings for the supplying plant:

o Sales organization

o Distribution Channel (Other Sales)

o Division

The system uses this data to determine the shipping data for the material to be transferred (for example, the shipping point).

Under Assign delivery type/checking rule you specify whether an SD delivery is to be created in the case of a PO with a certain supplying plant in connection with a certain document type and, if so, with which delivery type. The delivery type in Sales (SD) determines how a delivery

© SAP AG of 14


is processed. In the standard system, the delivery type NL is used for inter-plant stock transfers without billing documents.

You specify which document type is to be used for a certain combination of supplying (issuing) plant and receiving plant.


IMG Menu Materials Management à Purchasing à Purchase Order à Set Up Stock Transport Order à Define Shipping Data for Plants

Transaction Code

SPRO

2. On the Change View ”Stock Transfer Data”: Overview screen, enter the following information:

Field name User action and values Notes

Plant Plant_1 (1000)

Customer no. - plant Customer Company 01 Customer of the account group YBAC ‘ship-to party (stock transport)’

Sales organization Sales_organization_1 (1000)

Distribution Channel (Other Sales)

Distribution_Channel_1(10) Intercompany / Other sales

Division for intercompany billing

Division_1 (10) Product division

Language key EN English



Customer no. - plant

NATIONAL_PROD_PLANT_CUSTOMER2 (1100)

Customer of the account group YBAC ‘ship-to party (stock transport)’

Sales organization

Sales_organization_1 (1000)

Distribution Channel (Other Sales)

Distribution_Channel_1(10) Intercompany / Other Sales

Division for intercompany billing

Division_1 (10) Product division

Language key EN English

© SAP AG of 14


3.5 Assign Delivery Type/Checking Rule

Use The purpose of this activity is to specify whether an SD delivery is to be created in the case of a PO with a certain combination of supplying plant and document type.


IMG Menu Materials Management Purchasing Purchase Order Set Up Stock Transport Order Assign Delivery Type and Checking Rule


2. On the Deliveries: Change View ”Stock Transfer Data”: Overview screen, enter the following information:


Notes

Purchasing document type UD Stock transp.ord./SD

Supplying plant in case of stock transport order

Plant_1 (1000) Production Plant Plant_1 (1000)

Delivery type NL Replenishment Dlv.

Checking rule for the availability check

RP Replenishment

Delivery type 1 NL Delivery type within Company

Delivery type 2 NLCC Delivery type Cross Company

3. On the Deliveries: Change View ”Stock Transfer Data”: Overview screen, enter the following information:


Notes

Purchasing document type UD Stock transp.ord./SD


Plant_2 (1100) Distribution Plant Plant_2 (1100)

Delivery type NL Replenishment Dlv.

Checking rule for the availability check

RP Replenishment

Delivery type 1 NL Delivery type within Company

Delivery type 2 NLCC Delivery type Cross Company

4. Save your entries.

© SAP AG of 14


ResultCreating a PO with purchase order type UD and supplying plant Plant_1 or Plant_2 creates a delivery with delivery type NL.

3.6 Define Shipping Data for Plants - Order Types for Stock Transport

UseThe purpose of this activity is to define which document type is to be used for a certain combination of supplying plant and receiving plant.


IMG Menu Materials Management Purchasing Purchase Order Set Up Stock Transport Order Assign Document Type, One-Step Procedure, Underdelivery Tolerance


2. On the Change View ”Order Types for Stock Transport Order”: Overview screen, enter the following information:


Notes


Plant_1 (1000)


Purchasing Document Type UD Stock transport or with delivery

3. On the Change View ”Order Types for Stock Transport Order”: Overview screen, enter the following information:


Notes


Plant_2 (1100)




ResultOrder types are assigned to supplying plant and receiving plant.

© SAP AG of 14


3.7 Delivery Item Category Determination for Delivery

UseThe purpose of this activity is to determine delivery item category for delivery type NL.


IMG Menu Logistics Execution Shipping Deliveries Define Item Category Determination in Deliveries

Transaction Code 0184

2. In the Delivery item category determination screen, enter the following information:

Field name Description Value

DlvT Delivery type NL

ItCG Item category group from material master NORM

Usg Item usage CHSP

ItmC Default item category for delivery NLN

Field name Description Value

DlvT Delivery type LF

ItCG Item category group from material master NORM

Usg Item usage PACK

ItmC Default item category for delivery KLN


ResultThe delivery item category for delivery type NL and LF has been determined.

3.8 Define Default Values for Document Type

UseThe purpose of this activity is to define the default values for the document type in certain transactions.


IMG Menu Materials Management ® Purchasing ® Define Default Values for Document Type

© SAP AG of 14


Transaction Code

SPRO

2. On the Change View ”Default Purchasing Document Type in Transactions”: Overview screen, enter the following information:


TCode (Transaction code) ME27



ResultOrder types are assigned as default to specific transactions.

3.9 Define Texts for Purchase Order

UseThe purpose of this activity is to define the texts for purchase order messages.


IMG Menu Materials Management ® Purchasing ® Messages ® Texts for Messages ® Define Texts for Purchase Order


2. In the Dialog Structure pane, double-click Texts for Document Header.

3. On the Change View ”Texts For Document Header”: Overview screen, enter the following information:

Print Operation

Purchasing Doc. Type

Text Object

Text ID

Print Sequence

Text Name Print Title

1 UD EKKO F01 1

2 UD EKKO F01 1

3 UD TEXT ST 1 ME_PO_REMINDER

7 UD TEXT ST 2 ME_PO_ACKN_REM

4. In the Dialog Structure pane, double-click Texts for Document Item.

5. On the Change View ”Texts For Document Item”: Overview screen, enter the following information:

Print Operation


Item Category

Text Object

Text ID

Text Name

Print Sequence

Print Priority

Print Title

1 UD U EKPO F01 2

1 UD U EKPO F03 1 1

© SAP AG of 14


Print Operation


Item Category

Text Object

Text ID

Text Name

Print Sequence

Print Priority

Print Title

1 UD U EKPO F04 3

1 UD U MATERIAL BEST 1 2

2 UD U EKPO F01 2

2 UD U EKPO F03 1 1

2 UD U EKPO F04 3

2 UD U MATERIAL BEST 1 2

6. In the Dialog Structure pane, double-click Texts for Document Supplement.

7. On the Change View ”Texts for Document Supplement”: Overview screen, enter the following information:

Print Operation


Text Object

Text ID

Print Sequence

Text Name

Print Title

1 UD EKKO F04 1

1 UD EKKO F05 2

1 UD EKKO F13 3

1 UD EKKO F14 4

2 UD EKKO F04 1

2 UD EKKO F05 2

2 UD EKKO F13 3

2 UD EKKO F14 4

8. In the Dialog Structure pane, double-click Headings.

9. On the Change View ”Headings”: Overview screen, enter the following information:

Print Operation


Title Document Type

Heading for Doc. No.

1 UD Stock transport order PO number/date

2 UD Change to Stock transport order

PO number/date

3 UD Expediter relating to Stock transport order

PO number/date

7 UD Expediter re acknowledgment of

Stock transport order

PO number/date


ResultThe texts for purchase order messages are defined.

© SAP AG of 14


4 Master Data

4.1 Creating Message Condition for PO Type UD

UseThe purpose of this activity is to create the message condition for the purchase order type UD.

Procedure1. 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. Enter the data required on the Create Output – Condition Records: Purchase Order screen. Enter the Output Type NEU. Choose Key Combination. In the pop up mark the option Purchase Purchasing Output Determination: Document Type and choose Enter.

3. Enter the data required on the Create Condition Records (Purchase Order): Fast Entry screen. Refer to the following shortcuts for details of the master data required:


Document Type UD

Partner No Entry

Function DP

Medium 1

Date/Time 4

4. Choose Communication and enter the values shown below:


Output device Enter your output device, e.g. LP01 (or LOCL or other printer)

Number of messages 1

Print immediately X

5. Save your settings.

ResultThe message condition is created for purchase order type UD.

© SAP AG of 14

134 bb configguide en us stock transfer with delivery

Documents