What is a Division?
Divisions are a logical separation of following data in the TOPS Control Tower:
Masterdata: every masterdata record has a mandatory Division.
Transactions: every order (MO/SO/TO) has a mandatory Division.
Users do not have a linked Division. However, their Division access can be governed through:
Masterdata Role: to determine which Divisions they can see in masterdata tables.
AOR: to determine which Division's orders they can see.
Why would I need more than 1 Division?
The majority of TOPS customers uses a single Division, so very likely you would not need more!
Whilst a user can potentially see orders in multiple Divisions, it is not possible to cross reference between Divisions. This means that orders of multiple Divisions cannot be consolidated onto a single Transport.
The mean use-case for multiple Divisions is when there are multiple companies with a high degree of independence under the same group. Eg a global corporation using multiple ERP systems that are completely separated and where users of one Division would not be allowed access to data of the other Division.
Creating Divisions
For customers in the project phase: Work with your Project Manager to decide what the right setup is. They will create the necessary Divisions for you.
For other customers: Raise a ticket with Customer Care support.transporeon.com
System settings on Division level
There are several settings that are possible only on Division level and which consequently require a Customer Care ticket (support.transporeon.com) if you wish to change them.
General
In/Outbound: Determines if a Division can be used for inbound orders ( supplier/carrier ), outbound orders ( customer/carrier), or both?
Transport Orders
Arrival Schedule: There are 2 options to choose from, based on scheduled activity from and based on scheduled activity to. This means that we assume users ( or integration partners ) will provide either a deadline ( scheduled "to" ) or a time "from" which the pickup/delivery is possible. Based on either of these times, we will determine the stop's arrival schedule ( first milestone before activity ). If the Activity milestone has no scheduled time, the arrival schedule will be determined by the order creation time and the initial delay time.
Routing matching level: The system will always try to geocode with the highest possible accuracy. If no match has been found, the system will move down the accuracy ranking list until it reaches the Division's minimum required accuracy level. If no matches can be found, the geocoding ( and hence the routing ) will fail.
Carrier Licenses Alert: Allows alerts to be sent X days before expiration of one of the carrier's licenses which are managed in the Carrier Masterdata.
Auto-create TO: This is only valid if you wish to work with customer-facing sales orders. If TRUE, then a 1 to 1 copy of the Sales Order will be created as a Transport Order upon activation of the Sales Order. The transport order will then be shown in the transport order grid. Every milestone update that happens on the Transport Order will be transferred to the Sales Order.
Apply Sales & Purchase Rates: This is only relevant if you use the system for your freight settlement. If checked, rates and surcharges will always be added or recalculated upon saving the order to reflect its current state. If unchecked, then rates and surcharges will remain unchanged and need to be manually selected and updated using the select rates button on the order form.
Assign Chat to a group: Ensures users are alerted when someone sends a chat. This way, the notification is not just sent to users involved in the order. It is sent to all users in the user's group. See user group documentation for further explanation on user management.
Require billing file to complete: An order cannot reach status "complete" if a Sales Billing File or a Purchase billing file was not created. This feature was added to make sure orders are properly billed before they can be considered complete. This is only relevant if you want to use the system for your freight settlement.
Invoice Reference Prompt: Generates a pop-up upon invoice/PO creation to allow the user to add a reference to a Sales Billing File or a Purchase billing file
Require truck license plate: If activated, actual times entry will be blocked unless a license plate is provided.
Sales Orders
Sales order confirmation: An extra confirmation will be required when activating a sales order whose costs exceed the value entered in the amount field. The confirmation will be a pop-up shown to the user asking the user if they are sure they want to activate given that the order amount exceeds the allowed amount.
System generated documents
Transport Document: If enabled, the system will automatically generate a transport document each time a new Transport Order is created. The document will be generated in the language mentioned on the Transport Order (or default to English if there are no translations). The document will become available in the documents section on MO and TO level in the TOPS Control Tower, and also in the mobile application and carrier portal.
Power of Attorney for the Transport Document: If checked, the system will recognise the label "CT_TRANSPORTDOCUMENT_POA" on Material Order to then request driver to sign on behalf of the customer/supplier.
Generate POC: The POC document (PDF) is generated upon entry of an actual time of collection.
Generate POD: The POD document (PDF) is generated upon entry of an actual time of delivery.
Customer URL & Slogan: These will appear at the bottom of the POC and POD documents.
Mobile
Mobile consolidated stops: If checked, we will display all collection & delivery items of a stop into a single consolidated screen to the Mobile user.
β
βΒ