Carrier selection based on gross weight ?

[AdrienManier90]

Dear SAP TM experts,

I have a requirement from my customer and I am not sure it could be managed through standard features. Hereunder a few lines for this business requirement:

The customer wants to perform the carrier selection taking into account the gross weight of the truck. This weight limit can be different in function of the route of the trucks.

For example

From point A to point B, available carriers are

Carrier 1 between 10 and 25 tons

Carrier 2 between 10 and 25 tons

Carrier 3 for all the trucks under 10 tons.

From point A to point C, available carriers are

Carrier 1 between 12 and 25 tons

Carrier 2 between 12 and 25 tons

Carrier 4 for trucks under 12 tons.

In order to assign the carrier to the geographical attributes, the transportation lane seems to fit perfectly the requirement. On the other hand, it does not seem to handle such weight limitations.

I investigated also allocations but this object seems to be apply a limite on a period of time, not on each Freight Order.

A last possibility would maybe to deal with incompatibilities but i'm affraid to complexify a lot the solution for the users.

Did you already face this requirement ? Or maybe can you please suggest how you would handle it? 

Thank you for your help.

Best regards,

AdrienM

[Saurabh_Goyal]

Hi Adrien,

Have you explored using transportation lanes with MTR having relationship with truck types and selection based on cost strategy which is picked from TCM. 

Regards,

Saurabh

[AdrienManier90]

Hello @Saurabh_Goyal

Thank you for your proposal.

In theory this could work but not at 100% from my perspective because:

- The customer is using the same MTR in both cases

- The TCM layer can filter the TSP results if they are different from 0 ==> in this case the customer could forget to maintain some pricing master data. The customer wants to have a list of available carriers even if the price maintenance has been forgotten

-  The TCM layer can sort the TSP results based on pricing ==> in this case the customer doesn't want to have not relevant carrier proposed into the list

With all these reasons, we cannot deal with TCM feature for TSPS.

Best regards