Search Results submit_flag

Overview

IGI_ITR_CHARGE_HEADERS_SS_V is an APPS-owned reporting view within the IGI – Public Sector Financials International product family. Its name follows the standard Oracle EBS convention for a single-segment (SS) reporting view: it flattens a normalized transaction structure into a single presentation layer suitable for concurrent programs, forms-based inquiry, and discoverer-style reporting. The view exposes charge header records from the International Transaction Reporting (ITR) subsystem, presenting each charge with its descriptive status meaning, its originating user, and its owning charge center rather than exposing raw foreign keys alone.

The view is central to the "submit_flag" inquiry path. Because HEADER.SUBMIT_FLAG stores a coded value rather than a readable label, the view joins to IGI_LOOKUPS on LOOKUP_TYPE = 'ITR_CHARGE_STATUS' to resolve the meaning into the SUBMIT_DESC column. A user searching for "submit_flag" is typically attempting to identify charge headers by their submission status — for example those already submitted versus those retained in an unsubmitted state — which is precisely the denormalized relationship this view provides. The view is read-only in practice; no DML is supported against it, and it is intended strictly as a query surface over the IGI_ITR_CHARGE_HEADERS base table.

Underlying Base Objects

The ETRM documentation identifies five referenced base objects, all exposed through APPS synonyms or views:

• IGI_ITR_CHARGE_HEADERS — the primary base table, aliased HEADER, supplying IT_HEADER_ID, SET_OF_BOOKS_ID, NAME, IT_PERIOD_NAME, SUBMIT_FLAG, GL_DATE, currency and encumbrance attributes, entered debit and credit totals, submit date, charge center, employee, and standard WHO audit columns.
• IGI_ITR_CHARGE_CENTER — aliased CENT, joined on CHARGE_CENTER_ID, supplying the human-readable CHARGE_CENTER name.
• IGI_LOOKUPS — the IGI lookup view, joined on LOOKUP_CODE = HEADER.SUBMIT_FLAG and LOOKUP_TYPE = 'ITR_CHARGE_STATUS', returning MEANING as SUBMIT_DESC.
• FND_USER — aliased FND, joined on USER_ID = HEADER.IT_ORIGINATOR_ID, supplying USER_NAME as ORIGINATOR_NAME.
• GL_LEDGERS — referenced in the documented 12.2.2 dependency list, reflecting the set of books / ledger context of each charge header.

The joins are inner joins throughout, so a charge header is returned only when a matching charge center, a matching lookup code of type ITR_CHARGE_STATUS, and a matching originating FND_USER all exist. Rows carrying an unrecognized or inactive SUBMIT_FLAG code are therefore silently excluded from the result set.

Key Columns

• ROW_ID — the ROWID of the underlying header row, used by Oracle Forms as the row identifier for updateable blocks.
• IT_HEADER_ID — primary key of the charge header record.
• SUBMIT_FLAG — the raw status code stored on the header; this is the column targeted by the "submit_flag" search.
• SUBMIT_DESC — the lookup meaning corresponding to SUBMIT_FLAG, decodes the flag into a readable status.
• ORIGINATOR_NAME — the FND_USER user name of the person who originated the charge.
• CHARGE_CENTER / CHARGE_CENTER_ID — the owning charge center name and its identifier.
• TOTAL_DR / TOTAL_CR — sums of ENTERED_DR and ENTERED_CR, providing the entered debit and credit values for the header.
• SET_OF_BOOKS_ID, GL_DATE, CURRENCY_CODE, ENCUMBRANCE_TYPE_ID, IT_PERIOD_NAME — accounting context attributes.
• SUBMIT_DATE — the date and time the charge was submitted.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The principal use case is status-driven inquiry. Reporting on unsubmitted or submitted charges is the reason the view exists, and filtering on SUBMIT_FLAG or SUBMIT_DESC is the standard entry point. A typical query retrieves outstanding charges for a charge center and period:

• SELECT IT_HEADER_ID, NAME, SUBMIT_DESC, TOTAL_DR, TOTAL_CR, CURRENCY_CODE, ORIGINATOR_NAME, GL_DATE FROM IGI_ITR_CHARGE_HEADERS_SS_V WHERE SUBMIT_FLAG = 'N' AND IT_PERIOD_NAME = :period ORDER BY ORIGINATOR_NAME;
• SELECT CHARGE_CENTER, SUBMIT_DESC, COUNT(*) FROM IGI_ITR_CHARGE_HEADERS_SS_V WHERE SET_OF_BOOKS_ID = :sob GROUP BY CHARGE_CENTER, SUBMIT_DESC;
• SELECT IT_HEADER_ID, SUBMIT_FLAG, SUBMIT_DATE FROM IGI_ITR_CHARGE_HEADERS_SS_V WHERE TRUNC(SUBMIT_DATE) BETWEEN :from_date AND :to_date;

Because the view is not indexed apart from the underlying table indexes, queries should be selective on IT_HEADER_ID, SET_OF_BOOKS_ID, IT_PERIOD_NAME, or CHARGE_CENTER_ID. The FND_USER and IGI_LOOKUPS joins are inexpensive but may be applied to very large header sets, so restricting by period or ledger before aggregation is advisable.