Purchase requests

Choose purchase-request type, department and requester

Set the operational classification and owner.

Audience: Purchasing staffPermission: purchase_request capability and status capability where applicableModule v1.7.9

Exact navigationAdmin Area → Purchase → Purchase Request → New/Edit

Before you begin

Use an account with purchase_request capability and status capability where applicable and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Set the operational classification and owner. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Admin Area → Purchase → Purchase Request → New/Edit.
Open the exact setting, option or record named in this guide.
Enter or select the required value; leave unrelated options unchanged.
Save the form and wait for the success response.
Reload the page or open a controlled record to confirm the stored value is being used.

Fields, choices and supported possibilities

Request headerRequest code/name, requester, type, department, project, related sales estimate/invoice, currency and rate.

Request linesItems, description, quantity, unit, tax, price, discount, subtotal and total.

SourcingSelected vendors, attachments, public share/request-for-quotation actions and approval status.

Code-backed validations and workflow rules

Purchase-request status changes use the dedicated purchase_request status capability in addition to record access.
Department can be mandatory when pur_department_required_condition is enabled.

Expected result and verification

The supported choose purchase-request type, department and requester flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.