Results for “bill_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_FI_BILL_DPSTS is a table within the Oracle E-Business Suite IGS (Student System) product family, a module that has since been classified as obsolete in current Oracle documentation. The table captures eligible deposit records associated with a particular bill. In operational terms, it functions as a junction table that records the relationship between a bill header and the credit activities (deposits or credits) that are eligible to be applied against that bill.

From a data modeling perspective, the metadata’s heuristic Data Vault classification suggests this object behaves as a link table. This classification is consistent with its structure: the table contains no standalone descriptive attributes of its own beyond the references and audit columns, and its primary key is composed entirely of two foreign key columns. In a Data Vault representation, IGS_FI_BILL_DPSTS would therefore represent the intersection, or link, between the bill entity and the credit activity entity, resolving a many-to-many eligibility relationship.

As noted in the ETRM metadata, the object is not implemented in the reference database, meaning it may be absent from certain environments where the Student System deposit-eligibility functionality is not deployed.

Key Information Stored

The documented physical schema for the ETRM 12.1.1 release lists eleven columns. The most significant are the two composite primary key columns, which also serve as the business-key candidates via the unique index IGS_FI_BILL_DPSTS_PK:

Together, BILL_ID and CREDIT_ACTIVITY_ID form the surrogate primary key IGS_FI_BILL_DPSTS_PK. There is no single-column surrogate identifier documented; the composite key is the business key that enforces uniqueness and prevents duplicate deposit eligibility records for the same bill-credit pairing.

The remaining documented columns are standard Oracle EBS system-generated audit and concurrency-control attributes rather than business data: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. Of these, REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID provide traceability to the concurrent program or request that inserted or altered a row, while the CREATED_BY/LAST_UPDATED_BY and date pairs support audit and row-versioning requirements. No additional descriptive columns such as amounts, statuses, or effective dates are documented for this table in the supplied metadata.

Common Use Cases and Queries

Because IGS_FI_BILL_DPSTS records deposit eligibility for bills, the principal use case is determining which deposits or credit activities may be applied against a given bill. A reporting query to retrieve the eligible deposits for a bill typically joins the link table to both parent tables:

  • Join IGS_FI_BILL_DPSTS to IGS_FI_BILL_ALL on BILL_ID to retrieve bill-level context.
  • Join IGS_FI_BILL_DPSTS to IGS_FI_CR_ACTIVITIES on CREDIT_ACTIVITY_ID to retrieve deposit or credit detail.
  • Filter by BILL_ID to isolate the eligibility set for a single bill, or by CREDIT_ACTIVITY_ID to find all bills to which a deposit is eligible.
  • Use the audit columns (CREATED_BY, CREATION_DATE, REQUEST_ID, PROGRAM_ID) to audit when and by which process an eligibility row was created, or to reconcile data loads performed by concurrent programs.
  • Detect orphan or stale eligibility rows by left-joining to the parent tables and filtering on null keys, a useful data-quality check given the composite foreign keys.

Because the table is a pure link with a composite primary key, aggregate reporting — such as counting eligible deposits per bill — can be driven directly from IGS_FI_BILL_DPSTS without touching the parent tables, making it efficient for eligibility-count metrics.

Related Objects

The FK and PK relationship data identify two principal parent objects that reference IGS_FI_BILL_DPSTS and are essential to any query against it:

  • IGS_FI_BILL_ALL — referenced through IGS_FI_BILL_DPSTS.BILL_ID; holds the bill header information.
  • IGS_FI_CR_ACTIVITIES — referenced through IGS_FI_BILL_DPSTS.CREDIT_ACTIVITY_ID; holds the deposit and credit activity detail.

In addition to these directly documented foreign-key relationships, the object sits within the broader IGS financial aid and billing table family, which includes bill-line and credit-application tables that reference IGS_FI_BILL_ALL and IGS_FI_CR_ACTIVITIES. Practical reporting should therefore be scoped through these parent tables, since the link table itself carries no descriptive attributes. Consult the IGS_FI_BILL_ALL and IGS_FI_CR_ACTIVITIES schemas for available descriptive and status columns, as none are documented for IGS_FI_BILL_DPSTS.