Search Results get_interface_table




Overview
Explore in AI Chat

Overview

APPS.GL_INTERFACE_CONTROL_PKG is a PL/SQL package in the Oracle E-Business Suite General Ledger module responsible for validation and insertion routines against the GL_INTERFACE_CONTROL table. This table acts as the control mechanism for the Journal Import process, tracking each interface run and the source/group/ledger combinations submitted to it. The package supplies the utility functions that Journal Import and related programs use to generate unique run and group identifiers, confirm that a given combination of journal source, ledger, and group has not already been processed within a run, and determine whether a journal source is populated through an interface table other than GL_INTERFACE. It also encapsulates the logic to retrieve the correct interface table name and to insert control rows. The package is one of the lower-level infrastructure components of the GL import architecture and is invoked indirectly by concurrent programs and forms rather than being called directly by end users. Its header comment ($Header: glijicts.pls 120.6 2005/06/17) indicates a long-lived, stable code base originally authored in 1993 by D. J. Ogg.

Key Procedures and Functions

  • GET_UNIQUE_RUN_ID — Returns the next unique interface run identifier. Journal Import calls this to stamp every control and interface row belonging to a single import execution with the same run ID.
  • GET_UNIQUE_ID — Returns the next unique group identifier used to distinguish a batch of journal lines within an import run.
  • CHECK_UNIQUE — Verifies that the combination of interface run, journal source, ledger, and group ID is unique within the run, raising an error if a duplicate control row is detected. It receives the run ID, the translated (user-facing) source name, the internal source name, ledger ID, optional group ID, and the current row identifier.
  • USED_IN_ALTERNATE_TABLE — Examines whether a given interface journal source has data resident in an interface table other than GL_INTERFACE, returning 'Y' or 'N'. This allows Journal Import to route processing appropriately for sources such as subledger feeders.
  • GET_INTERFACE_TABLE — Returns the name of the interface table associated with a given journal source, resolving the correct staging table for import processing. This is the routine most directly relevant to the user's search term.
  • INSERT_ROW — Inserts a control row into GL_INTERFACE_CONTROL, registering a source/group/ledger combination for import.

Tables Accessed

  • GL_INTERFACE_CONTROL — The primary table maintained by this package; receives inserted control rows and is queried for uniqueness validation.
  • GL_INTERFACE_CONTROL_S — The companion sequence/seed table used in conjunction with control row numbering.
  • GL_JE_SOURCES — Consulted to translate between user-facing and internal journal source names and to determine source attributes such as whether an alternate interface table applies.
  • GL_JOURNAL_IMPORT_S — The Journal Import sequence used to derive unique run and group identifiers.
  • DUAL — Used by the sequence-based functions to return a single value.

Usage Notes

The package is normally invoked indirectly. The Journal Import concurrent program (GLJIMPTC) and related GL import routines call GET_UNIQUE_RUN_ID, GET_UNIQUE_ID, CHECK_UNIQUE, GET_INTERFACE_TABLE, and INSERT_ROW to establish and validate control records before processing interface lines. Its functions are also referenced by other PL/SQL packages within APPS — the ETRM metadata records five dependent packages — and by custom code that loads data into GL_INTERFACE and needs to register the load as a controlled run. Because the package is a low-level utility with no direct form or concurrent program submission path, developers typically call its functions from within their own import logic. When integrating external data into General Ledger on release 12.1.1 or 12.2.2, use GET_INTERFACE_TABLE to resolve the correct staging table for the source and CHECK_UNIQUE before inserting control rows, ensuring source/group/ledger integrity across a single import run.