Search Results owning_department_code




Overview
Explore in AI Chat

Overview

APPS.MTL_EAM_EQUIP_RESOURCES_V is a reporting and integration view in Oracle E-Business Suite (EAM / Enterprise Asset Management) that consolidates equipment resource definitions together with the department context in which each equipment instance is used. Rather than requiring consumers to join the underlying BOM resource, department, and instance tables directly, the view presents a denormalized, ready-to-use result set in which each row describes an equipment resource identified by organization, resource, instance, and department.

The view is defined as a UNION of two branches. The first branch derives its data from the BOM resource and department tables within the EAM schema; the second branch selects the equivalent columns from GMP_EAM_EQUIP_RESOURCES_V, which serves the process manufacturing (OPM) side of the application. This union strategy provides a single, consistent access point for equipment resource data across discrete and process manufacturing deployments, making the view suitable for reporting, discovery, and integration layers that must not be coupled to either source model separately.

The name of the view, together with its department-oriented columns, aligns with the user search term "share_from_dept_code." The view exposes both the raw identifier (SHARE_FROM_DEPT_ID) and the corresponding department code (SHARE_FROM_DEPT_CODE), which represents the department from which equipment capacity is shared. A related computed column, OWNING_DEPARTMENT_CODE, resolves the effective owning department when sharing is in effect.

Underlying Base Objects

Per the documented view metadata, the following base objects are referenced:

  • BOM_RESOURCE_EQUIPMENTS — links resources to specific equipment instances and inventory items.
  • BOM_RESOURCES — supplies the resource code, description, unit of measure, and autocharge type.
  • BOM_DEPT_RES_INSTANCES — associates a resource instance with a department and serial number.
  • BOM_DEPARTMENT_RESOURCES — holds the department-to-resource assignment, capacity units, and sharing attributes such as SHARE_FROM_DEPT_ID and SHARE_CAPACITY_FLAG.
  • BOM_DEPARTMENTS — referenced twice, once as the primary department (BD) and once as the sharing/owning department (BD1, outer-joined on SHARE_FROM_DEPT_ID).
  • GMP_EAM_EQUIP_RESOURCES_V — provides the process manufacturing rows combined via UNION.

The join condition uses DECODE(BDR.SHARE_FROM_DEPT_ID, NULL, BDR.DEPARTMENT_ID, BDR.SHARE_FROM_DEPT_ID) = BDRI.DEPARTMENT_ID, so the instance's department is matched to the owning department when no sharing is defined, and to the sharing department when sharing is in effect.

h4>Key Columns
  • ROW_ID — the ROWID of the driving BOM_DEPARTMENT_RESOURCES row.
  • ORGANIZATION_ID, INVENTORY_ITEM_ID, SERIAL_NUMBER — identify the organization and the specific equipment item instance.
  • RESOURCE_ID, RESOURCE_CODE, DESCRIPTION — the resource identity and descriptive text.
  • INSTANCE_ID — the equipment instance associated with the resource.
  • DEPARTMENT_ID, DEPARTMENT_CODE — the department recorded against the resource assignment.
  • SHARE_FROM_DEPT_ID, SHARE_FROM_DEPT_CODE — the department whose capacity is shared (the subject of the user's search); null when no sharing applies.
  • OWNING_DEPARTMENT_CODE — computed via DECODE(BD1.DEPARTMENT_CODE, NULL, BD.DEPARTMENT_CODE, BD1.DEPARTMENT_CODE), returning the sharing department code when present, otherwise the primary department code.
  • CAPACITY_UNITS, AVAILABLE_24_HOURS_FLAG, SHARE_CAPACITY_FLAG — capacity and scheduling attributes governing availability and whether capacity is shared.
  • RESOURCE_GROUP_NAME, UNIT_OF_MEASURE, AUTOCHARGE_TYPE, CTP_FLAG, SCHEDULE_TO_INSTANCE — additional planning and scheduling characteristics.
h4>Common Use Cases and Queries

A frequent requirement is identifying which equipment resources draw capacity from another department — a direct application of the SHARE_FROM_DEPT_CODE column. The following query lists equipment resources together with their owning and sharing departments:

  • SELECT organization_id, resource_code, instance_id, department_code, share_from_dept_code, owning_department_code FROM apps.mtl_eam_equip_resources_v WHERE share_from_dept_code IS NOT NULL;

For capacity planning, filter on sharing and availability flags:

  • SELECT resource_code, department_code, capacity_units, available_24_hours_flag FROM apps.mtl_eam_equip_resources_v WHERE share_capacity_flag = 'Y'

To restrict reporting to a single organization or resource, add predicates on ORGANIZATION_ID or RESOURCE_ID. Integration consumers can safely use OWNING_DEPARTMENT_CODE as the canonical department for a resource instance regardless of whether sharing is configured, since the view resolves that logic on the database side.