Search Results delete_line

Overview

GL_IMPORT_REFERENCES_PKG is a maintenance package in the Oracle EBS General Ledger module, owned by the APPS schema. Its business function is to purge or remove journal import reference data from the GL_IMPORT_REFERENCES table. The GL_IMPORT_REFERENCES table stores cross-references between General Ledger journal lines and their originating subledger or external source records, allowing drill-down and reconciliation from GL back to the subledger. Because this table grows rapidly in high-volume environments, the package provides controlled deletion routines that operate at the line, header, and batch levels, preserving referential integrity while allowing administrators to reclaim space or correct import anomalies.

The package is classified as OTHER in the ETRM metadata, indicating it is a utility/maintenance API rather than a formal business API. It exposes four documented procedures. Its source header (gliimrfs.pls 120.2) dates to 2005, and the object is referenced by two other packages, confirming its role as a shared utility within the GL import framework.

Key Procedures and Functions

• DELETE_LINE — Deletes a single GL_IMPORT_REFERENCES record identified by header and line number. The user search term "delete_line" maps directly to this procedure. It accepts a header ID and a line number, with the line number being unique within the header, making it suitable for surgical removal of one import reference.
• DELETE_LINES — Deletes all import reference lines belonging to a given header. It accepts the header ID and is used to clear the complete line set for one journal header without removing the header record itself.
• DELETE_HEADER — Deletes all lines associated with a given header. Functionally similar to DELETE_LINES in scope but named to reflect header-level cleanup semantics.
• DELETE_BATCH — Deletes all import reference lines for a given batch, identified by batch ID. This is the broadest deletion scope, designed to purge an entire journal import batch in a single call.

No return values are documented; each procedure is a void DML operation. Parameter names referenced in the documentation follow the X_header_id, X_line_num, and X_batch_id naming convention.

Tables Accessed

The package operates primarily on GL_IMPORT_REFERENCES, which holds the import reference rows targeted by all four procedures. The ETRM metadata also lists GL_JE_HEADERS as a referenced table, which supplies the header context needed to scope line-level deletions (for example, validating a header before removing its lines). Both tables are accessed through APPS synonyms, and no other tables are documented.

Usage Notes

GL_IMPORT_REFERENCES_PKG is typically invoked from custom PL/SQL maintenance scripts, corrective data-fix routines, or concurrent programs that purge journal import reference data after posting or reconciliation is complete. It is not a user-facing API and is generally called programmatically rather than from an Oracle Forms screen. Because deletions require a valid header or batch identifier, callers should resolve the correct IDs before invocation. The procedures do not publish return status; error handling must be managed by the calling program. Given that this table supports GL drill-down and audit capability, retention policies and reversal impacts should be evaluated before executing any delete operation. The documented call patterns — delete_line(header_id, line_num), delete_lines(header_id), delete_header(header_id), and delete_batch(batch_id) — reflect a simple, defensive interface appropriate for administrative purge tasks.