Odoo 19.0 Community · Persistent

purchase.requisition: fields, relations and API

The purchase.requisition model ("Purchase Requisition") is a persistent model declared by the Purchase Agreements module, then extended by 1 other module. It exposes 48 fields, 18 of them declared directly on the model; 3 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.

View source code Search another model

Model identity

Technical name: purchase.requisition
Label: Purchase Requisition
Type: Persistent (models.Model)
SQL table: purchase_requisition
Origin module: Purchase Agreements (purchase_requisition)
Extended by: purchase_requisition_stock
Default order (_order): id desc
Inherits from (mixins): mail.thread mail.activity.mixin

Model fields

18 own fields, 24 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

48 of 48 fields shown

Technical name	Label	Type	Details
active	Active	`boolean`
company_id	Company	`many2one` → res.company	required
currency_id	Currency	`many2one` → res.currency	requiredcomputed, stored
date_end	End Date	`date`
date_start	Start Date	`date`
description	Description	`html`
line_ids	Products to Purchase	`one2many` → purchase.requisition.line	inverse: `requisition_id`
name	Agreement	`char`	requiredread-only
order_count	Number of Orders	`integer`	computed
picking_type_id	Operation Type	`many2one` → stock.picking.type	required added by Purchase Requisition Stock (`purchase_requisition_stock`)
product_id	Product	`many2one` → product.product	related: `line_ids.product_id`
purchase_ids	Purchase Orders	`one2many` → purchase.order	inverse: `requisition_id`
reference	Reference	`char`
requisition_type	Agreement Type	`selection`	required Values: `blanket_order` (Blanket Order), `purchase_template` (Purchase Template)
state	Status	`selection`	required Values: `draft` (Draft), `confirmed` (Confirmed), `done` (Closed), `cancel` (Cancelled)
user_id	Purchase Representative	`many2one` → res.users
vendor_id	Vendor	`many2one` → res.partner
warehouse_id	Warehouse	`many2one` → stock.warehouse	added by Purchase Requisition Stock (`purchase_requisition_stock`)
activity_calendar_event_id	Next Activity Calendar Event	`many2one` → calendar.event	computed inherited from mail.activity.mixin
activity_date_deadline	Next Activity Deadline	`date`	read-onlycomputed inherited from mail.activity.mixin
activity_exception_decoration	Activity Exception Decoration Type of the exception activity on record.	`selection`	computed Values: `warning` (Alert), `danger` (Error) inherited from mail.activity.mixin
activity_exception_icon	Icon Icon to indicate an exception activity.	`char`	computed inherited from mail.activity.mixin
activity_ids	Activities	`one2many` → mail.activity	inverse: `res_id` inherited from mail.activity.mixin
activity_state	Activity State Status based on activities Overdue: Due date is already passed Today: Activity date is today Planned: Future activities.	`selection`	computed Values: `overdue` (Overdue), `today` (Today), `planned` (Planned) inherited from mail.activity.mixin
activity_summary	Next Activity Summary	`char`	related: `activity_ids.summary` inherited from mail.activity.mixin
activity_type_icon	Activity Type Icon	`char`	related: `activity_ids.icon` inherited from mail.activity.mixin
activity_type_id	Next Activity Type	`many2one` → mail.activity.type	related: `activity_ids.activity_type_id` inherited from mail.activity.mixin
activity_user_id	Responsible User	`many2one` → res.users	read-onlycomputed inherited from mail.activity.mixin
has_message	Has Message	`boolean`	computed inherited from mail.thread
message_attachment_count	Attachment Count	`integer`	computed inherited from mail.thread
message_follower_ids	Followers	`one2many` → mail.followers	inverse: `res_id` inherited from mail.thread
message_has_error	Message Delivery error If checked, some messages have a delivery error.	`boolean`	computed inherited from mail.thread
message_has_error_counter	Number of errors Number of messages with delivery error	`integer`	computed inherited from mail.thread
message_has_sms_error	SMS Delivery error If checked, some messages have a delivery error.	`boolean`	computed inherited from mail.thread
message_ids	Messages	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
message_is_follower	Is Follower	`boolean`	computed inherited from mail.thread
message_needaction	Action Needed If checked, new messages require your attention.	`boolean`	computed inherited from mail.thread
message_needaction_counter	Number of Actions Number of messages requiring action	`integer`	computed inherited from mail.thread
message_partner_ids	Followers (Partners)	`many2many` → res.partner	computed inherited from mail.thread
my_activity_date_deadline	My Activity Deadline	`date`	read-onlycomputed inherited from mail.activity.mixin
rating_ids	Ratings	`one2many` → rating.rating	inverse: `res_id` inherited from mail.thread
website_message_ids	Website Messages Website communication history	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
create_date	Created on	`datetime`	read-onlyautomatic
create_uid	Created by	`many2one` → res.users	read-onlyautomatic
display_name	Display Name	`char`	read-onlycomputedautomatic
id	ID	`integer`	read-onlyautomatic
write_date	Last Updated on	`datetime`	read-onlyautomatic
write_uid	Last Updated by	`many2one` → res.users	read-onlyautomatic

Relations

Models linked from this model

product.product: product_id
purchase.order: purchase_ids
purchase.requisition.line: line_ids
res.company: company_id
res.currency: currency_id
res.partner: vendor_id
res.users: user_id
stock.picking.type: picking_type_id
stock.warehouse: warehouse_id

Fields of other models pointing here

product.supplierinfo: purchase_requisition_id
purchase.order: requisition_id
purchase.requisition.line: requisition_id

Reading this model through the API

Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.

curl

curl -X POST "https://your-instance.odoo.com/json/2/purchase.requisition/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["name","company_id","currency_id","picking_type_id","requisition_type"],"limit":5}'

Python (requests)

import requests

BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}

res = requests.post(
    f"{BASE_URL}/purchase.requisition/search_read",
    headers=headers,
    json={"domain": [], "fields": ["name","company_id","currency_id","picking_type_id","requisition_type"], "limit": 5},
)
res.raise_for_status()
print(res.json())

External API access requires Odoo's Custom plan.
XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
The access rights and record rules of the key's user apply.

Cite this tool

Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.

<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/purchase-requisition">purchase.requisition (Odoo 19.0)</a>

Sources

Data verified on September 23, 2026 · Odoo 19.0 Community

Have an Odoo project, or want to put your ERP to work with AI? Let's talk

Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.