3508956 - API user created the Job Requisition can access it without having any roles assigned - Recruiting Management

API user who created the Job Requisition can access it despite not being assigned to any operator role.

SAP SuccessFactors Recruiting Management

1. Create a job requisition using an API user via OData API.
2. Set the originator to another user in the payload. Do not assign any role to the API user in the route map.
3. The API user can still access the job requisition. In reporting, the API user appears as "approver".

The API user is the job requisition creator. If the system cannot find another operator role associated with the creator, the creator is automatically assigned the [V] role.

It is recommended not to pass the Originator in the API payload. Doing so will conflict with the user creating the requisition.

Even if the Job Requisition creator is not assigned to Originator role (O) and is not a part of the route map, the creator will still be able to see the requisition, but will not be able to approve/update it.

2221569 - Recruiting Operators and Designator values - Recruiting Management

postman, odata api, job requisition form, access, originator, v role, approver, route map, originator , KBA , LOD-SF-RCM-API , Webservices & APIs , Problem