Version Version Date Changes

General

Shippers can now define attribute-based restrictions at the loading point level in the Manage Entities app. These restrictions allow the system to evaluate whether a loading point is suitable for a specific shipment based on shipment attributes or carrier. Previously, all loading points in a docking location were available for selection during appointment booking regardless of shipment-specific requirements, leading to manual corrections by shippers when carriers booked the wrong loading point.

Feature Availability

New Features in Release 2606

• Shippers can define attribute-based restrictions per loading point in Manage Entities
• During appointment booking, loading points are evaluated against shipment attributes
• Carriers see only compliant loading points when using the Self-Book Dock Appointments app; non-compliant loading points are filtered out
• Shippers using the Manual Dock Appointments app are notified when a non-compliant loading point is selected but can override the restriction
• Attribute values are sourced from the central codelist (Assign Codes App) , ensuring consistent terminology across entities 

Attribute-Based Restrictions – Manage Entities (Shipper)

Shippers configure loading point restrictions in Manage Entities under the loading point entity. A new Attributes section allows creating, viewing, updating, and deleting attribute-based rules for each loading point.

To configure loading point restrictions:

1. Open the Manage Entities app.
2. Navigate to the Loading Points section and select a loading point.
3. Go to the Attributes section.
4. Add one or more attribute restrictions by selecting an attribute and the permitted values from value help.
5. Ensure the Attribute is Enabled. 
6. Save the loading point.

Note:

• Transport Means Type and Transport Means Description: Attribute values available for selection are sourced from the central codelist (Assign Codes App). Either the SAP codes are already sent or a mapping from the customer to SAP code must exist.
• Dangerous Goods: True if one cargo item is dangerous goods relevant
• Carrier: All carrier business partner with a relationship to shipper

Attribute-Based Restrictions – Self-Book Dock Appointments (Carrier)

When a carrier books an appointment via the Self-Book Dock Appointments app, the system evaluates the loading point restrictions against the shipment attributes of the freight order based appointment request or the attributes defined in the appointment request sent via Provider API for Dock Appointment Scheduling (GenericAppointment_In ).

Only loading points where all attribute restrictions are satisfied are offered for selection to the carrier user.

In case no restriction was configured or all attributes match, carrier in Self-Book Dock Appointment App will have all Loading Points available in the LP drop-down.

In case one of the configured attributes do not match, carrier in Self-Book Dock Appointment App will only have the option to select from the available Loading Points as not compliant ones are filtered and not allowed for appointment booking.

Note: If no compliant loading points are available for the shipment, the carrier receives an error message indicating that no bookable loading points exist for this appointment.

Attribute-Based Restrictions – Manage Dock Appointments (Shipper)

When a shipper creates or modifies an appointment manually via the Manual Dock Appointments app, the system evaluates the selected loading point against the shipment attributes. If the selected loading point does not satisfy the configured restrictions, the shipper receives a warning notification.

Shipper in MDA can select all Loading Points assigned to a Docking Location and sees a checkbox or a warning icon in front of the LP, which indicates if a LP is compliant or non-compliant for appointment to be maintained.

Unlike carriers, shippers can proceed with the booking even when a non-compliant loading point is selected, but get a warning message to be fully aware that a non-compliant Loading Point was selected.

Supported Scenarios

Further Information