Results for “occupational_title”

23 results




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

Overview

IGS_PS_DIC_OCC_TITLS is a dictionary (lookup) table within the Oracle E-Business Suite Student System (IGS) product family. As its name implies, the object belongs to the "DIC" (dictionary/reference data) naming convention used throughout the IGS schema, and it stores the set of occupational titles that a student may be assigned or recognised as having attained upon passing from the university. In practical terms it functions as a controlled vocabulary of job or profession titles that downstream student records can reference by a short coded value rather than free text, preserving consistency across transcripts, graduate outcome reporting, and destination surveys.

The ETRM metadata explicitly marks this object as not implemented in this database for the documented release, and the product line itself is classified as "IGS – Student System (Obsolete)". This means the table is documented for historical and migration purposes only; it does not physically exist in a standard 12.1.1 or 12.2.2 installation. Any reference to it should be treated as legacy metadata rather than a live object.

From a modelling perspective, the mined Data Vault classification is hub-leaning. The table carries a single-column primary key on OCCUPATIONAL_TITLE_CODE and is referenced by other tables rather than acting as a transactional accumulator. This suggests it behaves as a hub-like reference entity: a stable, business-key-oriented list of occupational title codes that other objects resolve against.

Key Information Stored

The documented physical schema shows eight columns owned by the IGS schema. The most significant are:

Importantly, there is no separate surrogate numeric key documented here. The occupational title code serves simultaneously as primary key and business key, which is characteristic of a small dictionary entity. The absence of effective-dating columns (start/end dates) further indicates this is a static reference list rather than a dated satellite.

Common Use Cases and Queries

Because the table is obsolete and not implemented, the primary practical uses are legacy support, upgrade impact analysis, and data-migration scoping. Typical activities include confirming whether a customisation or interface references the object before an upgrade, and mapping legacy occupational title codes to a replacement destination. A representative lookup pattern would be:

  • Joining IGS_PS_OCCUP_TITLES_ALL to IGS_PS_DIC_OCC_TITLS on OCCUPATIONAL_TITLE_CODE to resolve a stored code to its descriptive title.
  • Reporting distinct occupational titles for graduate outcome or destination-of-leavers analysis.
  • Validating incoming data loads against the dictionary's unique code list to reject unrecognised titles.

A sample join would select the code and title from the dictionary and match it to the referencing table's code column, filtering on the occupational title for readability. Auditing queries would inspect CREATED_BY and LAST_UPDATED_BY to trace who maintained the reference data.

Related Objects

The FK relationship data identifies the principal dependent object:

  • IGS_PS_OCCUP_TITLES_ALL — references this table via OCCUPATIONAL_TITLE_CODE, forming the documented foreign-key dependency. This is the most significant related object.
  • IGS_PS_DIC_OCC_TITLS_PK — the primary key constraint enforcing code uniqueness.
  • IGS_PS_DIC_OCC_TITLS_U1 — the unique index on OCCUPATIONAL_TITLE_CODE, confirming the business key.

Beyond these documented relationships, other IGS dictionary-style tables (for example related title or outcome reference objects) tend to follow the same design pattern, but only IGS_PS_OCCUP_TITLES_ALL is confirmed by the supplied metadata as a referencing object.