Results for “wf_error_processes_s”

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

Overview

The APPS.ECX_RULE package is a core component of the Oracle E-Business Suite Procurement and Trading Partner integration infrastructure, forming part of the E-Commerce Gateway (ECX) and E-Business Transaction Management (ETRM) stack. Its principal business function is to evaluate and apply trading rules that govern how business documents and messages flow between the EBS instance and external trading partners. In essence, the package encapsulates the conditional logic that determines whether an inbound or outbound transaction should be processed, transformed, or discarded based on the configuration held in the ECX trading partner and standard tables.

The package is classified as OTHER in the ETRM metadata, indicating that it is an internal application programming interface rather than a formally published public API. Its status is VALID, and it resides in the APPS schema, which is consistent with its role as a shared integration utility invoked from multiple points in the ECX processing pipeline.

Key Procedures and Functions

The documented interface exposes seven procedures and functions:

• OUTBOUND_RULE — Evaluates outbound processing rules for a trading message, determining whether an outgoing document qualifies for transmission under the configured partner rules.
• INBOUND_RULE — Applies the original inbound rule evaluation logic to a received message, deciding whether the message proceeds through the inbound processing chain.
• INBOUND_RULE2 — A later variant of the inbound rule procedure, retained alongside the original to support revised or enhanced inbound evaluation behaviour.
• RECEIVETPMESSAGE — Handles receipt of a trading partner message, forming the entry point for inbound message intake.
• CREATETPMESSAGE — Constructs a trading partner message object, typically as part of outbound message assembly.
• ISTPENABLED — A function returning whether a given trading partner is enabled, used as a gating check before further processing.
• TPPREPROCESSING — Performs pre-processing steps on trading partner data prior to the main rule evaluation.

Tables Accessed

The package reads and writes a wide set of ECX and Workflow tables through APPS synonyms:

• ECX_TP_HEADERS, ECX_TP_DETAILS — Trading partner header and detail definitions, the primary source for partner configuration and enablement.
• ECX_STANDARDS, ECX_EXT_PROCESSES — Define document standards and external processing parameters used in rule evaluation.
• ECX_INBOUND_LOGS, ECX_INLSTN_S, ECX_TRIGGER_ID_S — Inbound logging and sequence generation for tracking received messages.
• WF_EVENT_T, WF_AGENT_T, WF_EVENT_SUBSCRIPTIONS, WF_PARAMETER_LIST_T, WF_ERROR_PROCESSES_S — Oracle Workflow event and agent structures used to raise, subscribe to, and route business events.
• DBMS_AQ, DBMS_LOB, DUAL — Advanced Queuing enqueue/dequeue, large object handling for message payloads, and singleton queries.

Usage Notes

ECX_RULE is not intended for direct invocation by end users. It is called internally by ECX inbound and outbound concurrent programs, by the ECX Gateway processing engine, and by the ECX_TRADING_PARTNER_PVT package, which references it. Because the package depends on WF_EVENT_T and the Workflow event tables, it participates in the EBS Business Event System, meaning rule decisions may trigger workflow subscriptions. Customisations should avoid modifying the package body directly; instead, extensions should be layered through supported ECX configuration. Any custom code invoking these procedures must respect the APPS schema privileges and the underlying Workflow and Advanced Queuing dependencies.