Results for “segment12_high”

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

Overview

The Oracle EBS view APPS.IGI_ITR_CHARGE_RANGE_AUTH_SS_V is a public-sector financials object delivered with the IGI – Public Sector Financials International product. It is a stored, VALID view sitting in the APPS schema and is classified as a Self-Service (SS) presentation view, as indicated by the _SS_V suffix. Its functional purpose is to expose charge range authorisation records — specifically the low and high bounds of an accounting flexfield segment range assigned to an authoriser — in a form suitable for an Oracle Forms self-service UI or an OAF-based page.

The view joins charge range authorisation rows to the application user repository so that an authorising employee's login name can be rendered directly without a secondary lookup. It therefore serves both display and data-integration roles: reporting extracts, personalisations, and custom self-service pages can query the view rather than joining the base tables independently. Because the segment columns are flattened into the view, a user searching for a specific column such as segment30_high will find it here as SEGMENT30_HIGH, the thirty-first (highest numbered) key flexfield segment's upper bound.

Underlying Base Objects

The documented ETRM metadata identifies two referenced base objects, both accessed through synonyms in the APPS schema:

• IGI_ITR_CHARGE_RANGES – the principal transaction table holding charge center, charge range, authoriser, employee, active flag, and the SEGMENTn_LOW / SEGMENTn_HIGH range definitions. This is the driving table of the view (aliased A).
• FND_USER – the Oracle Applications user repository, providing USER_NAME. The view aliases it F and uses it to derive PERSON_NAME_DSP.

The relationship is a join between the charge range authorisation row and the corresponding FND_USER record, allowing the authoriser's user name to be presented alongside the numeric range limits. The view additionally exposes ROW_ID (the base row's ROWID), which is commonly used by self-service frameworks for optimistic locking and row identification.

Key Columns

• ROW_ID – ROWID of the underlying IGI_ITR_CHARGE_RANGES row; used for row-level identification in the UI.
• CHARGE_CENTER_ID, CHARGE_RANGE_ID – foreign keys identifying the charge center and its associated charge range.
• AUTHORISER_ID, EMPLOYEE_ID – the authorising party and the associated employee.
• ACTIVE_FLAG – indicates whether the authorisation range is currently active.
• PERSON_NAME_DSP – display name sourced from FND_USER.USER_NAME.
• SEGMENT1_LOW … SEGMENT30_LOW – the lower bound of each key flexfield segment in the authorised range.
• SEGMENT1_HIGH … SEGMENT30_HIGH – the corresponding upper bound. SEGMENT30_HIGH is the highest-numbered such column documented, representing the upper limit of the thirtieth segment as defined on the charge range.

The LOW/HIGH pairing permits range-based comparison logic, for example determining whether a given accounting flexfield combination falls within an authoriser's permitted span.

Common Use Cases and Queries

Typical scenarios include validating whether a transaction's accounting combination lies within an authoriser's approved charge range, and building self-service maintenance pages that present authorisers with their own ranges. A representative query returning the active authorisation ranges for a given authoriser, including the segment 30 upper bound, is:

• SELECT AUTHORISER_ID, CHARGE_CENTER_ID, CHARGE_RANGE_ID, SEGMENT1_LOW, SEGMENT1_HIGH, SEGMENT30_LOW, SEGMENT30_HIGH, PERSON_NAME_DSP FROM APPS.IGI_ITR_CHARGE_RANGE_AUTH_SS_V WHERE ACTIVE_FLAG = 'Y' AND AUTHORISER_ID = :p_authoriser_id;
• A reporting variant filters on the range limits to test containment, substituting the relevant SEGMENTn_LOW / SEGMENTn_HIGH pair for the segment being validated.
• A self-service lookup joins PERSON_NAME_DSP to display the authoriser identity, relying on the view's pre-built FND_USER join rather than re-joining it manually.

Because the view flattens all thirty segment low/high pairs, it is well suited to generic, data-driven pages where the active segment count is not known at design time.