Standard position movements fields

Here are the standard position movement fields available for crossboarding via web services.

  • The fields are subject to validation. 
For the full XML structure, see crossboarding position movements XML structure (file). For the desktop spreadsheet equivalent, see Standard position movement data file format under the bulk data uploads section.

Position movement fields

The element names below sit under the PositionMovement. parent.

Position movements field description Field length Req? EmpowerHR tag
PositionMovement. 
Notes
Function Code 4 y FunctionCode Acceptable codes are:
  • cond
  • auto
  • ploy
  • prom
  • salc
  • tran
Movement Code 4 n MovementCode Must be a valid code.
Employee Code 10 y EmployeeCode Must be a valid code.
Old position number 10 n* OldPosition *For an employee with:
  • single employment, if the old position number is not provided, EmpowerHR defaults to Employment
  • multiple employments, if the old position number is not provided, an error occurs
Employment 3 n* Employment *If employment is not provided, EmpowerHR defaults from old position. Employment is used to refer to the old position employment, not for generating a new employment.
New movement/change date 9 y NewMovementChangeDate  
New position number 10 n* NewPosition *If the new position number is not provided, EmpowerHR uses the old position.
End date 9 n EndDate You can enter:
  • the end date for the movement, or
  • 99999999, if the movement does not have an end date (open-ended)
Classification/Award code 8 y Classification If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

Award level 2 y* AwardLevel *If hourly paid, then enter level or leave blank.
Cost centre 16 n CostCentre If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

Admin unit 4 n AdminUnit  
Program Activity or Job 16 n ProgramActivityOrJobNumber  
Section code 4 n Section If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

Duty code 4 n Duties  
Location code 4 n Location If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

Authorising officer 4 n Authority  
Employment type 4 n EmployeeType If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

Employment condition 4 n EmploymentCondition If entered, this must be a valid code.

This field can be left blank and default from the position if set to do so in the transaction rule for the movement code used.

Probation period 12 n ProbationPeriod  
Work pattern code 6 y WorkPattern Must be a valid code
Public holiday code 4 y PublicHoliday Must be a valid code
Contract reason 4 n ContractExpiryReason If the transaction rule defol is set to:
  • n and the take-on file has blank data for the column, then EmpowerHR creates a blank Contract Reason for the new movement record, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and the take-on file has blank data for the column, then EmpowerHR populates the new movement record with the previous movement's Contract Reason data, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and you still want to make the field blank (that is, not populate it from the previous movement's data), then set the column in the take-on file to 9999.
Contract expiry date 9 n ContractExpiryDate You can enter the contract expiry date for the movement using the format: ddmmyy, ddMmmyy, ddMmmccyy, ddMmmccyy, or If the transaction rule defol is set to:
  • n and the take-on file has blank data for the column, then EmpowerHR creates a blank Contract Expiry Date (open-ended date) for the new movement record, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and the take-on file has blank data for the column, then EmpowerHR populates the new movement record with the previous movement's Contract Expiry Date data, otherwise EmpowerHR populates the field with non-blank data from the take-on file.
  • y and you still want to make the field blank (that is, an open-ended date), then set the column in the take-on file to 99999999
Contract signed 1 n ContractSigned  
User field 4 8 n UserField4  
User field 5 8 n UserField5  
User narrative 180 n Narrative  
Pay basis 1 y PayBasis Must be one of the following:
  • h (hourly) or
  • s (salary)
Hours per period 10 y HoursPerPeriod Two decimal places
Hours per week 10 y HoursPerWeek Two decimal places
FTE % 10 y FtePercentage  
Base salary 10 n BaseSalary  
Hourly rate 12 n HourlyRate  
Variation % 10 n VariationPercentage  
Variation amount 10 n VariationAmount  
Salary Maint? 1 n SalaryMaintain  
Salary barrier level 2 n SalaryBarrierLevel  
Next Increment date 9 n NextIncrementDate Format: ddmmyy, ddMmmyy, ddmmccyy or ddMmmccyy
Auto increment 1 y AutoIncrement Must be one of the following:
  • y
  • n
  • d (school functionality)
Pay by exception 1 y PayByException Must be one of the following:
  • y
  • n
  • r (school functionality)
Schedule 6 n Schedule  
Pay 1 y Pay Must be:
  • y (yes) or
  • n (no)
Pay start date 9 y PayStartDate Format: ddmmyy, ddMmmyy, ddmmccyy or ddMmmccyy
Employee remuneration narrative 100 n RemunerationNarrative  

EmpowerHR tag values below are child elements of <PositionMovement> in the XML structure. The full XML path for any field is PositionMovement.<tag> (for example, PositionMovement.EmployeeCode).


Split cost codes

Splits are nested within each position movement using a repeating <CostCode> element under <SplitCostCodes>.

Repeat the <CostCode> element for each cost code in the split.

Split cost code field description

Field length

Req?

EmpowerHR tag

PositionMovement. 

Notes

Cost code  16 y SplitCostCodes.CostCode.CostCentre  
Split percentage  2 y SplitCostCodes.CostCode.Percentage Must be numeric. Splits must total 100%.

EmpowerHR tag values below are nested elements within <PositionMovement>. The full XML path for any field is PositionMovement.<tag> (for example, PositionMovement.SplitCostCodes.CostCode.CostCentre).


If using web services, see crossboarding position movements XML structure (file) for the complete structure on which the (detailed) data table is based.




Next topic

Overtime code fields




 

© 2023 Fusion5. All rights reserved.