Based on the information you provided, it appears that there may be an issue with how the Bookable Resource Start and End Location is configured to use the Organizational Unit address for travel time calculation. Here are a few potential suggestions for troubleshooting the issue:
1. Verify that the Organizational Unit address is set up correctly in Dynamics 365 Field Service. This could include checking that the latitude and longitude for the address are accurate and up-to-date.
2. Ensure that the Bookable Resource is correctly associated with the Organizational Unit. If the association is incorrect, this could be causing issues with the travel time calculation.
3. Consider reviewing the Field Service settings to see if there are any configuration options related to travel time that may be impacting the Bookable Resource Start and End Location calculation. This could include settings related to distance units, preferred routing, or other similar options.
4. If none of the above suggestions resolve the issue, it may be worth reaching out to Microsoft support for further assistance. Microsoft support can provide more in-depth troubleshooting and diagnostic tools to help identify and resolve the issue.
In general, it's worth noting that while Dynamics 365 Field Service is designed to be highly configurable and customizable, there may be instances where additional customization or configuration is necessary to achieve a desired outcome. If you're unable to resolve the issue through standard configuration options, you may need to explore additional customization options, such as plugins or flows, to achieve the desired outcome.
