Results for “invoice_to”

50+ results




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

Overview

OE_BLANKET_HDRS_HIST_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Management (ONT) product family. It exposes historical blanket sales agreement header information, complementing the operational OE_BLANKET_HEADERS_B and OE_BLANKET_HEADERS_TL tables by providing a denormalized, query-ready projection of blanket header data. The "HIST" suffix and its base object OE_BLANKET_HEADERS_HIST indicate that the view surfaces versioned history records for blanket agreements, which is significant because blanket sales agreements in Oracle Order Management support version control: each amendment produces a new version row, and prior versions remain accessible. This view therefore allows reporting on the full historical evolution of blanket headers rather than only the current active version.

In the 12.1.1 and 12.2.2 releases, the view is registered as VALID and is commonly referenced by custom reports, concurrent program extracts and integration interfaces that must reconcile or audit blanket agreement data over time. It is not an interface table and does not support DML; it is a read-only construct intended for queries and downstream extraction, including XML-based outbound integrations where header attributes are assembled for external systems.

Underlying Base Objects

The view is documented in ETRM 12.2.2 as being defined over the synonym OE_BLANKET_HEADERS_HIST, which holds the versioned history rows, joined to a broad set of reference and master data objects. The documented base objects include HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES and HZ_RELATIONSHIPS for customer, site and contact resolution; MTL_PARAMETERS for inventory organization context; OE_TRANSACTION_TYPES_TL for the order type description; OE_LOOKUPS and AR_LOOKUPS for code validation and meaning; FND_CURRENCIES for currency context; QP_LIST_HEADERS_TL for the price list; RA_RULES for accounting rules; RA_TERMS_TL for payment terms; and RA_SALESREPS for sales representative data. This join structure explains why the view presents descriptive values (names, meanings, descriptions) alongside the raw identifiers stored in OE_BLANKET_HEADERS_HIST, making it suitable for direct reporting without additional lookup joins.

Key Columns

Common Use Cases and Queries

Typical uses include auditing blanket agreement amendments, extracting version histories for data warehousing, and populating integration payloads. A common query retrieves all versions of a given blanket agreement:

SELECT header_id, order_number, version_number, expiration_date, transactional_curr_code, agreement_id
FROM   apps.oe_blanket_hdrs_hist_v
WHERE  order_number = :p_order_number
ORDER  BY version_number;

To track recent changes for a specific operating unit:

SELECT order_number, version_number, last_update_date, last_updated_by
FROM   apps.oe_blanket_hdrs_hist_v
WHERE  org_id = :p_org_id
AND    last_update_date >= :p_since_date;

When reconciling XML-based inbound flows, the PROGRAM_ID and REQUEST_ID columns can be filtered to isolate records created by a specific concurrent request, allowing correlation of blanket header history with the XML message processing that generated it. Users searching on "xml_message_id" should note that this view does not expose a dedicated XML_MESSAGE_ID column; message correlation is instead inferred through the audit columns and the originating concurrent program and request identifiers.