Search Results print_address




Overview
Explore in AI Chat

Overview

APPS.JTF_FM_PROCESSED_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It exposes processed records from the JTF Foundation Messaging (FM) subsystem, which handles outbound communications such as email, fax, and printed correspondence generated by Oracle's fulfillment and notification infrastructure. The view presents one row per processed messaging job, combining a REQUEST_ID and a JOB identifier as a compound primary key labeled PK_ID.

Because the underlying JTF_FM_PROCESSED table stores audit and status data for messaging requests, JTF_FM_PROCESSED_V provides a stable, read-friendly interface for reporting and integration. It is commonly queried in the context of address printing, party notification, and outcome tracking. Users searching for "print_address" will find that the PRINT_ADDRESS column is exposed directly by this view, making it relevant to print-queue diagnostics and correspondence auditing.

Underlying Base Objects

The view is defined over a single documented base object: the synonym JTF_FM_PROCESSED. The view definition is a direct projection with no joins, filters, or aggregations:

The only derived expression is PK_ID, a concatenation of REQUEST_ID and JOB that provides a synthetic unique identifier. All other columns map one-to-one to base table columns. Because it is a simple view, DML against JTF_FM_PROCESSED_V is not intended; it should be treated as read-only for reporting purposes.

Key Columns

  • REQUEST_ID – Identifier of the concurrent or messaging request that generated the processed record.
  • JOB – Job identifier within the request, distinguishing multiple messaging items under one request.
  • PARTY_ID / PARTY_NAME – The trading party or recipient associated with the message.
  • EMAIL_ADDRESS / FAX_ADDRESS / PRINT_ADDRESS – Destination values for the respective delivery channel. PRINT_ADDRESS holds the address text used when correspondence is printed rather than emailed or faxed.
  • OUTCOME_CODE – Result of the messaging attempt, used to determine success or failure.
  • MERGE_XML – The XML payload containing merge/attribute data used to render the communication.
  • EMAIL_STATUS – Delivery status specific to the email channel.
  • Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
  • PK_ID – Concatenation of REQUEST_ID and JOB, exposed for convenience as a row key.

Common Use Cases and Queries

Typical scenarios include auditing outbound correspondence, troubleshooting printed address delivery, and validating messaging outcomes by request. A simple query listing processed jobs with their print addresses follows:

  • SELECT REQUEST_ID, JOB, PARTY_NAME, PRINT_ADDRESS, OUTCOME_CODE FROM APPS.JTF_FM_PROCESSED_V;

To isolate print-related records for a specific request:

  • SELECT PARTY_NAME, PRINT_ADDRESS, EMAIL_STATUS, OUTCOME_CODE FROM APPS.JTF_FM_PROCESSED_V WHERE REQUEST_ID = :p_request_id ORDER BY JOB;

To inspect failed or unresolved outcomes across channels:

  • SELECT PK_ID, PARTY_ID, EMAIL_ADDRESS, FAX_ADDRESS, PRINT_ADDRESS FROM APPS.JTF_FM_PROCESSED_V WHERE OUTCOME_CODE IS NULL OR OUTCOME_CODE NOT IN ('SUCCESS');

Because the view is unaggregated and lightly structured, it performs well for filtered reporting driven by REQUEST_ID. For set-based integration, join PK_ID back to request-level metadata when correlating a job to its originating process.