Search Results not_replayed

Overview

The APPS.JTS_CONFIG_VER_STATUS_PVT_W package is a private PL/SQL wrapper within the Oracle E-Business Suite Java-based JTS (Java Technology Stack) schema, owned by APPS. In EBS 12.1.1 and 12.2.2, the JTS schema supports configuration and version-tracking services used by the CRM/TeleSales and related configuration frameworks, which rely on Java servlet and JDBC-layer components. The _PVT_W suffix indicates that this is a private wrapper package intended for internal use by JTS infrastructure rather than as a public, customer-callable API. Its principal business function is to evaluate and classify the replay/version status of configuration records, exposing Boolean and numeric flags that higher-level JTS components use to determine whether a given configuration version has been replayed, is currently in replay, or has not yet been replayed.

Key Procedures and Functions

The package exposes four procedures:

• ANY_VERSION_REPLAYED — Determines whether any version of a specified configuration has been replayed, returning the outcome through an out parameter that reports the replayed state for the given configuration identifier.
• IN_REPLAY_STATUS — Evaluates a supplied status value and returns a Boolean-style result (via ddrosetta_retval_bool) indicating whether the status corresponds to an in-replay condition.
• IN_VERSION_STATUS — The procedure referenced by the search term in_version_status. It accepts a status string and returns a Boolean-style result indicating whether that status qualifies as a version status within the JTS configuration workflow.
• NOT_REPLAYED — Evaluates a supplied status value and returns a numeric out flag indicating whether the configuration version has not been replayed.

Each procedure follows the JTS wrapper convention of accepting a leading p_api_version parameter for API versioning, and uses the ddrosetta_retval_bool convention to translate Oracle Boolean semantics into a numeric return representation.

Tables Accessed

The ETRM metadata for this object does not document any explicit base tables accessed directly or through APPS synonyms. In practice, the private wrapper delegates its logic to the underlying JTS configuration version-status implementation, which reads configuration and version-status data maintained by the JTS schema. Because no table-level dependencies are recorded, consumers should treat the package as an opaque status-evaluation utility rather than a direct data-access layer.

Usage Notes

As a private wrapper (_PVT_W), this package is not intended for direct invocation by end users or custom extensions. It is referenced internally by JTS components and, per the metadata, is not consumed by any other documented package. Oracle does not publish a public API contract for it, and its header carries a 2002-era change history, reflecting its role as stable infrastructure code. Customers encountering the in_version_status identifier during debugging should recognize it as an internal JTS status-check routine; modifications or direct calls are unsupported and should be avoided in favor of supported EBS APIs.