Search Results invoke_batch_auto_claim

Overview

OZF_SD_BATCH_PVT is a private PL/SQL package in the Oracle EBS Trade Management (formerly Oracle Sales and Marketing / Sponsored Deals) module. It belongs to the OZF schema family, which supports supplier and distributor programs including claim generation, fund utilization, and batch processing of supplier deals. The package encapsulates the business logic required to create and manage supplier deal batches, process pending claim batches, and convert claim amounts into offer currency. It is classified as a PVT (private) API, meaning it is intended for internal use by other Oracle EBS packages and concurrent programs rather than being a public integration interface. The package header carries a version marker reflecting maintenance through 2008, and the metadata identifies sixteen documented procedures and functions, of which CREATE_BATCH_MAIN and CREATE_BATCH_SUB are the primary entry points for batch creation.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions, organized around batch lifecycle activities:

• CREATE_BATCH_MAIN — The public driver procedure, typically invoked as a concurrent program entry point. It accepts organization, supplier, supplier site, product, request, fund, date range, period, and fifteen descriptive attribute parameters, and orchestrates the overall batch build process. Notably, in the 2008 revision its start and end date parameters were changed from DATE to VARCHAR2 to accommodate concurrent program argument handling.
• CREATE_BATCH_SUB — The worker procedure that performs the substantive batch construction. Unlike the main routine, it retains DATE-typed start and end date parameters and includes a p_commit flag that controls transactional commit behavior.
• CREATE_BATCH, CREATE_BATCH_HEADER — Lower-level routines that insert the batch header record and initialize batch structure.
• CREATE_OM_BATCH_LINES, CREATE_IDSM_BATCH_LINES — Generate batch line records specific to Order Management and iStore/IDSM source contexts respectively.
• UPDATE_AMOUNTS, GET_BATCH_CURRENCY_AMOUNT — Maintain and retrieve monetary values for batch records, supporting multi-currency offer processing.
• CONV_DISC_TO_OFFER_CURR_AMOUNT, CONV_AMT_TO_OFFER_CURR_AMOUNT — Convert discount and general amounts into the offer currency, applying conversion rules held in supplier code conversion data.
• GET_VENDOR_ITEM_ID — Resolves the vendor item identifier associated with a batch line.
• INVOKE_BATCH_AUTO_CLAIM, INVOKE_CLAIM — Trigger automated claim creation from completed batch records.
• PROCESS_SD_PENDING_CLM_BATCHES, PROCESS_SUPPLIER_SITES — Batch-level drivers that sweep pending supplier deal claim batches and iterate supplier site records.
• CURR_ROUND_EXT_PREC — Applies extended-precision rounding to currency amounts.

Tables Accessed

The package reads and writes a defined set of APPS-synonymed tables. Supplier identity and site data are drawn from AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. Accounting period validation relies on GL_PERIODS. Batch master and detail records are persisted in OZF_SD_BATCH_HEADERS_ALL, its _S sequence/audit companion OZF_SD_BATCH_HEADERS_ALL_S, and OZF_SD_BATCH_LINES_ALL. Fund consumption is tracked through OZF_FUNDS_UTILIZED_ALL_B, while supplier trade profiles and code conversion rules reside in OZF_SUPP_TRD_PRFLS_ALL and OZF_SUPP_CODE_CONVERSIONS_ALL. System-level behavior is governed by OZF_SYS_PARAMETERS_ALL. DBMS_SQL, DUAL, and PLITBLM are referenced for dynamic SQL, scalar evaluation, and index-by-table (PL/SQL table) operations.

Usage Notes

Because OZF_SD_BATCH_PVT is a private package, it is not intended for direct invocation by external integrations. It is normally called from concurrent program wrappers, most often through CREATE_BATCH_MAIN, which conforms to the standard EBS concurrent program signature (errbuf, retcode, and a parameter list). When invoked in this manner, the p_commit parameter on CREATE_BATCH_SUB governs whether the transaction commits per batch or defers to the caller. In Oracle EBS 12.1.1 and 12.2.2, the package operates within the APPS schema and depends on MOAC via the p_org_id parameter. Custom code should not call this package directly; instead, customers should use supported public APIs or concurrent programs in the Trade Management module. The package is referenced by one other package, reflecting its role as an internal building block rather than a standalone interface.