Beruflich Dokumente
Kultur Dokumente
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Charge Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Defining Source Location Scales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Defining Destination Region Scales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Defining Destination Zone Scales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Defining Source Zone Scales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.5 Defining Less-than-Truckload Break-Weight Scales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.6 Defining Carrier Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.7 Defining Fuel Surcharges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.8 Defining Calculation Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.9 Defining Freight Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
2 PUBLIC Content
1 Purpose
In this document, you find a description of how to create a master data for charge management for your S/4
HANA system. The description includes those data segments that are relevant for the master data to work in a
"usual" system environment. The reader mainly learns which data segments and fields usually need to be filled
with input values. Fields that are not relevant for the scope of the S/4 HANA content delivery by SAP Best
Practices are not described in this document although they may appear on the UI.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Purpose PUBLIC 3
2 Prerequisites
System Details
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
4 PUBLIC Prerequisites
3 Charge Management
Context
Define your master data records for source location scales using the SAP Fiori launchpad. Rates are based on
source and destination; in this scenario the source location is the shipping point.
Procedure
General Data
Items
Calculation Type Defines how the values of the scales Absolute, which means read the val
are read. ues directly.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 5
Field Description User Action and Values
Context
Define your destination region scales master data records using the SAP Fiori launchpad.
Truckload rates are represented by origin to state rates. In SAP, region and state are equivalent. Here we create
the scale to represent the states in the scenario.
In this scenario, there are two different scales for charge calculation. Carriers 17386001 and 17386002 are
region-based. so you must create a destination region scale. Carrier 17386003 and 17386004 are zip-code-
based. We define this using a destination zone scale.
Procedure
General Data
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
6 PUBLIC Charge Management
Field Description User Action and Values
Items
Calculation Type Defines how the values of the scales Absolute, which means read the val
are read. ues directly.
Note
You can add further rows to define more region values, but you must also add the respective rates.
Context
New scales are defined. The following zones have been defined for this scenario:
Procedure
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 7
Field Description User Action and Values
General Data
Scale Base Defines the basis of the scale, such as TRZONE(transportation zone)
location, distance, or duration.
Items
Calculation Type Defines how the values of the scales Absolute, which means read the val
are read. ues directly.
ZIP_ZONE_3
ZIP_ZONE_4
Note
You can add further rows to define more region values, but you must also add the respective rates.
Context
New scales are defined based on source zones. The following zones have been defined for this scenario:
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
8 PUBLIC Charge Management
Procedure
General Data
Scale Base This defines the basis of scale – such TRZONE – Transportation zone
as: location, distance, duration, and so
on.
Items
Calculation Type Defines how the values of the scales Absolute – means read the values di
are read rectly
Note
You can add further rows to define more region values, but remember to also add the respective rates.
Context
Define your master data records for less-than-truckload (LTL) rates using the SAP Fiori launchpad.
Less-than-truckload rates are based on break-weights, that is, scales. You must define them directly in SAP.
Standard business practice represenst break-weights in terms of CWT (hundredweight). You can do this by
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 9
creating a unit of measure for CWT. However, in this configuration, we have created the following pound break-
weights for you:
● 500
● 1000
● 2000
● 5000
● 10000
● 20000
Procedure
General Data
Scale Type Defines how the scales are to be main Base Scale (>=)
tained.
Items
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
10 PUBLIC Charge Management
Field Description User Action and Values
500
2000
5000
10000
20000
Procedure
General Data
RF-RATE-17386002
RF-RATE-17386003
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 11
Field Description Value
Charge Usage Scenario for the rate table's use, for Service Provider
example, customer billing integration
and/or supplier invoice integration, or
none.
Scales
Valid-From Date Date from which the rate table is valid. 01.01.2010
Valid-To Date Date until which the rate table is valid. 31.12.2099
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
12 PUBLIC Charge Management
Field Description Value
When the Dates row is entered, rate combinations are created in the screen area below. You need to highlight the row
of Valid-From Date to be able to enter the values.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 13
Rate Values for Carrier 17386002
Transportation Zone of Source Loca Transportation Zone of Destination
tion Location Rate Values
General Data
Charge Usage Scenario for the rate table's use, for Service Provider
example, customer billing integration
and/or supplier invoice integration, or
none.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
14 PUBLIC Charge Management
Field Description Value
Scales
2: Same Scale
3: Base Scale
2: TRZONE
3: WEIGHT
Valid-From Date Date from which the rate table is valid. 01.01.2010
Valid-To Date Date until which the rate table is valid. 31.12.2099
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 15
Field Description Value
When the Dates row is entered, rate combinations are created in the screen area below. You need to highlight the row
of Valid-From Date to be able to enter the values.
Transporta
>=
Source Lo tion Zone of 0,000001 >= 10,000 >= 20,000
cation Destination KG >= 500 KG >= 2,000 KG >= 5.000 KG KG KG
10. Select the date line, and choose Release to release the rates.
11. Save your entries.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
16 PUBLIC Charge Management
3.7 Defining Fuel Surcharges
Context
Fuel surcharges are based on a percentage of the base freight from origin to region (region and state are
equivalent in this scenario). This can be altered by changing the scale defined earlier. Standard fuel surcharge
indexes are not covered in this scenario, but you can also use them if configured accordingly.
Procedure
General Data
Charge Usage Scenario for the rate table's use, for Service Provider
example, customer billing integration
and/or supplier invoice integration, or
none.
Charge Type Link for integration with SAP ERP via Y_FUEL_RFSC
the harge type in Customising for T .
Charge Item Category Defaults from Charge Type. 903 – Transportation Charges +
Additional Charges
Charge Item Subcategory Defaults from Charge Type. 910308 – Fuel Surcharge
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 17
Field Description Value
Scales
Valid-From Date Date from which the rate table is valid. 01.01.2010
Valid-To Date Date until which the rate table is valid. 31.12.2099
When the Dates row is entered, rate combinations are created in the screen area below. You need to highlight the row
of Valid-From Date to be able to enter the values.
4. Enter basic data, choose the line just created and enter the following values into the resulting table:
CA 3
TX 5
5. Select the date line, and choose the Release pushbutton to release the rates.
6. Save your entries.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
18 PUBLIC Charge Management
3.8 Defining Calculation Sheets
Procedure
General Data
RF-TCCS-17386002
RF-TCCS-17386003
RF-TCCS-17386004
RF-17386002: TCCS
RF-17386003: TCCS
RF-17386004: TCCS
Items
Note
To create items, use the Insert Single Item option at the top of the Items area.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 19
Field Description Value
Instruction Type Relates charge types to each other Standard (for all charge types)
and defines how calculations are
made for each charge type.
Charge Type Defines the charge type that you have Y_BASE_FRGHT_RF
previously defined for each item.
Y_FUEL_RFSC
Y_FRKLFT_RFSC
Y_LOAD_RFSC
Y_UNLOAD_RFSC
Y_PICKUP_RFSC
Description User-definable description that ap Free text, such as the following:
pears in documents. We recommend
Line-Haul Charge
that you use descriptions that make
sense in other documents. Fuel Surcharge
Forklift Surcharge
Loading Fee
Unloading Fee
Pick-Up Fee
(Fuel )
4. Select the line item for Basic Freight and, in the details screen, enter the values in the following table:
Rate
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
20 PUBLIC Charge Management
Field Description User Action and Values
Rate Table Rate table assigned to each carrier. RF-RATE-17386001 for carrier 1
RF-RATE-17386002
RF-RATE-17386003
RF-RATE-17386004
Basic Data
5. Select the line item for Fuel Surcharge and, in the details screen, enter the values in the following table:
Rate
Rate Table Rate table assigned to each carrier. RF-RATE-FUEL-SRCHRG for carrier 1
Basic Data
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 21
Field Description User Action and Values
Procedure
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
22 PUBLIC Charge Management
Field Description Value
RF-FA-17386002
RF-FA-17386003
RF-FA-17386004
RF-FA-17186002
RF-FA-17186003
RF-FA-17186004
17386003
17386004
Items
Item Number 10
RF-TCCS-17386004
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Charge Management PUBLIC 23
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
24 PUBLIC Important Disclaimers and Legal Information
Transportation Management in SAP S/4HANA: Master Data Guide for Charge Management
Important Disclaimers and Legal Information PUBLIC 25
www.sap.com/contactsap
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.