Search Results expenditure_organization_code




Overview

BOMFV_MFG_DEPARTMENTS is an APPS-owned, read-only view in the Oracle E-Business Suite Bills of Material (BOM) module. The object carries the "Retrofitted" designation in the ETRM metadata, indicating that it was re-pointed to the current 12.1.1 / 12.2.2 base schema while preserving the historical column contract and view name. It presents manufacturing department definitions alongside the descriptive attributes of both the owning inventory organization and the expenditure organization to which a department is optionally assigned.

The view exists to simplify reporting and integration against department data. Rather than requiring a caller to join BOM_DEPARTMENTS to organization and location tables in order to obtain readable codes and names, the view performs that join internally and exposes a denormalized projection. It is defined WITH READ ONLY, so it is not a DML target; it is intended strictly for query and extraction. Because the view references the secured organization unit table, row-level access is constrained by the security predicate embedded in the view text, meaning a session only sees departments for organizations it is authorized to access.

Underlying Base Objects

The view is defined over four referenced base objects, all accessed through APPS synonyms: BOM_DEPARTMENTS, HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS_ALL, and MTL_PARAMETERS. BOM_DEPARTMENTS (aliased DE) is the driving table and supplies the department identity, class, description, disable date, location, and the expenditure organization identifier.

  • MTL_PARAMETERS (aliased PA) is joined on ORGANIZATION_ID and supplies the owning organization code of the department.
  • HR_ALL_ORGANIZATION_UNITS (aliased AL) is joined on ORGANIZATION_ID and supplies the organization name.
  • HR_LOCATIONS_ALL (aliased LO) is outer-joined on LOCATION_ID, so departments without a location still appear.
  • MTL_PARAMETERS (aliased PA2) and HR_ALL_ORGANIZATION_UNITS (aliased AL2) are outer-joined on PA_EXPENDITURE_ORG_ID, resolving the expenditure organization code and name where one is assigned.

The two outer joins on the expenditure organization are significant: departments that carry no expenditure organization identifier remain visible, with null expenditure code and name.

Key Columns

The projection includes identifiers, codes, descriptive names, and audit columns. DEPARTMENT_CODE, DESCRIPTION, and DEPARTMENT_CLASS_CODE describe the department itself. ORGANIZATION_CODE and ORGANIZATION_NAME identify the inventory organization that owns the department. INACTIVE_DATE reflects the source DISABLE_DATE, so a null value indicates an active department.

The columns most relevant to the search term "expenditure_organization_name" are EXPENDITURE_ORGANIZATION_CODE and EXPENDITURE_ORGANIZATION_NAME, both derived from the outer-joined HR_ALL_ORGANIZATION_UNITS record keyed by PA_EXPENDITURE_ORG_ID. Also exposed are LOCATION_NAME, the surrogate keys DEPARTMENT_ID, ORGANIZATION_ID, LOCATION_ID, and PA_EXPENDITURE_ORG_ID, the hidden "_DF" descriptive flexfield discriminator token, and the audit columns UPDATED_ON, UPDATED_BY, CREATED_ON, and CREATED_BY.

Common Use Cases and Queries

Typical uses include validating expenditure organization assignments on departments, producing organization-level department listings for costing and manufacturing reports, and feeding department reference data into integrations. A frequent pattern is to filter explicitly on the expenditure organization name:

  • SELECT department_code, organization_code, expenditure_organization_code, expenditure_organization_name FROM apps.bomfv_mfg_departments WHERE expenditure_organization_name = :p_org_name;
  • SELECT department_code, organization_name, expenditure_organization_name, location_name FROM apps.bomfv_mfg_departments WHERE inactive_date IS NULL ORDER BY organization_code, department_code;
  • SELECT department_id, department_code FROM apps.bomfv_mfg_departments WHERE expenditure_organization_name IS NULL; — identifies departments lacking an expenditure organization assignment.

Because rows are filtered by the security predicate on ORGANIZATION_ID, callers should not expect to see departments outside their authorized organization set. When the view is unavailable or restrictive, the equivalent result can be reproduced by joining BOM_DEPARTMENTS to MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS directly, replicating the outer join on PA_EXPENDITURE_ORG_ID used to derive the expenditure organization code and name.