Results for “language_code”

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

Overview

AD_SEED_DATA_LOADED is a table owned by the APPLSYS schema within the Applications DBA (AD) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to record the languages in a patch for which seed data loading has completed. Seed data consists of the reference and setup rows that Oracle ships with the application — flexfield definitions, lookup values, profile options, menu entries, and similar metadata — which must be loaded into the database in each installed language. During patch application, the AD utilities track this per-language load activity, and AD_SEED_DATA_LOADED serves as the completion ledger for that process.

The table is documented with four columns and a single foreign key to AD_APPLIED_PATCHES, making it a child of the patch application record set. Under the heuristic Data Vault classification mined from the foreign key structure, this object is identified as standalone. From a modeling perspective, it is better understood as a satellite-like detail table: its grain is one row per patch per language, and its identity is derived from the parent patch plus the language rather than from an independently generated key. It has no dependent children of its own.

Key Information Stored

The documented physical schema contains four columns. The relationships and semantics of each are as follows:

• APPLIED_PATCH_ID — The foreign key to AD_APPLIED_PATCHES. This column identifies the patch whose seed data load is being tracked and is the primary business-key component of the row.
• LANGUAGE_CODE — The language in which seed data loading completed for the identified patch. Together with APPLIED_PATCH_ID, this forms the natural composite business key that makes each row unique: one record per patch per language.
• CREATION_DATE — The date the row was inserted, effectively the timestamp at which the language's seed data load completed.
• LAST_UPDATE_DATE — The date the row was last modified, supporting the standard EBS audit convention maintained by the APPLSYS audit columns.

The metadata does not document a separate surrogate primary key column or a named unique index. Because the row has no independent identifier, the effective unique key is the combination of APPLIED_PATCH_ID and LANGUAGE_CODE, with the two date columns acting as audit attributes rather than key members.

Common Use Cases and Queries

The primary use case is diagnosing multilingual patch application. After a patch run, DBAs and support analysts query this table to confirm that seed data loading finished for every installed language, and to find patches where one or more languages are missing — a common cause of untranslated lookups, flexfield values, or messages after an upgrade.

A typical completeness check joins the table to AD_APPLIED_PATCHES and compares expected languages against loaded ones:

• List all languages recorded for a given patch: SELECT language_code, creation_date FROM applsys.ad_seed_data_loaded WHERE applied_patch_id = :patch_id ORDER BY language_code;
• Identify patches with incomplete language coverage: compare the distinct language codes in this table against the languages installed in the environment (for example via FND_LANGUAGES) for the same applied patch.
• Trace load timing: use CREATION_DATE and LAST_UPDATE_DATE to determine when a language's seed load completed relative to the patch's overall run, useful when correlating with AD patch log files.

These queries are read-only reporting patterns; the table is populated by the AD patch driver and is not intended for manual maintenance.

Related Objects

The most significant related objects are:

• AD_APPLIED_PATCHES — The parent table. Join on AD_SEED_DATA_LOADED.APPLIED_PATCH_ID = AD_APPLIED_PATCHES.APPLIED_PATCH_ID. This is the only documented foreign key and the primary path for identifying which patch a load record belongs to.
• AD_PATCH_RUN_BUGS and AD_PATCH_RUNS — Sibling patch-tracking tables that record the broader execution context; used alongside this table when correlating seed loads with a specific patch run session.
• FND_LANGUAGES — The installed-language reference table, used to validate that every language requiring seed data actually appears in AD_SEED_DATA_LOADED for a given patch.
• AD_PATCH_DRIVERS and the AD patch worker logs — the operational sources that write these completion records during patch application.
• FND_SEED_DATA-related repository tables and views — the destination of the seed rows whose per-language load this table tracks.

Collectively, these objects place AD_SEED_DATA_LOADED at the intersection of patch application tracking and multilingual seed data provisioning, and its principal value is as an audit and troubleshooting checkpoint rather than a transactional or reporting subject area.