Search Results sys_link_end_date_active

Overview

The view PA_EXPENDITURE_TYPES_EXPEND_V is an Oracle EBS Projects (PA) reporting object owned by the APPS schema. It is documented in ETRM with the notation "10SC Only," indicating that the object is intended for use within specific 10SC (Oracle Projects) contexts rather than as a general-purpose public interface. The view joins expenditure type definitions to their associated system linkage configurations, presenting a consolidated picture of which expenditure types are active, what unit of measure they carry, and how they map to system linkage functions such as cost distribution and interface processing.

Because it is a view rather than a base table, it carries no independent storage and is always populated in real time from its underlying sources. It is used primarily for inquiry, reporting, and integration validation where the relationship between an expenditure type and its system linkage function must be inspected. The view exposes both definitional attributes (description, unit of measure) and lifecycle attributes (start and end dates at both the expenditure type and system linkage level), making it useful for auditing current versus historical configurations.

Underlying Base Objects

The view is defined over four documented base objects:

• PA_EXPENDITURE_TYPES (SYNONYM) — the primary source of expenditure type definitions, supplying the expenditure type name, description, unit of measure, and cost rate flag.
• PA_EXPEND_TYP_SYS_LINKS (SYNONYM) — the association between expenditure types and system linkage functions, supplying the linkage function code and its active date range.
• PA_LOOKUPS (VIEW) — a lookup view used to translate the unit of measure code into its descriptive meaning via the 'UNIT' lookup type.
• PA_SYSTEM_LINKAGES (SYNONYM) — the source of the descriptive meaning for the system linkage function.

The driving join is between PA_EXPENDITURE_TYPES and PA_EXPEND_TYP_SYS_LINKS on EXPENDITURE_TYPE. Scalar subqueries against PA_LOOKUPS and PA_SYSTEM_LINKAGES enrich the result with meaningful descriptions.

Key Columns

• EXPENDITURE_TYPE — the expenditure type identifier common to both base tables.
• DESCRIPTION — the descriptive name of the expenditure type.
• UNIT_OF_MEASURE / UOM_CODE — the unit of measure code; the view also resolves this to a MEANING via PA_LOOKUPS.
• COST_RATE_FLAG — indicates whether a cost rate applies to the expenditure type.
• SYSTEM_LINKAGE_FUNCTION — the linkage function code used to route the expenditure type.
• MEANING1 — the descriptive meaning of the system linkage function from PA_SYSTEM_LINKAGES.
• START_DATE_ACTIVE / END_DATE_ACTIVE — active date ranges at the expenditure type level.
• SYS_LINK_START_DATE_ACTIVE / SYS_LINK_END_DATE_ACTIVE — active date ranges at the system linkage level.
• PROJECT_ID — a residual or placeholder column produced by the projection expression in the view definition.

Common Use Cases and Queries

Typical usages include validating that every expenditure type is linked to an appropriate system linkage function, reporting active expenditure types with their units of measure, and feeding downstream integrations that depend on linkage configuration.

A representative query returns active expenditure types and their linkage functions:

• SELECT expenditure_type, description, unit_of_measure, meaning1, system_linkage_function
• FROM apps.pa_expenditure_types_expend_v
• WHERE sys_link_start_date_active <= SYSDATE
• AND (sys_link_end_date_active IS NULL OR sys_link_end_date_active >= SYSDATE);

Because the column set reflects the documented projection, queries should reference the actual view columns rather than assumed attribute names. Care should also be taken with duplicate rows that may arise when multiple system linkage records exist per expenditure type.