Aid To Understanding How Purchasing Tests Elements Of A Purchasing Document Against Approval Rule
(Doc ID 1527136.1)
Last updated on MARCH 29, 2022
Applies to:
Oracle Purchasing - Version 12.1.3 and laterInformation in this document applies to any platform.
Goal
When a Purchasing document is submit for approval, the elements that are to be tested against the approval rules are placed in to a temporary table called PO_SESSION_GT
Column | Comment |
---|---|
num1 |
unit total for most checks |
num2 |
unit total for item/cat limit checks for PAs only |
num3 |
code combination id (for account limit check) |
num4 |
location id (for location check) |
num5 |
item_id (for item check) |
num6 |
category_id (for category check) |
char1 |
cancel_flag |
char2 |
closed_code |
The code that populates PO_SESSION_GT and performs the approval checks is contained in the package PO_DOCUMENT_ACTION_CHECK that is the file POXDACKB.pls
The approval rules that are tested are dependent on the type of document:
Document Type | Document Subtype | check_accounts | check_items | check_item_categories | check_locations | check_doc_totals |
---|---|---|---|---|---|---|
REQUISITION |
TRUE |
TRUE |
TRUE |
TRUE |
TRUE |
|
PO |
TRUE |
TRUE |
TRUE |
TRUE |
TRUE |
|
RELEASE |
TRUE |
TRUE |
TRUE |
TRUE |
TRUE |
|
PA |
BLANKET |
FALSE |
TRUE |
TRUE |
FALSE |
TRUE |
PA |
CONTRACT |
FALSE |
FALSE |
FALSE |
FALSE |
TRUE |
The purpose of this document is to provide SQL that returns the data that is populated in to PO_SESSION_GT so to gain a better understanding as to what the element values are that are being tested.
The SQL that follows is taken from the package PO_DOCUMENT_ACTION_CHECK
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 |