G82 BB ConfigGuide en De

V2.470 July 2004 English Transportation Management (G82) Building Block Configuration Guide SAP AG Neurottstr. 16 69190 Walldorf Germany SAP Best Practices Transportation Management (G82): Configuration Guide Copyright © Copyright 2004 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®, NT®, EXCEL®, Word®, PoyourPoint® and SQL Server® 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, z/OS, AFP, Intelligent Miner, YoubSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Youb 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as youll 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 information purposes only. National product specifications may vary. © SAP AG Page 3 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide Icons Icon Meaning Caution Example Note or Tip Recommendation Syntax Typographic Conventions Type Style Example text Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as youll as menu names, paths and options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. 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. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as youll as names of installation, upgrade and database tools. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Example text EXAMPLE TEXT Example text © SAP AG Page 4 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide Contents Configuration Guide.......................................................................................................................6 1 Purpose........................................................................................................................................6 2 Preparation..................................................................................................................................6 2.1 Prerequisites.........................................................................................................................6 3 Configuration................................................................................................................................6 3.1 Master Data ..........................................................................................................................6 3.1.1 Creating Customer Master Data.....................................................................................6 3.1.2 Creating Vendor Master Data.........................................................................................7 3.1.3 Creating Material Prices..................................................................................................7 3.2 Customizing ..........................................................................................................................8 3.2.1 Maintain Transportation Planning Point..........................................................................8 3.2.2 Defining Modes of Transportation...................................................................................8 3.2.3 Defining Shipping Types.................................................................................................9 3.2.4 Defining Transportation Connecting Points...................................................................10 3.2.5 Defining Routes and Stages ........................................................................................10 3.2.6 Checking Transportation Zones ...................................................................................11 3.2.7 Maintaining Country / Transportation Zone for Shipping Point s...................................12 3.2.8 Maintaining Router Determination ................................................................................12 3.2.9 Maintaining Transportation Relevance .........................................................................13 3.2.10 Defining Shipment Types ...........................................................................................14 3.2.11 Defining and Assigning Tariff Zones ..........................................................................15 3.2.12 Defining and Assigning Pricing Procedures................................................................15 3.2.13 Assigning Purchasing Data -- Shipment Cost Settlement ..........................................16 3.2.14 Determining G/L Accounts Automatically – Shipment Cost Settlement .....................17 3.2.15 Determining CO Assignments Automatically – Shipment Cost Settlement.................17 3.2.16 Maintaining Shipping Point Addresses .......................................................................18 3.2.17 Checking G/L Account Settings .................................................................................18 3.2.18 Creating Transportation Condition Records................................................................19 © SAP AG Page 5 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide Configuration Guide 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the installation guide of this building block. 2 Preparation 2.1 Prerequisites If you want to use this building block, you must first install the following building blocks: Building Block # G80 Description Basic Settings You need transportation goods, which can be either fast moving goods (C10010) or trading goods (C20010). If you use fast moving goods, you need to install J65 as a prerequisite; for trading goods, you need to install J57 as a prerequisite. In either case, you only need to install the respective material master data parts of the building block. 3 Configuration 3.1 Master Data 3.1.1 Use The customer master is where the goods will be delivered and transport to from the transportation point of view. Creating Customer Master Data If you installed J57, the customer C6120 has already been created and you may skip this step. Procedure © SAP AG Page 6 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide 1. To carry out the activity, choose one of the following navigation options: SAP Menu Path Transaction Code Logistics  Sales & Distribution  Master Data  Business Partners  Customer  Create  Sales & Distribution VD01 2. You can create the customer manually with reference to the data file SMB15_XD01_L001_J57.txt, note you only need customer C6120 for this scenario. For more information on how to do this, refer to the Essential Information. 3.1.2 Use Creating Vendor Master Data Vendor master is the business partner who may provide transportation service and is the business partner with whom the final transportation cost will be settled in G82. Procedure 1. To carry out the activity, choose one of the following navigation options: SAP Menu Path Transaction Code Logistics  Material Management  Purchasing  Master Data  Vendor  Central  Create XK01 2. You may create the vendor manually with reference to the data file SMB26_XK01_L001_G82.txt. For more information on how to do this, refer to the Essential Information. 3.1.3 Use Creating Material Prices You need to create material price that will used for sales. Procedure 1. Access the activity using one of the following navigation options: SAP Menu Path Transaction Code Logistics → Sales and Distribution → Master Data → Conditions → Create VK31 2. Create the material price with reference to the data file /SMB26/VK31_L002_G82. For more information on how to do this, refer to the Essential Information. © SAP AG Page 7 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide 3.2 Customizing 3.2.1 Use The transportation planning point is responsible for planning shipments with particular features. A shipment is assigned to one transportation planning point; a planning point is also used for the transportation cost settlement since it is linked with company code. Maintain Transportation Planning Point Procedure 1. Access the activity using one of the following navigation options: Transaction Code IMG Menu SPRO IMG → Enterprise Structure → Definition → Logistic Execution → Maintain transportation planning point 2. Check the following values. If they do not already exist, choose New entry. 3. Check the values according to the following table. If they do not already exist, enter values as follows and save: Field Transportation Planning Point Description Company code Value Z005 Transp. Z005 (comm.) Z005 4. If the system asks for a change request, create one and assign it to this customizing. 5. Maintain address information for the transportation planning point, Select the line you just created and choose Address. Enter the values as follows and save: Field Title Name Country Language Value Company Transportation planning point Z005 IN English 3.2.2 Use Defining Modes of Transportation Define every possible kind of mode of the transportation, for example, you may only use trucks and perform the transportation on road, or you may also use ship via sea transportation. Procedure 1. To carry out the activity, choose one of the following navigation options: © SAP AG Page 8 of 20 SAP Best Practices IMG Path Transportation Management (G82): Configuration Guide IMG →Logistic Execution→ Transportation →Basic Transportation Functions  Routes → Define routes Define modes of transport SPRO Transaction Code Some modes of transport have already been defined. If so, this step is only performed as a check. 2. Check if the following settings are set correctly: Field Sh TY Description Value 01 Road If you find other settings, you can leave these as they are. 3.2.3 Use Defining Shipping Types You define the shipping types in combination with the mode of transportation. The shipping types can include those listed below. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code IMG →Logistic Execution→ Transportation → Basic Transportation Functions  Route → Define shipping types SM30 Some modes of transport have already been defined. If so, this step is only performed as a check. 2. Check if the following settings are set correctly: Field PT Description Mdtr STPG Value 01 Truck 01 0001 © SAP AG Page 9 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide If you find other settings, you can leave these as they are. 3.2.4 Use Defining Transportation Connecting Points In this step, the transportation steps are defined. For example in this activity, 310000 represents the Shanghai plant where goods are delivered and 310010 represents the point of a customer in Beijing where the goods will be delivered. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path IMG →Logistic Execution→ Transportation → Basic Transportation Functions Routes →Define routes  Define transportation connection points SPRO Transaction Code 2. Choose New Entry. 3. Enter values like this and save: Field Name Points Load trnsf pnt Value 310000 Check this selection Description Frankfurt 4. Choose the Reference shipping point / plant tab, enter values as follows, and save Field Name Shipping point Value BP02 5. Define shipping point 310099 by choosing New and enter values as follows: Field Name Points Load trnsf pnt Value 310099 Check this selection Description Hamburg 6. Choose the Reference Customer/vendor tab, enter the following value, and save Field Name Customer Value C6120 3.2.5 Use Defining Routes and Stages Define the stages combination with routes, such as how its stages appear. You define the standard route here. © SAP AG Page 10 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path IMG →Logistic Execution→ Transportation → Basic Transportation Functions Routes → Define routes  Define routes and stages SPRO Transaction Code 2. Check if t route 000021 already exists. If not, create it as a new entry as follows : Field Name Route Description Value 000021 South-north Route Comments 3. Choose the Routes Stages folder, then choose Add new entry. 4. Enter the values like this and save: Field Name Dep. Point Dst. Point Service agent Distance Leg indicator Shipping type Stage category Shipment cost relevant 5. Save the changes and exit. Value 310000 310099 C7010 500 km Direct leg 01 truck Transportation Mark this check box Be sure this check box is select. Comments 3.2.6 Use Checking Transportation Zones Transportation zones can be defined according to country specifications and your company's needs. Transportation zones represent delivery recipients ‘ (ship-to party) regions or delivery shipper’s (vendor) regions. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path IMG →Logistic Execution→ Transportation → Basic Transportation Functions  Route  Router determination → Define transportation zones SPRO Transaction Code 2. Here you use the standard transportation zone, so just check if this entry exists: © SAP AG Page 11 of 20 SAP Best Practices City DE DE Transportation Management (G82): Configuration Guide Transportation zone 0000000001 0000000002 Description Region North Region South The standard transportation zone is available by default, so it was assigned to the customer master before the transportation zone was defined. If you want to use a self-defined transportation zone, you need to change the assignment to the customer after the definition. 3.2.7 Use Maintaining Country / Transportation Zone for Shipping Point s This step is set up the relationship betyeen transportation zones and shipping points in order to automatically determine the router in the sales order. Procedure 1. To carry out the activity, choose one of the following navigation options: SAP Menu Path IMG →Logistic Execution→ Transportation → Basic Transportation Functions  Route  Route determination → Maintain country and transportation zone for shipping point SPRO Transaction Code 2. Check if the following entry exists. If not, create it as follows: Shipping point BP02 3. Save the value. Country DE Zone 0000000002 3.2.8 Use Maintaining Router Determination In this step, the system will know which router will be selected when the sales order or delivery is created. Procedure 1. To carry out the activity, choose one of the following navigation options: © SAP AG Page 12 of 20 SAP Best Practices IMG Path Transportation Management (G82): Configuration Guide IMG →Logistic Execution→ Transportation → Basic Transportation Functions  Route  Router determination → Maintain router determination SPRO Transaction Code 2. Check if the following entry exists. If not, create it as follows: Field Name Cdep DepZ DstC RecZ Value DE 0000000002 DE 0000000001 Comments Depature Country Departure Zone Destination Country Receipt Zone 3. Select this line. Choose router determination without weighing group (order). 4. Check if the following entry exists. If not, create it as follows: Field Name SC TGroup Proposed route 5. Save your changes. Value 01 0001 000021 Comments Shipping Condition Transportation Group 3.2.9 Use Maintaining Transportation Relevance In this step, you define the following relevance: • • • Maintain transportation relevance for delivery types Maintain transportation relevance for delivery item types Maintain transportation relevance for routes Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code IMG →Logistic Execution→ Transportation → Shipments → Maintain transportation relevance SPRO 2. Choose the line Maintain transportation relevance for delivery types and check if the following entry was maintained. if not, maintain it, save your changes, and go back: Field Name Del type Value LF Relevant for transport Check the box © SAP AG Page 13 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide 3. Choose the line Maintain transportation relevance for delivery item types and check if the following entries are maintained. If not, maintain them, save your changes, and go back: Field Name Item category Item category Value TAN YG05 Relevant for transport Check the box Check the box 4. Choose the line Maintain transportation relevance for routes and check if the following entry was maintained. If not, maintain it, save your changes, and go back: Field Name Route 5. Save and exit. Value 000021 Relevant for transport Check the box 3.2.10 Use Defining Shipment Types A shipment type is a centralized document type that controls the activity of the shipment document and the subsequent activities. The standard shipment type will be used (0001 Indiv.Shipmt – Road, so the settings should be ready). If the settings already exist, then the following activity is performed as a check. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code IMG →Logistic Execution→ Transportation → Shipments →Define shipment types SPRO 2. Choose the line 0001(Indiv.Shipmt – Road) ,check the values, and do not make any changes. Field Name Shipping type Process control Leg indicator Adapt router Pick check Value 01 Individual shipment using one mode of transport Direct leg Adopt all stages Shipment completion only for full pick The shipment document can not be marked as completions unless the delivery within this shipment should be fully picked Comments 3. Exit without saving. © SAP AG Page 14 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide 3.2.11 Use Defining and Assigning Tariff Zones You define the tariff zones and assign postal code areas to the tariff zones for each organizational key. The tariff zones represent geographical-influencing factors during the calculation of shipment costs. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code IMG →Logistic Execution→ Transportation → Shipments cost → Basic functions  Define and assign tariff zones T_76 2. Choose New Entry and enter values as follows: Field Name Tariff zone Tariff zone 3. Save and exit. 4. Select the line just created and choose the folder Define organization key for tariff zone assignment. 5. Enter value as follows: Field Name TransportPlanningPt Service agent Shipping type Country key Value Z005 7776 01 IN Comments Value YG0001 YG0002 Description Frankfurt Hamburg 5. Select the newly -created tariff zones,choose Assign tariff zone to organization key and post code new entry, and enter values as follows: Post code 60311 20054 6. Save the changes and exit. Post code 68789 22769 Tariff Zone YG0001 YG0002 3.2.12 Use Defining and Assigning Pricing Procedures The settings of pricing and procedures will determine how the costs of transportation are calculated. Procedure © SAP AG Page 15 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide 1. To carry out the activity, choose one of the following navigation options: IMG Path IMG →Logistic Execution→ Transportation → Shipments cost → Pricing  Price control  define and assign pricing procedures SPRO Transaction Code 2. Select line Maintain pricing procedure. Choose the condition procedure SDFC00 and choose Copy, then enter, change the pricing procedure name from SDFC00 to YGFC00. 3. Chose Enter. 4. On the screen that appears, select Copy all, and change the new pricing description to BP Pricing,. 5. Save the changes. The result of this step is that you have a new pricing procedure called YGFC00. 4. Select line Define pricing procedure determination for shipment costs., 5. Select Transportation Planning Point Z005 with description Transp. Z005 (comm.). 6. Choose determine pricing procedure and choose New entry. Field Name It.Det.Group SA group Shp Typ Group CstgSheet 0001 YGFC00 Value 0001 Comments 7. Enter values as follows and save: 5. Now all transportations from transportation planning point Z005 have pricing procedure YGFC00. 3.2.13 Use Assigning Purchasing Data -- Shipment Cost Settlement In this step you assign transportation service groups to plants, transportation planning points, and shipment cost document type. The system can find the suitable purchase order for settling the transportation costs. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code IMG →Logistic Execution→ Transportation → Shipments cost → Settlement  Assign purchasing data SPRO 2. Choose New entry and enter values as follows: Field Name TPpt Value Z005 Comments Transportation planning point © SAP AG Page 16 of 20 SAP Best Practices SCty POrg PGrp Plant 0001 Z005 YG1 BP02 Transportation Management (G82): Configuration Guide Shipment cost type Purchasing organization Purchasing group 3. The purchase group is assigned to plant BP02, transportation planning point Z005, and shipment cost type 0001. 3.2.14 Determining G/L Accounts Automatically – Shipment Cost Settlement Use When the transportation cost is settled in shipment cost documents, the amount shoisuld be recorded to the G/L account automatically instead of manually. The purpose of this step is to define these settings. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code IMG → Logistics Execution  Transportation  Shipment Costs  Settlement Automatic G/L Account Determination OMWB 2. Choose Account assignment. 3. Select transaction GBB- Offsetting entry for inventory posting,and select Choose. 4. Enter IKR in field Chart of account and choose Enter. 5. Select New entries. 6. Make the following entry. Valuation Modif. 0001 General Modification VBR Valuation Class 3200 Debit 614000 Credit 614000 7. Save. Now the amount of transportation cost can be posted to G/L account automatically. 3.2.15 Determining CO Assignments Automatically – Shipment Cost Settlement Use When the transportation cost is settled in shipment cost documents, the costs are posted to FI for booking the amount. Also, the costs need to be posted to a certain cost collector, such as a cost center for internal orders (for controlling purpose). Here you post the transportation costs to a cost center. Procedure © SAP AG Page 17 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide 1. To carry out the activity, choose one of the following navigation options: IMG Path IMG Logistics Execution  Transportation  Shipment Costs  Settlement Automatic Determination of CO Assignments OKB9 Transaction Code 2. Select New entries. 3. Make the following entry. CoCd Z005 Cost elem. 614000 BarIn Cost Ctr 1602 Order PrfSeg Profit Ctr Acct assignment detail 4. Save. Now the costs of transportation can be posted to cost center 1602. 3.2.16 Use Maintaining Shipping Point Addresses The shipment cost is calculated based on tariff zones, therefore, you must be sure that the shipping point has the postcode and country maintained. Procedure 1. To carry out the activity, choose one of the following navigation options: IMG Path Transaction Code Enterprise Structure  Definition  Logistics Execution  Define, copy, delete, check shipping point SPRO 2. In the dialog box, choose Define shipping point. 3. Choose shipping point BP02, and then choose Detail. 4. On the detail screen, choose Address, and enter the following values: Field Country Postal code 5. Save the entry. Value DE 68789 3.2.17 Use Checking G/L Account Settings The shipment invoice will be posted to certain G/L accounts. These accounts should be relevant for taxes. Therefore the tax category should be either ‘-‘ or ‘*’. © SAP AG Page 18 of 20 SAP Best Practices Transportation Management (G82): Configuration Guide Procedure 1. To carry out the activity, choose one of the following navigation options: SAP Menu Path Transaction Code Field G/L Account No. Company Code Accounting  Financial Accounting  General Ledger  Master Records → Individual Processing → Centrally FS00 Value 614000 Z005 2. On the Edit screen, enter values as follows: 3. Choose Change and go to the Control Data tab. 4. Check if the tax category is set to either ‘-‘ or ‘*’. If not, set it to ‘*’. 5. Save the entry. 3.2.18 Use Creating Transportation Condition Records Transportation condition records are the combination of the forwarding agency and condition type. Normally, it stipulates the detailed pricing information, such as how much it will cost for this forwarding agency to transport a certain weight of the goods. In fact, support-scaled pricing and multi-factor pricing like considering both weight and distance. In this case, you use weight as the base to calculate a fixed starting point and end point. Procedure 1. To carry out the activity, choose one of the following navigation options: SAP Menu Path Transaction Code 2. Enter values as follows: Field Condition type Value FB00 Logistics  Logistic Execution Master data  Transportation Shipment cost  Prices  create TK11 3. Choose Key combination. In the dialog box that appears, select Service agent/Tariff zone dep./Tariff zone target. 4. On the Create Freight class/ Weight condition (FB00): Fast entry screen, enter values as follows and save: Field Service agent Tf zone point of dep TfZDt Value C7010 YG0001 YG0002 © SAP AG Page 19 of 20 SAP Best Practices Field Amount Unit Per Uom Calculation type Valid from Valid to 5. Save your changes. Transportation Management (G82): Configuration Guide Value 2 EUR 1 KG D Today’s date 30/12/9999 © SAP AG Page 20 of 20