Results for “corrected_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.JTF_FM_FAILURES_V view is a CRM Foundation (JTF) reporting object that consolidates failure and address-correction information originating from the JTF Foundation Media (FM) processing subsystem. It is defined as a join between two base objects, JTF_FM_CONTENT_FAILURES and JTF_FM_PROCESSED, and is designed to surface, for a given request and party, the outcome of content processing together with any corrective action taken on the associated address data. The view is particularly relevant to queries involving the CORRECTED_ADDRESS column, which exposes the reformatted or validated address retained after a failure, and to the companion CORRECTED_FLAG column that signals whether correction was applied.

Within Oracle EBS 12.1.1 and 12.2.2, this view is used primarily by CRM and Foundation diagnostics, by data-quality reporting, and by integrations that need to retrieve the disposition of address-processing requests. It provides a stable, read-only projection over the underlying failure and processing tables, so consumers avoid direct dependency on the base table structures.

Underlying Base Objects

The view is defined over two documented SYNONYM-referenced base objects in the APPS schema:

• JTF_FM_CONTENT_FAILURES (JFUFFE) — supplies request-level failure details, the raw and corrected address, media type, and the failure description.
• JTF_FM_PROCESSED (JFUFPD) — supplies the party context for the same request and job.

The join is an equi-join on both REQUEST_ID and JOB, ensuring that failure records and processed-request records align for the same processing run.

Key Columns

The view exposes the following columns:

• REQUEST_ID — identifier of the FM processing request; part of the join key.
• JOB — job identifier associated with the request; part of the join key.
• PARTY_ID — the party for whom the request was processed, joined from JTF_FM_PROCESSED.
• FAILURE — description or code of the failure encountered during content processing.
• ADDRESS — the address value as originally submitted or encountered.
• MEDIA_TYPE — the media type associated with the request.
• CORRECTED_ADDRESS — the address value after correction or standardization; the primary target of searches using the term "corrected_address".
• CORRECTED_FLAG — indicator of whether correction was applied.

Common Use Cases and Queries

Typical uses include auditing which addresses were corrected during a processing run, identifying recurring failures by media type, and joining request outcomes to party records for CRM reporting.

• List corrected addresses for a request:

  SELECT request_id, job, party_id, address, corrected_address, corrected_flag
  FROM   apps.jtf_fm_failures_v
  WHERE  request_id = :p_request_id;

• Isolate only records where correction occurred:

  SELECT request_id, party_id, corrected_address
  FROM   apps.jtf_fm_failures_v
  WHERE  corrected_flag = 'Y';

• Aggregate correction activity by media type:

  SELECT media_type, COUNT(*) corrected_count
  FROM   apps.jtf_fm_failures_v
  WHERE  corrected_flag = 'Y'
  GROUP  BY media_type;

All columns should be treated as read-only; corrections must be performed against the base tables or through the supported Foundation APIs.