Search Results igi_itr_charge_service_ss_v




Overview
Explore in AI Chat

Overview

The IGI_ITR_CHARGE_SERVICE_SS_V view is a reporting and integration object owned by the APPS schema within the IGI – Public Sector Financials International product family of Oracle E-Business Suite. Its status is VALID in both the 12.1.1 and 12.2.2 releases. The view presents a flattened, denormalized representation of charge service assignments, combining descriptive service attributes with their associated charge center linkage. Rather than exposing the normalized transactional tables directly, the view joins the charge service assignment record to its parent service definition and charge center, allowing downstream reports, concurrent programs, and integration interfaces to retrieve service names and descriptions alongside the assignment's accounting and date attributes in a single query.

The "_SS_V" naming convention is consistent with Oracle's standard for a stored or secured view used as a data source for a specific functional area, in this case charge service processing. It is intended for read-only consumption; no DML should be performed against it. Because it resides in APPS, it is accessible to any responsibility whose menu or request group references it, subject to the standard APPS schema grants.

Underlying Base Objects

The view is defined over three base objects, each exposed through a synonym in the APPS schema:

Two inner joins are present: SERVI.SERVICE_ID = SERV.SERVICE_ID and SERV.CHARGE_CENTER_ID = CC.CHARGE_CENTER_ID. Because inner joins are used, a charge service row is only returned when a matching service and a matching charge center both exist. The view therefore filters out orphaned assignments rather than exposing them with null descriptors.

Key Columns

  • ROW_ID – the ROWID of the underlying IGI_ITR_CHARGE_SERVICE row, useful for direct row identification.
  • CHARGE_SERVICE_ID – primary key of the charge service assignment.
  • CHARGE_CENTER_ID – the charge center to which the service is assigned.
  • SERVICE_ID, NAME, DESCRIPTION – service identity and descriptive text sourced from IGI_ITR_SERVICE.
  • CREATION_CCID, RECEIVING_CCID – accounting flexfield code combinations for the creating and receiving sides of the charge.
  • START_DATE, END_DATE – the effective period of the assignment, used for date-ranged reporting.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns for traceability.

Common Use Cases and Queries

Typical uses include charge service listings for a given charge center, active-assignment extracts for a period, and integration feeds where descriptive service text is required alongside the assignment row.

SELECT charge_service_id, charge_center_id, service_id,
       name, description, start_date, end_date
FROM   igi_itr_charge_service_ss_v
WHERE  charge_center_id = :p_charge_center_id
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date, TRUNC(SYSDATE))
                          AND NVL(end_date, TRUNC(SYSDATE));

A second common pattern retrieves all assignments for a named service or exports the full view for reconciliation against the base tables.

SELECT s.charge_service_id, s.charge_center_id, s.name
FROM   igi_itr_charge_service_ss_v s
WHERE  UPPER(s.name) LIKE UPPER('%'||:p_service||'%')
ORDER  BY s.charge_center_id, s.start_date;

Because the view performs inner joins only, reconciliation queries against IGI_ITR_CHARGE_SERVICE should account for rows lacking a valid service or charge center, which will not appear here.