Search Results chk_liability_acc




Overview
Explore in AI Chat

Overview

IGS_FI_GEN_APINT is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Student System (formerly Oracle iLearning/Student Systems, module prefix IGS) integration layer with Oracle Financials. The package is compiled with AUTHID CURRENT_USER, meaning its SQL and PL/SQL execute under the privilege domain of the calling user rather than the package owner, a design typical of shared utility packages invoked from concurrent programs, forms, and other packages across the EBS instance. Its header identifies creation by Sanil Madathil (Oracle IDC) on 20-Feb-2003, and the last recorded source revision is version 115.4 dated 03-Jul-2003.

Functionally, IGS_FI_GEN_APINT supports the interface between student-system financial data and Oracle Payables/general ledger constructs. It centralizes reusable validation and description-derivation logic — for example, checking whether a liability account code combination is valid and resolving descriptive text for account segments and unit/section academic structures — so that multiple calling programs apply consistent accounting rules. The package is referenced by six other packages, confirming its role as a shared dependency rather than a standalone entry point.

Key Procedures and Functions

  • CHK_LIABILITY_ACC — Returns a BOOLEAN indicating whether the supplied liability account code combination identifier is valid. It is the documented mechanism for validating Liability Account CCID combinations before financial processing.
  • GET_RFND_DESTINATION — Returns a VARCHAR2 value representing the refund destination. It is used to determine where a refund should be directed when processing student financial transactions.
  • GET_UNIT_SECTION_DESC — Returns a VARCHAR2 description for a unit/section. This is the function surfaced by the user's search term. Its signature accepts a unit offering option identifier plus optional context parameters (unit code, version number, calendar type, calendar instance sequence number, location code, and unit class), allowing callers to resolve a descriptive value with varying degrees of contextual specificity.
  • GET_SEGMENT_NUM — A procedure that returns the segment number through an OUT parameter, used to identify a key flexfield segment by position.
  • GET_SEGMENT_DESC — Returns a VARCHAR2 description for a given segment number and natural account segment value, providing human-readable accounting segment text.

Tables Accessed

The package reads several APPS-owned tables through synonyms. FND_ID_FLEX_SEGMENTS and FND_SEGMENT_ATTRIBUTE_VALUES supply key flexfield structure and segment attribute metadata used by GET_SEGMENT_NUM and GET_SEGMENT_DESC, and support liability account validation in CHK_LIABILITY_ACC. IGS_FI_CONTROL_ALL holds student financials control settings, typically consulted for liability account and refund configuration. IGS_CA_INST_ALL stores calendar instance data, referenced when resolving calendar type and sequence context in GET_UNIT_SECTION_DESC. IGS_PS_UNIT_OFR_OPT_ALL holds unit offering option records — the primary source for unit/section descriptions returned by GET_UNIT_SECTION_DESC.

Usage Notes

Consistent with its documented usage line, IGS_FI_GEN_APINT is invoked from concurrent jobs and Oracle Forms. Typical scenarios include student financials transaction processing, refund handling, and account validation during payable interface runs, where callers need either a validation result or a descriptive string without duplicating flexfield and student-structure lookups. Because the package is referenced by six other packages, it is normally called indirectly rather than directly from end-user forms. Customizations should treat it as a dependency-sensitive shared object: changes to function behavior can ripple into dependent packages. The absence of creation-record change history in the header and the 2003 source revision indicate this is long-standing seeded code, so extensions are best implemented through wrapper logic rather than modification of the package body.