Aid To Understanding How Purchasing Tests Elements Of A Purchasing Document Against Approval Rule (Doc ID 1527136.1)

Last updated on JUNE 15, 2019

Applies to:

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

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:

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.