You are on page 1of 7

Oracle Purchasing

Purchase Requisitions
A Purchase Requisition is the procedural method by which different departments of organization
may request the purchase of goods and/or services, which require processing by Procurement
Department.
In other words, a requisition is nothing but a formal request to buy something (like Inventory
material, office supplies etc.,) needed for the enterprise. Only an employee can create one.

Navigation
Purchasing Vision Operations (USA) > Requisitions > Requisitions
Choose the requisition type and enter the Item, quantity, Price details in
the Lines tab.

In Source Details tab, we
select the Buyers name
(Optional)
Charge Account is entered
in the Distributions and
Save
The status of the requisition will now be Incomplete. The Approve button is
highlighted. Now, the requisition needs to be approved, thus, we need to submit
this requisition for Approval by clicking on the Approve button.
The status will now be updated to In Process .The workflow then will send an
Approval notification to the concerned person (derived based on hierarchy used
Position or Supervisor hierarchy) using which he can Approve or Reject the requisition.
PO_Requisition_Headers_All : it stores information about requisition headers. Each row contains the
requisition number and Addition relevant information. REQUISTION_HEADER_ID is primary key.

HR_Employees : it's a view that contains information about employees. You must have a row for each
requestor, requisition preparer, approver , buyer or receiver . The primary key is EMPLOYEE_ID.

PO_Requisition_Lines_All : This table stores the information about the requisition lines like quantity, item,
deliver to location, requestor etc. Primary Key is REQUISTION_LINE_ID

MTL_System_Items_B : This is the definition table for items. This table holds the definitions for inventory
items, and purchasing items. The primary key is INVENTORY_ITEM, ORGANIZATION_ID.

PO_REQ_Distributions_All : This table stores the information about the accounting distributions
associated with each requisition line. Each requisition line must have at least one accounting distribution.
Each row includes the accounting flex field id and requisition line quantity. The primary key is
DISTRIBUTION_ID.

GL_CODE_Combinations: This table stores valid Accounting Flex Field segment value combinations for
each accounting flex field structure within your GL application. GL_CODE_COMBINATIONS is populated by
the system when a new accounting flex field combination is used, either through dynamic insertion or
manually.

Important Metrics on PR
# of Requisition Lines - Count of number of requisition lines
# of Requisitions - # of Requisitions
Approval Cycle Time - This metric is the elapsed day between when
the requisition was submitted to when it was approved. when they
are done in the same day, this metric will be 0.
Average Number of Requisition Lines - This metric tracks the
average number of lines for a requisition or group of requisitions. It
can be analyzed over time or by various attributes such as
department, cost center, location, or organization.
Requested Amount - The currency value of the requisition in
document or transaction at the time the action was performed.
Time To Perform - This metric is the average time elapsed in
performing a particular action on a requisition, such as submitting,
approving, or declining. Requisitions may contain more than one
action depending on the business rules of the sources system.

You might also like