Search Results ld_coa

Overview

IGF_AP_EFC_TERM_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGF.IGF_AP_EFC_TERM_V. It belongs to the Oracle Financial Aid (IGF) product family and, in the Oracle EBS 12.1.1 and 12.2.2 releases, is classified as a "supplementary view used to simplify forms coding." The view exposes expected family contribution (EFC) term-attribute data — specifically calendar term identifiers and start/end dates — in a shape convenient for Oracle Forms blocks rather than for direct end-user reporting. In the ETRM metadata, the view is marked VALID, and the design notes carry an explicit Oracle warning: querying or altering data through this view is not recommended, because its definition may change dramatically in subsequent minor or major releases. For integration and reporting purposes this means the view is safest treated as an internal, form-facing object; any custom code that references it, including code that filters on LD_START_DT, should be verified against the owning form and against the supported interface tables rather than treated as a stable public contract.

Underlying Base Objects

The documented dependency information is deliberately narrow. In the View Source section, the base objects list includes PUBLIC and DUAL, and the dependency section states: "APPS.IGF_AP_EFC_TERM_V references the following: PUBLIC, DUAL." No business tables are documented as base objects, and the metadata explicitly records "Referenced base objects: none documented." The view is also documented as not being referenced by any database object, meaning no other view, synonym, or PL/SQL unit in the ETRM dependency graph depends on it. Two consequences follow. First, the visible query text is a direct projection from the view's own column list, with no documented joins to IGF base tables in the excerpt. Second, because no base objects are enumerated, the underlying tables that actually supply BASE_ID, LD_CAL_TYPE, and the LD_* columns cannot be confirmed from the supplied metadata alone. In common practice, views named with the LD_ prefix relate to term or calendar-attribute storage; the LD_CAL_TYPE and LD_SEQUENCE_NUMBER columns strongly suggest the view is derived from term/calendar setup data rather than from transactional aid records. Because the documented dependency list is limited to DUAL, the practical conclusion is that the view is a forms-support construct whose true data sources are not exposed as documented dependencies and should not be assumed to be fixed.

Key Columns

The view exposes seven VARCHAR2 columns, all defined with datatype VARCHAR2:

• BASE_ID — the base record identifier carried through to the form block.
• LD_CAL_TYPE — the calendar type for the term, identifying the calendar category to which the term belongs.
• LD_SEQUENCE_NUMBER — the sequence number used to order terms within their calendar type.
• LD_ALTERNATE_CODE — the alternate code for the calendar/term instance.
• LD_START_DT — the term start date, exposed as VARCHAR2 rather than as a native DATE type. This is directly relevant to the searched term; comparisons should account for the character datatype and for any NLS or date-format conversion performed by the underlying form.
• LD_END_DT — the term end date, likewise exposed as VARCHAR2.
• LD_COA — the chart of accounts associated with the term record.

Because every column is VARCHAR2, callers filtering or sorting LD_START_DT must consider lexicographic versus chronological ordering, and should apply explicit date conversion only where the stored string format is known and stable.

Common Use Cases and Queries

The primary supported use is behind-the-scenes support for Oracle Forms coding within the Financial Aid module — for example, maintaining term date ranges as users navigate aid setup forms. It is not a recommended reporting source. Where it is queried for diagnostic purposes, the documented query text can be used as-is:

• SELECT BASE_ID, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_ALTERNATE_CODE, LD_START_DT, LD_END_DT, LD_COA FROM APPS.IGF_AP_EFC_TERM_V;
• To inspect term boundaries only: SELECT BASE_ID, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_START_DT, LD_END_DT FROM APPS.IGF_AP_EFC_TERM_V;

Given the warning that the view may change dramatically, customizations that select from it, especially those keyed on LD_START_DT, should be reviewed before applying EBS patches or upgrades between 12.1.1 and 12.2.2.