Search Results oe_blanket_lines_hist




Overview
Explore in AI Chat

Overview

The OE_BLANKET_LINES_HIST table is a core data object within the Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically for releases 12.1.1 and 12.2.2. Its primary function is to serve as a historical audit trail for sales agreement lines. Sales agreements, also known as blanket sales agreements, are long-term contracts that define pricing, terms, and conditions for future transactions. When a line on such an agreement is modified, this table captures a historical snapshot of the line's state prior to the change. This is critical for maintaining a complete audit history, enabling compliance reporting, trend analysis, and troubleshooting of order fulfillment against contractual terms over time.

Key Information Stored

While the provided ETRM metadata does not list specific columns beyond foreign keys, the table's purpose and relationships indicate it stores a denormalized historical record of a blanket line. Key data typically includes the line's header and line identifiers (likely linking to OE_BLANKET_HEADERS and OE_BLANKET_LINES), the item, pricing, quantities, dates, and shipping information at the point of change. Crucially, it stores contact role identifiers, as evidenced by its foreign key relationships. These columns—SHIP_TO_CONTACT_ID, INTMED_SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, and DELIVER_TO_CONTACT_ID—capture the specific contacts associated with various roles on the agreement line at that historical moment, which is vital for auditing changes to fulfillment and billing instructions.

Common Use Cases and Queries

The primary use case is auditing and reporting on changes to sales agreement lines. This supports business processes such as analyzing pricing history, verifying contract terms at a past date, and investigating discrepancies. A common query pattern involves joining to the main transaction tables to compare current and historical states.

  • Audit Trail for a Specific Agreement Line: Querying OE_BLANKET_LINES_HIST for a given BLANKET_LINE_ID, ordered by a change date or version column, to see its evolution.
  • Reporting on Contact Changes: Identifying when and how shipping or billing contacts were modified on an agreement by joining OE_BLANKET_LINES_HIST to HZ_CUST_ACCOUNT_ROLES on the contact ID columns.
  • Historical Snapshot Reporting: Reconstructing the state of an entire agreement as of a specific date by selecting the most recent historical record for each line prior to that date.

Related Objects

The OE_BLANKET_LINES_HIST table has defined foreign key relationships with other EBS tables, ensuring referential integrity for the contact data it stores. As per the documented metadata, it references the following object:

  • HZ_CUST_ACCOUNT_ROLES: This table from the Trading Community Architecture (TCA) module stores customer contact role assignments. OE_BLANKET_LINES_HIST joins to it via four key columns to validate and describe the contact information:
    • SHIP_TO_CONTACT_ID
    • INTMED_SHIP_TO_CONTACT_ID (Intermediate Ship-To Contact)
    • INVOICE_TO_CONTACT_ID
    • DELIVER_TO_CONTACT_ID

Logically, this history table is a child of the primary transaction table OE_BLANKET_LINES, from which the historical snapshots are derived, though this specific PK-FK relationship is not detailed in the provided excerpt.