Case Studies

Custom Job-Requisition Export vs. Workday Workforce Planning Actions

Custom Job-Requisition Export vs. Workday Workforce Planning Actions

Platform: Workday HCM and Workday Adaptive Planning

Scope: review of how approved positions in the plan become job requisitions in Workday

The business problem

Approved hires in the workforce plan had to become job requisitions in Workday HCM. The organisation asked whether the standard publishing feature could replace the process they ran, and what it would take.

Existing architecture

The organisation used a staged approval process inside the planning model, followed by an export integration. Workday created the requisition, and the status returned to the plan. This is a custom design. It is not the standard publish feature, and we took care not to call it that.

Why it happened

The two approaches were being described with the same words. Without a clear line between them, nobody could judge whether a change was worth making.

Design decision

We documented the standard option from current Workday documentation only, and kept it apart from the description of the organisation’s process. We did not recommend a switch before the tenant was checked against the documented prerequisites.

Implementation approach

The standard option, as Workday documents it:

  1. The planner works in a level-assigned modeled sheet and filters to the rows to publish. At least one filter is required.
  2. The planner selects Publish and chooses the Create Job Requisition workforce planning action.
  3. Workday Adaptive Planning sends the action to Workday HCM.
  4. Publish history shows the status and what was sent.
  5. A data loader can then update the sheet with the created requisition details.

The documentation also lists limits that matter for this decision. Workforce Planning Actions cover the initiating action only and do not support sub-processes. Create Job Requisition supports the expedite path and supervisory organisations on the position management staffing model. Top-level members of a hierarchy cannot be published.

Controls and validation

We listed what to check in the tenant before proposing a change: the publishing permission, the field mappings on the sheet including worker type, the external system and loader setup, the business process and security setup in Workday HCM, and whether the organisation’s staffing model meets the documented requirements.

Outcome

The organisation has a clear comparison of the two approaches and a validation list. No change was made to the running process.

Lessons learned

Sources

Scope of the outcome

Documented comparison and prerequisites; the running requisition integration was not changed.


EPMLogic | Implementation insight based on an anonymized scenario. Exact operational amounts and client details are intentionally omitted.

Workday Adaptive Planning
Related Insights

More from the architecture desk.

Assessing a Multi-Year Headcount Model Before Rebuilding It
Case Studies

Assessing a Multi-Year Headcount Model Before Rebuilding It

Platform: Workday HCM, a worksheet model inside Workday, and Workday Adaptive Planning Scope: assessment of a...

Read more
Tracing an Inherited Workday Adaptive Planning Forecast Model One Path at a Time
Case Studies

Tracing an Inherited Workday Adaptive Planning Forecast Model One Path at a Time

Platform: Workday and Workday Adaptive Planning Scope: review of an existing forecast model built by an...

Read more
Diagnosing Workday Adaptive Planning Access Issues Layer by Layer
Case Studies

Diagnosing Workday Adaptive Planning Access Issues Layer by Layer

Platform: Workday and Workday Adaptive Planning with single sign-on Scope: user access requests for department budgeting...

Read more