Search Results sales_transaction_rec_type

Overview

The APPS.OZF_SALES_TRANSACTIONS_PVT package is a private (PVT class) PL/SQL API within the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / OZF) module. It encapsulates the core business logic that governs the creation, validation, and persistence of trade management sales transactions — the records that represent resale activity, distributor sell-through, and channel sales reported into ETRM for the purposes of accrual calculation, chargeback processing, volume-based incentives, and special pricing eligibility. As a private package, it is not intended to be called directly by end-user consumers or external integrations; instead it functions as the shared internal engine invoked by multiple public APIs and processing engines across the OZF schema.

The package is registered as VALID in the APPS schema and is documented across Oracle EBS 12.1.1 and 12.2.2 environments. It depends on FND_API (the standard Oracle Applications error-handling and API framework), OZF_RESALE_COMMON_PVT, and the SYS STANDARD package. Its architectural role is central: it is referenced by eleven other packages, including OZF_ACCRUAL_ENGINE, OZF_CHARGEBACK_PVT, OZF_VOLUME_CALCULATION_PUB, OZF_SPECIAL_PRICING_PVT, OZF_ADJUSTMENT_EXT_PVT, and OZF_TP_ACCRUAL_PVT.

Key Procedures and Functions

Six documented procedures and functions form the public surface of this private package:

• VALIDATE_TRANSACTION — Performs pre-persistence validation of a sales transaction record, confirming required attributes, referential integrity, and business-rule compliance before the record is written or processed further.
• CREATE_TRANSACTION — Inserts a new trade management sales transaction, applying the standard API conventions for defaulting, sequence population, and caller-controlled commit semantics.
• INITIATE_INVENTORY_TMP — Initializes temporary inventory holding records, preparing the staging structure used for downstream volume or inventory-level processing.
• UPDATE_INVENTORY_TMP — Maintains and adjusts the temporary inventory records created during initiation, supporting cumulative or incremental updates as transaction lines are processed.
• VALIDATE_INVENTORY_LEVEL — Validates inventory-level quantities against the applicable sales transaction context, ensuring that volume-driven logic receives consistent data.
• GET_PURCHASE_PRICE — Retrieves the purchase price associated with an item or transaction line, supplying pricing input to downstream accrual, chargeback, or special pricing calculations.

Parameter lists are intentionally not documented here; callers should consult the package specification in the instance for exact signatures.

Tables Accessed

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

• OZF_SALES_TRANSACTIONS_ALL and OZF_SALES_TRANSACTIONS_ALL_S — the primary transaction and sequence tables into which created records are persisted.
• OZF_INVENTORY_TMP_T — the temporary inventory structure managed by the initiate and update procedures.
• OZF_RESALE_LINES_INT_ALL — resale line interface data used to source and reconcile incoming sales transactions.
• HZ_CUST_ACCOUNTS — customer and account validation and lookup.
• MTL_SYSTEM_ITEMS — item master validation for inventory and pricing logic.
• OE_ORDER_LINES_ALL — order line reference for traceability between trade transactions and the originating sales order.
• OZF_SYS_PARAMETERS_ALL — system-level configuration parameters governing processing behavior.
• DUAL and PLITBLM — used for scalar evaluation and PL/SQL table (index-by table) type support respectively.

Usage Notes

Because OZF_SALES_TRANSACTIONS_PVT is a private API, it is not called directly from Oracle Forms, concurrent programs, or external integrations. Instead it is invoked internally by the OZF processing engines and public APIs listed among its referencing objects. The most relevant caller in the context of the user's search term is OZF_VOLUME_CALCULATION_PUB, which relies on this package to validate transactions, manage temporary inventory levels, and retrieve purchase prices prior to performing volume-based incentive calculations. Similarly, the accrual engine, chargeback, special pricing, and adjustment extension packages delegate sales transaction creation and validation to this package to ensure consistent behavior across all trade management flows. Custom development should avoid direct calls where a corresponding public API exists; where no public alternative is available, the standard FND_API initialization and commit/rollback conventions used by this package must be honored by the caller to maintain transactional integrity.