Results for “igs_fi_applications”

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

Overview

IGS_FI_APPLICATIONS is a transaction-level table in the Oracle E-Business Suite Student System (IGS) product family. It records application information about credits and charges transactions that have been applied against one another — for example, the application of a credit memo, payment, or adjustment to an open invoice line. The table effectively acts as the ledger that ties the credit side of a student financial transaction to the debit side by storing the credit account, debit account, and amounts involved. Because it records the event of applying value rather than the identity of the party itself, the heuristic Data Vault classification supplied in the metadata is link. Under that modeling suggestion, IGS_FI_APPLICATIONS would function as a link table joining the invoice, credit, and posting hubs, with its descriptive columns (amounts, dates, GL accounts) residing in a satellite. In native EBS physical terms, it is a standard transactional detail table owned by the IGS schema, with status VALID in the ETRM 12.1.1 registry.

Key Information Stored

The table contains 27 documented columns. The most significant are:

• APPLICATION_ID — surrogate primary key, enforced by the unique index IGS_FI_APPLICATIONS_PK and by the business-key candidate IGS_FI_APPLICATIONS_U1. This is the only documented unique identifier on the table.
• APPLICATION_TYPE — classifies the application event (for example, how the credit was consumed).
• INVOICE_ID — the invoice against which the application is made; foreign key to IGS_FI_INV_INT_ALL.
• CREDIT_ID and CREDIT_ACTIVITY_ID — the credit and credit activity being applied; foreign keys to IGS_FI_CREDITS_ALL and IGS_FI_CR_ACTIVITIES respectively.
• AMOUNT_APPLIED and APPLY_DATE — the monetary value applied and the effective date of the application.
• DR_ACCOUNT_CD and CR_ACCOUNT_CD — debit and credit account codes; both reference IGS_FI_ACC_ALL and are central to the accounting footprint of the application.
• DR_GL_CODE_CCID and CR_GL_CODE_CCID — the corresponding General Ledger code combinations used when the application is transferred to GL.
• APPLIED_INVOICE_LINES_ID and APPL_HIERARCHY_ID — the specific invoice line applied and the application hierarchy driving the allocation; foreign keys to IGS_FI_INVLN_INT_ALL and IGS_FI_A_HIERARCHIES.
• POSTING_ID and POSTING_CONTROL_ID — links to the posting and posting-control records (IGS_FI_POSTING_INT_ALL and AR_POSTING_CONTROL).
• GL_DATE and GL_POSTED_DATE — accounting dates used for subledger-to-GL transfer.
• LINK_APPLICATION_ID — self-referencing linkage used to model reversals or offsetting applications.
• Standard WHO audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID and PROGRAM_UPDATE_DATE for concurrent-program traceability.

Common Use Cases and Queries

Finance and student-accounts reporting typically aggregate AMOUNT_APPLIED by APPLY_DATE or GL_DATE to reconcile credits applied to charges. A representative query joins the credit and invoice sides:

• SELECT a.APPLICATION_ID, a.INVOICE_ID, a.CREDIT_ID, a.AMOUNT_APPLIED, a.APPLY_DATE FROM IGS_FI_APPLICATIONS a WHERE a.GL_DATE BETWEEN :from_date AND :to_date;
• Reconciling subledger detail to GL by grouping on DR_GL_CODE_CCID and CR_GL_CODE_CCID where GL_POSTED_DATE is null (unposted applications).
• Auditing application hierarchies by joining APPL_HIERARCHY_ID to IGS_FI_A_HIERARCHIES.
• Tracing postings by joining POSTING_ID to IGS_FI_POSTING_INT_ALL for accounting-event drill-downs.
• Detecting reversals by matching LINK_APPLICATION_ID back to APPLICATION_ID.

Related Objects

The table is a heavily dependent link entity; its most significant related objects are:

• IGS_FI_INV_INT_ALL — joined on INVOICE_ID.
• IGS_FI_CREDITS_ALL — joined on CREDIT_ID.
• IGS_FI_CR_ACTIVITIES — joined on CREDIT_ACTIVITY_ID.
• IGS_FI_INVLN_INT_ALL — joined on APPLIED_INVOICE_LINES_ID.
• IGS_FI_ACC_ALL — referenced twice, via DR_ACCOUNT_CD and CR_ACCOUNT_CD.
• IGS_FI_A_HIERARCHIES — joined on APPL_HIERARCHY_ID.
• IGS_FI_POSTING_INT_ALL — joined on POSTING_ID for posting detail.
• AR_POSTING_CONTROL — joined on POSTING_CONTROL_ID, bridging the IGS student system to Oracle Receivables posting control.