There are many fields for work tickets to capture the details about the work. This topic explains the meaning of each field on the All Work Tickets page (fields are listed in alphabetical order).
The most commonly used fields are visible by default, arranged in a default order, but you can change the column visibility and order to your liking and then save the grid layout for future use. If you have many different kinds of work tickets, you may want to create a layout for each kind of ticket since the fields that are relevant may vary. For example, the fields relevant to a silviculture planting activity are likely to be different than the fields relevant to a road maintenance activity, so you can create two different layouts. For more information about changing the appearance of the grids, please see Grids.
| Field Name | Description |
| Activity | ID indicating the specific type of work (service) performed (for example, 103-Chemical_Spray). |
| Activity Details | Freeform text providing more details about the work that was performed. This is useful for example if the activity is more general. |
| Additional Fees | Indicates if there are additional fees associated with the ticket (Yes or No), the idea being to flag all records for a particular ticket the same way. (that is, some or all of the records for the ticket are the additional fees). This allows you to filter tickets that may require extra review. |
| Approved | Indicates if the ticket has been reviewed and approved (is considered to be correct or not). Value should be Yes, No or blank (Null). |
| Attachment Attachment Description Attachment Filename | A file attached to the ticket. When a ticket has an attachment, a download button is displayed in the Attachment column; when clicked the attachment is downloaded. |
| Block | ID of the Block within a Source location where the work was performed. |
| Contract | ID of the contract that governs the work being performed (for example, contract for silviculture planting services). |
| CR | Credit account code for the work. |
| Created By Created Date | ID (such as e-mail address) of the user that created the record. Date/Time when the record was created. |
| Customer ID Customer Name | ID and/or name of the company that the product/services are being sold to. For a purchase of products/services, this is normally left blank because you are typically the purchaser. |
| Data Source | Indicates where the ticket came from (for example, CFHarvest if the ticket was uploaded from the CFHarvest app). |
| Destination | ID of the destination location for the Product identified on the ticket (if applicable). |
| Diameter Diameter Unit | Diameter of the product. This is only used for some measurement types. This should typically contain the actual (usable) diameter measurement rather than a diameter class (records can be grouped into classes as needed by functionality that consumes the data). If a value is specified, the unit of measure must also be specified. |
| Distance Distance Unit | Distance traveled. This could be the distance traveled while performing the work (such as forwarding distance), or distance traveled to get to the work site. If a value is specified, the unit of measure must also be specified. |
| DR | Debit account code for the work. |
| External Ticket | Identifier assigned to the ticket by another company. This is also useful if the meaningful identifier for the ticket contains non-numeric data. |
| Import Batch ID | If the ticket was imported into CFXchange using the import tool, identifies the “batch” that the record was imported in (that is, the upload operation). This allows records that were imported in the batch to be viewed by filtering on the ID. It also allows the records in the batch to be deleted. |
| Length Length Unit | Length of the product. This is only used for some measurement types. This should typically contain the actual (usable) length measurement rather than a length class (records can be grouped into classes as needed by functionality that consumes the data). If a value is specified, the unit of measure must also be specified. |
| Measurement Type Measurement Type ID | Indicates how the quantities for the ticket were determined. This is a required field. The ID values are keywords that must match the standard types defined in Admin > Setup > Measurement Types; the descriptions can be modified if necessary to use terms that are more meaningful to your company. |
| Modified By Modified Date | ID (such as e-mail address) of the last user to update the record. Date/Time when the record was last updated. |
| Notes | Comments about the ticket. |
| Parcel ID | Used to distinguish detail records for a particular ticket - for example, ticket #123, parcels A, B and C. This allows each detail record to be uniquely identified within a ticket, which is used by the import and Application Program Interface (API) code when replacing an existing ticket with a new version. Values should always be set for Parcel ID for a ticket that has multiple detail records. Values are optional for a ticket that has only a single record. Values can be alpha, numeric, or alphanumeric. |
| Party 1 ID ... Party 5 ID Party 1 Name ... Party 5 Name | Many companies can be paid or invoiced based on a work ticket beyond the Supplier and Customer (for example, a forest owner, a forwarding contractor, etc.). Therefore up to 5 additional companies can be identified on each ticket (ID and/or company name). Companies of the same type should be recorded in a given field (for example, forest owners should always be recorded in the Party 1 field). |
| Piece Count | Number of pieces. |
| Product | ID indicating the goods/materials provided/consumed (for example, timber assortments, chemicals, culverts). |
| Project ID | ID of a project that the work is associated with. This can be used to group work tickets together (for example, for budget tracking), and can be used in settlement. |
| Quality | Quality of the product. This is only used for some measurement types. This should typically contain the actual quality measurement rather than a quality class (records can be grouped into classes as needed by functionality that consumes the data). |
| Region | ID of the region where the work was performed. |
| Resource | ID of the specific resource used for the work (for example the registration number of a machine or an employee ID). |
| Resource Type | Identifies the type of resource (for example, a machine type or human resource type) used for the work. |
| Source | ID of the location where the work was performed. |
| Species | Species ID of products/materials (for example, tree species harvested, forwarded or planted). |
| Supplier ID Supplier Name | ID and/or name of the company that did the work. (for example, a silviculture contractor, a harvest contractor, a road maintenance contractor). |
| Task | ID indicating the general type of work (service) performed (for example, Silviculture or Harvesting). |
| Ticket | Number that identifies the work ticket in a way that is meaningful to you. This is a required field. Ticket numbers should be unique for a given date (that is, you should not have two different records with the same ticket number on different dates). However many work tickets for a particular date can have the same value, because this allows multiple records to be grouped together into a “logical ticket” (for example, to match an invoice received from a Silviculture Contractor which contains many line items, with each line item becoming a work ticket and the Ticket # matching the Invoice #). The Parcel ID field can be used to identify specific line items within a ticket. Ticket numbers should never be reused (for example, from one year to the next). |
| Version | Indicates how many times the work ticket has been modified. This is set when tickets are uploaded using the Application Program Interface (API) or import tool. A new work ticket starts at 1, and each time the ticket is modified the number is incremented by 1. |
| Void | Indicates if the ticket is considered void (canceled / logically deleted). |
| Volume Volume Unit | Volume of the product (goods). This is only used for some measurement types. If a value is specified, the unit of measure must also be specified. |
| Weight Weight Unit | Weight of the product (goods). This is only used for some measurement types. If a value is specified, the unit of measure must also be specified. |
| Work Date | Date the work was performed (which may include time). This is a required field. |
| Work Finished | Indicates if the work is complete for this particular activity. Value should be Yes, No or blank (Null). The app providing the data can decide what the scope of the “work” is (for example, block level, worksite level, ...). |
| Work Profile | Characteristics of the product or service that are meaningful to you. This is intended to contain keywords because it can be used in settlement. For example, a work ticket for a product could characterize the timber as PULP or LOGS. |
| Work Quantity Work Quantity Unit | Actual amount of work (goods or services) for quantities other than weights, volumes and distances. This can be a positive or negative value. If a value is specified, the unit of measure must also be specified. |
| Work Type | Categorizes the type of the work in some way that is meaningful to you. This is intended to contain keywords because it can be used in settlement. |
| Zone | Zone where the work was performed. A zone is a way for you to divide the land base into areas that are meaningful from a business perspective. Zones could be larger or smaller than regions, or even unrelated to regions. |
If you use CFBusiness to settle work tickets, refer to the online help in CFBusiness for additional information about which of these fields impact payment calculations.