


Author
Tech Leads IT
Interview questions rarely stop at "What is a purchase order?" The hard one comes next. "So why didn't this requisition turn into a PO automatically?" That's where most candidates go quiet.
This guide from TechLeads IT gives you 40 questions with answers you can say out loud in under a minute. They cover business units, requisitions, purchase orders, sourcing, the Supplier Portal, and approvals. Every answer reflects Oracle Fusion Cloud Procurement Release 26D.
This guide directly answers three questions. "What are the most common Oracle Fusion Procurement interview questions?" "What is the difference between a blanket and a contract purchase agreement?" "What can suppliers do in Oracle Supplier Portal?"
Oracle Fusion Procurement setup questions focus on business units and who can do what. Interviewers check whether you know the requisitioning and procurement business functions, the service provider model, and procurement agent access. For example, a company with three country units and one shared buying team needs three requisitioning BUs served by one procurement BU.
Why do interviewers start here? Because almost every Procurement bug traces back to setup. Say a buyer can't see a requisition, or a supplier site won't appear on a PO. The cause is usually a business unit or agent setting, not a broken screen.
Think of business units like offices in one company. The requisitioning BU is the office where someone asks for something. The procurement BU is the buying desk that places the order. They can sit in the same building or in different cities, and the service provider model is the hallway that connects them.
Oracle Fusion Cloud Procurement is Oracle's cloud suite for the source-to-pay process. The core products are Purchasing, Self Service Procurement, Sourcing, Supplier Portal, Supplier Qualification Management, and Procurement Contracts. Most interview rounds focus on the first four. Know where each one starts and stops, because the questions move across them quickly.
A requisitioning BU is where people create requisitions, and it supplies defaults such as the deliver-to organization. A procurement BU is where buyers create purchase orders, agreements, and negotiations, and where supplier sites are managed. One business unit can hold both functions, or they can be split across units. Interviewers expect you to know both setups.
The service provider model lets one procurement BU buy on behalf of other business units. Oracle's Configure Basic Enterprise Structure for Procurement process sets this up quickly. It creates a central procurement BU as the service provider and gives every other BU the requisitioning function. It's the usual design for companies with a shared buying team.
It sets defaults for requisitions and purchase orders raised from that business unit. Key settings include the default deliver-to organization, line type, default procurement BU, ship-to location, price change tolerance, and whether one order can cover multiple legal entities. If a requisition line doesn't name a procurement BU, the default procurement BU processes it.
A procurement agent is a user set up in a procurement BU with specific actions, such as managing purchase orders, agreements, negotiations, or catalog content. The setup also controls whether the agent can view or change documents owned by other buyers. If a buyer can't see requisitions in Process Requisitions, check the procurement agent setup first.
Document styles control how a purchase order or agreement looks and which features it uses, so you can offer a simpler style for routine buying. Line types decide whether a line is quantity-based goods or amount-based fixed-price services. Line types also set defaults such as matching rules. Both are interview favorites because they change what users see.
A supplier has addresses, and each address can become a supplier site in a procurement BU. Site assignments then decide which client business units can use that site for buying and invoicing. If a supplier site doesn't show on a purchase order, a missing site assignment for that business unit is the most common cause.
Oracle ships quarterly updates, and Redwood pages keep replacing classic screens. Release 26C added an AI agent that researches suppliers from a plain-language description. It matches product and service categories and filters by relationships such as Spend Authorized or Prospective. Read the 26D What's New before your interview, because interviewers like asking about recent features.
Requisition and purchase order questions test the full request-to-order flow. Interviewers ask how a requisition gets approved, how it becomes a purchase order, and which order type fits which situation. For example, office supplies from one supplier at fixed prices belong on a blanket purchase agreement. Approved requisitions then become purchase orders with no buyer touch.
What separates a strong answer from a weak one? Strong candidates explain why something happened, not just where to click. "The requisition went to Process Requisitions because the agreement wasn't set to generate orders automatically" sounds like someone who has done the job.
Think of the flow like ordering food at an office canteen. The requisition is your order slip. The agreement is the fixed menu with agreed prices. The purchase order is the ticket the kitchen actually cooks from. If your dish isn't on the menu, someone at the counter has to handle it by hand.
A requester creates a requisition in Self Service Procurement, and it routes for approval. Once approved, the line either becomes a purchase order automatically through an agreement, or it lands in Process Requisitions for a buyer. The buyer builds the order, which goes through its own approval and is sent to the supplier. Receiving, invoicing, and payment follow.
Self Service Procurement supports five content types. Local catalogs live inside Oracle. Punchout catalogs are hosted by suppliers. Informational catalogs are for reference, smart forms cover non-catalog requests, and public shopping lists handle repeat buys. Content zones control which of these each group of users can see. A good answer names the content type and the business reason for it.
A smart form is a request template for goods or fixed-price services that aren't in a catalog. It can carry default values, instructions, information templates, and attachments. If you link a smart form to a contract purchase agreement, approved requisition lines from it become purchase orders automatically. Smart forms are created in a procurement BU and secured through content zones.
A requester clicks a punchout link, the supplier authenticates the user, and the user shops on the supplier's site. The cart then returns to the requisition. Oracle supports Oracle native XML (Model 1a) and cXML (Model 1b). If the cart returns a blanket agreement number, the item and price default from that agreement.
There are three. A standard purchase order is a one-time order with items, quantities, prices, and delivery schedules. A blanket purchase agreement sets agreed prices for specific items over a period, and standard orders are released against it. A contract purchase agreement holds terms and conditions only, with no item lines.
| Document | What It Holds | Typical Use | Has Item Lines? |
| Standard Purchase Order | Items, quantities, prices, delivery schedules | One-time purchases | Yes |
| Blanket Purchase Agreement | Agreed prices for specific items over a period | Repeat buys of known items, such as office supplies | Yes, no delivery schedule |
| Contract Purchase Agreement | Terms and conditions only | Framework agreements, smart form and punchout spend | No |
The requisition line must be sourced to an agreement, either by the requester picking an agreement item or through automatic document sourcing. The agreement must have "Automatically generate orders" turned on, and usually "Automatically submit for approval" too. If either setting is off, the approved line waits in Process Requisitions for a buyer.
Process Requisitions is the buyer's workbench for approved requisition lines that didn't become orders automatically. The buyer can add lines to the Document Builder, which groups them into a new purchase order, adds them to an existing one, or starts a negotiation. Buyers can also return lines to the requester or reassign them.
When a buyer changes an approved purchase order, Oracle creates a change order and a new document revision. Approval rules decide whether the change needs approval again, for example, when the amount goes up. Suppliers can also request changes through the Supplier Portal, and those requests go to the buyer for review.
Two-way matching checks the invoice against the purchase order. Three-way matching adds the receipt. Four-way matching adds inspection or acceptance. The match level sits on the purchase order schedule and usually defaults from the line type, item, or supplier. Three-way matching is the common choice for physical goods.
Requisitions and purchase orders check and reserve funds against the budget. A document that fails the funds check can't move ahead until someone fixes the budget or approves an override. Oracle provides funds override approval rules for requisitions and purchase orders, so you can route those exceptions to the right finance approver.
Oracle Fusion Sourcing questions test whether you can pick the right negotiation type and carry it through to an award. Oracle supports three negotiation types: RFI, RFQ, and auction. For example, a manufacturer qualifying new packaging vendors runs an RFI first, then invites the shortlisted suppliers to an RFQ and awards the winner a blanket agreement.
Do you need to have run a live auction to answer these well? No. You do need to know which features belong to which negotiation type. Interviewers often ask, "Can you use proxy bidding in an RFQ?" The answer is no, and knowing why shows real understanding.
Think of sourcing like hiring for a role. The RFI is the screening call. The RFQ is the detailed interview round, which might take a few rounds. The auction is the final offer stage, where candidates can see they're competing and sharpen their offers.
| Negotiation Type | Best For | Price Involved? | Auction-Only Features |
| RFI (Request for Information) | Qualifying suppliers and gathering information | Usually not | — |
| RFQ (Request for Quotation) | Complex or hard-to-define items, such as made-to-order goods | Yes | Supports two-stage RFQ |
| Auction | Clearly defined goods, such as office furniture | Yes | Autoextend, staggered closing, proxy bidding |
There are three: RFI, RFQ, and auction. An RFI gathers information and qualifies suppliers, usually without prices. An RFQ asks for quotes on complex or hard-to-define items and often runs several rounds. An auction asks for competitive bids on clearly defined items within a set time, and suppliers may be allowed to see other bids.
In a blind RFQ, the buyer can see quotes as they arrive, but suppliers can't. In a sealed RFQ, nobody sees the quotes until the RFQ closes and the quotes are unsealed. Either way, suppliers never see each other's quotes during an RFQ. Sealed RFQs suit public sector and other strict-governance buying.
A two-stage RFQ splits evaluation into a technical stage and a commercial stage. The evaluation team scores the technical responses first, without seeing prices. Only after that do they open the commercial responses. Two-stage evaluation is supported only for RFQs, not for RFIs or auctions, and it's common in engineering and capital buying.
Negotiation styles control which features and sections appear when a buyer creates a negotiation. An administrator can build a simple style for quick quotes and a full style for large strategic events. Styles help new buyers by hiding options they don't need, which reduces setup mistakes.
Buyers add requirements, which are questions suppliers must answer, such as certifications or delivery capacity. Each requirement can have a score and a weight, so responses can be ranked on more than price. Evaluation teams can score responses, and the buyer uses the combined result to decide the award.
Autoextend, staggered closing, and proxy bidding work only in auctions. Autoextend adds time when late bids come in. Staggered closing closes lines one after another. Proxy bidding lets a supplier set a minimum and have the system bid down to it. RFQs and auctions both support prebid submissions and mass price reductions.
The buyer awards lines to one or more suppliers, and the award can route for approval. After approval, the buyer creates the purchasing documents set by the negotiation's outcome: standard purchase orders, blanket purchase agreements, or contract purchase agreements. Interviewers like this question because it connects Sourcing back to Purchasing.
Yes. A buyer can add approved requisition lines to the Document Builder in Process Requisitions and create a negotiation from them. When the negotiation is awarded, the resulting purchase order keeps the link to the original requisition. This is the usual path when a large request needs competitive quotes before ordering.
Interviewers rarely ask where a button sits. They ask why a result happened. Before your interview, pick five common problems. Try a requisition that didn't convert, a supplier site missing from a PO, a stuck approval, a failed funds check, and a punchout cart without prices. Practice explaining the cause and the fix for each one in two sentences.
Supplier Portal questions test the supplier's side of the process. Oracle Supplier Portal is the work area where suppliers see and acknowledge orders, ship goods, submit invoices, check payments, and respond to negotiations. For example, a distributor can acknowledge a purchase order, send an advance shipment notice, and submit an invoice without emailing the buyer once.
Why do interviewers care about the supplier side? Because supplier adoption makes or breaks a go-live. A perfect purchasing setup still fails if suppliers can't register, log in, or find their orders. The candidate who can explain registration and spend authorization stands out.
Think of Supplier Portal like a delivery app for a restaurant's suppliers. The restaurant posts the order, the supplier confirms it, marks it shipped, and sends the bill, all in one place. Nobody has to chase anyone by phone.
Suppliers can view and acknowledge purchase orders, request order changes, create advance shipment notices, submit invoices when that's enabled, check payment status, and respond to negotiations. They can also view agreements and update their own company profile. All of this runs in the same Oracle Fusion Cloud Procurement application the buyers use.
A buyer can require acknowledgment on a purchase order, either at document level or at document and schedule level, with a due date. The supplier accepts or rejects the order in the Supplier Portal. A rejected order goes back to the buyer to fix. Acknowledgment gives the buyer written confirmation that the supplier agreed to the terms.
A prospective supplier fills in a registration form from a registration link set up for the procurement BU. The request routes through supplier registration approvals. Once it's approved, the supplier record is created, and the supplier's contacts can get user accounts for the Supplier Portal. Internal users can also register suppliers on a supplier's behalf.
Suppliers can update details such as addresses, contacts, and bank accounts in Supplier Portal. Changes route through supplier profile change approvals before they take effect. This keeps sensitive data, especially bank accounts, under review. Interviewers often ask who approves bank changes, so be ready to name an approval group.
Spend authorization controls whether a supplier can receive purchase orders. A prospective supplier can take part in sourcing, but it needs an approved spend authorization request before buyers can place orders with it. That way, new suppliers can compete for business before the full onboarding checks are done.
Supplier Qualification Management lets you assess suppliers through questionnaires and initiatives, then record qualifications with outcomes such as approved or rejected. Buyers can use those outcomes when picking suppliers for sourcing. For example, a food company can require a valid safety certification before a supplier can be invited to a negotiation.
Supplier contacts get roles based on what they do. Supplier Sales Representative handles negotiations. Supplier Customer Service Representative handles orders and shipments. Supplier Accounts Receivable Specialist handles invoices and payments, and Supplier Self Service Administrator manages the supplier's own users. Getting roles wrong is a common go-live problem.
Approval and scenario questions test whether you can design and support the whole procure-to-pay process. Oracle Fusion Procurement approvals run on rules that route documents to individuals, approval groups, or HCM hierarchies. For example, a rule can send every purchase order over ₹10 lakh to the plant head after the buyer's manager approves it.
How should you answer a scenario question? Start with questions, not configuration. Ask how many business units buy, whether buying is central or local, which spend runs through agreements, and who approves what. Then map the answers to setup.
Think of approval rules like the security desks in an office tower. Small visitors sign in at reception. Bigger visitors need an escort. The rules decide which desk each document passes, and how many.
Oracle uses Approval Management extensions (AMX) to route tasks. AMX pulls supervisory and position hierarchies from Oracle Fusion HCM (Human Capital Management). Administrators set rules in Procurement Approval Rules Management, and approvers act on tasks through the BPM (Business Process Management) worklist. Oracle's approvals overview covers the setup tasks.
Requisitions, purchasing documents, supplier negotiations, and negotiation awards can all go through approval. So can internal and external supplier registrations, supplier profile changes, supplier spend authorizations, and external purchase prices. Each has its own setup task, such as Manage Requisition Approvals or Manage Purchasing Document Approvals.
Rules can route to individual users, approval groups, the supervisory hierarchy, the position hierarchy, or job levels. Routing can be serial or parallel, and some tasks can be FYI only. A common design sends requisitions up the supervisory hierarchy by amount, then adds a category approval group for IT or capital items.
Start with the approval history on the document to see where it stopped. Then use the Transaction Manager in the Transaction Console to check the task and step in if needed. Common causes are a missing supervisor in HCM, an empty approval group, or a rule condition that no approver satisfies.
Use File-Based Data Import (FBDI) templates for purchase orders, blanket agreements, and contract agreements, then run the matching import processes. Load only open documents with their remaining quantities, not years of closed history. Suppliers load first, because orders need valid supplier sites. Reconcile open amounts against the legacy system before cutover.
Purchase order schedules drive receiving, and receipts update what's been received against each schedule. Payables matches supplier invoices to the purchase order and, for three-way matching, to the receipt. If the quantities or prices fall outside tolerance, the invoice goes on hold. That's why procurement and payables teams need to agree on match levels and tolerances early.
Start with questions: who buys, which spend repeats, and who approves. Then map the answers. Give each plant a requisitioning BU served by one central procurement BU. Put repeat items on blanket agreements so they convert automatically. Use RFQs for capital buys. Route approvals by amount through the supervisory hierarchy, and onboard suppliers through Supplier Portal.
One limitation is worth knowing. Oracle updates Fusion Cloud Procurement every quarter, and Redwood pages keep replacing classic screens. Page names and navigation in this guide may differ slightly from your own instance. Concepts such as business functions, agreement types, and negotiation types stay the same, and those are what interviewers test.
Reality: A blanket purchase agreement holds agreed prices for specific items. A contract purchase agreement holds terms and conditions only, with no item lines, and purchase orders reference it for any item covered by those terms. Why it matters: Mixing up the two is one of the fastest ways to lose an interviewer's confidence.
Reality: They can be the same unit or different units. Oracle's service provider model lets one procurement BU buy for many requisitioning BUs, and Oracle's setup process for basic procurement structures builds exactly that. Why it matters: Shared-service buying is common, and interviewers expect you to design it.
Reality: Supplier Portal runs inside Oracle Fusion Cloud Procurement. Suppliers act on the same purchase orders, agreements, and negotiations that buyers create, with no interface in between. Why it matters: Candidates who describe an "integration" here signal they haven't worked with the cloud product.
Reading answers helps you remember them. Running the flow yourself is what makes them sound real in an interview. Our Oracle Fusion Procurement Course runs on a live instance, so you set up business units, build agreements, run sourcing events, and act as a supplier yourself.
About TechLeads IT: TechLeads IT trains working professionals and graduates in Oracle Fusion Procurement, Financials, HCM, and related modules through hands-on, instance-based courses. Learn more: About TechLeads IT
Stay updated with the latest insights, trends, and expert tips on Oracle Fusion SCM. Subscribe to our newsletter and never miss an update!
0
LikesConnect with us
Subscribe