Results for “oks_defaults”

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

Overview

OKS_PARTY_MERGE_PKG is a service-contracts package in the Oracle E-Business Suite (EBS) Applications (APPS) schema. Its business function is to support the Oracle Trading Community Architecture (TCA) party merge process for data owned by the Oracle Service (OKS) module. When two parties (for example, two customers or two organizations) are merged through the TCA party merge facility, records in dependent tables must be repointed from the "from" party to the "to" party so that history, preferences, and eligibility data remain consistent after the merge. This package provides the OKS-specific callback procedures that the generic TCA merge engine invokes for each registered OKS entity.

The package is declared AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling user rather than the definer. Its header carries the revision marker $Header: OKSPYMGS.pls 120.0 2005/05/25 18:30:33 appldev noship $, confirming it is a long-standing component of the service contracts data model. Under ETRM 12.2.2 it is classified as API classification OTHER, and it is referenced by zero other packages, indicating it is designed to be called by the merge framework rather than by other PL/SQL units.

Key Procedures and Functions

The package exposes four documented procedures, each responsible for merging the records of a single OKS entity:

• OKS_BILLING_PROFILES — Merges records in the OKS billing profiles entity, updating ownership from the source party to the target party.
• OKS_DEFAULTS — Merges records in the OKS defaults entity (backed by OKS_K_DEFAULTS), reassigning the default service contract attributes tied to the party.
• OKS_SERVICE_EXCEPTS — Merges records in the service availability exceptions entity (OKS_SERV_AVAIL_EXCEPTS), which governs party-specific service eligibility exceptions. This is the procedure most directly associated with the search term "oks_service_excepts".
• OKS_QUALIFIERS — Merges records in the OKS qualifiers entity, which stores party-level qualification rules used by service contract coverage and entitlement logic.

Each procedure follows the standard TCA merge callback signature, accepting the merge dictionary entity name, the source record identifier, the target identifier, the source and target foreign-key party identifiers, the parent entity name, the merge batch identifier, and the batch party identifier, and returning a status. The target identifier is passed as an IN OUT parameter so that the merge engine can record the surviving record.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• HZ_MERGE_DICTIONARY, HZ_MERGE_PARTIES, HZ_MERGE_BATCH, HZ_MERGE_PARTY_DETAILS — the TCA merge control and registry tables that supply entity names, party identifiers, and batch context to each callback.
• OKS_BILLING_PROFILES_B — the billing profile base table, updated by OKS_BILLING_PROFILES.
• OKS_K_DEFAULTS — the service contract defaults table, updated by OKS_DEFAULTS.
• OKS_SERV_AVAIL_EXCEPTS — the service availability exceptions table, updated by OKS_SERVICE_EXCEPTS.

Because the OKS_QUALIFIERS procedure is documented in the package but its underlying table is not included in the referenced-table list, it follows the same pattern of operating on the qualifiers entity within the OKS schema.

Usage Notes

OKS_PARTY_MERGE_PKG is not intended to be called directly from forms or custom code. Its procedures conform to the TCA party merge subscription model and are invoked by the TCA Merge engine (commonly through the "Merge Parties" concurrent program or the party merge UI) whenever a merge batch includes an OKS entity registered in HZ_MERGE_DICTIONARY. The merge engine passes batch context and record identifiers, and expects each procedure to return a status indicating success or failure so that the merge can be committed or rolled back consistently.

Implementers extending or troubleshooting party merge behavior should verify that the OKS entities are registered in HZ_MERGE_DICTIONARY and that this package is installed at the expected version. Because the package is referenced by no other packages, customizations should avoid modifying it directly; instead, the supported approach is to ensure the OKS entity registrations are correct and to review the merge batch log for any status returned by these procedures.