Co-op Transactions
Purpose
The CoopTransactions data-table holds data for people, farmers, and staff KKFU work with. It is a child data-table which links to other data-tables: Farmers and Societies. Each Person record includes a "SocietiesID" to link the record to the main data-entities of KKSys.
The CoopTransaction data-table includes data-fields for recording money received from and paid to farmers, such as payments of dues or entrance fees, or reciepts of dividends. The table includes a field for "TransactionsTypeID", which is set to the type of transaction such as "Bonus Payment" or "Entrace fee payment", and includes currency fields for the value Received from Farmer or Paid to Farmer.
A full listing of all the fields in the data-table with their purposes and any automation built into the App is laid out below. To fully understand the purpose of the data-fields please consult this.
How and where to access CoopTransactions data
The image below shows the "CoopTransactions" Edit Form. This is accessed via its own entry in the System Entities, visible in the same group as the People / Farmers entity.
Co-op Transactions edit form
Note that the layout of this edit form may have changed if it has been updated by your administrator, and additional actions, reports or resources may have been added.
How access to Co-opTransactions works in practice in KKSys
Because large numbers of Co-opTransations records must be added, together with other data relating to things like the Fields a Farmer owns, cocoa delivered to KKFU etc., automated systems have been built to enable staff to enter data into multiple entities simulataneously using Rapid-data-entry-grids.
To understand thes more fully please consult the following links:
Farmer Deliveries Rapid Entry Grid
Dynamic Pascal-Scripting in Orixa: Adding a Resource to create Rapid-Entry-Grids in your App
The existance of these Rapid data-entry grids does not remove any of the usual functionality of edit-forms within KKSys. All records that hae been inserted automatically using a rapid-entry process can also be reviewed and updated in their edit-forms, and added to any reporting that management require.
Data-schema: full details of the data-fields and their purpose in the FarmFields data-table
Field- Name / Data-type |
Description / Purpose |
Possible Values |
Coding / Automation |
|---|---|---|---|
| ID (Primary Key) | Unique number which identifies each record. | Automatically set by Orixa, not under the control of users or developers. | |
| DateDone (Date) | Self explanitory | Entered by user | |
| SocietiesID (Link-ID) | Links to the Societies table | Selected from list by User | Will default to the currently open Societies ID |
| FarmersID (Link-ID) | Links to the Farmers table | Selected from list by User | Will default to the currently open Farmers ID |
| StatusID (Link-ID) | Links to the Status table | Pick from list of possible Status values. | |
| TransactionsTypeID (Link-ID) | Links to the Types table | Pick from list of possible Types values. | |
| ReceivedFromFarmer (Currency Value) | Details the value in Cedis of any money received from the farmer in this transaction. | Any number value | Default value: 0 |
| PaidToFarmer (Currency Value) | Details the value in Cedis of any money paid to the farmer in this transaction. | Any number value | Default value: 0 |
| Memo (Text) | Self explanitory, used to add any extra note or text about the transactions. | Entered by user | |
| DateCreated (Timestamp) | Set to the exact date and time the record was first created. | Automatically set by Orixa, not under the control of users or developers. | |
| Complete (true/false) | Tick this field to lock the record so further editing is restricted. | True / false | Default value: false |