Results for “okx_organization_defs_v”

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

Overview

OKX_ORGANIZATION_DEFS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the OKX – Contracts Integration product. The view's documented purpose is to expose "Organization unit definitions," presenting a denormalized, reporting-friendly projection of organization records that originate in Oracle HRMS and Oracle Inventory. Within the ETRM (E-Business Suite Technical Reference Manual) it is cataloged as a VALID view in both the 12.1.1 and 12.2.2 documentation sets.

The OKX module handles contracts integration, and this view supplies the organization-unit reference data that integration flows and contract-related reporting rely upon. Rather than forcing consumers to join the HR organization tables, inventory parameters, and address formatting logic themselves, OKX_ORGANIZATION_DEFS_V packages that logic into a single queryable object. It exposes business group, legal entity, operating unit, and set of books identifiers alongside descriptive names, organization codes, addresses, and active/inactive status—making it a convenient source for validation lists, lookups, and downstream contract processing.

Underlying Base Objects

The view text joins six documented base objects, all referenced through synonyms in the APPS schema:

• HR_ALL_ORGANIZATION_UNITS (OU) – The primary organization unit table, driving ORGANIZATION_ID, BUSINESS_GROUP_ID, and the DATE_FROM/DATE_TO effective dates.
• HR_ALL_ORGANIZATION_UNITS_TL (OUTL) – The translation table supplying the organization NAME in the session language.
• HR_ORGANIZATION_INFORMATION (OI1, OI2) – Joined twice (aliased OI1 and OI2) to retrieve the organization classification context, including organization type, set of books, legal entity, and operating unit values.
• MTL_PARAMETERS (MTLP) – Inventory parameters, joined with an outer join (+) on ORGANIZATION_ID, providing the ORGANIZATION_CODE used for organization code, description, and party number.
• HR_LOCATIONS_ALL (LOC) – Location records yielding address components such as address lines, city, postal code, and country.
• ARP_ADDR_LABEL_PKG (PACKAGE) – The Receivables address formatting package, invoked via FORMAT_ADDRESS to build a single concatenated ADDRESS column.

Key Columns

• ID1 / ID2 – Key flexfield surrogate columns; ID1 carries ORGANIZATION_ID, ID2 is a constant '#' placeholder.
• ORGANIZATION_ID, BUSINESS_GROUP_ID – Core identifiers for the organization unit and its business group.
• NAME, ORGANIZATION_CODE, DESCRIPTION – Descriptive attributes; ORGANIZATION_CODE is derived from MTL_PARAMETERS.
• ORGANIZATION_TYPE, B_STATUS – Classification (for example INV or OPERATING_UNIT) and business-group status from HR organization information.
• STATUS – Derived active/inactive indicator ('A' or 'I') computed from SYSDATE against DATE_FROM/DATE_TO.
• SET_OF_BOOKS_ID, LEGAL_ENTITY, OPERATING_UNIT – DECODE-driven attributes resolved according to organization type.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective date range from the organization unit.
• ADDRESS, ADDRESS1–ADDRESS4, CITY, POSTAL_CODE, STATE, COUNTY, COUNTRY – Address fields, with ADDRESS assembled by ARP_ADDR_LABEL_PKG.
• WOMEN_OWNED_FLAG, SMALL_BUSINESS_FLAG, MINORITY_GROUP_LOOKUP_CODE – Present as NULL placeholders.

Common Use Cases and Queries

Typical uses include contract integration validation, organization lookup lists, and reporting on operating units and legal entities by effective status. A basic listing of active organizations:

• SELECT organization_id, name, organization_code, organization_type, status FROM apps.okx_organization_defs_v WHERE status = 'A';
• SELECT organization_id, name, legal_entity, operating_unit, set_of_books_id FROM apps.okx_organization_defs_v WHERE organization_type = 'OPERATING_UNIT';
• SELECT organization_code, name, address, city, country FROM apps.okx_organization_defs_v ORDER BY name;

Because STATUS is evaluated dynamically at query time, joins against this view automatically reflect current effective dating. Filtering by ORGANIZATION_TYPE isolates inventory organizations from operating units, and SET_OF_BOOKS_ID or LEGAL_ENTITY supports ledger-oriented reporting for contract integration scenarios.