How to configure requisition approvals based on project/PPM standard fields exposed in requisitions
Summary:
We need to route Purchase Requisition approvals based on a standard project attribute (Project Work Type, set to Budgeted or Unbudgeted on the project header in PPM). Rules built on the seeded "Project Work Type" attribute never fire, and submission fails with "We can't assign approvers to this requisition right now." Backend analysis shows the work type is not carried from the project header onto the requisition distribution. We're looking for the supported way to drive requisition approvals from project/PPM standard fields.
Content (please ensure you mask any confidential information):
Requirement:
Requisitions charged to a project should route to different approvers depending on the project's Work Type:
0