Search Results gl_journal_import_s




Overview
Explore in AI Chat

Overview

The APPS.GL_INTERFACE_CONTROL_PKG package body provides the low-level control logic that governs how journal entry data is staged, validated, and processed through the Oracle General Ledger interface tables. Its primary business function is to manage the GL_INTERFACE_CONTROL records that track each run of the Journal Import process. Every time journal data is loaded into the GL interface tables — whether through a feeder system, an external conversion, or a subledger transfer — a control row must exist to identify the run, group the incoming lines, and give the Journal Import concurrent program a way to locate the unprocessed data. This package supplies the mechanisms that create, validate, and identify those control rows. The dependency list confirms that the package is used almost exclusively within the Journal Import pipeline: it references GL_INTERFACE_CONTROL, GL_INTERFACE_CONTROL_S, GL_JE_SOURCES, and GL_JOURNAL_IMPORT_S.

Key Procedures and Functions

The ETRM metadata documents six callable units:

  • GET_UNIQUE_RUN_ID — Returns a unique run identifier for a Journal Import execution, ensuring that concurrently staged interface data can be distinguished from prior or parallel runs.
  • GET_UNIQUE_ID — Generates or retrieves a unique identifier used to key individual control or interface records.
  • CHECK_UNIQUE — Verifies the uniqueness of a proposed run identifier or control record before insertion, preventing collisions in the interface control table.
  • USED_IN_ALTERNATE_TABLE — Determines whether a given identifier or run is already referenced in an associated interface table, guarding against duplicate or conflicting processing.
  • GET_INTERFACE_TABLE — Returns the interface table associated with a given run or source, directing Journal Import to the correct staging area.
  • INSERT_ROW — Inserts a new control row into GL_INTERFACE_CONTROL for a Journal Import run.

Exact parameter lists are not represented in the available metadata and are therefore not enumerated here.

Tables Accessed

The package reads and writes the following objects, all accessed through APPS synonyms:

  • GL_INTERFACE_CONTROL — the primary table managed by the package; holds one control row per interface run.
  • GL_INTERFACE_CONTROL_S — the sequence supplying unique identifiers for new control rows.
  • GL_JE_SOURCES — the journal source definition, validated to confirm a legitimate source before a run is created.
  • GL_JOURNAL_IMPORT_S — the sequence used to generate unique run identifiers for Journal Import.
  • DUAL — used for single-row sequence and validation queries.

Error handling draws on APP_EXCEPTION, APP_EXCEPTIONS, and FND_MESSAGE.

Usage Notes

GL_INTERFACE_CONTROL_PKG is not referenced by any other database object according to the dependency report, although the ETRM metadata notes it is referenced by five other packages through the interface workflow. It is therefore invoked primarily by Oracle's delivered Journal Import concurrent program and by the standard GL interface forms, and by custom feeder code that must register a control row before loading journal lines. Custom code should call this package rather than inserting directly into GL_INTERFACE_CONTROL, so that run identifiers remain unique and consistent with Journal Import expectations. The package is valid in both 12.1.1 and 12.2.2, with no documented behavioral divergence.