Self-check: jobs, positions and assignments

Five questions on which record survives an exit, the determinants behind the jobs-or-positions decision, where a grade is chosen, two assignments on one person, and the values that cannot be edited later.

5 questionsPass mark 70%Back to the lesson
  • Separate the three records and their lifetimes
  • Explain the jobs or positions decision
  • Explain where a grade is chosen
  • Interpret two assignments on one person
  • Recognise what cannot be edited later

Every incorrect option names the misconception it represents. A wrong answer tells you which model of the process you reached for, which is the part that is worth correcting.

1. A regional payroll manager resigns and an HR administrator ends the assignment, then deletes the position because it is now empty. What breaks?

Separate the three records and their lifetimes · targets: Treating an empty position as leftover data to clean up, because it is only a slot rather than a person.

2. Which two determinants does Oracle give for deciding between using jobs and positions together, or only jobs?

Explain the jobs or positions decision · targets: Treating the decision as a system preference or a default, rather than one Oracle says is decided during implementation.

3. A payroll element is scoped to grade A2. A worker in a grade that is not valid for their job or position still exists and nothing objects at save time. Why?

Explain where a grade is chosen · targets: Assuming the valid-grade list is a constraint on the assignment, so an out-of-list grade should have been rejected.

4. A person number 45678 appears with assignment numbers E45678-1 and E45678-2. What has this person got, and what should you check?

Interpret two assignments on one person · targets: Reading a second assignment number as a duplicate worker record created by mistake.

5. A worker was hired with the wrong legal employer. Which change can be made without cancelling the work relationship?

Recognise what cannot be edited later · targets: Assuming every attribute on a worker record can be corrected in place, because most of them can.