Results for “segment_value_desc”

22 results




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

Overview

The database view IGS_PS_UNIT_ACCTS_V belongs to the Oracle Student System (IGS) product family, which is documented as obsolete in the E-Business Suite 12.1.1 and 12.2.2 releases. The view exposes account segment values associated with a Unit, where a Unit represents an academic organizational entity such as a department, faculty, or teaching unit within the Student System. Its stated description is "Account segment values for a Unit," indicating that the view serves as a consolidated access point for General Ledger-style accounting segment information attached to units.

In EBS reporting and integration contexts, this view would have been used to retrieve the accounting flexfield segment assignments for a given unit code and version. Rather than querying the underlying unit account table directly, external reports, concurrent programs, or integration interfaces could select from this view to obtain both the stored segment values and their human-readable descriptions, resolved through the Accounting Flexfield value set definitions. The view joins unit account records to account segment metadata, making it convenient for reporting scenarios where the descriptive name of each segment must be presented alongside its stored value.

Underlying Base Objects

The view text references two source objects. The primary transactional object is IGS_PS_UNIT_ACCTS (aliased PSUA), which stores the unit-level account segment values keyed by row identifier, unit account identifier, unit code, and version number. The second object is IGS_FI_ACCT_SEGS_V (aliased ACCSEG), which supplies segment-level metadata including the segment name, segment number, flex value set identifier, validation type, independent segment number, and display flag.

The join is expressed with outer-join syntax (PSUA.SEGMENT(+) and PSUA.SEGMENT_NUM(+)), meaning that segment definitions from IGS_FI_ACCT_SEGS_V are retained even where no corresponding unit account value exists. This is significant for complete reporting, since segments without assigned values still appear with null segment values. The result set is ordered by segment number, producing a predictable sequence that mirrors the accounting flexfield structure.

Key Columns

Common Use Cases and Queries

The view would typically support reporting on which accounting segments and values are configured for a given academic unit and version. A representative query retrieves the segment order, name, value, and resolved description for a specific unit:

  • SELECT segment_num, segment_name, segment_value, segment_value_desc FROM igs_ps_unit_accts_v WHERE unit_cd = :unit_code AND version_number = :version ORDER BY segment_num;
  • Filtering by org_id to restrict results to a single operating unit when multi-org access is in effect.
  • Joining the view to other IGS unit or finance integration objects using unit_cd and version_number to correlate unit definitions with their accounting segment assignments.

Because the product is obsolete and the view is documented as not implemented in the reference database, these queries should be treated as illustrative of the view's intended shape rather than as verified execution against a live 12.2.2 instance. Where the object is absent, equivalent data would be sourced from the underlying IGS_PS_UNIT_ACCTS and IGS_FI_ACCT_SEGS_V objects directly, applying the same outer-join and segment-number ordering logic.