Results for “edit_generated_amt_flag”

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

Overview

PA_FIN_PLAN_TYPES_B is the base (non-translated) definition table in the Oracle E-Business Suite Projects (PA) module that stores the various plan types used for financial plans. In Oracle EBS 12.1.1 and 12.2.2, financial plan types serve as the reusable templates that govern how project budgets, forecasts, cost plans, and revenue plans are created, versioned, approved, and reported. Each row defines a single financial plan type, along with its classification as a cost plan, revenue plan, or both, the currency conversion rate types applied to project and project functional currency conversions, approval behavior, workflow enablement, and interaction with billing, forecasting, and workplan features.

The table is owned by the PA schema and, per the ETRM 12.2.2 physical schema, contains 53 columns. Its primary key is PA_FIN_PLAN_TYPES_B_PK on FIN_PLAN_TYPE_ID. A second unique index, PA_FIN_PLAN_TYPES_B_U1 on (FIN_PLAN_TYPE_ID, ZD_EDITION_NAME), supports the editioning construct introduced in 12.2. Based on the relationship structure mined from its foreign keys—a small set of outbound references combined with a dense set of inbound references—the object is heuristic-classified as hub-leaning in Data Vault terms. In practice this suggests modeling PA_FIN_PLAN_TYPES_B as a hub, with descriptive attributes such as rate types, approval flags, and dates carried in an associated satellite.

Key Information Stored

The most significant columns of PA_FIN_PLAN_TYPES_B fall into identification, classification, conversion-rate, and control categories:

• FIN_PLAN_TYPE_ID — the surrogate primary key that uniquely identifies each financial plan type and is propagated into every dependent table.
• FIN_PLAN_TYPE_CODE — the user-visible, business-meaningful identifier for the plan type. Together with the edition column it forms the unique business key (PA_FIN_PLAN_TYPES_B_U1).
• PLAN_CLASS_CODE — distinguishes whether the plan type behaves as a cost plan, revenue plan, or similar classification.
• PRE_DEFINED_FLAG and GENERATED_FLAG — indicate whether the plan type is seeded by Oracle or created by generation logic.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the date range during which the plan type may be used.
• APPROVED_COST_PLAN_TYPE_FLAG and APPROVED_REV_PLAN_TYPE_FLAG — control whether cost and revenue plans of this type can be baselined or approved.
• PROJFUNC_COST_RATE_TYPE, PROJFUNC_REV_RATE_TYPE, PROJECT_COST_RATE_TYPE, and PROJECT_REV_RATE_TYPE — foreign keys to GL_DAILY_CONVERSION_TYPES, specifying the rate types used when converting cost and revenue amounts between project and functional currency and between transaction and project currency.
• MIGRATED_FRM_BDGT_TYP_CODE — a reference to PA_BUDGET_TYPES, linking migrated budget types to the financial plan type framework.
• ENABLE_WF_FLAG, ENABLE_PARTIAL_IMPL_FLAG, USE_FOR_WORKPLAN_FLAG, EDIT_AFTER_BASELINE_FLAG, and EDIT_GENERATED_AMT_FLAG — behavioral controls for workflow routing, partial implementation, workplan integration, and post-baseline editing.
• ZD_EDITION_NAME — the editioning column used in 12.2 online patching.
• Standard audit columns include RECORD_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, plus the fifteen ATTRIBUTE flex columns and ATTRIBUTE_CATEGORY.

Common Use Cases and Queries

Typical reporting and integration scenarios revolve around identifying which plan types are active, which support approval, and how they are consumed downstream. A common query retrieves all active cost plan types:

• Listing active plan types: SELECT fin_plan_type_id, fin_plan_type_code, plan_class_code FROM pa_fin_plan_types_b WHERE start_date_active <= SYSDATE AND NVL(end_date_active, SYSDATE+1) > SYSDATE;
• Joining to the translation table for language-specific names: SELECT b.fin_plan_type_code, t.name FROM pa_fin_plan_types_b b, pa_fin_plan_types_tl t WHERE b.fin_plan_type_id = t.fin_plan_type_id AND t.language = USERENV('LANG');
• Resolving conversion rate types for a plan type via GL_DAILY_CONVERSION_TYPES on the four rate-type columns.
• Auditing which project options generate plans from a source plan type by querying PA_PROJ_FP_OPTIONS.GEN_SRC_COST_PLAN_TYPE_ID and GEN_SRC_REV_PLAN_TYPE_ID.
• Reporting billing defaults through PA_BILLING_EXTENSIONS.DEFAULT_COST_PLAN_TYPE_ID and DEFAULT_REV_PLAN_TYPE_ID.

Because the table drives so many downstream features, it is frequently referenced when troubleshooting plan generation, allocation rule setup, and event auditing.

Related Objects

The following objects are among the most significant that reference or depend on PA_FIN_PLAN_TYPES_B:

• PA_FIN_PLAN_TYPES_TL — stores translated names and descriptions, joined on FIN_PLAN_TYPE_ID.
• PA_PROJ_FP_OPTIONS — project-level options referencing plan types via FIN_PLAN_TYPE_ID, GEN_SRC_COST_PLAN_TYPE_ID, GEN_SRC_REV_PLAN_TYPE_ID, and GEN_SRC_ALL_PLAN_TYPE_ID.
• PA_FP_ELEMENTS and PA_FP_EXCLUDED_ELEMENTS — define included and excluded elements per plan type via FIN_PLAN_TYPE_ID.
• PA_FP_TXN_CURRENCIES — currencies associated with each plan type.
• PA_BUDGET_VERSIONS and PA_PROJECT_ACCUM_BUDGETS — budget and accumulated budget records tied to FIN_PLAN_TYPE_ID.
• PA_ALLOC_RULES_ALL and PA_ALLOC_RUNS_ALL — allocation definitions and runs referencing BASIS_FIN_PLAN_TYPE_ID.
• PA_BILLING_EXTENSIONS — billing defaults referencing cost and revenue plan types.
• PA_EVENTS — audit records linking cost and revenue plan types via AUDIT_COST_PLAN_TYPE_ID and AUDIT_REV_PLAN_TYPE_ID.
• GL_DAILY_CONVERSION_TYPES and PA_BUDGET_TYPES — referenced outbound for rate types and migrated budget types.