Results for “igs_ps_usec_accts”

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

Overview

The view IGS_PS_USEC_ACCTS belongs to the IGS (Student System) product family within Oracle E-Business Suite. It is documented in the ETRM repository against both Oracle EBS 12.1.1 and 12.2.2 releases. The IGS product line historically supported the Oracle Student System (OSS), a module that was never fully released as a production component in the standard EBS application stack and is now classified as obsolete in the ETRM metadata.

Functionally, IGS_PS_USEC_ACCTS is a multi-organization (MO) secured view. Its purpose is to expose usage account records — accounts associated with the usage of a Unit of Occupancy (UOO) — while automatically filtering rows by the organization identifier (ORG_ID) that is active for the current session. The view serves reporting and integration consumers who require organization-scoped access to usage account data without having to embed MO security predicates manually in each query.

An important caveat from the ETRM metadata is the statement "Not implemented in this database." This indicates that in the reference environment documented, the underlying objects do not exist, which is consistent with the obsolete status of the IGS Student System in recent EBS releases. The view definition is preserved for legacy reference.

Underlying Base Objects

The view is defined over a single base object: IGS_PS_USEC_ACCTS_ALL. The _ALL suffix follows the standard EBS multi-organization convention, where the _ALL table stores rows for every organization and a corresponding _ORG (or secured) view applies the operating unit filter.

The view selects an explicit column list from IGS_PS_USEC_ACCTS_ALL and applies a WHERE clause that compares the normalized ORG_ID value against the client information stored in the session. The predicate uses USERENV('CLIENT_INFO'), extracting the first characters of that value and converting them to a number, then wrapping both sides of the comparison in NVL(..., -99). This is the classic Oracle Applications row-level security (RLS) or MO filter pattern, ensuring that only rows belonging to the caller's current operating unit context are visible. The ETRM record documents no additional referenced base objects, so the dependency chain is a single table and its MO variant.

Key Columns

The view exposes the following columns, which mirror the underlying table structure:

• ROWID — The physical row identifier of the underlying table row.
• USEC_ACCOUNT_ID — Primary identifier for the usage account record.
• UOO_ID — Foreign key linking the account to its Unit of Occupancy.
• SEGMENT — The accounting segment name or identifier.
• SEGMENT_NUM — Numeric ordinal of the segment within the account structure.
• SEGMENT_VALUE — The actual value assigned to that segment.
• ORG_ID — Organization identifier used for multi-organization security partitioning.
• CREATED_BY, CREATION_DATE — Standard EBS audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent modification.

Together these columns represent the decomposition of an accounting flexfield into its constituent segments for a given usage account, keyed to an occupancy entity.

Common Use Cases and Queries

The principal use case is organization-scoped reporting on usage account segment assignments. Because the view enforces MO filtering automatically, it is typically queried directly without additional ORG_ID predicates. A representative query follows:

• SELECT usec_account_id, uoo_id, segment, segment_value, org_id FROM igs_ps_usec_accts WHERE uoo_id = :p_uoo_id; — retrieve all segment assignments for a specific unit of occupancy.
• SELECT uoo_id, COUNT(*) FROM igs_ps_usec_accts GROUP BY uoo_id; — count usage account segments per occupancy entity within the current organization.
• SELECT * FROM igs_ps_usec_accts WHERE segment = :p_segment AND segment_value = :p_value; — locate usage accounts that reference a particular segment value.

Before relying on any of these queries in a live environment, confirm that IGS_PS_USEC_ACCTS_ALL and IGS_PS_USEC_ACCTS actually exist. Given the obsolete designation and the ETRM note that the object is not implemented, the view should be treated as legacy documentation rather than an active integration surface in EBS 12.1.1 or 12.2.2.