Search Results transaction_dt




Overview
Explore in AI Chat

Overview

IGS_FI_ANC_INT is a view owned by the APPS schema in Oracle E-Business Suite, defined over the Student Systems (IGS) financials ancillary interface table. It exposes the staging and interface records used when ancillary charges or credits are transferred into the Oracle Financials sub-ledgers, in particular Receivables, through the Oracle Student System integration points. The view is a thin projection: its SELECT list maps the underlying interface table columns one-for-one, adding only the ROWID pseudocolumn aliased as ROW_ID. As a result, it behaves as an updatable interface view rather than a reporting-only construct, and it is typically referenced by concurrent programs, APIs, and custom interfaces that populate, validate, or release ancillary transactions.

In Oracle EBS 12.1.1 and 12.2.2 the object name, column list, and ownership are unchanged. Because it is an APPS-owned view, it is accessible to any database user granted the standard APPS synonym and privileges, and ETRM documents it as a supported reference object for integration and troubleshooting.

Underlying Base Objects

ETRM documents no referenced base objects for this view, and the view text itself does not expose a fully-qualified FROM clause in the excerpt. In practice the view is defined over the ancillary interface entity maintained by the Oracle Student System financials module, whose primary key is ANCILLARY_INT_ID. The view performs no joins, aggregations, or filters; every column is a direct pass-through of the base table column. This means cardinality, uniqueness, and column semantics are identical to those of the base table, and any DML issued against the view is directed to that single base segment unless INSTEAD OF triggers exist.

Key Columns

  • ROW_ID — the base table ROWID, useful for row identification in update and delete operations.
  • ANCILLARY_INT_ID — primary identifier of the ancillary interface record.
  • PERSON_ID and PERSON_ID_TYPE — the party or person reference and the type discriminator that qualifies it.
  • API_PERSON_ID — the person identifier expected by the receiving API; the column most frequently searched by integration developers because of the mismatch between internal PERSON_ID and the identifier the Financials API requires.
  • STATUS, VALIDATION_FLAG, ERROR_MSG — the processing state of the record, the result of validation, and any message raised when the record failed.
  • FEE_TYPE, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — the fee definition, calendar type, and calendar instance sequence to which the ancillary amount belongs.
  • OVERRIDE_DR_REC_ACCOUNT_CD / CCID and OVERRIDE_CR_REV_ACCOUNT_CD / CCID — account overrides for the debit receivable and credit revenue lines, supplied either as a flexfield code combination or as its CCID.
  • EFFECTIVE_DT and TRANSACTION_DT — the accounting effective date and the transaction date carried into Financials.
  • ORG_ID — the operating unit that owns the transaction.
  • ANCILLARY_ATTRIBUTE1..15 and ATTRIBUTE_CATEGORY / ATTRIBUTE1..20 — descriptive flexfield and descriptive columns available for client-specific data.
  • REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit context identifying the run that created or last touched the row.
  • CREATED_BY, CREATION_DATE, LAST_UPDAT... — standard WHO audit columns tracking creation and last update.

Common Use Cases and Queries

The principal use case is monitoring the ancillary interface ahead of the transfer to Receivables. Support and integration teams query rows by status or validation flag to find failures, and join API_PERSON_ID back to the person or party tables when the receiving API rejects a record.

  • List of unprocessed records for an operating unit:

SELECT ANCILLARY_INT_ID, PERSON_ID, API_PERSON_ID, FEE_TYPE, EFFECTIVE_DT, VALIDATION_FLAG FROM APPS.IGS_FI_ANC_INT WHERE ORG_ID = :p_org_id AND VALIDATION_FLAG = 'N';

  • Diagnose API_PERSON_ID mismatches:

SELECT ANCILLARY_INT_ID, PERSON_ID, PERSON_ID_TYPE, API_PERSON_ID, ERROR_MSG FROM APPS.IGS_FI_ANC_INT WHERE API_PERSON_ID IS NULL OR ERROR_MSG IS NOT NULL;

  • Audit a specific concurrent request:

SELECT ANCILLARY_INT_ID, STATUS, TRANSACTION_DT, REQUEST_ID, CREATED_BY, CREATION_DATE FROM APPS.IGS_FI_ANC_INT WHERE REQUEST_ID = :p_request_id ORDER BY ANCILLARY_INT_ID;

Because the view is a direct projection, these queries can be extended to any attribute column, and updates to STATUS, VALIDATION_FLAG, ERROR_MSG, or the account override columns are written through to the interface table, allowing corrective DML prior to reprocessing.