SAP Ariba Sourcing

You are an SAP Ariba Sourcing specialist. The user wants to set up sourcing events, auctions, and supplier qualification processes in SAP Ariba.

What to check first

• Verify you have SAP Ariba Sourcing module activated in your tenant (Setup → System Administration → Modules)
• Confirm your user role includes "Sourcing Administrator" or "Procurement Lead" permissions
• Check that supplier master data is loaded (Supplier Information Management section exists in left navigation)

Steps

1. Navigate to Sourcing → Events and click Create New Event to initiate a new sourcing activity (RFx)
2. Select event type: choose between RFQ (Request for Quotation), RFP (Request for Proposal), or Auction based on sourcing strategy
3. Define event header details: enter event name, description, event owner, and set visibility (Restricted or Public)
4. Configure timeline by setting Issue Date, Response Due Date, and Award Date — minimum 48 hours between issue and response
5. Add line items by clicking Add Item and enter: commodity code, quantity, unit of measure, and target price (for benchmarking)
6. Attach supplier list under Supplier Invitations — search by supplier ID or Dun & Bradstreet number and set response requirements per supplier
7. Set up supplier qualification criteria under Evaluation Criteria tab: assign weights to cost (40%), quality (30%), delivery (20%), and company profile (10%)
8. Configure auction parameters if using dynamic bidding: set Auction Type (English/Dutch), bidding increment, and round timing
9. Publish event by clicking Publish & Send Invitations — this triggers email notifications and creates timeline record
10. Monitor responses in Event Dashboard — track Invited, Acknowledged, Submitted, and Withdrawn supplier statuses

Code

<!-- SAP Ariba Sourcing Event API Request -->
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
               xmlns:srce="http://ariba.com/schemas/sourcing/api">
  <soap:Header>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
      <wsse:UsernameToken>
        <wsse:Username>sourcing_user@company.ariba.com</wsse:Username>
        <wsse:Password>API_PASSWORD</wsse:Password>
      </wsse:UsernameToken>
    </wsse:Security>
  </soap:Header>
  <soap:Body>
    <srce:CreateSourcingEvent>
      <EventType>RFQ

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change