Results for “hr_pf”

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

Overview

APPS.HR_DTR_APPLICATION_LIST_V is a documented Oracle E-Business Suite view owned by the APPS schema. Its purpose is to expose a curated list of Oracle EBS application names and short names that participate in the HR and Payroll data transformation and upgrade definition framework. The view is defined as a UNION of two distinct data sets. The first set derives from the intersection of FND_APPLICATION_VL with the Payroll upgrade definition tables, filtering out a fixed list of system application identifiers. The second set contributes a single synthesized row drawn from FND_NEW_MESSAGES, where the message text associated with message number 52382 is truncated to 240 characters and hard-coded with the short name 'HR_PF'. In the context of the user's search for "hr_pf", the literal identifier 'HR_PF' appears directly in the view definition as the second column value of the UNION branch, making this view the likely resolution of that search term. The view serves reporting and integration purposes by presenting a consolidated, ready-to-query list of applications relevant to HR data transformation and upgrade processing, without requiring consumers to join the underlying definition and translation tables themselves.

Underlying Base Objects

The ETRM metadata documents four referenced base objects. FND_APPLICATION_VL is itself a view over the application registry, supplying the application identifier, translatable application name, and application short name. PAY_UPGRADE_DEFINITIONS is the core definition table that links an upgrade definition to its owning application through OWNER_APPLICATION_ID. PAY_UPGRADE_DEFINITIONS_TL is the translation table for upgrade definitions, joined on UPGRADE_DEFINITION_ID. FND_NEW_MESSAGES is a synonym to the messages table, queried for the row matching MESSAGE_NUMBER = 52382. The view joins applications to upgrade definitions and their translations, excluding application identifiers 800, 801, 805, 8301, 8302, and 8403, which correspond to system or seeded applications that should not appear in the list. The union operation appends the synthesized 'HR_PF' row, ensuring this special entry is included regardless of whether it is present in the upgrade definition tables.

Key Columns

The view projects exactly two columns. The first column carries the application name. For rows from the first UNION branch, this is FND.APPLICATION_NAME from FND_APPLICATION_VL; for the second branch, it is the first 240 characters of MESSAGE_TEXT from FND_NEW_MESSAGES. The second column carries the application short name. For the first branch it is FND.APPLICATION_SHORT_NAME; for the second branch it is the literal value 'HR_PF'. Although the view text does not explicitly alias these columns, consumers should treat the first as the display name and the second as the short name used in lookup and filtering logic. Because the union combines a translatable name column with a substring of a message, the character semantics follow the NLS and length conventions of the underlying columns, with the 240-character cap protecting against oversized message text.

Common Use Cases and Queries

This view is typically used to populate list-of-values and selection screens that require the set of applications involved in HR and Payroll data transformation, and to resolve the special 'HR_PF' entry referenced in messages. A basic query returns the full list:

• SELECT application_name, application_short_name FROM apps.hr_dtr_application_list_v ORDER BY 2;
• SELECT application_name FROM apps.hr_dtr_application_list_v WHERE application_short_name = 'HR_PF'; — isolates the synthesized HR_PF row contributed by the FND_NEW_MESSAGES branch.
• SELECT COUNT(*) FROM apps.hr_dtr_application_list_v; — returns the number of qualifying applications plus one for the HR_PF entry.

Because the view performs the exclusions and the union internally, callers avoid re-implementing the filtered application logic and the hard-coded HR_PF inclusion. The documented metadata confirms the structure and referenced objects; join semantics to downstream tables should be validated against the specific upgrade definition columns (UPGRADE_DEFINITION_ID, OWNER_APPLICATION_ID) when finer-grained analysis is required.