There are only two types of requisitions. One is InternalRequisition, which is used for material application between internal organizations; the other is PurchaseRequisition, which is used
There are only two types of requisitions, one is Internal Requisition, used for material application between Internal organizations; the other is Purchase Requisition, used
1. Requisitions
Path: Purchasing> Requisitions
There are only two types of requisitions. One is Internal Requisition, which is used for material application between Internal organizations; the other is Purchase Requisition, which is used to generate PO, apply for procurement from external suppliers.
Tables
The procurement application mainly involves the following three tables: PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_REQ_DISTRIBUTIONS_ALL.
The header table and the lines table are associated through REQUISITION_HEADER_ID. header <-1... *-> lines
The lines table and the distributions table are correlated through REQUISITION_LINE_ID. lines <-1... *-> distributions
PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_HEADERS_ALL stores information about requisition headers. You need one row for each requisition header you create. Each row contains the requisition number, preparer, status, and description.
.
REQUISITION_HEADER_ID is the unique system-generated requisition number. REQUISITION_HEADER_ID is invisible to the user. SEGMENT1 is the number you use to identify the requisition
In forms and reports. Oracle Purchasing generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONTROL table if you choose to let Oracle Purchasing generate requisition numbers for you.
.
PO_REQUISITION_HEADERS_ALL is one of three tables storing requisition information. PO_REQUISITION_HEADERS_ALL corresponds to the Header region of the Requisitions window.
.
SEGMENT1 provides unique values for each row in the table in addition to REQUISITION_HEADER_ID.
PO_REQUISITION_LINES
PO_REQUISITION_LINES stores information about requisition lines. you need one row for each requisition line you create. each row contains the line number, item number, item category, item description, need-by date, deliver-to location, item quantities, units, prices, requestor, notes, and suggested supplier information for the requisition line.
.
LINE_LOCATION_ID identifies the purchase order shipment line on which you placed the requisition. LINE_LOCATION_ID is null if you have not placed the requisition line on a purchase order.
BLANKET_PO_HEADER_ID and BLANKET_PO_LINE_NUM store the suggested blanket purchase agreement or catalog quotation line information for the requisition line.
PARENT_REQ_LINE_ID contains the REQUISITION_LINE_ID from the original requisition line if you exploded or multisourced this requisition line.
.
PO_REQUISITION_LINES is one of three tables storing requisition information. This table corresponds to the Lines region of the Requisitions window
PO_REQ_DISTRIBUTIONS_ALL
PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions associated with each requisition line. Each requisition line must have at least one accounting distribution.
You need one row for each requisition distribution you create. Each row where the Accounting Flexfield ID and requisition line quantity.
.
PO_REQ_DISTRIBUTIONS_ALL is one of three tables storing your requisition information. This table corresponds to the requisition Distributions window, accessible through the Requisitions window
Fields in the PO_REQ_DISTRIBUTIONS_ALL table corresponding to the three Account information in Distribution
Debit (DR): CODE_COMBINATION_ID,
Credit (CR): ACCRUAL_ACCOUNT_ID,
Variance: VARIANCE_ACCOUNT_ID
All three accounts can be found in GL_CODE_COMBINATIONS_KFV.
Queries
SELECT * FROM PO_REQUISITION_HEADERS_ALL WHERE segment1 = '20140901 ';
SELECT line. * FROM PO_REQUISITION_HEADERS_ALL header, PO_REQUISITION_LINES_ALL line
WHERE header. REQUISITION_HEADER_ID = line. REQUISITION_HEADER_ID
AND header. segment1 = '20140901 ';
SELECT * FROM PO_REQUISITION_LINES_ALL line, PO_REQ_DISTRIBUTIONS_ALL dis
WHERE line. REQUISITION_LINE_ID = dis. REQUISITION_LINE_ID
AND line. REQUISITION_HEADER_ID IN (SELECT REQUISITION_HEADER_ID FROM PO_REQUISITION_HEADERS_ALL WHERE segment1 = '20140901 ');
2. AutoCreate
AutoCreate is used to convert PR to PO
Path: Purchasing> AutoCreate
NOTE: If PR cannot be found, check whether the Buyer or Ship-To inputs are correct. You can clear the two fields and check again.
Here we use the Automatic mode to generate the PO, and then the window will pop up, enter necessary information about the necessary purchase order, such as the supplier, currency...