Results for “igf_se_payment”

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

Overview

IGF_SE_PAYMENT is a transaction table within the IGF (Financial Aid) product family in Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its stated purpose is to store payroll details that are loaded into the application through a payment upload process. Records flow from a staging interface table into IGF_SE_PAYMENT, and users may additionally enter or maintain external payroll details manually. The table therefore functions as a persistent repository for externally sourced payroll and payment information that supports financial aid disbursement and reconciliation activities.

The ETRM metadata notes that the object is classified under IGF as Obsolete, and that it is not implemented in the database captured by the reference environment. This is a material caveat: in environments where the corresponding Financial Aid functionality was never deployed or has been retired, the table will not exist, and any query or concurrent program referencing it will fail. The heuristic Data Vault classification mined from the foreign-key structure is link, which suggests modeling IGF_SE_PAYMENT as a relationship or association construct connecting a person, an award fund, and an academic calendar instance, with descriptive attributes attached. This classification is offered as a modeling suggestion rather than an enforced design rule.

Key Information Stored

The table is defined with 21 documented columns in the 12.1.1 physical schema, owned by the IGF schema. The surrogate primary key is TRANSACTION_ID, enforced by the IGF_SE_PAYMENT_PK constraint and also carried by the unique index IGF_SE_PAYMENT_U1. The most significant columns are:

• TRANSACTION_ID — surrogate primary key and unique business-key candidate, uniquely identifying each payroll transaction row.
• PAYROLL_ID — identifier of the payroll batch or source payroll record from which the row originated.
• PAYROLL_DATE — effective date of the payroll entry, used for period-based reporting.
• PERSON_ID — the individual associated with the payment; foreign key to HZ_PARTIES.
• FUND_ID — the award fund against which the payment is recorded; foreign key to IGF_AW_FUND_MAST_ALL.
• LD_CAL_TYPE and LD_SEQUENCE_NUMBER — composite reference to the load calendar instance in IGS_CA_INST_ALL.
• AUTH_ID — authorization reference linking to JTF_XML_INV_AUTHS.
• PAID_AMOUNT — monetary value disbursed to the person.
• HRS_WORKED — hours worked, supporting work-study style payment calculations.
• ORG_UNIT_CD — organizational unit code owning or sponsoring the payment.
• SOURCE — indicator distinguishing upload-derived records from manually entered ones.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and audit context columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-column audit attributes.

Common Use Cases and Queries

Typical reporting scenarios include reconciling uploaded payroll against award fund balances, summarizing disbursements by person or fund, and analyzing hours worked for work-study programs. A representative aggregation by fund follows:

• SELECT FUND_ID, COUNT(*), SUM(PAID_AMOUNT) FROM IGF_SE_PAYMENT GROUP BY FUND_ID;
• SELECT PERSON_ID, PAYROLL_DATE, PAID_AMOUNT FROM IGF_SE_PAYMENT WHERE SOURCE = 'UPLOAD';
• SELECT p.TRANSACTION_ID, h.PARTY_NAME, f.FUND_CODE FROM IGF_SE_PAYMENT p, HZ_PARTIES h, IGF_AW_FUND_MAST_ALL f WHERE p.PERSON_ID = h.PARTY_ID AND p.FUND_ID = f.FUND_ID;

Data-quality checks commonly compare counts between the interface table and IGF_SE_PAYMENT to confirm that all uploaded rows posted successfully, and audit queries filter on REQUEST_ID to trace records created by a specific concurrent request.

Related Objects

Foreign-key relationships define the principal dependencies of IGF_SE_PAYMENT:

• HZ_PARTIES — joined on IGF_SE_PAYMENT.PERSON_ID = HZ_PARTIES.PARTY_ID, supplying person identity.
• IGF_AW_FUND_MAST_ALL — joined on IGF_SE_PAYMENT.FUND_ID = IGF_AW_FUND_MAST_ALL.FUND_ID, supplying fund definitions.
• IGS_CA_INST_ALL — joined on IGF_SE_PAYMENT.LD_CAL_TYPE and LD_SEQUENCE_NUMBER, supplying calendar instance context.
• JTF_XML_INV_AUTHS — referenced through IGF_SE_PAYMENT.AUTH_ID for authorization validation.
• The upstream payment interface table — the staging source from which rows are loaded into IGF_SE_PAYMENT.

Because the object is marked Obsolete and was not implemented in the reference database, integrators should validate its physical presence before relying on the join patterns above.