Configuring Sourcing Projects, Templates, and RFx Events
A practical look at how sourcing projects, reusable templates, and RFx event settings are structured and configured in SAP Ariba Sourcing to support repeatable, compliant sourcing processes.
Explanation
Once a consultant understands the business purpose of Strategic Sourcing, the next step is understanding how projects, templates, and RFx events are actually structured and configured within SAP Ariba Sourcing. This is where design decisions have long-term consequences: a poorly designed template gets copied hundreds of times across an organization, so getting the structure right early matters more than in many other configuration areas. A sourcing project is the top-level container in SAP Ariba Sourcing. It typically holds project team members, task lists, related documents, and one or more RFx events or auctions. Projects are almost always created from a project template rather than from scratch, because templates encode organizational standards: required approval tasks, standard terms and conditions documents, default team roles (project owner, approver, observer), and default phase/task sequencing. When designing templates, a consultant works with category management and procurement leadership to decide what should be mandatory versus optional, and how much flexibility category managers retain to deviate from the standard flow. Within a project, an RFx event is configured with several key building blocks. Line items define what is being sourced, whether goods, services, or a lump-sum scope, and can carry quantity, unit of measure, and specification details. Questions capture qualitative and quantitative supplier responses, ranging from simple text answers to complex pricing grids with multiple pricing terms (unit price, volume discounts, freight, payment terms). Terms sections capture commercial and legal conditions suppliers must acknowledge. Content can be pulled from a library of reusable question sets and terms, which is one of the biggest efficiency gains templates provide, since category managers are not rebuilding standard supplier questionnaires for every event. Event timing settings control the bidding lifecycle: preview period (when invited suppliers can see the event before it opens), open period, and close time, plus optional bid extension rules to prevent last-second sniping. Auction-specific settings, when used, define ranking visibility (whether a supplier sees their rank or only their own bid), bid decrement rules, and overtime/extension logic to keep price competition active until bidding genuinely settles. Supplier invitation is another configuration decision point. Buyers can invite suppliers from the internal Ariba supplier database, and in many configurations suppliers registered on the SAP Business Network are what gets invited and responds, since the network account is what suppliers use to log in and submit bids. Consultants need to confirm whether supplier records are being maintained natively in Ariba, synchronized from an ERP system, or a hybrid, because this affects how invitation lists are built and kept current. Scoring and evaluation configuration determines how responses are compared after the event closes. Weighted scorecards let organizations combine price and non-price factors (quality, delivery, sustainability criteria) into a composite score rather than awarding purely on lowest price. Award scenario tools, where available, allow buyers to model splitting volume across multiple suppliers and compare total cost outcomes before committing to a final award. A critical intermediate-level concept is separating configuration that lives at the template level (reusable, governed, changed infrequently) from configuration that lives at the individual event level (project-specific, changed by category managers routinely). Consultants should push standard content, mandatory approval steps, and compliance-critical terms into templates, while leaving line items, specific pricing structures, and supplier lists as event-level decisions. Getting this balance wrong either creates rigid templates that frustrate category managers or overly loose templates that fail to enforce compliance and consistency across the organization.
Real project scenario
A global retail company's procurement center of excellence asks a consultant to build three standard RFP templates: one for indirect goods, one for professional services, and one for logistics/freight. During requirements gathering, the consultant discovers each regional category team has slightly different approval requirements and preferred pricing grid formats. Rather than building one rigid template, the consultant designs a shared core template with a standardized terms library and mandatory approval task, then allows region-specific question sets to be added at the event level from a shared content library, balancing global governance with regional flexibility.
Common mistakes
• Hardcoding too much event-specific detail (exact line items, one-off pricing terms) directly into a shared project template, forcing frequent template edits. • Failing to confirm whether supplier invitation lists rely on Business Network registration status, causing invited suppliers who cannot log in or respond during the event window. • Ignoring bid extension/anti-sniping settings for auctions, resulting in suppliers gaming the close time. • Designing weighted scorecards without agreeing on scoring criteria and weights with stakeholders beforehand, causing disputes after the event closes. • Not separating mandatory compliance content (terms, approvals) from optional content, leading to inconsistent application across category teams.
Best practices
• Push mandatory compliance content (approvals, standard terms) into templates; leave line items and specific pricing structures at the event level. • Build and maintain a shared library of reusable questions and terms to reduce duplication across templates. • Confirm supplier Business Network registration status before finalizing invitation lists for a live event. • Configure bid extension rules for auctions to prevent last-second sniping and preserve genuine price competition. • Agree on scorecard weighting criteria with stakeholders before the event opens, not after responses are received.
Interview angle
Interview questions at this level often probe whether a candidate has actually configured templates and RFx events versus only used them as an end user. Expect questions like how you would design a reusable RFP template versus event-specific content, how supplier invitation and Business Network registration interact, and how weighted scoring or award scenario tools support multi-supplier award decisions. Strong answers reference the trade-off between template rigidity and category-manager flexibility, since that trade-off comes up in almost every real sourcing rollout.