141 bb configguide en us internal procurement: cross-company stock transfer

EHP4 for SAP ERP 6.0

June 2010

English

Internal Procurement Cross-Company Stock Transfer (141)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Internal Procurement Cross-Company Stock Transfer (141): Config 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


Content

Internal Procurement Cross-Company Stock Transfer...................................................................5

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

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

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

3 Master Data............................................................................................................................. 5

3.1 Enhance Material Master for New Plant........................................................................5

3.1.1 Sales Data for Material Master..................................................................................7

3.1.2 Purchasing Data for Material Master.........................................................................8

3.1.3 MRP Data for Material Master...................................................................................9

3.1.4 General/Storage Data for Material Master...............................................................10

3.1.5 Warehouse Data for Material Master.......................................................................11

3.1.6 Accounting Data for Material Master.......................................................................11

3.2 Creating Purchase Info Record...................................................................................12

3.2.1 Creating Purchase Info Record for HAWA..............................................................12

4 Configuration.........................................................................................................................13

4.1 Assigning Delivery Type/Checking Rule......................................................................13

4.2 Assigning Document Type, One-Step Procedure, Underdelivery Tolerance...............13

© SAP AG of 14

SAP Best Practices Internal Procurement Cross-Company Stock Transfer (141)

Internal Procurement Cross-Company Stock Transfer

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.

a) If you use PERSONALIZED values (for example "company code 9999" instead of the default value "company code 1000" or "shipping point 8888" instead of default value "shipping point 1000" and so on), replace the DEFAULT values in the descriptions below by your personalized values.

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 Master DataCustomer Master, Vendor Master, both linked to Plant:

3.1 Enhance Material Master for New Plant

UseIn the following sections it is described what to do to enhance a trading material so that it can be used in intercompany procurement. If you want to use other materials in intercompany procurement you will have to do the enhancement steps for those materials accordingly. In this way, the material H11 can be used as an example.

Procedure

© SAP AG of 14

SAP Best Practices Internal Procurement Cross-Company Stock Transfer (141) 1. Access the transaction choosing one of the following navigation options:

SAP ECC Menu Logistics Materials Management Material Master Material Create (General) Immediately

Transaction code MM01

2. On the initial screen, enter the following values and choose Enter:

Field Name Description User Action and Values Comment

Material H11

Material (Copy from…) enter the same material number

3. You will receive an Information message "Material type…copied from master record"

4. Select - Sales: Sales Org. Data 1,- Sales: Sales Org. Data 2,- Sales: Sales: General/Plant Data,- Sales Text,- Purchasing,- Purchase Order Text,- MRP1,- MRP2,- MRP3,- MRP4,- General Plant Data / Storage 1,- General Plant Data / Storage 2,- Warehouse Management 1,- Accounting 1,- Accounting 2,- Choose Enter.


Plant enter new plant (e.g. 1010)

Stor. Location Enter Storage Location (E.g. 1C50)

Sales Org. Required (e.g. 1010)

Distr.Channel Required (e.g. 10)

Warehouse No

if applicable per material type (e.g. 101)

Plant (Copy from) enter plant from which to copy plant data (e.g. 1000)

Sales Org (Copy from) enter sales org. from which to copy sales data (e.g. 1000)

Distr.Channel (Copy from) enter dist. chan. from which to copy sales data (e.g.10)

Warehouse No

enter if different (not the same as in copy structure!)

5. Choose Enter:

© SAP AG of 14


Select views based on the material type of the material being copied. There is no need to select Basic Data or Classification as those views are already created.

Result The Views are selected and the organization data is entered.

To view the material lists run the transaction MM60 or the menu path Logistics → Materials Management → Material Master → Other → Materials List.

3.1.1 Sales Data for Material Master

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

Option 1: SAP Graphical User Interface (SAP GUI)



2. On the initial screen, re-enter the following values from previous step and choose Enter:

Field name Description User action and values Comment

Material H11

3. On the Select View(s) dialog box, select the following:

View name Description User action and values Comment

Sales: Sales Org. Data1

required

Plant enter new plant (for example, 1010)

Sales Organization

enter new sales organization (for example, 1010)

Distribution Channel

10

4. Choose Enter.

5. Choose the Sales: sales org. 1 tab.

6. Choose Conditions and enter the following data.

Field name Description User action and values Comment

CnTy PR00

Amount enter a price:

© SAP AG of 14


H11: for example, 1.755,00

Unit USD

Per 100

UoM EA

7. Choose Back.

8. Go to Sales → Sales org. → screen 2, enter the following values, and choose Enter:


Item category group

Enter as appropriate for material type (e. g. NORM)

9. Go to Sales → Sales org. → general/plant screen and choose Enter.


Availability check

Individ.requirements Y2

Loading group Take the values from another plant (e.g. 0002 crane)

10. Go to the Sales text screen.

11. Enter the text that should appear on sales documents for this material.

12. Choose Next. (Enter doesn't work when the cursor is in a text field)

Result The sales data is entered.

You will need to resume this transaction to continue with the following steps.

3.1.2 Purchasing Data for Material Master





2. On the Initial Purchasing screen, enter the following values.


Purchasing group change as necessary (e.g. 110)

3. Choose Enter.

© SAP AG of 14


Remark:The Purchasing tab page is only relevant for certain material types (not relevant for FERT).

Result The purchasing data is entered.


3.1.3 MRP Data for Material Master





2. On the initial MRP1 screen, enter the following values and choose Enter.


MRP type Take value from plant1 (e.g. PD)

(VB could also be possible)

Lot size Take value from plant1 (e.g. EX)

MRP controller

change as necessary (e.g. 101 )

3. On the MRP2 screen, enter the following values and choose Enter.

Field Name Description User Action and Values

Comment

Special procurement

change as necessary

Prod. Stor. Location

change as necessary

Storage loc. For EP

Take the same kind of location as in plant1 (e.g.1C50

The storage location 1C50 in plant 1010 is a copy of the storage location 1050 of plant 1000 and has the same name.

Stock det. Grp. delete entry

SchedMarging Key

Take value from plant1 (e.g.000)

© SAP AG of 14


Planned Deliv Time

Take value from plant1 (e.g.10)

4. Select the MRP3 screen, enter the following values and choose Enter.


Strategy group change as necessary

Consumption mode change as necessary

Bwd consumption per change as necessary

Fwd consumption per. change as necessary

5. Select the MRP4 screen

6. In Individual/coll, change as necessary.

7. Choose Enter.

Result The MRP data is entered.


3.1.4 General/Storage Data for Material Master





2. Select the initial Plant data/stor. screen, and choose enter.

3. Select the second Plant data/stor. screen, and choose enter.

Result The General/storage data is entered.


3.1.5 Warehouse Data for Material Master

Procedure

© SAP AG of 14

SAP Best Practices Internal Procurement Cross-Company Stock Transfer (141) 1. Access the transaction choosing one of the following navigation options:




2. Select the initial Warehouse mgmt screen, and choose enter.

The Warehouse tab page is only relevant for certain material types.

Result The warehouse data is entered.


3.1.6 Accounting Data for Material Master




Transaction code

MM02

2. On the initial Accounting screen, make the following entries and choose enter.

Field Name

Description User Action and Values Comment

Price unit do not change unless absolutely necessary (see special instructions below)

Take the values from the other plant

Standard price

change as necessary Take the values from the other plant

Moving price

change as necessary Take the values from the other plant

Valuation class

change as necessary (e,g, 3100) Take the values from the other plant

3. Select the second Accounting screen, and choose enter.

© SAP AG of 14


The "Price Unit" is the quantity basis for the standard price. For example, if the standard price is $50 per 1000 units, enter 1000 in the Price Unit field and "50" in the Standard Price field.

Result The accounting data is entered.


3.2 Creating Purchase Info Record3.2.1 Creating Purchase Info Record for HAWA



SAP ECC Menu Logistics Materials Management Purchasing Master Data Info Record Create

Transaction code

ME11

2. On the initial screen, enter the following values and choose Enter:


Vendor 491000

Material H11

Purchasing Org. 1000

Plant 1000

Info Category Standard

3. In General data: Vendor Mat.No, enter optional (if known, enter the vendor's material number).

4. In Puch.Organization Data 1, enter the following values and choose Enter:


Plnd dely time For example 5 days

Purch. group 200

Standard qty enter 10

Tol. Underdl 10%

Tol. Overdl. 10%

© SAP AG of 14


Tax code V1

Net price 1.283 EUR

Price unit per 100 PC

Incoterms EXW VENDOR

5. Choose Save.

Result The info record for Trade material is created.

4 Configuration

4.1 Assigning Delivery Type/Checking Rule

UseThe 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. You can also specify which delivery type is to be used.

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

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

Transaction Code

SPRO

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

3. On the New Entries: Overview of Added Entries screen, enter the following information:

Type SPI DITy. CRI

NB 1000 NLCC RP

NB 1100 NLCC RP

NB 1010 NLCC RP

4. Save your entries.

ResultDelivery types and checking rules are assigned to the purchasing document types.

© SAP AG of 14


4.2 Assigning Document Type, One-Step Procedure, Underdelivery Tolerance

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.

Procedure1. Access the activity using 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

Transaction Code SPRO

2. On the Change View “Order Types for Stock Transport Order”: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, enter the following information:

SPlt Plnt Type

1000 1010 NB

1100 1010 NB

1010 1000 NB

1010 1100 NB

4. Save your settings.

Result You have defined purchasing document type NB for the combination of supplying and receiving plants that do not belong to the same company.

© SAP AG of 14

141 bb configguide en us internal procurement: cross-company stock transfer

Documents