Search Results ozf_debug_low_on

Overview

OZF_SALES_TRANSACTIONS_PVT is the private implementation package body for the Sales Transactions API in Oracle E-Business Suite's Trade Management (formerly Oracle Sales Foundation / OZF) application, part of the Oracle Advanced Pricing and Channel Revenue Management family. It provides the underlying PL/SQL logic used to validate, create, and maintain sales transaction records that feed the Trade Promotion and accrual processes. The package exposes public procedures through a companion specification (OZF_SALES_TRANSACTIONS_PVT is classified as a PVT API), and its body contains the concrete implementation of those procedures along with internal helpers. The package operates on sales transactions drawn from external order management and inventory data, staging them for downstream rebate, accrual, and settlement calculations.

The header identifies the source file as ozfvstnb.pls (version 120.13.12010000.4, last modified 2008/12/01) and confirms functionality shipped for both the 12.1.1 and 12.2.2 releases. Debug level flags (OZF_DEBUG_HIGH_ON, OZF_DEBUG_LOW_ON) are declared using FND_MSG_PUB.check_msg_level, and the package caches the profile values OZF_TP_COMMON_UOM and OZF_TP_COMMON_CURRENCY at package initialization.

Key Procedures and Functions

The documented API surface consists of six procedures and functions:

• VALIDATE_TRANSACTION — Validates an inbound sales transaction record (SALES_TRANSACTION_REC_TYPE) against business rules, returning standard FND_API return status, message count, and message data.
• CREATE_TRANSACTION — Inserts a new, validated sales transaction into the repository, typically the OZF_SALES_TRANSACTIONS_ALL table via the API.
• INITIATE_INVENTORY_TMP — Initializes the inventory temporary staging structure used to hold item/quantity information before validation.
• UPDATE_INVENTORY_TMP — Updates records in the temporary inventory staging table as transaction processing progresses.
• VALIDATE_INVENTORY_LEVEL — Validates that inventory quantities and related attributes satisfy the required rules.
• GET_PURCHASE_PRICE — Retrieves the applicable purchase price for a given item or transaction, used in pricing and accrual logic.

Tables Accessed

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

• OZF_SALES_TRANSACTIONS_ALL and OZF_SALES_TRANSACTIONS_ALL_S — the primary sales transaction repository and its sequence; written by CREATE_TRANSACTION.
• OZF_INVENTORY_TMP_T — the temporary inventory staging table used by the initiate/update inventory procedures.
• OZF_RESALE_LINES_INT_ALL — resale line interface records, consulted during validation of transaction lines.
• HZ_CUST_ACCOUNTS — customer account validation and identification.
• MTL_SYSTEM_ITEMS — item definition lookups for validation and pricing.
• OE_ORDER_LINES_ALL — order line source data for transactions.
• OZF_SYS_PARAMETERS_ALL — system parameters used to drive business rule behavior.
• DUAL and PLITBLM — utility lookups.

Usage Notes

OZF_SALES_TRANSACTIONS_PVT is referenced by eleven other packages, indicating it sits at the core of the Trade Management transaction pipeline. It is typically invoked from concurrent programs and other OZF APIs rather than directly from end-user forms, since its procedures follow the standard FND_API calling convention with API version, initialization flag, validation level, and return status parameters. Customizations should use the corresponding public specification rather than calling the body directly, and should respect the OZF_DEBUG_LOW_ON/OZF_DEBUG_HIGH_ON message levels when logging diagnostics.