sap tm

EHP5 for

SAP ERP 6.0

October 2011

English

Prerequisite Settings and Master Data (ERP) (T55)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Prerequisite Settings and Sample Master Data (T55): Configuration Guide

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, Clear Enterprise, SAP BusinessObjects Explorer, 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 SAP France in the United States and in other countries.

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 57


Icons

Icon Meaning

Caution

Example

Note

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 57


Content

1 Purpose 6

2 Preparation 7

2.1 Prerequisites............................................................................................................7

3 Configuration 7

3.1 Enterprise Structure in SAP ERP............................................................................7

3.1.1 Check Plant.........................................................................................................7

3.1.2 Check Assignment of Plant to Company Code....................................................8

3.1.3 Check Storage Location......................................................................................9

3.1.4 Check Transportation Zones...............................................................................9

3.1.5 Check Transportation Planning Points for Shipment Integration with SAP TM..10

3.1.6 Check Shipping Conditions...............................................................................11

3.1.7 Check Loading Groups......................................................................................12

3.1.8 Check Shipping Point........................................................................................13

3.1.9 Maintain Country and Transportation Zone for Shipping Point..........................14

3.1.10 Check Shipping Point Determination.................................................................14

3.1.11 Check Picking Location Assignment..................................................................15

3.2 Settings for Material Master Data..........................................................................15

3.2.1 Check or Maintain ISO Codes...........................................................................15

3.2.2 Define Transportation Groups...........................................................................16

3.3 Settings for Carrier Master Data............................................................................17

3.3.1 Define Partner Procedure for Carriers...............................................................17

3.3.2 Define Account Group for Carriers....................................................................18

3.3.3 Define Partner Roles per Account Group..........................................................18

3.3.4 Assign Account Group to APO Location Type...................................................19

3.3.5 Define Number Range for Carriers....................................................................19

3.3.6 Assign Number Range to Account Group..........................................................20

3.4 Settings for Document Types................................................................................20

3.4.1 Check Sales Order Type in SAP ERP...............................................................20

3.4.2 Check assigned Sales Areas to Sales Document Type.....................................21

3.4.3 Check Delivery Type.........................................................................................21

3.4.4 Check Transportation Relevance for Delivery Type..........................................22

3.5 Route Determination..............................................................................................22

3.5.1 Define Routes....................................................................................................22

3.5.2 Maintain Route Dependent Scheduling.............................................................24

3.5.3 Define Route Determination..............................................................................25

4 Master Data 29

4.1 Creating Customer Master Data............................................................................29

© SAP AG of 57


4.2 Create Carrier Master Data...................................................................................38

4.3 Assign Default Carrier to Route YT9999................................................................44

4.4 Create Material Master Data..................................................................................45

4.4.1 Basic Data.........................................................................................................46

4.4.2 Sales Data.........................................................................................................48

4.4.3 MRP Data..........................................................................................................49

4.4.4 General Plant Data /Storage Data.....................................................................49

4.4.5 Accounting Data................................................................................................50

4.4.6 Costing Data......................................................................................................50

4.4.7 Repeat steps for further materials.........................................................................51

4.4.7.1 Basic Data.....................................................................................................52

4.4.7.2 Sales Data.....................................................................................................52

4.4.7.3 MRP Data......................................................................................................53

4.4.7.4 General Plant Data /Storage Data.................................................................53

4.4.7.5 Accounting Data............................................................................................54

4.4.7.6 Costing Data.................................................................................................54

5. Appendix 55

5.2 Reversal of Process Steps for Customer...............................................................55

5.3 Reversal of Process Steps for Carrier...................................................................55

5.4 Reversal of Process Steps for Material..................................................................55

© SAP AG of 57


Prerequisite Settings and Sample Master Data: Configuration Guide

1 PurposeThe purpose of this document is to describe the general configuration steps required to manually set up configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.

If you do not want to configure manually and would prefer to run an automated installation process using BC Sets and other tools, refer to the quick guide for your SAP rapid-deployment solution.

This document supplements the existing Customizing documentation in the Implementation Guide (IMG) and provides additional information where required.

The Customizing and master data described in this document are required to set up an SAP ERP system to test and demo the capabilities of SAP Transportation Management rapid-deployment solutions.

Since the described configuration and master data focuses on the bare minimum required for testing and showcasing the scenarios covered with the SAP Transportation Management rapid-deployment solutions, the following restrictions apply if you are using sample master data described in this guide:

Sales orders and outbound deliveries can be created without inventory in the assigned storage location. To do this, switch off the availability check in the material master data.

Warehouse functions are not used in the scenarios. For this reason, the proposed picking storage location is not assigned to a warehouse number. The material master data therefore has to be maintained for a storage location, but not for a warehouse number.

You can of course include these other processes in your SAP ERP productive system or, if you are using your own test data, in your SAP ERP development and test system.

Your SAP ERP system must meet the following prerequisites:

Sales order processing, including sales order scheduling, is already configured and running

Outbound delivery processing is configured and running Shipment processing is configured and running

You can use this guide to check whether all required settings have been made in your own system.

In SAP ERP, sales order scheduling is a mandatory prerequisite for SAP Transportation Management integration. For sales order scheduling we use routes as part of the sample content of the rapid-deployment solution. If you are using your own SAP ERP data, you can follow a different approach for sales order scheduling.

If you are using you own SAP ERP system, you cannot use the eCATTs and BC sets provided as part of the SAP Transportation Management rapid-deployment solutions to set up the configuration and master data described below.

© SAP AG of 57


2 Preparation

2.1 PrerequisitesBefore you start installing this scenario, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for your SAP rapid-deployment solution. You will find this document in the Content Library, attached to the step-by-step guide.

Before you implement the configuration and master data described below, you have to set up best practice US baseline building blocks. For more information, see the Quick Guide for your SAP rapid-deployment solution.

3 ConfigurationThis section describes all of the settings required for this building block. These settings fall into the following three main groups:

Prerequisite settings that have to be checked and were delivered by SAP (as part of the standard delivery)

The term Check used in this document refers to these prerequisite settings.

Settings defined by the customer (customer-specific settings and those defined in the customer namespace):

The system uses automation to request individual customer settings during the personalization process. These settings can be initial or reused from existing SAP ERP layers and are indicated in the text by <your value>.

Additional settings that need to be made either by automation or manual configuration (in the customer namespace)

The term Create in the text refers to these additional settings.

3.1 Enterprise Structure in SAP ERP

For the sample master data of the rapid-deployment solution, we use a SAP Best Practices US baseline organizational structure. The following sections describe which organizational entities are used and whether they have to be adapted for the SAP Transportation Management rapid-deployment solutions.

3.1.1 Check Plant

UseThe SAP Transportation Management rapid-deployment solutions use plant 1000 for the sample configuration in SAP ERP.

You can use your own plant for implementation in your productive system.

Procedure

1. Choose:

Transaction Code SPRO

© SAP AG of 57


Customizing Menu Enterprise Structure Definition Logistics – General Define Plant

2. Choose Define Plant.

3. Choose the Choose pushbutton

4. Select Details

5. Check the following data:

Field Name Input Value

Plant 1000

Name 1 Plant 1

Name 2 Plant 1

6. Check the following data:


Title Company

Name Plant 1

Search Terms 1/2 Plant 1

Postal Code 94304

City Palo Alto

Country US

Region CA

Time Zone PST

Factory Calendar US

Language Key EN

7. Choose the Enter pushbutton

8. Choose the Back pushbutton

3.1.2 Check Assignment of Plant to Company Code

UseA plant has to be assigned to a company code to enable stock valuation and almost all of the accounting functionalities. Accounting is not a part of the test scenarios of the SAP Transportation Management rapid-deployment solutions; however, assignment to a company code is necessary just to be able to maintain mandatory accounting data for sample customers, vendors, and materials.

Procedure

1. Choose:

Transaction Code OX18

Customizing Menu Enterprise Structure Assignment Logistics - General Assign Plant to Company Code

2. Check that the following combination of values exists:

© SAP AG of 57



Company Code 1000

Plant 1000

3. Choose the Exit or Back pushbutton to exit this activity.

3.1.3 Check Storage Location

UseStorage locations are needed for picking material in outbound delivery items. The picking process itself is not relevant for the test scenarios of the SAP Transportation Management rapid-deployment solutions. Deliveries can be created without predetermined storage locations. Nevertheless, at least one storage location should be defined in every plant.

For the sample content of the rapid-deployment solution in SAP ERP, storage location 1020 (shop floor) is assigned to plant 1000. Storage location 1020 is not assigned to a warehouse number, meaning that picking activities can be performed in this storage location without confirming transfer orders in SAP ERP warehouse management.

Procedure

1. Choose:

Transaction Code OX09

Customizing Menu Enterprise Structure Definition Materials Management Maintain Storage Location

2. Check the following entries


Plant 1000

Storage location 1020

Description Shop floor

3. Choose the Back (F3) pushbutton.

3.1.4 Check Transportation Zones

UseTransportation zones are part of the sample master data of the SAP Transportation Management rapid-deployment solutions. They are assigned to business partners’ address data and to shipping points for route determination in SAP ERP. These sample zones are not used in SAP Transportation Management.

If you have transportation zones in your ERP system, they have to be replicated in SAP Transportation Management if they are relevant for transportation planning. Transportation zones are not replicated individually, but using the master data object to which they are assigned (customer master records). Also, the sample zones contained in the rapid-deployment solution are replicated in SAP Transportation Management, but they are not used in SAP Transportation Management.

© SAP AG of 57


Procedure

1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Transportation Basic Transportation Functions Routes Route determination Define Transportation Zones

2. Check the following transportation zones for country US:


Zone / Description US00010000 / Pacific N.W.

Zone / Description US00020000 / Southwest

Zone / Description US00030000 / Southeast

Zone / Description US00040000 / Northeast

Zone / Description US00050000 / Rockies

Zone / Description US00060000 / Midwest

3. Choose the Back (F3) pushbutton

3.1.5 Check Transportation Planning Points for Shipment Integration with SAP TM

Use

To create shipments in ERP, you require a transportation planning point.

Shipments in SAP ERP can be created by SAP Transportation Management directly or created in SAP ERP and replicated to SAP Transportation Management.

With SAP Transportation Management, you have to use different transportation planning points for the two integration points:

For ERP shipments created by SAP Transportation Management, you have to determine exactly one transportation planning point that will later have to be maintained as a transportation planning point for external systems (see Configuration Guide T58).

For shipments created in SAP ERP and replicated to SAP Transportation Management (tendering rapid-deployment solution only), you have to use different transportation planning points that are NOT defined as a transportation planning point for external systems.

Check the transportation planning points in your system and identify the one that is relevant for ERP shipment creation from SAP Transportation Management and those relevant for shipment creation in SAP ERP.

You CANNOT use the same transportation planning point for both options.

Note the transportation planning points for later usage when you configure your respective integration scenario:

T58: Shipment integration TM to ERP T59: Shipment integration ERP to TM

© SAP AG of 57


Procedure

4. Choose:


Customizing Menu Enterprise Structure Definition Logistics – Execution Maintain Transportation Planning Point

5. Please check the following entries:

Transportation planning point used for ERP shipments created in SAP Transportation Management:


Transportation Planning Point

1000

Description Transp. 1000

Company Code 1000

Transportation planning point used for shipments created in SAP ERP and mapped to SAP Transportation Management:


Transportation Planning Point

0001

Description Transp. 0001

Company Code 0001

6. Choose the Back (F3) pushbutton

For ERP shipments created in SAP Transportation Management, transportation planning point 1000 is used as the default for value mapping within SAP NetWeaver Process Integration. If you want to use a different transportation planning point, you will need to maintain value mapping within SAP NetWeaver Process Integration. For more information, see Configuration Guide T66.

3.1.6 Check Shipping Conditions

UseShipping conditions can be assigned to sales order types or customer master data. The SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses shipping conditions for shipping point and route determination in SAP ERP.

Shipping conditions can also be used in SAP Transportation Management to influence transportation planning. In SAP Transportation Management, they are mapped to transportation service level codes, which can be used in freight unit building rule determination.

See the following table for the shipping conditions used in the SAP Transportation Management rapid-deployment solutions.

© SAP AG of 57


You can use your own shipping conditions for implementation in your productive system. Identify the shipping conditions you want to use for the purposes mentioned below.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point Determination Define Shipping Conditions

2. Please check the following entries


SC / Description 01 / Standard (used as default in sample customer master data of SAP Transportation Management rapid-deployment solutions; not used in SAP Transportation Management rapid-deployment solutions however)

SC / Description 02 / Pick-up (used to differentiate sales orders in SAP Transportation Management if domestic transportation planning and domestic freight tendering rapid-deployment solutions are running in the same SAP Transportation Management client; see also Configuration Guide T64 for the domestic freight tendering rapid-deployment solution).

SC / Description 04 / Transport Service (used to avoid transfer of sales orders to SAP Transportation Management in domestic freight tendering rapid-deployment solution where only the ERP shipments created for those ERP sales orders have to be transferred to SAP Transportation Management)

3.1.7 Check Loading Groups

UseThe SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses loading group 0001 for shipping point determination in SAP ERP.

You can use your own loading groups for shipping point determination relevant for SAP Transportation Management integration for implementation in your productive system.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point Determination Define Loading Groups

2. Check the following entries


LGrp / Description 0001 / Crane

3. Choose the Back pushbutton

© SAP AG of 57


3.1.8 Check Shipping Point

UseShipping point is a mandatory field in SAP ERP outbound delivery header data. Every outbound delivery is assigned to exactly one shipping point.

The SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses shipping point 1000. The shipping point is replicated to SAP Transportation Management via the Core Interface (CIF, see T70 configuration guide) and used as the source destination.

For implementation in your productive system you can use a shipping point that already exists in your SAP ERP system.

Procedure1. Choose:


Customizing Menu Enterprise Structure Definition Logistics – Execution Define, copy, delete, check shipping point

2. Choose Define shipping Point.

3. Choose the Choose pushbutton.

4. Check the following entries:


Shipping Point 1000

Description Shipping Point 1000

5. Double-click Shipping Point 1000

6. Check the following entries (you will make further entries in section Maintain Country and Transportation Zone for Shipping Point) below:


Name Shipping Point 1000

Factory calendar US

Determining loading time A (Route-dependent)

Determining pick/pack time A (Route-dependent)

7. Go to address data to check country, departure zone, and time zone.


Title Company

Name Shipping Point 1000

Country US

Transportation Zone US00020000

To see this field, choose More Fields.

Time Zone PST (Pacific Time, Los Angeles)

8. Choose the Enter pushbutton.

9. Choose the Exit pushbutton (or Save if you have changed any data).

© SAP AG of 57


You assign a country and transportation zone for each shipping point of your relevant enterprise structure in the following activity. These assignments are needed for route determination.

3.1.9 Maintain Country and Transportation Zone for Shipping Point

UseIn the SAP ERP sample configuration used for the SAP Transportation Management rapid-deployment solutions, routes are used for sales order scheduling. To enable route determination of shipping points, you have to assign a country and transportation zone to the shipping point.

This setting is not required if you will not be using route determination and instead have a different approach to sales order scheduling.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Transportation Basic Transportation Functions Routes Route determination Maintain Country and Transportation Zone for Shipping Point



Shipping Point 1000

Country US

Zone US00020000

3.1.10 Check Shipping Point Determination

UseIn the SAP ERP sample configuration used for the SAP Transportation Management rapid-deployment solutions, shipping point determination is configured for shipping point 1000 to allow a shipping point to be determined for outbound deliveries.

For implementation in your productive system, you will need to configure shipping point determination for your own shipping point.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Basic Shipping Functions Shipping Point and Goods Receiving Point Determination Assign Shipping Points


© SAP AG of 57



Shipping condition 01 / 02 / 03 / 04

Loading Group 0001

Plant 1000

Proposed Shipping Point 1000

3. Choose the Back(F3) pushbutton

3.1.11 Check Picking Location Assignment

UseSAP WM is not included in the SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions. We therefore assign storage location 1020 as the picking location.

Storage location 1020 is not assigned to a warehouse number. As a result, picking activities can be performed at this storage location without having to confirm transfer orders in SAP ERP warehouse management.

For implementation within your productive system, you can use a storage location that supports warehouse processes in SAP ERP.

Material master records have to be maintained for this storage location.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Picking Determine Picking Location Assign Picking Locations

2. Please check and/or maintain the following entries:


Plant 1000

Shipping Point 1000

Shipping Condition (blank) Leave blank

Storage Location 1020

If an entry already exists with the same plant, shipping point, and shipping condition, change this entry accordingly.

3.2 Settings for Material Master Data

© SAP AG of 57


3.2.1 Check or Maintain ISO Codes

Use

Message interfaces between SAP ERP and SAP Transportation Management use ISO codes. Make sure that the ISO code is assigned to each unit of measure you are using in both systems.

An ISO code is not included with the SAP standard Customizing for some units of measure. You will have to maintain the ISO code for these units of measure at least.

Check that any other units of measure you want to use have ISO codes assigned. The data transfer to TM will fail if no ISO code is assigned.

Procedure1. Choose:

Transaction Code CUNI

3.2.1.1 Customizing Menu

SAP Customizing Implementation Guide SAP NetWeaver General Settings Check Units of Measurement

2. To check the ISO codes, select all relevant Volume units of measure:


Units of measurement VOLUME Volume

3. Select Units of measurement, and double-click FT3. On the ALE/EDI pane, you will find the field ISO Code.


ISO code FTQ

4. Repeat steps 2 and 3 with the following data:


Units of measurement MASS Mass

Unit LB

ISO Code LBR

5. Save your entries.

3.2.2 Define Transportation Groups

Use

The SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses routes for sales order scheduling and transportation groups for route determination.

Within the SAP Transportation Management rapid-deployment solution Domestic Transportation Planning, transportation groups are also used to control incompatibilities in SAP Transportation Management. For more information, see Configuration Guide T65.

© SAP AG of 57


This setting is not required if you will not be using route determination and instead have a different approach for sales order scheduling, and if you are not using incompatibilities in SAP Transportation Management.

Note that different transportations groups are relevant for outbound delivery split.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Sales and Distribution Basic Functions Routes Route Determination Define Transportation Groups

2. Enter the following:


Transportation Group / Description

YTC1 / chemical1


YTC2 / chemical2


YTC3 / chemical3


YTS1 / solid 1


YTS2 / solid 2


3.3 Settings for Carrier Master Data Within the SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions, we use a separate account group for vendors in SAP ERP in order to identify vendors as carriers in SAP Transportation Management. This account group has to be assigned to APO location type 1020 TSP in order to identify those vendors as carriers in SAP Transportation Management.

The following sections describe the required settings in SAP ERP.

Other than assignment to APO location type 1020, the following settings are not required if you have your own accounting group for carriers (or forwarding agents) in SAP ERP.

3.3.1 Define Partner Procedure for Carriers

Use

© SAP AG of 57


Within the SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions, we use a separate own partner procedure for carriers, which allows us to use one of our own partner functions for carriers.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Materials Management Purchasing Partner Determination Partner Settings in Vendor Master Records Define Partner Schemas

2. Define the following new entries for the partner determination procedure by choosing the New Entries pushbutton:


Partner Schema / Description

Y1 / RDS TM Carrier

3. Assign the following partner function for procedure Y1 by selecting the procedure you have just created and double-clicking folder Partner Functions in Procedure:


Partner function CR Forwarding Agent

No Change

Mandatory X

4. Save.

3.3.2 Define Account Group for Carriers

UseWithin the SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions, we use our own account group for carriers, which allows us to use one of our own number ranges for carriers.

Procedure

1. Choose:

Transaction Code OMSG

Customizing Menu SAP Customizing Implementation Guide Logistics – General Business Partner Vendors Control Define Account Groups and Field Selection (Vendor)

2. Choose the New entries pushbutton

3. Enter the following data:


Account Group YTFA

Description TM RDS Carriers

Partner schema, purch. org.

Y1

4. Choose the Enter pushbutton and save your entries.

© SAP AG of 57


The number range will be assigned in 3.3.6.

3.3.3 Define Partner Roles per Account Group

UseHere, you define the possible partner functions/roles per account group.

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Materials Management Purchasing Partner Determination Partner Roles Define Permissible Partner Roles per Account Group

2. Define the following new entries for partner functions:


Function CR (Forwarding Agent)

Account Group YTFA (TM RDS CARRIERS)


3.3.4 Assign Account Group to APO Location Type

UseAn account group is assigned to the APO location type in order to allow vendors to be identified as carriers in SAP Transportation Management.

Procedure1. Choose:


Customizing Menu in SAP ERP

SAP Customizing Implementation Guide Integration with Other mySAP.com Components Advanced Planning and Optimization Application-Specific Settings and Enhancements Settings and Enhancements for Shipments Assign vendor Account Group to APO location Type

3. Enter the following data:


Account Group YTFA

Location Type 1020 TSP

© SAP AG of 57


3.3.5 Define Number Range for Carriers

UseHere, you define the number range for carrier master records.

Procedure1. Choose:

Transaction Code OMSJ

Customizing Menu SAP Customizing Implementation Guide Logistics - General Business Partner Vendors Control Define Number Ranges for Vendor Master Records Intervals

2. Define the following new interval by choosing Intervals and Insert Interval pushbuttons:


Number Object Vendor

Interval Y5

From Number 0000500000

To number 0000599999

External X

3.3.6 Assign Number Range to Account Group

UseThe number range interval is assigned to the account group.

Procedure1. Choose:

Transaction Code OMSJ

Customizing Menu SAP Customizing Implementation Guide Logistics - General Business Partner Vendors Control Define Number Ranges for Vendor Master Record Number Range

2. Define the following new interval by choosing Number Range:


Group YTFA (TM RDS Carriers)

Number range Y5


3.4 Settings for Document Types

3.4.1 Check Sales Order Type in SAP ERP

UseThe SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses sales order type OR.

© SAP AG of 57


For implementation in your productive system you can use your own sales order type.

Procedure

1. Choose:

Transaction Code VOV8

Customizing Menu SAP Customizing Implementation Guide Sales and Distribution Sales Sales Documents Sales Document Header Define Sales Document Types

2. Check that sales order type OR has been maintained.

3. Double-click sales order type OR and check that it has been assigned delivery type LF:


Sales Document Type OR (TA)

Description Standard Order

Delivery Type LF

4. Choose the Back pushbutton.

3.4.2 Check assigned Sales Areas to Sales Document Type

UseSales orders have to be created for sales areas. The relevant sales order types have to be assigned to each sales area.

For implementation in your productive system you can use your own sales area.

Procedure

1. Choose:


Customizing Menu SAP Customizing Implementation Guide Sales and Distribution Sales Sales Documents Sales Document Header Assign Sales Area to Sales Document Types

2. Choose Assign sales order types permitted for sales areas followed by the Choose pushbutton.



Ref. S (Reference sales org.for sales doc.types (by sales area))

1000 (TM RDS Scenario)

RefD (Distribution channel for sales doc types


Div (Reference division for document types (by sales area)


© SAP AG of 57



Sales Document Type OR (or other relevant sales order types)


3.4.3 Check Delivery Type

UseThe SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses delivery type LF.

For implementation in your productive system you can use your own delivery type.

Procedure

1. Choose:

Transaction Code OVLK

Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Deliveries Define Delivery Type

2. Double-Click Delivery types LF



Delivery Type LF

Description Delivery (SAP Standard Delivery Type)

Document Category J


3.4.4 Check Transportation Relevance for Delivery Type

UseTo assign an ERP delivery to an ERP shipment, the ERP delivery type has to be relevant for transportation.

Procedure

1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Transportation Shipments Maintain Transportation Relevance

2. Choose Maintain transportation relevance for delivery types followed by the Choose pushbutton.



Delivery type LF (or any other relevant delivery type)

© SAP AG of 57



Rel. Transport X


3.5 Route Determination

If you are using SAP Best Practices Solution Builder to automatically implement sample SAP ERP content for the TM rapid-deployment solutions, you can use BC Sets to implement all the settings described below.

3.5.1 Define Routes

UseThe SAP ERP sample configuration for the SAP Transportation Management rapid-deployment solutions uses routes for sales order scheduling and shipment processing.

For implementation in your productive system you can use your own routes.

Procedure

1. Choose:

Transaction Code 0VTC

Customizing Menu SAP Customizing Implementation Guide Logistics Execution Transportation Basic Transportation Functions Routes Define Routes Define Routes and Stages


Customizing Menu SAP Customizing Implementation Guide Sales and Distribution Basic Transportation Functions Routes Define Routes Define Routes and Stages


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Routes Define Routes Define Routes and Stages

2. Choose the New Entries pushbutton:

Enter the following:


Route YT0001

Description One calendar day of Transit Duration,

Transit Time (duration in calendar days)

1

TransLdTm. (Transportation lead time in calendar days)

1

© SAP AG of 57



Factory Calendar US

Service Agent blank

Rel.transport (Relevance for transportation)

X

3. Repeat step 2 with following data:


Route YT0003

Description Three calendar days Transit Duration

Transit Time 3


1

Factory Calendar US

Service Agent blank


X

4. Repeat step 2with the following data:


Route YT0008

Description Eight calendar days Transit Duration

Transit Time 8


1

Factory Calendar US

Service Agent blank


X

5. Repeat step 2 with the following data for ERP Shipment Integration (T59):


Route YT9999

Description Default Carrier 599999 (see 4.2)

Transit Time 9


1

Factory Calendar US

© SAP AG of 57



Service Agent 599999 (can be assigned if vendor master data were created before, see 4.2. Leave this field empty, if default carrier 599999 does not exist up to now. You can assign this default carrier later).


X

6. Save your entries and choose the Back pushbutton.

3.5.2 Maintain Route Dependent Scheduling

Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Basic Shipping Functions Scheduling Delivery Scheduling and Transportation Scheduling Maintain Duration

2. Select Pick/Pack Time from the dialog structure on the left


Shipping Point 1000

Route YT0001/ YT0003/ YT0008/ YT9999

Pick/Pack days 1 day

3. Select Loading Time from the dialog structure on the left. Default for the lead time in days should be 1 day; see also loading group 0001. Loading group 0002 should be 2 days.


Shipping Point 1000

Route YT0001

Loading Group Blank

Loading Time days 1.00

4. Repeat step 3 and enter data according to the table below:

Loading Group / Route

YT0001 YT0003 YT0008 YT9999

Blank 1 1 1 1

0001 1 1 1 1

0002 2 2 2 2

5. Save your entries and choose the Back pushbutton.

3.5.3 Define Route Determination

© SAP AG of 57


Procedure1. Choose:


Customizing Menu SAP Customizing Implementation Guide Sales and Distribution Basic Transportation Functions Routes Route Determination Maintain Route Determination

2. Choose the New Entries pushbutton.

3. Maintain the following entries:


Departure Country TM RDS example: US (from shipping point 1000)

Departure Zone TM RDS example: US00020000 (from shipping point 1000)

Country of Destination TM RDS example: US (from customer master data)

RecZ (Transportation zone to or from which the goods are delivered)

TM RDS example: US00010000 (from customer master data, maintain all 6 possible US determination zones, see 3.1.4)

4. Click on Route Determination without Weight Group (sales order). Remark: Route determination with weight group is needed for deliveries.

5. Maintain the following entries:


Shipping Conditions TM RDS example: 01

Transportation Group TM RDS example: YTC1

Proposed order item route TM RDS example: YT0001

6. Repeat step 5 for shipping conditions 02 and 03 with transportation groups YTC2, YTC3, YZS1 and YTS2.


For all shipping conditions 01, 02, and 03 the route should be determined from departure zone US00020000 depending on the destination country and destination transportation zone, as listed here:

- Destination Zone US00010000: Route YT0001


- Destination Zone US00030000: Route YT0008(new requirement: 8 days, not 5 as in YT0005)

- Destination Zone US00040000: Route YT0008(new requirement: 8 days, not 5 as in YT0005)



For shipping condition 04 only, route YT9999 should be determined independently of other criteria.

Once you have completed this Customizing activity, the following 120 entries should now be contained in table TROLZ:

© SAP AG of 57


Ctry DepartZone SC TGroup DstC TranspZone Act.RteUS US00020000 01 YTC1 US US00010000 YT0001US US00020000 01 YTC1 US US00020000 YT0001US US00020000 01 YTC1 US US00030000 YT0008US US00020000 01 YTC1 US US00040000 YT0008US US00020000 01 YTC1 US US00050000 YT0003US US00020000 01 YTC1 US US00060000 YT0003US US00020000 01 YTC2 US US00010000 YT0001US US00020000 01 YTC2 US US00020000 YT0001US US00020000 01 YTC2 US US00030000 YT0008US US00020000 01 YTC2 US US00040000 YT0008US US00020000 01 YTC2 US US00050000 YT0003US US00020000 01 YTC2 US US00060000 YT0003US US00020000 01 YTC3 US US00010000 YT0001US US00020000 01 YTC3 US US00020000 YT0001US US00020000 01 YTC3 US US00030000 YT0008US US00020000 01 YTC3 US US00040000 YT0008US US00020000 01 YTC3 US US00050000 YT0003US US00020000 01 YTC3 US US00060000 YT0003US US00020000 01 YTS1 US US00010000 YT0001US US00020000 01 YTS1 US US00020000 YT0001US US00020000 01 YTS1 US US00030000 YT0008US US00020000 01 YTS1 US US00040000 YT0008US US00020000 01 YTS1 US US00050000 YT0003US US00020000 01 YTS1 US US00060000 YT0003US US00020000 01 YTS2 US US00010000 YT0001US US00020000 01 YTS2 US US00020000 YT0001US US00020000 01 YTS2 US US00030000 YT0008US US00020000 01 YTS2 US US00040000 YT0008US US00020000 01 YTS2 US US00050000 YT0003US US00020000 01 YTS2 US US00060000 YT0003US US00020000 02 YTC1 US US00010000 YT0001US US00020000 02 YTC1 US US00020000 YT0001US US00020000 02 YTC1 US US00030000 YT0008US US00020000 02 YTC1 US US00040000 YT0008US US00020000 02 YTC1 US US00050000 YT0003US US00020000 02 YTC1 US US00060000 YT0003US US00020000 02 YTC2 US US00010000 YT0001US US00020000 02 YTC2 US US00020000 YT0001US US00020000 02 YTC2 US US00030000 YT0008US US00020000 02 YTC2 US US00040000 YT0008US US00020000 02 YTC2 US US00050000 YT0003US US00020000 02 YTC2 US US00060000 YT0003US US00020000 02 YTC3 US US00010000 YT0001

© SAP AG of 57


US US00020000 02 YTC3 US US00020000 YT0001US US00020000 02 YTC3 US US00030000 YT0008US US00020000 02 YTC3 US US00040000 YT0008US US00020000 02 YTC3 US US00050000 YT0003US US00020000 02 YTC3 US US00060000 YT0003US US00020000 02 YTS1 US US00010000 YT0001US US00020000 02 YTS1 US US00020000 YT0001US US00020000 02 YTS1 US US00030000 YT0008US US00020000 02 YTS1 US US00040000 YT0008US US00020000 02 YTS1 US US00050000 YT0003US US00020000 02 YTS1 US US00060000 YT0003US US00020000 02 YTS2 US US00010000 YT0001US US00020000 02 YTS2 US US00020000 YT0001US US00020000 02 YTS2 US US00030000 YT0005US US00020000 02 YTS2 US US00040000 YT0005US US00020000 02 YTS2 US US00050000 YT0003US US00020000 02 YTS2 US US00060000 YT0003US US00020000 03 YTC1 US US00010000 YT0001US US00020000 03 YTC1 US US00020000 YT0001US US00020000 03 YTC1 US US00030000 YT0008US US00020000 03 YTC1 US US00040000 YT0008US US00020000 03 YTC1 US US00050000 YT0003US US00020000 03 YTC1 US US00060000 YT0003US US00020000 03 YTC2 US US00010000 YT0001US US00020000 03 YTC2 US US00020000 YT0001US US00020000 03 YTC2 US US00030000 YT0008US US00020000 03 YTC2 US US00040000 YT0008US US00020000 03 YTC2 US US00050000 YT0003US US00020000 03 YTC2 US US00060000 YT0003US US00020000 03 YTC3 US US00010000 YT0001US US00020000 03 YTC3 US US00020000 YT0001US US00020000 03 YTC3 US US00030000 YT0008US US00020000 03 YTC3 US US00040000 YT0008US US00020000 03 YTC3 US US00050000 YT0003US US00020000 03 YTC3 US US00060000 YT0003US US00020000 03 YTS1 US US00010000 YT0001US US00020000 03 YTS1 US US00020000 YT0001US US00020000 03 YTS1 US US00030000 YT0008US US00020000 03 YTS1 US US00040000 YT0008US US00020000 03 YTS1 US US00050000 YT0003US US00020000 03 YTS1 US US00060000 YT0003US US00020000 03 YTS2 US US00010000 YT0001US US00020000 03 YTS2 US US00020000 YT0001US US00020000 03 YTS2 US US00030000 YT0008US US00020000 03 YTS2 US US00040000 YT0008

© SAP AG of 57


US US00020000 03 YTS2 US US00050000 YT0003US US00020000 03 YTS2 US US00060000 YT0003US US00020000 04 YTC1 US US00010000 YT9999US US00020000 04 YTC1 US US00020000 YT9999US US00020000 04 YTC1 US US00030000 YT9999US US00020000 04 YTC1 US US00040000 YT9999US US00020000 04 YTC1 US US00050000 YT9999US US00020000 04 YTC1 US US00060000 YT9999US US00020000 04 YTC2 US US00010000 YT9999US US00020000 04 YTC2 US US00020000 YT9999US US00020000 04 YTC2 US US00030000 YT9999US US00020000 04 YTC2 US US00040000 YT9999US US00020000 04 YTC2 US US00050000 YT9999US US00020000 04 YTC2 US US00060000 YT9999US US00020000 04 YTC3 US US00010000 YT9999US US00020000 04 YTC3 US US00020000 YT9999US US00020000 04 YTC3 US US00030000 YT9999US US00020000 04 YTC3 US US00040000 YT9999US US00020000 04 YTC3 US US00050000 YT9999US US00020000 04 YTC3 US US00060000 YT9999US US00020000 04 YTS1 US US00010000 YT9999US US00020000 04 YTS1 US US00020000 YT9999US US00020000 04 YTS1 US US00030000 YT9999US US00020000 04 YTS1 US US00040000 YT9999US US00020000 04 YTS1 US US00050000 YT9999US US00020000 04 YTS1 US US00060000 YT9999US US00020000 04 YTS2 US US00010000 YT9999US US00020000 04 YTS2 US US00020000 YT9999US US00020000 04 YTS2 US US00030000 YT9999US US00020000 04 YTS2 US US00040000 YT9999US US00020000 04 YTS2 US US00050000 YT9999US US00020000 04 YTS2 US US00060000 YT9999

4Master Data The following sections describe the sample master data used by the SAP Transportation Management rapid-deployment solutions for SAP ERP. If you deploy the solutions automatically using SAP Best Practices Solution Builder, the master data is created automatically via eCATTs.

4.1 Creating Customer Master Data

Use

© SAP AG of 57


The SAP Transportation Management rapid-deployment solutions provide sample customers as part of the SAP ERP sample master data.

For implementation in your productive system you will use your own master data.

Procedure1. Access the following transaction:

SAP ERP Menu Logistics Sales and Distribution Master Data Business Partner Customer Create Complete

Transaction Code XD01

2. On the Customer Create: Initial Screen, enter Account Group, Customer (number), and Company Code.

Field Name Input Value Comment

Account Group YB01 The account group is a classifying feature within customer master records. The account group determines:

the number range for the customer account number (account group YB01 is assigned to number range 01);

whether the number is assigned by the user or the system;

which specifications are necessary or possible in the master record.

Customer Account Number

150001 150000 to 159999Number range 01 is assigned to account group YB01 with values between 100000 and 199999. This number range is flagged as external, which means that you need to enter a number. The number you enter needs to be between the from-number and to-number.

In this scenario we only use the range 150000 to 159999.

Company Code 1000 Company code is an organizational unit within financial accounting.

3. Enter the appropriate Sales Organization (domestic / foreign), Distribution Channel, and Division.


Sales Org. 1000 A Sales Organization is an organizational unit responsible for the sale of certain products or services.

You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.

Distribution Channel

10 The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.

Division 10 A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines


5. On the Create Customer: General Data screen, choose the Address tab page and enter the following data:

© SAP AG of 57



Title Company The title is displayed in text form in the screen field in the logon language, and its key is stored in the database.

Name TM_CUST01 Address component.

Name 2 Sacramento Address component.

Search Term 1 Customer Short description used for search helps.

Street I Street J St Alley

Address component.

House number 1 Address component.

Postal Code 94203 Address component.

City Sacramento Address component.

Country US Address component.

Region CA Address component.

6. Choose the More fields pushbutton to open the Street Address section and enter the following data:


Time Zone PST Address component.

Transportation Zone

US00020000 You can define regional zones to suit the requirements of your own business and country.

The system automatically proposes a suitable route using the transportation zone of the goods recipient in combination with other information about the delivery, such as the:

Countries of origin and destination

Shipping conditions

Transportation group

7. In the Communication section enter the following data:


Language EN The language key designates the language in which you:

Display texts

Enter texts

Print documents.

Telephone <tel.> First telephone no.: dialing code+number

Telephone number as it must be dialed from within the country, consisting of dialing code and number, but without the country code.

If the telephone number consists of a company number and an extension, the extension must be entered in the field extension.

Fax <fax> First fax no.: dialing code+number

Fax number, as it is to be dialed from within the same country, consisting of dialing code and number, but without country dialing code.

If the fax number consists of a company number and an extension, the extension must be entered in the field extension.

© SAP AG of 57


8. If customers have agreed to direct debits/bank collections, enter Country, Bank Key, and Bank Account on the Payment transactions tab page. Set the flag Collection Auth. if needed.


Country US Country of the bank.

Bank Key <bank key> For U.S.:Since 1910, the American Bankers Association has used 9-digit routing transit numbers to identify banks in the United States of America. These numbers are used in the automated processing of checks. The bank company is identified in the 5th to 8th digits (the 4 digits before the last checksum digit). The company number assigned to a bank includes a regional prefix indicating the metropolitan area and/or state.

Bank Account <bank account> This field contains the number under which the account is managed at the bank.

Collection Auth X (checked), if needed

If you have agreed with a customer that they will pay you by bank collection and the payment program is to pay with the corresponding payment method, this field must be selected for at least one bank in the customer's master record. This bank will then be authorized to collect payment from this customer.

9. Maintain the IBAN:Comment: The IBAN is comprised of a maximum of 27 alphanumeric characters within Europe and a maximum of 34 outside of Europe (German IBAN: 22 characters). At present, the United States does not participate in IBAN. Therefore, e.g. the Bank of America does not have an IBAN number.

10. On the Contact Person tab page, enter Name, First Name, and Function.


Name <name> Name of the contact person.

First Name <first name> First name of the contact person.

Function <function> Describes the function of the contact person (for example, marketing manager) for your internal purposes.

11. Choose the Company Code Data pushbutton.

12. On the Account Management tab page, enter the correct Recon. Account and Sort key.


Recon. Account 121000 This is a mandatory field!

The reconciliation account in G/L accounting is the account that is updated parallel to the sub ledger account for normal postings (for example, invoice or payment).

Sort Key 009 Key for sorting according to assignment numbers

Indicates the layout rule for the Allocation field in the document line item.

The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.

13. On the Payment transactions tab page, enter Terms of Payment. If relevant, maintain the Payment Methods. Select Payment History Record.

© SAP AG of 57



Terms of payment 0001 Key for defining payment terms composed of cash discount percentages and payment periods.

It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:

Cash management

Dunning procedures

Payment transactions

Payment Methods 1 List of payment methods that may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.

If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the items not listed in the master record.

Payment History Record

X (checked), if needed

Indicator that the payment history of the customer is to be recorded.

The amount and number of payments are then recorded per calendar month, as well as the average days in arrears.

14. On the Correspondence tab page, enter Dunn. Procedure.


Dunn. Procedure 0001 This field contains the key for the dunning procedure to be used.

15. Choose the Sales Area Data pushbutton.

16. On the Sales tab page, enter the following:


Currency USD Check this field as it is filled automatically

Cust. Price. Proc. 1 This is a mandatory field!You can define different pricing procedures for your system. A pricing procedure determines the type and sequence of conditions that the system uses for pricing in a sales order for example.

17. On the Shipping tab page, enter the following:


Shipping conditions

01 This is a mandatory field!General shipping strategy for the delivery of goods from the vendor to the customer.

The loading group, plant, and shipping condition determine the shipping point that will be proposed by the system for the determination of the shipping point in an outbound delivery.

Delivery plant 1000 This plant is automatically copied into the sales order item as the default value.

Order combination X (checked) Indicates whether you are allowed to combine orders during delivery processing.

18. On the Billing document tab page, enter the following:


© SAP AG of 57


Incoterms FH Incoterms specify certain internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.

Terms of payment 0001 Key for defining payment terms composed of cash discount percentages and payment periods.


Cash management

Dunning procedures


Account assignment group

01 The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.

Tax classification 0 This is a mandatory field!Specifies the tax liability of the customer based on the tax structure of the customer's country.


© SAP AG of 57


20. Repeat the previous steps for the other customers.

Field Name Customer 2 Customer 3 Customer 4 Customer 5

Account Group YB01 YB01 YB01 YB01


150002 150003 150004 150005

Company Code 1000 1000 1000 1000

Sales Org. 1000 1000 1000 1000


10 10 10 10

Division 10 10 10 10

Title Company Company Company Company

Name TM_CUST02 TM_CUST03 TM_CUST04 TM_CUST05

Name 2 Redding Santa Rosa Los Angeles

Reno

Search Term 1 Customer Customer Customer Customer

Street Market Street

Sunny View Way

E 77th Street

W 1st Street

House number 2 3 4 5

Postal Code 96001 95401 90001 89501

City Redding Santa Rosa Los Angeles

Reno

Country US US US US

Region CA CA CA NV

Time Zone PST PST PST PST

Transportation Zone

US00020000 US00010000 US00010000 US00020000

Language EN EN EN EN

Telephone <tel.> <tel.> <tel.> <tel.>

Fax <fax> <fax> <fax> <fax>

Country US US US US

Bank Key <bank key> <bank key> <bank key> <bank key>

Bank Account <bank account>

<bank account>

<bank account>

<bank account>





Name <name> <name> <name> <name>

First Name <first name>

<first name>

<first name>

<first name>

Function <function> <function> <function> <function>

© SAP AG of 57


Field Name Customer 6 Customer 7 Customer 8 Customer 9

Account Group YB01 YB01 YB01 YB01


150006 150007 150008 150009

Company Code 1000 1000 1000 1000

Sales Org. 1000 1000 1000 1000


10 10 10 10

Division 10 10 10 10

Title Company Company Company Company

Name TM_CUST06 TM_CUST07 TM_CUST08 TM_CUST09

Name 2 Gary Peoria Janesville Rochelle

Search Term 1 Customer Customer Customer Customer

Street Martin Luther King Drive

Commercial Alley

Humes Road N 7th Street

House number 6 7 8 9

Postal Code 46401 61601 53545 61068

City Gary Peoria Janesville Rochelle

Country US US US US

Region IN IL WI IL

Time Zone EST MST CST CST

Transportation Zone

US00040000 US00040000 US00040000 US00040000

Language EN EN EN EN

Telephone <tel.> <tel.> <tel.> <tel.>

Fax <fax> <fax> <fax> <fax>

Country US US US US

Bank Key <bank key> <bank key> <bank key> <bank key>


<bank account>

<bank account>

<bank account>





Name <name> <name> <name> <name>

First Name <first name>

<first name>

<first name>

<first name>

Function <function> <function> <function> <function>

© SAP AG of 57


Field Name Customer 10 Customer 11 Customer 12

Account Group YB01 YB01 YB01


150010 150011 150012

Company Code

1000 1000 1000

Sales Org. 1000 1000 1000


10 10 10

Division 10 10 10

Title Company Company Company

Name TM_CUST10 TM_CUST11 TM_CUST12

Name 2 Pensacola Atlanta Montgomery

Search Term 1 Customer Customer Customer

Street W Brainerd Street

Andrew Young International Boulevard NW

Wilson Street

House number 10 11 12

Postal Code 32501 30301 36101

City Pensacola Atlanta Montgomery

Country US US US

Region FL GA AL

Time Zone EST EST CST

Transportation Zone

US00030000 US00030000 US00030000

Language EN EN EN

Telephone <tel.> <tel.> <tel.>

Fax <fax> <fax> <fax>

Country US US US

Bank Key <bank key> <bank key> <bank key>


<bank account> <bank account>




Name <name> <name> <name>

First Name <first name> <first name> <first name>

Function <function> <function> <function>

© SAP AG of 57


And for all customers:


Recon. Account 121000

Sort Key 009

Terms of payment 0001

Payment Methods 1

Payment History Record X (checked), if needed

Dunn. Procedure 0001

Currency USD

Cust. Price. Proc. 1

Shipping conditions 01

Delivery plant 1000

Order combination X (checked)

Incoterms FH

Terms of payment 0001

Account assignment group 01

Tax classification 0

Result You have created the customer master data in the system. To display the customers that have been created in the system, proceed as follows:

SAP ERP Menu Logistics Sales and Distribution Master Data Business Partner Customer Display Complete.

Transaction Code XD03

1. Select the customer and choose the Display pushbutton.

© SAP AG of 57


5

4.2 Create Carrier Master Data

UseSample carriers are part of the SAP ERP sample master data provided with the SAP Transportation Management rapid-deployment solutions.

For implementation in your productive system you will use your own carrier data.

Procedure1. Choose:

SAP ERP Menu Logistics Materials Management Purchasing Master Data Vendor Central

Transaction Code XK01

2. Go to the Create vendor: Initial Screen, and enter the following.


Vendor 500000 500000 to 599999Number range Y5 is assigned to account group YTFA with values between 500000 and 599999. This number range is flagged as external, which means that you need to enter a number. The number you enter needs to be between the from-number and the to-number.

Company code 1000 The company code is an organizational unit within financial accounting.

Purchase organization

1000

Account group YTFA The account group is a classifying feature within vendor master records. The account group determines:

The number interval for the account number of the vendor (account group YTFA is assigned to number range Y5),

Whether the number is assigned by the user or by the system,

Which specifications are necessary and/or possible in the master record.

Reference:It is possible to use an existing carrier as a reference and make an entry in the Reference area in the fields Vendor, Company code, and Purchasing Organization (several field values of the reference vendor will posted by the system in the new vendor master data).


4. On the Create Vendor: Address screen, enter the data as follows, and then choose the Next Screen (F8) pushbutton.


Title Company The title is displayed in text form in the screen field in the logon language, and its key is stored in the database.

© SAP AG of 57


Name Carrier 500000 Address component.

Name 2 Chicago Address component.

Search Term 1 Carrier Short description used for search helps.

Street North Rockwell Street Address component.

House Number 1 Address component.

Postal Code 60618 Address component.

City Chicago Address component.

Country US Address component.

Region IL Address component.

Time Zone CST Address component.

Telephone <telephone> First telephone no.: dialing code+number

Telephone number as it must be dialed from within the country, consisting of dialing code and number, but without the country code.

If the telephone number consists of a company number and an extension, the extension must be entered in the field extension.

Fax <fax> First fax no.: dialing code+number

Fax number, as it is to be dialed from within the same country, consisting of dialing code and number, but without country dialing code.

If the fax number consists of a company number and an extension, the extension must be entered in the field extension.

5. On the Create Vendor: Control screen, choose the Next Screen (F8) pushbutton.

6. On the Create Vendor: Payment transactions screen, choose Next Screen (F8) pushbutton.

Comment: The IBAN is comprised of a maximum of 27 alphanumeric characters within Europe and a maximum of 34 outside of Europe (German IBAN: 22 characters). At present, the United States does not participate in IBAN. Therefore, e.g. the Bank of America does not have an IBAN number.

7. On the Create Vendor: Accounting information Accounting screen, enter the data as follows, then choose the Next Screen (F8) pushbutton.

Field name Input Value Comment

Reconciliation Account

211000 The reconciliation account in G/L accounting is the account that is updated parallel to the sub ledger account for normal postings (for example, invoice or payment).

Sort Key 009 Key for sorting according to assignment numbers

Indicates the layout rule for the Allocation field in the document line item.

The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.

8. On the Create Vendor: Payment transactions Accounting screen, enter the data as follows, then choose the Next Screen (F8) pushbutton twice.

© SAP AG of 57



Payment Terms 0001 Key for defining payment terms composed of cash discount percentages and payment periods.


Cash management

Dunning procedures


Check double inv. X (checked) Indicator that incoming invoices and credit memos are checked for double entries at the time of entry.

Payment Methods 1 List of payment methods that may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid.

If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item not listed in the master record.

9. On the Create Vendor: Correspondence Accounting screen, enter Dunn. Procedure.


Dunning Procedure 0001 A pre-defined procedure specifying how customers or vendors are dunned.

For each procedure, the user defines:

Number of dunning levels

Dunning frequency

Amount limits

Texts for the dunning notices

10. On the Create Vendor: Purchasing data screen, enter Order currency, Terms of payment, Incoterms, Purchasing group.


Currency USD Key for the currency on which an order placed with a vendor is based.

Terms of Payment 0001 Key for defining payment terms composed of cash discount percentages and payment periods.


Cash management

Dunning procedures


Incoterms FH Incoterms specify certain internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.

Schema Group, Vendor

This field is not relevant for rapid-deployment solutions.

IF this field is not a mandatory field, do

Determines which calculation schema (pricing procedure) is to be used in purchasing documents containing this vendor number.

© SAP AG of 57


not maintain a value.

Else, use standard schema group 01 or your own defined group.

Purchasing Group 001 Key for a buyer or a group of buyers who is/are responsible for certain purchasing activities.

Internally, the purchasing group is responsible for the procurement of a material or a class of materials.

Externally, it is the medium through which contacts with the vendor are maintained.


© SAP AG of 57


12. Repeat the previous steps for the other carriers.

Field Name Carrier 1 Carrier 2 Carrier 3 Carrier 4 Carrier 5

Vendor 500001 500002 500003 500004 500005

Company code

1000 1000 1000 1000 1000


1000 1000 1000 1000 1000

Account group

YTFA YTFA YTFA YTFA YTFA

Title Company Company Company Company Company

Name Carrier 500001

Carrier 500002

Carrier 500003

Carrier 500004

Carrier 500005

Name 2 Orlando New York New Orleans

Boston San Francisco

Search Term 1

Carrier Carrier Carrier Carrier Carrier

Street W South Street

Broadway Dumaine Street

Park Street

Oak Street

House Number

101 102 103 104 105

Postal Code 32803 10001 70117 02101 94101

City Orlando New York New Orleans

Boston San Francisco

Country US US US US US

Region FL NY LA MA CA

Time Zone EST EST CST EST PST

Telephone <tel.> <tel.> <tel.> <tel.> <tel.>

Fax <fax> <fax> <fax> <fax> <fax>

© SAP AG of 57


Field Name Carrier 6 Carrier 7 Carrier 8 Carrier 9 Carrier 10 Dummy Carrier

Vendor 500006 500007 500008 500009 500010 599999

Company code

1000 1000 1000 1000 1000 1000


1000 1000 1000 1000 1000 1000

Account group

YTFA YTFA YTFA YTFA YTFA YTFA

Title Company Company Company Company Company Company

Name Carrier 500006

Carrier 500007

Carrier 500008

Carrier 500009

Carrier 500010

Default Carrier for TM Tendering

Name 2 Los Angeles

Seattle Salt Lake City

Dallas Atlanta Detroit

Search Term 1

Carrier Carrier Carrier Carrier Carrier Default Carrier

Street S Los Angeles Street

Madison Street

E 400 Street

N Collet Avenue

Mitchell Street SW

Inglis Street

House Number

106 107 108 109 110 9

Postal Code 90001 98101 84118 75201 30060 48209

City Los Angeles

Seattle Salt Lake City

Dallas Atlanta Detroit

Country US US US US US US

Region CA WA UT TX GA MI

Time Zone PST PST MST CST EST CST

Telephone <tel.> <tel.> <tel.> <tel.> <tel.> <tel.>

Fax <fax> <fax> <fax> <fax> <fax> <fax>

© SAP AG of 57


And for all carriers:


Reconciliation Account

211000

Sort Key 009

Payment Terms 0001

Check double inv. X (checked)

Payment Methods 1

Dunning Procedure 0001

Currency USD

Terms of Payment 0001

Incoterms FH

Schema Group, Vendor

“ “

or 01

or own defined value

Purchasing Group 001

Result You have created the carrier master records for purchasing organization 1000.

4.3 Assign Default Carrier to Route YT9999

1. Choose:


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Transportation Basic Transportation Functions Routes Define Routes Define Routes and Stages


Customizing Menu SAP Customizing Implementation Guide Sales and Distribution Basic Transportation Functions Routes Define Routes Define Routes and Stages


Customizing Menu SAP Customizing Implementation Guide Logistics Execution Shipping Routes Define Routes Define Routes and Stages

2. Select Route YT9999 and choose the New Entries pushbutton to maintain the default carrier in the route:

© SAP AG of 57



Route YT9999

Description Default Carrier 599999 (maintained in 4.2)

Service Agent 599999 (can now be assigned if vendor master data are created before).

3. Save your entries and choose the Exit pushbutton.

Default carrier 599999 should now be assigned to route YT9999, see 3.5.1.

4.4 Create Material Master Data

UseSample materials are provided as part of the SAP ERP sample master data for the SAP Transportation Management rapid-deployment solutions.

You will use your own master data for implementation in your productive system.

Procedure1. Choose:

SAP ERP 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:


Material TM_PROD01 Alphanumeric key that uniquely identifies the material.

In create mode, you can either choose a number yourself or have a consecutive number assigned for you by the system, depending on the method preferred by your company.

If you leave the field blank, the system will assign a number automatically.

If you enter a number, it must be within the corresponding number range.

Industry sector M Key that specifies the branch of industry to which the material is assigned.

Material type FERT Key that assigns the material to a group of materials such as raw materials, operating supplies, or trading goods.

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

View Name Comment

Basic Data 1, Basic Data 2

Required

Sales: Sales Org. Data 1, Sales: Sales Org. Data 2, Sales: General/Plant Data

Required

MRP1 Required

General Plant Data / Storage 1 General Plant Data / Storage 2

Required

© SAP AG of 57


Accounting 1 Accounting 2

Required

Costing 1 Costing 2

Required

4. Choose Enter and complete the entries in the following organizational levels:


Plant 1000

Stor. Location 1020

Sales Org. 1000

Distr.Channel 10

MRP profile Leave empty

5. Choose Enter:

4.4.1 Basic Data

Procedure

1. On the Basic Data 1 tab page, enter the following values and choose Enter:


Description RDS Product 01 Text containing up to 40 characters that describes the material in more detail.

Base Unit of Measure

EA Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure.

Material Group YBT01 Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.

Prod. Hierarchy 00001B000100000003 Alphanumeric character string for grouping together materials by combining different characteristics. It is used for analyses and price determination.

Division 10 A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.

GenItemCatGroup NORM Materials’ grouping that helps the system to determine item categories during sales document processing.

If a group is configured specific to distribution channel, it has priority if the corresponding activity is distribution channel-dependent.

The system automatically suggests an item type in the document depending on the item category group you assign and the sales document type you are processing.

Gross Weight 500 Gross weight expressed in the unit of weight specified by you in the Unit of weight field.

Weight Unit LB Unit referring to the gross weight or net weight of the material.

Net Weight 450 Net weight expressed in the unit of weight specified by you in the Unit of weight field.

Volume 19 Space that the material occupies per unit of volume. The volume refers to the unit specified in the Volume unit field.

The volume and its unit always refer to the base unit of

© SAP AG of 57


measure.

Volume Unit FT3 Unit referring to the volume of the material

Use the dropdown selection tool for the product hierarchy. At each level, click the appropriate level once, then choose the Next Level. When you reach the appropriate end, use the Choose pushbutton.

2. To main the description in languages other than EN, choose the Additional Data pushbutton and maintain the description in the required languages. Then choose the Main Data pushbutton.

3. Choose Enter.

4. On the Basic data 2 tab page, choose Enter.

© SAP AG of 57


4.4.2 Sales Data

Procedure1. On the Sales: sales org. 1 tab page, enter the following values, and choose Enter:


Delivering Plant 1000 Plant from which the goods should be delivered to the customer.

This plant is automatically copied into the sales order item as the default value.

Tax classification 0 The indicator with which the system determines output tax for the material when processing sales and distribution-specific documents.

2. Choose the Conditions pushbutton.

3. On the Change Price Condition (PR00): Scales tab page, enter the following values:


Scale Quantity 1 Scale quantity (for example, number of pieces) to which a scale refers.

UoM EA Unit of measure to which the quantity scale refers.

Amount 1,00 Determines how the system calculates pricing using this condition. Depending on the condition type, the rate can be a fixed amount or a percentage. If the condition includes a pricing scale, the rate displays the first line of the scale.

Rate Unit USD The unit that determines whether the condition for a material is based on a percentage or on an amount in a particular currency.

Per 1 The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for example, bottles).

UoM EA Quantity unit to which the condition rate refers.


5. Choose Enter.

6. On the Sales: sales org.2 tab page, check or enter the following values, and choose Enter:


Item Category group

NORM A grouping of materials that the system uses to determine item categories during the processing of sales documents.

Depending on the item category group that you apply and the sales document type you are processing, the system automatically proposes an item category in the document.

7. On the Sales: General/plant tab page, check or enter the following values and choose Enter:

© SAP AG of 57



Availability check KP This field has two uses:

Specifies whether and how the system checks availability and generates requirements for materials planning.

In Flexible Planning, defines - together with the checking rule - the different MRP elements that make up this key figure. The sum of these elements gives the key figure.

Trans.Grp. YTS1 A grouping of materials that share the same route and transportation requirements.

Transportation groups are used for automatic route scheduling during sales order and delivery note processing.

Loading Group 0001 A grouping of materials that share the same loading requirements.

The system uses the loading group as well as the shipping conditions and delivering plant to automatically determine the shipping point for the item.

4.4.3 MRP Data

Procedure

1. On the MRP1 tab page, enter the following values and choose Enter.


MRP type ND Key that determines whether and how the material is planned.

4.4.4 General Plant Data /Storage Data

Procedure1. On the Plant data/stor.1 tab page, check:


Storage Condition Leave blank Indicates what storage conditions are required for the material.

2. If your material is not batch relevant, you have to skip this step.

If your material is batch relevant, enter the following:


Batch Management

Set indicator Specifies whether the material is managed in batches.

Period Ind. For SLED

D The period indicator specifies the unit of measurement for a period of time.

Maximum Storage <maximum storage> Maximum period for which the material may be stored.

Any value displayed in this field is for information only. The field has no functional use. In particular, there is no functional relationship between this field and the following fields:

Minimum remaining shelf life

Total shelf life

© SAP AG of 57


Storage percentage

Min. Rem. Shelf Life

<min. rem. Shelf life>

Minimum amount of time for which the material must remain usable upon goods receipt for the goods receipt to be accepted by the system.

Total shelf life <total shelf life>

Period for which the material will remain usable in total, that is, from the date of production to the shelf life expiration date.

3. Choose Enter.

4. Choose the Plant data/stor. 2 tab page, and choose Enter.

4.4.5 Accounting Data

Procedure1. On the Accounting 1 tab page, enter the following and choose Enter.


Price unit 1 Number of units to which the price refers.

Example:If 10 gallons of gasoline cost $12.00, the price unit is 10.

Price control S You have the following options:‘S’: Standard price‘M’ Moving average price

Standard price 1,20 The valuation of material stocks at standard prices means that all goods movements are valuated at the same price over an extended period.

Valuation Class 7920 The valuation class has the following functions:

Allows the stock values of materials of the same material type to be posted to different G/L accounts.

Allows the stock values of materials of different material types to be posted to the same G/L account.

Determines, together with other factors, the G/L accounts updated for a valuation-relevant transaction (such as a goods movement).

2. On the second Accounting screen, choose enter.

Default values are shown for price unit, valuation class, and price control . You may change the price unit and price control values if required for your data.

4.4.6 Costing Data

Procedure1. On the Costing 1 tab page, choose Enter.

2. On the Costing 2 tab page, choose Enter.

3. A Last data screen reached dialog box appears.

4. Choose the Yes pushbutton to save.

© SAP AG of 57


4.4.7 Repeat steps for further materials

Procedure1. Choose:

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

Transaction Code MM01

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

Field Name TM_PROD02 TM_CHEM01 TM_CHEM02 TM_CHEM03

Material TM_PROD02 TM_CHEM01 TM_CHEM02 TM_CHEM03

Industry sector M

Material type FERT

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

View Name Comment

Basic Data 1, Basic Data 2

Required

Sales: Sales Org. Data 1, Sales: Sales Org. Data 2, Sales: General/Plant Data

Required

MRP1 Required

General Plant Data / Storage 1 General Plant Data / Storage 2

Required

Accounting 1 Accounting 2

Required

Costing 1 Costing 2

Required

4. Choose Enter and complete the following organizational levels:


Plant 1000

Stor. Location 1020

Sales Org. 1000

Distr.Channel 10

MRP profile Leave empty

5. Choose Enter:

© SAP AG of 57


4.4.7.1 Basic Data

Procedure

1. On the Basic Data 1 tab page, enter the following and choose Enter:


Description RDS Product 02

RDS Chemical 01

RDS Chemical 02

RDS Chemical 03

Base Unit of Measure

EA L L L

Material Group YBT01

Prod. Hierarchy 00001B000100000003

Division 10

GenItemCatGroup NORM

Gross Weight 400 200 200 200

Weight Unit LB LB LB LB

Net Weight 400 200 200 200

Volume 18 15 17 20

Volume Unit FT3 FT3 FT3 FT3

Use the dropdown selection tool for the product hierarchy. At each level, click the appropriate level once, then select the Next Level. When you reach the appropriate end, choose the Choose pushbutton.

2. Choose the Additional Data pushbutton and maintain the description in language EN and DE.

3. Choose the Main Data pushbutton.

4. Choose Enter.

5. On the Basic data 2 tab page, choose Enter.

4.4.7.2 Sales Data

Procedure1. On the Sales: sales org. 1 tab page, enter the following values and choose Enter:


Delivering Plant 1000

Tax classification 0

2. Choose the Conditions pushbutton.

3. On the Change Price Condition (PR00): Scales tab page, enter the following:


© SAP AG of 57


Scale Quantity 1 1 1 1

UoM EA L L L

Amount 2,00 1,00 2,00 3,00

Rate Unit USD USD USD USD

Per 1 1 1 1

UoM EA L L L


5. Choose Enter.

6. On the Sales: sales org.2 tab page, check or enter the following values, and choose Enter:


Item Category group

NORM

7. On the Sales: General/plant tab page, check or enter the following values and choose Enter:


Availability check KP

Trans.Grp. YTS2 YTC1 YTC2 YTC3

Loading Group 0001

4.4.7.3 MRP Data

Procedure1. On the MRP1 tab page, enter the following values and choose Enter.


MRP type ND

4.4.7.4 General Plant Data /Storage Data

Procedure1. On the Plant data/stor.1 tab page, check:


Storage Condition Leave blank

2. If your material is not batch relevant, you have to skip this step.

If your material is batch relevant, enter the following values:


Batch Management Set indicator

Period Ind. For SLED D

© SAP AG of 57


Maximum Storage

Min. Rem. Shelf Life

Total shelf life

3. Choose Enter.

4. Choose the Plant data/stor. 2 tab page, and choose Enter.

4.4.7.5 Accounting Data

Procedure1. On the Accounting 1 tab page, make the following entries and choose Enter.


Price unit 1

Price Control S

Standard Price 1,20 1,30 1,30 1,30

Valuation Class 7920

2. On the second Accounting screen, choose Enter.

Default values are shown for price unit, valuation class, and price control. You may change price unit and price control if required for your data.

4.4.7.6 Costing Data

Procedure1. On the Costing 1 tab page, choose Enter.

2. On the Costing 2 tab page, choose Enter.

3. A Last data screen reached dialog box appears.

4. Choose the Yes pushbutton to save.

© SAP AG of 57


5. Appendix

5.2 Reversal of Process Steps for CustomerThis section describes the most common reversal steps. Use these reversal steps to reverse some of the activities described in this document.

Create Customer Master

Transaction Code (SAP GUI) XD01

Reversal Flag Customer Master for Deletion

Transaction Code (SAP GUI) XD06

Business Role Accounts Receivable Manager

(SAP_NBPR_AR_CLERK-M)

Business Role Menu Accounts Receivable Master Data Customers Mark customer for deletion (centr.)

Comment Customer will be deleted during the next archiving run.

5.3 Reversal of Process Steps for CarrierThis section describes the most common reversal steps, which you can take to reverse some of the activities described in this document.

Create Vendor Master

Transaction Code ( SAP GUI) XK01 and FK01

Reversal: Set Deletion Indicator

Transaction Code ( SAP GUI) XK06

Business Role Purchasing Administrator

(SAP_NBPR_PURCHASER-K)

Business Role Menu Purchasing Master Data Vendors Flag Vendor for Deletion

Comment Set checkbox all areas.

5.4 Reversal of Process Steps for Material

© SAP AG of 57


Material Master – Flag for Deletion

Transaction Code (SAP GUI) MM01

Reversal: Flag for Deletion

Transaction Code (SAP GUI) MM06

Business Role Engineering Specialist

(SAP_NBPR_ENGINEER-S)

Business Role Menu Engineering Master Data Material Master Flag Material for Deletion

Comment In transaction MM06 choose: Material flag for deletion

Material master deletion requires data archiving (not part of the process scenarios), starting with flagging the material for deletion

1. Enter the following on the screen and choose Enter.

Field Name Description User Action and Values Comment

Material Material number Material to be deleted

plant Plant number Relating plant

Stor. location Storage location Relating storage location, if needed

Sales Org. Sales org unit If needed

Distr. Channel Distr. Channel If needed

Warehouse no.

Warehouse Number If needed

Storage Type Storage Type

2. The Flag for Deletion: Data screen appears. Select the material number s for deletion as listed.


© SAP AG of 57

sap tm

Documents

Transcript of sap tm