Search Results cs_contracttmpl_pvt




Overview
Explore in AI Chat

Overview

CS_CONTRACTTMPL_PVT is a private PL/SQL package in the APPS schema that underpins the Service (CS) Contract Templates functionality within Oracle E-Business Suite. Contract templates provide the reusable source records from which service contracts, warranties, and entitlement agreements are generated, supplying default terms, coverage, billing, pricing, and party information. This package encapsulates the low-level data manipulation logic — insert, lock, update, delete, and validation — for contract template records, and is designated with the PVT (private) API classification. As a private package, it is not a public integration surface; instead it is invoked internally by the public API layer and by the Contract Templates form, allowing a single, centralized implementation of the template table maintenance logic. The package status is documented as VALID in both 12.1.1 and 12.2.2, and it depends on the Oracle Application Object Library API package FND_API and on the TAPI_DEV_KIT, indicating conformance to the standard EBS Table API (TAPI) development model and error-handling conventions.

Key Procedures and Functions

The practice in a private TAPI package is to expose one procedure per DML operation on the underlying base table. The documented procedures are:

  • INSERT_ROW — Creates a new contract template record, populating the base table columns and performing any defaulting and pre-insert validation required before the row is committed.
  • LOCK_ROW — Acquires a row-level lock on an existing template, used to enforce concurrency control when an update is imminent.
  • UPDATE_ROW — Modifies an existing template record, applying the changed attributes and any necessary re-validation logic.
  • DELETE_ROW — Removes or logically deactivates a template record, subject to the business rules governing deletion of template data.
  • VALIDATE_ROW — Executes the attribute and entity validation checks for a template, typically used before insert or update, and consistent with FND_API error-stack conventions.

All procedures are invoked exclusively through the package specification and are documented as private to the application, so callers should not invoke them directly from custom code.

Tables Accessed

Three base tables are referenced through APPS synonyms, consistent with the TAPI pattern of manipulating both the base table and its translated (_S) table:

  • CS_CONTRACT_TEMPLATES — The primary contract template entity; the target of insert, update, and delete operations and the source for row-level locking.
  • CS_CONTRACT_TEMPLATES_S — The translated/attributes shadow table where translatable or additional column values are stored alongside the base row.
  • CS_CONTRACT_TYPES — The contract type definition table, read by the validation logic to verify that a template is associated with a valid contract type.

Usage Notes

Because the package is classified PVT, the correct integration point for custom or extension development is the corresponding public API, CS_CONTRACT_TPL_PUB, which the ETRM metadata confirms as the sole package referencing CS_CONTRACTTMPL_PVT. The standard course of action is to call the public API rather than the private package, preserving upgrade safety and ensuring that all validation and error handling are applied consistently. The Oracle Forms–based Contract Templates maintenance screen in the Service module invokes this package indirectly through the public layer when users create, change, or remove templates. Batch and concurrent processing that generates contracts and entitlements from templates likewise reaches the package through the public API. The dependency on FND_API indicates the use of the standard message-handling interface, so errors are returned to the caller through the FND_API error stack rather than raised as unhandled exceptions.