Results for “project_cost_exchange_rate”

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

Overview

PA_FP_TXN_CURRENCIES is a transactional configuration table in the Oracle Projects (PA) module that stores the plannable transaction currencies defined for a project. Within Oracle EBS 12.1.1 and 12.2.2, it defines which currencies can be used when entering financial plan amounts, budgets, and forecasts for a given project and financial plan type. Each row associates a project, a financial plan type, and a specific financial plan version with a transaction currency, and records the defaulting behavior and exchange rate values applied to cost and revenue planning.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is best modeled as a link entity. It resolves the many-to-many relationships between projects, financial plan options, plan types, budget versions, and currencies, carrying descriptive attributes that qualify those relationships. This classification is a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• FP_TXN_CURRENCY_ID — The surrogate primary key (PA_FP_TXN_CURRENCIES_PK) that uniquely identifies each currency row.
• PROJ_FP_OPTIONS_ID — References the financial plan options record that governs the project's planning setup.
• PROJECT_ID — Identifies the owning project; joins to PA_PROJECTS_ALL.
• FIN_PLAN_TYPE_ID — References PA_FIN_PLAN_TYPES_B, indicating which plan type (for example, budget or forecast) the currency applies to.
• FIN_PLAN_VERSION_ID — References PA_BUDGET_VERSIONS, tying the currency to a specific plan version.
• TXN_CURRENCY_CODE — The transaction currency, validated against FND_CURRENCIES.
• DEFAULT_REV_CURR_FLAG, DEFAULT_COST_CURR_FLAG, DEFAULT_ALL_CURR_FLAG — Flags indicating whether the currency is the default for revenue, cost, or all planning entries.
• PROJECT_CURRENCY_FLAG, PROJFUNC_CURRENCY_FLAG — Flags indicating whether the currency corresponds to the project currency or the project functional currency.
• PROJECT_COST_EXCHANGE_RATE, PROJECT_REV_EXCHANGE_RATE, PROJFUNC_COST_EXCHANGE_RATE, PROJFUNC_REV_EXCHANGE_RATE — Stored exchange rates used to convert cost and revenue amounts between the transaction currency and the project and project functional currencies.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns.

Two unique indexes are documented: PA_FP_TXN_CURRENCIES_U1 on FP_TXN_CURRENCY_ID (the primary key) and PA_FP_TXN_CURRENCIES_U2 on the composite (PROJ_FP_OPTIONS_ID, TXN_CURRENCY_CODE), which is the business-key candidate that prevents duplicate currencies for the same planning option set.

Common Use Cases and Queries

Typical reporting and validation scenarios involve determining which currencies are plannable for a project, verifying default currency behavior, and auditing exchange rates stored for planning conversions. A representative query joins the table to projects and currencies:

• SELECT t.project_id, p.segment1 project_number, t.txn_currency_code, t.default_all_curr_flag FROM pa_fp_txn_currencies t, pa_projects_all p WHERE t.project_id = p.project_id AND t.default_all_curr_flag = 'Y';
• List all plannable currencies by plan type: SELECT t.project_id, t.fin_plan_type_id, t.txn_currency_code FROM pa_fp_txn_currencies t WHERE t.fin_plan_type_id = :plan_type_id;
• Audit stored conversion rates: SELECT t.project_id, t.txn_currency_code, t.project_cost_exchange_rate, t.project_rev_exchange_rate FROM pa_fp_txn_currencies t;

These queries support financial planning validation, currency setup reviews, and reconciliation of planned versus converted amounts.

Related Objects

The table participates in the following documented relationships:

• PA_PROJECTS_ALL — joined via PROJECT_ID; the master project definition.
• PA_PROJ_FP_OPTIONS — joined via PROJ_FP_OPTIONS_ID; project financial plan configuration.
• PA_FIN_PLAN_TYPES_B — joined via FIN_PLAN_TYPE_ID; defines plan types.
• PA_BUDGET_VERSIONS — joined via FIN_PLAN_VERSION_ID; identifies plan versions.
• FND_CURRENCIES — joined via TXN_CURRENCY_CODE; validates the currency.

Collectively these references establish the project planning currency framework used throughout Oracle Projects financial plan processing.