Basic Jobs Report¶
The Basic Jobs Report offers a comprehensive overview of transactional activities within the Work module of Dsposal's Paperwork. It serves as a fundamental tool for accessing critical information regarding various job-related transactions, providing users with essential insights into job statuses, customer details, waste management specifics, and logistical aspects. This report streamlines the process of tracking and managing job-related data, ensuring swift and efficient access to essential information for effective decision-making and workflow management.
Before you start¶
Before getting started, there are a couple of helpful things to know:
- The date from and to fields relate to the dates when the job scheduled OR when the job was requested by the client and all jobs that have NO date assigned to them.
- Deleted jobs are NOT included in the report.
Fields in the report¶
Field Name | Format Type | Description |
---|---|---|
jobId | Number | The unique identifier for the job record. |
jobNumber | Text | Paperwork-generated unique identifier for this job. |
quoteNumber | Text | Paperwork-generated unique identifier for this sales transaction. |
consignmentNoteCode | Text | Code for the consignment note related to the job. |
jobName | Text | The name assigned to this job. It provides a descriptive label for the job, aiding in easy recognition. |
jobDescription | Text | Description of the job. |
jobStatus | Text | Current status of the job (e.g., Invoiced, Completed). |
contactMethod | Text | Method of contact for the job (e.g., Existing Customer, Email). |
jobDate | Date/Time | The date and time when the job was either requested OR scheduled. |
accountNumber | Text | Account number of the customer associated with the job. |
customerName | Text | Name of the customer associated with the job. |
customerAddress | Text | Address of the customer associated with the job. |
customerSector | Text | Sector or industry of the customer associated with the job. |
customerContactName | Text | Name of the contact person at the customer's organisation. |
customerContactEmail | Text | Email address of the contact person at the customer's organisation. |
requestedByName | Text | Name of the individual who requested the job. |
requestedByEmployeeNumber | Text | Employee number of the individual who requested the job. |
customerDepartment | Text | Department within the customer's organisation. |
invoicingName | Text | Name for invoicing associated with the job. |
invoicingAddress | Text | Address for invoicing associated with the job. |
siteName | Text | Name of the site where the job is taking place. |
siteAddress | Text | Address of the site where the job is taking place. |
siteAdminDistrict | Text | Administrative district of the site. |
siteAdminDistrictEA | Text | Environment Agency administrative district of the site. |
siteRegion | Text | Region of the site. |
siteContactName | Text | Name of the contact person at the site. |
siteContactEmail | Text | Email address of the contact person at the site. |
jobOwner | Text | Owner or responsible person for the job. |
department | Text | Department responsible for the job. |
purchaseOrderNumber | Text | Purchase order number associated with the job. |
processGivingRiseToTheWaste | Text | Process that generates the waste associated with the job. |
carrierName | Text | Name of the carrier responsible for transporting waste. |
carrierAddress | Text | Address of the carrier responsible for transporting waste. |
carrierRegistrationNumber | Text | Registration number of the carrier. |
carrierLicenceType | Text | Licence type of the carrier. |
disposalSiteName | Text | Name of the disposal site for waste. |
disposalSiteAddress | Text | Address of the disposal site for waste. |
disposalSiteAdminDistrict | Text | Administrative district of the disposal site. |
disposalSiteAdminDistrictEA | Text | Environment Agency administrative district of the disposal site. |
disposalSiteRegion | Text | Region of the disposal site. |
disposalSitePermitNumber | Text | Permit number for the disposal site. |
disposalSitePermitType | Text | Permit type for the disposal site. |
jobContainsHazardousWaste | Boolean | Indicates if the job contains hazardous waste (Yes/No). |
jobContainsADRWaste | Boolean | Indicates if the job contains ADR (Accord européen relatif au transport international des marchandises Dangereuses par Route) waste (Yes/No). |
noOfWasteLines | Numeric | Number of waste lines associated with the job. |
estWasteTotalPrice | Currency | Estimated total price for waste associated with the job. |
noOfExtrasLines | Numeric | Number of extra pricing lines associated with the job. |
estExtrasTotalPrice | Currency | Estimated total price for extras associated with the job. |
driverName | Text | Name of the driver associated with the job. |
driverEmployeeNumber | Text | Employee number of the driver associated with the job. |
vehicleRegistrationNumber | Text | Registration number of the vehicle used for the job. |
vehicleType | Text | Type of vehicle used for the job. |
co2Emissions | Text | CO2 emissions associated with the job. |
costPerMile | Currency | Cost per mile for transportation associated with the job. |
assetName | Text | Name of the asset associated with the job. |
createdBy | Text | User who created the job. |
invoiceNumberMostRecent | Text | Most recent invoice number associated with the job. |
invoiceNumbers | Text | List of invoice numbers associated with the job. |
purchaseOrderNumbers | Text | List of purchase order numbers associated with the job. |
creditNoteNumbers | Text | List of credit note numbers associated with the job. |
Frequently asked questions¶
Why is there an additional Environment Agency administrative district?
Dsposal Paperwork uses ONS data for site location purposes, whereas the Environment Agency employs distinct names and districts for waste reporting. Paperwork accommodates these variations by offering both datasets to address diverse scenarios effectively.
What is a field?
A field refers to a single piece of data within a dataset, also known as a column or attribute. It represents a specific characteristic or attribute of the data being collected or analysed. For example, in a dataset of opportunity information, fields may include "department," "salesType," "customerSite," and "lostReason".
Why do your field names look funny?
We use a computer programming convention called camel case
(more accurately lower camel case) where multiple words are combined into a single word, with each word (except the first one) capitalised and no spaces between the words. The name "camel case" comes from the capitalisation's resemblance to the humps of a camel.