Results for “fnd_imp_lang_summary”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_IMP_LANG_SUMMARY is a table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. It is a VALID database object in both the 12.1.1 and 12.2.2 releases. The table functions as an implementation and DBA data repository, capturing summary-level statistics that relate translation activities to specific patch and bug identifiers during the language implementation and patching lifecycle. In practice, the table records aggregated counts of translation requests associated with a given snapshot, patch, and bug registration, providing administrators and DBAs a consolidated view of translation workload per implementation event.

From a heuristic Data Vault modeling perspective — mined from the foreign key structure documented in the ETRM metadata — FND_IMP_LANG_SUMMARY is classified as a standalone object. This classification suggests that the table does not participate in a conventional hub-and-satellite pattern driven by a business key lineage within the documented relationship graph; rather, it may be modeled as an independent satellite or reference table anchored only by the snapshot relationship. The sole documented foreign key (SNAPSHOT_ID) referencing AHL_SNAPSHOTS indicates the table is largely self-contained from a referential standpoint.

Key Information Stored

The documented physical schema for FND_IMP_LANG_SUMMARY in release 12.2.2 comprises four columns. All four are significant to the table's purpose:

• SNAPSHOT_ID — The functional key linking this summary record to a specific snapshot stored in AHL_SNAPSHOTS. This is the only documented foreign key and serves as the primary correlation point for the summary row.
• BUG_NO — The bug or defect number associated with the translation activity being summarized, typically originating from the bug tracking system used to drive patch content.
• REQ_TRANS_CNT — The count of requested translations, providing the quantitative measure that gives the summary its analytical value.
• PATCH_ID — The identifier of the patch with which the summarized translation requests are associated, enabling correlation of translation effort to a specific patch deployment.

Because only four columns are documented, no surrogate primary key or unique business-key index is explicitly visible in the ETRM metadata beyond the SNAPSHOT_ID relationship. In application practice, the effective key is likely the combination of SNAPSHOT_ID, BUG_NO, and PATCH_ID, which together identify a unique translation-summary line.

Common Use Cases and Queries

Typical usage centers on implementation and patching analysis. DBAs and system administrators query this table to assess translation scope before or after applying a patch, and to audit which bugs drove the largest translation loads. A representative query joining to the snapshot source follows:

• Reporting total translation requests per patch: SELECT PATCH_ID, SUM(REQ_TRANS_CNT) FROM FND_IMP_LANG_SUMMARY GROUP BY PATCH_ID;
• Correlating translation counts to snapshots: SELECT s.*, f.BUG_NO, f.REQ_TRANS_CNT FROM FND_IMP_LANG_SUMMARY f JOIN AHL_SNAPSHOTS s ON f.SNAPSHOT_ID = s.SNAPSHOT_ID;
• Identifying high-volume bugs affecting language implementation for prioritization.
• Supporting capacity planning during language pack installation by quantifying translation request volumes.

Related Objects

The principal documented relationship is with AHL_SNAPSHOTS, joined on the SNAPSHOT_ID column. Additional contextually related objects in the FND patching and language implementation domain include FND_PATCHES and the AD (Applications DBA) patch driver tables, which provide the PATCH_ID and bug context referenced here. Bug-related reference data maintained by the bug tracking system supplies the BUG_NO. Administrators commonly combine FND_IMP_LANG_SUMMARY with FND_IMP_LANG_SUMMARY-adjacent translation and NLS tables when validating the completeness of a language installation, though the documented FK structure identifies AHL_SNAPSHOTS as the primary and sole referential dependency.