Search Results delete_some_versions

Overview

APPS.JTS_CONFIG_VERSION_PVT is a private PL/SQL package body belonging to the Oracle E-Business Suite Configure-to-Order (CTO) product family, delivered under the JTS schema prefix. Its stated purpose in the package header is “Configuration Versions.” It provides the internal engine that maintains the version history of configurations stored by the CTO and Oracle Configurator integration. In EBS 12.1.1 and 12.2.2, configurations are user-defined assemblies whose structure and rules evolve over time; this package preserves each change as a discrete, numbered version so that an historical configuration can be reproduced, replayed, or deleted without corrupting the live definition. It is classified as a PRIVATE (PVT) API, meaning it is not an integration surface intended for external callers; ETRM records three other packages referencing it, and the public-facing wrapper packages within the JTS family depend on it for the low-level create, update, delete, and query operations against the version tables.

Key Procedures and Functions

• GET_VERSION_ID — Returns the next primary key for a new version row, drawing from the JTS_CONFIG_VERSIONS_B_S sequence.
• CREATE_VERSION — Inserts a new configuration version, assembling the derived version identifier with the next version number returned for the supplied configuration.
• UPDATE_NAME_DESC — Maintains the translated name and description of an existing version.
• UPDATE_VERSION_STAT — Transitions a version through its status lifecycle. Status values referenced by the package include NEW, PROCESS, SUBMIT, NOSUBMIT, COMPLETE, FAIL, CANCEL, RUNNING, SUCCESS and ERRORS.
• UPDATE_REPLAY_DATA — Stores or refreshes the replay payload used to reconstitute a configuration version.
• UPDATE_LAST_MODIFIED — Stamps the audit columns for a version row.
• DELETE_VERSION — Removes a single version.
• DELETE_SOME_VERSIONS — Bulk removal of a selected subset of versions.
• DELETE_VERSIONS — Deletes all versions associated with a configuration.
• GET_VERSION — Retrieves a single version record.
• GET_VERSIONS — Retrieves the set of versions for a configuration.

Two additional private helpers, GET_NEXT_VERSION_NUMBER and GET_NEXT_VERSION_ID, are visible in the source excerpt. The former counts existing rows for a configuration and returns MAX(version_number)+1, or 1 when none exist, with a WHEN OTHERS handler defaulting to 1.

Tables Accessed

The package operates on the JTS_CONFIG_VERSIONS family: JTS_CONFIG_VERSIONS_B for the base version rows and version numbering, JTS_CONFIG_VERSIONS_TL for translated name and description attributes, and the sequence JTS_CONFIG_VERSIONS_B_S for identifier generation. It also reads JTS_CONFIGURATIONS_B to validate the parent configuration. Supporting lookups include FND_LANGUAGES for the language of translated rows, FND_LOOKUP_VALUES for the JTS_STATUS lookup type that governs version status codes, and FND_USER for created-by and updated-by identification. The legacy PLITBLM table appears in the dependency list, indicating use of the older PL/SQL table-to-array interlist utility in set-based operations.

Usage Notes

As a PVT package, JTS_CONFIG_VERSION_PVT is not designed for direct invocation by customers or integrators. It is normally exercised through the CTO configuration user interface and the Oracle Configurator forms, through concurrent programs that submit, complete, or purge configuration versions, and indirectly from the three documented referencing packages. Custom code should call the supported public JTS APIs instead. Administrators may observe its activity indirectly through status values stored in the version tables, and any purge or archival process that removes configuration history ultimately routes through the DELETE_VERSION, DELETE_SOME_VERSIONS and DELETE_VERSIONS routines described here.