R12.2.9 Oracle Purchasing Fundamentals — Lesson 2: Requisitions, RFQs, Quotations, and Sourcing

Technical Scope

• manual and imported requisitions, distributions, funds context, and status
• auto-create, document builder, buyer assignment, and source-document references
• RFQs, supplier quotations, price breaks, negotiation comparison, and award
• approval routing, communication, change history, and sourcing evidence

Instructor Demonstration

The instructor will configure and verify manual and imported requisitions, distributions, funds context, and status in the context of a procurement team standardizing requisitions, sourcing, purchase orders, approvals, receiving, and audit evidence. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering auto-create, document builder, buyer assignment, and source-document references and RFQs, supplier quotations, price breaks, negotiation comparison, and award, then introduce a realistic exception involving approval routing, communication, change history, and sourcing evidence. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for Requisitions, RFQs, Quotations, and Sourcing requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across manual and imported requisitions, distributions, funds context, and status, auto-create, document builder, buyer assignment, and source-document references, RFQs, supplier quotations, price breaks, negotiation comparison, and award; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for Requisitions, RFQs, Quotations, and Sourcing with a reusable implementation record or runbook.