Skip to end of metadata
Go to start of metadata
 System Flags

Central Allocation Miscellaneous Tables

Central Allocation CustomerList of customers available for use in Central Allocations.
Central Allocation DriversList of available drivers for use in Central Allocations.
Central Allocation On-Charge GL AccountsDetermines which GL accounts the on-charge costs will be posted against.
Central Allocation Products

Used to assign existing products for use in Central Allocations. The list displayed contains the available products for use in Central Allocations. Products listed are based on the Site Id.

Central Allocations SitesList of available site branches and their corresponding transport branches.
Central Allocation Socket ParametersDefines the serial socket parameters for the connection to the weighbridge.
Central Allocation Supplier Expense GL AccountsUsed in the case where the company has hired out a vehicle (owner vehicle) for a delivery and an expense invoice has been created. If the Supplier (as defined in Vehicle Maintenance) matches the Supplier here, then the expense invoice will use the defined GL account. If there isn't a GL account defined here for the Supplier, then it will use the GL account defined in Supplier Maintenance.
Central Allocation Trade CartageDetermines a "cost rate" for use in the calculation of On Charge costs and any Supplier invoices. The rates are broken down by customer, customer contract, distance traveled and load size. There is a default customer used here, shown by customer 000000, which is used when a customer is not set up within the miscellaneous table.

Central Allocation Flags

FeatureCALFeature code to turn on Central Allocations. 
CenDespTailoring code to determine the despatch method for Central Allocations. 
CenLogTailoring code for the day-end log file.  All postings will go into this log file for debugging purposes.  The log file is overwritten each time the day-end runs. 
Defaults to /prostix/dmp/centralAllocations.log
CenSub%The default percentage of delivery charge that all subcontractors (owner drivers) will receive. 
Defaults to 7%
CenDSplitUsed for the delivery charges where everything greater than or equal to this value will be determined to be a truck and trailer load.  Anything under this value will be a tandem load. 
This determines which column in the delivery charges to use to determine the rate.
Defaults to 20

If ticked / activated , uses the invoice date as the posting date for invoices.

If un-ticked, then the previously existing functionality of using the current system date to post apples.

(info) This only impacts invoices whose posting is delayed, such as those used in Interim Invoicing or Central Allocations.

Central Allocations is a functionality within Frameworks. It processes orders, deliveries and pick ups from quarry sites with weigh bridge integration, to enable visibility on all transport requirements throughout your business. This allows trucks to be allocated to particular jobs in a centralised manner.

Some of our customers have quarries where they sell large volumes of individual products including sand and gravel by the ton. They also have their own weighbridges to weigh the trucks that interface with Frameworks to track the weight of the products being delivered.

An order processed through Central Allocations can require multiple deliveries from multiple trucks. Orders can also be quickly duplicated in the system to allow for reoccurring orders (For example, the same order can be processed and delivered every Monday and Wednesday for three weeks).

Some of our customers sell their products to account customers and deliver to their account customers via their own trucks, however they may also have sub-contractors who also deliver products to customers. A supplier invoice is automatically created when a sub-contractor makes the delivery (as part of the overall process). Delivery rates are or can be setup differently for a customer's own drivers and sub-contractors.

Trucks driven by a customer's drivers and sub-contractors need to be defined and maintained within Central Allocations. This includes identifying those vehicles that are not roadworthy/complaint for use and therefore cannot be allocated to a delivery.

On rare occasions, some of our customers also sell their product/s via a cash sale to a customer who then takes the products in their own trailer.

(lightbulb) Prior to Central Allocations being used
, setup & configuration activities must be completed. Refer to Central Allocations - System Administration & Setup for further information.

Refer to the processes below for how to use Central Allocations: