Search Results ahl_req_supply_schedule_u1




Overview
Explore in AI Chat

Overview

The AHL.AHL_REQ_SUPPLY_SCHEDULE table is a transactional data store within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the AHL (Advanced Supply Chain Planning – Discrete Manufacturing) schema. Its documented purpose is to store requested supply data that is requested from Oracle Advanced Supply Chain Planning (ASCP). In other words, it acts as a staging or interface table that captures the supply quantities a downstream or upstream planning process has requested for a given item and organization on a particular date, along with the planning date returned or confirmed by ASCP.

From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning it has no documented foreign-key parents other than the SECURITY_GROUP_ID reference to FND_SECURITY_GROUPS. A reasonable modeling suggestion would be to treat the composite of INVENTORY_ITEM_ID, ORGANIZATION_ID, and REQUESTED_DATE as a business key hub (or a link combining item, organization, and date dimensions), with QUANTITY, UOM_CODE, and ASCP_PLAN_DATE behaving as satellite-style descriptive attributes that can change over time. Because the table also carries standard WHO columns and an OBJECT_VERSION_NUMBER, it supports optimistic locking and audit tracking consistent with Oracle Application Object Library conventions.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are listed below:

  • INVENTORY_ITEM_ID – Identifies the inventory item; part of the unique business key.
  • ORGANIZATION_ID – Identifies the inventory organization; part of the unique business key.
  • REQUESTED_DATE – The date for which supply was requested; completes the unique business key.
  • QUANTITY – The requested supply quantity for the item/organization/date combination.
  • UOM_CODE – Unit of measure for the requested quantity.
  • ASCP_PLAN_DATE – The planned date returned by ASCP, which may differ from the requested date.
  • SOURCE_APPLICATION – Short code identifying the application that originated the request.
  • SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS; controls data visibility by security group.
  • OBJECT_VERSION_NUMBER – Version number used for optimistic locking during updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – Descriptive flexfield (DFF) columns for customer-specific extension.

The unique key is enforced by the index AHL_REQ_SUPPLY_SCHEDULE_U1 on (INVENTORY_ITEM_ID, ORGANIZATION_ID, REQUESTED_DATE), which is the exact index name the user searched for. A secondary non-unique index, AHL_REQ_SUPPLY_SCHEDULE_N1, exists on (ORGANIZATION_ID, REQUESTED_DATE) to support range and date-filtered queries by organization.

Common Use Cases and Queries

The primary use case is to reconcile or inspect what supply quantities have been requested from ASCP against what ASCP has actually planned. A typical query retrieves the requested versus planned dates and quantities for a given item and organization:

  • Reporting on requested supply by organization and date range, leveraging the N1 index.
  • Comparing REQUESTED_DATE to ASCP_PLAN_DATE to identify slippage or planning discrepancies.
  • Filtering by SOURCE_APPLICATION to isolate requests originating from a specific module.
  • Joining to master item and organization tables to present descriptive names instead of surrogate IDs.

A representative SQL pattern follows the documented query text:

  • SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, REQUESTED_DATE, QUANTITY, UOM_CODE, ASCP_PLAN_DATE, SOURCE_APPLICATION FROM AHL.AHL_REQ_SUPPLY_SCHEDULE WHERE ORGANIZATION_ID = :org AND REQUESTED_DATE BETWEEN :from_date AND :to_date;

Related Objects

Because the metadata classifies this object as standalone, it has limited direct foreign-key relationships. The most significant related objects are:

  • FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID; governs row-level security.
  • MTL_SYSTEM_ITEMS_B – Master item definition, joined on INVENTORY_ITEM_ID.
  • MTL_PARAMETERS / HR_OPERATING_UNITS – Organization context, joined on ORGANIZATION_ID.
  • ASCP planning tables (e.g., MSC_* interface tables) – The ASCP feed that populates or consumes the requested supply rows.
  • FND_APPLICATION – Resolves SOURCE_APPLICATION short codes to application names.
  • FND_DESCRIPTIVE_FLEXS / FND_FLEX_VALUES – Underpin the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 columns.

These join paths reflect both the documented FK to FND_SECURITY_GROUPS and standard EBS master-data relationships implied by the item and organization identifiers.