Skip to main content

Purchase Requisition

Purchase Requisition is the request-to-buy module. It sits between planning and sourcing: BOM or indirect demand enters as a draft PR, then leaves as approved line items ready for RFQ staging.

The PR is where Grinea checks whether the request has enough business context, delivery information, and approval before suppliers are asked to quote.

Basic Concepts​

A Project Purchase PR comes from an active project BOM. It keeps the project context and uses BOM line items as the source demand.

A Non-Project Purchase PR is created without a project or BOM. It uses CAPEX or OPEX context instead.

Line Items are the materials or services being requested.

Delivery Details describe where, when, and in what quantities the requested items should be delivered.

Approval Flow shows the current decision path and who needs to act next.

Project Purchase​

Project Purchase workspaceProject Purchase workspaceDraftLine ItemsDelivery DetailsApproval FlowMaterial lineService lineDelivery schedule rowSave DraftSubmit PR
A project PR page combines selected BOM lines, delivery rows, documents, and the submit action.

Project Purchase is used when the buyer needs to procure items from an active BOM. The project and issue number anchor the PR, and the buyer adds the eligible BOM lines that should be requested.

The important decision in this workspace is not only which lines to buy. The buyer also confirms how those lines should be delivered. Delivery details should reflect the intended procurement plan, not just the earlier planning estimate.

When the PR is submitted, approvers can approve it or return it for correction. An approved project PR makes its line items available for RFQ staging.

Non-Project Purchase​

Indirect PR workspaceIndirect PR workspaceOPEXAdditional DetailsLine ItemsDelivery DetailsCost centreWarehouseReceiving contactAdd ServiceUpdate ScheduleSubmit PR
The indirect workspace gives the buyer the same PR controls without project or BOM dependency.

Non-Project Purchase is used when the spend is not tied to a project BOM. The PR itself carries the context that a project purchase would inherit from the project.

The additional details section matters more here: purchase type, org unit, cost centre, warehouse, and transaction data shape approval and later order handling.

Delivery locations come from delivery location management rather than the project profile. The receiving contact matters because that person may later receive or reject delivery from the order.

Approval And Assignment​

Approval actionsApproval actionsApproval FlowApproval FlowReviewer noteNext approverReason required on returnApproveReturn
Approval work is handled from record headers and confirmation modals, not from a separate flow screen.

Approval turns a draft request into sourcing-ready demand.

For indirect PRs, the Purchasing Director assigns a buyer after the required approval steps. The buyer then accepts the task before making the buyer decision.

Returned PRs stay in the PR module. The owner corrects the record and resubmits it. Rejected buyer tasks go back to Purchasing Director assignment.

RFQ Staging Entry​

RFQ stagingRFQ stagingRFQ StagingSearch and filtersCreate RFQ DraftPR line itemMaterial categoryRemaining quantity
The staging page lets the buyer select approved PR lines and create one RFQ draft from them.

Approved PR lines become the input for RFQ staging. The Create RFQ action appears when the PR has approved, stageable line items.

If Create RFQ is missing, read the PR status, line item status, and current owner before assuming the RFQ module is the problem.