Results for “acct_tp_rate_date”

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

Overview

PA_CC_BL_CUR_SEL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) module. It is a denormalized selection view whose purpose is to expose cross-charge expenditure item detail together with the derived currency, organization, task, and expenditure-type context required for billing and cross-charge processing. The view resolves surrogate keys into descriptive attributes and performs inline business-rule calculations that would otherwise require procedural code, allowing concurrent programs, billing generators, and custom reports to consume a single flat result set.

The view's internal name — "CC_BL_CUR_SEL" — reflects its role: cross-charge (CC) and billing (BL) currency (CUR) selection logic. It is particularly associated with the currency determination and provider/receiver transfer-price processing required when expenditures are shared across organizations, projects, or tasks via cross-charge arrangements.

Underlying Base Objects

PA_CC_BL_CUR_SEL_V is defined over the principal Projects transaction tables and a small number of lookup, HR, and utility objects. The documented referenced base objects are:

• PA_EXPENDITURE_ITEMS_ALL — the parent transaction table; supplies expenditure item identifiers, dates, quantities, billable flags, transfer prices, cross-charge codes, and currency columns.
• PA_EXPENDITURES_ALL — supplies the expenditure group, expenditure ending date, and incurred-by organization.
• PA_EXPENDITURE_TYPES — supplies expenditure category and revenue category code.
• PA_PROJECTS_ALL, PA_TASKS — supply project, task, task number, and carrying-out organization context.
• PA_SYSTEM_LINKAGES, PA_FUNCTION_TRANSACTIONS — supply system linkage function attributes used in cross-charge derivation.
• PA_EMPLOYEES, HR_ALL_ORGANIZATION_UNITS_TL — resolve resource and organization names.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, PA_UTILS — packages invoked for date conversion (PA_UTILS.GET_PA_DATE) and HR name/security resolution.
• FND_LANGUAGES — joins the organization translation table for language-specific names.

The view therefore sits directly on top of the core expenditure item and expenditure stacks, adding decode logic rather than storing any data itself.

Key Columns

• EXP_ITEM_ROWID — ROWID of the expenditure item row, exposed via ROWIDTOCHAR for updatable cursors or row-level navigation.
• EXPENDITURE_ITEM_ID, PROJECT_ID, TASK_ID — primary keys linking back to the transaction tables.
• CALC_TP_FLAG — derived flag; equals 'Y' when the item is a billable-type cross-charge (CC_CROSS_CHARGE_CODE = 'B') with no adjusted expenditure item, driving whether a transfer price must be calculated.
• ADJUSTED_EXP_ITEM_ID, NET_ZERO_FLAG — identify adjustment and net-zero expenditure items.
• CROSS_CHARGE_CODE, SYSTEM_LINKAGE_FUNCTION — classify the cross-charge mechanism applied to the item.
• Currency columns — DENOM_TP_CURRENCY_CODE, DENOM_CURRENCY_CODE, DENOM_TRANSFER_PRICE, ACCT_CURRENCY_CODE, ACCT_TP_RATE_TYPE, ACCT_TP_RATE_DATE, ACCT_TP_EXCHANGE_RATE, ACCT_TRANSFER_PRICE, PROJ_CURRENCY_CODE, providing the denominated and accounted transfer-price amounts and exchange rates.
• BILLABLE_FLAG, REVENUE_DISTRIBUTED_FLAG — billing status indicators.
• Organization columns — PRVDR_ORGANIZATION_ID, RECVR_ORGANIZATION_ID, NL_RESOURCE_ORGANIZATION_ID, EXPENDITURE_ORGANIZATION_ID (derived from override or incurred-by), TASK_ORGANIZATION_ID, PROJ_ORGANIZATION_ID, with corresponding name columns from HR_ALL_ORGANIZATION_UNITS_TL.
• PA_DATE — formatted expenditure item date produced by PA_UTILS.GET_PA_DATE.

Common Use Cases and Queries

Typical consumers include cross-charge transfer-price generation, burdening and billing concurrent programs, and custom reconciliation reports validating transfer prices against exchange rates.

Sample query listing billable cross-charge items requiring transfer-price calculation:

SELECT expenditure_item_id, project_id, task_id,
       cross_charge_code, denom_currency_code,
       denom_transfer_price, acct_transfer_price, pa_date
FROM   apps.pa_cc_bl_cur_sel_v
WHERE  calc_tp_flag = 'Y'
AND    billable_flag = 'Y';

Sample query summarizing provider/receiver transfer prices by organization:

SELECT prvdr_organization_id, recvr_organization_id,
       proj_currency_code, SUM(acct_transfer_price)
FROM   apps.pa_cc_bl_cur_sel_v
WHERE  expenditure_ending_date BETWEEN :start_date AND :end_date
GROUP  BY prvdr_organization_id, recvr_organization_id, proj_currency_code;

Because the view exposes ROWID-derived identifiers and full currency context, it is equally suited to drill-down reports linking back to PA_EXPENDITURE_ITEMS_ALL as to standalone aggregation in cross-charge audit processes.