Search Results update_version_stat




Overview
Explore in AI Chat

Overview

JTS_CONFIG_VERSION_PVT is a private PL/SQL package in the APPS schema that provides the internal API layer for Oracle Setup Online Configuration Management. Its declared purpose, stated in the package header, is to serve as the "Private API for Oracle Setup Online Configuration Management." The package manages the lifecycle of configuration versions: the header constants identify the package as G_PKG_NAME 'JTS_CONFIG_VERSION_PVT' and define a queue prefix constant, C_QUEUE_PREFIX, set to 'JTSCONFIGXMLAQ', which is used when configuration version data is published to an Advanced Queue. The package is declared AUTHID CURRENT_USER, so its unqualified references resolve against the calling schema's privileges rather than the definer's, a characteristic typical of EBS private APIs that are invoked from within the owning application stack.

The package centers on the record type Config_Version_Rec_Type, which models a configuration version together with its owning configuration and version status attributes. The record carries identifiers (configuration_id, version_id, version_name, version_number, description), the queue_name used for XML publication, the standard fifteen descriptive flexfield attribute columns, audit columns (creation_date, created_by, last_update_date, last_updated_by, last_update_login) with denormalized user name columns, a nested set of JTS_CONFIGURATIONS fields (config_name, config_desc, config_flow_id, config_flow_name, config_flow_type, config_record_mode, config_disp_record_mode), and status information from JTS_CONFIG_VERSION_STATUSES such as replayed_date. This structure supports the Version Summary and Version Details pages referenced in the source comments.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, all concerned with version maintenance:

  • GET_VERSION_ID — resolves the identifier for a configuration version.
  • CREATE_VERSION — creates a new configuration version record.
  • UPDATE_NAME_DESC — updates the name and description of an existing version.
  • UPDATE_VERSION_STAT — updates the status of a configuration version. This is the routine most directly associated with the search term "update_version_stat" and the version status transitions tracked by the package.
  • UPDATE_REPLAY_DATA — updates replay-related data for a version, corresponding to the replayed_date element in the version status record.
  • UPDATE_LAST_MODIFIED — maintains the last-modified audit information on a version.
  • DELETE_VERSION — deletes a single configuration version.
  • DELETE_SOME_VERSIONS — deletes a specified subset of versions.
  • DELETE_VERSIONS — deletes versions, likely the full set for a configuration.
  • GET_VERSION — retrieves a single version into the version record structure.
  • GET_VERSIONS — retrieves multiple versions, supporting the Version Summary page.

Parameter lists are not reproduced here; only the documented names and purposes are described.

Tables Accessed

The package references the following tables through APPS synonyms. JTS_CONFIGURATIONS_B stores the configuration header rows, and the configuration name, description, and flow attributes in Config_Version_Rec_Type are sourced from it. JTS_CONFIG_VERSIONS_B and JTS_CONFIG_VERSIONS_B_S hold the base and secondary version records, while JTS_CONFIG_VERSIONS_TL provides the translated version name and description columns. FND_USER supplies the created-by and last-updated-by name values exposed in the record. FND_LOOKUP_VALUES resolves the display value for the configuration record mode, and FND_LANGUAGES supports the translation join to JTS_CONFIG_VERSIONS_TL. PLITBLM is the EBS PL/SQL table-to-integer-table utility used for list handling within the package. The queue named by C_QUEUE_PREFIX is used for publication of configuration XML.

Usage Notes

As a private (PVT) API, JTS_CONFIG_VERSION_PVT is not intended for direct invocation by external custom code. It is consumed by the Oracle Setup Online configuration management forms pages — notably the Version Summary and Version Details screens — and by the three packages documented as referencing it. The status routine UPDATE_VERSION_STAT is invoked as versions move through their lifecycle states, and UPDATE_REPLAY_DATA is invoked when replay processing completes for a version. Customizations should generally call the public JTS_CONFIG_VERSION API or the supported configuration management flows rather than this package, and any direct use should respect the AUTHID CURRENT_USER semantics and the audit-column conventions maintained by UPDATE_LAST_MODIFIED.