Search Results c_queue_prefix




Overview
Explore in AI Chat

Overview

JTS_CONFIG_VERSION_PVT is a private PL/SQL package owned by the APPS schema that provides the internal API for Oracle Setup Online Configuration Management within Oracle E-Business Suite. The package manages the lifecycle of configuration versions—the named, numbered snapshots that record the state of a setup configuration at a point in time. Its header declares AUTHID CURRENT_USER, so all statements execute with the privileges of the calling schema rather than the definer. The package is classified as PVT (private), meaning it is not intended as a public integration surface; it supports the user-facing configuration management pages (Version Summary and Version Details) and is consumed by other internal packages. The documented version stamp ($Header: jtsvcvrs.pls 115.6) identifies it as a long-standing component carried forward unchanged across EBS 12.1.1 and 12.2.2. A typed record, Config_Version_Rec_Type, models a full version row, spanning version identity and descriptive attributes through 15 descriptive flexfield segments, audit columns (creation and last-update date/user/login, plus resolved user names), joined configuration attributes (config name, description, flow id, flow name, flow type, and record mode), and version status fields such as replayed date. The package also declares the constant C_QUEUE_PREFIX = 'JTSCONFIGXMLAQ', tying version processing to the configuration XML Advanced Queue.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, grouped by function:

  • GET_VERSION_ID, GET_VERSION, and GET_VERSIONS retrieve a single version identifier, a single version record, and a set of version records respectively. GET_VERSIONS supplies the data set rendered by the Version Summary and Version Details pages.
  • CREATE_VERSION creates a new configuration version, establishing the snapshot identity that the remaining procedures subsequently manipulate.
  • UPDATE_NAME_DESC, UPDATE_VERSION_STAT, UPDATE_REPLAY_DATA, and UPDATE_LAST_MODIFIED maintain existing versions: renaming or re-describing a version, transitioning its status, writing replay-related data captured during reprocessing, and stamping last-modified audit information.
  • DELETE_VERSION, DELETE_SOME_VERSIONS, and DELETE_VERSIONS remove configuration versions. DELETE_VERSION targets a single version; DELETE_SOME_VERSIONS accepts a qualified subset for bulk removal; DELETE_VERSIONS provides the full bulk deletion entry point. The delete_versions search term maps directly to this trio of deletion routines, which is the documented mechanism for purging obsolete configuration snapshots.

Tables Accessed

Access is performed through APPS synonyms. The base and translation tables JTS_CONFIG_VERSIONS_B and JTS_CONFIG_VERSIONS_TL hold the version rows and their translatable name and description text; JTS_CONFIG_VERSIONS_B_S is the corresponding sequence or secondary object used to generate version identifiers. JTS_CONFIGURATIONS_B supplies the parent configuration to which each version belongs, including flow and record-mode attributes surfaced in the record type. FND_USER resolves created-by and last-updated-by identifiers into display names. FND_LOOKUP_VALUES translates coded values such as the display record mode into user-readable meanings, and FND_LANGUAGES supports language-aware retrieval and maintenance of the translated columns. PLITBLM is the standard EBS PL/SQL index-by table of VARCHAR2 used for bulk DML arrays, consistent with the bulk deletion procedures that pass sets of version identifiers in a single operation.

Usage Notes

Because JTS_CONFIG_VERSION_PVT is private, it is not called directly from custom forms or concurrent programs as a supported interface. It is invoked by Oracle Setup Online configuration management pages and by the three internal packages documented as referencing it. The deletion routines are the appropriate path when obsolete versions must be purged, with DELETE_VERSION for single-row removal and DELETE_VERSIONS or DELETE_SOME_VERSIONS for set-based cleanup; because deletes touch both the base and translation tables, completion of the corresponding rows should be verified after execution. Version-status, replay-data, and last-modified updates are normally triggered by configuration replay and reprocessing flows, and the JTSCONFIGXMLAQ queue prefix indicates that version content is materialized through the Advanced Queue mechanism. In 12.1.1 and 12.2.2, the package is functionally equivalent, with the 12.2 online patching architecture affecting only the editioning context in which the same API executes. Any custom use should be treated as unsupported and validated against a clone before production deployment.