¶ Booking, shipment & trip
¶ Booking
An order is the agreement that a transport company makes with their client to transport something from A to B. Everything that is agreed upon can be found in that order. In Transpas we distinguish between salesorder (also called transportbooking) and shipment.
The booking contains information such as the customer. Therefore all shipments within a booking have the same customer.
Other terms used: order, transportbooking, booking, or salesorder.
¶ Shipments
A booking contains shipments. A booking can contain 1, or more shipments. On the shipment information is recorded such as the loading and unloading address, the goods and the tariff.
A shipment can be split, for example when the goods are first loading into vehicle 1 en are unloaded the next day by vehicle 2. A shipment then has 2 or more legs or trajectories. We call these planlegs.
Other term used: Leg
¶ Trip
A trip is a collection of one or more planlegs, executed by a truck, trailer, and driver.
The moment that the truck or driver of a trip is changed, we are talking about decoupling. It is like the trip is split into two subtrips: each subtrip has its own resourcecombination (rc).
A trip normally follows the trailer.
A trip can last a day, or a daypart, but trips can also last several days or even a month. It is up the planner where a trip begins and ends, Transpas Enterprise is very flexible there.
¶ Department & Plangroup
Departments are regularly confused with plangroups.
Roughly one can say the following: departments have to do with shipments, plangroups have to do with trips.
¶ Department
- A booking consists of a bookingline with 1 or more shipments.
- Every booking automatically is assigned a Department. This is the department that is visible in the top of the transportbookingscreen when the booking order is created.
- All shipments in the booking belong to the same departement (contrary to the plangroup).
- A department contains multiple standard settings for filling in orders.
¶ Plangroup
This is a collection of orders, planlegs, vehicles and trips which belong together.
A plangroup can be set on an order, a planleg, a resource or a trip. Plangroups offer the possibility of gaining an overview of the planning. A list of 1000 planlegs is difficult to manage. By dividing these into plangroup you get a lot more overview, for example:
- Plangroup Export: All planlegs from the crossdock to Germany.
- Plangroup Fetch: All the planlegs that end at the crossdock.
¶ Purchase invoicing & Sales invoicing
¶ Purchase invoicing
Purchase invoicing is everything related to processing of purchase invoices. Up until making a booking in your financial software.
A creditor is always involved in purchase invoicing, this is the party that sends you an invoice. This could be a charter, a cleaning stations or a ferry company.
These are all costs.
¶ Sales invoicing
Sales invoicing is everything related to processing sales invoices.
A debtor is always involved in sales invoicing, this is customer whom you send an invoice.
This is income.
Sales invoices are made, printed and e-mailed in Enterprise. Only the booking is sent to the financial application.
¶ (Financial) Relations
Two screens have a lot in common: Financial relations and Relations.
- Financial relations: these are all relations that are a debtor or creditor.
- Relations: All relations, so also loading/unloadingaddresses, depots, terminals, etc. But also the financial relations, only without the financial data.
Data of employees is recorded separately in the screen employees.
A financial relation is always also a relation, but a relation is only a financial relations when the box Debtor and/or Creditor is checked.
Only then this relation becomes visible in Financial relations. In that screen extra data for this relations can be stored, such as VAT number, bankaccountnumber, information for invoicing, etc.
A relations (financial or otherwise) always has one or more addresses, which are visible on the tab sheet Addresses. Every address has a type (postal address, delivery address, invoicing address, depot, etc.)
What is shown in the top grid depends upon the screen:
- In the screen Financial relations in the grid the postal address is shown.
- In the screen Relations in the grid the delivery address is shown.
These are properties which you can check on the tab Address details.
¶ Resourcecombination
A resourecombination is, as the name suggests, a combination of resources.
More specifically a combination of truck, trailer(s) and driver(s) (and optionally a forklift) as this exists for a trip.
When within a trip there is no coupling or decoupling (apart from the first and last activity) a trip has 1 resourcecombination. Is there a change of truck or driver halfway through the trip? Then 2 resourcombinations are created.
The resourcecombinations can be seen on the tab sheet Costs in the screen Planning.
¶ Technical concepts
Below are some concepts which for regular users of Transpas aren't very interesting.
When building custom functions it can be useful when some things can be addressed specifically.
That's why some technical concepts are explained here.
¶ Grid
The grid is the table with fields that's often displayed in the top half of the screen.
The grid is used to display information of multiple lines at once, for instance transportbookings or shipments.
Let's take the screen Transport bookings as an example.
In the top we see the ordergrid.
¶ Fieldscrollbox
The fieldsscrollbox, also calles FSB, is the part, often in the lower half of the screen, containing information about that specific line.
More information is often displayed in the fieldscrollbox then in the grid, this is used to record more detailled information.
This is the fieldscrollbox of a goods line.