Search Results pos_acnt_addr_s_u1

Overview

The POS.POS_ACNT_ADDR_SUMM_REQ table is a supplier bank account and address assignment request entity within the Oracle E-Business Suite Procurement (POS) schema. It stores the details of assignment requests that link supplier bank accounts and remit-to addresses to specific business purposes, operating as a child table of POS_ACNT_ADDR_REG. In EBS release 12.1.1 and 12.2.2, this table supports the Supplier Banking and Payments (IBY) integration flow, where assignment summaries capture which bank accounts and addresses are active for a supplier, site, or payment process at any given point in time.

From a heuristic Data Vault modeling perspective, the table exhibits characteristics of a link table. Its primary key is a surrogate (ASSIGNMENT_ID) rather than a natural business key, and it carries multiple foreign key references that connect suppliers, bank accounts, address requests, and assignment requests. The presence of START_DATE, END_DATE, ASSIGNMENT_STATUS, and PRIORITY indicates the table also functions as an effectivity-bearing relationship, tracking the temporal validity of each assignment.

Key Information Stored

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

• ASSIGNMENT_ID — The surrogate primary key (POS_ACNT_ADDR_SUMM_REQ_PK) and the column underlying the unique business-key candidate index POS_ACNT_ADDR_S_U1. It uniquely identifies each assignment record.
• ASSIGNMENT_REQUEST_ID — Foreign key to POS_ACNT_ADDR_REQ, identifying the parent assignment request that generated this summary row. Indexed non-uniquely through POS_ACNT_ADDR_S_N1.
• ACCOUNT_REQUEST_ID — Foreign key to POS_ACNT_GEN_REQ, linking the assignment to the originating account generation request.
• EXT_BANK_ACCOUNT_ID — Foreign key to IBY_EXT_BANK_ACCOUNTS, identifying the external supplier bank account being assigned.
• ASSIGNMENT_STATUS — A VARCHAR2(30) field capturing the lifecycle state of the assignment (for example, active, pending, or cancelled).
• PRIORITY — Numeric priority used to rank assignments when multiple records apply to the same supplier or site.
• START_DATE and END_DATE — Define the active window during which the assignment is valid.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent update control.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide audit lineage.

Common Use Cases and Queries

Typical reporting scenarios include identifying active bank account assignments for a supplier, reconciling assignment requests against generated accounts, and auditing temporal gaps in effectivity windows. A representative query retrieving active assignments joined to their parent request is:

• SELECT a.ASSIGNMENT_ID, a.ASSIGNMENT_STATUS, a.PRIORITY, a.START_DATE, a.END_DATE, a.EXT_BANK_ACCOUNT_ID FROM POS.POS_ACNT_ADDR_SUMM_REQ a WHERE a.ASSIGNMENT_STATUS = 'ACTIVE' AND SYSDATE BETWEEN a.START_DATE AND NVL(a.END_DATE, SYSDATE + 1);
• Join patterns frequently link to POS_ACNT_ADDR_REQ via ASSIGNMENT_REQUEST_ID and to IBY_EXT_BANK_ACCOUNTS via EXT_BANK_ACCOUNT_ID to resolve account numbers and supplier identifiers.
• Priority-based reporting orders results by PRIORITY to determine which assignment prevails when overlapping records exist.

Related Objects

The following objects are the most significant partners to this table, based on documented foreign key and dependency data:

• POS.POS_ACNT_ADDR_REQ — Parent assignment request table; joined on ASSIGNMENT_REQUEST_ID.
• POS.POS_ACNT_GEN_REQ — Account generation request; joined on ACCOUNT_REQUEST_ID.
• IBY.IBY_EXT_BANK_ACCOUNTS — External bank account master; joined on EXT_BANK_ACCOUNT_ID.
• POS.POS_ACNT_ADDR_REG — Parent registration table referenced in the documented dependency information.
• POS.POS_ACNT_ADDR_SUMM_REQ# — The companion object listed as referencing this table, typically associated with editioning or change-tracking behavior.

Administrators and developers querying the POS_ACNT_ADDR_S_U1 index should note that it enforces uniqueness on ASSIGNMENT_ID, making it the canonical access path for single-record lookups.