Results for “functional_currency_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_CE_EXP_REPORTS_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. It is a reporting-oriented construct designed to expose expenditure item data tied to cost distribution activity for use in external reporting, integration extraction, and downstream analysis. The view is catalogued as VALID in the ETRM metadata for release 12.2.2, and the same object is documented in the 12.1.1 code line for Projects.

The view's central purpose is to identify expenditure items that have associated cost distribution lines which are in a pending or rejected transfer state. It joins expenditure items to their cost distribution lines and task records, restricting output to items where the parent cost distribution line carries a TRANSFER_STATUS_CODE of 'P' (pending) or 'R' (rejected), while excluding items whose expenditure system linkage function is not 'ER' and whose transaction source is 'AP EXPENSE'. This makes the view particularly relevant when troubleshooting held or unprocessed cost transfers.

Underlying Base Objects

The view is defined over three documented base objects, each referenced through APPS synonyms:

• PA_EXPENDITURE_ITEMS_ALL (aliased PEI) — the primary fact source, supplying expenditure item identifiers, amounts, dates, org, and status flags.
• PA_COST_DISTRIBUTION_LINES_ALL (aliased PCDL) — joined on EXPENDITURE_ITEM_ID to filter items whose cost distribution lines are pending or rejected.
• PA_TASKS (aliased PT) — joined on TASK_ID to return the owning project identifier.

The join predicates enforce the pending/rejected transfer filter and the exclusion of AP EXPENSE transactions, using an NVL guard on TRANSACTION_SOURCE to handle nulls safely.

Key Columns

• PROJECT_ID — derived from PA_TASKS; identifies the project associated with the task owning the expenditure item.
• BILL_HOLD_FLAG — the flag indicating whether the expenditure item is held from billing, a frequent subject of the user's search.
• EXPENDITURE_ITEM_ID — unique identifier of the expenditure item, the principal join key.
• ORG_ID — operating unit identifier, essential for multi-org security.
• AMOUNT / BASE_AMOUNT — expenditure amounts in transaction and functional currency, mapped from PEI.ACCT_RAW_COST and PEI.DENOM_RAW_COST respectively.
• CURRENCY_CODE / FUNCTIONAL_CURRENCY_CODE — the denominated and accounting currencies.
• TRX_DATE — the expenditure item date.
• TRANSACTION_SOURCE — origin of the transaction, used to exclude AP EXPENSE.

Common Use Cases and Queries

Typical uses include identifying expenditure items blocked from cost transfer, reconciling transferred versus unprocessed costs, and extracting pending or rejected distributions for a given project or operating unit. Because the view exposes BILL_HOLD_FLAG, it is also used to isolate held items that will not flow to billing.

The following query returns held items with pending or rejected cost distribution lines for a given operating unit:

• SELECT project_id, expenditure_item_id, bill_hold_flag, transaction_source, amount, currency_code FROM pa_ce_exp_reports_v WHERE org_id = :org_id AND bill_hold_flag = 'Y';

A second common pattern aggregates amounts by project to review transfer exposure:

• SELECT project_id, SUM(amount) total_amount FROM pa_ce_exp_reports_v WHERE org_id = :org_id GROUP BY project_id ORDER BY total_amount DESC;

Because the view pre-applies the 'P'/'R' transfer filter and the AP EXPENSE exclusion, join logic should be kept simple, and org_id should always be supplied to satisfy multi-org access requirements.