Search Results award_name_num_concat

Overview

APPS.PA_XLA_COST_V is a denormalized reporting view in the Oracle E-Business Suite Projects (PA) application, owned by the APPS schema and registered under FND Design Data as PA.PA_XLA_COST_V. The object is a VIEW of type Internal with status VALID in both EBS 12.1.1 and 12.2.2. Its purpose is to expose project expenditure cost lines in a flattened, human-readable form suitable for Subledger Accounting (XLA) extraction, cost distribution reporting, and downstream warehouse loads. The view consolidates identifying and descriptive attributes for each expenditure item, including concatenated project, task, and award identifiers together with expenditure classification and incurring organization.

The view is flagged by Oracle as Internal Use Only; Oracle Corporation does not support customer access to the underlying applications data through this object except from standard Oracle Applications programs. The view is not referenced by any other database object, so it functions as a terminal reporting surface rather than a dependency of further application logic.

Underlying Base Objects

The view is defined over the following documented base objects, all resolved as APPS synonyms in 12.2.2:

• PA_EXPENDITURE_ITEMS_ALL — the primary transaction table supplying expenditure item rows.
• PA_EXPENDITURES_ALL — the parent expenditure header providing expenditure type and category context.
• PA_EXPENDITURE_TYPES — supplies the expenditure type name and expenditure type class.
• PA_PROJECTS_ALL — provides the project name and number used in the project concatenation.
• PA_TASKS — provides task name and number for the task concatenation.
• PA_SYSTEM_LINKAGES — links project transactions to their originating subledger context.
• HR_ALL_ORGANIZATION_UNITS — resolves the incurring (expenditure) organization name.
• GMS_AWARDS_ALL and GMS_AWARD_DISTRIBUTIONS — grant award header and distribution details used to build the award concatenation.

The join of expenditure items to expenditure types, projects, tasks, and organization units produces one row per expenditure item with descriptive context attached.

Key Columns

• EXPENDITURE_ITEM_ID (NUMBER, 15) — the unique expenditure item identifier; the primary grain of the view.
• PROJECT_NAME_NUM_CONCAT (VARCHAR2, 58) — concatenated project name and number.
• TASK_NAME_NUM_CONCAT (VARCHAR2, 48) — concatenated task name and number.
• AWARD_NAME_NUM_CONCAT (VARCHAR2, 48) — concatenated grant award name and number.
• EXPENDITURE_TYPE (VARCHAR2, 30) — the expenditure type assigned to the item.
• EXPENDITURE_TYPE_CLASS (VARCHAR2, 80) — the class of the expenditure type, used for accounting derivation.
• EXPENDITURE_CATEGORY (VARCHAR2, 30) — cost or revenue category classification.
• EXPENDITURE_ITEM_DATE (DATE) — the transaction date of the expenditure item.
• EXP_ORGANIZATION_NAME (VARCHAR2, 240) — the incurring organization name, resolved from HR_ALL_ORGANIZATION_UNITS; this is the column most frequently targeted by searches such as "exp_organization_name".
• NON_LABOR_RESOURCE (VARCHAR2, 20) — the non-labor resource identifier for the item.

Common Use Cases and Queries

Typical uses include cost-line extracts for XLA reconciliation, organization-level expenditure analysis, and grant award cost reporting. The recorded query text is:

SELECT EXPENDITURE_ITEM_ID
     , PROJECT_NAME_NUM_CONCAT
     , TASK_NAME_NUM_CONCAT
     , AWARD_NAME_NUM_CONCAT
     , EXPENDITURE_TYPE
     , EXPENDITURE_TYPE_CLASS
     , EXPENDITURE_CATEGORY
     , EXPENDITURE_ITEM_DATE
     , EXP_ORGANIZATION_NAME
     , NON_LABOR_RESOURCE
  FROM APPS.PA_XLA_COST_V;

A filtered variant matching the user's search term retrieves items incurred by a specific organization:

SELECT EXPENDITURE_ITEM_ID
     , PROJECT_NAME_NUM_CONCAT
     , EXPENDITURE_TYPE
     , EXPENDITURE_ITEM_DATE
     , EXP_ORGANIZATION_NAME
  FROM APPS.PA_XLA_COST_V
 WHERE EXP_ORGANIZATION_NAME = :p_org_name
   AND EXPENDITURE_ITEM_DATE BETWEEN :p_start AND :p_end;

Because the view is unsupported for direct customer access, production use should be restricted to read-only reporting, and organizations should consider building supported extracts or custom views over the base PA tables where long-term stability is required.