Search Results igi_post_gl_posting

Overview

IGI_POST is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM metadata as an "OTHER" API type. The package forms part of the IGI (Internal Controls Manager / Governance, Risk and Compliance) product family shipped with EBS 12.1.1 and 12.2.2. Its central responsibility is to drive the transfer of subledger accounting entries into the Oracle General Ledger by initiating and managing a General Ledger posting run. In effect, it acts as the bridge between the IGI module's posting activity and the core GL journal tables, allowing accounting events captured within IGI to be consolidated into journal batches, headers, and lines suitable for GL posting.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the definer. This design causes the package to respect the caller's security context, which is significant because GL posting affects critical financial data and must observe the appropriate access controls and MOAC (Multi-Org Access Control) settings of the session.

Key Procedures and Functions

The documented metadata identifies a single entry point:

• IGI_POST_GL_POSTING — This is the sole documented procedure in the package. It accepts a posting run identifier that ties the invocation to a specific posting run record, and uses that identifier to orchestrate the GL posting process. Its purpose is to take the accounting entries associated with the specified posting run and submit them for General Ledger processing. The procedure carries out the work required to move the IGI-side data into the GL journal structures and is the only public routine exposed by the package specification.

No further procedures or functions are documented, and the parameter list beyond the posting run identifier should not be assumed beyond what the metadata provides.

Tables Accessed

The package references three core General Ledger tables through APPS synonyms, consistent with its posting role:

• GL_JE_BATCHES — Stores journal entry batches that group related journal headers for posting, control totals, and audit tracking.
• GL_JE_HEADERS — Holds individual journal entries, including their status, currency, and posting attributes.
• GL_JE_LINES — Contains the individual debit and credit lines that make up each journal entry.

Together these three tables represent the standard GL posting schema. The procedure reads and writes these objects as it assembles or updates the batches, headers, and lines associated with the posting run, ultimately enabling the entries to be posted to the General Ledger.

Usage Notes

IGI_POST is an internal supporting package rather than a standalone business-facing API. It is typically invoked programmatically, either from a concurrent program that schedules or triggers a posting run, from Oracle Forms within the IGI/GL user interface, or from other PL/SQL packages that need to post IGI accounting entries. The metadata confirms that the package is referenced by one other package, indicating it is called from within the application's own code base rather than being designed for direct end-user execution.

Because it is a low-level posting utility, it should be invoked with valid, committed posting run data and within a session that holds appropriate GL posting privileges. Customizations should call the package only after the source entries are fully staged, since the procedure operates on GL journal tables that are central to financial reporting integrity. The fixed $Header reference (igiposts.pls 120.4.12020000.1) indicates the package was last revised in the 12.2 code line, so behavior should be validated against the specific patch level in use.