Search Results ozf_debug_high_on

Overview

The APPS.OZF_BASELINESALES_LIFT_PVT package body is a private (PVT-classified) PL/SQL implementation residing in the Oracle E-Business Suite APPS schema. It belongs to the Oracle Trade Management (formerly Oracle Sales Compensation / Trade Management) family of objects, as indicated by the OZF prefix. Its documented business function is to purge baseline sales and promotional lift factor data held in the Trade Management interface, history, and error tables. Baseline sales represent the underlying sales volume against which promotional lift is measured; promotional lift factors quantify the incremental uplift attributable to a promotion. This package therefore supports the administrative maintenance of that analytical data, allowing stale or unwanted records to be removed cleanly, together with associated interface error entries.

Key Procedures and Functions

The ETRM metadata documents a single public procedure within the package body:

• START_PURGE — The primary entry point for purging baseline sales and promotional lift factor data. It accepts caller-supplied parameters that specify the data source, data type, whether current or historical records are targeted, the record type, and an as-of date. The procedure returns an error buffer and return code to the concurrent manager (ERRBUF and RETCODE), consistent with the standard concurrent program calling convention. Internally it constructs dynamic DELETE statements against the interface and history tables and removes related rows from the interface errors table based on entity name and entity row identifier.

Tables Accessed

The documented metadata does not enumerate synonyms accessed, but the source excerpt explicitly references OZF_INTERFACE_ERRORS. The dynamic SQL constructed by START_PURGE targets three logical table families:

• OZF_INTERFACE_ERRORS — purged of records whose ENTITY_NAME matches the purge target and whose ENTITY_ROW_ID corresponds to deleted interface rows, filtered by DATA_SOURCE and STATUS_FLAG.
• Interface tables (referenced through the dynamically built l_del_tbl_stmt1 statement) — purged based on DATA_SOURCE and STATUS_FLAG.
• History tables — purged based on DATA_SOURCE and a HISTORY_SNAPSHOT_DATE compared against the supplied as-of date.

Usage Notes

This is a private package, not intended for direct invocation by end users. It is typically called by a concurrent program wrapper—most likely the "Purge Baseline Sales and Promotional Lift Factor Data" program—which passes ERRBUF and RETCODE back to the concurrent manager. The presence of the flags OZF_DEBUG_HIGH_ON, OZF_DEBUG_MEDIUM_ON, and OZF_DEBUG_LOW_ON, derived from FND_MSG_PUB.CHECK_MSG_LEVEL, confirms that the package uses the standard FND message stack for debug logging. Users investigating the search term ozf_debug_high_on are likely tracing debug output emitted by this constant when the FND message level is set to Debug High; enabling that profile option causes verbose logging within START_PURGE. The package is referenced by zero other packages, confirming its role as a leaf-level implementation called only from its own concurrent program interface.