Search Results delete_seed_qual_record

Overview

JTF_QUALIFIER_PVT is a private PL/SQL package in the APPS schema that provides the internal implementation layer for Oracle E-Business Suite's qualifier and territory-qualifier infrastructure within the CRM Foundation (JTF) product family. The package operates on the principle of a public/private API pair: the public package JTF_QUALIFIER_PUB exposes the callable interface, while JTF_QUALIFIER_PVT contains the actual business logic, validation routines, and DML operations that the public layer delegates to. The "PVT" classification confirms this split, and the documented dependency chain — JTF_QUALIFIER_PVT references JTF_QUALIFIER_PUB and FND_API, and is in turn referenced by JTF_QUALIFIER_PUB — reflects the standard Oracle Application Object Library (AOA) pattern where the public and private packages call into one another for shared helper logic while isolating direct data manipulation.

In functional terms, this package governs the definition and maintenance of qualifiers, seeded qualifier records, and their usage assignments against territory definitions. Qualifiers describe criteria used to filter and classify data (such as customers, resources, or territories) so that territory and assignment engines can evaluate them consistently.

Key Procedures and Functions

The ETRM metadata documents ten procedures that fall into three logical groups:

• Seeded qualifier maintenance: CREATE_SEED_QUAL_RECORD, UPDATE_SEED_QUAL_RECORD, and DELETE_SEED_QUAL_RECORD manage the entries in the seeded qualifier repository — the prebuilt qualifiers delivered by Oracle that form the base vocabulary used by territory and assignment rules.
• Qualifier usage maintenance: CREATE_QUAL_USGS_RECORD, UPDATE_QUAL_USGS_RECORD, and DELETE_QUAL_USGS_RECORD control records that associate a qualifier with a specific usage context, determining where and how a given qualifier is permitted to be applied.
• Qualifier definition maintenance: CREATE_QUALIFIER, UPDATE_QUALIFIER, and DELETE_QUALIFIER implement the lifecycle of user-defined qualifiers themselves, while CHECK_QUALIFIER_USAGE validates whether a qualifier is currently in use — typically functioning as a guard that prevents deletion or modification of qualifiers referenced elsewhere in the application.

Because these routines are private, they are not intended for direct invocation by external callers; parameter details are documented only within the package specification itself.

Tables Accessed

Based on documented references through APPS synonyms, the package touches the following tables:

• JTF_SEEDED_QUAL — the seeded qualifier repository maintained by the seed record procedures.
• JTF_QUAL_USGS — qualifying usage definitions, populated and maintained by the usage record procedures and inspected by CHECK_QUALIFIER_USAGE.
• JTF_TERR, JTF_TERR_QUAL, and JTF_TERR_TYPE_QUAL — territory, territory-qualifier, and territory-type qualifier tables, used to determine whether a qualifier participates in territory definitions before permitting modification or removal.
• FND_ORACLE_USERID, ALL_TAB_COLUMNS, and USER_SYNONYMS — Oracle Applications and data dictionary views used for environment and metadata validation, including verification of the database user and the existence of expected synonyms and columns.

It also depends on FND_API, the Oracle Application Object Library foundation package, indicating use of the standard API error-handling and message-stack conventions.

Usage Notes

JTF_QUALIFIER_PVT is not intended as a public integration point. Its documented caller is JTF_QUALIFIER_PUB, meaning that supported entry into this logic occurs exclusively through the public API. In practice the package is exercised when users create or maintain qualifiers and usage assignments through Oracle EBS forms (such as the territory and qualifier setup screens) that are built on the JTF_QUALIFIER_PUB API, and through any concurrent programs or published API calls that route through the public layer.

Custom code should likewise invoke JTF_QUALIFIER_PUB rather than this private package. Direct calls to JTF_QUALIFIER_PVT bypass Oracle's supported interface, risk breaking on patch application, and forgo the public API's validation and error handling. All operations ultimately write to the JTF seeded qualifier, usage, and territory-qualifier tables, so downstream territory and assignment processes depend on the integrity of these routines.