The solution not handling dimension values on transfer orders based on the two underlying transactions (shipment, receipt) makes Direct Transfers unusable for users with dimension values (with controls) on Locations as they cannot post.

Even with not-direct Transfer Orders, the steps to post are unnecessarily cumbersome if dimension values with controls are assigned on Locations.

Posting the shipment requires the Dimension Value of the 'Transfer-From' Location. Posting the receipt requires the Dimension Value of the 'Transfer-To' Location. The 'Transfer-From' Location is entered before the 'Transfer-To' Location. when a user enters a transfer order. The steps to successfully and accurately post are:

1. Enter transfer order header (and lines but those can be done after)

2. Re-enter the 'Transfer-From' Location and say 'Yes' when asked if you want to update the dimensions on the lines.

3. Post the shipment.

4. Re-enter the 'Transfer-To' Location and say 'Yes' when asked if you want to update the dimensions on the lines.

5. Post the receipt.

This obviously cannot work with Direct Transfers. The only solution for Direct Transfers to post is to not use a ‘Same Code’ control on Location default dimensions and use ‘Code Mandatory’. This removes a control that could have an adverse impact on postings for other transaction types which is not the best workaround. The dimensions attached to the transfers are also inaccurate as only the last entered dimension value is used but since transfer orders only post to balance sheet accounts, it's not necessarily a concern (dimensions would typically not be required or reported on at the balance sheet).