Search Results ahl_req_supply_schedule

Overview

The AHL_REQ_SUPPLY_SCHEDULE table is a core planning and scheduling object within the Oracle E-Business Suite (EBS) Complex Maintenance Repair and Overhaul (AHL) module. It stores the time-phased supply schedule for materials and components required against maintenance and overhaul demands. In the 12.1.1 / 12.2.2 release stream, this table serves as the staging and storage layer for requisition supply date lines — capturing when a given quantity of an inventory item is expected to be available within a specific organization, keyed by the requested date. It bridges the gap between maintenance execution planning and the supply chain execution engine, feeding MRP/ASCP planning runs and supporting the scheduling of parts to overhaul work orders.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is modeled as a satellite (referred to here as standalone in the metadata). It depends on a parent business key from the inventory/organization domain and attaches descriptive, time-stamped supply attributes. The single documented foreign key — SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS — is a Multi-Org / data-security construct rather than a functional parent, which reinforces the satellite classification: the row's identity flows from its business key (item, organization, date), not from a foreign-key parent relationship.

Key Information Stored

The table comprises 30 documented columns. The most business-critical are:

• INVENTORY_ITEM_ID, ORGANIZATION_ID, REQUESTED_DATE — the composite business-key candidates. Together they form the unique index AHL_REQ_SUPPLY_SCHEDULE_U1, which is the principal uniqueness constraint for the object.
• QUANTITY and UOM_CODE — the scheduled supply amount and its unit of measure of record.
• ASCP_PLAN_DATE — the date supplied to the Advanced Supply Chain Planning engine, allowing the schedule to align with ASCP planning buckets independently of the requested date.
• SOURCE_APPLICATION — identifies the originating application that published the schedule line, enabling multi-source traceability.
• SECURITY_GROUP_ID — the sole documented foreign key, pointing to FND_SECURITY_GROUPS, enforcing row-level security across operating units.
• OBJECT_VERSION_NUMBER — optimistic locking column for the Oracle Application Framework (OAF) / ADF concurrency model.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns for audit and change tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) block, allowing customer-specific extensions without schema change.

No surrogate primary-key column is documented in the metadata; identity therefore rests on the three-column unique business key, consistent with the satellite classification.

Common Use Cases and Queries

Typical usage includes shortage reporting, supply-versus-demand pegging, and ASCP feed validation. A reporting query for open supply against an item and organization might be:

• SELECT inventory_item_id, organization_id, requested_date, quantity, uom_code, ascp_plan_date FROM ahl.ahl_req_supply_schedule WHERE organization_id = :org AND requested_date BETWEEN :from AND :to ORDER BY requested_date;
• Join to FND_SECURITY_GROUPS on security_group_id to constrain rows to the caller's secured organizations.
• Aggregate by ascp_plan_date to produce time-bucketed supply projections for the planning engine.
• Query source_application to determine which upstream system published a schedule line during reconciliation.
• Filter on object_version_number and the who-columns for change-audit extracts.

Related Objects

The most significant related objects include:

• FND_SECURITY_GROUPS — referenced via AHL_REQ_SUPPLY_SCHEDULE.SECURITY_GROUP_ID; the only documented foreign key and the anchor for data-security filtering.
• MTL_SYSTEM_ITEMS_B — source of INVENTORY_ITEM_ID validation and item description.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — source of ORGANIZATION_ID context.
• MTL_UNITS_OF_MEASURE — resolves UOM_CODE.
• AHL work order / maintenance demand tables — the planning side that consumes these supply schedule rows.
• Standard EBS audit entities FND_USER and FND_LOGINS — referenced through the who-columns.