Description

Many customers use a preparer/requester model where one user creates and submits purchase requisitions on behalf of another employee.

Currently, approval hierarchies are resolved from the preparer, even when a different requester is specified.

Customers need the ability to:

• Resolve approval hierarchy based on the requester
• Optionally enforce the requester as the first approver
• Continue the workflow through the requester’s managerial hierarchy

This is a very common scenario for shared services, executive assistants, and centralized procurement teams and currently requires complex workflow design or customization.

Requested Enhancement

Introduce a configurable option in Purchase Requisition workflows to:

• Resolve approval hierarchy based on:
• Requester or
• Preparer
• Optionally require the requester to be the first approver when requester ≠ preparer

Example configuration:

• “Hierarchy source: Requester / Preparer”
• “Enforce requester approval as first step: Yes / No”