134 bb config_guide_en_in

SAP ECC 6.00

March 2008

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 2008 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, 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 in several other countries all over the world. 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 15


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 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 of 15


Content

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

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

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

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

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

3.2 Defining Allowed Item Categories..................................................................................6

3.3 Linking Purchase Requisition with Document Type.......................................................6

3.4 Setting up Stock Transport Order - Plant.......................................................................8

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

3.6 Defining Shipping Data f. Plants - Order Types f. Stock Transport..............................10

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

3.8 Defining Default Values for Document Type................................................................12

3.9 Defining Texts for Purchase Order..............................................................................13

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

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

© SAP AG of 15


Stock Transfer with Delivery: Configuration Guide

1 PurposeThis configuration guide provides 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 installation guide of this building block.

2 Preparation

2.1 PrerequisitesBefore you start installing this scenario, you must install prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for SAP Best Practices Baseline Package.

3 Configuration

3.1 Defining Document Type UD for Purchase Order

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

Procedure1. Access the transaction choosing one of the following navigation options:

IMG menu Materials Management Purchasing Purchase Order Define Document Types

Transaction code SPRO

2. On the Document Types Purchase Order Change screen, copy the order type of UB Stock transport ord. to UD StockTranspOrderDel for the stock transfer with delivery.

3. Select the document type UB and choose Copy As...

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.

7. The three dependent entries should be copied with the following entries:

Field name Description User action and values Comment

Type UD

© SAP AG of 15


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

8. Choose Save.

3.2 Defining Allowed Item Categories

UseThe purpose of this activity is to define allowed item categories.

Procedure1. Access the transaction choosing one the following navigation options:



2. On the Document Types Purchase Order Change screen, select the line created for item category UD, double-click Allowed item categories and then check the following entries:

Allowed item categories for type UD


Item category U

Text item category Stock transfer

3. Choose Back.

3.3 Linking Purchase Requisition with Document Type

UseThe purpose of this activity is to add the linkage between purchase requisitions and document type.

© SAP AG of 15


Procedure1. Access the transaction choosing one the following navigation options:



2. On the Document Types Purchase Order Change screen, select the line created for item category UD, double-click Link purchase requisition - document type, and then check the following entries:

First entry


Document type NB

Description Purchase requisition

Item category in purchasing document (1)

No entry

Text for item category (1)

Standard


U


Stock transfer

Dialog indicator X

Second entry


Document type NB

Description Purchase requisition


U


Stock transfer

Dialog indicator X


U


Stock transfer

Dialog indicator No entry

3. Choose Back.

© SAP AG of 15


ResultThe order type UD StockTranspOrderDel is defined.

3.4 Setting 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 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


2. On the Change View “Stock Transfer Data”: Overview screen, choose New Entries and make the following entries:

Field name Description User action and values Notes

Plant 1000

Customer no. - plant

491000 Customer's Plant located in Bangalore

Sales organization

1000

Distribution Channel (Other Sales)

10 Direct Sales

Division for intercompany

10 Product division

© SAP AG of 15



billing

Language key EN English


Plant 1100

Customer no. - plant

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

Sales organization

1000

Distribution Channel (Other Sales)

10 Direct Sales

Division for intercompany billing

10 Product division

Language key EN English

3. Choose Back.

3.5 Assigning 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, choose New Entries and then make the following entries:


Purchasing document type

UD Stock transp.ord./SD

Supplying plant in case of stock transport order

1000 Production Plant Plant_1 (1000)

© SAP AG of 15



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


Purchasing document type

UD Stock transp.ord./SD


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

3. Save your entries.

4. Choose Back.

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 Defining Shipping Data f. Plants - Order Types f. 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.

Procedure

© SAP AG of 15


1. Access the transaction choosing one of the following navigation options:

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, choose New Entries and then make the following entries:



1000

Plant 1100

Purchasing Document Type

UD Stock transport or with delivery



Plant_2 (1100)

Plant Plant_1 (1000)




4. Choose Back.

ResultOrder types are assigned to supplying plant and receiving plant.

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. On the Delivery item category determination Overview screen, choose New Entries and make the following entries:

© SAP AG of 15


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


4. Choose Back.

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

3.8 Defining 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


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


T-Code Transaction code ME27




4. Choose Back.

Result

© SAP AG of 15


Order types are assigned as default to specific transactions.

3.9 Defining 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. On the Change View "Texts for Document Header": Overview screen, double-click Texts For Document Header in screen Dialog Structure.

3. On the Change View “Texts For Document Header”: Overview screen, choose New Entries to make the following entries:

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. Double-click Texts for Document Item in screen Dialog Structure.

5. On the Change View “Texts For Document Item”: Overview screen, choose New Entries to make the following entries:

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

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. Double-click Texts for Document Supplement in screen Dialog Structure.

© SAP AG of 15


7. On the Change View “Texts for Document Supplement”: Overview screen, choose New Entries to make the following entries:

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. Double-click Headings in screen Dialog Structure.

9. On the Change View “Headings”: Overview screen, choose New Entries to make the following entries::

Print Operation


Title Document Type

Heading for Doc. No.

1 UD Stock transport order TEXT 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


11. Choose Back.

ResultTexts for purchase order messages are defined.

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

© SAP AG of 15


Messages Purchase Order Create

Transaction code MN04

2. On the Create Output - Conditions Records: Purchase Order screen, enter NEU in the field of Output Type.

3. Choose Key Combination. In the pop up mark the option Purchasing Output Determination: Document Type and choose Enter.

4. On the Create Condition Records (Purchase Order): Fast Entry screen, make the following entries:

Field name User action and values

Document Type UD

Vendor No Entry

Function DP

Medium 1

Date/Time 4

5. Choose Communication and enter the values shown below:

Field name User action and values

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

Number of messages 1

Print immediately X

6. Save your settings.

ResultThe message condition is created for purchase order type UD.

© SAP AG of 15

134 bb config_guide_en_in

Documents

Transcript of 134 bb config_guide_en_in