Results for “eng_subjects_b_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ENG.ENG_SUBJECTS_B is a seed table in the Oracle E-Business Suite Engineering (ENG) schema that stores subject information used by the EBS notification and workflow subscription framework. In Oracle EBS 12.1.1 and 12.2.2, "subjects" define the business events and objects that users can subscribe to, and this table holds the internal identity, display naming, and navigation URLs associated with each subject. The table resides in the APPS_TS_SEED tablespace, reflecting its role as a seeded, relatively static configuration object rather than a high-volume transactional table.

From a heuristic Data Vault modeling perspective, the metadata classifies ENG.ENG_SUBJECTS_B as a standalone object. This suggests treating it as a hub-like reference entity, where SUBJECT_ID serves as the durable business key and the descriptive attributes (internal name, region URLs, and subject action) behave like satellite attributes. Because the table has no outbound foreign keys of its own, it acts as an anchor point rather than a dependent child in the surrounding dependency graph.

Key Information Stored

The table's documented structure contains twelve columns, several of which are standard WHO audit columns. The most significant columns are:

• SUBJECT_ID — the numeric surrogate primary key and subject internal identifier; it is the leading column of the unique index ENG_SUBJECTS_B_U1 and the primary join key to dependent objects.
• SUBJECT_INTERNAL_NAME — a VARCHAR2(30) business-key candidate holding the human-readable internal name of the subject; combined with the edition column, it uniquely identifies a subject in the documented 12.2.2 schema.
• SUBJECT_ACTION — a VARCHAR2(30) field indicating the action the subject refers to, such as attribute changes or attachment changes.
• CREATE_REGION_URL, EDIT_REGION_URL, VIEW_REGION_URL — VARCHAR2(240) columns holding the URLs to the create, edit, and view pages for the subject, enabling the framework to route users to the correct region.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking row creation and modification.
• ZD_EDITION_NAME — the editioning column present in the 12.2.2 documented schema; it participates in the business-key uniqueness of ENG_SUBJECTS_B_U1.

The unique index ENG_SUBJECTS_B_U1 enforces uniqueness on SUBJECT_ID (and, in 12.2.2, SUBJECT_ID plus ZD_EDITION_NAME), confirming SUBJECT_ID as the surrogate key while SUBJECT_INTERNAL_NAME acts as the principal business-key candidate.

Common Use Cases and Queries

Typical applications of this table include reporting on configured subjects, auditing which subjects exist in a given environment, and diagnosing notification or subscription misconfiguration. Because the table is seeded, administrators frequently query it to locate the SUBJECT_ID required for joining to subscription or workflow metadata tables.

A basic lookup retrieves the subject identity and its navigation URLs:

• SELECT SUBJECT_ID, SUBJECT_INTERNAL_NAME, SUBJECT_ACTION FROM ENG.ENG_SUBJECTS_B;
• SELECT SUBJECT_ID, CREATE_REGION_URL, EDIT_REGION_URL, VIEW_REGION_URL FROM ENG.ENG_SUBJECTS_B WHERE SUBJECT_INTERNAL_NAME = :name;
• SELECT SUBJECT_ID, SUBJECT_INTERNAL_NAME FROM ENG.ENG_SUBJECTS_B WHERE SUBJECT_ACTION = 'ATTRIBUTE_CHANGE';

In 12.2.2 editioned environments, queries should include ZD_EDITION_NAME when resolving the current edition. Joining SUBJECT_ID to downstream subscription records allows reporting on which subjects are actively subscribed and which target regions are invoked.

Related Objects

The FK/PK relationship data identifies the following significant dependencies:

• IGS_UC_COM_EBL_SUBJ — the documented foreign-key relationship maps ENG_SUBJECTS_B.SUBJECT_ID to this table, meaning IGS_UC_COM_EBL_SUBJ references or relates via SUBJECT_ID as the join column.
• APPS.ENG_SUBJECTS_B — the synonym or view layer exposing the seed table under the APPS schema, which is the standard access path for application code and concurrent programs.

Because the ETRM excerpt shows no additional explicit referrers, the principal dependency surface is the EBS notification/subscription framework itself, which consumes SUBJECT_ID, SUBJECT_INTERNAL_NAME, and the three region URLs to drive user navigation. No outbound foreign keys are documented on ENG_SUBJECTS_B, consistent with its classification as a standalone reference entity.