Search Results master_organization_code

Overview

The APPS.INVFV_INVENTORY_ORGANIZATIONS view is a denormalized reporting and integration object within the Oracle E-Business Suite Inventory (INV) module. It consolidates the primary configuration attributes of both inventory organizations and their associated master organizations into a single flat structure. Rather than requiring application code or reports to join MTL_PARAMETERS to HR_ALL_ORGANIZATION_UNITS and multiple lookup sources, this view exposes organization identifiers, codes, names, cost method, costing organization references, calendar assignments, ATP and picking rules, and the full set of accounting flexfield references in one place.

The view is marked as retrofitted, indicating it was re-implemented during the transition toward Oracle EBS 12.2.x architecture while retaining its name and column contract. Its schema owner is APPS, and the object resides in the INV product schema, making it a standard reference point for organization-level configuration queries. Because the object is a view rather than a base table, it carries no storage of its own and is intended strictly for read access.

For users investigating the master_organization_code attribute, this view is the canonical location because it joins the operating organization parameters to the master organization record and surfaces both the master organization ID and its code in the same row.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all exposed through synonyms in the APPS schema:

• MTL_PARAMETERS — the primary source, providing organization configuration such as cost method, costing organization, calendar, ATP rule, picking rule, and default accounts.
• HR_ALL_ORGANIZATION_UNITS — supplies the descriptive organization name for each organization ID.
• BOM_CALENDARS and BOM_EXCEPTION_SETS — provide the production calendar description and exception set name.
• BOM_RESOURCES — supplies the default resource code used in cost rollups.
• MTL_ATP_RULES and MTL_PICKING_RULES — supply ATP and picking rule names.
• GL_CODE_COMBINATIONS — supplies the accounting flexfield references for the many inventory accounts exposed by the view.

The view text shows MTL_PARAMETERS joined multiple times (aliased MP, MP1, MP2, MP3) to resolve the operating organization, master organization, costing organization, and source organization respectively, each paired with its own HR_ALL_ORGANIZATION_UNITS alias (HOU, HOU1, HOU2, HOU3). Message and lookup columns are exposed through value-set substitution placeholders that resolve at runtime.

Key Columns

• ORGANIZATION_ID and ORGANIZATION_CODE — the operating inventory organization.
• MASTER_ORGANIZATION_ID and the aliased MP1.ORGANIZATION_CODE — the master organization identifier and code, the attribute most commonly searched for as master_organization_code.
• COST_ORGANIZATION_ID with MP2.ORGANIZATION_CODE — the costing organization reference.
• CALENDAR_CODE and EXCEPTION_SET_NAME — manufacturing calendar configuration.
• DEFAULT_ATP_RULE_ID and DEFAULT_PICKING_RULE_ID with their rule names — order fulfillment defaults.
• Account columns such as MATERIAL_ACCOUNT, COST_OF_SALES_ACCOUNT, and ENCUMBRANCE_ACCOUNT — each bound to a GL code combination key flexfield.
• Lookup-based columns such as GENERAL_LEDGER_UPDATE_CODE, NEGATIVE_INV_RECEIPT_CODE, and STOCK_LOCATOR_CONTROL_CODE — descriptive flags resolved from message lookup views.

Common Use Cases and Queries

The predominant use case is resolving the master organization for a given inventory organization, or listing all organizations under a specific master. For example:

• Retrieving the master code for a single organization: SELECT organization_code, master_organization_code FROM apps.invfv_inventory_organizations WHERE organization_code = :org_code;
• Listing all child organizations for a master: SELECT organization_code FROM apps.invfv_inventory_organizations WHERE master_organization_code = :master_code;
• Auditing costing and calendar configuration: SELECT organization_code, cost_organization_id, calendar_code FROM apps.invfv_inventory_organizations;
• Reconciling account assignments across organizations for subledger mapping validation.

Because all joins are predefined, these queries avoid the complexity of manually linking MTL_PARAMETERS to organization units and are suitable for reports, interfaces, and diagnostic scripts across both 12.1.1 and 12.2.2.