Results for “run_posting_flag”

14 results




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

Overview

GL_CONS_SET_NAMES_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, security-aware listing of consolidation sets defined in the Oracle General Ledger consolidation workbench. A consolidation set identifies a source ledger, a target (parent) ledger, the consolidation method, and a collection of runtime options that govern how balances are transferred, summarized, and posted during a consolidation run.

The view is primarily consumed by consolidation setup forms, list-of-values queries, and reporting or integration components that must display the consolidation set name (cons_set_name) together with its target ledger and method without joining the underlying transaction tables directly. Because it embeds row-level data security through the FND_DATA_SECURITY package, it is the canonical read interface for consolidation set metadata within the EBS application tier.

Underlying Base Objects

The view is defined over four documented objects:

  • GL_CONSOLIDATION_SETS (SYNONYM) — the driving table holding consolidation set definitions, including source/target ledger mapping, method code, and runtime flags. Aliased as CONS.
  • GL_LEDGERS (SYNONYM) — the target ledger master, joined on CONS.TO_LEDGER_ID = LGR.LEDGER_ID. Supplies currency, calendar, period type, and the consolidation ledger flag. Aliased as LGR.
  • GL_LOOKUPS (VIEW) — a lookup view restricted to LOOKUP_TYPE = 'CONSOLIDATION_METHOD', joined on LOOKUP_CODE = CONS.METHOD to resolve the method meaning. Aliased as L.
  • FND_DATA_SECURITY (PACKAGE) and FND_GLOBAL (PACKAGE) — invoked in the SELECT list to evaluate per-user privileges against the consolidation set data security object.

No direct base table access is required by callers; the joins and security logic are encapsulated in the view definition.

Key Columns

Common Use Cases and Queries

Typical scenarios include LOV population during consolidation definition, dependency analysis when changing a target ledger, and migration or audit extracts. A common query to retrieve consolidation sets by name is:

  • SELECT consolidation_set_id, cons_set_name, to_ledger_name, method_meaning, currency_code, calendar FROM gl_cons_set_names_v WHERE cons_set_name LIKE :search ORDER BY cons_set_name;
  • Filtering by target ledger: SELECT cons_set_name, method_meaning FROM gl_cons_set_names_v WHERE to_ledger_id = :ledger_id;
  • Security-limited listings that display only sets the current user may view: SELECT cons_set_name, view_privilege, use_privilege, modify_privilege FROM gl_cons_set_names_v WHERE view_privilege = 'Y';

Because the security columns depend on FND_GLOBAL and FND_DATA_SECURITY evaluated in the session context, queries should be executed after FND_GLOBAL.APPS_INITIALIZE in custom code paths.