Search Results create_contract




Overview
Explore in AI Chat

Overview

APPS.AHL_WARRANTY_CONTRACTS_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) and Complex Maintenance, Repair, and Overhaul (CMRO) module. It provides the core programmatic infrastructure for creating and validating warranty contracts associated with item instances tracked in the Oracle Installed Base (CSI) repository. Warranty contracts represent service entitlements that a customer holds against a specific configured item or unit, and this package encapsulates the business logic required to instantiate those entitlements from predefined warranty templates.

The package is designated with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the defining schema. This is characteristic of private API packages intended to be invoked through a higher-level public wrapper or another controlled entry point rather than called directly by end-user extensions. The ETRM metadata classifies this package as PVT, indicating that Oracle does not publish it as a supported public interface; Oracle's documented public warranty APIs reside in other packages that delegate to this one.

Key Procedures and Functions

The package exposes five documented program units:

  • AUTO_CREATE_WARRANTY_CONTRACTS — A public procedure designed to automatically generate warranty contracts in bulk. According to the embedded comments, it is invoked by a concurrent program (noted as "CP" in the source header), accepting only an API version parameter to drive the creation of contracts for eligible item instances.
  • CREATE_CONTRACT — The primary contract-creation routine. It builds a warranty contract from an existing warranty template for a specified item instance. It follows the standard Oracle API conventions: it accepts API version, initialization message list, commit, validation level, and module type parameters, along with the warranty template identifier and item instance identifier. It returns a warranty contract identifier and the standard return status, message count, and message data out parameters.
  • CAN_CONTRACT_BE_CREATED — A validation function that determines whether a given combination of warranty template and item instance is eligible for contract creation. It serves as a gatekeeper before the heavier creation logic executes.
  • IS_INSTANCE_WARRANTY_AVAILABLE — A function that checks whether an active warranty entitlement already exists or is otherwise available for a specific item instance, supporting duplicate-prevention logic.
  • ADD_LANGUAGE — A translation-support routine, consistent with the package's management of translated (_TL) tables, ensuring language rows exist for newly created or updated warranty contract records.

Tables Accessed

The package references a coherent set of warranty, template, and Installed Base tables through APPS synonyms. The core transactional tables are AHL_WARRANTY_CONTRACTS_B and its _S (sequence/primary key) and _TL (translation) counterparts, which store the warranty contract header. Contract-to-template linkage is held in AHL_WARRANTY_CONT_CTR_B, AHL_WARRANTY_CONT_CTR_B_S, and AHL_WARRANTY_CONT_CTR_TL. Template definitions and their associated items reside in AHL_WARRANTY_TEMPLATES_B, AHL_WARRANTY_TEMPLATES_TL, AHL_WARRANTY_TMPL_CTR_B, AHL_WARRANTY_TMPL_CTR_TL, and AHL_WARRANTY_TMPL_ITEMS. Installed Base context is supplied by AHL_UNIT_CONFIG_HEADERS, CSI_ITEM_INSTANCES, and CSI_COUNTER_ASSOCIATIONS. FND_LANGUAGES provides language validation for the translation logic.

Usage Notes

Because this is a PVT-class object, it is not intended for direct invocation from custom code. It is most commonly triggered through concurrent programs—notably the automatic warranty contract creation process—through Oracle's public warranty APIs, or indirectly through Installed Base and service contract forms. It is referenced by seven other packages within the application, underscoring its role as an internal service layer. In EBS 12.1.1 and 12.2.2, the package is deployed under the APPS schema, and its behavior around "extension of contract" scenarios is handled through the template-to-contract inheritance logic rather than through a dedicated extension procedure in this unit. Customizations should target documented public APIs, leaving this private package to Oracle's own lifecycle management.