Results for “maintenance_dept_id”

5 results




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

Overview

The AHL_MR_ORGANIZATIONS table resides in the AHL schema and belongs to the Complex Maintenance Repair and Overhaul (AHL) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the organization-modeling anchor for maintenance and overhaul transactions, defining which maintenance organizations, departments, and operating organizations participate in the maintenance repair (MR) framework. In practical terms, the table stores the organizational context required before maintenance work orders, routings, and resource assignments can be processed against a specific maintenance entity.

The documented relationship structure classifies this object, as a modeling suggestion, as a standalone Data Vault entity. Its only foreign key reference is to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, indicating the table is not a dependent child of another AHL transaction table but rather a foundational reference and configuration entity. The table contains 28 documented columns and includes the standard EBS WHO (Who) audit columns and the DFF-enabled ATTRIBUTE1 through ATTRIBUTE15 flexfield columns, confirming it is a fully registered, multi-org aware EBS table.

Key Information Stored

The most significant columns and their roles are as follows:

  • MR_ORGANIZATION_ID — the surrogate primary key uniquely identifying each maintenance repair organization record.
  • MAINTENANCE_ORG_ID — the operating unit or inventory organization designated for maintenance execution; a primary business-key candidate.
  • MAINTENANCE_DEPT_ID — the maintenance department associated with the MR organization.
  • OPERATING_ORG_ID — the operating organization owning or driving the maintenance activity; a second business-key candidate.
  • MR_TITLE — the descriptive name or title of the maintenance repair organization.
  • OBJECT_VERSION_NUMBER — optimistic locking column used for concurrency control in the OAF/ADF-based forms architecture.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing data security grouping across organizations.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns recording creation and modification history.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield (DFF) columns enabling customer-specific extension of the base schema without structural modification.

Common Use Cases and Queries

This table is queried when validating organizational setup for maintenance transactions, when resolving the operating unit to which a maintenance repair belongs, and when filtering AHL dashboards and reports by maintenance organization. A representative lookup is:

  • Resolve an MR organization by operating unit: SELECT mr_organization_id, mr_title, maintenance_org_id FROM ahl_mr_organizations WHERE operating_org_id = :p_org_id;
  • Join to security groups: SELECT m.mr_title, s.security_group_name FROM ahl_mr_organizations m, fnd_security_groups s WHERE m.security_group_id = s.security_group_id;
  • Audit recent changes: SELECT mr_organization_id, last_updated_by, last_update_date FROM ahl_mr_organizations WHERE last_update_date > SYSDATE - 30;
  • DFF reporting: SELECT mr_organization_id, attribute_category, attribute1, attribute2 FROM ahl_mr_organizations;

Typical consumers include maintenance planning reports, organizational validation concurrent programs, and integration extracts that synchronize AHL organization data with external MRO or ERP systems.

Related Objects

Because the table is standalone, the primary documented dependency is inbound to FND_SECURITY_GROUPS. Related and commonly joined EBS objects include:

Collectively these objects frame the organizational setup layer required to operate the Complex Maintenance Repair and Overhaul module.