Comments
I totally agree with you Zach. These changes you suggest would be very beneficial to the base functionality in this screen.I've been using this Transport load screen mainly to ship full trucks of license plates coming cross docking works generated from different sales orders between several legal entities and multiple destination without load planning them and I know for sure; mistakes can be easily happened. Every Transport load generated for the company I work for is usually shipped to one Site destination and having multiple destinations in a Transport load ID is avoided to not mess with the documentation. I would also suggest including in the enhancement of this screen the following:Let the transport screen generate its own Bill of Lading with the current information of what is loaded in the Transport load. Currently, if you hit Generate BOL, D365 will generate multiple times documents based on the shipments and orders on the Transport loads, meaning, it will generate separately a BOL times the number of orders in the Transport load instead of giving the user only one Bill of Lading for that Transport load.I would think in adding a block or Warning to the Transport loading MDMI that let the user know they are adding a different Sales orders destination for Intercompany orders so they can back up and if would load a pallet to a wrong destination.
This is a very important idea for the internal IT controls and much needed, also the vendor on hold is something that can relate to the payments for this vendor, so just like the other fields that are already included with financial impact right now in the Proposed vendor changes workflow.
We ran into a similar issue. We ran the update on one specific PO, and it removed records for many other workflow records on the VendInvoiceInfoTable. This caused a lot of workflow approvals to become inaccessible and thus a high audit risk. We highly recommend a warning message or functionality update, so this unintended consequence does not happen to others in the future.
We ran into a similar issue. We ran the update on one specific PO, and it removed records for many other workflow records on the VendInvoiceInfoTable. This caused a lot of workflow approvals to become inaccessible and thus a high audit risk. We highly recommend a warning message or functionality update, so this unintended consequence does not happen to others in the future.