Results for “oe_processing_msgs_vl”

50+ results




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

Overview

OE_PROCESSING_MSGS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the ONT – Order Management product family and is defined over OE_PROCESSING_MSGS and its translation table OE_PROCESSING_MSGS_TL. The view exists to de-normalize processing message data so that language-dependent text is resolved at query time, eliminating the multilingual ambiguity that arises when base tables store translatable attributes separately from their translated values.

OE_PROCESSING_MSGS records asynchronous order-processing events such as order import, order capture, and concurrent-program activity. Because these records reference many foreign entities — orders, lines, transaction types, concurrent programs, users, and workflow activities — the VL view enriches each message row with descriptive names resolved from the corresponding master and translation tables. This makes the view suitable for reporting, troubleshooting, and integration diagnostics without requiring the caller to hand-join numerous lookup objects.

Underlying Base Objects

The documented base objects underlying the view include OE_PROCESSING_MSGS and OE_PROCESSING_MSGS_TL, OE_ORDER_HEADERS, OE_ORDER_LINES, OE_TRANSACTION_TYPES_TL, OE_SOLD_TO_ORGS_V, FND_CONCURRENT_PROGRAMS_TL, FND_CONCURRENT_REQUESTS, FND_USER, WF_PROCESS_ACTIVITIES, and WF_ACTIVITIES_TL. All are referenced as synonyms or views within APPS. Notably, WF_ACTIVITIES_TL — the object associated with the search term "wf_activities_tl" — is joined here to produce the human-readable activity display name.

The joins are predominantly outer joins. Header, line, transaction type, concurrent program, request, user, sold-to organization, and workflow activity lookups are all marked with the (+) operator, ensuring that a processing message row is still returned even when the related reference data is missing or purged. The MESSAGE_TEXT column is resolved with NVL(MSG.MESSAGE_TEXT, MT.MESSAGE_TEXT), preferring the base message text and falling back to the translated value.

Key Columns

Common Use Cases and Queries

The view is typically queried to diagnose order import failures, review processing notifications, and report on concurrent request activity in a specific operating unit. A basic query filtering by order and operating unit is shown below.

  • SELECT order_number, line_number, message_text, message_status_code FROM oe_processing_msgs_vl WHERE org_id = :p_org_id AND order_number = :p_order_number;
  • SELECT request_id, message_text, user_name, creation_date FROM oe_processing_msgs_vl WHERE message_status_code = 'ERROR' ORDER BY creation_date DESC;
  • SELECT process_activity, display_name, COUNT(*) FROM oe_processing_msgs_vl GROUP BY process_activity, display_name;

Because the view resolves translated names for transaction types, concurrent programs, and workflow activities, it is also useful for building multilingual reports and for troubleshooting messages whose PROCESS_ACTIVITY references a workflow activity whose display name is stored in WF_ACTIVITIES_TL. Queries should filter on ORG_ID where multi-org data is present to preserve performance and correctness.