Monday Knowledge Snippet (MKS) – 50 Means of Transport, Resource Class, and Vehicle Types
When setting up your SAP Transportation Management and having the need to create resources, it can be a bit confusing what needs to be defined first. On a bit higher level, I have already blogged about Transportation Modes (MKS05).
So lets get started with the relevant customizing path including all required activities:
First of all we define a resources class, which is basically an element to structure your resources. In my example I create 2 different resources classes and classify them as vehicle resources. Note that the resource types are hard coded.
As a second step, we define a generic means of transport. Remember that MTRs are used for example to define transportation lanes, when determining distances, and defining transportation cost. To minimize the effort here, it is possible to create an MTR hierarchy by setting a superordinate MTR for each entry. In case no specific definition (for example for speeds) is available for a MTR, the definitions of the superordinate MTR are taken into consideration. Note that on this generic entry I have selected resource class Truck and not one of my just created specific ones. Transportation Mode is set to Road.
Now the specifics MTRs:
For each resource class it is possible ot have multiple MTRs (1 – n relation).
Next step is to define a Vehicle Group and Type. Those are used to specify vehicles further regarding physical attributes, capacity, and transportation relevant information. When creating the vehicle type, it is required to enter an MTR.
For each resource class it is possible ot have multiple Vehicle Groups.
Each Vehicle Type can only have 1 MTRs, but for each MTR there can be mutliple types (1 – n relation).
And finally, when creating the master data resource instances, we can benefit from the already made definitions and ensure data consistency. On the entry screen, we can already select a resource class.
Within the resource header details, we can then select MTR and vehicle group/type (automatically the defined attributes are taken over into the resource).
Next step for those resources would be the definition of transportation lanes on MTR level, and the definition of MTR specific cost in the planning.
Hope this clarifies the usages of the different definitions a bit.