Search Results create_resale_utilization

Overview

OZF_RESALE_PUB is a public PL/SQL package in the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / ETRM) module, owning the resale and chargeback adjustment lifecycle. In releases 12.1.1 and 12.2.2, the package header (ozfprssh.pls) exposes four documented public APIs, while the body (ozfprssb.pls, $Header: ozfprssb.pls 120.8.12020000.2 2012/07/09) implements them alongside internal batch-processing logic. The package exists to move resale data from staging interfaces into Oracle's resales and adjustments tables, calculate resale utilization against the underlying offers and price lists, generate payment requests, and purge obsolete or processed records. As a _PUB classified package, OZF_RESALE_PUB is intended for external invocation by forms, concurrent programs, and integration code rather than being a private implementation detail.

Key Procedures and Functions

The package body documents four procedures:

• START_PROCESS_IFACE — Initiates the data processing of records held in the resale staging tables for a given resale batch, driving the interface from staged lines into the live resale structures.
• START_PAYMENT — Drives payment handling for eligible resale adjustments, producing or advancing the payment side of the resale/chargeback flow.
• START_PURGE — Removes processed or obsolete resale and adjustment data, supporting housekeeping and data-retention requirements.
• CREATE_RESALE_UTILIZATION — Creates resale utilization records, capturing how resale activity consumes (utilizes) the underlying offer and adjustment entitlements. This is the procedure most commonly targeted by callers and is the object matched by the search term create_resale_utilization.

Only START_PROCESS_IFACE has a full signature shown in the supplied source excerpt: it follows the standard EBS API pattern with p_api_version, p_init_msg_list, p_commit, p_validation_level, and a batch identifier input, returning x_return_status, x_msg_data, and x_msg_count. It validates the caller's API version via FND_API.Compatible_API_Call, sets a savepoint (PROCESS_IFACE_PUB), and honors FND_MSG_PUB debug levels. No parameter lists are asserted for the remaining procedures, as the metadata does not document them.

Tables Accessed

Via APPS synonyms, the package reads and writes the core resale and adjustment data model:

• OZF_RESALE_BATCHES_ALL — batch headers; START_PROCESS_IFACE selects ORG_ID from this table by RESALE_BATCH_ID.
• OZF_RESALE_LINES_ALL and OZF_RESALE_BATCH_LINE_MAPS_ALL — resale line records and their mapping back to source batch lines.
• OZF_RESALE_ADJUSTMENTS and OZF_RESALE_ADJUSTMENTS_ALL — adjustments derived from resale activity.
• OZF_OFFERS and OZF_OFFER_ADJ_RLTD_LINES — offer definitions and the lines related to offer adjustments, used when computing utilization.
• QP_LIST_LINES — Oracle Advanced Pricing list lines underlying the accruals used in utilization.
• OZF_SD_REQUEST_HEADERS_ALL_B — request headers supporting the payment flow.
• FND_USER — for user context/audit.

Usage Notes

OZF_RESALE_PUB is a public API and is not referenced by other packaged PL/SQL objects in the documented metadata (referenced by 0 other packages), indicating it is normally invoked directly from Oracle Forms UI actions, concurrent programs, or custom integration code. Callers should supply the standard FND_API parameters, pass FND_API.G_TRUE for init_msg_list where applicable, and expect FND-style message handling on the OUT parameters. Because the body defines only G_PKG_NAME, G_FILE_NAME, and debug flags at package level, no session state is cached; each call is self-contained and savepoint-protected, making the package safe to call from batch and online contexts alike.