Search Results crdt_decision_ovrd_code

Overview

IGF.IGF_SL_COD_TEMP is a transient staging table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schema owned by the IGF (Financial Aid / Student Loan) application. As documented in the ETRM metadata, it is described as a table containing information about response codes, and is explicitly designated as a dummy table used in the COD (Common Origination and Disbursement) XML Inbound process. It therefore serves as a temporary landing area where inbound COD XML payloads — parsed into a structured row-per-record form — are held prior to validation, transformation, and propagation to permanent loan, disbursement, and promissory note tables. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10 and is indexed in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. This suggests the object behaves less like a conformed hub or link and more like a staging or temporary satellite, capturing descriptive attributes keyed by a composite identifier rather than participating in formal referential relationships with other EBS entities.

Key Information Stored

The table holds 37 documented columns. The most operationally significant include:

• REC_ID and LEVEL_CODE — together forming the unique primary key index IGF_SL_COD_TEMP_PK. These are the surrogate/business identifiers identifying each inbound record and its level within the COD XML hierarchy.
• RESP_CODE — the response code returned for the processed record, central to the table's stated purpose.
• DOC_TYPE_CODE and DOC_STATUS_CODE — the document type and its processing status within the inbound flow.
• CRDT_DECISION_STATUS, CRDT_DECISION_DATE, and CRDT_DECISION_OVRD_CODE — credit decision status, date, and any override code, matching the user's search term "crdt_decision_status."
• PNOTE_MPN_ID, MPN_STATUS_CODE, and MPN_LINK_FLAG — promissory note identifiers, status, and linkage flags.
• PYMT_SERVICER_AMT, BOOK_LOAN_AMT, ENDORSER_AMT, and YTD_DISB_AMT — monetary amounts associated with servicing, book loans, endorsers, and year-to-date disbursements.
• PROCESS_DATE and standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID) — supporting concurrency control, audit, and concurrent-program traceability.

Common Use Cases and Queries

The dominant use case is inspecting and troubleshooting COD XML inbound processing. Because the table is a dummy/staging object, data is typically short-lived and is purged or superseded after the inbound concurrent program completes. Typical queries include:

• Retrieving all records for a specific inbound run:
  SELECT rec_id, level_code, resp_code, doc_status_code, crdt_decision_status FROM igf.igf_sl_cod_temp WHERE request_id = :p_request_id;
• Identifying records where credit decisions were overridden:
  SELECT rec_id, crdt_decision_status, crdt_decision_ovrd_code, crdt_decision_date FROM igf.igf_sl_cod_temp WHERE crdt_decision_ovrd_code IS NOT NULL;
• Reconciling monetary amounts and promissory note link status for a given MPN identifier:
  SELECT pnote_mpn_id, mpn_status_code, mpn_link_flag, pymt_servicer_amt, book_loan_amt FROM igf.igf_sl_cod_temp WHERE pnote_mpn_id = :p_mpn_id;

Reporting use cases center on inbound error diagnostics and audit trails of the COD response codes received from the federal processor.

Related Objects

The metadata classifies this object as standalone, meaning no foreign key dependencies were mined. Consequently, related-object identification relies on functional coupling rather than documented FK joins. Anticipated related objects include the permanent COD response and loan tables in the IGF schema that receive transformed data after staging, the COD XML inbound concurrent program (referenced through PROGRAM_ID and REQUEST_ID), and IGF student loan and promissory note tables joined on PNOTE_MPN_ID or REC_ID. Because the object is a dummy staging table, it should not be treated as a system of record; consumers should prioritize the downstream permanent tables for authoritative reporting.