Discrete Unit Data
Discrete unit functionality (previously known as 'batch tracking') in Production Accounting is used for material that is handled as a distinct, identifiable entity in terms of processing, packing, movement, storage, sales or consumption. This includes bulk material processed in 'batches' rather than by continuous feed; material formed as individual units (like ingots or bars); and groupings of such material (for example, as packages, containers or shipments). Each discrete unit is tracked as a distinct object and assigned a unique Discrete Unit ID. Relevant data, such as mass and assay values, is recorded for each discrete unit.
Discrete unit functionality is for 'transactional' production data, that is, where data about the processing and movement of material is recorded against a specific date and time. In Production Accounting, logsheets record data for a period of time; for example, an entire shift, which might have a duration of 7:00 am - 7:00 pm. However, discrete unit data can be logged against a specific time; for example, 11:22 am.
Discrete unit data is propagated through the system as units are moved between locations. Discrete units can be grouped into new discrete units at a location. When units are grouped, data is aggregated to calculate totals and weighted averages for the group. For example, gold bars are produced as individual units and stored securely in a safe on site. When transported from the safe to the mint, multiple bars are grouped into a 'deposit'. Transactions are entered on the required discrete unit screens for the initial creation of each bar and the subsequent movement of the grouped bars from the safe to the mint. In this scenario, the data for each bar is aggregated for the deposit.
Discrete unit data overview
Transactions
A 'transaction' is a specific kind of data entry in Production Accounting used for discrete units. Transactions are recorded in customised grids on discrete unit data entry screens. Each transaction is recorded against a specific date and time and assigned a unique identifier.
Transactions can represent both the creation and movement of discrete units (DUs). When a new discrete unit (DU) is created; for example, a gold bar is poured or a new container is loaded with concentrate; a transaction is entered to represent its creation or formation. When DUs are moved between locations; for example, gold bars are moved from a production area to a secure storage location or containers loaded with concentrate are transported to a buyer; transactions are entered to represent their movement. Transactions can also be used to represent an adjustment made to a deposit or shipment; therefore, a transaction may not always represent a physical movement.
Transaction data entry grids
Discrete unit data entry is done through a customised grid called a 'staging set'. Each data entry item, or 'transaction', is recorded as a row in the grid. For each transaction, you specify the date and time.
Multiple transaction grids may be grouped together on the same screen. Grids can be grouped based on logical commonalities between the data. For example, one discrete unit screen may contain all transaction grids for a particular material (such as middlings) or all grids for transactions to and from a specific location in the plant (such as a smelt furnace, safe or warehouse).
Location Manager
The Location Manager displays a list of discrete unit inventory that is currently at that location (for example, a processing area in the plant or a storage location like a warehouse or safe). The Location Manager may be configured as a separate screen or may display as an additional section on discrete unit screens; for example, under the transaction data entry grid. Multiple locations may display on a single screen.
The Location Manager includes functionality for grouping discrete units so that they can be moved together via a transaction to another location.
Using the discrete unit interface
Below are tips and general guidelines for the discrete unit user interface.
Note: Production Accounting is a web application that requires users to enter data in a 'stateless' manner. There is no auto-save functionality during data entry. Before you enter or update discrete unit data, make sure your screen is refreshed to display the most up to date data. When you enter or update discrete unit data, frequent manual saving is recommended.
Select transaction data entry grids
Some discrete unit screens have multiple transaction grids grouped together. To display a different grid, select the required grid from the Transaction Data Entry drop-down list and click Load Grid.
Working with transaction rows
Only one row in a transaction grid can be edited at a time. If multiple rows are visible when you add or edit a row, starting an interaction with another row changes the focus to that other row and also cancels your current row edits.
Data entry cells may be numeric-only, alphanumeric, or include a drop-down list from which you select an option. Some cells have no data entry field and display calculated values once the row is saved. You can press Tab to move to the next field in the row. The Enter key cannot be used to move between rows or save data.
For each row, a transaction date and time is required. When you add a new row, the date field auto-populates with the current date and time. The date and time can be edited as required but must be entered in the correct format.
You must also enter or select a Discrete Unit ID for each transaction row. Depending on the grid configuration, this identifier may be for objects such as bulk material batches, formed units (like bars or ingots), packages, containers, or shipments. Discrete Unit IDs are numeric and/or alphanumeric and can be configured with a character limit.
If the transaction represents the movement of a discrete unit from a location with discrete units which match this transaction's DU template, the Discrete Unit ID field has a drop-down list from which the ID for an existing discrete unit can be selected.
Note: Discrete Unit IDs must be unique across the entire system. Production Accounting does not allow the creation of duplicate Discrete Unit IDs. Datamine recommends that you define and follow a consistent naming format for Discrete Unit IDs to avoid duplication.
Transaction dates and times
For discrete unit data entry, the transaction date and time is entered as a 'string', rather than with date selector drop-downs or a calendar pop-up. Dates and times must be entered in the correct format configured for your system. Date/time cells include validation to ensure the format is correct.
When you add a new transaction row, the current date and time is auto-populated by default. If you edit the date/time string, typing over or deleting the existing characters can conflict with the validation rules. The system may attempt to delete or overwrite your updates. The cell may revert to the default or previous value, display the example date/time format, or insert characters in the wrong place in the string.
For accurate date/time entry, use one of the following methods:
- Select the section of the string you want to edit first, before typing. Click and drag with your mouse to highlight the characters (for example, the HH). Then, enter the updated value.
- Place your mouse cursor in the section of the string you want to edit (for example, place your cursor on either side of or in the middle of the HH). Press the Up and Down arrow keys to increment the value.
Numeric data entry
For data entry in numeric cells in a transaction grid:
- You cannot enter text or symbols. Validation rules prevent any non-numeric characters being entered. This includes qualifiers that may appear before assay values (such as < or >) and unit abbreviations or symbols (such as ppm or %).
- For decimal values less than zero, you must include the leading zero before the decimal separator (for example, 0.5 or 0,5).
- Negative values that begin with a minus symbol are accepted (for example, -2.54).
Other non-numeric cells in a transaction grid, such as Discrete Unit ID fields and comment fields, can accept text and symbols.
Audit comments
Any audit comments you enter while updating a row are attached to the saved data in that row. Audit comments are attached to the table's key, which is usually the Discrete Unit ID (in the example below, the Discrete Unit ID is the Container Number).
If the key is changed, you’ll no longer see older comment history for that row, unless the key is changed back to its prior value.
Refresh grids
After you edit and save a row, the row is greyed out until it has been processed by the Production Accounting server. Click Load Grid to refresh the view, if required. A status label displays when loading if server processing is still in progress.
Note: An edited row is always greyed out initially, until the view is refreshed. If a row remains greyed out for an extended period, contact Datamine Support.
Date filters
Take note of the Start Date and End Date filters at the top of the transaction grid. If you save a transaction with a date that is outside of the date filters, the row disappears from view after saving. To make the row visible again, change the date filters to include the row's date.
The Production Accounting user interface can be configured to display a warning message when the date entered is outside of an expected range. Warnings help avoid user error in which incorrect dates (especially the wrong year) are entered and are subsequently difficult to find and correct.
Warnings on save
If a warning displays when you save a transaction row, but you wish to continue, click the Update button again. If you proceed without changing the data, or if you make changes that would trigger the same warning, the row will save.
If there is an issue with the data entered, errors display in red text. Saving is prevented until the errors are resolved.
