Results for “source_tp_location_code”

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

Overview

The ECX_IN_PROCESS_VL view is a reporting and monitoring construct within the ECX – XML Gateway product of Oracle E-Business Suite. It exposes the status of inbound messages processed by the XML Gateway, providing a consolidated, query-friendly presentation of transactional documents received from trading partners. The view is owned by the APPS schema and is documented as VALID in the ETRM repository for both EBS 12.1.1 and 12.2.2. The "_VL" suffix conventionally denotes a "view language" object that presents descriptive, business-readable interpretations of underlying transactional data.

Its principal role is to allow integration administrators and support analysts to inspect the lifecycle of inbound XML messages — from receipt through processing — without having to join the numerous low-level ECX configuration and logging tables directly. Because XML Gateway requires the correlation of message logs, trading partner setup, standard type definitions, and error message text, the view encapsulates that join logic and returns a single denormalized result set keyed by the inbound trigger. This makes it well suited to operational reporting, exception monitoring, and reconciliation of inbound message flows.

Underlying Base Objects

The view is defined over several documented base objects, all referenced as synonyms resolving to their underlying ECX tables:

• ECX_DOCLOGS — the driving table holding the document header information for inbound messages, including document number, transaction type and subtype, message standard, party type, and the message IDs.
• ECX_INBOUND_LOGS — holds the per-attempt inbound processing record, including trigger ID, processing status, timestamp, logfile path, and any associated error ID.
• ECX_ERROR_MSGS — supplies error message text and parameters, translated at query time through the ECX_DEBUG.GETMESSAGE function.
• ECX_EXT_PROCESSES, ECX_STANDARDS, ECX_TP_DETAILS, and ECX_TP_HEADERS — these four tables are joined in an inline view (aliased TPSETUP) to resolve trading partner setup for processes whose direction is 'IN'.
• ECX_DEBUG — a package supplying the GETMESSAGE function used to render human-readable processing messages.

The joins between ECX_DOCLOGS and the TPSETUP inline view are outer joins on transaction type/subtype, party site, message type, and message standard, ensuring that inbound documents remain visible even when no matching trading partner configuration row exists.

Key Columns

• TRIGGER_ID — unique identifier for the inbound processing event.
• DOCUMENT_ID — reference to the inbound document record.
• TRANSACTION_TYPE / TRANSACTION_SUBTYPE — the categorization of the inbound business document.
• PARTY_ID / PARTY_SITE_ID / PARTY_TYPE — the trading partner and site from whom the message was received.
• INTERNAL_CONTROL_NUMBER — control reference for the interchange.
• PROCESSING_STATUS — the outcome state of the inbound processing attempt.
• PROCESSING_MESSAGE — the resolved error or informational message text.
• PROCESSING_TIMESTAMP / PROCESSING_LOGFILE — when processing occurred and the associated log file location.
• OUT_MSGID / MSGID — internal and outgoing message identifiers used for correlation.

Common Use Cases and Queries

Typical usage centers on monitoring inbound message health and diagnosing failures. A straightforward query to list recent inbound messages and their status is:

• SELECT trigger_id, document_id, transaction_type, processing_status, processing_message, processing_timestamp FROM apps.ecx_in_process_vl ORDER BY processing_timestamp DESC;
• SELECT trigger_id, party_id, transaction_type, processing_message FROM apps.ecx_in_process_vl WHERE processing_status = 'ERROR';

Analysts also use the view to correlate a specific trading partner's inbound activity or to trace a document by its MSGID or internal control number. Because the view resolves error text through ECX_DEBUG.GETMESSAGE, its output is directly suitable for support tickets and integration dashboards without additional decoding.