Aid to Understanding How CREATEPO Workflow Groups Requisition Lines On To A Single Purchasing Document
(Doc ID 1478648.1)
Last updated on SEPTEMBER 01, 2022
Applies to:
Oracle Purchasing - Version 12.1.3 and laterInformation in this document applies to any platform.
Goal
To provide an understanding as to how the CREATEPO Workflow groups requisition lines on to a single purchasing document.
The package PO_AUTOCREATE_DOC contained in the file POXWATCB.pls contains the procedures that parse the requisitions lines and inserts the successful Lines in to the PO Open Interface (PDOI).
When the lines are inserted in to the PDOI, they are grouped so those with similar citeria are placed on to one purchasing document.
The procedure that perfoms the grouping is group_req_lines which reads parsed lines inserted earlier in to the tempoary table po_wf_candidate_req_lines_temp.
Two identical cursors, c1 & c2, are used to read from the tempoary table po_wf_candidate_req_lines_temp
This procedure then loops through the rows in po_wf_candidate_req_lines_temp comparing the values in c1 & c2 and those that match are grouped on to one purchasing document.
| Cursor Field c1 & c2 | Table | Column | Form Display Field |
|---|---|---|---|
| _DELIVER_TO_LOCATION_CODE |
PO_REQUISITION_LINES_ALL HR_LOCATIONS_ALL |
LOCATION_CODE DELIVER_TO_LOCATION_ID |
Location |
| _SUGGESTED_BUYER_ID | PO_REQUISITION_LINES_ALL | SUGGESTED_BUYER_ID | Buyer |
| _SUGGESTED_VENDOR_ID | PO_REQUISITION_LINES_ALL | VENDOR_ID | Supplier |
| _SUGGESTED_VENDOR_SITE_ID | PO_REQUISITION_LINES_ALL | VENDOR_SITE_ID | Site |
| _SOURCE_DOC_TYPE_CODE | PO_REQUISITION_LINES_ALL | DOCUMENT_TYPE_CODE | Source Detail: Document Type |
| _SOURCE_DOC_ID | PO_REQUISITION_LINES_ALL | BLANKET_PO_HEADER_ID | Source Detail: Document |
| _GA_FLAG | PO_HEADERS_ALL | GLOBAL_AGREEMENT_FLAG | |
| _CONTRACT_ID | PO_HEADERS_ALL | PO_HEADER_ID | Number |
| _CURRENCY_CODE | PO_REQUISITION_LINES_ALL | CURRENCY_CODE | Currency: Currency |
| _RATE_TYPE | PO_REQUISITION_LINES_ALL | RATE_TYPE | Currency: Rate Type |
| _RATE_DATE | PO_REQUISITION_LINES_ALL | RATE_DATE | Currency: Rate Date |
| _RATE | PO_REQUISITION_LINES_ALL | RATE | Currency: Rate |
| _PCARD_ID | PO_REQUISITION_LINES_ALL | PCARD_ID | Procurement cards (Used in iProcurment only) |
| _REQ_LINE_ID | PO_REQUISITION_LINES_ALL | LABOR_REQ_LINE_ID |
The CREATEPO Workflow attribute GROUPING_ALLOWED_FLAG does not determine if requisition lines are created on different purchasing documents.
When the attribute is 'N' the meaning is 'REQUISITION', 'Y' the meaning is 'DEFAULT'.
These meanings correspond to the Autocreate form field 'Grouping' which are described in the Purchasing Users Guide, AutoCreate page 6-13:
Default: Combine requisition lines for the same item, revision, line type, unit of measure, supplier item number, and transaction reason onto one purchase order line.
Requisition: Create Purchase Order with one purchase order line for one requisition line.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |