Booking Revision Rule ID: Unique identifier of the booking revision rule.
Description: Description of the booking revision rule.
Division: Division for which the booking revision rule is assigned. When defined, only the booking revisions associated with the same division are eligible to use this booking revision rule. Otherwise, this rule can be used across all divisions.
Active: Determines whether the booking revision rule is active.
Options
Booking Revision Action:
Needs Review: When applicable, the booking revision will have status set to Open and will require review by analyst before accepting or rejecting a booking revision.
Auto-Accept: When applicable, the booking revision will be automatically accepted if routing, rating, and scheduling (RR&S) succeeded according to the accepted proposed changes from booking revision. If failed, then the booking revision status will remain as Open and review/manual accept can be executed from the booking revision properties.
Auto-Reject: When applicable, booking revision will be automatically rejected. Booking revision status will be changed to Rejected and the tender request is set to Canceled. Associated booking and loads will be processed according to the option selected from Reject Option.
Reject Option: Required if the Booking Revision Action is Auto-Reject.
Cancel Tender: When applicable, in addition to reject booking revision, booking tender cancel operation will also be executed.
Remove Booking: When applicable, in addition to execute reject booking revision and booking tender cancel operation, cancel booking operation will also be executed.
Collapse Itineraries: When applicable, in addition to execute reject booking revision and booking tender cancel operation, the operations of cancel booking, cancel loads and collapsed shipment itineraries will be executed. Itineraries will be collapsed for shipments only if all below conditions are satisfied. For shipments that violate any conditions, the shipment itineraries will not be collapsed and shipment legs will not be removed from dependent loads but all other cancel actions will be performed:
Shipment must be not ‘On Hold’ AND
Shipment legs do not have conflicting hard commitments AND
All dependent loads of the shipment must have operational status less than Tendered or equal to Tender Rejected.
Tender Cancel Reason Code: The reason code applied when rejecting a booking revision. Required if Booking Revision Action is Auto-Reject.
Tender Update Reason Code: The reason code applied when accepting a booking revision. Required if Booking Revision Action is Auto-Accept.
Issue Tender Update: If selected, after successfully accepting a booking revision, booking Tender Update process will be executed if booking information is changed and uses same carrier. If booking information remains unchanged, then tender is not updated. If booking carrier is changed, then tender associated with booking revision will be canceled and new tender will be issued. When deselected, a Booking Tender Update will not be issued.
Route, Rate and Schedule Options
Update Itinerary Timetable Entry: When applicable, the itinerary timetable entry used by the booking will be updated according to the un-rejected changes from booking revision. Following are the possible options:
Never: Itinerary Timetable Entry will not be updated when Auto-Accepting a booking revision. Error will occur when ‘Maintain Itinerary Timetable Entry’ is executed manually.
Manual: Itinerary Timetable Entry will not be updated when Auto-Accept is performed. However, users will have an option to manually execute the ‘Update Itinerary Timetable Entry’ operation.
Auto-Update: Itinerary timetable Entry will be updated automatically based on the changes from booking revision when Auto-Accepting. However, the automatic update is only allowed for booking revision without carrier or location changes. If auto-accept failed and manual accept is required, you will have an option to manually execute the system supported ‘Update Itinerary Timetable Entry’ operation.
Apply Resource Constraints: Enable or disable Resource Constraints for all loads on booking when RR&S is executed upon accepting the booking revision.
Override Weight/Volume Constraints: Enable or Disable for all loads on booking when validating the feasibility of changes upon accepting the booking revision.
Disable Route, Rate and Schedule: Allows you to specify whether the route, rate and schedule can be disabled according to the proposed change on booking revision when this booking revision rule is applied. If the primary schedule information is changed without a change in the carrier or locations, then the requirement of booking route, rate and schedule when accepting the booking revision will depend on this setting. Following are the possible options:
Never: Route, rate and schedule cannot be disabled when accepting the booking revision.
Manual: Route, rate and schedule is allowed to be disabled when manually accepting the booking revision.
Auto-Update: Route, rate and schedule is disabled when auto-accepting the booking revision. When manually accepting the booking revision, you must manually disable Route, rate and schedule.
Rule Assignment Conditions
The conditions in Booking Revision Rule can be defined for each booking revision attributes (Carrier, Booking Departure Date, Booking Arrival Date, Booking Departure Location, Booking Arrival Location, Vessel Name, Voyage Number, Shipping Instruction Date, and Container Yard Date) plus an indicator of whether the equipment is changed. Conditions for a range of durations is supported for all date related attributes.
Conditions Matching Criteria:
No Difference On Proposed Change: This rule will be eligible for a booking revision having all proposed change values are same as existing values on the booking.
Any Proposed Conditions Matched: This rule will be eligible for a booking revision if proposed change satisfies any of the condition. Undefined conditions will be excluded from the comparison.
All Conditions Matched: This rule will be eligible for a booking revision if all proposed changes are satisfied for all defined conditions. Undefined conditions will be included in the comparison. For an undefined condition, it will consider as satisfied if booking revision does not have proposed change or having proposed value same as existing booking value.
Matching criteria examples
Booking Revision Rule 1 conditions defined for:
Departure Date – change later for 2 or more days
Vessel Name – change to VESL1
Voyage Number – change to VOYG1
Booking Revision 1 has
Departure Date delay by 3 days.
Shipping Instruction Date/Time delay by 1 day
For ‘Any Proposed Conditions Matched’, Rule 1 is eligible because departure date/time condition satisfied.
For ‘All Conditions Matched’, Rule 1 is not eligible because Shipping Instruction is not defined in the rule.
Booking Revision 2 has
Departure Date change early by 2 days
Vessel Name change to VESL2
Voyage Number change to VOYG2
For ‘Any Proposed Conditions Matched’, Rule 1 is NOT eligible because none of the conditions satisfied.
For ‘All Conditions Matched’, Rule 1 is NOT eligible because none of the conditions satisfied.
Booking Revision 3 has
Departure Date delay by 2 days
Vessel Name change to VESL1
Voyage Number change to VOYG1
For ‘Any Proposed Conditions Matched’, Rule 1 is eligible because at least one of the conditions satisfied (vessel / voyage / Departure Date).
For ‘All Conditions Matched’, Rule 1 is eligible because all conditions are satisfied.