Results for “xml_mapcode”

2 results




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

Overview

The view APPS.EDR_WFEVENT_XMLMAP_V is a dictionary-enabled reporting object within the EDR – E-Records product family of Oracle E-Business Suite. Its documented purpose is to expose an X-reference, or cross-reference, between the event name of an E-Records (ERES) event and the corresponding XML Gateway map code associated with that event. In Oracle EBS 12.1.1 and 12.2.2, XML Gateway is the messaging infrastructure that transforms business events into XML payloads for outbound integration with external systems. The view therefore acts as a lightweight mapping layer that allows implementers and administrators to determine, for a given subscribed ERES event, which XML map code will be invoked when the event is published through the Workflow Business Event System.

Because the object is a view and not a table, it stores no data of its own. Instead, it derives its result set dynamically from Workflow event metadata and from the EDR XML utility package. The view is owned by APPS and is documented with VALID status, indicating it is a supported, active object in the application schema. Its relevance to the user search term "wf_event_subscriptions" is direct: the view is defined in part over the WF_EVENT_SUBSCRIPTIONS entity, which records the event filter subscriptions that drive Business Event System routing.

Underlying Base Objects

The documented view definition joins two principal sources. The first is WF_EVENTS_VL, the Workflow Events view that supplies the owner tag, display name, and internal event name (OWNER_TAG, DISPLAY_NAME, NAME) along with the event GUID. The second is WF_EVENT_SUBSCRIPTIONS, referenced in the ETRM metadata as a synonym resolving to the subscription records that store the EVENT_FILTER_GUID, the subscribed rule function, and the subscription GUID. The join condition matches A.GUID to B.EVENT_FILTER_GUID, and the result set is further restricted to subscriptions whose RULE_FUNCTION equals the value EDR_PSIG_RULE.PSIG_RULE. The fourth projected value is produced by a call to EDR_INDEXED_XML_UTIL.GET_WF_PARAMS with the parameter name EDR_XML_MAP_CODE and the subscription GUID B.GUID, returning the configured XML map code.

Additional documented base objects include the WF_CORE package and the EDR_INDEXED_XML_UTIL package. WF_CORE provides the underlying Workflow engine PL/SQL used by the event views, while EDR_INDEXED_XML_UTIL supplies the GET_WF_PARAMS function that reads the XML Gateway parameter associated with a specific subscription.

Key Columns

  • OWNER_APPLICATION — Corresponds to A.OWNER_TAG, the application short name that owns the business event (for example, an EDR or ERP application tag).
  • EVENT_DISPLAY_NAME — Corresponds to A.DISPLAY_NAME, the user-facing name of the event as presented in the Workflow Event setup and subscription administrative forms.
  • EVENT_NAME — Corresponds to A.NAME, the internal event identifier used programmatically by the Business Event System.
  • XML_MAPCODE — The value returned by EDR_INDEXED_XML_UTIL.GET_WF_PARAMS('EDR_XML_MAP_CODE', B.GUID), representing the XML Gateway map code associated with the ERES subscription.

Common Use Cases and Queries

The view is typically queried during E-Records integration diagnostics, when an administrator needs to confirm that each active ERES subscription is bound to the correct XML Gateway map. A representative query lists all mapped events:

SELECT owner_application, event_name, event_display_name, xml_mapcode FROM apps.edr_wfevent_xmlmap_v ORDER BY owner_application, event_name;

A second common pattern filters for a single event to verify the map code assigned to it:

SELECT event_name, xml_mapcode FROM apps.edr_wfevent_xmlmap_v WHERE event_name = :p_event_name;

Because the view already restricts results to the EDR_PSIG_RULE.PSIG_RULE rule function, it returns only those subscriptions relevant to E-Records XML publication, making it a convenient validation source during implementation and post-clone verification in both 12.1.1 and 12.2.2 environments.