Results for “patch_driver_id”

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

Overview

AD_PATCH_DRIVER_LANGS is an Applications DBA (AD) intersection table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the languages to which a given patch driver pertains, effectively resolving the many-to-many relationship between patch drivers and the language definitions registered in the EBS instance. The table is a control-plane object: it does not carry transactional or application data, but governs which language-specific artifacts a driver processes during patch application, notably through AD utilities such as adpatch and the AutoPatch driver analysis routines.

Under the heuristic Data Vault classification provided in the ETRM metadata, this object is described as satellite-leaning. Modeling practitioners may therefore treat AD_PATCH_DRIVER_LANGS as a satellite hanging off the AD_PATCH_DRIVERS hub, rather than as an independent hub or a pure link, since it carries descriptive attributes (LANGUAGE) and audit columns rather than only key relationships. This classification is a suggestion derived from FK structure, not a native Oracle construct.

Key Information Stored

The documented physical schema for 12.2.2 defines seven columns. The most operationally significant are:

• LANG_ID — the language identifier. This column participates in the surrogate primary key AD_PATCH_DRIVER_LANGS_PK and in the unique index AD_PATCH_DRIVER_LANGS_U1.
• PATCH_DRIVER_ID — foreign key to AD_PATCH_DRIVERS, identifying the parent driver record. It forms part of the composite unique index AD_PATCH_DRIVER_LANGS_U2.
• LANGUAGE — the language code associated with the driver, combined with PATCH_DRIVER_ID in AD_PATCH_DRIVER_LANGS_U2 as a documented business-key candidate.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard EBS audit and who-columns introduced by the Applications DBA concurrency and auditing conventions.

The distinction between the surrogate key family (AD_PATCH_DRIVER_LANGS_PK on LANG_ID) and the business-key candidates (AD_PATCH_DRIVER_LANGS_U1 on LANG_ID and AD_PATCH_DRIVER_LANGS_U2 on PATCH_DRIVER_ID, LANGUAGE) is central to correct querying, as it permits joins either by surrogate identifier or by the natural driver-plus-language pairing.

Common Use Cases and Queries

Typical scenarios include determining which languages a patch driver targets prior to applying a patch, verifying whether a driver was generated for a specific NLS language, and supporting translation and NLS reporting. A representative query joins the table to its parent driver:

• SELECT l.PATCH_DRIVER_ID, l.LANG_ID, l.LANGUAGE FROM APPLSYS.AD_PATCH_DRIVER_LANGS l WHERE l.PATCH_DRIVER_ID = :p_driver_id;
• SELECT l.LANGUAGE, COUNT(*) FROM APPLSYS.AD_PATCH_DRIVER_LANGS l GROUP BY l.LANGUAGE ORDER BY 2 DESC; to profile language coverage across drivers.
• SELECT d.PATCH_DRIVER_ID, l.LANGUAGE FROM APPLSYS.AD_PATCH_DRIVERS d, APPLSYS.AD_PATCH_DRIVER_LANGS l WHERE d.PATCH_DRIVER_ID = l.PATCH_DRIVER_ID;

Reporting use cases include auditing NLS patch coverage and validating that all required languages are present before a multilingual patch run.

Related Objects

The most significant related objects are follows:

• AD_PATCH_DRIVERS — parent table referenced by AD_PATCH_DRIVER_LANGS.PATCH_DRIVER_ID.
• MTH_TRANSLATED_MESSAGE — references this table via MTH_TRANSLATED_MESSAGE.LANG_ID.
• The unique indexes AD_PATCH_DRIVER_LANGS_PK, AD_PATCH_DRIVER_LANGS_U1, and AD_PATCH_DRIVER_LANGS_U2, which enforce the documented key constraints.
• The AD product’s AutoPatch utilities and language installation routines, which consume this data during patch application.