Positions are getting inactivated when employee is in suspended status.

When a position has an incumbent with an Active assignment, the system prevents the position from being inactivated, which aligns with the expected validation. However, in the reported scenario, the incumbent's assignment associated with the position is in Suspended status. Although the employee record remains visible in the system because the person has another active assignment, the assignment linked to the position being inactivated is suspended. As a result, Oracle considers the position eligible for inactivation and allows the transaction to be processed through HSDL.

We would like to explore whether there is any possibility to enhance the validation logic so that transactions involving positions with suspended incumbents are not allowed to be processed through HSDL.