Search Results az_selection_set_apis

Overview

AZ_SELECTION_SET_APIS is a table in the AZ (Application Implementation) product schema of Oracle E-Business Suite, documented as "Selection Set APIs Definition." It stores the definition and execution metadata for APIs that Oracle's Application Implementation module invokes against selection sets — the query criteria groups used when generating implementation-related output such as setup data extraction and comparison reports. Each row describes a specific API call associated with a job and an entity occurrence within a selection set.

From the mined foreign-key structure, the table is classified heuristically as standalone; it does not appear to be a dependent child in a documented hierarchical relationship. In Data Vault terms, this suggests a modeling as a hub or independent satellite-style record keyed by its composite business key, rather than a link between two parent hubs. This classification is a heuristic derived from the FK structure and should be treated as a modeling suggestion, not a documented constraint.

Key Information Stored

The table contains 11 documented columns in the ETRM 12.2.2 physical schema. The primary key, AZ_SELECTION_SET_APIS_PK, is a composite key defined on (JOB_NAME, ENTITY_OCCURANCE_CODE, SUBMITTED_BY). A unique index, AZ_SELECTION_SET_APIS_U1, is also defined on the same three columns, making it the strongest business-key candidate. Note that there is no separate single-column surrogate key; the composite primary key functions as the row identifier.

• JOB_NAME — identifies the job (concurrent program/process context) for which the API definition applies; part of the primary key and unique index.
• ENTITY_OCCURANCE_CODE — the entity occurrence within the selection set that the API targets; part of the primary key and unique index.
• SUBMITTED_BY — the submitter associated with the API definition; part of the primary key, unique index, and a common security/reporting filter.
• API_CODE — the identifier of the API being invoked against the selection set.
• EXECUTION_STATUS — tracks the processing state of the API for the job/entity combination.
• FILTERING_PARAMETER — input parameter controlling the filtering behavior of the API.
• CREATED_BY, CREATION_DATE — standard EBS audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS audit columns recording the most recent modifier and timestamp.
• LAST_UPDATE_LOGIN — the login/session identifier associated with the last update, used for audit traceability in EBS.

Common Use Cases and Queries

Typical scenarios include diagnosing why a selection-set job failed, auditing which submitter defined a given API, and reporting on execution status per job. Because SUBMITTED_BY is part of the composite key and a common search term, queries often filter on it directly.

• Retrieve all API definitions for a job and submitter:
  SELECT JOB_NAME, ENTITY_OCCURANCE_CODE, API_CODE, EXECUTION_STATUS
FROM AZ.AZ_SELECTION_SET_APIS
WHERE JOB_NAME = :job AND SUBMITTED_BY = :user;
• Status summary by job and API code for monitoring concurrent processing.
• Audit of changes using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.
• Parameter review by inspecting FILTERING_PARAMETER alongside API_CODE to understand filtering behavior.

Related Objects

The ETRM relationship data classifies this table as standalone, so no explicit foreign keys to parent tables are documented. The most significant relationships are implied by the composite key and by shared AZ schema conventions rather than declared constraints.

• AZ_SELECTION_SET_APIS_PK — the primary key constraint over (JOB_NAME, ENTITY_OCCURANCE_CODE, SUBMITTED_BY), the primary join path for any related selection-set job metadata.
• AZ_SELECTION_SET_APIS_U1 — the unique index over the same three columns; enforces the business-key candidate.
• AZ schema job/selection-set definition tables referenced by JOB_NAME and ENTITY_OCCURANCE_CODE.
• Concurrent program and request tables in the FND schema, joined via request identifiers that correspond to SUBMITTED_BY and job context.
• Standard EBS audit/security views that resolve CREATED_BY, LAST_UPDATED_BY, and SUBMITTED_BY to FND_USER.

Because documented FK relationships are limited, joins to these related objects are best validated against the actual AZ schema in the target environment before production use.