Configuring Approval Flows and Requisition Routing in Ariba Buying
Learn how approval flows are designed and configured in SAP Ariba Buying, how requisitions route through approvers based on business rules, and how to troubleshoot routing issues in production.
Explanation
Approval flows are the control backbone of SAP Ariba Buying. Every requisition, whether created from a catalog, non-catalog form, or punchout session, must pass through an approval process before it becomes a purchase order. The purpose of approval routing is twofold: enforce spend controls (budget owner sign-off, category manager review, legal or compliance checks) and provide an audit trail for internal and external audit purposes. Getting this configuration right is critical because incorrect routing either creates bottlenecks that frustrate requesters or, worse, allows spend to bypass required controls. In Ariba Buying, approval flows are typically built using approval rules that reference attributes of the requisition such as total amount, commodity code, cost center, ship-to location, or a custom field captured on the requisition header or line item. These rules are evaluated by the approval engine at submission time and dynamically generate an approver chain. Common patterns include a serial chain (requester's manager, then next-level manager based on threshold), a parallel approval (finance and procurement approve simultaneously), and ad hoc approvers who can be added by an approver during the process. A key design decision is whether to use organizational hierarchy-based approvals (tied to the user's manager as defined in the user master or org structure) or rule-based approvals driven by procurement-specific attributes. Most mature implementations use a hybrid: a baseline organizational approval for budget accountability, combined with rule-based approvals for compliance requirements like restricted commodities, sustainability review, or high-value thresholds. Configuration is done in the approval flow rules area of Ariba's administration, where each rule specifies a condition and the approver role or group to insert into the flow. At runtime, when a requester submits a requisition, the system evaluates all applicable rules and constructs the approval flow, which is visible to the requester and approvers as a flow diagram showing pending, approved, and future steps. If an approver rejects the requisition, it returns to the requester with comments, and the requester can edit and resubmit, which typically re-triggers rule evaluation and may produce a different flow. If an approver delegates or is out of office, delegation rules (configured separately) route the approval to a designated substitute automatically. Troubleshooting routing issues is a frequent production support task. Common symptoms include requisitions stuck with no visible approver, unexpected approvers appearing, or approval steps being skipped. Root causes often trace back to: a user's manager field being blank or misconfigured in the user record, a rule condition referencing a field that is empty on that particular requisition, overlapping rules producing conflicting approver insertion order, or a recent rule change that was not tested against edge cases like zero-value lines or split accounting. Diagnosing these issues requires reviewing the requisition's approval flow log, checking the user master data for the requester and any named approvers, and, where available, using rule simulation or test submission in a non-production environment before pushing a fix live. Integration context matters too. When Ariba Buying is integrated with S/4HANA or ECC via Cloud Integration Gateway or a middleware layer, purchase requisitions may also carry account assignment or cost center validations sourced from the ERP master data. Approval rules referencing budget availability sometimes depend on real-time or batch budget checks pulled from the backend, and delays or failures in that integration can cause approval flows to stall or display stale budget data, which requires coordinating between the Ariba functional team and the integration/basis team supporting the backend connection. From a change management perspective, approval flow changes should always go through a controlled testing cycle in a test tenant before production deployment, since a misconfigured rule can either block all procurement activity or inadvertently remove a required control, creating audit exposure.
Real project scenario
During a rollout for a manufacturing client, finance flagged that requisitions above a certain value were bypassing the required capital expenditure approver. Investigation showed a newly added rule for a different business unit had an overlapping condition that matched first and inserted its own approver chain, effectively short-circuiting the capex rule. The fix involved reordering rule precedence and adding a more specific condition to the capex rule, followed by regression testing across all business units before promoting to production.
Common mistakes
• Leaving a requester's manager field blank, causing approval flows to have no valid approver • Writing overlapping approval rules without considering evaluation order, leading to unintended approver substitution • Not testing approval rule changes against edge cases such as zero-amount lines, split accounting, or non-catalog items • Assuming organizational hierarchy alone satisfies compliance requirements without adding rule-based controls for restricted spend • Failing to account for delegation and out-of-office settings when diagnosing stuck approvals
Best practices
• Design approval rules with clear, non-overlapping conditions and document rule precedence explicitly • Combine organizational approvals for accountability with rule-based approvals for compliance-sensitive spend • Always test approval flow changes in a non-production tenant using representative sample requisitions before go-live • Maintain up-to-date manager and delegation data in user master records to avoid stalled approvals • Build a lightweight runbook for support teams covering common approval routing symptoms and their likely root causes
Interview angle
Interviewers commonly probe whether a candidate can explain the difference between organizational hierarchy approvals and rule-based approvals, and how they would troubleshoot a requisition stuck in an unexpected approval state. Be ready to describe a real diagnostic sequence: checking the approval flow log, verifying user master data, and reviewing rule precedence, rather than giving only a theoretical answer.