Search Results paq_pk

Overview

POS_ACNT_GEN_REQ is a transactional table in the Oracle E-Business Suite iSupplier Portal (POS) module that stores supplier bank account registration and change requests submitted through the iSupplier Portal self-service interface. It acts as the staging and tracking entity for bank account information that suppliers propose, which is subsequently reviewed and approved by the buying organization before being promoted to the operational payment records in Oracle Payments (IBY).

The table carries a single-column primary key, PAQ_PK, defined on ACCOUNT_REQUEST_ID, and is reinforced by the unique index POS_ACNT_GEN_REQ_U1 on the same column. From a heuristic Data Vault modeling perspective, this object leans toward a satellite classification: its foreign keys point outward to master and reference entities (POS_SUPPLIER_MAPPINGS, IBY_EXT_BANK_ACCOUNTS, IBY_TEMP_EXT_BANK_ACCTS), while dependent request detail tables attach to it, indicating it records descriptive request state rather than serving as a standalone hub or a pure link. Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support concurrency control and change tracking.

Key Information Stored

The documented schema exposes ten columns. The most significant are:

• ACCOUNT_REQUEST_ID — Surrogate primary key (PAQ_PK) and business-key candidate via unique index POS_ACNT_GEN_REQ_U1. Uniquely identifies each supplier bank account request.
• MAPPING_ID — Foreign key to POS_SUPPLIER_MAPPINGS, tying the request to the supplier-to-portal-user mapping that authored it.
• EXT_BANK_ACCOUNT_ID — Foreign key to IBY_EXT_BANK_ACCOUNTS, linking the request to an existing external bank account once approved or matched.
• TEMP_EXT_BANK_ACCT_ID — Foreign key to IBY_TEMP_EXT_BANK_ACCTS, pointing to the temporary/staging bank account record used while the request is in progress.
• OBJECT_VERSION_NUMBER — Optimistic locking token for concurrent update protection.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who-columns supporting audit and workflow attribution.

The distinction between EXT_BANK_ACCOUNT_ID and TEMP_EXT_BANK_ACCT_ID is central to the table's purpose: the former represents the finalized payment account, the latter the in-flight staging account during review.

Common Use Cases and Queries

Typical uses include tracking pending supplier bank account requests, auditing approval history, and reconciling portal-submitted accounts against Oracle Payments records. A representative query joins the request to its supplier mapping:

• List pending requests with supplier context: SELECT r.ACCOUNT_REQUEST_ID, r.MAPPING_ID, r.EXT_BANK_ACCOUNT_ID FROM POS.POS_ACNT_GEN_REQ r JOIN POS.POS_SUPPLIER_MAPPINGS m ON r.MAPPING_ID = m.MAPPING_ID;
• Identify staged versus live accounts: compare TEMP_EXT_BANK_ACCT_ID against EXT_BANK_ACCOUNT_ID to find requests not yet promoted.
• Audit activity windows: filter on CREATION_DATE or LAST_UPDATE_DATE to report request volumes per period.
• Detail expansion: join to POS_ACNT_ADDR_SUMM_REQ on ACCOUNT_REQUEST_ID for address summary detail attached to a request.

Related Objects

• POS_SUPPLIER_MAPPINGS — joined via MAPPING_ID; identifies the supplier registrant.
• IBY_EXT_BANK_ACCOUNTS — joined via EXT_BANK_ACCOUNT_ID; the approved external bank account.
• IBY_TEMP_EXT_BANK_ACCTS — joined via TEMP_EXT_BANK_ACCT_ID; temporary staging account.
• POS_ACNT_ADDR_SUMM_REQ — references this table via ACCOUNT_REQUEST_ID, holding address summary request detail.
• POS_ACNT_GEN_REQ_U1 / PAQ_PK — unique index and primary key enforcing request identity.

Together these objects form the iSupplier bank account request lifecycle, from submission through staging to final payment account creation.