--- title: "Transport Scheduling - Setup and Configuration" canonical: "https://kb.myframeworks.com.au/space/FRAM/28410354/Transport%20Scheduling%20-%20Setup%20and%20Configuration" format: markdown --- # Overview > ⚠️ The Transport Scheduling is feature code driven. Before Transport Scheduling can be used the following system administration activities marked (*required*) must be completed. Also, depending on your business requirement, there are some are recommended (*optional*) settings. Refer to the following processes for further information  # Feature Code The following feature code is required to be **Active **for **Transport Scheduling **to available as a module via the Frameworks menu - **TPO** - Transport Scheduling > ✅ Refer to [Feature Codes](https://kb.myframeworks.com.au/space/FRAM/595952322/Feature+Codes) for more information. # System Settings and Flags ## Miscellaneous Tables Click **Frameworks **then navigate to **System Administration > System Tables > Miscellaneous Table Maintenance **then search for and setup the information for the below tables: ### 1. Central Allocation Vehicle Configurations (*Required*) In this table you can add **Vehicle Configuration **codes to be used when defining vehicles in [Vehicles Maintenance](https://kb.myframeworks.com.au/space/FRAM/610436048/Vehicles+Maintenance).  ![image](media://1372920c-22f0-4064-aec3-b30ba1f5055d) > ⚠️ **InstallerFW5120** - is required to be installed via the **Miscellaneous Table Installer** to be able to access the **Central Allocation - Vehicle Configuration** miscellaneous table. ### 2. System - Shipping Basis Codes (*Recommended*) If you require to despatch pick-ups for purchase orders, then you will need to configure a **Pick-Up **shipping basis code to view the orders in Transport Scheduling.  ![image](media://ed13d9e1-d21f-4248-99c5-a30b81f8c876) ### 3. System - Requested Delivery Times (*Optional*) In this table you can add predefined **Requested Time**. You can also define colours for the times to help more easily view the different times throughout Transport Scheduling   ![image-20241207-132643.png](media://281d8b50-aae1-446f-b88a-f9cbde532517) ### 4. Delivery - Drivers (*Optional*) In this table can add **Drivers **that can be used when defining the default runsheet headers. ![image](media://5272209a-c7f9-4c8f-9301-f95a9281573e) ### 5. Delivery - load Types (*optional*) In this table you will need to have defined the **Load Types **which can be displayed within the **Delivery Maintenance **window in Transport Scheduling.  ![image](media://6d7ffba7-2e04-4b35-a7d3-47aeab4ecbed) ### 6. Delivery - Map Reference (*optional*) In this table you can add **Map References **which can used by the Transport Scheduling to plan deliveries.  ![image](media://ac22fcab-778f-4b7e-885a-3d15ecfb4cd4) > ✅ Refer to [Delivery Map Reference Maintenance](https://kb.myframeworks.com.au/space/FRAM/595984947/Delivery+Map+Reference+Maintenance) for more information. ### 7. Delivery - Transport Companies (*optional*) In this table you can add a **Transport Company **which can be displayed within the **Delivery Maintenance **window in Transport Scheduling.  ![image](media://b7c8e28a-2cff-4d04-93fd-2b2063b0c5c4) --- ## System Settings - Flags The following system flags are not required, however depending on your business needs they may be beneficial. From the Frameworks menu navigate to **System Administration > System Tables > Miscellaneous Table Maintenance** and then search for **System Settings - Flags**. Then in the filter section you can search for and enable the following flags as required.  1. **SOPConfDDt** - Capture confirmed delivery date on Sales Orders (*Recommended*). - This will allow the delivery date to be highlighted when it has not been confirmed 2. **FWPKENT **- Enable Enterprise Picking. - With enterprise picking enabled transport scheduling with display the orders picking status. 3. **BranchDefDesp** - Use branch default despatch method. - On opening Transport Scheduling screen, the orders with the default despatch method will display first 4. **DelMapForce** - Enforce the delivery area based on the map ref. 5. **ManEntryBndl** - Manual Entry of Bundles - When enabled, the Vehicle Load Sheet output in Runsheet Maintenance includes bundle count, bundle type and assembly location detail for each order, plus a **P/L Taken** checkbox for the driver to manually confirm collection. --- # Other Configuration Considerations Below is a list of other configuration considerations when using the Transport Scheduling module. These are: > ℹ️ Click on a heading below for more information. ### 1. Despatch Method Maintenance (*Required*) In this table you will need to have defined the **Delivery, Courier **and/or **P and D** (Pick and despatch) despatch types for the **Despatch Methods** to be available from within Transport Scheduling.  ![image](media://5d16eca1-ee5f-4aa2-a010-b4e897788ee0) > ✅ Refer to [Despatch Methods Maintenance](https://kb.myframeworks.com.au/space/FRAM/556007984/Despatch+Methods+Maintenance) for more information. ### 2. Vehicle Maintenance *(Required)* - Allows you to create the vehicles required to be added to your runsheets. > ✅ Refer to [Central Allocations - Setup and Configuration](https://kb.myframeworks.com.au/space/FRAM/609847215/Central+Allocations+-+Setup+and+Configuration) for more information. ### 3. Company and Branch Maintenance (*Recommended*) - Ensure that you have defined the **Addresses** for your company and branches for the maps work correctly. (*Required*) - Define each branches default despatch method. (*Optional*) > ✅ Refer to [Company Maintenance](https://kb.myframeworks.com.au/space/FRAM/595788530/Company+Maintenance) and [Branch Maintenance](https://kb.myframeworks.com.au/space/FRAM/542484345/Branch+Maintenance) for more information. ### 4. Branch Non Despatch Days (*Recommended*) - Allows you to create blocked out dates within the calendar for which deliveries cannot be scheduled. > ✅ Refer to [Branch Non Despatch Days](https://kb.myframeworks.com.au/space/FRAM/595764643/Branch+Non+Despatch+Days) for more information ### 5. Runsheet Defaults Maintenance (*Optional*) - Allows you to setup and define Runsheet Defaults per Branch, Truck, and Driver. > ✅ Refer to [Runsheet Defaults Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401778) for more information. ### 6. Warehouse/Assembly Locations (*Optional*) - If you are not using Assembly Location, this might assist you to better define where your orders are allocated to, once picked, in preparation for despatch. > ✅ Refer to [Warehouse and Assembly Locations](https://kb.myframeworks.com.au/space/FRAM/571509790/Warehouse+and+Assembly+Locations) for more information. --- # Scheduled Tasks The **Build Default Runsheet Headers** scheduled task will add the default runsheet configurations to the next 7 days. From the Frameworks menu navigate to **System Administration > Task Scheduler > Schedulable Tasks > Build Default Runsheet Headers** from the navigation tree. > ✅ Refer to [Schedulable Tasks](https://kb.myframeworks.com.au/space/FRAM/511934716/About+Schedulable+Tasks) for more information. --- # Additional Information  > ✅ Refer to the [Transport Scheduling](https://kb.myframeworks.com.au/space/FRAM/7373187/Transport+Scheduling) User Manual for more information.