Search Results igf_se_payment_int_pk

Overview

IGF_SE_PAYMENT_INT is an interface (staging) table owned by the IGF schema within the Oracle E-Business Suite Financial Aid module. It exists to receive payment detail records from an external HRMS system and hold them until a Financial Aid concurrent process consumes the rows and transfers the validated data into the permanent IGF_SE_PAYMENT table. Because the table functions purely as a landing zone, it plays a transient role in the payroll-to-aid disbursement flow: data is inserted by the external integration, processed by Financial Aid batch logic, and subsequently removed or marked processed.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification identifies this table as standalone. In practice this suggests treating IGF_SE_PAYMENT_INT as a source staging entity rather than a persistent hub, link, or satellite. Where a Data Vault model is desired downstream, TRANSACTION_ID would typically resolve to a hub (transaction/business key), while PAYROLL_ID and AUTH_ID combine as a secondary business key that could form a link to authorization and payroll hubs.

Key Information Stored

The table contains 19 documented columns. The most significant are grouped below.

• TRANSACTION_ID — surrogate primary key, enforced by index IGF_SE_PAYMENT_INT_PK and also carried by unique index IGF_SE_PAYMENT_INT_U1. This is the technical row identifier.
• PAYROLL_ID and AUTH_ID — together these form the unique business key IGF_SE_PAYMENT_INT_U2. PAYROLL_ID identifies the source payroll run; AUTH_ID is a foreign key to JTF_XML_INV_AUTHS, tying the payment to an authorization record.
• BATCH_ID — groups interface rows into a processing batch for the Financial Aid loader.
• PAYROLL_DATE — the effective date on which the payroll payment applies.
• PERSON_ID — the recipient (student or employee) associated with the payment.
• FUND_ID — the aid fund against which the payment is applied.
• LD_CAL_TYPE and LD_SEQUENCE_NUMBER — the academic calendar type and sequence, anchoring the payment to a specific award period.
• PAID_AMOUNT — the monetary value of the payment.
• HRS_WORKED — hours worked, relevant where the payment derives from work-study or hourly payroll.
• ORG_UNIT_CD — the organizational unit responsible for the payment.
• STATUS and ERROR_CODE — processing outcome indicators; STATUS flags whether the row is pending, processed, or rejected, while ERROR_CODE captures validation failure reasons.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns reflecting row provenance and change history.

Common Use Cases and Queries

Operational use cases center on monitoring and reconciliation of the inbound payroll interface. Typical scenarios include checking for unprocessed rows, isolating validation failures, and reconciling batch totals before the Financial Aid load runs.

A common pattern is identifying rows that failed validation:

• SELECT TRANSACTION_ID, PAYROLL_ID, PERSON_ID, ERROR_CODE FROM IGF_SE_PAYMENT_INT WHERE STATUS IS NULL OR ERROR_CODE IS NOT NULL;

Reconciliation by batch and fund is another frequent query, aggregating PAID_AMOUNT grouped by BATCH_ID and FUND_ID. Reporting for audit purposes joins AUTH_ID to JTF_XML_INV_AUTHS to confirm that each staged payment is backed by a valid authorization before it is posted to IGF_SE_PAYMENT. Support teams also query by PERSON_ID or PAYROLL_ID to trace individual disbursements during a payroll cycle.

Related Objects

The following objects are most significant in relation to IGF_SE_PAYMENT_INT:

• IGF_SE_PAYMENT — the destination table into which Financial Aid processing moves validated interface rows.
• JTF_XML_INV_AUTHS — referenced through the foreign key IGF_SE_PAYMENT_INT.AUTH_ID, providing authorization context for each payment.
• IGF_SE_PAYMENT_INT_PK — primary key constraint/index on TRANSACTION_ID.
• IGF_SE_PAYMENT_INT_U1 — unique index on TRANSACTION_ID.
• IGF_SE_PAYMENT_INT_U2 — unique business-key index on (PAYROLL_ID, AUTH_ID).
• External HRMS interfaces — the upstream source system populating the table.
• Financial Aid concurrent programs — the load process that reads from this table and writes to IGF_SE_PAYMENT.