Search Results display_column

Overview

The PA_ONLINE_EXPENDITURE_TYPES_V view is a customizable presentation-layer object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides within the Projects (PA) product family and is delivered to support the Self Service Time application, where end users must select an expenditure type when entering or reporting time. The view surfaces expenditure type records in a display-ready format, most notably by concatenating the expenditure type name with its associated system linkage value to produce a human-readable label suitable for a list of values (LOV) or dropdown in a self-service form.

Because the view is documented as "customizable," Oracle permits implementers to modify or extend it to meet site-specific requirements—for example, adding filtering logic, exposing adjacent descriptive columns, or refining the display string presented to end users. It functions as a reporting and integration surface rather than a transactional entity; consumption occurs through reporting tools such as Oracle Reports, BI Publisher, and ad-hoc SQL, or through form LOV definitions. Notably, the user search term system_linkage_m corresponds directly to a column exposed by this view, which is the dependency that drives its inclusion of the concatenated display column.

Underlying Base Objects

Per the documented ETRM metadata, PA_ONLINE_EXPENDITURE_TYPES_V is defined over a single referenced object: the view PA_EXPENDITURE_TYPES_EXPEND_V, aliased as ET in the view text. It is layered one level above the expenditure type base data rather than querying the base tables directly. The underlying PA_EXPENDITURE_TYPES_EXPEND_V view ultimately resolves to the PA_EXPENDITURE_TYPES (and related lookup) structures that hold expenditure type definitions, unit of measure attributes, cost rate flags, and system linkage configuration.

The design intent of this layering is to isolate the self-service consumption pattern—particularly the concatenated display string—from the general-purpose expenditure type view, allowing the display format to be customized without disturbing downstream logic. The dependency on SYSTEM_LINKAGE_M at the base view confirms that linkage information is already resolved before the online display view is built.

Key Columns

• DISPLAY_COLUMN — The concatenation EXPENDITURE_TYPE || ' - (' || SYSTEM_LINKAGE_M || ')', the primary column intended for LOV presentation.
• EXPENDITURE_TYPE — The name of the expenditure type.
• DESCRIPTION — Descriptive text for the expenditure type.
• UOM_CODE / UNIT_OF_MEASURE — The unit of measure code and its display equivalent.
• COST_RATE_FLAG — Indicates whether the expenditure type carries cost rate implications.
• SYSTEM_LINKAGE_M — The system linkage value used in the display string; this is the column matching the user search term.
• SYSTEM_LINKAGE_FUNCTION — The linkage function associated with the expenditure type.
• SYS_LINK_START_DATE_ACTIVE / SYS_LINK_END_DATE_ACTIVE — Effective date bounds for the system linkage.
• EXPND_TYP_START_DATE_ACTIVE / EXPND_TYP_END_DATE_ACTIVE — Effective date bounds for the expenditure type itself.
• PROJECT_ID — Project context associated with the record.

Common Use Cases and Queries

The most frequent scenario is populating an expenditure type LOV in Self Service Time, where the concatenated DISPLAY_COLUMN provides clarity by pairing the expenditure type name with its system linkage. Reporting and validation queries, including those filtered by the SYSTEM_LINKAGE_M search term, are equally common.

Listing active expenditure types with their display label:

• SELECT display_column, expenditure_type, system_linkage_m, cost_rate_flag
• FROM apps.pa_online_expenditure_types_v
• WHERE TRUNC(SYSDATE) BETWEEN expnd_typ_start_date_active AND NVL(expnd_typ_end_date_active, SYSDATE);

Retrieving records tied to a specific system linkage:

• SELECT expenditure_type, description, uom_code, project_id
• FROM apps.pa_online_expenditure_types_v
• WHERE system_linkage_m = :linkage;