Search Results default_claim_line_tbl




Overview
Explore in AI Chat

Overview

OZF_OM_VALIDATION_PVT is an Oracle E-Business Suite private PL/SQL package owned by the APPS schema and associated with the Oracle Trade Management (OZF) application module. Its role is to centralize the validation and defaulting logic used when claim lines in Oracle Trade Management are converted into or associated with Oracle Order Management (OM) transactions. The package is declared with AUTHID CURRENT_USER, a standard convention for EBS private APIs that execute under the privileges of the calling session.

The package exposes a record type, claim_line_item_rec_type, and an associated collection type, claim_line_item_tbl_type, both derived from columns on OZF_CLAIM_LINES. These types carry the claim line identity (claim line index, source object class, source object id, source object line id), item and quantity attributes (item_id, quantity, quantity_uom), and pricing attributes (rate, currency_code). The collection form is what enables the bulk _TBL variants of the APIs to process multiple claim lines in a single call. Because the package is classified as PVT, it is not intended for direct customer use; it is invoked internally by OZF public APIs and other private packages.

Key Procedures and Functions

  • GET_DEFAULT_ORDER_TYPE — Resolves and returns a default order type identifier. It accepts context inputs including a reason code, claim type, and set of books, and returns the order type id along with standard FND_API messaging outputs.
  • DEFAULT_CLAIM_LINE — Applies defaulting logic to a single claim line record, populating derived values on the inbound claim line structure before validation.
  • DEFAULT_CLAIM_LINE_TBL — The bulk counterpart to DEFAULT_CLAIM_LINE. This is the procedure most directly relevant to the search term default_claim_line_tbl. It operates against the claim_line_item_tbl_type collection, applying defaulting logic across many claim lines in one invocation, which is the standard pattern for set-based processing in EBS private APIs.
  • VALIDATE_CLAIM_LINE — Performs validation on a single claim line record, returning status and message information through the standard FND_API output parameters.
  • VALIDATE_CLAIM_LINE_TBL — The bulk validation counterpart, validating an entire claim line collection.
  • COMPLETE_RMA_VALIDATION — Finalizes validation for return material authorization (RMA) processing, handling the RMA-specific completion steps that follow standard claim line validation.

Tables Accessed

The package references a set of OZF and OM tables through APPS synonyms. OZF_CLAIM_LINES is the primary claim line source and the anchor for the record type definitions. OZF_CLAIMS and OZF_SYS_PARAMETERS supply claim header context and Trade Management system parameter values used during defaulting. On the Order Management side, OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, and OE_ORDER_LINES_ALL provide the order structures against which claim lines are validated or created, while OE_SYS_PARAMETERS_ALL supplies OM system parameters. Receivables tables RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES, and RA_CUSTOMER_TRX_LINES_ALL support validation of the corresponding invoice and credit transactions. PLITBLM is the standard EBS PL/SQL table used for message handling in bulk API processing.

Usage Notes

OZF_OM_VALIDATION_PVT is a private package and is not exposed to end users through forms or concurrent program parameters. It is invoked programmatically from within Oracle Trade Management processing flows—typically from a public OZF API or the package that is documented as referencing it—whenever claim lines must be defaulted or validated prior to order creation or RMA completion. The _TBL procedures are preferred for batch operations because they process a collection of claim lines in a single database call. Custom code should call the supported public OZF APIs rather than this private package directly, as its signature and behavior may change without notice between patch levels. The standard FND_API messaging parameters (x_return_status, x_msg_data, x_msg_count) should always be checked by any caller.