Search Results initiate_payment

Overview

OZF_SPECIAL_PRICING_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 Trade Management (formerly Oracle Channel Revenue Management / ETRM) module. It is owned by the APPS schema and declared with AUTHID CURRENT_USER, meaning its unqualified references to database objects are resolved against the privileges of the calling user rather than the package owner. The package supports the special pricing and chargeback business flow, providing the internal logic that validates resale batch data, processes direct-customer order information, and drives the accrual and payment cycle associated with chargeback and resale claims. Because it is classified as a PVT (private) API, it is not intended as a public integration point; it is called internally by other Trade Management packages (the metadata indicates it is referenced by two other packages) rather than being exposed directly to external consumers or open interfaces.

Key Procedures and Functions

The package exposes three documented procedures:

• VALIDATE_ORDER_RECORD — Validates order information specific to the chargeback process. It performs the chargeback-relevant validation checks against a resale batch before further processing proceeds.
• PROCESS_ORDER — Described as the main API for chargeback. It reads the order information of direct customers and creates accruals based on the result of the pricing simulation.
• INITIATE_PAYMENT — Initiates payment for a batch. This is the procedure matching the user's search term. It triggers the payment step for a given resale batch within the special pricing workflow.

All three procedures follow the Oracle Applications API conventions, exposing the standard p_api_version, p_init_msg_list, p_commit, and p_validation_level input parameters along with x_return_status, x_msg_data, and x_msg_count output parameters. VALIDATE_ORDER_RECORD, PROCESS_ORDER, and INITIATE_PAYMENT each take a p_resale_batch_id input that identifies the batch being processed. The package also declares a default fetch-size constant, G_DEFAULT_NUM_REC_FETCH, set to 30, reflecting bulk-processing behaviour.

Tables Accessed

The package reads and writes a range of Trade Management tables through APPS synonyms, including:

• OZF_RESALE_BATCHES, OZF_RESALE_HEADERS, OZF_RESALE_LINES, OZF_RESALE_LINES_ALL, OZF_RESALE_LINES_INT, OZF_RESALE_LINES_INT_ALL — resale batch, header, line, and interface data that define the transactions being validated and processed.
• OZF_RESALE_ADJUSTMENTS_ALL — adjustment records applied during pricing and accrual calculation.
• OZF_RESALE_LOGS_ALL, OZF_RESALE_LOGS_ALL_S — processing log tables used to capture execution history and diagnostics.
• OZF_CLAIMS, OZF_CLAIM_LINES_UTIL_ALL, OZF_FUNDS_UTILIZED_ALL_B — claim and fund-utilization data used to track accruals and payments against customer funds.
• OZF_REQUEST_HEADERS_ALL_B, OZF_REQUEST_LINES_ALL — request/approval data tied to the batch workflow.
• AMS_ACT_PRODUCTS — activity product information referenced during processing.

Usage Notes

OZF_SPECIAL_PRICING_PVT is invoked internally within the Trade Management special pricing and chargeback flow, typically from concurrent programs (such as resale batch processing) or from other Trade Management packages that orchestrate batch validation, order processing, and payment initiation. Because it is a private API, custom code should not call it directly unless the full calling context — including batch state and interface data — is established; standard practice is to drive processing through the supported concurrent programs and let this package perform the underlying validation, accrual, and payment steps. Its parameter signatures mirror the Oracle Applications API standards, so error handling should check x_return_status and inspect x_msg_data / x_msg_count when a call returns an unexpected status. The package's reliance on AUTHID CURRENT_USER also means calling users must hold the appropriate privileges on the underlying OZF and AMS tables.