Study guide

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes

Microsoft Dynamics 365 Supply Chain Management Functional Consultant MB-330

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Product Master and Released Products

1.1 Product Masters, Variants, and Configuration Technologies 1.2 Product Templates, Category Hierarchies, and Product Lifecycle States 1.3 Product Attributes, Attribute Types, and Attribute Groups

2 Chapter 2: Bills of Materials (BOM) and Formulas

2.1 BOM Lines, Line Types, and Component Configurations 2.2 BOM Versions, Activation, Approvals, and Circularity Checks 2.3 BOM Calculations, Cost Group Types, Flushing Principles, and Scrap Handling

3 Chapter 3: Product Prerequisites and Dimension Groups

3.1 Product, Storage, and Tracking Dimension Groups 3.2 Item Model Groups, Inventory Models, and Physical/Financial Posting 3.3 Reservation Hierarchies and Unit Sequence Groups

4 Chapter 4: Additional Product Details and Warehouse Fit

4.1 Bar Codes, GTINs, and Product Unit Conversions 4.2 Default Order Settings and Site-Specific Order Settings 4.3 Product Filter Codes and Physical Warehouse Dimensions

5 Chapter 5: Inventory Costing and Pricing

5.1 Costing Versions, Costing Sheets, and Standard Costing 5.2 Base Item Prices, Price Groups, and Price Tolerances 5.3 Trade Agreements, Price/Discount Journals, and Smart Rounding

6 Chapter 6: Inventory Journals and Core Transactions

6.1 Movement, Adjustment, and Transfer Journals 6.2 Counting Journals, Tag Counting, and Cycle Count Adjustments 6.3 Item Arrival Journals, Output Orders, and BOM Journals

7 Chapter 7: Inventory Operations, Blocking, and Closing

7.1 Transfer Orders, In-Transit Warehouses, and Delivery Schedules 7.2 Inventory Blocking Mechanisms, Batch Disposition Codes, and Inventory Status 7.3 Inventory Closing, Recalculation, Settlement, and ABC Classification

8 Chapter 8: Quality Management and Nonconformance

8.1 Quality Control Setup: Tests, Test Groups, and Item Sampling 8.2 Quality Associations, Automatic Generation, and Quality Orders Processing 8.3 Nonconformances, Corrections, Corrective Operations, and Quarantine Orders

9 Chapter 9: Asset Management: Setup and Maintenance

9.1 Assets, Asset Types, and Functional Locations Setup 9.2 Asset Lifecycle Models, Lifecycle States, and Asset Loans 9.3 Work Orders Configuration, Work Order Settings, and Maintenance Capacity Management 9.4 Maintenance Plans, Maintenance Requests, Work Order Scheduling, and Journal Consumption

10 Chapter 10: Procurement and Sourcing Configuration

10.1 Vendors, Vendor Groups, and Procurement Category Hierarchies 10.2 Purchasing Policies, Spending Limits, Procurement Workflows, and Charge Codes 10.3 Purchase Agreements, Vendor Rebates, and Vendor Collaboration Portal

11 Chapter 11: Purchase Order Lifecycle and Consignment

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes 11.2 Purchase Orders Creation, Over/Under-Delivery Tolerances, Delivery Schedules, and Product Receipt 11.3 Consignment Inventory Replenishment/Ownership Change and Vendor Return Orders

12 Chapter 12: Landed Cost and Inbound Logistics

12.1 Landed Cost Architecture: Voyages, Shipping Containers, Folios, and Journey Templates 12.2 Cost Type Codes, Auto-Costs, and Allocation Methods 12.3 Tracking Control Center, Goods in Transit Orders, and Over/Under Tolerances

13 Chapter 13: Sales Management and Order Processing

13.1 Customers, Customer Groups, Sales Agreements, and Sales Quotations 13.2 Sales Order Processing, Manual and Automatic Reservation, and Sales Returns 13.3 Order Promising: ATP, CTP, Delivery Schedules, and Product Bundles 13.4 Intercompany Trading Chains, Sales Commissions, and Customer Rebates

14 Chapter 14: Warehouse Setup and Core Infrastructure

14.1 Warehouse Topology: Sites, Warehouses, Locations, Profiles, Formats, and Zones 14.2 Work Policies, Work Breaks, and Packing Dimensions 14.3 Wave Templates, Work Templates, and Location Directives Configuration 14.4 Label Layouts, Document Routing, Wave Label Printing, and GS1 Number Sequences

15 Chapter 15: Warehouse Execution Processes

15.1 Inbound Receiving Processes, Planned Cross-Docking, and Putaway 15.2 Outbound Waves, Wave Processing, Picking (Order, Cluster, Batch), and Manual Packing 15.3 Replenishment Strategies (Wave vs. Min/Max) and Inventory Movements via Warehouse Work 15.4 Cycle Counting Plans, Thresholds, Blind Counting, and Automated Containerization

16 Chapter 16: Transportation Management and Logistics

16.1 Shipping Carriers, Carrier Groups, Carrier Services, and Rate/Route Engines 16.2 Route Plans, Route Guides, Inbound/Outbound Loads, and Dock Appointment Scheduling 16.3 Freight Bills, Freight Invoicing, and Manual/Automatic Freight Reconciliation

17 Chapter 17: Warehouse Management Mobile App

17.1 Mobile App Installation, Display Settings, Connection Profiles, and Warehouse Worker Setup 17.2 Mobile Device Menus, Work-Based and Indirect Menu Items, and Inventory Inquiries 17.3 Step Detours Configuration and GS1 Barcode Scanning Implementation

18 Chapter 18: Master Planning and Planning Optimization

18.1 Master Planning Parameters, Coverage Groups, and Planning Optimization Cloud Service Architecture 18.2 Item Coverage Settings, Positive/Negative Days, Time Fences, and Action Messages 18.3 Running Master Planning, Analyzing Results, Planned Orders Firming, and Supply Schedule 18.4 Safety Stock Journals, Safety Margins, and Copilot in Dynamics 365 Supply Chain Management

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes

Key Takeaways Explain This Topic AI

Purchase requisitions capture internal employee demand for operational consumption (cost-centered expensing) or replenishment (inventory restocking), supporting catalog-released products and non-catalog category lines.

Requisitions advance through Draft, In review, Approved, Rejected, and Closed lifecycle states, governed by configurable header- and line-level workflows enforcing employee signing limits.

Purchasing policy demand consolidation rules automate purchase order generation from approved requisitions or aggregate demand across disparate requesters into single purchase orders for negotiated volume discounts.

Requests for Quotation (RFQs) support Purchase order, Purchase agreement, and Purchase requisition target types, with solicitation executed via manual invitations or public vendor bidding through the Vendor Collaboration portal.

Vendor replies can be captured via direct vendor collaboration entry or internal proxy entry, scored against multi-criteria weighting matrices (price, lead time, quality), and accepted to automatically spawn purchase orders or update requisition lines.

Last updated: September 2026

11.1 Purchase Requisitions, Requests for Quotation (RFQs), and Bidding Processes

Quick Answer: In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), internal procurement demand initiates through Purchase Requisitions for Consumption (expensed operational goods/services) or Replenishment (warehouse inventory restocking), utilizing either Catalog items or non-catalog Procurement categories . Requisitions progress through a workflow state machine ( Draft , In review , Approved , Rejected , Closed ) governed by Signing limits and Purchasing policies . Approved lines can automatically generate purchase orders or be aggregated using the Demand consolidation workbench. For competitive sourcing, Requests for Quotation (RFQs) solicit bids across three document types ( Purchase order , Purchase agreement , or Purchase requisition ) via direct invitation or the Vendor Collaboration portal , where bids are captured, evaluated using weighted Scoring criteria , and awarded.

1. Purchase Requisitions Architecture and Demand Intake

A Purchase requisition is an internal document authorizing the purchasing department to procure goods and services. Requisitions prevent uncontrolled organizational spending by requiring internal authorization before commercial commitments exist.

Navigation : Procurement and sourcing > Purchase requisitions > Purchase requisitions prepared by me (or All purchase requisitions )

Requisition Purposes: Consumption vs. Replenishment

When creating a requisition header, the user selects a Requisition purpose , which strictly governs line behavior and downstream document conversion:

Consumption :

Intended for internal operational consumption (e.g., office stationery, employee laptops, third-party consulting, machine maintenance spares).

Goods are directly expensed upon receipt to an operating department, cost center, or project work breakdown structure (WBS).

Can utilize either Released products (catalog items) or Procurement categories (non-catalog lines).

Downstream conversion creates standard commercial purchase orders.

Replenishment :

Intended to restock warehouse inventory across distribution centers or production facilities.

Must specify Released products with valid inventory storage dimensions ( Site , Warehouse ).

Interacts directly with Master Planning; approved replenishment requisitions generate planned purchase orders or transfer orders.

Catalog Items vs. Non-Catalog Category Lines

Requisition lines handle two distinct procurement data structures:

Catalog Items (Item lines) :

Sourced from released products configured in Product Information Management and mapped to internal procurement catalogs.

Reference pre-defined item numbers, standard units of measure, approved vendor lists, trade agreement pricing, and item model groups.

Require physical inventory dimension tracking when received.

Non-Catalog Category Lines (Category lines) :

Used for one-off, ad-hoc, or service purchases where maintaining a formal released product master is impractical (e.g., legal advisory, facility cleaning, custom fabrication).

Sourced from the Procurement category hierarchy ( Procurement and sourcing > Setup > Categories > Procurement categories ).

Requesters specify a category node, free-text commodity description, unit of measure, requested quantity, and estimated unit price.

General Ledger distribution derives from the Category policy rules and inventory posting profiles mapped to the Purchase expenditure for expense posting type. +-------------------------------------------------------------------------------------------------+

  • | PURCHASE REQUISITION LINE TYPES |
  • +------------------------------------+------------------------------------------------------------+
  • | Catalog Item Line | Non-Catalog Category Line |
  • | • Released product ID required | • Selected from Procurement Category Hierarchy |
  • | • Default pricing from trade agmts | • Free-text item description and estimated unit price |
  • | • Inventory transactions created | • Expensed directly to P&L accounts (No item inventory) |
  • | • Mandatory Site / Warehouse | • Financial dimensions (Cost Center, Dept) set on line |
  • +------------------------------------+------------------------------------------------------------+
  • Purchasing Policies and Catalog Access

Requisition behavior is governed by Purchasing policies ( Procurement and sourcing > Setup > Policies > Purchasing policies ):

Catalog policy rule : Determines which procurement catalogs are visible to specific legal entities, operational units, or user roles.

Category policy rule : Controls whether specific categories require matching purchase orders, allow receiving without POs, or enforce price tolerance thresholds.

Requisition purpose rule : Dictates whether employees can submit replenishment requisitions or are restricted strictly to consumption.

2. Requisition Lifecycle, Workflow Topologies, and Signing Limits

Purchase requisitions progress through a deterministic state machine managed by the workflow infrastructure: [Draft] ---> (Submit) ---> [In review] ---> (Approve) ---> [Approved] ---> (Release) ---> [Closed]

  • | |
  • (Reject) (Re-approve rule)
  • v |
  • [Rejected] -------------------------+
  • Lifecycle Status Progression

Draft : The requisition is created and editable by the preparer. Line inventory transactions do not exist.

In review : Submitted to the workflow engine. The document is locked from interactive editing. Workflow evaluates approval conditions, managerial hierarchies, and signing limit policies.

Approved : All workflow approvers have signed off. Requisition lines are locked and eligible for conversion into purchase orders or RFQs.

Rejected : A designated approver rejects the document. The requisition returns to the preparer with reviewer audit notes. The preparer can modify details and resubmit or cancel the requisition.

Closed : All approved lines have been converted into purchase orders, fulfilled via internal transfers, or manually cancelled.

Workflow Topologies: Header vs. Line-Level Routing

Organizations deploy two complementary workflow types for purchase requisitions:

Purchase requisition review workflow ( PurchReqReview ) : Operates at the document header level. Orchestrates global submission, overall state management, and final approval.

Purchase requisition line review workflow ( PurchReqLineReview ) : Operates independently on individual lines within the requisition. Allows parallel, conditional routing: Line 1 (IT Hardware) routes to the Chief Information Officer, while Line 2 (Safety Equipment) routes to the Plant Health & Safety Director.

Signing Limits and Spending Authority

Approver authority is enforced using Signing limits ( Organization administration > Setup > Signing limits > Signing limit parameters ):

Spending limit : Maximum monetary amount an employee can authorize on a requisition they author.

Approval limit : Maximum monetary threshold an approver can approve for subordinates within their reporting hierarchy.

If a requisition's net amount exceeds a manager's approval limit, the workflow engine automatically escalates the document up the managerial hierarchy until an executive with sufficient limit signs off.

Important

Re-approval Rules: If an approved requisition is amended prior to purchase order generation, the Re-approval rule for purchase requisitions policy determines whether the document must re-enter the workflow. Configurable triggers include changes to net line amount, quantity, unit price, required date, or vendor account.

3. Demand Consolidation and Automated Purchase Order Generation

Once requisitions attain Approved status, they must be converted into commercial purchase orders for vendor fulfillment.

Policy-Driven Automated PO Generation

Under Procurement and sourcing > Setup > Policies > Purchasing policies , open the Purchase order creation and demand consolidation rules policy rule:

Automatically create purchase orders : When enabled, the workflow approval event immediately and automatically spawns purchase orders in the background without buyer intervention.

Run automatic purchase order creation as a batch job : Schedules asynchronous processing to prevent user session timeouts during high-volume periods.

Manual Release and Demand Consolidation Workbench

When automatic creation is disabled or lines require commercial evaluation, approved lines route to the Release approved purchase requisitions form:

Navigation : Procurement and sourcing > Purchase requisitions > Approved purchase requisition processing > Release approved purchase requisitions

Buyers utilize this workbench to achieve economy-of-scale savings through Demand consolidation :

Aggregating Lines : Multiple approved lines from different departments requesting the identical released item or vendor are grouped together.

Negotiating Volume Pricing : Consolidating five separate requests of 20 units into a single PO of 100 units triggers negotiated supplier price breaks and minimizes inbound freight handling.

Consolidation Opportunities : Buyers create a Consolidation opportunity record ( Approved purchase requisition processing > Consolidation opportunities ), setting a demand holding window (e.g., hold open requisitions for 7 days) to pool requirements across the enterprise before generating consolidated orders.

4. Requests for Quotation (RFQs): Types, Solicitation, and Portal Collaboration

A Request for Quotation (RFQ) solicits competitive pricing, lead times, and delivery terms from multiple suppliers before an order is placed.

  • Navigation : Procurement and sourcing > Requests for quotations > All requests for quotations
  • RFQ Document Types

When creating an RFQ header, the Request for quotation type determines the downstream commercial document generated upon bid award:

RFQ Type Business Application Target Document Generated Upon Award

Purchase order Discrete purchase of items or services with immediate delivery requirements. Generates a standard commercial Purchase order ( PurchTable ).

Purchase agreement Establishing long-term blanket contracts with negotiated pricing, quantity, or value commitments. Generates a formal Purchase agreement ( PurchAgreementHeader ).

Purchase requisition Competitive sourcing initiated directly from an approved or draft requisition line. Does not create a PO directly; updates the originating requisition line with the winning vendor, price, and terms.

Solicitation Mechanisms: Direct Invitation vs. Public Collaboration

Direct Invitation : The purchasing agent manually adds approved vendors to the RFQ header's Vendors FastTab. The system generates vendor-specific quotation sheets.

Open Bidding / Public Solicitation : RFQs are published to the Vendor Collaboration portal . Prospective or registered vendors view public opportunities, register their intent to bid, and submit bids electronically.

RFQ Status Progression

Created : RFQ lines, delivery specifications, and questionnaire attachments are drafted.

Sent : Quotations are transmitted to vendors (printed, emailed, or published to Vendor Collaboration). Line status updates to Sent .

Received : Vendor responses are captured in the system. The RFQ is locked against modifications until evaluated.

Accepted / Rejected : Winning bid lines are accepted; non-winning bids are declined with mandatory reason codes.

Closed : Target purchase documents have been spawned, closing the sourcing event.

  • 5. Vendor Bidding, Multi-Criteria Scoring, and Quote Awarding
  • Capturing Vendor Bid Responses

Vendor responses are ingested through two pathways:

Vendor Collaboration Portal : External suppliers log in securely, navigate to Bid on RFQs , enter unit prices, lead times, promised delivery dates, line discounts, and miscellaneous charges. Suppliers can propose alternate items or split delivery quantities.

Manual Bid Entry ( Enter reply ) : If vendors submit quotations via physical mail or email, the buyer opens the RFQ, clicks Enter reply on the Action Pane, and transcribes the commercial terms directly into D365 SCM.

Multi-Criteria Scoring Framework

To prevent purchasing decisions based solely on unit cost, D365 SCM provides an objective, multi-criteria scoring engine:

Scoring Criteria : Configure evaluation dimensions under Procurement and sourcing > Setup > Request for quotation > Scoring criteria (e.g., Unit Price, Lead Time, Technical Specification Compliance, Quality Rating, Warranty Duration).

Scoring Methods : Group criteria into a Scoring method ( Setup > Request for quotation > Scoring methods ) and assign percentage weightings (e.g., Price = 50%, Delivery Lead Time = 30%, Quality Rating = 20%).

During bid evaluation, evaluators assign numerical scores (e.g., 1 to 5) to each criterion for each vendor response line.

Bid Comparison and Award Execution

On the RFQ Action Pane, click Compare replies .

The system displays a side-by-side comparison matrix showing prices, quantities, delivery dates, line charges, and weighted composite scores.

Awarding : The buyer selects the winning vendor line and clicks Accept . The system prompts for an acceptance reason code.

Declining : Non-winning vendor lines are updated by clicking Reject , triggering automated rejection notifications containing formal reason codes ( Setup > Request for quotation > Reason codes ).

Document Generation : Accepting the line instantly updates the RFQ line to Accepted and executes document conversion based on the RFQ type (Purchase order, Purchase agreement, or Purchase requisition update).

Tip

Prospective Vendor Promotion: If an open RFQ is awarded to an unapproved prospective vendor who bid via Vendor Collaboration, D365 SCM halts purchase order generation until the vendor completes the Prospective vendor registration workflow and is promoted to an active approved vendor account.