Results for “before_after”

50+ results




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

Overview

OKC_BUS_DOC_EVENTS_V is a valid, Oracle-owned view in the APPS schema delivered with the OKC – Contracts Core product. It presents a single, translation-aware projection of business document events used throughout Oracle Contracts and related modules. The view joins the base event table OKC_BUS_DOC_EVENTS_B with its translation table OKC_BUS_DOC_EVENTS_TL, so callers receive the internal event attributes alongside the language-specific event name (MEANING exposed as EVENT_NAME) resolved through USERENV('LANG'). In EBS 12.1.1 and 12.2.2 reporting and integration scenarios, the view functions as the canonical read interface for lookup-style business document event definitions, shielding callers from the multilingual table split and from direct access to the _B/_TL pair. Its inclusion of ROW_ID, OBJECT_VERSION_NUMBER, and the standard WHO audit columns also makes it usable where row identity and concurrency information are required.

Underlying Base Objects

The view is defined over two documented synonyms: OKC_BUS_DOC_EVENTS_B, which holds the language-independent event definition, and OKC_BUS_DOC_EVENTS_TL, which holds the translated event name. The join predicate is DEVB.BUS_DOC_EVENT_ID = DEVT.BUS_DOC_EVENT_ID, restricted by DEVT.LANGUAGE = USERENV('LANG'). This construction follows the standard EBS MLS pattern: the _B table supplies the business key, the business event code, the document-type and timing qualifiers, and audit information; the _TL table supplies the user-facing MEANING. Because the language predicate is evaluated against the session language, each query returns exactly one translated row per BUS_DOC_EVENT_ID, providing deterministic, language-neutral selection behavior regardless of the reporting environment.

Key Columns

  • ROW_ID — the physical row identifier of the base _B row, exposed for updatable or identity-based access.
  • BUS_DOC_EVENT_ID — the primary business key linking the base and translation rows; this is the column returned by the internal search term bus_doc_type context, since it identifies the event record to which a document type applies.
  • BUSINESS_EVENT_CODE — the internal code for the business event raised or recognized by the contract.
  • BUS_DOC_TYPE — the business document type associated with the event; this is the column most frequently filtered in queries that resolve which events apply to a given document type.
  • BEFORE_AFTER — the timing qualifier indicating whether the event applies before or after the document action.
  • START_END_QUALIFIER — the qualifier distinguishing start versus end events.
  • EVENT_NAME — the translated event meaning sourced from _TL, suitable for display and reporting.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — the standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical uses include resolving which events apply to a document type, building reporting extracts of event definitions, and validating event codes during integrations. To retrieve all events for a given document type:

SELECT BUS_DOC_EVENT_ID, BUSINESS_EVENT_CODE, BUS_DOC_TYPE, BEFORE_AFTER, START_END_QUALIFIER, EVENT_NAME
FROM APPS.OKC_BUS_DOC_EVENTS_V
WHERE BUS_DOC_TYPE = :p_bus_doc_type
ORDER BY BUSINESS_EVENT_CODE;

To look up the translated name of a single event by its business key:

SELECT EVENT_NAME, BUSINESS_EVENT_CODE, BUS_DOC_TYPE
FROM APPS.OKC_BUS_DOC_EVENTS_V
WHERE BUS_DOC_EVENT_ID = :p_event_id;

Because the language predicate is embedded in the view, no additional language filter is required. Integrations should treat the view as read-only, rely on OBJECT_VERSION_NUMBER for concurrency checks where relevant, and avoid joining to the _TL table directly to prevent duplicate or missing translation rows.