Results for “oebv_results”

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

Overview

The view OEBV_RESULTS is an Order Entry (OE) reporting object in Oracle E-Business Suite. Its ETRM title is "View: OEBV_RESULTS," it is registered against the OE - Order Entry product, and its description is recorded simply as "- Retrofitted." This is a notable attribute: the "Retrofitted" designation indicates that the object was introduced or regenerated to preserve backward compatibility, typically during the transition from earlier EBS releases into the 12.1.1 and 12.2.2 code lines, rather than being an original native object of those releases.

Functionally, the view presents a minimally exposed projection of result records — the identifiers and descriptive attributes stored against results — together with the standard Oracle EBS "Who" audit columns (creation and last-update metadata). Because the view is defined with a read-only constraint, it is intended strictly for query access, not for DML. It therefore belongs to the class of OE objects surfaced for reporting, ad hoc inquiry, and integration lookups where a consumer needs result names and descriptions without navigating the base table directly.

One documented caveat is significant for implementers: the ETRM metadata records the view as "Not implemented in this database." In other words, the object is documented in the reference material but is not necessarily deployed in every environment. Its presence depends on the specific patch level and configuration of the instance.

Underlying Base Objects

The view text documented in the ETRM metadata is unambiguous:

• SELECT RESULT_ID, NAME, DESCRIPTION, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY FROM SO_RESULTS WITH READ ONLY

Accordingly, the single referenced base object is SO_RESULTS, the Order Management results table. The ETRM entry lists no additional referenced base objects, and the owner is not documented. The WITH READ ONLY clause appended to the defining query enforces that no insert, update, or delete can be issued through the view; the optimizer treats it purely as a query surface.

Structurally, the relationship between OEBV_RESULTS and SO_RESULTS is a straightforward one-to-one column mapping. The view adds no joins, no filters, no aggregation, and no derived expressions — it is a compatibility projection. Any row returned by the view corresponds to exactly one row in SO_RESULTS, and the view exposes only seven of that table's columns.

Key Columns

• RESULT_ID — Primary identifier for the result record. This is the join key used by any consumer linking results to other Order Management entities.
• NAME — The short name of the result, used as the display label in inquiry screens and reports.
• DESCRIPTION — Free-text description providing the fuller meaning of the result.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
• LAST_UPDATED_BY — The application user who performed the most recent modification.
• CREATION_DATE — Timestamp when the row was originally created.
• CREATED_BY — The application user who created the row.

The four audit columns follow Oracle EBS standard naming and semantics and are commonly used for incremental extraction and change tracking. The absence of a RESULT_CODE, effective-date range, or enabled flag in the view means that validation or lookup-style attributes must be obtained elsewhere if required.

Common Use Cases and Queries

The view is typically used as a lightweight lookup for result names and descriptions in reports, concurrent programs, and integration extracts. A basic retrieval is:

• SELECT result_id, name, description FROM oebv_results ORDER BY name;
• SELECT result_id, name FROM oebv_results WHERE name LIKE :p_name;
• Incremental extraction by audit stamp: SELECT * FROM oebv_results WHERE last_update_date >= :p_since;
• Joining to a base-table reference by identifier: SELECT r.name, r.description FROM oebv_results r WHERE r.result_id = :p_result_id;

Before relying on the view, verify that it is actually deployed, given the "Not implemented in this database" notation in the metadata. Where it is absent, the equivalent query can be issued directly against SO_RESULTS using the same seven columns. This pattern — documenting a retrofitted compatibility view that may or may not be instantiated — is the principal point of caution for the 12.1.1 and 12.2.2 environments.