Show TOC

Function documentationIncompatibilities Locate this document in the navigation structure

 

You use incompatibilities to define the compatibility of planning data that the system is to take into account during transportation planning, for example:

  • Freight units with different Incoterms must not be transported together.

  • Refrigerated goods must only be transported in appropriate means of transport (refrigerated trucks).

  • A certain means of transport cannot be unloaded at a location since the location does not have a suitable loading ramp.

In this way, you can control how freight units are assigned to vehicle resources in manual planning, for example.

Note Note

For consistency reasons, you can define incompatibilities only. To define a compatibility, you have to define an incompatibility with all other attribute values.

End of the note.

Features

You can define incompatibilities in different ways.

On the one hand, you can define incompatibilities between any two attributes of two business object nodes. To do so, you define two conditions and specify the relevant results. Two business object instances are then incompatible if the result of the condition matches these relevant results.

On the other hand, you can enter only one condition and select the Ident. Values Only (Identical Values Only) checkbox. In this way, you can define an incompatibility between two instances of the same business object (BO), for example, two freight units. The two BO instances are then only incompatible if their values differ. If a planning run comprises many business objects and the attribute can have many values, performance might be reduced. In this case, we do not recommend that you use this option.

Alternatively, you can use customer-specific logic to determine the pairs of incompatible objects. To do so, choose the option External Determination Strategy in the Determination Method field and specify the required strategy in the External Determination Strategy field. For more information, see External Strategies. If you define incompatibilities with conditions and a freight unit has several products, the system only determines the first product, and it does this randomly. You can avoid this restriction by using example strategy TM_INCOMP. In this case, you specify two products that are incompatible in your incompatibility. The example strategy then checks whether the freight units contain these products. TM_INCOMP serves as an example strategy for incompatibilities, the class assigned describes the interface and serves as reference implementation for customer-specific classes. The unit tests serve documentation purposes.

The example strategy shows that condition-based incompatibilities are not always suitable. However, if a freight unit has only a single product item (package items or container items can, however, also exist), a filter on the item type Product in the condition is sufficient.

You use the incompatibility area to define the area in which the system is to take into account an incompatibility:

  • Manual planning, VSR optimization, and generating transportation proposals

  • Creating freight units

  • Carrier selection (including continuous move)

  • Creating delivery proposals

VSR optimization considers incompatibilities as hard constraints.

You use the incompatibility type to define the BOs between which an incompatibility is to be valid. For example, you can use the incompatibility type FU – Compartment to ensure that a freight unit is not transported in a certain compartment. You can also use the incompatibility type to define the incompatibility level.

Note Note

You can define incompatibilities between freight units on three incompatibility levels:

  • Vehicle level (this means that the two freight units must not be transported in the same vehicle or in the same compartment)

  • Compartment level (this means that the two freight units must not be transported in the same compartment)

  • Means-of-transport combination level (this means that the two freight units must not be transported in the same vehicle, in the same compartment, or in the same means-of-transport combination)

End of the note.

Note Note

  • Compartments and means-of-transport combinations are nodes of the BO vehicle resource. In this case, you have to use the node COMPARTMENTITEM or MEANS_TRANSP_COMB from the BO vehicle resource.

  • A condition type exists for each BO node that the system uses in an incompatibility type.

End of the note.

Furthermore, when defining your incompatibility, you can specify whether the system is allowed to violate incompatibilities during manual planning, VSR optimization, or background processing. You can override this setting in the incompatibility settings.

In the incompatibility settings, you specify which incompatibilities the system is to consider in a certain incompatibility area. You can assign them to your planning profile, your carrier selection settings, and your freight unit building rule. Moreover, you can define default incompatibility settings, for example, for a certain incompatibility area. This system considers these if you have not assigned any incompatibility settings to the specified profiles.

Note Note

When you access the transportation cockpit, the system checks for incompatibility settings in the following order: in the profile and layout sets, in the planning profile, and in the default incompatibility settings.

If you then create a freight order or a freight booking directly in the transportation cockpit, the incompatibility settings that were identified when you accessed the cockpit are assigned to the business document. When you open the freight order or freight booking document directly, these settings are then used for the incompatibility check.

After you have defined an incompatibility, you can perform a simulation.

If you want to simulate an incompatibility with the incompatibility type Freight Unit – Freight Unit (Vehicle Level), for example, you specify two freight units. In this case, the system checks whether an incompatibility exists between the two freight units.

End of the note.

Activities

You can define incompatibilities in SAP NetWeaver Business Client by choosing   Application Administration   Planning   General Settings   Incompatibility Definitions   Create Incompatibility  .

You can define incompatibility settings in SAP NetWeaver Business Client by choosing   Application Administration   Planning   General Settings   Incompatibility Settings   Create Incompatibility Settings  .