Search Results delete_claim_type

Overview

OZF_CLAIM_TYPE_PVT is a private PL/SQL package in the Oracle E-Business Suite Application Object Library (APPS) schema. It belongs to the Oracle Trade Management (formerly Oracle Marketing) product family, whose database objects carry the OZF prefix. The package encapsulates the business logic governing claim types — the configurable classifications that determine how trade promotion claims are created, accounted for, and posted to the General Ledger.

Claim types drive a significant amount of downstream behavior in Trade Management: they control whether claims are posted to GL, which transaction types are used for credit memos, debit memos, chargebacks and write-offs, which accounting flexfield segments apply to deductions and accruals, and whether approval processing is required. The package exists to centralize the validation and persistence of this configuration so that the same rules are applied regardless of the calling interface. It is classified as a PVT (private) package, meaning it is intended for internal use by other OZF packages and the Trade Management forms, not as a public integration API. The embedded record type claim_rec_type is the canonical structure through which a single claim type row is passed between procedures.

Key Procedures and Functions

The package exposes eight documented procedures and functions. Their purposes are as follows:

• CREATE_CLAIM_TYPE — Inserts a new claim type record based on the values supplied in the claim_rec_type record and returns the generated claim_type_id of the newly created row.
• UPDATE_CLAIM_TYPE — Applies changes to an existing claim type record, including its descriptive attributes and its associated GL and transaction type assignments.
• DELETE_CLAIM_TYPE — Removes a claim type record, subject to the package's integrity checks against dependent claims.
• VALIDATE_CLAIM_TYPE — Performs the business rule validation that must pass before a claim type can be created or updated, verifying the completeness and consistency of the supplied record.
• CHECK_CLAIM_TYPE_ITEMS — Verifies the items or dependent configuration associated with the claim type, used to determine whether referenced setup exists and is usable.
• CHECK_CLAIM_TYPE_RECORD — Validates the structure and content of a claim_rec_type record itself, confirming that mandatory columns and derived values are populated correctly.
• INIT_CLAIM_TYPE_REC — Initializes a claim_rec_type record, populating default values such as the who-columns (created_by, creation_date, last_update_login) and other standard defaults before the record is passed to CREATE_CLAIM_TYPE.
• COMPLETE_CLAIM_TYPE_REC — Finalizes a claim type record, resolving or populating derived fields so that the record is complete and ready for insertion or update.

Tables Accessed

The package operates against a small, focused set of tables, all reached through APPS synonyms:

• OZF_CLAIM_TYPES_ALL_B_S — The base table holding the claim type definition itself. This is the primary insert, update and delete target, and its columns map directly to the fields of claim_rec_type, including the GL account identifiers, transaction type identifiers, set of books, posting flag, and the fifteen descriptive flexfield attributes.
• OZF_CLAIMS — The claims transaction table. It is consulted during validation and deletion to determine whether existing claims reference the claim type, thereby preventing removal of a claim type that is in active use.
• AMS_APPROVAL_DETAILS — Stores approval routing and history for marketing objects. It is checked when validating the approval setup associated with the claim type configuration.
• DUAL — Used for simple single-row queries, such as obtaining sequence values or evaluating expressions within PL/SQL bodies.

Usage Notes

Because OZF_CLAIM_TYPE_PVT is a private package, it is not documented as a supported public API. It is normally invoked from the Oracle Trade Management claim type setup form and from other OZF packages — the metadata records that one other package references it. Customizations should not call it directly where a public API exists, and any direct invocation must respect the two-step pattern implied by the interface: call INIT_CLAIM_TYPE_REC to obtain a populated claim_rec_type record, then complete and validate it before calling CREATE_CLAIM_TYPE or UPDATE_CLAIM_TYPE. The claim_type_id and object_version_number fields support the standard EBS optimistic locking convention. The package carries the header revision 120.1, dated August 2005, and behaves identically under release 12.1.1 and 12.2.2, as no 12.2-specific changes are recorded.