Search Results fnd_entity_tab

Overview

FND_LOADER_OPEN_INTERFACE_PKG is an Oracle E-Business Suite 12.1.1 / 12.2.2 PL/SQL package owned by the APPS schema and classified under the ETRM "OTHER" API category. It provides the programmatic foundation of the FND Loader (FNDLOAD) open-interface mechanism, which externalizes Oracle EBS configuration and definition data as flat .lct (loader control) and .ldt (loader data) files. The package manages the staging area used to queue, organize, and process loader requests before the loader engine consumes them.

Its central responsibility is batch management. Each request to load or extract an entity — a concurrent program, a profile option, a responsibility, a menu, or a similar configuration object — is captured as a "batch" row in the open-interface table. The package allows callers to create batches, append rows to an existing batch, lock a batch against concurrent modification, delete completed batches, and clean up the staging table. The "lock_batch" operation matters because FNDLOAD processing can be long-running; a lock prevents a second caller from mutating the same batch while the loader is consuming it. Batches hold the file names, loader mode (UPLOAD, DOWNLOAD, UPLOAD_PARTIAL), entity name, and optional parameters that describe a single loader job.

Key Procedures and Functions

The documented interface exposes six callable objects plus a set of collection types.

• INSERT_BATCH (function) — Creates a new batch in FND_LOADER_OPEN_INTERFACE from a set of collection types: FND_LCT_TAB, FND_LDT_TAB, FND_BATCH_ID_TAB, FND_SEQ_IN_BATCH_TAB, FND_LOADER_MODE_TAB, FND_ENTITY_TAB, and FND_PARAMS_TAB. Returns the generated batch identifier.
• INSERT_BATCH (overloaded, no-argument form) — Provides a default/simplified entry point for inserting a batch.
• DELETE_BATCH — Purges all rows belonging to a specified batch_id from the open-interface table. Typically invoked after a loader run completes successfully or is abandoned.
• ADD_ROW_TO_BATCH — Appends one or more additional records to an existing batch, allowing incremental assembly of a loader payload across multiple calls.
• LOCK_BATCH — Acquires a lock on a batch so that concurrent sessions cannot process or delete it simultaneously. This is the operation most commonly searched for under the keyword "lock_batch" and is implemented using DBMS_LOCK.

Because ETRM classifies the API as "OTHER", callers should not assume a formally versioned public contract; signature stability is not guaranteed across patches.

Tables Accessed

• FND_LOADER_OPEN_INTERFACE — The primary staging table. Insert, delete, update, and lock operations all target this table, which stores batch_id, sequence-in-batch, LCT/LDT file names, loader mode, entity, and parameter strings.
• FND_LOADER_OPEN_INTERFACE_S — The sequence backing the batch_id and sequence-in-batch generation used by INSERT_BATCH and ADD_ROW_TO_BATCH.
• DBMS_LOCK — Supplied Oracle package used by LOCK_BATCH to obtain an exclusive lock handle for a batch.
• DUAL — Used for singleton SELECTs and sequence value retrieval.
• PLITBLM — Internal PL/SQL table-management package referenced for collection handling.

Usage Notes

The package is normally invoked indirectly rather than typed by end users. Typical entry points include FNDLOAD command-line execution, the "Load" and "Extract" concurrent programs that stage data into the open-interface table before a loader worker consumes it, and custom forms or OAF pages that submit loader jobs. Custom code should only call these procedures when it must emulate the FNDLOAD staging workflow.

The recommended sequence is: INSERT_BATCH to create a batch, ADD_ROW_TO_BATCH to populate it, LOCK_BATCH to freeze it before processing, then DELETE_BATCH to clean up. Because only one dependent package references this API in the ETRM graph, integrations are sparse and brittle. Always COMMIT after the insert and add steps, and avoid holding a batch lock for longer than the loader run itself to prevent lock-timeout contention in DBMS_LOCK.