Search Results partysite_update_post

Overview

PV_TAP_BES_PKG is a PL/SQL package residing in the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package belongs to the Oracle Partner Management and Trade Management (formerly Advanced Planning and Partner Relationship Management) functional area, and its name — containing the "TAP" and "BES" tokens — associates it with the Trading Partner / "Business Event Subscription" processing model used to synchronize partner and customer master data changes across applications. The package operates as a business event handler package: it consumes Oracle Workflow business events recorded in WF_EVENT_T and propagates the affected entity changes into the TAP staging and partner profile structures.

Its central purpose is to detect and post updates originating from the Oracle Trading Community Architecture (TCA) model — organizations, party sites, locations, and contact points — into the partner management tables that drive partner profile maintenance and partner batch change processing. In effect, PV_TAP_BES_PKG provides the inbound synchronization layer so that partner records remain consistent with the underlying TCA registry whenever master data is modified.

Key Procedures and Functions

The package exposes four documented procedures, each aligned to a specific TCA entity whose change must be propagated:

• ORGANIZATION_UPDATE_POST — Processes organization-level update events, applying changes from the TCA organization record to the affected partner profile definitions.
• PARTYSITE_UPDATE_POST — Handles party site update events, ensuring that changes to a party's site assignments are reflected in the associated partner profile data.
• LOCATION_UPDATE_POST — Processes location update events, propagating address and location attribute changes into the partner management structures.
• CONTACTPOINT_UPDATE_POST — Handles update events for contact points (such as phone, email, and other communication methods) attached to parties, maintaining consistency between TCA contact points and partner profiles.

The metadata does not document formal parameter lists for these procedures; they are designed to be invoked as event subscription handlers, consuming the event payload passed by the Workflow Business Event System runtime.

Tables Accessed

The package reads and writes a defined set of tables, accessed through APPS synonyms:

• WF_EVENT_T — the Oracle Workflow event queue table, the source of change notifications that trigger each handler.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_CONTACT_POINTS — the TCA registry tables holding the updated party, site, and contact point records being consumed.
• JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUP_MEMBERS — resource and resource group membership tables, used to resolve sales or partner resources linked to the parties.
• PV_PARTNER_PROFILES — the partner profile table updated with the incoming TCA changes.
• PV_TAP_BATCH_CHG_PARTNERS — the batch change staging table for partner records, used to queue or record the partner changes resulting from the event processing.

Usage Notes

PV_TAP_BES_PKG is not intended for direct invocation by end users. It is typically registered as a subscription handler against Oracle Workflow business events emitted by TCA or Partner Management when organization, party site, location, or contact point records are updated. When such an event fires, the Workflow Business Event System invokes the corresponding *_UPDATE_POST procedure automatically.

The package is referenced by no other documented packages, confirming its role as a leaf-level event handler rather than a shared utility. Customizations should avoid modifying the package directly; instead, extensions should follow Oracle's event subscription framework. In both 12.1.1 and 12.2.2, the package remains status VALID, and its dependencies on the STANDARD SYS package and WF_EVENT_T indicate a standard Workflow-integrated design with no unusual external dependencies.