utilities_building_blocks_china_master data logistics _192_bb_configguide.doc

35
SAP ECC 6.0 EhP3 August 2008 English Master Data Logistics (SP) (192) Building Block Configuration Guide

Upload: ksureshkumar

Post on 27-Jan-2016

217 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP ECC 6.0 EhP3

August 2008

English

Master Data Logistics (SP) (192)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

Page 2: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): 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.

SAP, R/3, xApps, xApp, 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 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 Page 2 of 26

Page 3: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

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 Page 3 of 26

Page 4: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Contents1 Purpose................................................................................................................................... 6

2 Preparation.............................................................................................................................. 6

2.1 Prerequisites..................................................................................................................6

3 Configuration........................................................................................................................... 6

3.1 MM General Settings.....................................................................................................6

3.1.1 Defining Material Groups...........................................................................................6

3.1.2 Defining Industry Sector............................................................................................7

3.2 SD General Settings......................................................................................................7

3.2.1 Defining Condition Types..........................................................................................7

3.2.2 Defining Document Pricing Procedure......................................................................8

3.2.3 Defining Pricing Procedures......................................................................................9

3.2.4 Checking Master Data Relevant For Account Assignment......................................10

3.2.5 Assigning G/L Accounts..........................................................................................11

3.2.6 Defining and Assigning Pricing Procedures.............................................................12

3.2.7 Defining the Sales Document Type.........................................................................12

3.2.8 Defining Scheduling By Sales Document Type.......................................................14

3.2.9 Assigning Incompletion Procedures........................................................................14

3.2.10 Assigning Pricing Procedure to Sales Document Types.........................................15

3.2.11 Assigning Sales Area to Sales Document Types....................................................16

3.3 Master Data: HCM.......................................................................................................16

3.3.1 Creating Employee..................................................................................................16

3.4 Master Data: Material..................................................................................................18

3.4.1 Creating Material Master.........................................................................................18

3.4.2 Flagging the Valuation Material...............................................................................20

3.5 Master Data: Customer................................................................................................20

3.5.1 Creating Customer Master Data..............................................................................20

3.6 Master Data: Vendor...................................................................................................22

3.6.1 Creating Vendor Master Data..................................................................................22

3.6.2 Creating Vendor Master Data for Travel..................................................................23

3.7 Output Control Data Records......................................................................................25

3.7.1 Creating Condition Records BA00...........................................................................25

3.7.2 Creating Condition Records RD00..........................................................................25

3.8 Pricing Conditions........................................................................................................26

3.8.1 Creating Condition Record......................................................................................26

© SAP AG Page 4 of 26

Page 5: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Master Data Logistics (SP)

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 to use an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide.

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 (Prerequisites_Matrix_[xx]_EN_CN.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, BL refers to the SAP Best Practices Baseline Package: Prerequisites_Matrix_BL_EN_CN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\BBLibrary\General\.

3 Configuration

3.1 MM General Settings

3.1.1 Defining Material Groups

Use

With material groups you group materials with the same attributes or purpose. You can use material groups to limit the scope of analyses and systematically search for material master records via match codes.

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

Transaction code OMSF

IMG menu Logistics – General Material Master Settings for Key Fields Define Material Groups

2. Activities

Create the Material Groups by choosing the button New Entries and type in the following data:

Fields Data Data

Matl. Group YBSVM1 YBSVS1

Material Group Desc. Spare parts SP-Services

© SAP AG Page 5 of 26

Page 6: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Grp.

DUW

Description 2 for the material group Spare parts Services

Result The material groups are defined.

3.1.2 Defining Industry Sector

Use

In this step, you check the industry sectors and, if necessary, create new ones. You use the industry sector to determine which fields require an entry when maintaining material master data and which fields do not.

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

Transaction code OMS3

IMG menu Logistics – General Material Master Field Selection Define Industry Sectors and Industry-Sector-Specific Field Selection

2. Activities

Create the Industry Sector by selecting the Industry Sector 1, choose the button Copy As and type in the following data:

Fields Data

Industry Sector S

Industry Description Services

Field reference A

ResultThe industry sector is defined.

The material master can be created.

3.2 SD General Settings

3.2.1 Defining Condition Types

Use

Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.

© SAP AG Page 6 of 26

Page 7: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.

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

Transaction code SPRO

IMG menu Sales and Distribution->Basic Functions-> Pricing->Pricing Control->Define Condition Types-> Maintain Condition Types

2. Activities

Maintain condition types YBS1 and YBS2 by copying standard condition type K005, accept all associated copy controls and ensure the following primary settings:

Tab page Fields YBS1 YBS2

Condition type SP: Surcharge SP: Realization %

Access seq. K305 PPAR

Control data1 Cond.class A A

Calculat.type A A

Plus/minus A Positive X Negative

Rounding rule Commercial Commercial

Changes which can be made

Item condition x x

Delete x x

Amount/percent x x

Master data Delete fr. DB Do not delete Do not delete

Scales Scale basis B value scale

Text determination TextDetPrc 02 Discounts/surcharges

Text ID 0001 Internal comment

3. Save your entries

ResultThe condition types are created.

3.2.2 Defining Document Pricing Procedure

UseIn the pricing procedure, you define which condition types should be taken into account and in which sequence. During pricing, the SAP system automatically determines which pricing procedure is valid for a business transaction and it takes the condition types contained in it into account one after the other.

© SAP AG Page 7 of 26

Page 8: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

The determination of the procedure depends on the Document pricing procedure; you specify the document pricing procedure for each sales document type.

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

Transaction code SPRO

IMG menu Sales and Distribution Basic Functions Pricing Pricing Control Define And Assign Pricing Procedures Define document pricing procedure

2. Activities:

Define the pricing procedure S for Services by clicking on the button New entries and type in the following data:

Fields Description

DoPr S

Description Services

ResultThe pricing procedure for service scenarios is created.

3.2.3 Defining Pricing Procedures

Use

In the pricing procedure, you define which condition types should be taken into account and in which sequence. During pricing, the SAP System automatically determines which pricing procedure is valid for a business transaction and it takes the condition types contained in it into account one after the other.

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

Transaction code SPRO

IMG menu Sales and Distribution Basic Functions Pricing Pricing Control Define And Assign Pricing Procedures Maintain pricing procedures

2. Activities:

Maintain the pricing procedure YBA002 Service Providers by copying the standard pricing procedure RVAA01 Standard. Add the following new lines by clicking on button New Entries:

Field Line Line

Step 30 40

© SAP AG Page 8 of 26

Page 9: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Cntr

CTyp YBS1 YBS2

Description SP: Surcharge SP: Realization %

From

To

Man.

Required

Stat

Print X X

SubTo

Reqt 2 2

AltCTy

AltCBV

ActKy ERL ERS

Accrls

ResultThe pricing procedure for Service Providers is defined.

3.2.4 Checking Master Data Relevant For Account Assignment

Use

In the following menu options, you define the control of revenue account determination for transferring billing values from the SD module to the FI module. Revenue account determination is carried out using the condition technique.

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

Transaction code SPRO

IMG menu Sales and Distribution Basic Functions Account Assignment/Costing Revenue Account Determination Check Master Data Relevant For Account Assignment

2. ActivitiesDouble-click Materials: Account Assignment Groups. Define a new account assignment group that will be entered in the material master and used for revenue account determination.

Fields Description

Acct Assignment Grp Y3

Description Travel Expenses RRB

© SAP AG Page 9 of 26

Page 10: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

ResultThe new account assignment group Travel Expenses RRB was generated and is the basis for the account determination for the Travel Expenses.

3.2.5 Assigning G/L Accounts

Use

In this menu option, you allocate G/L accounts for revenue account determination. You have to make the allocation for every access sequence you have defined beforehand. A variety of criteria is valid for a G/L account, depending on the key combination. For the key combination ‘Cust.Grp/MaterialGrp/AcctKey’ a G/L account depending upon the following criteria, for example, is given:

Application (key for SD application)

Condition type for account determination

Chart of accounts (from the module FI)

Sales organization

Customer account determination group

Material account determination group

Account key

PrerequisitesYou have to make the allocation for every access sequence you have defined beforehand.

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

Transaction code VKOA

IMG menu Sales and Distribution Basic Functions Account Assignment/Costing Revenue Account Determination Assign G/L Accounts

2. Activities:

Double-click ‘Cust.Grp/MaterialGrp/AcctKey’ and choose New Entries. Make the following entries:

App CndTy. ChAc SOrg. AAG AAG ActKy G/L acct Prov.acc.

V KOFI YBCN 1000 1 Y1 ERL 60010303  

ResultThe revenue account determination was set to find the right account in FI.

© SAP AG Page 10 of 26

Page 11: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

3.2.6 Defining and Assigning Pricing Procedures

Use

To determine the procedure, you allocate the customer determination procedure and the document pricing procedure to a pricing procedure within a sales area.

Prerequisites You have defined the pricing procedure.

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

Transaction code OVKK

IMG menu Sales and Distribution Basic Functions Pricing Pricing Control Define And Assign Pricing Procedures Define Pricing Procedure Determination

2. Activities:

Go to the button New Entries and type in the following data:

SOrg. DChl Dv DoPr CuPP PriPr. CTyp

1000 10 10 S 1 YBAA02 PR00

Result The pricing procedure determination for Service Providers is defined.

3.2.7 Defining the Sales Document Type

UseThe sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for. The Sales Document Types used for this business scenario are the Sales Order and the Debit Memo Request.

PrerequisitesSales area 1000, 10, 10 has been set up.

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

Transaction code VOV8

IMG menu Sales and Distribution Sales Sales Documents Sales Document Header Define Sales Documents Types

© SAP AG Page 11 of 26

Page 12: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

2. Activities

Create the Sales Document Types YBO1 and YBDR by copying standard document types OR and DR respectively; accept all associated copy controls and ensure the following primary settings. The sales document type YBDR is created first and is used as Billing Request in sales document type YBO1.

Tab Page Fields YBDR YBO1

Description SP: Debit Memo Req SP: SD-Order

SD Doc Category L C

Number systems No.RangeIntAssgt 15 01

No.RangeExtAssgt 16 02

Item no.increment 10 10

Subitem increment 10 10

General Control Check Division 2

Probability 100

Credit Group 01

Output Application V1

Item Division X

Read Info Record X X

Transaction flow Screen Seq Group GA AU

Transaction Group 0 0

Doc Pricing Proc S S

Display Criteria UALL UALL

Fcode for Over Scr UER2 UER1

Prod.Attr.messages A

Billing Order-Rel Bill Type L2 L2

Intercomp.bill.type IV

Billing Block 09

Cnd Type Line Item EK01 EK02

Billing Plan Type 02

Paymt.guarant.proc. 01 01

Paymt. Card plan type 03 03

Checking group 01 01

Requested del date Propose deliv.Date X X

Contract Billing Request YBDR

ResultThe new sales document types are created.

© SAP AG Page 12 of 26

Page 13: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

3.2.8 Defining Scheduling By Sales Document Type

UseIn this step you define for sales document types whether delivery scheduling and/or transportation scheduling should be carried out.

Prerequisites The sales order types have been created.

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

Transaction code SPRO

IMG menu Sales and Distribution Basic Functions Delivery Scheduling and Transportation Scheduling Define Scheduling By Sales Document Type

2. We do not need any scheduling in our scenario. Therefore we have to delete all entries depending on our sales document types.

Fields YBDR YBO1

Description SP: Debit Memo Req SP: SD-Order

DlvSchedlg blank blank

TranspSchd deselect deselect

Backwards deselect deselect

ResultWe do not have any scheduling in our scenario.

3.2.9 Assigning Incompletion Procedures

UseIn the following activities, you define when a sales document should be regarded as incomplete and how the system should respond when you create a document.

Prerequisites The sales order types have been created.

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

Transaction code VUA2

IMG menu Sales and Distribution Basic Functions Log of Incomplete Items Assign Incompleteness Procedures

© SAP AG Page 13 of 26

Page 14: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

2. We do not need any scheduling in our scenario. Therefore we have to delete all entries depending on our sales document types.

Fields YBDR YBO1

Description SP: Debit Memo Req SP: SD-Order

Proc. 15 blank

Description Debit Memo blank

IC-Dialog deselect deselect

Result Only the Debit Memo Request has an incompletion log assigned.

3.2.10Assigning Pricing Procedure to Sales Document Types

UseIn the pricing procedure, you define which condition types should be taken into account and in which sequence. During pricing, the SAP system automatically determines which pricing procedure is valid for a business transaction and it takes the condition types contained in it into account one after the other.

The determination of the procedure depends on the Document pricing procedure; you specify the document pricing procedure for each sales document type.

PrerequisitesThe sales order types have been created.

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

Transaction code SPRO

IMG menu Sales and Distribution Basic Functions Pricing Pricing control Define and Assign Pricing Procedures

2. ActivitiesDouble-click Assign document pricing procedures to order types. Define or assign the document procedure as listed in the table below:

Sales Type YBDR YBO1

Sales Document Type SP: Debit Memo Req SP: SD-Order

Document Procedure S S

Result You have specified the document pricing procedure for each sales document type.

© SAP AG Page 14 of 26

Page 15: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

3.2.11Assigning Sales Area to Sales Document Types

Use

In this menu option, you allocate the allowed order types to each sales area group. You do not need to make any entries at all if all the sales order types are allowed for each of your sales areas.

PrerequisitesYou must define common sales organizations, common distribution channels and common divisions.

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

Transaction code SPRO

IMG menu Sales and Distribution Sales Documents Sales Document Header Assign Sales Area To Sales Document Types Assign sales order types permitted for sales areas

2. ActivitiesDouble-click Assign sales order types permitted for sales areas. Go to the button New Entries and type in the following data:

Ref.SOrg. RefDistCh. RefDivDoc SaTy Name Name Name Description

1000 10 10 YBO1 Inland Direct Sales

Product Division 10

SP: SD-Order

Result You have assigned the allowed sales document types to the sales area.

3.3 Master Data: HCM

3.3.1 Creating Employee

UseIn this step, you create employees.

Procedure

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

SAP ECC menu Human Resources Personnel Management Administration HR Master Data Personnel Actions

Transaction code PA40

2. Select action type Hiring Service Provider.

© SAP AG Page 15 of 26

Page 16: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

3. In the From field, enter 2007.01.01 and in the Personnel no. field, enter 999101.(Repeat the following steps for personnel numbers 999102, 999103, ...)

4. Choose Execute.

5. On the screen Create Actions maintain the data as shown in the table below:

Personnel number

Position Employee Group

Personnel Area

Employee Subgroup

999101 1 1000 Y1

999102 1 1000 Y1

999103 1 1000 Y1

999201 1 1000 Y1

999202 1 1000 Y1

999203 1 1000 Y1

999301 1 1100 Y1

999302 1 1100 Y1

6. Choose Enter.

7. Save your entries.

8. On the screen Create Organizational Assignment maintain the data as shown in the table below:

Personnel number

Cost Center Personnel Subarea Payroll Area

999101 1321 1010 YB

999102 1321 1010 YB

999103 1321 1010 YB

999201 1321 1010 YB

999202 1321 1010 YB

999203 1321 1010 YB

999301 1602 1110 YB

999302 1501 1120 YB

9. Choose Enter.

10. Save your entries.

11. On the screen Create Personnel Data, maintain the data as shown in the table below:

PersNo Title Last Name First Name Birth Date Language Nationality

999101 Mr 红 张 1960.12.10 ZH CN

999102 Mrs 杰 李 1960.03.03 ZH CN

999103 Mr 健 孙 1960.04.14 ZH CN

999201 Mr 强 王 1958.03.30 ZH CN

© SAP AG Page 16 of 26

Page 17: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

999202 Mrs 丽 赵 1956.05.13 ZH CN

999203 Mr 瑞 宋 1960.10.13 ZH CN

999301 Mrs 红 张 1960.12.10 ZH CN

999302 Mr 杰 李 1960.03.03 ZH CN

12. Choose Enter.

13. Save your entries.

14. On screen Create Planned Work time enter Work schedule rule YB00.

15. Choose Enter.

16. Save your entries.

17. On screen Create Travel Privileges set Flag Changes Permitted to Trip in area Company Code Changes.

18. Choose Enter.

19. Save your entries.

20. On screen Create Time Sheet Defaults, maintain the data as shown in the table below:

Personnel number Controlling Area Cost Center Activity Type

999101 1000 1321 8

999102 1000 1321 8

999103 1000 1321 8

999201 1000 1321 101

999202 1000 1321 101

999203 1000 1321 102

999301 1000 1602 9

999302 1000 1501 9

3.4 Master Data: Material

3.4.1 Creating Material Master

UseThe purpose of this activity is to create the material master data.

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

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

© SAP AG Page 17 of 26

Page 18: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Transaction code MM01

2. On the Create Material: Initial screen, enter the following values for each single material and choose Enter.

Field name User action and values Comment

Material D300

Industry sector S - Services

Material type DIEN

3. Select the following views: Basic Data 1, Basic Data 2, Sales: Sales Org Data 1, Sales: Sales Org Data 2 and Sales: General/Plant Data and enter the following values.

Field name Description User action and values Comment

Plant Plant 1 (1000)

Sales Org Inland (1000)

Distr. Channel Direct Sales (10)

4. Choose Enter.

5. On the Basic Data 1 screen, enter the following values.

Field name Description User action and values Comment

Material Description Short Text Consulting 1 FP

Base Unit of Measure H

Material Group YBSVS1 SP-Services

GenItemCatGroup LEIS

6. On the Basic Data 2 screen no entries have to be made.

7. On the Sales: Sales Org Data 1 screen, enter the following values:

Field Description Values1 Comment

Delivering Plant Plant 1 (1000)

Cash Discount X

Tax Data/Tax Category MWST

Tax Classification 1

8. On the Sales: Sales Org Data 2 screen, enter the following values:

Field Description Values1 Comment

Acct Assignment grp Y1 (Service Provider)

9. On the Sales: General/Plant Data screen, enter the following values:

Field Description Values1 Comment

Profit Center YB700 (Service)

10. Save your entries.

© SAP AG Page 18 of 26

Page 19: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

3.4.2 Flagging the Valuation Material

UseThe purpose is to set the FIFO flag for the material master data.

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

SAP ECC menu Logistics Materials Management Valuation Balance Sheet Valuation FIFO Valuation Prepare Select Materials

Transaction code MRF4

2. On the FIFO Valuation: Flag Materials screen, enter the following values for each single material and choose Enter.

Field name User action and values Comment

Material D300

LIFO/FIFO Set

3. Choose Excute.

3.5 Master Data: Customer

3.5.1 Creating Customer Master Data

Use The SAP Baseline Package scenarios require several different customers.

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

SAP ECC menu Logistics Sales and Distribution Master Data Business Partner Customer Create Complete

Transaction code XD01

Business role Customer Service

2. Choose Customer Create: Initial screen. Make the following entries:

Customer Name Account Group Cmpny Code Sales Org. Sales. Ch.

100100 天傲科技 YB01 1000 1000 10

3. Choose Enter.

4. Choose the Create Customer: General Data Address Tab and make the following entries:

Customer Name 1 Name 2 SearchTerm Street House No.

100100 天傲科技 服务 天山路 600 1

© SAP AG Page 19 of 26

Page 20: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Customer Postal Code City Country Region Time Zone

100100 201205 上海 CN 020 UTC+8

Customer Telephone Fax

100100 52534599 06227700

5. Choose the Company Code Data button.

6. Choose the Create customer: Company code data: Account management tab.

7. Enter the Recon. Account, Sort key, Cash Managmt group and Previous Master Record No.:

Customer Recon. Account

100100 11220101

8. Choose Create customer: Company code data: Payment transactions tab.

9. Enter Terms of Payment,

Customer Terms of Payment

100100 0001

10. Choose the Sales Area Data button.

11. Choose the Create customer: Sales Area Data: Sales tab.: Enter following Data

Customer sales district Sales Office Sales Group customer group currency

100100 CNY

Customer order probab.

Price group

customer pricing procedure

price list Customer statistics group

100100 01 1

12. Choose the Create customer: Sales Area Data: Shipping tab and make the following entries:

Customer Delivery priority

shipping conditions

Delivering Plant (Own or External)

Relevant for POD processing

Order

Combination

max. partial deliv.

100100 02 (Normal item)

01 (Standard)

   9

13. Choose the Create customer: Sales Area Data: Billing document tab and make the following entries:

Customer Invoicing Dates

Price determination

Incoterms Incoterm description

Terms of payment

100100 01 X FH 0001

Customer Acct assgmt group tax classification

100100 01 1

© SAP AG Page 20 of 26

Page 21: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

14. Choose Save.

ResultThe customer master data has been created.

3.6 Master Data: Vendor

3.6.1 Creating Vendor Master Data

UseThe service scenarios require one vendor.

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

SAP ECC menu Logistic->logistics Execution->Master Data->Partner->Vendors->Create

Transaction code XK01

2. Select the Create vendor: Initial Screen, and make the following entries:

Company Code 1000

Purchase Organization 1000

Account Group Vendor Name

YB01 300100 Vendor Services

3. On the Create Vendor: Address screen, make the following entries, and then choose Next Screen. (F8).

Vendor Name 1 Name 2 Search Term Street Postal Code City

300100 供应商服务 服务 张江高科碧波路

201203 上海

Vendor Country Region Time Zone

Transp. Zone

Langu. Tel. Phone Fax

300100 CN 020 UTC+8 0000000002 ZH 50806566 50806666

4. On the Create Vendor: Control screen, make the following entries, and then choose Next Screen (F8) twice.

Vendor Custom. No. Trading Partner

300100

5. On the Create Vendor: Payment transactions screen, enter the following data:

Vendor Bank country key Bank Keys Bank account number

© SAP AG Page 21 of 26

Page 22: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

300100 CN 88917866 252525

6. On the Create Vendor: Accounting information accounting screen, make the following entries, and then choose Next Screen (F8).

Vendor Recon. account Sort Key Cash mgmnt goup

300100 22020101 009 (Ext.doc number) A1 (Domestic)

7. On the Create Vendor: Payment transactions accounting screen, make the following entries, and then choose Next Screen (F8) twice.

Vendor Payt Terms Chk double inv. Payment Methods

300100 0001 X BCEU

8. On the Create Vendor: Purchasing data screen, make the following entries:.

Vendor Order Currency

Incoterms

GR. Based Inv.

Autom. EvalGR Setmt Del.

Auto. Purch. order

Returns Vend.

Ship. Cond.

300100 CNY FH X X 01

9. Choose Save.

ResultThe vendor master data has been created.

3.6.2 Creating Vendor Master Data for Travel

UseThe service scenarios require one vendor.

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

SAP ECC menu Logistic->logistics Execution->Master Data->Partner->Vendors->Create

Transaction code XK01

2. Select the Create vendor: Initial Screen, make the following entries, and then choose Enter.

Company Code 1000

Purchase Organization 1000

Account Group Vendor Name

YB01 YB999101 Vendor Services

3. On the Create Vendor: Address screen, make the following entries, and then choose Next Screen. (F8).

Vendor Name 1 Name 2 Search Term Street Postal Code City

© SAP AG Page 22 of 26

Page 23: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

YB999101

Vendor Services

SERVICES Altrottstrasse 1

69120 Walldorf

Vendor Country Region Time Zone Transp. Zone

Langu. Tel. Phone Fax

YB999101

CN 02 UTC+8 0000000002 ZH 62277110 62277111

4. On the Create Vendor: Control screen, make the following entries, and then choose Next Screen (F8) twice.

Vendor Custom. No. Trading Partner

YB999101

5. On the Create Vendor: Payment transactions screen, enter the following data:

Vendor Bank country key Bank Keys Bank account number

YB999101 CN 88917866 123456790

6. On the Create Vendor: Accounting information accounting screen, make the following entries, and then choose Next Screen (F8).

Vendor Recon. account Sort Key Personnel number

YB999101 22410102 009 (Ext.doc number) 999101

7. On the Create Vendor: Payment transactions accounting screen, make the following entries, and then choose Next Screen (F8) twice.

Vendor Payt Terms Chk double inv. Payment Methods

YB999101 0001 X OPSU

8. On the Create Vendor: Purchasing data screen, make the following entries:

Vendor Order Currency

Incoterms

GR. Based Inv.

Autom. EvalGR Setmt Del.

Auto. Purch.order

Returns Vend.

Ship. Cond.

YB999101

CNY FH X X 01

9. Choose Save.

10. Repeat the steps to create other vendors:

YB999102

YB999103

YB999201

YB999202

YB999203

© SAP AG Page 23 of 26

Page 24: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

ResultThe vendor master data has been created.

3.7 Output Control Data Records

3.7.1 Creating Condition Records BA00

UseIn this activity you determine the values for which a message should be found. You define the message attributes, for example the processing time or the language.

PrerequisitesThe sales order types have been created.

Procedure1. Access the transaction choosing the following navigation:

SAP ECC menu Logistics Sales and Distribution Master Data Output Sales Document Create

Transaction code VV11

2. Select the following Output Type to create an output condition record for:

Output Types Name Sales Organization SalesDocTy Funct Partner

BA00 Order Confirmation 1000 YBO1 SP

Output Types Name Medium Date/Time Language

BA00 Order Confirmation 1 4

3. Choose Save.

ResultThe output condition record for the sales document has been created.

3.7.2 Creating Condition Records RD00

UseIn this activity you determine the values for which a message should be found. You define the message attributes, for example the processing time or the language.

PrerequisitesThe billing document types have been created.

© SAP AG Page 24 of 26

Page 25: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

Procedure1. Access the transaction choosing the following navigation:

SAP ECC menu Logistics Sales and Distribution Master Data Output Billing Document Create

Transaction code VV31

2. Select the following Output Type to create an output condition record for:

Output Types Name Sales Organization Bill.Type Funct Partner

RD00 Invoice 1000 L2 BP

Output Types Name Medium Date/Time Language

RD00 Invoice 1 4

3. Choose Save.

ResultThe output condition record for the billing document has been created.

3.8 Pricing Conditions

3.8.1 Creating Condition Record

UseThe purpose of this activity is to create a condition record for a customer price depending on the material.

PrerequisitesThe customer and material master have been created.

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

SAP ECC menu Logistics Sales and Distribution Master Data Conditions Select Using Condition Type Create

Transaction Code VK11

2. On the Create Condition records screen, enter Condition type PR00 and choose Enter.

3. Select the Key combination material with release status

4. On the Create Price Condition (PR00): Fast Entry screen, make the following entries:

Use the following data:

Condition Type

Sales Organization

Distribution Channel

Material Description Amount

© SAP AG Page 25 of 26

Page 26: Utilities_Building_Blocks_China_Master Data Logistics _192_BB_ConfigGuide.doc

SAP Best Practices Master Data Logistics (SP) (192): Configuration Guide

PR00 1000 10 D300 Consulting 1 FP Price (f.ex.: 1200)

Condition Type Unit Per UoM Valid from Valid to

PR00 CNY 1 H Start date End date

5. Choose Save.

ResultThe price condition record for pricing has been created.

© SAP AG Page 26 of 26