Search Results az_selection_set_apis_u1

Overview

The AZ.AZ_SELECTION_SET_APIS table is an Oracle Application Object Library (AZ schema) repository table that records which Application Programming Interfaces (APIs) are bundled into each selection set used by the iSetup Migrator utility. iSetup is the Oracle E-Business Suite framework that allows administrators to extract, migrate, and compare configuration and reference data between environments, and selection sets define the scope of entities and APIs that a given migration job operates against. This table therefore acts as the operational ledger linking a migration job to the specific API handlers invoked for each entity occurrence within that job.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as standalone, meaning it exhibits no enforced parent-child dependencies on other tables within the schema and does not itself act as a parent to related child tables. In Data Vault terms this suggests a self-contained satellite-like structure whose natural business key is composite (job, entity occurrence, and submitting user), rather than a hub or link participating in a broader integration bus. The object is owned by the AZ schema with FND design data registered as AZ.AZ_SELECTION_SET_APIS, and it resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, consistent with transactional configuration data.

Key Information Stored

The table contains eleven documented columns, with the physical primary key AZ_SELECTION_SET_APIS_PK defined on the composite of JOB_NAME, ENTITY_OCCURANCE_CODE, and SUBMITTED_BY. A unique index, AZ_SELECTION_SET_APIS_U1, mirrors this same column combination in the APPS_TS_TX_IDX tablespace, confirming it as the business-key candidate. The most operationally significant columns include:

• JOB_NAME (VARCHAR2, 45) — identifies the iSetup migration or extraction job to which the API entry belongs.
• ENTITY_OCCURANCE_CODE (VARCHAR2, 45) — denotes the specific entity occurrence processed within the job, allowing multiple occurrences per job.
• SUBMITTED_BY (NUMBER, 15) — the user ID of the individual who submitted the job, providing security and auditing context.
• API_CODE (VARCHAR2, 45) — the identifier of the API invoked for the referenced entity occurrence.
• EXECUTION_STATUS (VARCHAR2) — the runtime status of the API's execution, used to track success, failure, or in-progress conditions.
• FILTERING_PARAMETER (LONG) — holds filtering parameter data, allowing selection sets to restrict the records returned or processed.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — provide the standard Oracle audit trail.

Common Use Cases and Queries

Typical use cases include auditing which APIs were executed for a given iSetup migration job, diagnosing failures by inspecting EXECUTION_STATUS, and reconciling selection set contents before re-running a migration. A representative query to list APIs and their statuses for a specific job is:

• SELECT API_CODE, ENTITY_OCCURANCE_CODE, EXECUTION_STATUS FROM AZ.AZ_SELECTION_SET_APIS WHERE JOB_NAME = :job AND SUBMITTED_BY = :user_id;
• Filtering by EXECUTION_STATUS to isolate failed API invocations during troubleshooting.
• Joining against user tables via SUBMITTED_BY to attribute job activity to specific administrators.

Related Objects

The documented dependency metadata indicates that AZ.AZ_SELECTION_SET_APIS does not reference any database object and is referenced only by the APPS synonym AZ_SELECTION_SET_APIS. No foreign-key relationships to other EBS tables are enforced, consistent with its standalone Data Vault classification. In practice, related iSetup objects include the selection set definition tables and the concurrent job tables that populate JOB_NAME and SUBMITTED_BY, but the ETRM record confirms a self-contained structure with only the APPS synonym as a formal dependent object.