DemandFlow Support Centre

PRREQ: PR Request

ReferenceEntity Reference16/04/2026Updated 16/04/2026
The PRREQ entity represents a purchase requisition request capturing what is being bought, why, vendor selection, approvals, and spend profiling.

PRREQ: PR Request

The PRREQ entity represents a purchase requisition request capturing what is being bought, why, vendor selection, approvals, and spend profiling.

Default definition. This article describes the default PRREQ definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches PRREQ.

Entity properties

PropertyValue
Entity codePRREQ
Display namePR Request
PluralPR Requests
Level800

Use cases

PRREQ is the originating request entity in the procurement workflow, created before a PO exists. It captures the business justification (what, why, and impact of not purchasing), links to a vendor (VEN), and tracks the request through a multi-stage status workflow from 'New' through approval, PR/PO request, to done or cancelled. The entity supports both kanban and grid views for pipeline management, with a card template showing reference, name, requestor, and quote amount. The purchase section includes telecom-specific network category codes (N056, T092, etc.) reflecting deployment in a telecoms procurement environment. The existContract and newContract checkboxGroup fields implement TSA (Transition Services Agreement) classification logic for determining contract uplift timelines. Two spend profile rows (receipting and future) use the spend row type for 12-period financial planning. The PO panel shows related purchase orders via SUB|PRREQ|PO comboKey, linking the requisition to its resulting POs. CPA (Corporate Purchase Agreement) fields track whether spending is covered by existing framework agreements.

Fields

General

FieldTypeRequiredNotes
nametextYesName.
descriptiontext (multi-line)Description.
ownerIdreference → userRequestor. Read-only.
createdtimestampRequest date.
statusenumYesStatus. Valid ids: new (New), onhold (On hold), approvalRequested (Approval requested), prRequested (PR requested), poRequested (PO requested), done (Done), cancelled (Cancelled).
quoteReftextYesQuote reference.
quoteAmountnumberYesQuote amount.
portfolioreference → PORTPortfolio.
projectreference → PJProject.
cpaCoveredsingleselectCovered by CPA.
cpaReftextCPA reference.
whattext (multi-line)What is being purchased.
whytext (multi-line)Why is this required?
impacttext (multi-line)Impact of not purchasing.
vendorreference → VENVendor.
dayratenumberDay rate.
sharepointtext (URL)Sharepoint URL.
networkCatenumNetwork category. Valid ids: Unknown (Unknown), N056 - Hardware / Software virtualized infrastructure for Mobile Core Network Elements Only (N056 - Hardware / Software virtualized infrastructure for Mobile Core Network Elements Only), N506 - Support, Maintenance and Assisted Operation for virtualized infrastructure for Mobile Core Network Elements Only (N506 - Support, Maintenance and Assisted Operation for virtualized infrastructure for Mobile Core Network Elements Only), S101 - Installations in network buildings, except relating to Mobile Radio / Core Network Equipment (S101 - Installations in network buildings, except relating to Mobile Radio / Core Network Equipment), T092 - NT Server (T092 - NT Server), T101 - Disk Storage, Recovery and Backup Systems (T101 - Disk Storage, Recovery and Backup Systems), T150 - Distributed infrastructure Operation & Transformation Services (servers x86, Unix, storage, backup) (T150 - Distributed infrastructure Operation & Transformation Services (servers x86, Unix, storage, backup)), T170 - IT Infrastructure Consultancy Services (T170 - IT Infrastructure Consultancy Services), Not shown in list (Not shown in list).
existContractcheckboxGroupNot Classified as a new contract - needs to be uplifted by April 2027.
newContractcheckboxGroupClassified as a new contract - would need to be uplifted by April 2024.
poreference → POPurchase order. Read-only.
prNumbertextPR reference.
poNumbertextPO reference. Read-only.

Additional panels

  • Documents. Field files.
  • Documents. Field files.
  • 12-period spend grid panel.

Relationships

  • Lookups: portfolio points at PORT record; project points at PJ record; vendor points at VEN record; po points at PO record.
  • Related lists: PO via format SUB|PRREQ|PO.

Creating a PR Request via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "PRREQ",
  "level":    800,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "status": "new",
  "quoteRef": "Example text",
  "quoteAmount": 100
}

Listing PRREQ records

# All pr requests in your tenant
GET /v1/entities/PRREQ/SUB

See also

prreqpr requestpr requestsrequest

Was this article helpful?

← Back to Knowledge Base