Employee
Employee records represent your employees. Use the employee record to store information for contact, login, payroll and human resources purposes. For more information, see Employee Information Management.
The employee record is defined in the employees XSD.
Supported Operations
The following operations can be used to modify employee records:
add | addList | attach / detach | delete | deleteList | get | getDeleted | getList | getSavedSearch | getSelectValue | search | searchMoreWithId | update | updateList | upsert | upsertList
You can also use the asynchronous equivalents of SOAP web services list operations. For information about asynchronous operations, see SOAP Web Services Asynchronous Operations. For more information about request processing, see Synchronous Versus Asynchronous Request Processing.
Field Definitions
The SOAP Schema Browser includes definitions for all body fields, sublist fields, search filters, and search joins available to this record. For details, see the SOAP Schema Browser’s employee reference page.
For information about using the SOAP Schema Browser, see SOAP Schema Browser.
Usage Notes
Entering Expense Reports in SOAP web services
SOAP web services support for expense reports is different from user interface behavior. In the user interface, expense reports can only be entered for active employees. If an employee's release date is before the current date, expense reports are not supported. In SOAP web services, expense reports can be entered for employees that have a release date before the current date.
Specifying Employee Jobs and Positions
When you work with employee jobs and positions, you must submit a value for the workAssignment field to distinguish between a job and a position. By default, the workAssignment field is set to job. If you submit values for the hcmPosition sublist, you must override the value of the workAssignment field, otherwise the sublist values will not be used.
EmployeeAddressbookList
When you work with the addressbookList in the 2009.2 endpoint and beyond, be sure to use internalId as the key. Do not use label. For the 2009.1 and lower endpoints, the addressbookList is not a keyed sublist, but you can use label to identify records.