Search Results translate_row

Overview

FND_APPLICATION_PKG is a foundational Oracle E-Business Suite (EBS) PL/SQL package owned by the APPS schema that manages metadata for registered Oracle Applications. The FND_APPLICATION table and its related translation and sequence tables form the central registry of every Oracle product installed in an EBS instance — including the application short name, basepath, descriptive name, and associated product code. FND_APPLICATION_PKG encapsulates the DML operations required to maintain that registry, providing a controlled API layer over direct table manipulation. In EBS 12.1.1 and 12.2.2, this package is classified as an "OTHER" API and is used primarily by Oracle's application registration and patching utilities, as well as by customers who must register custom or third-party applications before their schema and concurrent programs become usable within the EBS framework.

The header comment ($Header: AFSCAPPS.pls 120.3 2005/10/05) indicates the package has been stable since the early R12 timeframe, with the core DML and loader logic unchanged across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

• INSERT_ROW — Inserts a new application registration row, populating the application ID, short name, basepath, name, description, and audit columns (creation/last update date, user, login). It also supports an optional product code.
• LOCK_ROW — Acquires a row-level lock on an existing FND_APPLICATION row identified by its key attributes. Typically invoked before an update to enforce concurrency control.
• UPDATE_ROW — Modifies an existing application registration, updating short name, basepath, name, description, and audit columns.
• LOAD_ROW — Standard Oracle EBS loader entry point used by seed-data and translation-loading (XLA/seed) concurrent programs. It accepts the short name, owner, basepath, name, description, and optional product code, performing an upsert so that shipped application definitions can be inserted or refreshed without duplicating rows.
• Overloaded LOAD_ROW version #1 — Extends the base loader with a custom mode indicator and a last-update-date (string) parameter, permitting controlled, deployment-aware loading behavior.
• Overloaded LOAD_ROW version #2 — Accepts an explicit application ID alongside the short name, supporting deterministic identification when loading specific registrations.
• TRANSLATE_ROW — Populates or maintains translated application name and description records, driving the FND_APPLICATION_TL table.
• DELETE_ROW — Removes an application registration row.
• ADD_LANGUAGE — Inserts translation rows for a new language into the translation tables, extending application metadata to installed languages.

Tables Accessed

• FND_APPLICATION — The primary registration table holding application ID, short name, basepath, name, description, and audit columns.
• FND_APPLICATION_S — The sequence/primary-key source for application IDs, ensuring unique identifiers.
• FND_APPLICATION_TL — Translation table storing language-specific application names and descriptions.
• FND_LANGUAGES — Reference to installed/registered languages, consulted by ADD_LANGUAGE and TRANSLATE_ROW.
• DUAL — Used for single-row queries such as sequence retrieval and existence checks.

Usage Notes

Application registration is a privileged operation normally performed during installation, patching, or setup of an EBS instance. FND_APPLICATION_PKG is not typically invoked from the standard Oracle Forms UI; instead it is called by Oracle's internal registration and seed-data utilities, the AD (Applications DBA) patching infrastructure, and translation-loader concurrent programs. In EBS 12.2, application registration must also align with the online patching (adop) file system model, so the basepath parameter takes on additional significance. The LOAD_ROW overloads are the entry points reported by Oracle's seed-data loader (FNDLOAD-style) mechanisms. Custom integrators who need to register a third-party product schema, a custom application, or a localization typically call INSERT_ROW or LOAD_ROW from a custom PL/SQL script or concurrent program rather than writing directly to FND_APPLICATION, ensuring audit columns, ID generation, and translation consistency are handled correctly. Because registration affects the entire EBS instance, such calls should be executed only under controlled, tested change procedures, with appropriate backups of the FND_APPLICATION family of tables.