Oracle Sourcing Testing

It covers the negotiation lifecycle in Oracle Fusion Sourcing — creating RFIs, RFQs, RFPs and reverse auctions, inviting suppliers, collecting responses, scoring and evaluation, the award decision, and the hand-off to a purchase agreement or purchase order. It does not cover supplier onboarding or the agreements and orders themselves, which have their own pages.

Sourcing testing focuses on competitive negotiations and awards. Supplier onboarding, registration approval, and qualification assessments are a separate concern covered on the Supplier Qualification Testing page. A supplier must exist and be able to register for an event, but qualifying that supplier is out of scope here.

All four: RFI for information gathering, RFQ for priced quotes, RFP for evaluated proposals, and reverse auction for competitive bidding. Each has different disclosure, scoring, and award behaviour, so a suite that tests only one document type leaves the others unverified.

Enter known responses, then assert the computed weighted score against the value you expect from the configured criteria and weights. Test both automatic scoring and manual evaluator scoring, and check weight boundaries so a change in a single weight produces the ranking you intend rather than a silent tie or reversal.

Cost factors — freight, duty, tooling and similar — turn a quoted unit price into a landed cost that the evaluation actually compares. If a factor is omitted or mis-applied, the ranking is based on the wrong number. Tests should verify cost-factor and price-break arithmetic per line, not just the raw bid price.

With negative visibility tests: submit responses and assert they are not visible to the buyer before the unseal event, and for two-stage RFPs, that the commercial stage stays locked until the technical stage completes. Premature disclosure is a fairness and audit risk, so these cases are high priority even though they need role and timing setup.

Full award to one supplier, award by line to different suppliers, partial award of a line quantity, and split award across suppliers. Each should be tested through to the generated document, because an award that scores correctly but fails to create the agreement or PO leaves purchasing with nothing to act on.

An award can create a blanket or contract purchase agreement for ongoing supply, or a purchase order for a specific buy. Both paths must be tested and confirmed to generate the correct document with the awarded lines, prices and supplier. The agreements themselves are covered in depth on the Purchase Agreement Testing page.

Amend an open negotiation or open a new round and confirm that prior supplier responses are preserved or re-solicited as configured, suppliers are notified, and the close date behaves correctly. A defect here can silently drop competition data, so amendment cases belong in every cycle that touches negotiation setup.

Yes. When suppliers bid in different currencies, evaluation must convert to a common basis before ranking. Tests should confirm the conversion rate is applied and the ranking reflects converted values — a missing rate or an unconverted comparison ranks the wrong supplier first.

Create awards above and below the configured approval threshold and assert that the above-threshold award routes for approval before it can be released, while the below-threshold award proceeds per rule. This protects segregation of duties and becomes critical after any approval-rule or security-role change.

Yes. Negotiations can be created and responses imported through REST and file-based import as well as the UI. A complete suite runs both and confirms an integration-created negotiation and imported responses behave the same as the UI, because bulk and integrated events rely on that path and any divergence is a control gap.

On every Oracle quarterly update, and after any change to negotiation styles, cost factors, scoring criteria, award approvals, tax or currency setup, or security roles. Because a negotiation produces an auditable award, testing after these events protects against silent drift that would otherwise surface only when the wrong supplier wins.

Each test needs suppliers able to register, a negotiation with the right lines, cost factors and scoring criteria, and responses engineered to produce a known score and award. SyntraFlow's Oracle Data Vault provisions suppliers and negotiations so tests produce the intended outcome reliably instead of relying on hand-built events.