Results for “xla_post_acct_progs_tl”

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

Overview

XLA_POST_ACCT_PROGS_TL is a translation table within the XLA (Subledger Accounting) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific, translated columns for Post-Accounting Programs — the concurrent programs that execute the transfer of subledger journal entries to the General Ledger after accounting has been generated. Post-accounting programs include functionality such as transferring journal entries to GL, creating and applying accruals, and running period-close processing for subledger journals.

The "_TL" suffix is a standard Oracle EBS convention indicating that the table holds translatable descriptive columns (NAME, DESCRIPTION) for a base entity, allowing each supported language to present the program name and description in the user's native language. The base, language-independent attributes reside in the corresponding XLA_POST_ACCT_PROGS_B table, and the two are joined by the program's business key plus LANGUAGE. In terms of heuristic Data Vault classification, the metadata designates this object as standalone; in practice it most closely resembles a satellite table attached to the base program definition, carrying descriptive, language-dependent attributes.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

• PROGRAM_OWNER_CODE — identifies the owner (application) of the post-accounting program; part of the composite primary key.
• PROGRAM_CODE — the internal code uniquely identifying the post-accounting program within its owner; also part of the primary key.
• LANGUAGE — the language code for the translated row, forming the third component of the primary key and determining which locale's text is returned.
• SOURCE_LANG — the source language from which the row was derived, used by the translation (TL) framework to track the origin of the translated content.
• NAME — the translated display name of the post-accounting program; also forms part of the XLA_POST_ACCT_PROGS_TL_U2 unique index.
• DESCRIPTION — the translated description explaining the program's purpose.
• ZD_EDITION_NAME — the editioning column introduced for online patching in EBS 12.2, included in both unique indexes to support edition-based redefinition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording row creation and last modification.

The surrogate primary key is XLA_POST_ACCT_PROGS_TL_PK over (PROGRAM_OWNER_CODE, PROGRAM_CODE, LANGUAGE). Two unique indexes serve as business-key candidates: XLA_POST_ACCT_PROGS_TL_U1 (PROGRAM_OWNER_CODE, PROGRAM_CODE, LANGUAGE, ZD_EDITION_NAME) and XLA_POST_ACCT_PROGS_TL_U2 (PROGRAM_OWNER_CODE, NAME, LANGUAGE, ZD_EDITION_NAME), the latter enforcing that the translated name is unique per owner and language within an edition.

Common Use Cases and Queries

This table is primarily queried to obtain user-language names and descriptions of post-accounting programs for display in concurrent program lists, setup forms, and diagnostics. The ubiquitous join pattern combines the translation table with its base table using the business key and the session language:

• List programs in the current language: SELECT b.program_owner_code, b.program_code, t.name, t.description FROM xla_post_acct_progs_b b, xla_post_acct_progs_tl t WHERE b.program_owner_code = t.program_owner_code AND b.program_code = t.program_code AND t.language = USERENV('LANG');
• Audit translations: query where LANGUAGE <> SOURCE_LANG to identify rows that have been translated from the base language, supporting localization validation.
• Verify seeded programs: filter by PROGRAM_OWNER_CODE (for example, the XLA owner) and PROGRAM_CODE to confirm that standard post-accounting programs are properly defined and translated after patching.
• Post-patch troubleshooting: compare row counts in the _TL and _B tables to detect missing or orphaned translations that could cause programs to display as untranslated.

Reporting rarely targets this object directly; instead it is used as a lookup to embellish dashboards or extracts that enumerate subledger accounting concurrent programs.

Related Objects

The following objects are most significant in relation to XLA_POST_ACCT_PROGS_TL:

• XLA_POST_ACCT_PROGS_B — the base, language-independent table holding the untranslated program definition; joined on PROGRAM_OWNER_CODE and PROGRAM_CODE.
• XLA_POST_ACCT_PROGS_VL — the translated view that union-selects base and translation rows using the current session language, commonly queried by forms and reports.
• XLA_POST_ACCT_PROGS_V — the standard (base-only) view over the program definition.
• XLA_ACCT_PROGRAMS — broader accounting program definitions that reference post-accounting processing logic via program codes.
• FND_CONCURRENT_PROGRAMS — the concurrent manager repository that links the post-accounting program code to the executable run by the concurrent manager.
• XLA_LOOKUPS — defines the lookup values (such as owner and language codes) referenced by this table's code columns.
• FND_LANGUAGES — the language repository joined on LANGUAGE to resolve language names for reporting.

These relationships are founded on the documented composite keys and the standard EBS _B/_TL/_VL pattern rather than on explicit foreign key constraints, since the object is classified as standalone in the FK structure.