Search Results as_issues_b_pk

Overview

AS_ISSUES_B is the base table for the Issues entity within the Oracle E-Business Suite AS – Sales Foundation product family. The table resides in the OSM schema and is classified as VALID in the ETRM 12.1.1 / 12.2.2 data dictionary. It stores the master definition of an issue, which is the core inbound record that drives funds capture processing — the granting of credit or payment commitments associated with a party, sector, and issue type. Every downstream authorization, settlement, and funds disbursement transaction ultimately traces back to a row in this table.

From a dimensional modelling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. No parent hubs are referenced by foreign key other than the security group. This suggests the table behaves as an independent entity rather than a pure hub, link, or satellite; analysts treating it as a hub should note that it carries its own descriptive attributes plus WHO-columns, effectively merging hub and satellite semantics.

Key Information Stored

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

• ISSUE_ID — surrogate primary key, backed by the unique index AS_ISSUES_B_U1 and the primary key constraint AS_ISSUES_B_PK. All child tables join on this column.
• ISSUE_TYPE — discriminator that classifies the nature of the issue record.
• SECTOR — the operational sector or category to which the issue belongs.
• PARTY_ID — the trading partner or party associated with the issue; typically resolves to HZ_PARTIES.
• SECURITY_GROUP_ID — multi-tenant / data-security grouping; the sole documented foreign key, referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J layer to detect concurrent updates.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
• Flexfield support: ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15, providing the DFF segment store for customer-specific extensions.

ISSUE_ID is the true surrogate key; there is no separately documented business-key unique index beyond the primary key itself.

Common Use Cases and Queries

Typical reporting scenarios include retrieving issues for a given party, auditing issue creation during a period, and tracing settlements back to their originating issue.

SELECT i.issue_id, i.issue_type, i.sector, i.party_id, i.creation_date
FROM   as_issues_b i
WHERE  i.security_group_id = :p_security_group
AND    i.party_id = :p_party_id
ORDER BY i.creation_date DESC;

To reconcile funds against issues, join the child funds table:

SELECT i.issue_id, f.funds_id, f.amount
FROM   as_issues_b i, as_funds_b f
WHERE  i.issue_id = f.issue_id;

DFF-based reporting can pivot on ATTRIBUTE_CATEGORY while WHO columns support change-audit reporting.

Related Objects

• AS_ISSUE_LISTING_IDFR — references AS_ISSUES_B.ISSUE_ID via its own ISSUE_ID; holds listing identifiers for the issue.
• AS_FUNDS_B — references AS_ISSUES_B.ISSUE_ID; the base funds capture record tied to the issue.
• FND_SECURITY_GROUPS — parent of AS_ISSUES_B.SECURITY_GROUP_ID; enforces row-level security grouping.
• AS_ISSUES_TL — the translatable attributes table companion to the _B base table, joined on ISSUE_ID.
• HZ_PARTIES — logical parent resolved through PARTY_ID for party name and profile data.

Together these objects form the issue-to-funds-to-identifier chain that underlies Sales Foundation funds capture processing.