Search Results replay_status_code

Overview

APPS.JTS_CONFIG_VERSIONS_VL is a multi-lingual (VL) view in the Oracle E-Business Suite Applications (APPS) schema, registered under the FND Design Data object JTS.JTS_CONFIG_VERSIONS_VL. It presents configuration version records maintained by the JTS (TeleSales / CRM) product family and is described in the ETRM metadata as storing "Configuration Versions as described in Versions Summary page." In practice, the view exposes the language-resolved form of the underlying configuration-version entity, meaning it joins the base schema table to the corresponding translation table and returns the row in the session's current language, defaulting to the base language when no translation row exists.

Because the object is flagged VALID and typed as a MultiLingual view, it is safe for direct SQL access, but it is intended primarily as a reporting and integration surface rather than an update target. The presence of the REPLAY_STATUS_CODE column makes the view particularly relevant when users are investigating replayed or pending replay operations against configuration versions — that is, the state of version rows that have been pushed to a queue and reconciled back. The view also carries the standard WHO audit columns, which permits date-bounded and user-bounded reporting consistent with EBS conventions.

Underlying Base Objects

The ETRM metadata for this object documents no referenced base objects explicitly, which is typical for VL views whose source SQL is generated by the FND design layer. From the exported query text and the documented columns, the view is defined over the base configuration-version table (identified by the JTS_CONFIG_VERSIONS family) and its associated translation (_TL) table, with the language join enforced through the VL mechanism. The ROW_ID column of type ROWID reflects a direct selection from the base table row and is not resolvable from a translation join alone, confirming the base table is the driving table of the query.

In Oracle EBS 12.1.1 and 12.2.2 the JTS schema objects are owned by the product install, with synonyms or grants in APPS to make them available to the EBS application layer. The dependency chain therefore runs JTS base table and JTS translation table into the VL view, exposed as APPS.JTS_CONFIG_VERSIONS_VL. No other dependent objects are documented in the ETRM extract.

Key Columns

• VERSION_ID — surrogate primary identifier of the configuration version row.
• VERSION_NAME and DESCRIPTION — the translated attributes surfaced through the VL layer; these are the values that change with the session language.
• CONFIGURATION_ID — foreign reference to the parent configuration record.
• VERSION_NUMBER — sequence number identifying which iteration of the configuration is stored.
• QUEUE_NAME — the advanced queue used when the version is dispatched for replay.
• VERSION_STATUS_CODE — lifecycle state of the configuration version itself.
• REPLAY_STATUS_CODE — the status of the replay attempt for the version; this is the column most commonly searched by users and is the primary indicator of whether a replay succeeded, failed, or remains pending.
• REPLAYED_ON and REPLAYED_BY — timestamp and FND user identifier of the replay action.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the Forms layer.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield segment columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical uses include monitoring replay activity, identifying stalled configuration versions, and auditing who replayed a version and when. The query text supplied in the metadata forms the basis of ad-hoc reports:

• List all versions whose replay has not completed:
  SELECT version_id, version_name, configuration_id, version_status_code, replay_status_code FROM apps.jts_config_versions_vl WHERE replay_status_code <> 'COMPLETE';
• Replay audit for a given date range:
  SELECT version_id, replayed_by, replayed_on, replay_status_code FROM apps.jts_config_versions_vl WHERE replayed_on BETWEEN :from_date AND :to_date ORDER BY replayed_on DESC;
• Queue backlog inspection by QUEUE_NAME combined with REPLAY_STATUS_CODE to determine which AQ queues are accumulating unprocessed versions.
• Join to FND_USER on REPLAYED_BY to render the operator name in a report, and to the parent configuration table on CONFIGURATION_ID for a hierarchical view.

Because the view is language resolved, reports built against it return translated VERSION_NAME and DESCRIPTION text appropriate to the reporting user's language setting, which makes it suitable for end-user dashboards without additional translation joins.