Search Results check_items

Overview

JTF_LOC_TYPES_PVT is a private (PVT-classified) PL/SQL package body owned by APPS that implements the business logic supporting location type definitions in Oracle E-Business Suite. The package manages the data stored in the JTF_LOC_TYPES_B and JTF_LOC_TYPES_TL tables, which underpin the classification of locations used throughout CRM and shared applications. Location types allow an enterprise to categorize physical or logical addresses — for example, as a customer site, an internal office, or a warehouse — so that downstream processes can apply consistent rules to each category.

The package follows the standard Oracle Application Object Library (AOA) API design pattern: it exposes a locking procedure, update logic, and a series of validation routines. It uses the FND_API message and exception framework, including FND_MSG_PUB and FND_API compatibility checks, so that calling code receives standardized return statuses (x_return_status), message counts, and message data. It also relies on JTF_Utility_PVT for diagnostic debug messages. The body carries a header revision reference to jtfvlotb.pls, indicating maintenance lineage within the JTF (CRM Foundation) product family.

Key Procedures and Functions

• LOCK_LOC_TYPE — Acquires a row-level lock on a location type record prior to update. The implementation opens two cursors against JTF_LOC_TYPES_B and JTF_LOC_TYPES_TL, selecting by location_type_id and object_version_number with FOR UPDATE NOWAIT, guarding against concurrent modification and enforcing optimistic locking.
• UPDATE_LOC_TYPE — Persists modifications to an existing location type record in the base and translation tables, applying the object-version check and returning the standard API return status, message count, and message data to the caller.
• CHECK_ITEMS — General validation routine used to verify the attribute set supplied for a location type before an insert or update is committed. It is the routine most frequently reached when callers search on validation logic within the package.
• CHECK_LOC_TYPE_REQ_ITEMS — Validates that all required (mandatory) items for a location type have been provided, ensuring that no location type is created or updated with missing mandatory attributes.
• CHECK_LOC_TYPE_UK_ITEMS — Validates uniqueness-key items for a location type, enforcing that the combination of key attributes does not duplicate an existing record and thereby preserving the integrity of the unique key constraint.

Tables Accessed

• JTF_LOC_TYPES_B — The base table holding the primary, language-independent definition of each location type, including the location_type_id and object_version_number used for locking and updates.
• JTF_LOC_TYPES_TL — The translation table holding the language-specific descriptive text for each location type. The locking cursor filters on USERENV('LANG') matching the language or source language, so only the appropriate translation row is locked. Referenced through APPS synonyms, consistent with the ETRM metadata for release 12.2.2.

Usage Notes

As a PVT package, JTF_LOC_TYPES_PVT is not intended for direct invocation by external or customer code; it is referenced internally by one other package, which acts as the public wrapper or business-layer entry point. Typical callers are CRM Foundation setup forms and related APIs that create, maintain, or validate location type definitions. Customizations should call the supported public API rather than this private body. When invoked, callers must pass a compatible API version (l_api_version is 1.0), and may request message-list initialization via p_init_msg_list. The locking procedure should precede any update to respect the object_version_number concurrency model. Because validation is split across CHECK_ITEMS, CHECK_LOC_TYPE_REQ_ITEMS, and CHECK_LOC_TYPE_UK_ITEMS, integrators can rely on the package to enforce both mandatory-attribute and uniqueness rules before data is committed.