Search Results ozf_code_conversions

Overview

APPS.OZF_ACCOUNT_MERGE_PKG is a Trading Community and Trade Management (formerly Oracle Trade Management / Oracle Incentive Compensation Offer and Claim modules) PL/SQL package body responsible for propagating customer account merge events across the OZF (Oracle Trade Management) schema. When two customer accounts are merged at the Trading Community Architecture (TCA) layer — for example, through the Customer Merge concurrent program or the Oracle Customers Online merge UI — the affected transactional and denormalized tables in the OZF footprint must be re-pointed from the losing (duplicate) account to the surviving (master) account. This package implements that re-pointing logic as a set of modular merge procedures, one per related OZF entity.

The package is classified in ETRM as an OTHER API, owned by APPS, and is referenced by no other packages, meaning it is designed to be driven directly by the TCA customer merge framework rather than called as a dependency of other OZF APIs. The header line reference ozfvcmrb.pls 115.6 indicates this body has been stable since the 11.5.x code line and is carried forward into 12.1.1 and 12.2.2 without structural change.

Key Procedures and Functions

The documented package exposes thirteen merge procedures, each targeting a specific OZF entity:

• MERGE_ACCT_ALLOC — Merges account allocation records in OZF_ACCOUNT_ALLOCATIONS, the primary subject of the excerpted source. It defines a MERGE_HEADER_ID_LIST_TYPE associative array indexed by BINARY_INTEGER to collect distinct CUSTOMER_MERGE_HEADER_ID values, along with parallel collections for account allocation IDs, customer account IDs, bill-to site use IDs, and site use IDs — storing original and new values in paired lists so that source and target keys can be reconciled record by record.
• MERGE_CLAIMS and MERGE_CLAIMS_HISTORY — Re-point customer references on active and historical claims respectively.
• MERGE_CLAIM_LINES and MERGE_CLAIM_LINES_HIST — Apply the same treatment to claim line detail and its history table.
• MERGE_CODE_CONVERSIONS — Updates account-scoped code conversion mappings in OZF_CODE_CONVERSIONS.
• MERGE_CUST_DAILY_FACTS — Reassigns customer-denormalized daily fact rows in OZF_CUST_DAILY_FACTS.
• MERGE_FUND_UTILIZATION — Consolidates fund utilization balances in OZF_FUNDS_UTILIZED_ALL_B.
• MERGE_OFFER_DENORM and MERGE_OFFER_HEADER — Handle the denormalized offer tables and OZF_OFFERS header rows.
• MERGE_REQUEST_HEADER — Merges request header records in OZF_REQUEST_HEADERS_ALL_B.
• MERGE_RETAIL_PRICE_POINTS — Re-points retail price point data in OZF_RETAIL_PRICE_POINTS.
• MERGE_TRADE_PROFILES — Merges customer trade profile records in OZF_CUST_TRD_PRFLS.

Parameter lists are not documented here and should not be assumed; callers must consult the live package specification.

Tables Accessed

The package reads merge context from HZ_CUSTOMER_MERGE_LOG and its _S sequence, and from RA_CUSTOMER_MERGE_HEADERS via the excerpted cursor, to determine which account IDs map to which merge header. It then writes to the OZF tables named above — allocations, activity customers (OZF_ACTIVITY_CUSTOMERS), claims and claim lines with their history counterparts, code conversions, customer daily facts, trade profiles, fund utilization, offers, request headers, and retail price points — updating the customer, site use, and bill-to site use identifiers to the surviving account.

Usage Notes

OZF_ACCOUNT_MERGE_PKG is invoked as part of the customer merge flow, typically from the TCA merge framework or an administratively scheduled concurrent request rather than from an end-user form. Because it is not referenced by any other package, it is not embedded in the normal OZF transaction APIs and must be called explicitly during account consolidation projects. Its internal use of a req_id, set_num, and process_mode signature in the excerpted procedure indicates it supports batched (set-based) processing, which matters for performance when large claims or fund utilization volumes are involved. Custom code calling this package should replicate the same request/batch identifiers used by the driving merge process to keep processing idempotent and restartable.