Results for “content_name”

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

Overview

JTF_FM_CONTENT_HISTORY is a CRM Foundation (JTF) table that stores historical fulfillment content records generated by the Oracle E-Business Suite fulfillment management subsystem. Its documented description in ETRM is simply "This table stores the fulfillment content history," and it holds 24 columns in the JTF schema. The table has a composite primary key, JTF_FM_CONTENT_HISTORY_PK, defined over BATCH_NUMBER, CONTENT_NUMBER, HIST_REQ_ID, and SUBMIT_DT_TM.

Under the heuristic Data Vault classification derived from its foreign key structure, the object leans toward a satellite. This is a modeling suggestion rather than a physical design statement: the primary key columns act as a composite parent reference, HIST_REQ_ID points outward to the fulfillment request history, and the remaining descriptive columns represent transactional attributes about the content delivered at a particular point in time — the classic profile of an attribute-bearing satellite attached to a request-history hub.

Key Information Stored

The most operationally significant columns are those that identify, categorize, and describe each historical content record.

• BATCH_NUMBER, CONTENT_NUMBER, SUBMIT_DT_TM, and HIST_REQ_ID together form the surrogate composite primary key, JTF_FM_CONTENT_HISTORY_PK. HIST_REQ_ID is also the foreign key to JTF_FM_REQUEST_HISTORY_ALL, so it links each row to its parent fulfillment request.
• CONTENT_TYPE, CONTENT_NAME, and DOCUMENT_TYPE classify the delivered content and are strong business-key candidates for identifying a record in reporting contexts.
• MES_DOC_ID references JTF_FM_QUERY_MES and ties the row to the message/query document it originated from.
• PARTY_ID and PARTY_NAME identify the customer or trading partner to whom the content pertains.
• DESTINATION_ADDR captures the delivery address associated with the content.
• QUANTITY records the amount of content delivered or requested.
• OUTCOME_CODE and OUTCOME_DESC record the result of the fulfillment attempt (for example success or failure), which is essential for reconciliation reporting.
• OUTPUT_ID points to the generated output artifact, and USER_NOTES holds free-text remarks entered by users.
• Audit and versioning columns include LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER (used for optimistic locking). F_DELETEDFLAG marks logical deletions.
• SECURITY_GROUP_ID is a foreign key to FND_SECURITY_GROUPS and enforces data security across the row.

Common Use Cases and Queries

Typical scenarios include auditing fulfillment history for a given batch, tracing which content was delivered to a party, and reconciling outcomes by code. Sample query patterns follow.

• History for a specific request:
  SELECT BATCH_NUMBER, CONTENT_NUMBER, CONTENT_NAME, OUTCOME_CODE, SUBMIT_DT_TM FROM JTF.JTF_FM_CONTENT_HISTORY WHERE HIST_REQ_ID = :p_req_id AND F_DELETEDFLAG = 'N';
• Delivery outcomes by party over a period:
  SELECT PARTY_ID, PARTY_NAME, OUTCOME_CODE, COUNT(*) FROM JTF.JTF_FM_CONTENT_HISTORY WHERE SUBMIT_DT_TM BETWEEN :from_dt AND :to_dt GROUP BY PARTY_ID, PARTY_NAME, OUTCOME_CODE;
• Content joined to parent request:
  SELECT c.CONTENT_NAME, c.QUANTITY, r.* FROM JTF.JTF_FM_CONTENT_HISTORY c JOIN JTF.JTF_FM_REQUEST_HISTORY_ALL r ON c.HIST_REQ_ID = r.HIST_REQ_ID;

Related Objects

• JTF_FM_REQUEST_HISTORY_ALL — parent request history; joined on HIST_REQ_ID.
• JTF_FM_QUERY_MES — source message/query document; joined on MES_DOC_ID.
• FND_SECURITY_GROUPS — data security group; joined on SECURITY_GROUP_ID.
• FND_USER — implicitly referenced by CREATED_BY and LAST_UPDATED_BY for audit reporting.
• JTF_FM_CONTENT and related fulfillment content definition objects supply the content metadata categorized by CONTENT_TYPE and DOCUMENT_TYPE.

These relationships make JTF_FM_CONTENT_HISTORY the historical reference point for CRM fulfillment content tracking in EBS 12.1.1 and 12.2.2.