Results for “hr_dtr_application_list_v”

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

Overview

HR_DTR_APPLICATION_LIST_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 reporting and integration view owned by the APPS schema and delivered under the PER (Human Resources) product family. Its documented purpose is to expose the "Downtime Reduction application list" — the set of registered Oracle applications that are subject to downtime reduction processing. The view synthesizes this list from the Payroll upgrade definitions repository and a supplementary seeded message row, projecting a uniform two-column result set containing an application display name and a corresponding short name or product code. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of its underlying definition and message tables at query time.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents four referenced base objects: FND_APPLICATION_VL (a view), FND_NEW_MESSAGES, PAY_UPGRADE_DEFINITIONS, and PAY_UPGRADE_DEFINITIONS_TL (all three presented to APPS as synonyms). The view text joins FND_APPLICATION_VL to PAY_UPGRADE_DEFINITIONS and PAY_UPGRADE_DEFINITIONS_TL. Specifically, FND_APPLICATION_VL.APPLICATION_ID is matched to PAY_UPGRADE_DEFINITIONS.OWNER_APPLICATION_ID, and PAY_UPGRADE_DEFINITIONS_TL.UPGRADE_DEFINITION_ID is matched to PAY_UPGRADE_DEFINITIONS.UPGRADE_DEFINITION_ID. This union of the applications registry with the Payroll upgrade definition metadata yields the primary result set. A filter excludes the application IDs 800, 801, 805, 8301, 8302, and 8403, removing internal or non-participating applications. A second UNION branch appends a single synthetic row built from FND_NEW_MESSAGES, where MESSAGE_NUMBER = 52382 supplies the display name and the literal 'HR_PF' supplies the short name.

Key Columns

The view exposes two documented columns. APPLICATION_NAME carries the human-readable application label, sourced either from FND.APPLICATION_NAME or, in the union branch, from the first 240 characters of MESSAGE_TEXT. PRODUCT_NAME carries the machine-oriented identifier, sourced from FND.APPLICATION_SHORT_NAME or the literal 'HR_PF'. In practice the two columns are positional aliases for name and short name, and consumers should treat PRODUCT_NAME as the stable join key rather than the descriptive APPLICATION_NAME. The view text references a column named PRODUCT_NAME in the metadata header; the projection order remains APPLICATION_NAME followed by the short name.

Common Use Cases and Queries

This view is typically used to drive runtime LOVs, concurrent program parameter lists, and validation logic that must restrict processing to applications participating in downtime reduction. A typical lookup reads both columns and orders by the display name:

• SELECT application_name, product_name FROM apps.hr_dtr_application_list_v ORDER BY 1;
• SELECT product_name FROM apps.hr_dtr_application_list_v WHERE UPPER(application_name) LIKE UPPER(:search) || '%';
• Joining to FND_APPLICATION_VL to obtain additional attributes for each returned short name.

Because the view includes TRANSLATABLE columns via PAY_UPGRADE_DEFINITIONS_TL, results can vary with session language, which is relevant when localizing LOV entries. Administrators should be aware that the unioned 'HR_PF' row is seeded from the message table and will not correspond to a standard FND_APPLICATION row. The referenced table PAY_UPGRADE_DEFINITIONS_TL is itself a translated table and shares the _TL naming convention with objects such as those returned by searches for pay_upgrade_definitions_tl, reinforcing that the view is tightly coupled to the Payroll upgrade definition model rather than to a generic HR lookup.