Results for “ahl_build_goals”

22 results




Overview
Explore in AI Chat

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

Overview

AHL_BUILD_GOALS is a table in the AHL schema, belonging to the Oracle E-Business Suite product AHL – Complex Maintenance Repair and Overhaul (CMRO). It records "build goals," which represent quantitative, unit-of-measure-based targets associated with a visit or maintenance event. Each row captures a target value expressed against a specified unit of measure (UOM_CODE) and a counter value (COUNTER_VALUE), tied to a visit through VISIT_ID. In the context of complex MRO operations, this table supports the definition and tracking of measurable goals—such as flight hours, cycles, or other counters—that drive maintenance planning and execution.

From a heuristic Data Vault modeling perspective, the ETRM metadata classifies AHL_BUILD_GOALS as a standalone table. This suggests it is best understood as a satellite-like entity that records descriptive attributes and measures attached to a parent business key. The parent business key is most naturally the visit, referenced via VISIT_ID, while the row-level identity is provided by the generated BUILD_GOAL_ID. The absence of inbound foreign keys indicates the table is not itself a referenced parent in the modeled FK graph, reinforcing its role as a dependent, attribute-bearing object.

Key Information Stored

The table contains 27 documented columns. The most significant are:

  • BUILD_GOAL_ID – The surrogate primary key. It is the sole column of unique index AHL_BUILD_GOALS_U1 and uniquely identifies each build goal record.
  • VISIT_ID – Foreign key to AHL_VISITS_B. Identifies the visit or maintenance event to which the goal belongs. Together with UOM_CODE it forms the business-key candidate AHL_BUILD_GOALS_U2.
  • UOM_CODE – The unit of measure in which the goal is expressed. Combined with VISIT_ID, it enforces uniqueness of the goal per visit per unit of measure.
  • COUNTER_VALUE – The numeric target or counter associated with the build goal, expressed in UOM_CODE.
  • SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or organizational data segregation and access control.
  • OBJECT_VERSION_NUMBER – Implements optimistic locking, preventing lost updates in concurrent editing scenarios.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard Oracle EBS audit columns that record who created and last modified each row and when.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – The standard Oracle EBS descriptive flexfield (DFF) columns, providing extensibility for customer-specific goal attributes without schema changes.

The distinction between the surrogate key (BUILD_GOAL_ID) and the business-key candidate (VISIT_ID, UOM_CODE) is important for data integration and de-duplication logic.

Common Use Cases and Queries

Typical usage centers on retrieving and reporting the goals defined for a given visit or across a set of visits. A common query joins build goals to visits to present measurable targets:

  • List all goals for a visit: SELECT BUILD_GOAL_ID, UOM_CODE, COUNTER_VALUE FROM AHL_BUILD_GOALS WHERE VISIT_ID = :visit_id;
  • Aggregate counter values per unit of measure across visits: SELECT UOM_CODE, SUM(COUNTER_VALUE) FROM AHL_BUILD_GOALS GROUP BY UOM_CODE;
  • Security-scoped reporting: ... WHERE SECURITY_GROUP_ID = :sgid to respect organizational partitioning.
  • Audit and change tracking using LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • DFF-based filtering using ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for customer-defined goal classifications.

Because the table is standalone in the FK graph, reporting is generally driven outward from AHL_VISITS_B rather than from AHL_BUILD_GOALS as a parent.

Related Objects

  • AHL_VISITS_B – Referenced by AHL_BUILD_GOALS.VISIT_ID. The principal parent and the usual entry point for goal reporting.
  • FND_SECURITY_GROUPS – Referenced by AHL_BUILD_GOALS.SECURITY_GROUP_ID. Governs access partitioning.
  • AHL_VISITS_TL – The translation table for visits, useful when displaying visit descriptions alongside goals.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS – Commonly joined to resolve DFF and UOM_CODE values.
  • Standard EBS audit views – Such as the _VL views and WHO columns consumers, used in concurrent programs and BI Publisher reports.

These relationships, together with the unique indexes AHL_BUILD_GOALS_U1 and AHL_BUILD_GOALS_U2, define the primary integration and reporting paths for the object.