Results for “content_source”

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

Overview

JTF.JTF_FM_REQUEST_CONTENTS is a table within the CRM Foundation (JTF) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. As its description states, it holds details on the contents within a request. In the Oracle CRM Foundation architecture, "FM" denotes the Foundation Manager subsystem, which supports structured request handling — a generic container for capturing requests and the items (contents) associated with them. This table therefore acts as the detail or line-level store that records what each request contains, including descriptive attributes, media, quantities, and outcomes.

From a data-modeling perspective, the mined Data Vault classification is standalone. This heuristic suggests the table can be treated as an independent structure rather than as a strict hub, link, or satellite. In practice, the composite primary key (REQUEST_ID, CONTENT_NUMBER) makes it behave like a dependent detail entity, so it is best modeled as a satellite-like detail table keyed to its parent request.

Key Information Stored

The table carries 18 documented columns. The most significant are:

• REQUEST_ID — the parent request identifier; part of the composite primary key JFUFRQS_PK.
• CONTENT_NUMBER — the line or sequence number within a request; the second component of the composite primary key.
• CONTENT_ID — the surrogate/content identifier for the item.
• CONTENT_NAME — the descriptive name of the content.
• CONTENT_TYPE and DOCUMENT_TYPE — classification attributes distinguishing the nature of the content.
• BODY — the actual content payload or textual body.
• USER_NOTES — free-form notes entered by users.
• QUANTITY — numeric quantity associated with the content line.
• OUTCOME_CODE — the result or disposition code for the content.
• MEDIA_TYPE and CONTENT_SOURCE — describe the media format and origin of the content.
• FND_FILE_ID — a foreign reference into the Oracle Application Object Library file repository, linking content to an uploaded or stored file.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns.

The surrogate primary key is JFUFRQS_PK, defined over REQUEST_ID and CONTENT_NUMBER. The business-key candidates are likewise these two columns, since the pair uniquely identifies a content line within a request.

Common Use Cases and Queries

Typical uses include reporting on the items attached to CRM Foundation requests, auditing content outcomes, and tracing stored files via FND_FILE_ID. A representative query lists the contents of a given request:

• SELECT content_number, content_name, content_type, quantity, outcome_code FROM jtf_fm_request_contents WHERE request_id = :request_id ORDER BY content_number;
• Joining to the file repository: SELECT r.content_name, r.media_type, f.file_name FROM jtf_fm_request_contents r, fnd_lobs f WHERE r.fnd_file_id = f.file_id;
• Aggregating outcomes per request: SELECT request_id, outcome_code, COUNT(*) FROM jtf_fm_request_contents GROUP BY request_id, outcome_code;

These patterns support operational dashboards, content-completeness checks, and audit extracts.

Related Objects

Because the table is classified as standalone, no FK relationships were mined; relationships are inferred from naming and the shared request header. The most significant related objects are the request header table (joined on REQUEST_ID), and FND_LOBS / FND_FILE_ID for stored files. Standard audit references link to FND_USER via CREATED_BY and LAST_UPDATED_BY. Reporting typically joins to the parent request object on REQUEST_ID and to FND_LOBS on FND_FILE_ID.