Procurement BPM Approvals

Client Requirement on PO Approvals:

The Client is on Oracle EBS, and has a heavily customized PO approval workflow. Their current approval process for Purchase Orders involves maintaining buyer levels (that are different from the employee Job) and associated approval thresholds separately in custom lookups for manufacturing and services. Each buyer is linked to a buyer level or grade (maintained as an attribute), and the corresponding approval limits are fetched from these custom lookups. If a buyer lacks the necessary approval limit for a Purchase Order (PO), the approval is routed through the buyer’s supervisory hierarchy.

Additionally, for POs exceeding a certain threshold, a dual-approval mechanism is required, involving a finance delegate whose assignment is determined based on the PO amount and commodity code. The finance delegate’s details are also stored in a separate custom lookup.