Results for “ce_le_bg_ou_vs_v”

50+ results




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

Overview

CE_LE_BG_OU_VS_V is an APPS-owned database view in the Cash Management (CE) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to store organization access information, presenting a unified list of the organizations a given user is authorized to access. Rather than persisting its own data, the view dynamically derives results at query time from security grants and responsibility-level profile settings, returning one row per accessible organization. In practice, CE_LE_BG_OU_VS_V functions as a security-filtering construct for Cash Management and related Treasury flows, exposing three organization types:Legal entities (identified by a leading "L"), Business groups (identified by a leading "O", sourced from the PER_BUSINESS_GROUP_ID profile), and Operating units. Because access is evaluated against the session's current user context (FND_GLOBAL.USER_NAME / USER_ID) and the active responsibility, the same view can return different row sets for different sessions. This makes it central to reporting, integration, and any custom code that must honor EBS organization-level access rules within the Cash Management domain.

Underlying Base Objects

The view is defined over a mix of synonyms, views, and packages. Grant-based legal entity access is resolved from FND_GRANTS joined to FND_OBJECTS, WF_USER_ROLES, and XLE_ENTITY_PROFILES, keyed on the object name 'CEBAA' and an INSTANCE_PK1_VALUE matching the legal entity ID. A second branch handles direct user grants through FND_GRANTS and XLE_ENTITY_PROFILES. A third branch derives legal entity access from XTR_PARTIES_V, GL_SETS_OF_BOOKS, XLE_ENTITY_PROFILES, XTR_COMPANY_AUTHORITIES, and XTR_DEALER_CODES, using XTR_USER_ACCESS-style dealer authority logic. Business group access is supplied directly from DUAL using FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID') and the organization name from FND_ACCESS_CONTROL_UTIL.GET_ORG_NAME. Operating unit access is drawn from HR_OPERATING_UNITS, with MO_GLOBAL and FND_ACCESS_CONTROL_UTIL providing the access-control filtering. FND_GLOBAL, FND_PROFILE, and XTR_USER_ACCESS supply session and authority context, while FND_USER, WF_LOCAL_ROLES, and DUAL are referenced for identity resolution.

Key Columns

  • ORGANIZATION_TYPE — Classifies each row as 'LEGAL_ENTITY', 'BUSINESS_GROUP', or 'OPERATING_UNIT'; determines which identifier column is populated.
  • BUSINESS_GROUP_ID — Populated for business group rows; derived from FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID'). The primary column relevant to the search term "per_business_group_id".
  • LEGAL_ENTITY_ID — Populated for legal entity rows; the XLE_ENTITY_PROFILES.LEGAL_ENTITY_ID representing the accessible entity.
  • NAME — The organization name, taken from XLE_ENTITY_PROFILES.NAME for legal entities or resolved via FND_ACCESS_CONTROL_UTIL.GET_ORG_NAME for business groups and operating units.
  • Access key / organization key — The final concatenated expression (for example 'L'||LEGAL_ENTITY_ID or 'O'||business group ID) that uniquely tags the organization for downstream lookups.

Common Use Cases and Queries

Typical scenarios include restricting Cash Management dashboards or custom reports to the legal entities, business group, and operating units a user may see, and validating organization access before posting or querying treasury data. A simple query listing all accessible organizations follows:

  • SELECT organization_type, business_group_id, legal_entity_id, name FROM ce_le_bg_ou_vs_v ORDER BY organization_type, name;
  • To isolate the current user's business group: SELECT name, business_group_id FROM ce_le_bg_ou_vs_v WHERE organization_type = 'BUSINESS_GROUP';
  • To list accessible legal entities only: SELECT legal_entity_id, name FROM ce_le_bg_ou_vs_v WHERE organization_type = 'LEGAL_ENTITY';

Because results depend on FND_GLOBAL session context and the PER_BUSINESS_GROUP_ID profile, queries return meaningful data only when run within an authenticated EBS session (for example, via a concurrent program or an APPS-schema session). The business group row appears only when PER_BUSINESS_GROUP_ID is not null for the current responsibility.