Search Results facility_description

Overview

The view IGS_PS_USO_FACILITY_V belongs to the IGS — Student System product family in Oracle E-Business Suite and is owned by the APPS schema. Its status is documented as VALID in ETRM for both 12.1.1 and 12.2.2. The view exposes the association between a unit section occurrence and the physical facility (media equipment) assigned to it, resolving the stored FACILITY_CODE into a human-readable FACILITY_DESCRIPTION. This decoded description is the element most commonly searched for under the term facility_description, and it is the principal reason the view is queried rather than the underlying base table.

The view is a denormalized, reporting-oriented construct. It does not store data; it projects filtered and joined data from the transactional scheduling model so that reports, concurrent programs, and integrations can surface descriptive facility text alongside the scheduling keys without reproducing the join logic. Because it is a view, it inherits the security and privileges of the APPS schema and is typically accessed through the standard Oracle EBS responsibility and menu structures or through custom reporting layers.

Underlying Base Objects

The view is defined over two base objects:

• IGS_PS_USO_FACILITY — aliased USF. This is the transactional table holding the assignment of a facility code to a unit section occurrence.
• IGS_PS_MEDIA_EQUIP — aliased ME. This is the reference table containing the media/equipment master, including the descriptive text.

The join condition is USF.FACILITY_CODE = ME.MEDIA_CODE. It is an inner join, so rows in IGS_PS_USO_FACILITY whose facility code has no matching media code are excluded from the result set. The view therefore returns one row per qualifying facility assignment. No additional filters, decoded lookups, or WHERE predicates beyond the equijoin are present in the documented view text.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_PS_USO_FACILITY row; useful for identifying the base row in DML or diagnostics.
• USO_FACILITY_ID — primary identifier of the facility assignment record.
• UNIT_SECTION_OCCURRENCE_ID — foreign key linking the assignment to the scheduled unit section occurrence; the principal scheduling context.
• FACILITY_CODE — the stored code from IGS_PS_USO_FACILITY, matching IGS_PS_MEDIA_EQUIP.MEDIA_CODE.
• FACILITY_DESCRIPTION — sourced from ME.MEDIA_DESCRIPTION; the decoded, display-ready facility name. This is the column users search for.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns, projected from the base facility table and used for audit, change tracking, and incremental extraction.

Common Use Cases and Queries

Typical uses include scheduling and room-utilization reports, facility assignment listings by unit section occurrence, and integration extracts where descriptive facility text is required alongside scheduling keys. A standard query pattern is:

• List facilities for a specific occurrence: SELECT uso_facility_id, unit_section_occurrence_id, facility_code, facility_description FROM igs_ps_uso_facility_v WHERE unit_section_occurrence_id = :occurrence_id;
• Reverse lookup by description: SELECT unit_section_occurrence_id, facility_code, facility_description FROM igs_ps_uso_facility_v WHERE facility_description LIKE '%' || :search_text || '%';
• Reporting all assigned descriptions: SELECT facility_code, facility_description, COUNT(*) FROM igs_ps_uso_facility_v GROUP BY facility_code, facility_description ORDER BY facility_code;

Because the view carries no filter beyond the equijoin, queries should apply selective predicates on UNIT_SECTION_OCCURRENCE_ID or FACILITY_CODE for performance. Reports requiring facilities not yet mastered in IGS_PS_MEDIA_EQUIP must query the base table directly, since such rows are excluded here.