Basic Sales Report¶
The Basic Sales Report , based on data from sales transactions located within the Work module of Dsposal's Paperwork, provides an simple overview of all sales transactions within the system. This report serves as the source for accessing information regarding sales transactions. As the basic report for the Sales Area ensuring that users obtain critical insights into active and archived sales transactions swiftly and efficiently.
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 sale was created
- Deleted sales are NOT included in the report
Fields in the report¶
| Field Name | Format Type | Description |
|---|---|---|
| salesId | Number | The unique identifier for the sales record. |
| salesNumber | Text | Paperwork-generated unique identifier for this sales transaction. |
| salesType | Text | The type of sales transaction (e.g., Price List, Quote, Agreement). |
| department | Text | The department responsible for the sales transaction. |
| contactMethod | Text | The method through which the sales transaction was initiated. |
| salesStatus | Text | The current status of the sales transaction (e.g., Won, Lost, Technical). |
| salesOwner | Text | The individual responsible for managing the sales transaction. |
| salesDate | Date/Time | The date and time when the sales transaction occurred. |
| salesExpiryDate | Date/Time | The expiry date of the sales transaction, if applicable. |
| salesReference | Text | The name assigned to this sale. It provides a descriptive label for the sales transaction, aiding in easy recognition. |
| salesDescription | Text | A description of the sales transaction. |
| customerName | Text | The name of the customer associated with the sales transaction. |
| customerId | Number | The unique identifier for the customer, if applicable. |
| customerAddress | Text | The address of the customer. |
| customerAccountNumber | Text | The account number of the customer, if applicable. |
| siteName | Text | The name of the site associated with the sales transaction. |
| customerSiteId | Number | The unique identifier for the customer site. |
| siteAddress | Text | The address of the site associated with the sales transaction. |
| siteContactName | Text | The name of the contact person at the site. |
| siteContactEmail | Text | The email address of the contact person at the site. |
| processGivingRiseToTheWaste | Text | The process or activity that generates the waste. |
| privateNotes | Text | Private notes or comments related to the sales transaction. |
| additionalDetails | Text | Additional details or information regarding the sales transaction. |
| salesCreatedDate | Date/Time | The date and time when the sales transaction was created. |
| salesCreatedBy | Text | The user who created the sales transaction. |
| salesLastUpdated | Date/Time | The date and time when the sales transaction was last updated. |
| opportunityNumber | Text | Paperwork-generated unique identifier for this opportunity, if applicable. |
| noOfWasteLines | Number | The number of waste lines associated with the sales transaction. |
| estWasteTotalPrice | Number | The estimated total price for waste associated with the sales transaction. |
| noOfExtrasLines | Number | The number of extra lines associated with the sales transaction. |
| estExtrasTotalPrice | Number | The estimated total price for extras associated with the sales transaction. |
Frequently asked questions¶
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 "customerName", "department", "salesNumber", and "noOfExtrasLines".
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.