Results for “short_code”

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

Overview

The APPS.HR_OPERATING_UNITS view is a reporting and integration object within the PER (Human Resources) product family of Oracle E-Business Suite. It exposes information about operating units, which are the organizations within a legal entity that perform day-to-day transactional activities such as sales, purchasing, and receivables. Operating units are a foundational construct in the Oracle EBS multi-organization architecture, and this view provides a consolidated, query-friendly representation of them without requiring the consumer to navigate the underlying organization classification and information tables directly.

In Oracle EBS 12.1.1 and 12.2.2, the view carries a VALID status in the APPS schema and is documented in the ETRM repository. Because it belongs to the HR product and is defined over the HR organization model, it is frequently referenced by concurrent programs, discoverer reports, custom SQL, and integration interfaces that need to resolve operating unit identifiers to descriptive names and associated legal entity and ledger attributes. It abstracts the complex organization classification model into a single view, making it suitable for joins with other multi-org views such as ORG_ORGANIZATION_DEFINITIONS and financial tables keyed by ORG_ID.

Underlying Base Objects

The view is defined over three base objects in the APPS schema, resolved through synonyms:

• HR_ALL_ORGANIZATION_UNITS — the master organization definition table (aliased O), supplying the business group, organization identifier, and effective dates.
• HR_ALL_ORGANIZATION_UNITS_TL — the translated (language) table (aliased OTL), supplying the organization name in the session language.
• HR_ORGANIZATION_INFORMATION — the organization classification table, joined twice: once as O2 to identify the CLASS context where ORG_INFORMATION1 = 'OPERATING_UNIT' and ORG_INFORMATION2 = 'Y', and once as O3 for the OPERATING UNIT INFORMATION context.

The view joins all of these on ORGANIZATION_ID and filters the translated rows by OTL.LANGUAGE = USERENV('LANG'), ensuring the name returned matches the current session language. This design means the view only returns organizations explicitly classified as operating units.

Key Columns

• BUSINESS_GROUP_ID — the identifier of the business group that owns the operating unit; used to scope queries to a specific HR business group.
• ORGANIZATION_ID — the unique organization identifier for the operating unit.
• NAME — the translated display name of the operating unit, sourced from the TL table in the session language.
• DATE_FROM / DATE_TO — the effective date range of the organization unit record.
• LEGAL_ENTITY_ID — the legal entity to which the operating unit belongs, derived from the operating unit information context.
• SET_OF_BOOKS_ID — the ledger (set of books in 12.1.1 terminology) associated with the operating unit, mapping it to its accounting context.

Common Use Cases and Queries

Typical scenarios include resolving an ORG_ID to a friendly name for reports, validating operating unit assignments in integrations, and joining to subledger data that is partitioned by operating unit.

List all operating units for a business group:

• SELECT organization_id, name, legal_entity_id, set_of_books_id FROM apps.hr_operating_units WHERE business_group_id = :p_bg_id ORDER BY name;

Join to a transaction table to translate operating unit identifiers:

• SELECT h.name, t.* FROM apps.hr_operating_units h, apps.some_txn_table t WHERE h.organization_id = t.org_id;

Because the view is not a table, no DML should be issued against it. Queries should be scoped by BUSINESS_GROUP_ID or ORGANIZATION_ID for performance, and effective dates considered where point-in-time accuracy is required.