Search Results oracle base and oracle home configuration




PA_GANTT_CONFIG_TL (Project Accounting Gantt Configuration Translation Table)
Overview

The PA_GANTT_CONFIG_TL table is a translation table within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 that stores multilingual support data for Gantt chart configurations in the Project Accounting module. This table works in conjunction with its base table PA_GANTT_CONFIG to provide translated descriptions and labels for Gantt chart elements across different language implementations.

Primary Purpose

This table serves as the repository for translated text associated with Gantt chart configuration settings in multi-language Oracle EBS environments. It enables organizations to display project planning and tracking information in localized languages while maintaining a single configuration structure in the base table.

Technical Specifications:
- Table Type: Translation Table (TL)
- Module: Project Accounting (PA)
- Related Base Table: PA_GANTT_CONFIG
- Key Columns: CONFIG_ID, LANGUAGE, SOURCE_LANG
- Multi-Org Enabled: No
- Audited: Typically yes (depends on implementation)
Key Columns and Structure

The table contains these critical columns:

  • CONFIG_ID: Foreign key reference to PA_GANTT_CONFIG
  • LANGUAGE: ISO language code (e.g., 'US' for American English)
  • SOURCE_LANG: Indicates the source language of the translation
  • CONFIG_NAME: Translated name of the Gantt configuration
  • DESCRIPTION: Localized description text
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE: Standard Oracle audit columns
Functional Integration

PA_GANTT_CONFIG_TL integrates with these EBS components:

  1. Project Planning and Scheduling tools
  2. Oracle Projects module reporting
  3. Multi-language support framework
  4. Project Gantt chart rendering engine
Implementation Considerations

For implementations using multiple languages:

  • Translation records are automatically created when new configurations are added
  • Default translations use the installation's base language
  • Custom translations require proper NLS (National Language Support) setup
  • Performance impact is minimal as translations are cached
Maintenance Best Practices

Recommended practices include:

  1. Using standard Oracle translation tools for updates
  2. Maintaining translation consistency across modules
  3. Validating translations after major upgrades
  4. Including translation tables in custom report development
Upgrade Impact

Between 12.1.1 and 12.2.2, the table structure remained consistent, but:

  • New languages may be added during upgrade
  • Online patching in 12.2.2 affects maintenance windows
  • Translation data migrates automatically during upgrades