Results for “igs_ad_app_req”

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

Overview

IGS_AD_APP_REQ is a table in the IGS (Student System) product schema of Oracle E-Business Suite, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to hold an applicant's application requirements, meaning the financial and administrative obligations an applicant must satisfy in order to complete an admission application. Within EBS, the table functions as the transactional intersection between an admission application record and the fee, payment, and accounting attributes that govern how that application is paid for and posted to the general ledger.

The table carries 31 documented columns at the 12.1.1 physical schema level. Based on the mined foreign key structure, the heuristic Data Vault classification for this object is link. This classification is offered as a modeling suggestion: the table records relationships and transactional associations between an admission application, an applicant's fee type and status, receivable and cash accounts, a posting control record, and a payment transaction extension, rather than serving as a standalone descriptive entity.

Key Information Stored

The surrogate primary key is APP_REQ_ID, uniquely identifying each application requirement row. Two additional unique indexes are documented. The first, IGS_AD_APP_REQ_PK, is defined on APP_REQ_ID. The second, ADAR_UK, is a composite business-key candidate defined on PERSON_ID and ADMISSION_APPL_NUMBER, tying the requirement record to a specific applicant and application. A third documented primary key, IGS_AD_APP_REQ_UK, is defined on PERSON_ID, ADMISSION_APPL_NUMBER, and APPLICANT_FEE_TYPE, reinforcing that an applicant may hold more than one requirement type per application.

The most significant columns include:

• APP_REQ_ID — system-generated surrogate identifier for the requirement row.
• PERSON_ID and ADMISSION_APPL_NUMBER — the business keys linking the requirement to the applicant and application.
• APPLICANT_FEE_TYPE and APPLICANT_FEE_STATUS — classify the fee obligation and track its lifecycle state.
• FEE_AMOUNT, FEE_DATE, and FEE_PAYMENT_METHOD — capture the monetary value, effective date, and tender used.
• REFERENCE_NUM — external or internal payment reference.
• CREDIT_CARD_CODE, CREDIT_CARD_NUMBER, CREDIT_CARD_EXPIRATION_DATE, CREDIT_CARD_STATUS_CODE, CREDIT_CARD_HOLDER_NAME, CREDIT_CARD_PAYEE_CD, and CREDIT_CARD_TANGIBLE_CD — payment card details and processing attributes.
• REV_ACCOUNT_CD, CASH_ACCOUNT_CD, REV_GL_CCID, and CASH_GL_CCID — receivable and cash account references plus their GL code combinations.
• GL_DATE and GL_POSTED_DATE — accounting date and the date the entry was posted to the ledger.
• POSTING_CONTROL_ID and TRXN_EXTENSION_ID — links to posting control and payment transaction extension records.
• NOMINATED_COURSE_CD and SEQUENCE_NUMBER — academic and ordering context.

Common Use Cases and Queries

Typical reporting scenarios include identifying unpaid or partially paid application fees, reconciling fee revenue against GL postings, and auditing credit-card transactions associated with applications. A representative query joining the table to the application header is:

SELECT r.APP_REQ_ID, r.PERSON_ID, r.ADMISSION_APPL_NUMBER, r.APPLICANT_FEE_TYPE, r.APPLICANT_FEE_STATUS, r.FEE_AMOUNT, r.GL_POSTED_DATE FROM IGS.IGS_AD_APP_REQ r WHERE r.PERSON_ID = :person_id AND r.ADMISSION_APPL_NUMBER = :appl_number;

Unposted fee activity is commonly extracted with a filter such as WHERE GL_POSTED_DATE IS NULL AND FEE_AMOUNT IS NOT NULL, while account analysis groups rows by REV_ACCOUNT_CD and CASH_ACCOUNT_CD. Status reporting typically filters on APPLICANT_FEE_STATUS to monitor outstanding requirements.

Related Objects

The most significant related objects, drawn from the documented foreign keys, are:

• IGS_AD_APPL_ALL — joined on PERSON_ID and ADMISSION_APPL_NUMBER; the parent application header.
• IGS_AD_CODE_CLASSES — joined on APPLICANT_FEE_STATUS; supplies status code meanings.
• IGS_FI_ACC_ALL — joined on REV_ACCOUNT_CD and CASH_ACCOUNT_CD; source of receivable and cash account definitions.
• AR_POSTING_CONTROL — joined on POSTING_CONTROL_ID; governs the GL posting run.
• IBY_FNDCPT_TX_EXTENSIONS — joined on TRXN_EXTENSION_ID; holds payment transaction extension data.

Together these relationships establish IGS_AD_APP_REQ as the central link between admissions data, fee processing, and financial accounting within the IGS Student System.