Search Results okc_ph_line_breaks_hv

Overview

The OKC_PH_LINE_BREAKS_HV view is a dictionary-defined object owned by the APPS schema within the Oracle E-Business Suite Contracts Core (OKC) module. It is a thin, passthrough view constructed as a simple projection over the base table OKC_PH_LINE_BREAKS_H, exposing every column of that table without joins, filters, aggregations, or transformations. The ETRM (E-Business Suite Technical Reference Manual) metadata explicitly designates this view with the descriptor "Not Used," indicating that it is a legacy or vestigial object retained in the schema but no longer referenced by delivered application code, concurrent programs, or standard product flows.

Despite its dormant status, the view remains relevant for reporting and integration scenarios because it inherits the full attribute set of the underlying line-break history table. Line breaks in OKC represent pricing interval definitions — the threshold values (VALUE_FROM, VALUE_TO) and associated pricing types that determine how contract line pricing is calculated across graduated ranges. The _HV suffix conventionally denotes a history/version view in EBS naming standards, and the presence of MAJOR_VERSION confirms that the view surfaces version-aware data rather than a single current row per business key.

Underlying Base Objects

The view is defined over exactly one referenced object: the synonym OKC_PH_LINE_BREAKS_H, which resolves to the physical table in the APPS schema. The view text selects from OKC_PH_LINE_BREAKS_H PHLBH using column aliases that match the base column names one-for-one. No WHERE clause, DISTINCT, UNION, or outer join is present. Consequently, the view provides no row-level security, organizational filtering, or translation logic beyond what exists on the table itself.

Because the view is a direct projection, its execution plan collapses to a full table scan or index access against the base table, and DML against the view is theoretically possible if it were treated as a key-preserved updatable join view — though in practice it is queried read-only. The view's ETRM status is VALID, confirming that it compiles cleanly against the current table definition in 12.1.1 and 12.2.2.

Key Columns

• ID / MAJOR_VERSION — Primary identifier and version number for the line-break history record; MAJOR_VERSION distinguishes successive revisions.
• CLE_ID — Foreign key to the contract line or pricing entity to which the break applies.
• VALUE_FROM / VALUE_TO — Lower and upper bounds of the pricing interval.
• PRICING_TYPE / VALUE — The pricing method and the rate, amount, or factor applied within the interval.
• START_DATE / END_DATE — Effective dating for the line break.
• SHIP_TO_ORGANIZATION_ID — The ship-to organization (inventory organization) associated with the break; this is the column users most commonly search for, as it enables organization-specific pricing break analysis.
• SHIP_TO_LOCATION_ID — The ship-to site address identifier corresponding to the organization.
• INTEGRATED_WITH_QP / QP_REFERENCE_ID — Flags and references linking the break to Oracle Advanced Pricing (QP) integration.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM framework.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID for audit and concurrent program tracking.

Common Use Cases and Queries

The primary practical use is ad hoc reporting on pricing break history segmented by ship-to organization or location, often to reconcile contract pricing against Advanced Pricing setups.

• List all breaks for a contract line: SELECT * FROM OKC_PH_LINE_BREAKS_HV WHERE cle_id = :cle_id ORDER BY major_version, value_from;
• Filter by ship-to organization: SELECT id, cle_id, value_from, value_to, value FROM OKC_PH_LINE_BREAKS_HV WHERE ship_to_organization_id = :org_id;
• Audit recent changes: SELECT id, last_updated_by, last_update_date FROM OKC_PH_LINE_BREAKS_HV WHERE last_update_date > SYSDATE - 7;
• Identify QP-integrated breaks: SELECT * FROM OKC_PH_LINE_BREAKS_HV WHERE integrated_with_qp = 'Y';

Because the metadata labels the view "Not Used," developers should treat it as a read-only convenience wrapper and, where feasible, query the base table directly to avoid dependency on an undocumented legacy object.