Search Results pa_fin_plan_types_tl

Overview

The PA_FIN_PLAN_TYPES_TL table is a core translation table within the Oracle E-Business Suite Projects (PA) module. Its primary function is to store the user-facing names for financial plan types in multiple languages, enabling the application's multilingual support. It operates in conjunction with its base table, PA_FIN_PLAN_TYPES_B, which holds the seed data and non-translatable attributes. This separation of translatable and non-translatable data is a standard Oracle Applications architecture pattern. The table is essential for ensuring that plan type descriptions, such as "Cost Budget," "Revenue Forecast," or "Funding Budget," are displayed correctly in the language selected by the end-user within the Projects module's financial planning and control functionalities.

Key Information Stored

The table's structure is typical of an Oracle Applications translation table. While the full column list is not detailed in the provided metadata, based on the standard pattern, its critical columns include:

• FIN_PLAN_TYPE_ID: The primary key column that uniquely identifies a financial plan type. This column is also a foreign key referencing the PA_FIN_PLAN_TYPES_B base table, linking the translated name to its corresponding definition.
• NAME: The column storing the actual translated name of the financial plan type (e.g., "Budget des coûts" in French).
• LANGUAGE: The column indicating the language of the translation (e.g., 'US', 'FR', 'DE').
• SOURCE_LANG: A column that typically identifies the language of the source record from which the translation was created.

The combination of FIN_PLAN_TYPE_ID and LANGUAGE typically forms the table's unique key.

Common Use Cases and Queries

This table is primarily accessed by the Oracle Applications framework to retrieve locale-specific labels for financial plan types across forms, reports, and self-service pages. Common operational and reporting queries involve joining it with the base table to present a complete, language-specific view of plan types. A typical SQL pattern for retrieving active plan types for a session's language would be:

• SELECT b.FIN_PLAN_TYPE_CODE, tl.NAME
  FROM PA_FIN_PLAN_TYPES_B b,
  PA_FIN_PLAN_TYPES_TL tl
  WHERE b.FIN_PLAN_TYPE_ID = tl.FIN_PLAN_TYPE_ID
  AND tl.LANGUAGE = userenv('LANG')
  AND b.END_DATE_ACTIVE IS NULL;

Data in this table is usually maintained via the Oracle Applications translation forms or tools, not via direct SQL manipulation. Reports that list financial plan types for international user bases will rely on this table to ensure correct terminology.

Related Objects

As indicated by the metadata, PA_FIN_PLAN_TYPES_TL has a direct and critical relationship with its base table.

• PA_FIN_PLAN_TYPES_B: This is the primary related object. The TL table is a child of the B table via a foreign key constraint on the FIN_PLAN_TYPE_ID column. The B table contains the core definition, including the plan type code, start and end dates, and system-level controls.
• Financial Planning Forms and APIs: All user interfaces and public APIs within the Projects module that display or validate financial plan type descriptions will internally reference this translation table to resolve the appropriate name for the user's session language.
• Seed Data: The initial set of translated names is delivered as seed data during the installation or upgrade of the Oracle E-Business Suite and the Projects module.