Results for “xla_post_acct_progs_vl”

28 results




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

Overview

XLA_POST_ACCT_PROGS_VL is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the translatable definition of subledger accounting posting programs — the executable programs registered with the Subledger Accounting Engine that create and post journal entries for a given subledger application. The view follows the standard EBS "_VL" (view with language) convention: it joins the base table to its translation table and filters on the session language, returning descriptive text in the language of the current user session. As a reporting and integration layer, it exposes posting program codes, their owning application, and their language-dependent name and description without requiring the caller to perform the translation join manually. It is read-only and is typically consumed by setup inquiries, diagnostics, and extension code that must resolve a posting program code to a user-facing name.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • XLA_POST_ACCT_PROGS_B — the base (non-translatable) table holding the posting program definition, including program code, program owner code, owning application, and standard WHO audit columns.
  • XLA_POST_ACCT_PROGS_TL — the translation table holding the language-specific NAME and DESCRIPTION for each program.

The join is performed on the composite key PROGRAM_CODE plus PROGRAM_OWNER_CODE, and the translation row is restricted by T.LANGUAGE = USERENV('LANG'), so each posting program returns exactly one row in the current session language. The view text also projects B.ROWID as ROW_ID. Because the defining query is a straight equijoin on the translation key and a language predicate, the view is not updateable and carries no additional aggregation or filtering logic beyond language restriction.

Key Columns

  • ROW_ID — the ROWID of the base table row in XLA_POST_ACCT_PROGS_B; useful for direct base-table addressing.
  • PROGRAM_CODE — the unique code identifying the posting program within the Subledger Accounting Engine.
  • PROGRAM_OWNER_CODE — the code identifying the owner (typically the subledger application) of the posting program; combined with PROGRAM_CODE it forms the translation join key.
  • APPLICATION_ID — the application identifier associated with the posting program, joinable to FND_APPLICATION.
  • NAME — the translated, user-facing name of the posting program from the TL table.
  • DESCRIPTION — the translated description of the posting program.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns sourced from the base table.

Common Use Cases and Queries

The view is most often used to translate a known program code into a display name or to enumerate available posting programs for a subledger during setup verification and troubleshooting.

  • Retrieve the name and description for a specific posting program:
SELECT program_code,
       program_owner_code,
       application_id,
       name,
       description
FROM   apps.xla_post_acct_progs_vl
WHERE  program_code = :p_program_code;
  • List all posting programs owned by a given owner code:
SELECT program_code,
       name,
       application_id
FROM   apps.xla_post_acct_progs_vl
WHERE  program_owner_code = :p_owner_code
ORDER  BY name;
  • Resolve the owning application name for reporting by joining to the application registry:
SELECT v.program_code,
       v.name,
       a.application_short_name
FROM   apps.xla_post_acct_progs_vl v,
       apps.fnd_application_vl a
WHERE  v.application_id = a.application_id;

These queries are safe for concurrent reporting because the view is read-only and the language predicate is resolved from the session environment. All access should be granted through the APPS schema, consistent with standard EBS security practice.