Search Results pos_acnt_addr_summ_req_pk

Overview

POS_ACNT_ADDR_SUMM_REQ is a transactional table in the POS (iSupplier Portal) schema of Oracle E-Business Suite, present and validated in both 12.1.1 and 12.2.2. It stores the details of supplier bank account and address assignment requests — the summary-level records that reconcile a supplier's request to assign a bank account or address to a specific operating context. In the supplier lifecycle, suppliers submit account and address registration requests through iSupplier Portal; once the underlying detail requests are captured, this table provides the summarization layer that links a given assignment request to the external bank account and to the originating account-generation request.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link: it holds the relationships between an assignment request, an external bank account, and an account request, rather than acting as a standalone hub or a descriptive satellite. This classification is a heuristic derived from the FK topology and should be treated as a modeling suggestion, since the table also carries descriptive status and date attributes.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• ASSIGNMENT_ID — the surrogate primary key, enforced by POS_ACNT_ADDR_SUMM_REQ_PK and the unique index POS_ACNT_ADDR_S_U1. This is the business-key candidate exposed by the unique index and uniquely identifies each summary assignment record.
• ASSIGNMENT_REQUEST_ID — foreign key to POS_ACNT_ADDR_REQ; identifies the parent address/account assignment request from which this summary row derives.
• ACCOUNT_REQUEST_ID — foreign key to POS_ACNT_GEN_REQ; links the summary to the originating account-generation request.
• EXT_BANK_ACCOUNT_ID — foreign key to IBY_EXT_BANK_ACCOUNTS; the external bank account being assigned.
• ASSIGNMENT_STATUS — the workflow or processing state of the assignment request (for example, pending, approved, rejected).
• PRIORITY — relative processing priority of the request.
• START_DATE and END_DATE — the effective window during which the assignment applies.
• OBJECT_VERSION_NUMBER — optimistic-locking version column used by the Oracle framework.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit and concurrency columns populated by the application.

Note that the surrogate ASSIGNMENT_ID is distinct from ASSIGNMENT_REQUEST_ID, which is the business-level request identifier inherited from the parent table.

Common Use Cases and Queries

Typical uses include supplier-registration reporting, assignment approval tracking, and reconciliation of bank account assignments against their originating requests. A common pattern joins the summary up to its parent request and down to the external bank account:

• Retrieve all assignments with their status and effective dates for a supplier: query POS_ACNT_ADDR_SUMM_REQ filtering on ASSIGNMENT_STATUS and START_DATE/END_DATE.
• Reconcile to the parent request: join POS_ACNT_ADDR_SUMM_REQ.ASSIGNMENT_REQUEST_ID to POS_ACNT_ADDR_REQ.
• Locate the assigned bank account: join EXT_BANK_ACCOUNT_ID to IBY_EXT_BANK_ACCOUNTS.
• Trace back to the originating account request via ACCOUNT_REQUEST_ID to POS_ACNT_GEN_REQ.
• Detect stale or duplicate assignments by grouping on ASSIGNMENT_REQUEST_ID and EXT_BANK_ACCOUNT_ID.

A representative query: SELECT s.ASSIGNMENT_ID, s.ASSIGNMENT_STATUS, s.START_DATE, s.END_DATE FROM POS.POS_ACNT_ADDR_SUMM_REQ s WHERE s.ASSIGNMENT_REQUEST_ID = :req_id;

Related Objects

• POS_ACNT_ADDR_REQ — parent request table; joined via ASSIGNMENT_REQUEST_ID.
• POS_ACNT_GEN_REQ — account-generation request; joined via ACCOUNT_REQUEST_ID.
• IBY_EXT_BANK_ACCOUNTS — external bank account master; joined via EXT_BANK_ACCOUNT_ID.
• IBY_PAYEE and related IBY payment objects that consume assignment results.
• POS_ACNT_ADDR_SUMM_REQ_PK / POS_ACNT_ADDR_S_U1 — the primary key constraint and unique index enforcing ASSIGNMENT_ID.