Search Results oke_party_merge_pkg




Overview
Explore in AI Chat

Overview

OKE_PARTY_MERGE_PKG is an Oracle Applications (APPS) PL/SQL package within the Oracle E-Business Suite Order Capture / Oracle Knowledge Exchange (OKE) module, which governs Oracle Contracts and the party and funding relationships associated with contract terms and pooling arrangements. The package's classification is listed as OTHER within the ETRM repository, indicating it is not a public, supported open interface API such as those published for purchasing or order management, but rather an internal utility package that participates in party merge processing.

The name of the package, together with its documented procedures, indicates that it exists to handle the re-pointing and reconciliation of contract-relevant party references when records for a party (customer, supplier, or trading partner) are merged within Oracle Trading Community Architecture (TCA). When two party records are consolidated into a single surviving party, any dependent data that stores the old party identifier must be updated to the surviving identifier. OKEE_PARTY_MERGE_PKG carries out this housekeeping for the contract funding source, funding source history, and pool party entities maintained by the contracts module.

The package is reported as VALID in the APPS schema and, per the documented dependency data, is referenced by no other APPS packages. Its own dependency list is minimal, consisting only of SYS.STANDARD and the package body itself, which is consistent with a leaf-level utility invoked directly by the merge framework rather than by other application packages.

Key Procedures and Functions

The ETRM metadata documents three procedures within OKEE_PARTY_MERGE_PKG, each corresponding to one of the contract-entity families that store party references:

  • POOL_PARTY_MERGE — Processes the merge of party records for pooled contract participation. This procedure is responsible for re-pointing or reconciling records in OKE_POOL_PARTIES so that party references are consolidated onto the surviving party identifier after a TCA party merge.
  • FUNDING_PARTY_MERGE — Processes the merge of party records for contract funding sources. This procedure operates on the funding source entity to update party references in the base funding source definition, OKE_K_FUNDING_SOURCES.
  • FUNDING_PARTY_H_MERGE — Processes the merge of party records for the history (audit) table associated with funding sources. This procedure mirrors the base-table logic of FUNDING_PARTY_MERGE against OKE_K_FUNDING_SOURCES_H so that historical versions remain consistent with the surviving party.

The parameter lists for these procedures are not published in the available metadata and are therefore not reproduced here; callers should inspect the package specification directly in a given environment.

Tables Accessed

The documented table references, resolved through APPS synonyms, are:

  • OKE_POOL_PARTIES — Stores the parties participating in a contract pool. POOL_PARTY_MERGE is the procedure that maintains this relationship across a party merge.
  • OKE_K_FUNDING_SOURCES — Holds the funding source definitions attached to contract terms, including the funding party reference. FUNDING_PARTY_MERGE maintains this table.
  • OKE_K_FUNDING_SOURCES_H — Holds historical (audit) versions of funding source rows. FUNDING_PARTY_H_MERGE maintains this table so that prior versions remain aligned with the surviving party.

Reads and writes are performed against these tables in support of the merge logic; the package writes the updated party identifiers and leaves the surrounding funding and pool data otherwise intact.

Usage Notes

OKEE_PARTY_MERGE_PKG is not a public open interface and is not intended for direct invocation by customers. It is typically called as part of the Oracle party merge framework (TCA and its dependent applications) when a user submits a merge of two party records from the Customer or Trading Partner forms. The contracts application registers these procedures as the merge handlers for its funding source, funding source history, and pool party data, so that consolidation of party records does not orphan or misalign contract funding and pooling relationships.

In Oracle EBS 12.1.1 and 12.2.2, the package should be treated as an internal implementation object. It is not referenced by any other APPS package, and custom code should not depend on its procedures because the interface is not documented as a supported API and may change without notice. The correct approach for party-related contract data correction is to use the supported Oracle party merge user interface, which will drive this package in the proper sequence. If troubleshooting is required, callers can enable diagnostics within the merge process and inspect the package body, which is present and VALID in the APPS schema.