Calculation Logic 
This function enables the system to use the following objects when calculating transportation charges:
Resolution base
Calculation base
Collective rate
Integration
This function is used in the charge calculation process, which is used in the following SAP Transportation Management (SAP TM) components:
For more information about the charge calculation process, see Charge Calculation.
Features
Resolution Base
With the resolution base, you assign the charge type to a certain data source level. The charge type, for example, FB00, which is a single building block of the calculation sheet, is calculated with regard to the resolution base. During charge calculation, the system resolves the calculation sheet according to the given input data. At runtime, the calculation logic works as follows:
As a result of the initial resolution step, the system creates a calculation table based on the logistical data source. The system has not yet performed any calculations or determined any rates.
The system processes the calculation table and determines a value for each row given in the calculation sheet. If the system cannot determine any value for a certain charge type, the system issues a warning or error and does not apply a charge for that row in the calculation sheet. However the process is not interrupted.
Calculation Base
With the calculation base, you define the instruction to determine the data source. The calculation base represents the configurable link to the data source with which a rate is determined. The system uses the calculation base to automatically execute charge calculation.
Example
You have a two-dimensional rate table with the first dimension (scale) based on the destination harbor and the second dimension (scale) based on the weight of the cargo to be shipped. The rate that the system identifies after the two dimensions of the price matrix have been evaluated, for example USD 39.60, is multiplied by the volume to be shipped. In this example, the logistical data source has to provide at least three different pieces of information to calculate the correct charge. There is a calculation base for each of these three entities, describing the path to the certain data source.
Example
You are shipping a container from Europe to various destinations in the United States, such as New York and Los Angeles. You want to charge for the transportation based on the source location (Europe), the destination location (New York and Los Angeles), and the gross weight of the container. To enable this, you define a rate table with three scales (dimension) – source location, destination location, and gross weight. Each of these scales uses the corresponding calculation bases, which are SOURCELOC, DESTLOC, and GROSS_WEIGHT.
The calculation base and the resolution base are coupled in a way that the same calculation base leads to a different data source dependent on the currently processed resolution base.
Example
You have the following master data maintained in a calculation sheet:
Calculation Base |
Resolution Base |
Calculation Rule |
|---|---|---|
Gross Weight (maintained in rate table A for charge type FB00) |
Container (for charge type FB00) |
USD 10 per 100 kg |
Gross Weight (maintained in rate table B for charge type BASE) |
Package (for charge type BASE) |
USD 25 per 100 kg |
You have an FWO with 2 containers and 1 package with the following gross weights:
Container 1 – 1000 kg
Container 2 – 2000 kg
Package 1 – 200 kg
In this situation, the system applies charge type FB00 for each container (resolution base = container) and calculates the transportation charges as follows:
Container 1: (1000/100)*10 = USD 100
Container 2: (2000/100)*10 = USD 200
The system also applies charge type BASE for each package (resolution base = package) and calculates the transportation charges as follows:
Package 1: (200/100)*25 = USD 50
Collective Rate
With a collective rate, you apply group discounts to charge types using a grouping rule. You base the grouping rule on a calculation base, such as resource type or destination location. The grouping calculation base is determined by a grouping rule either directly or dynamically using a condition. When you group charge types, the combined quantity of the charge items is used to calculate the rate.
Example
You use a weight scale to charge for transporting containers, and you create a grouping rule to group containers by destination location. The system uses the combined weight of all containers going to the same location to calculate the collective rate, but each individual weight is applied to the grouping rule.
The standard rate for a container is USD 1 per kg. The collective rate is USD .7 per kg if the combined weight is over 600 kg. Each container going to one warehouse weighs 150 kg. However the combined weight for five containers is 750 kg, so the system charges the collective rate of USD .7 per kg instead of USD 1 per kg.
Example
Resolution Base
You have an FWO with 3 stages and want to calculate the transportation charges for the entire FWO, not for each stage. Therefore you specify the header as the calculation level. You want the system to calculate charge type BAF once in this FWO. Therefore you specify the resolution base as Root. This ensures there is only one resulting row for the calculated calculation sheet in the Charges tab page of the FWO. For more information about the Charges tab page, see Charges Overview.
You want the system to calculate charge type THC for each container in the FWO. Therefore you specify the resolution base as Container. If you ship three different containers, there are three resulting rows for the calculated calculation sheet – one for each container.
The final sum adds the transportation charges in the four rows:
Row 1 for the BAF with amount a.
Sum of rows 2, 3, and 4 of THC with the following amounts:
b: Charge for container 1
b: Charge for container 2 (amount is the same as for container 1, because it has the same attributes)
c: Charge for container 3 (different than amount b because container 3 is bigger)