Search Results eng_subjects_b




Overview
Explore in AI Chat

Overview

ENG.SUBJECTS_B (commonly referenced as ENG_SUBJECTS_B) is a base table in the Oracle E-Business Suite Engineering (ENG) product family. According to the ETRM 12.2.2 documentation, the table stores subject information, and its operational role centers on defining the navigable subject entries that drive the Oracle EBS Framework-based user interface within Engineering flows. In EBS, a "subject" typically represents a functional or transactional theme that the framework uses to resolve where a user should be routed for create, edit, or view actions — the CREATE_REGION_URL, EDIT_REGION_URL, and VIEW_REGION_URL columns exist precisely for this routing purpose. The table is owned by the ENG schema and is documented as VALID with 12 columns.

On the Data Vault modeling heuristic mined from the foreign-key structure, this object is classified as standalone. In other words, it does not behave as a conventional hub, link, or satellite — its single documented outbound foreign key (SUBJECT_ID → IGS_UC_COM_EBL_SUBJ) points to an external reference rather than to a parent in a normalized ENG hierarchy. A modeling exercise would therefore treat ENG_SUBJECTS_B as a self-contained reference/dimension table, with its unique key as the natural business key.

Key Information Stored

The most significant columns fall into three groups.

  • Identity: SUBJECT_ID is the surrogate primary-key component and also the column participating in the documented outbound FK to IGS_UC_COM_EBL_SUBJ. SUBJECT_INTERNAL_NAME is the human-readable internal label used to look up a subject programmatically.
  • Business key: the unique index ENG_SUBJECTS_B_U1 covers (SUBJECT_ID, ZD_EDITION_NAME), making this pair the documented business-key candidate. ZD_EDITION_NAME enables edition-based redefinition and multi-edition coexistence of subject definitions.
  • Framework behavior: CREATE_REGION_URL, EDIT_REGION_URL, and VIEW_REGION_URL store the target region endpoints invoked for each action; SUBJECT_ACTION records the action context associated with the subject.
  • Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow the standard EBS WHO-column conventions and support change auditing and concurrency tracking.

Common Use Cases and Queries

Typical usage includes resolving the region URL for a given subject, joining subject definitions to the external IGS_UC_COM_EBL_SUBJ reference to obtain descriptive context, and auditing changes to routing definitions. Because the table participates in edition-based redefinition, queries against the current edition should filter on ZD_EDITION_NAME.

  • Look up a routing target by internal name: SELECT subject_internal_name, create_region_url, edit_region_url, view_region_url FROM eng.eng_subjects_b WHERE subject_internal_name = :name AND zd_edition_name = :edition;
  • Enumerate all subjects with their external reference: SELECT s.subject_id, s.subject_internal_name, c.* FROM eng.eng_subjects_b s JOIN igs_uc_com_ebl_subj c ON s.subject_id = c.subject_id;
  • Change audit: SELECT subject_id, last_update_date, last_updated_by FROM eng.eng_subjects_b WHERE last_update_date >= :since ORDER BY last_update_date DESC;

These patterns are useful for extension development, personalization debugging, and reverse-engineering which region a user is directed to when a subject is triggered.

Related Objects

  • IGS_UC_COM_EBL_SUBJ — referenced by ENG_SUBJECTS_B.SUBJECT_ID; the principal documented foreign key and the natural join partner for descriptive subject data.
  • ENG_SUBJECTS_B_U1 — the unique index enforcing the (SUBJECT_ID, ZD_EDITION_NAME) business key; important for any upsert or merge logic.
  • Oracle EBS Framework region/URL resolution components — consume CREATE_REGION_URL, EDIT_REGION_URL, and VIEW_REGION_URL to navigate users.
  • Standard EBS WHO/audit access views and concurrent programs that maintain subject definitions, which read and write the audit columns.
  • Edition-based redefinition infrastructure that manages ZD_EDITION_NAME values across editions.

Because the ETRM metadata classifies this table as standalone with a single documented FK, related-object dependencies beyond IGS_UC_COM_EBL_SUBJ are largely interface-driven rather than referential, and should be confirmed against the deployed 12.1.1 or 12.2.2 instance before reliance in custom code.