Search Results update_claim

Overview

OZF_PARTNER_CLAIM_GRP is a public PL/SQL package owned by APPS in the Oracle E-Business Suite, classified in ETRM metadata as a group (GRP) API. It belongs to the Oracle Trade Management (OZF) product family and provides the programmatic interface for creating and maintaining partner claim records. In the trade management and channel revenue model, a claim represents a receivable or payable transaction raised against a partner, reseller, distributor, or similar trading relationship. The package header declares the pragma AUTHID CURRENT_USER, meaning the executing user's privileges govern name resolution and access at runtime rather than the definer's; this is characteristic of seeded group APIs intended primary for internal orchestration and secondary for controlled custom extension.

The user search term "SIB insurance partners" suggests interest in partner claim handling for specialized trading partners. The package is partner-agnostic: any partner type, including insurance-sector partners transacting channel or promotional claims, is modeled through the generic claim structures rather than through partner-type-specific logic. No partner-class-specific branching is documented in the package source.

Key Procedures and Functions

ETRM documents two procedures for this package. Parameter lists are not reproduced here and must be confirmed against the installed package specification.

• CREATE_CLAIM — Inserts a new claim into the trade management schema. It accepts the claim attributes defined by the package's CLAIM_REC_TYPE record type and persists the header-level claim record. It is the primary entry point for raising a claim from an external process or a form.
• UPDATE_CLAIM — Modifies an existing claim identified by its claim identifier (CLAIM_ID), applying changed attribute values to the stored record. It supports corrections and status progression on claims previously created.

The package defines the record type CLAIM_REC_TYPE for the claim header, spanning identifiers (CLAIM_ID, CLAIM_NUMBER), classification (CLAIM_TYPE_ID, SOURCE_OBJECT_CLASS), dates (CLAIM_DATE, DUE_DATE, GL_DATE, CUSTOMER_REF_DATE), monetary fields (AMOUNT, CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE, SET_OF_BOOKS_ID), customer and site references (CUST_ACCOUNT_ID, CUST_BILLTO_ACCT_SITE_ID, CUST_SHIPTO_ACCT_SITE_ID, RELATED_CUST_ACCOUNT_ID), ownership and responsibility (OWNER_ID, SALES_REP_ID, COLLECTOR_ID, CONTACT_ID, BROKER_ID), status (STATUS_CODE, USER_STATUS_ID), and the standard DFF columns ATTRIBUTE1 through ATTRIBUTE15 with ATTRIBUTE_CATEGORY. Multi-org context is supplied via ORG_ID. The record shape aligns directly with the claim table columns, so callers populate the record and pass it to CREATE_CLAIM or UPDATE_CLAIM.

Tables Accessed

• OZF_CLAIMS_ALL — The claim header table. CREATE_CLAIM inserts here; UPDATE_CLAIM updates the corresponding row. The _ALL suffix indicates the table is partitioned by operating unit, consistent with the ORG_ID element of the record type.
• OZF_CLAIM_LINES_ALL — Holds claim line detail. The package references this table to maintain or validate line-level content associated with the claim header.
• OZF_CLAIM_LINES_UTIL_ALL — Stores claim line utilization, typically against accrued or budgeted funds. Referenced for utilization bookkeeping tied to claim lines.
• OZF_FUNDS_UTILIZED_ALL_B — Records funds consumed against trade management budgets; the _B designation indicates a base (non-translated) table. The package references this table so that claim activity is reflected in fund utilization balances.

All tables are addressed through APPS synonyms, and row-level operating unit security applies to the _ALL tables. One other package references OZF_PARTNER_CLAIM_GRP, indicating it is a dependency in the higher-level claim orchestration flow rather than a standalone entry point.

Usage Notes

OZF_PARTNER_CLAIM_GRP is classified as a group API, so it is generally not invoked directly by end users. Typical invocation paths are the Trade Management claim entry forms in the Oracle Forms layer, concurrent programs that generate claims from trade promotions or accruals, and internal PL/SQL packages that call CREATE_CLAIM and UPDATE_CLAIM as part of the broader claim lifecycle. Because the original header carries a 2003 revision marker and no ship flag, the package is a long-standing seeded component whose behavior is stable across EBS 12.1.1 and 12.2.2. The header is sparsely documented on purpose, so integrators should treat the package specification and the CLAIM_REC_TYPE definition as the authoritative interface contract, populate the DFF and status attributes with values valid for the target operating unit, and rely on the standard EBS error and validation conventions rather than assuming additional business rules. New custom code should call this package rather than writing directly to the four claim tables, so that utilization and funds bookkeeping remain consistent.