Search Results submit_date




Overview
Explore in AI Chat

Overview

IGI_ITR_CHARGE_LINES_ENTRY_V is a reporting view in the APPS schema that belongs to the IGI – Public Sector Financials International product family. It presents charge line entry data from the Inter-Governmental Transactions (ITR) subsystem, joining charge line detail records with their associated charge center definitions. The view carries a status of VALID and is available in both Oracle EBS 12.1.1 and 12.2.2 environments.

The view is designed as a form and reporting access layer over the intersection of IGI_ITR_CHARGE_CENTER and IGI_ITR_CHARGE_LINES. Functional entry screens in the IGI module reference charge lines by charge center, and this view provides a single denormalized source that exposes the charge center name alongside each line, avoiding the need for form-level or report-level joins. The presence of the ROW_ID column, derived from LINES.ROWID, indicates the view supports updatable, row-identified access typical of Oracle Forms block data sources. For 12.2.x environments, the same definition remains valid, though the underlying synonyms resolve through the edition-based redefinition architecture and Online Patching AD_ZD infrastructure.

Underlying Base Objects

The view definition is based on two synonyms: IGI_ITR_CHARGE_CENTER (aliased CC) and IGI_ITR_CHARGE_LINES (aliased LINES). These synonyms resolve to the corresponding IGI base tables in the APPS schema. The relationship is an equijoin on CHARGE_CENTER_ID, meaning each charge line is joined to exactly one charge center master record. No outer join is used, so lines without a matching charge center are not returned by the view.

All transactional attributes — amounts, dates, flags, and audit columns — originate from IGI_ITR_CHARGE_LINES. The only attribute sourced from the charge center table is CC.NAME, exposed as the CHARGE_CENTER column. The view retains the ROWID of the charge lines table, which makes it suitable for identifying and updating specific line records within form blocks.

Key Columns

  • ROW_ID — The rowid of the underlying charge line record; used for row-level identification and form updates.
  • IT_LINE_NUM — The line number within the inter-governmental transaction.
  • DESCRIPTION — Free-text description of the charge line.
  • SUBMIT_DATE — The date the charge line was submitted; a primary filter in period and status reporting and the term most frequently searched by users of this view.
  • REJECTION_NOTE — Reason text recorded when a line is rejected.
  • IT_HEADER_ID — Foreign key to the parent inter-governmental transaction header.
  • SET_OF_BOOKS_ID — Ledger identifier governing the accounting context of the line.
  • CODE_COMBINATION_ID — Accounting flexfield combination to which the line posts.
  • CHARGE_CENTER_ID — Identifier of the owning charge center.
  • STATUS_FLAG and POSTING_FLAG — Workflow and accounting state indicators for the line.
  • ENTERED_CR / ENTERED_DR — Entered credit and debit amounts.
  • SUGGESTED_AMOUNT — System-suggested amount for the line.
  • EFFECTIVE_DATE — Effective date used for accounting and reporting.
  • CHARGE_CENTER — The charge center name joined from the master table.
  • Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include reviewing submitted charge lines by date, auditing rejected lines, reconciling entered versus suggested amounts, and extracting charge line detail with charge center names for downstream reporting. A common search pattern filters on SUBMIT_DATE:

SELECT it_line_num, description, submit_date, charge_center, entered_dr, entered_cr, status_flag FROM apps.igi_itr_charge_lines_entry_v WHERE submit_date BETWEEN :p_from_date AND :p_to_date ORDER BY submit_date, it_line_num;

To isolate rejected submissions:

SELECT it_header_id, it_line_num, submit_date, rejection_note, charge_center FROM apps.igi_itr_charge_lines_entry_v WHERE status_flag = 'REJECTED' AND submit_date >= :p_start_date;

Because the view exposes ROW_ID and joins two base objects without aggregation, it can also be queried within Oracle Forms blocks and used for integration extracts where a unified, charge-center-labeled line record is required.