Results for “setup_data_element_id”

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

Overview

The view IGS_PE_STUP_DATA_EMT belongs to the IGS – Student System product family within Oracle E-Business Suite, and is classified in the ETRM repository as obsolete. Its purpose is to expose setup data element records associated with person types in the Student System, presenting a secured, organization-filtered projection of the underlying setup data element table. In Oracle EBS releases 12.1.1 and 12.2.2, the view is defined in the database schema but the ETRM documentation explicitly notes that it is "Not implemented in this database," indicating that no compiled object exists in the reference environment and that any dependent reporting or integration logic must be treated as legacy.

The view performs a row-level security filter using the ORG_ID column and the session attribute USERENV('CLIENT_INFO'). This is the standard Oracle Application Object Library multi-org pattern for views that must restrict access to the operating unit stored in the client information context. Only records matching the current session's operating unit, or the default sentinel value -99, are returned to the caller.

Underlying Base Objects

The view text selects from a single documented base object: the table IGS_PE_STUP_DATA_EMT_ALL. The _ALL suffix denotes that the base table stores rows across all operating units, with each row tagged by an ORG_ID. The view therefore acts as an operating-unit-specific filter over that table, exposing the union of accessible rows rather than a separate physical entity. Four of the exposed columns—ORG_ID, SETUP_DATA_ELEMENT_ID, PERSON_TYPE_CODE, and DATA_ELEMENT—form the logical business key that the _ALL table maintains, while the remaining columns carry descriptive, control, and audit information.

No other base tables, synonyms, or packaged functions are documented as dependencies of this view. Because the ETRM entry lists no referenced base objects beyond the _ALL table, the view should be understood purely as a security wrapper rather than a join-intensive reporting object.

Key Columns

• ROW_ID — The pseudo-column ROWID of the underlying table row, aliased for use by Oracle Forms and other tooling that requires a stable row identifier.
• ORG_ID — The operating unit identifier used by the multi-org security predicate; this is the column against which the USERENV('CLIENT_INFO') comparison is made.
• SETUP_DATA_ELEMENT_ID — The surrogate primary key of the setup data element definition.
• PERSON_TYPE_CODE — The person type to which the setup data element applies, linking the element to a category of person record in the Student System.
• DATA_ELEMENT — The identifier or name of the individual data element being configured.
• VALUE — The configured value assigned to that data element for the given person type.
• REQUIRED_IND — A flag indicating whether the data element is mandatory for the associated person type.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row and when.

Common Use Cases and Queries

The primary use case is configuration reporting: extracting the set of data elements configured for each person type, together with their values and required flags, for a given operating unit. Integration scenarios may also read this view to drive external form rendering or validation logic. Because the view is obsolete and not implemented in the reference database, any query against it in 12.1.1 or 12.2.2 should be validated against the customer's actual schema before reliance.

A representative query lists required elements for a person type:

• SELECT setup_data_element_id, person_type_code, data_element, value FROM igs_pe_stup_data_emt WHERE person_type_code = 'STUDENT' AND required_ind = 'Y' ORDER BY data_element;
• SELECT person_type_code, COUNT(*) FROM igs_pe_stup_data_emt GROUP BY person_type_code;

In all cases the multi-org predicate is applied automatically by the view; callers need not add their own ORG_ID filter, and attempting to do so with a mismatched value will return no rows.