Search Results encumbered_amount

Overview

The view APPS.IGI_ITR_CHARGE_LINES_SS_V belongs to the IGI - Public Sector Financials International product family within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes intra-governmental (ITR) charge transaction line data in a denormalized, reporting-ready form, joining charge line records to their associated headers, service definitions, charge centers, lookup meanings, and user information. In the IGI schema it is catalogued as a VALID VIEW object owned by APPS, and the naming suffix _SS_V indicates that it is a secured or self-service query view typically consumed by OAF pages, Oracle Reports, and custom SQL against the EBS database.

Practically, the view serves as the presentation layer for ITR charge adjustment and recharge processing, allowing descriptive attributes (service type, charge center name, lookup meaning) to be surfaced alongside the raw numbered columns stored on the underlying transaction tables. The column FAILED_FUNDS_LOOKUP_CODE, present on the base charge lines, is exposed verbatim through this view and is the attribute most often sought by administrators investigating why a particular recharge line did not pass funds-check validations.

Underlying Base Objects

The documented ETRM metadata for release 12.2.2 lists the following referenced base objects: FND_USER (synonym), IGI_ITR_CHARGE_CENTER (synonym), IGI_ITR_CHARGE_HEADERS (synonym), IGI_ITR_CHARGE_LINES (synonym), IGI_ITR_CHARGE_SERVICE_SS_V (view), IGI_ITR_SERVICE (synonym), and IGI_LOOKUPS (view).

• IGI_ITR_CHARGE_LINES is the primary driver, supplying line number, amounts, status and posting flags, encumbrance attributes, accounting code combinations, and the failed funds lookup code.
• IGI_ITR_CHARGE_HEADERS provides header-level context joined on IT_HEADER_ID.
• IGI_ITR_CHARGE_SERVICE_SS_V supplies the service name exposed as SERVICE_TYPE; its underlying IGI_ITR_SERVICE synonym carries the SERVICE_ID.
• IGI_ITR_CHARGE_CENTER supplies the charge center name joined via CHARGE_CENTER_ID.
• IGI_LOOKUPS resolves the lookup code into a readable MEANING, notably for FAILED_FUNDS_LOOKUP_CODE.
• FND_USER is referenced for created-by / last-updated-by user identification.

Key Columns

• IT_LINE_NUM, IT_SERVICE_LINE_ID, IT_HEADER_ID — transaction identifiers linking the line to its header and service line.
• STATUS_FLAG and POSTING_FLAG — indicate the processing state of the line and whether it has been posted to General Ledger.
• FAILED_FUNDS_LOOKUP_CODE — the lookup code indicating the reason a funds/appropriation check failed on the line; surfaced directly from the base line table.
• MEANING — the decoded description for the lookup code, resolved through IGI_LOOKUPS.
• ENTERED_DR, ENTERED_CR, SUGGESTED_AMOUNT — debit, credit, and proposed recharge amounts.
• ENCUMBRANCE_FLAG, ENCUMBERED_AMOUNT, UNENCUMBERED_AMOUNT, GL_ENCUMBERED_DATE, GL_ENCUMBERED_PERIOD_NAME, GL_CANCELLED_DATE, PREVENT_ENCUMBRANCE_FLAG — budget and encumbrance status attributes.
• CREATION_CODE_COMBINATION_ID, RECEIVING_CODE_COMBINATION_ID, SUGGESTED_RECV_CCID — accounting flexfield identifiers for the creating and receiving cost centers.
• CHARGE_CENTER, SERVICE_TYPE, DESCRIPTION — descriptive attributes for reporting.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include identifying lines that failed funds checking, reconciling encumbrance balances for intra-governmental recharges, and reporting posted versus unposted ITR activity by charge center.

• Listing failed funds lines with decoded reasons:

  SELECT it_line_num, it_header_id, failed_funds_lookup_code, meaning,
         entered_dr, entered_cr, status_flag
  FROM   apps.igi_itr_charge_lines_ss_v
  WHERE  failed_funds_lookup_code IS NOT NULL;

• Summarizing encumbrance status by charge center:

  SELECT charge_center, status_flag,
         SUM(encumbered_amount) encumbered, SUM(unencumbered_amount) available
  FROM   apps.igi_itr_charge_lines_ss_v
  GROUP  BY charge_center, status_flag;

• Extracting unposted lines for a period:

  SELECT it_line_num, service_type, suggested_amount, gl_encumbered_period_name
  FROM   apps.igi_itr_charge_lines_ss_v
  WHERE  posting_flag = 'N'
  AND    gl_encumbered_period_name = :period_name;

• Auditing failed funds reasons against lookup validation:

  SELECT f.failed_funds_lookup_code, l.meaning, COUNT(*)
  FROM   apps.igi_itr_charge_lines_ss_v f, apps.igi_lookups l
  WHERE  l.lookup_code = f.failed_funds_lookup_code
  GROUP  BY f.failed_funds_lookup_code, l.meaning;

Because the view is APPS-owned and exposes ROWID-based ROW_ID, it is also suitable for joining to base tables when drill-down to the transactional record is required.