Search Results user_definition_enable_date

Overview

MSD_ORGANIZATION_DEFINITIONS is an APPS-owned database view within the Oracle E-Business Suite Demand Planning (MSD) product family, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to expose organization definitions — that is, the inventory organizations and their associated accounting, legal, and calendar attributes — in a denormalized, reporting-friendly form. The view consolidates attributes that are otherwise scattered across the Human Resources organization model, the inventory parameters table, and the General Ledger sets of books, thereby providing a single-row-per-organization projection suitable for demand planning, supply chain reporting, and downstream integration extracts.

The view is particularly relevant to users searching for the identifier USER_DEFINITION_ENABLE_DATE. That column is an alias for HR_ALL_ORGANIZATION_UNITS.DATE_FROM, the effective start date of the organization unit definition. The complementary DATE_TO value is exposed as DISABLE_DATE. Because the view filters on MP.PROCESS_ENABLED_FLAG = 'N', it returns only organizations that are treated as inventory organizations for planning purposes rather than as process-enabled manufacturing entities.

Underlying Base Objects

The documented base objects behind the view are:

• HR_ALL_ORGANIZATION_UNITS_VL (VIEW) — source of organization identity and date-effectivity: ORGANIZATION_ID, BUSINESS_GROUP_ID, NAME, DATE_FROM, DATE_TO.
• HR_ORGANIZATION_INFORMATION (SYNONYM) — joined twice (aliases HOI1 and HOI2). HOI1 supplies the 'CLASS' context, confirming the organization is an inventory organization ('INV' with INVENTORY_ENABLED_FLAG = 'Y'). HOI2 supplies the 'ACCOUNTING INFORMATION' context, from which the legal entity and set of books linkage are derived.
• MTL_PARAMETERS (SYNONYM) — provides ORGANIZATION_CODE and CALENDAR_CODE, and enforces the PROCESS_ENABLED_FLAG = 'N' filter.
• GL_SETS_OF_BOOKS (VIEW) — supplies SET_OF_BOOKS_ID and CHART_OF_ACCOUNTS_ID, joined to the accounting information context via HOI2.ORG_INFORMATION1 = TO_CHAR(GSOB.SET_OF_BOOKS_ID).
• FND_PRODUCT_GROUPS (SYNONYM) — provides MULTI_ORG_FLAG, used to decide whether the operating unit value is populated.

All joins are equijoins on ORGANIZATION_ID, and the view therefore yields one row per qualifying inventory organization that has valid class and accounting information.

Key Columns

• ORGANIZATION_ID / BUSINESS_GROUP_ID — primary and business group identifiers.
• USER_DEFINITION_ENABLE_DATE — alias for HR_ALL_ORGANIZATION_UNITS.DATE_FROM; the effective enablement date.
• DISABLE_DATE — alias for DATE_TO; null for currently active organizations.
• ORGANIZATION_CODE / ORGANIZATION_NAME — inventory code from MTL_PARAMETERS and descriptive name.
• SET_OF_BOOKS_ID / CHART_OF_ACCOUNTS_ID — GL accounting context.
• INVENTORY_ENABLED_FLAG — ORG_INFORMATION2 from the CLASS context.
• OPERATING_UNIT — populated via DECODE on MULTI_ORG_FLAG = 'Y'.
• LEGAL_ENTITY — derived from ORG_INFORMATION2 in the ACCOUNTING INFORMATION context.
• CALENDAR_CODE — inventory calendar from MTL_PARAMETERS.

Common Use Cases and Queries

Typical scenarios include validating which organizations are enabled for inventory and demand planning, reconciling organization enablement dates against accounting configuration, and driving extracts that require the legal entity and operating unit mapping.

Example: list active inventory organizations with their enablement dates.

SELECT organization_id,
       organization_code,
       organization_name,
       user_definition_enable_date,
       disable_date
  FROM apps.msd_organization_definitions
 WHERE disable_date IS NULL
 ORDER BY organization_code;

Example: retrieve organizations by set of books and legal entity.

SELECT organization_code,
       set_of_books_id,
       legal_entity,
       operating_unit,
       calendar_code
  FROM apps.msd_organization_definitions
 WHERE set_of_books_id = :p_sob_id;

Because the view is read-only and derived from HR, INV, and GL sources, no DML should be issued against it. Queries should be tuned against the underlying tables, particularly HR_ORGANIZATION_INFORMATION, which is joined twice and can dominate execution cost on large multi-organization installations.