Search Results fnd_concurrent_programs_tl

The FND_CONCURRENT_PROGRAMS_TL table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for storing translated descriptions and user-friendly names of concurrent programs. As part of the Application Object Library (AOL) module, it supports multilingual implementations by maintaining language-specific metadata for concurrent programs, which are executable processes scheduled to run in the background. This table works in conjunction with its base table, FND_CONCURRENT_PROGRAMS, following Oracle’s translatable table design pattern where the _TL suffix denotes a translation layer.

Table Structure and Key Columns

The table’s structure includes both technical and descriptive columns:

• APPLICATION_ID: Foreign key linking to FND_APPLICATION, identifying the owning application.
• CONCURRENT_PROGRAM_ID: Primary key column, referenced from FND_CONCURRENT_PROGRAMS.
• LANGUAGE: Stores the ISO language code (e.g., 'US' for English) for multilingual support.
• SOURCE_LANG: Indicates the source language of the original record.
• USER_CONCURRENT_PROGRAM_NAME: End-user visible name (up to 80 characters) displayed in the Concurrent Programs form.
• DESCRIPTION: Detailed functional explanation of the program (up to 240 characters).

Functional Role in EBS

This table enables:

1. Multilingual UI Support: Allows concurrent program names/descriptions to render in the user’s session language.
2. Runtime Label Resolution: The Concurrent Manager uses this data when displaying job statuses or logs.
3. Reporting Clarity: Translated names appear in standard reports like Concurrent Program Executions (FNDCPCON).

Integration Points

Key integration dependencies include:

• Concurrent Program Definition: Joins with FND_CONCURRENT_PROGRAMS via CONCURRENT_PROGRAM_ID.
• Value Set Validation: Some programs reference value sets with translated prompts stored in FND_FLEX_VALUES_TL.
• OA Framework: Translation files (.xlf) may synchronize with these entries for consistency.

Technical Considerations

1. Indexing: Oracle creates unique indexes on (CONCURRENT_PROGRAM_ID, LANGUAGE) for performance.
2. Seed Data Predefined programs (e.g., 'General Ledger Journal Import') include translations for 30+ languages.
3. Patching Impact: AD patches may update translations during localization upgrades.
4. Customization Adding custom translations requires proper NLS settings to avoid data corruption.

Version-Specific Notes

In EBS 12.2.2, this table resides in the APPS schema but is accessed via edition-based redefinition (EBD) views. The 12.2.2 architecture enhances translation management through:

• Online Translation Editor integration
• Improved synchronization with Oracle Translation Hub
• Reduced patching downtime for language updates

Common Maintenance Operations

Administrators typically interact with this table indirectly through:

• Concurrent Program Form (Navigation: System Administrator > Concurrent > Program > Define)
• AD Administration Utility: For bulk language maintenance
• FNDLOAD: To extract/upload translations using .ldt files

This table exemplifies Oracle’s approach to separating functional logic (FND_CONCURRENT_PROGRAMS) from presentation layer (_TL table), ensuring both technical robustness and localization flexibility.