Results for “terms_name”

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

Overview

IGI_INSTALMENT_AUDIT_V is a reporting and integration view owned by the APPS schema within the IGI – Public Sector Financials International product family. It is defined and shipped as a VALID database object in Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates instalment audit information required to satisfy the Instalment Terms requirement, combining audit records maintained by Public Sector Financials with the user identity responsible for each recorded action and the descriptive name of the associated payment terms.

Functionally, the view presents a denormalised, read-only projection of instalment audit activity. It links each audit row to the receivables transaction it relates to, the payment term that governed the schedule, and the application user who created or last touched the record. Because the underlying audit data is stored in a narrow transactional table, this view provides the additional descriptive attributes (user name and terms name) that make the data usable directly in reports, extracts, and downstream interfaces without further joins.

Underlying Base Objects

According to the documented view text, IGI_INSTALMENT_AUDIT_V is defined over three referenced base objects:

• IGI_INSTALMENT_AUDIT (SYNONYM) — the primary transactional source, aliased as JIA in the view definition. It supplies the audit identifier, the receivables transaction reference, the payment term reference, the user reference, the start date, and the standard WHO audit columns.
• FND_USER (SYNONYM) — the Oracle Application Object Library user table, aliased as FU. It is joined on FND_USER_ID = USER_ID to resolve the numeric user identifier into a displayable USER_NAME.
• RA_TERMS_VL (VIEW) — the Receivables payment terms view, aliased as RA. It is joined on RA_TERM_ID = TERM_ID to supply the terms name. RA_TERMS_VL is itself a view, exposing the translated (VL, or "view language") representation of payment terms.

The join conditions are expressed as inner joins: JIA.FND_USER_ID = FU.USER_ID and JIA.RA_TERM_ID = RA.TERM_ID. Consequently, rows in IGI_INSTALMENT_AUDIT that reference a user or term not present in the referenced objects will not be returned by the view.

Key Columns

• INSTALMENT_AUDIT_ID — primary identifier of the instalment audit record.
• RA_CUSTOMER_TRX_ID — foreign key to the Receivables customer transaction (invoice) against which the instalment arrangement applies.
• RA_TERM_ID — foreign key to the payment terms governing the instalment schedule.
• TERMS_NAME — the descriptive name of the payment terms, sourced from RA_TERMS_VL.NAME.
• FND_USER_ID — the application user identifier associated with the audit event.
• USER_NAME — the resolved FND_USER user name.
• START_DATE — the effective start date recorded for the instalment audit entry.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns describing record creation and last modification.
• ROW_ID — the ROWID of the underlying IGI_INSTALMENT_AUDIT row, exposed for row-level addressing.

Common Use Cases and Queries

The view is typically used to audit instalment term activity on customer transactions and to report on which users established or modified instalment arrangements. A representative query lists all instalment audit activity for a transaction:

• SELECT instalment_audit_id, ra_customer_trx_id, terms_name, user_name, start_date, creation_date FROM igi_instalment_audit_v WHERE ra_customer_trx_id = :trx_id;
• SELECT user_name, terms_name, COUNT(*) FROM igi_instalment_audit_v GROUP BY user_name, terms_name;
• SELECT * FROM igi_instalment_audit_v WHERE start_date BETWEEN :from_date AND :to_date;

Because the view resolves both the user name and the terms name, it is well suited to operational reporting and reconciliation extracts. A frequent point of confusion arises because users searching for payment terms metadata often reference RA_TERMS_VL directly; the equivalent terms descriptive attribute within this view is exposed as TERMS_NAME, which originates from RA_TERMS_VL.NAME.