Request for Quotation
MM / P2Padvanced

MM Request for Quotation Part 2: RFQ Strategy, Sourcing Integration and Award Governance

Key takeaway

Beyond simple RFQs: when to run sourcing in SAP Ariba or other sourcing tools versus S/4HANA, integration of awards into contracts and info records, competitive bidding rules, documentation of award decisions, and governance for audit.

Explanation

📌 KEY POINTS
✅ Simple RFQs can run in S/4HANA; complex events (auctions, multi-round, many suppliers) usually run in a sourcing tool like SAP Ariba Sourcing.

✅ Awards must flow into contracts, scheduling agreements or info records so operational buying uses them.

✅ Policies define when competitive bids are mandatory (value thresholds, categories).

✅ Award decisions need documentation: criteria, scores, approvals.

⚠️ Awarded prices not transferred to S/4HANA mean buyers keep buying at old prices.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 1 covered RFQ mechanics. Now strategy and governance.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHERE TO SOURCE

  • S/4HANA RFQs for simple, few suppliers.
  • Sourcing tools for events, auctions, weighted scoring.

━━━━━━━━━━━━━━━━━━━━
▶ 2. AWARD INTEGRATION

  • Award → contract/info record/source list in S/4HANA.
  • Monitoring of transfer errors.

━━━━━━━━━━━━━━━━━━━━
▶ 3. POLICIES

  • Thresholds for number of quotes; exceptions with justification.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DOCUMENTATION

  • Criteria (price, quality, delivery, risk), scores, approvals.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE

  • Audit trail, KPIs (sourced spend %, savings, cycle time).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Define sourcing policy thresholds.
  2. Decide tool per category.
  3. Set up award integration and checks.

✅ CHECKPOINT: every award above threshold has documented competition and appears as a source in S/4HANA.

Code example

ABAP Code
===== STEP 1: policy example =====< 5,000: one quote | 5,000–50,000: 3 quotes | > 50,000: sourcing event with approval ===== STEP 2: integration =====Ariba sourcing event → award → contract in S/4HANA (or info records) → source list update ===== STEP 3: KPIs =====Sourced spend % | realized savings | cycle time | awards without competition

Real project scenario

An Ariba sourcing event selected a new supplier with a 7% lower price, but no contract or info record was created in S/4HANA. Buyers kept ordering from the old supplier for months. Automating award-to-contract transfer and a weekly check of awards without S/4HANA sources closed the gap.

Common mistakes

  • Awards not transferred.
  • No competition thresholds.
  • Undocumented decisions.
  • Using spreadsheets for scoring.
  • No savings tracking.

Best practices

  • Integrate awards with sources.
  • Enforce thresholds.
  • Document criteria and approvals.
  • Track savings realization.
  • Review exceptions.

Interview angle

Questions: "When would you use Ariba instead of S/4HANA RFQs?", "How do awards reach operational buying?", "What governance applies?"
Strong answer: tool choice, award to contract/info record/source list, thresholds, documentation, KPIs and audit.

Practice this lesson

Quick check

1. Which governance element ensures fair competition above a value threshold?

2. When is a dedicated sourcing tool typically preferred over S/4HANA RFQs?

3. When configuring RFQs for external services procurement, how does account assignment on the RFQ item affect the resulting quotation comparison and PO conversion? Choose the response that best aligns with the expected SAP approach.

Interview questions

1. Design the sourcing and award process for a company using SAP Ariba Sourcing and S/4HANA.

Answer it in your own words first, then compare.

2. When designing a global sourcing process comparing quotations across regions with differing currencies and RFQ document types, what architecture considerations ensure a valid, apples-to-apples price comparison?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics