Search Results system_linkage_m




Overview
Explore in AI Chat

Overview

APPS.PA_ONLINE_EXPENDITURE_TYPES_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that exposes expenditure types together with their system linkage attributes. Its defining purpose is to present a human-readable, concatenated display value that pairs the expenditure type name with its associated system linkage, making it convenient for Oracle Forms LOVs, online validation, and ad-hoc reporting. The view originates from the pre-12.2 ETRM repository and remains valid in both Oracle EBS 12.1.1 and 12.2.2, where it is owned by the APPS schema.

The user who searched for "system_linkage_m" will find that this column is central to the view. SYSTEM_LINKAGE_M identifies the system linkage mapped to an expenditure type—that is, the interface point between Oracle Projects and a source or target application such as Payables, Purchasing, Inventory, or Time and Labor. The view surfaces this linkage value both as a standalone column and as part of the first, derived display column, which is constructed as EXPENDITURE_TYPE || ' - (' || SYSTEM_LINKAGE_M || ')'.

Underlying Base Objects

According to the documented view text, PA_ONLINE_EXPENDITURE_TYPES_V is defined solely over a single referenced object: PA_EXPENDITURE_TYPES_EXPEND_V, which is itself a view, not a base table. The ETRM metadata lists this as the only referenced base object and explicitly identifies it as a VIEW.

Because the definition is a thin projection over PA_EXPENDITURE_TYPES_EXPEND_V, the parent view inherits its join logic, filters, and attribute derivations. PA_EXPENDITURE_TYPES_EXPEND_V in turn resolves expenditure type definitions and their effective dating from the underlying PA_EXPENDITURE_TYPES and related Projects configuration tables. This layered design means any change to filtering or row visibility in the parent view propagates directly to PA_ONLINE_EXPENDITURE_TYPES_V without additional logic in this view itself.

Key Columns

  • Derived display column — the unnamed first expression, EXPENDITURE_TYPE || ' - (' || SYSTEM_LINKAGE_M || ')', used as the friendly label in online lists of values.
  • EXPENDITURE_TYPE — the expenditure type name, the primary business key for classification of project costs.
  • DESCRIPTION — the descriptive text associated with the expenditure type.
  • UOM_CODE / UNIT_OF_MEASURE — the unit of measure code and its corresponding descriptive name.
  • COST_RATE_FLAG — indicates whether the expenditure type is subject to cost rate determination.
  • SYSTEM_LINKAGE_M — the system linkage mapping that governs the interface between the expenditure type and the external or internal source system.
  • SYSTEM_LINKAGE_FUNCTION — the specific function performed by the system linkage for this expenditure type.
  • SYS_LINK_START_DATE_ACTIVE / SYS_LINK_END_DATE_ACTIVE — the effective start and end dates of the system linkage.
  • EXPND_TYP_START_DATE_ACTIVE / EXPND_TYP_END_DATE_ACTIVE — the effective start and end dates of the expenditure type itself.
  • PROJECT_ID — the project identifier context carried through from the parent view.

Common Use Cases and Queries

The view is typically queried to populate online selection lists and to report on which system linkage is attached to each expenditure type. A representative query follows:

  • SELECT EXPENDITURE_TYPE, SYSTEM_LINKAGE_M, SYSTEM_LINKAGE_FUNCTION FROM APPS.PA_ONLINE_EXPENDITURE_TYPES_V; — lists expenditure types with their linkage mapping.
  • SELECT * FROM APPS.PA_ONLINE_EXPENDITURE_TYPES_V WHERE SYSTEM_LINKAGE_M = :linkage; — filters all columns for a specific linkage, useful when troubleshooting interface configuration.
  • SELECT EXPENDITURE_TYPE, SYSTEM_LINKAGE_M FROM APPS.PA_ONLINE_EXPENDITURE_TYPES_V WHERE SYSDATE BETWEEN SYS_LINK_START_DATE_ACTIVE AND NVL(SYS_LINK_END_DATE_ACTIVE, SYSDATE); — returns only currently active linkage mappings.

Because the underlying metadata is limited, consumers should treat the documented column list as authoritative and validate effective-dating behavior against current configuration before relying on historical date ranges.