EmployeeEarnings
Create, update, delete, and query Reckon Employee Earnings.
Table Specific Information
The Ids for the EmployeeEarnings table operate a bit differently than Line Items. Unlike Line Items, Reckon does not return a unique Id for EmployeeEarnings. Instead, each EmployeeEarnings entry is returned in a specific order, and Employee Earnings entries can be updated in that order back to Reckon. To give the Employee Earnings unique Ids, we have appended the index number of each EmployeeEarnings entry to the Id. It will be up to the programmer to ensure that any modifications to Employee entries through the Reckon UI (or another application between a SELECT and an UPDATE call) are handled.
Select
By default, SupportEnhancedSQL is set to true, and the following will be honored if present. Other filters will be executed client side. If SupportEnhancedSQL is set to false, only the following filters will be honored.
Reckon allows only a small subset of columns to be used in the WHERE clause of a SELECT query. These columns can typically be used with only the equals or = comparison. The available columns for Employees are Id, Name, and IsActive. TimeModified may be used with the >, >=, <, <=, or = conditions and may be used twice to specify a range. Name may be used with the = or LIKE conditions to establish a starts-with, ends-with, or contains syntax. For example:
SELECT * FROM EmployeeEarnings WHERE Name LIKE '%George%' AND TimeModified > '1/1/2011' AND TimeModified < '2/1/2011'
Insert
To add an EmployeeEarnings entry, specify the EmployeeId field in the INSERT statement. If you instead specify the Employee Name, the driver will attempt to add a new Employee. For example:
INSERT INTO EmployeeEarnings (Name, EarningsWageName, EarningsRate) VALUES ('370000-933272659', 'Regular Pay', 21.32)
Columns
Name | Type | ReadOnly | References | Description |
ID [KEY] | String | True |
The unique identifier in the format EmployeeId|EmployeeEarningsId. | |
Name | String | True |
The name of the employee. | |
PayPeriod | String | False |
Indicates how often employees are paid The allowed values are Daily, Weekly, Biweekly, Semimonthly, Monthly, Quarterly, Yearly. | |
EmployeeId | String | False |
Employees.ID |
The Id of the employee. This is required to have a value when inserting. |
EarningsId | String | True |
The Id of the employee earnings entry. | |
EarningsWageName | String | False |
The wage name. This is required to have a value when inserting. | |
EarningsWageId | String | False |
A reference Id to the wage. Used for payroll. | |
EarningsRate | Double | False |
Employee earnings rate. Used for payroll. | |
EarningsRatePercent | String | False |
Employee earnings ratepercent. Used for payroll. | |
TimeModified | Datetime | True |
When the item was last modified. | |
TimeCreated | Datetime | True |
When the item was created. |
Pseudo-Columns
Pseudo Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
ActiveStatus | String |
This pseudo column is deprecated and should no longer be used. Limits the search to active or inactive records only or all records. The allowed values are ACTIVE, INACTIVE, ALL, NA. The default value is ALL. |
StartTxnDate | String |
This pseudo column is deprecated and should no longer be used. Earliest transaction date to search for. |
EndTxnDate | String |
This pseudo column is deprecated and should no longer be used. Latest transaction date to search for. |
StartModifiedDate | String |
This pseudo column is deprecated and should no longer be used. Earliest modified date to search for. |
EndModifiedDate | String |
This pseudo column is deprecated and should no longer be used. Latest modified date to search for. |