Some Peoplesoft Financials tables include a number of columns that are coming from different modules such as PO, AP, REQ. Commonly these transaction data are stored in modules' own specific tables, and a certain functions, such as Commitment Control, capture these transaction into a single table. In such case, the Commitment Control transaction table is defined with a column assigned for each type of the modules, such as VOUCHER_ID, PO_ID, REQ_ID, JOURNAL_ID etc.
The Search Key for such tables is defined by another auto-incrementing numeric column. This renders the key column meaningless. On a deliverered search page, user has to know beforehand what the unique key is in order to bring up the transaction.
