Search Results start_payment

Overview

OZF_RESALE_PUB is a public PL/SQL API package in the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / iPayment) application, owned by the APPS schema. It governs the resale processing lifecycle for trade promotion resale batches, which represent vendor-funded resale activities recorded against offers, adjustments, and offers-related lines. The package encapsulates the business logic used to validate, process, pay, and purge resale records that have been staged in the resale interface tables. It exposes a published, versioned API surface following the standard FND_API conventions — including API version compatibility checks, message list initialisation, savepoints, and the standard request/output parameter triplet (x_return_status, x_msg_data, x_msg_count). In the context of Oracle EBS 12.1.1 and 12.2.2, OZF_RESALE_PUB is the central entry point for programmatic control of resale batch processing, allowing callers such as concurrent programs, forms, and custom extensions to drive the resale lifecycle without directly manipulating the underlying transaction tables.

Key Procedures and Functions

• START_PROCESS_IFACE — Initiates processing of records held in the resale interface tables for a given resale batch. It performs API compatibility validation, initialises the message list, resolves the operating unit (org_id) from OZF_RESALE_BATCHES_ALL for the supplied batch, and establishes a savepoint before invoking the core processing logic.
• START_PAYMENT — This is the procedure most relevant to the user search term "start_payment". It drives the payment initiation step for processed resale records, moving eligible resale lines and adjustments toward settlement. It is the documented public entry point for triggering payment activity on a resale batch.
• START_PURGE — Removes or clears processed resale data in accordance with the resale purge rules, supporting housekeeping and data-retention requirements after processing and payment have completed.
• CREATE_RESALE_UTILIZATION — Creates resale utilization records, representing the consumption or application of resale funds against the associated offer, adjustment, and offer-adjusted-related-line structures.

Tables Accessed

• OZF_RESALE_BATCHES_ALL — Read to resolve the operating unit for the resale batch referenced during processing.
• OZF_RESALE_LINES_ALL and OZF_RESALE_BATCH_LINE_MAPS_ALL — The primary resale line data and its mapping to batches, updated as processing and payment progress.
• OZF_RESALE_ADJUSTMENTS and OZF_RESALE_ADJUSTMENTS_ALL — Adjustment records derived from or associated with resale activity.
• OZF_OFFERS, OZF_OFFER_ADJ_RLTD_LINES, and QP_LIST_LINES — Offer and pricing/list line definitions providing the promotional context and qualification basis for resale transactions.
• OZF_SD_REQUEST_HEADERS_ALL_B — Supplier/customer request header records linked to resale settlement requests.
• FND_USER — Referenced for user identity and audit context during processing.

Usage Notes

OZF_RESALE_PUB is classified as a PUB (public) API, meaning it is the supported integration surface for resale processing and is intended to be called rather than having its underlying tables modified directly. In practice, it is invoked from Oracle Trade Management concurrent programs that process, pay, and purge resale batches, and from associated OAF/Forms-based resale batch user interfaces. Custom code should invoke the procedures using the standard FND_API parameter pattern, passing an API version compatible with version 1.0 of the individual API, and should honour the returned x_return_status (FND_API.G_RET_STS_SUCCESS, G_RET_STS_ERROR, or G_RET_STS_UNEXPECTED_ERROR) together with the message count and message data outputs. Because the package references OZF_*_ALL tables, callers must ensure the correct operating unit context is initialised (MO/GMO) before invocation. The package is not referenced by any other documented package, so it functions as a top-level integration and processing entry point rather than a shared utility layer.