Results for “igs_fi_encmb_type”

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

Overview

IGS_FI_ENCMB_TYPE is a multi-organization secured view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes the master records of encumbrance types maintained in the Financials integration layer of the Student System, allowing authorized users and concurrent programs to reference encumbrance type definitions without querying the underlying table directly. The view is reported as VALID in the ETRM data dictionary for release 12.2.2 and is equally applicable to 12.1.1 deployments.

Encumbrance types are the classification codes used by the Student System to categorize financial commitments raised against student accounts — for example tuition fee holds, deposit encumbrances, and sponsor-funded liabilities. Because these definitions are organization-specific, the view enforces operating unit (ORG_ID) security at the database layer rather than relying on application-level filtering. This makes it the recommended access point for both seeded concurrent programs and custom reporting against encumbrance type setup.

Underlying Base Objects

The view is defined over the single base table IGS_FI_ENCMB_TYPE_ALL. The ETRM-documented metadata lists no other referenced objects, and the view text confirms that all columns are sourced from that one table, aliased as A. The definition is:

• SELECT A.ROWID ROW_ID, A.ENCUMBRANCE_TYPE, A.DESCRIPTION, A.S_ENCUMBRANCE_CAT, A.CLOSED_IND, A.COMMENTS, A.ORG_ID, A.CREATED_BY, A.CREATION_DATE, A.LAST_UPDATED_BY, A.LAST_UPDATE_DATE, A.LAST_UPDATE_LOGIN FROM IGS_FI_ENCMB_TYPE_ALL A

The WHERE clause applies the standard Oracle multi-org security predicate. It derives the current operating unit from the first ten characters of USERENV('CLIENT_INFO'), converts that value to a number, and compares it to the row's ORG_ID. Both sides apply NVL to a sentinel value of -99, so rows with a null ORG_ID (global or reference records) remain visible irrespective of the active operating unit. Note that the view is not a synonym-based "current org" view; it returns rows for the session's operating unit only, determined by the CLIENT_INFO initialization performed by FND_GLOBAL when the user selects a responsibility with an associated operating unit.

Key Columns

• ENCUMBRANCE_TYPE — The primary business key, the code identifying the encumbrance type.
• DESCRIPTION — The user-facing name of the encumbrance type.
• S_ENCUMBRANCE_CAT — The system-level encumbrance category to which the type belongs.
• CLOSED_IND — Indicates whether the encumbrance type has been closed and should no longer be selected for new transactions.
• COMMENTS — Free-form annotation entered by the setup user.
• ORG_ID — The operating unit owning the record; the column driving the view's security predicate.
• ROW_ID — The ROWID of the underlying table row, exposed for tools and forms that require a row identifier.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and last modification details.

Common Use Cases and Queries

Typical uses include validating that an encumbrance type is open before charging it, producing setup listings for a specific operating unit, and joining the view to student financial records to report commitments by category.

• List active encumbrance types for the current operating unit:
  SELECT encumbrance_type, description, s_encumbrance_cat FROM apps.igs_fi_encmb_type WHERE closed_ind = 'N' ORDER BY encumbrance_type;
• Retrieve a single type's details including audit information:
  SELECT encumbrance_type, description, comments, org_id, creation_date FROM apps.igs_fi_encmb_type WHERE encumbrance_type = :p_type;
• Summarize counts by category and operating unit:
  SELECT s_encumbrance_cat, org_id, COUNT(*) FROM apps.igs_fi_encmb_type GROUP BY s_encumbrance_cat, org_id;

Because the view enforces operating unit security through CLIENT_INFO, queries executed outside the EBS Forms session (for example from SQL*Plus) must set the client information explicitly or they will return only unqualified (null ORG_ID) rows. Develop against IGS_FI_ENCMB_TYPE rather than the _ALL table wherever row-level operating unit security is required.