Search Results dpp_inventory_details_all




Overview
Explore in AI Chat

Overview

DPP.DPP_INVENTORY_DETAILS_ALL is a transactional table within the Oracle Price Protection (DPP) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to store the covered inventory breakup by warehouse details for all products appearing on a price protection transaction. In practice, this means the table captures, line by line, which inventory quantities at which inventory organizations are eligible for price protection coverage under a given transaction, and it records how each of those inventory rows was qualified — for example, whether it was included automatically by the application or added manually by a user.

The table resides in the DPP schema, is owned by the Oracle Price Protection product, and has a documented physical schema comprising 48 columns. Its primary key is enforced through DPP_INVENTORY_DETAILS_ALL_PK on INVENTORY_DETAILS_ID, with a unique index DPP_INVENTORY_DETAILS_ALL_U1 also defined on that same column. From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone; as a modeling suggestion, given that it carries a surrogate key, a foreign key to the transaction line, descriptive attributes, and audit columns, it behaves most naturally as a satellite or detail entity whose driving context is the transaction line rather than as an independent hub in its own right.

Key Information Stored

The most operationally significant columns are the following:

  • INVENTORY_DETAILS_ID — the surrogate primary key and the unique business-key candidate for this row. Child tables reference the parent through this column.
  • TRANSACTION_LINE_ID — the transaction line to which the inventory breakup belongs; this is the principal join back to the price protection transaction structure.
  • INVENTORY_ITEM_ID — the inventory item being covered.
  • ORG_ID and ORGANIZATION_ID — the operating unit and the inventory organization (warehouse) in which the covered quantity resides; these two columns provide the warehouse breakup referenced in the table description.
  • QUANTITY and UOM — the covered quantity and its unit of measure.
  • INCLUDE_FLAG — indicates whether the inventory row is included in the covered inventory set.
  • MANUALLY_ADDED — distinguishes inventory rows entered manually by a user from those derived by the application.
  • COMMENTS — free-text annotation attached to the inventory line.
  • PROGRAM_ID and the standard WHO columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — providing concurrency control and auditability.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the descriptive flexfield storage typically used to capture customer-specific extensions on the covered inventory row.

Common Use Cases and Queries

Typical reporting queries join the inventory breakup back to the transaction line to report covered quantity by warehouse or by item, or to flag lines that were manually added versus automatically qualified. A representative pattern is:

  • Covered inventory by warehouse: SELECT ORGANIZATION_ID, INVENTORY_ITEM_ID, SUM(QUANTITY) FROM DPP.DPP_INVENTORY_DETAILS_ALL WHERE TRANSACTION_LINE_ID = :line_id GROUP BY ORGANIZATION_ID, INVENTORY_ITEM_ID;
  • Manual versus system-qualified rows: SELECT MANUALLY_ADDED, INCLUDE_FLAG, COUNT(*) FROM DPP.DPP_INVENTORY_DETAILS_ALL GROUP BY MANUALLY_ADDED, INCLUDE_FLAG;
  • Adjustment lookup: joining to DPP_INVENTORY_DETAILS_ADJ_ALL on INVENTORY_DETAILS_ID to determine which covered inventory rows were subsequently adjusted.

Because the table carries ORG_ID, queries must respect operating unit security to return the correct subset for a given responsibility.

Related Objects

The most significant relationships documented for this object are:

  • DPP.DPP_INVENTORY_DETAILS_ADJ_ALL — the primary dependent table; it references the parent via INVENTORY_DETAILS_ID and stores adjustments applied to the covered inventory breakup.
  • DPP_INVENTORY_DETAILS_ALL_PK and DPP_INVENTORY_DETAILS_ALL_U1 — the primary key constraint and unique index, both defined on INVENTORY_DETAILS_ID.
  • The DPP transaction line entity referenced by TRANSACTION_LINE_ID, which supplies the parent context for each covered inventory record.
  • Inventory item and organization reference data resolved through INVENTORY_ITEM_ID, ORGANIZATION_ID, and ORG_ID.

Because the table is classified as standalone in the mined relationship data, integration and extension work should rely on the documented INVENTORY_DETAILS_ID linkage to the adjustment table rather than on assumptions of additional foreign key dependencies.