Search Results process_comp_appr_batch

Overview

OZF_SD_BATCH_FEED_PVT is a private PL/SQL package owned by the APPS schema within Oracle E-Business Suite, classified as a PVT (private) API. It belongs to the Oracle Trade Management / Channel Revenue Management product family, as indicated by the OZF module prefix. Its role is to support the batch feed processing of supplier ship-and-debit, dispute, and claim data — the supplier-initiated deduction workflow in Oracle Trade Management where a supplier or distributor submits batch feeds of transaction lines that are then validated, disputed, and reconciled against funds utilized.

The package declares a PL/SQL associative array type (number_tbl, an INDEX BY BINARY_INTEGER collection of NUMBER) used for in-memory processing of identifier lists. It carries an AUTHID CURRENT_USER directive, meaning it executes with the privileges of the invoking session rather than as definer, a common pattern for internal helper packages in EBS that must resolve APPS synonyms under the caller's security context. The header identifies the author as MBHATT with an original creation date of 16-Nov-2007, and history records note adjustment-related changes added in July 2009. The latest version marker corresponds to a 12.2 release shipment, though the same source line is compatible with 12.1.1 deployments.

Key Procedures and Functions

The ETRM metadata documents eight program units. Their names describe the batch feed lifecycle:

• POPULATE_INTERFACE — the largest documented routine by parameter count; it stages header and contact information into the interface tables that feed downstream batch line processing. Its extensive parameter list covers operating unit, supplier contact name, email, fax, phone, global partner role class, global business identifier, supply chain code, business name, address lines, city, country, postal code, region, and distribution attributes. This is the primary inbound staging procedure.
• UPDATE_DATA — applies updates to already-staged batch feed records, generally after validation or enrichment.
• UPDATE_STALE_DATA_BATCH_LINE — refreshes batch lines whose source data has changed or whose processing state has become out of date, keyed by batch number and batch line number.
• UPDATE_DISPUTE_DATA — maintains dispute records associated with batch lines, keeping the dispute tables synchronized with line changes.
• PROCESS_CHILD_BATCH — handles subordinate or dependent batches, allowing hierarchical batch structures to be processed independently of their parent.
• PROCESS_COMP_APPR_BATCH — processes completed or approved batches, moving them through the post-approval stage of the feed cycle.
• PROCESS_CLAIM — drives claim creation or processing from batch feed data.
• PROCESS_CHILD_BATCH and the remaining units operate in concert; no public standalone entry points are exposed beyond the declared set.

Tables Accessed

The package reads and writes the core Trade Management batch feed tables through APPS synonyms:

• OZF_SD_BATCH_HEADERS_ALL — the batch header record, holding batch number, operating unit, and supplier/distributor attributes populated by POPULATE_INTERFACE.
• OZF_SD_BATCH_LINES_ALL and OZF_SD_BATCH_LINES_ALL_S — the batch line detail and its sequence, the target of UPDATE_STALE_DATA_BATCH_LINE and UPDATE_DATA.
• OZF_SD_BATCH_LINES_INT_ALL and OZF_SD_BATCH_LINES_INT_ALL_S — the interface (staging) tables and sequence that POPULATE_INTERFACE writes into.
• OZF_SD_BATCH_LINE_DISPUTES and OZF_SD_BATCH_LINE_DISPUTES_S — dispute records maintained by UPDATE_DISPUTE_DATA.
• OZF_FUNDS_UTILIZED_ALL_B — funds utilization balances consulted during claim and approval processing.
• OZF_SYS_PARAMETERS_ALL — system parameter lookups that control processing behavior.
• DUAL — utility row source for scalar evaluations.
• PLITBLM — the standard EBS PL/SQL table-to-VARCHAR2 utility, used for list formatting.

Usage Notes

As a private (PVT) package, OZF_SD_BATCH_FEED_PVT is not intended as a direct public API. It is referenced by at least one other APPS package, which supplies the public wrapper that forms, concurrent programs, or OAF pages call. In a 12.1.1 or 12.2.2 environment, invocation typically originates from the Oracle Trade Management batch feed concurrent programs or from the supplier ship-and-debit UI flow, where batch feeds are loaded, validated, disputed, and approved. Because the package spec uses AUTHID CURRENT_USER, callers must have the appropriate grants on the underlying OZF tables and APPS synonyms. Customizations should avoid calling these procedures directly; instead, they should follow the supported path through the documented parent package or the standard concurrent program submission, since internal signatures may change between patch levels and are not covered by Oracle's public API commitment.