Search Results form_field_name

Overview

The view PJM_TASK_ATTRIBUTES is a Project Manufacturing (PJM) module object within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It serves as a translated, user-language-specific view of task attribute metadata. Its primary role is to provide a localized, readable layer over the underlying transactional data stored in the PJM_TASK_ATTRIBUTES_TL table. This view is essential for applications and reports that need to display attribute names and form field identifiers in the language of the current EBS user, as determined by the USERENV('LANG') function. It functions as a reference source for the configurable attributes associated with project tasks in a manufacturing context.

Key Information Stored

The view exposes a focused set of columns from the translation table. The key columns include ASSIGNMENT_TYPE and ATTRIBUTE_CODE, which together uniquely identify a specific task attribute. The ATTRIBUTE_NAME column stores the descriptive label for the attribute in the user's language. A critical column for integration and development is FORM_FIELD_NAME, which holds the identifier used for the attribute within Oracle Forms or other user interface components. The remaining columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are standard EBS audit columns tracking the record's lifecycle.

Common Use Cases and Queries

This view is predominantly queried for user interface configuration, data validation, and reporting. A common use case is retrieving the display label for a known attribute code to populate a report or a custom screen. For instance, a query to fetch all attribute metadata for a specific assignment type would be: SELECT attribute_code, attribute_name, form_field_name FROM apps.pjm_task_attributes WHERE assignment_type = 'TASK' ORDER BY attribute_code;. Developers interfacing with task data would use the FORM_FIELD_NAME to programmatically map UI fields to their corresponding database attributes. The view is also integral for generating dynamic lists of available task attributes for configuration screens within the PJM module.

Related Objects

The most direct related object is the table PJM_TASK_ATTRIBUTES_TL, which is the source of this view's data. The view applies a language filter to this table. The non-translated base table, likely named PJM_TASK_ATTRIBUTES_B, would store the core, language-independent definition of the attributes. This view is also closely related to the underlying transactional tables that store the actual attribute values for project tasks, which would reference the ATTRIBUTE_CODE. It may be referenced by PJM forms, reports, and APIs responsible for managing project task definitions and assignments.