Search Results itr_charge_status

Overview

The view APPS.IGI_ITR_CHARGE_HEADERS_SS_V is a reporting and inquiry construct within the Oracle E-Business Suite public sector and grants/expenditure tracking family of modules, exposed under the APPS schema. It presents charge header records from the ITR (Information Technology Reporting / charge processing) subsystem in a denormalized, presentation-ready form. Its principal purpose is to feed Oracle Form-based summary screens and concurrent reporting by joining a charge header row to its associated charge center, status lookup meaning, originator user name, and ledger name, so that consumers do not have to reconstruct these joins themselves.

The suffix _SS_V indicates a "Summary Screen" or single-source view, meaning it is typically bound to a specific Oracle Forms block. The view carries a ROWID-derived ROW_ID column, which is a strong indicator the view is used in a mutable, block-based UI context where Forms requires a unique identifier for each row to support locking and updates.

Underlying Base Objects

The view is defined over five documented objects, joined as follows:

• IGI_ITR_CHARGE_HEADERS (aliased HEADER) — the driving table supplying the charge header, period, submit flag, amounts, currency, and audit columns.
• IGI_ITR_CHARGE_CENTER (aliased CENT) — joined on CHARGE_CENTER_ID to supply the human-readable charge center name via CENT.NAME.
• IGI_LOOKUPS (aliased LOOKUPS) — joined on LOOKUP_CODE = HEADER.SUBMIT_FLAG where LOOKUP_TYPE = 'ITR_CHARGE_STATUS', yielding the status meaning in the SUBMIT_DESC column.
• FND_USER (aliased FND) — joined on USER_ID = HEADER.IT_ORIGINATOR_ID to obtain FND.USER_NAME as ORIGINATOR_NAME.
• GL_LEDGERS (aliased GLL) — joined twice on set of books, CENT.SET_OF_BOOKS_ID = GLL.LEDGER_ID and HEADER.SET_OF_BOOKS_ID = GLL.LEDGER_ID, producing LEDGER_NAME.

The lookup join to type ITR_CHARGE_STATUS is the critical link explaining why users searching on itr_charge_status are directed to this view: the status domain for charge headers is stored under that lookup type, and the view surfaces its meaning alongside each header.

Key Columns

• ROW_ID, IT_HEADER_ID — the Form row identifier and the primary business key of the header.
• NAME, CHARGE_CENTER, LEDGER_NAME — human-readable identifiers for the charge record, its center, and its ledger.
• SUBMIT_FLAG, SUBMIT_DESC — the raw status code and its translated meaning from the ITR_CHARGE_STATUS lookup.
• SUBMIT_DATE, CREATE_DATE family (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — audit and submission timing.
• TOTAL_DR (from ENTERED_DR) and TOTAL_CR (from ENTERED_CR) — debit and credit totals for the charge line aggregation.
• CURRENCY_CODE, GL_DATE, IT_PERIOD_NAME, ENCUMBRANCE_TYPE_ID — accounting attributes.
• IT_ORIGINATOR_ID, ORIGINATOR_NAME, EMPLOYEE_ID — the submitting user and associated employee.

Common Use Cases and Queries

Typical uses include listing charge headers by status, reviewing amounts by charge center, and locating records awaiting submission.

SELECT IT_HEADER_ID, NAME, CHARGE_CENTER, SUBMIT_DESC,
       TOTAL_DR, TOTAL_CR, CURRENCY_CODE, ORIGINATOR_NAME
FROM   APPS.IGI_ITR_CHARGE_HEADERS_SS_V
WHERE  SUBMIT_FLAG = 'SUBMITTED';

SELECT CHARGE_CENTER, SUM(TOTAL_DR) DR, SUM(TOTAL_CR) CR
FROM   APPS.IGI_ITR_CHARGE_HEADERS_SS_V
WHERE  IT_PERIOD_NAME = :p_period
GROUP  BY CHARGE_CENTER;

Because the view already resolves the lookup meaning, queries against SUBMIT_DESC avoid hard-coding status codes and remain aligned with the ITR_CHARGE_STATUS lookup maintained in IGI_LOOKUPS.