Search Results jtf_fm_request_outcome_code

Overview

The APPS.CS_SR_FULFIL_STATUS_V view is a reporting and integration object within Oracle E-Business Suite, owned by the APPS schema. It exposes the fulfillment status of service requests (SRs) processed through the Oracle TeleService fulfillment engine, specifically by joining request history records against lookup-driven status meanings and interaction activity records. The view is documented and available in both EBS 12.1.1 and 12.2.2, and appears in ETRM under the view repository.

Its principal role is to present a denormalized, human-readable snapshot of fulfillment requests: for each request history row it surfaces the associated interaction source, a translated (language-dependent) request status, the outcome description, and the submission timestamp. Because the view resolves status codes through FND_LOOKUP_VALUES with a language and security-group filter, it returns locale-appropriate status text suited to end-user reporting, dashboards, and integration extracts rather than raw code values.

Underlying Base Objects

The documented referenced objects are:

• JTF_FM_REQUEST_HISTORY (VIEW) — aliased as ful_req; the core source of fulfillment request history, contributing hist_req_id, outcome_code, outcome_desc, and submit_dt_tm.
• JTF_IH_ACTIVITIES_V (VIEW) — aliased as interact; the interaction header source, contributing doc_ref, doc_id, and doc_source_object_name.
• FND_LOOKUP_VALUES (SYNONYM) — aliased as fnd; the lookup source for the translated status meaning, restricted to lookup type JTF_FM_REQUEST_OUTCOME_CODE.
• FND_GLOBAL (PACKAGE) — used indirectly through the LOOKUP_SECURITY_GROUP call that enforces lookup security on the status meaning.

The joins are textual and instruction-driven: interact.doc_source_object_name = to_char(ful_req.hist_req_id) links an interaction to its fulfillment request history; ful_req.outcome_code = fnd.lookup_code resolves the status. Because doc_source_object_name is a character column, the numeric history request ID is converted with TO_CHAR, a known performance consideration on large tables.

Key Columns

• source_code — sourced from interact.doc_ref; identifies the interaction/source document reference.
• source_id — sourced from interact.doc_id; the interaction document identifier.
• request_id — sourced from interact.doc_source_object_name; effectively the fulfillment history request ID in character form.
• request_status — sourced from fnd.meaning; the translated status text for the outcome code.
• description — sourced from ful_req.outcome_desc; the outcome narrative.
• submit_date — sourced from ful_req.submit_dt_tm; the request submission timestamp.

The view filters on LANGUAGE = USERENV('LANG'), VIEW_APPLICATION_ID = 0, the appropriate lookup security group, and the fixed lookup type, so only the current session's language and permitted values are returned.

Common Use Cases and Queries

Typical uses include service-request fulfillment tracking, agent work queues, and status extracts for downstream systems. Retrieve the status history for a specific interaction:

• SELECT request_id, request_status, description, submit_date FROM apps.cs_sr_fulfil_status_v WHERE source_id = :interaction_id ORDER BY submit_date DESC;

List counts of fulfillment outcomes over a period:

• SELECT request_status, COUNT(*) FROM apps.cs_sr_fulfil_status_v WHERE submit_date >= :start_date GROUP BY request_status;

Join back to interactions for reporting:

• SELECT v.source_code, v.request_status, v.description, v.submit_date FROM apps.cs_sr_fulfil_status_v v WHERE v.request_id = :hist_req_id;

Because the view embeds a TO_CHAR predicate, queries should be filtered on indexed interaction columns where possible. The fixed lookup type JTF_FM_REQUEST_OUTCOME_CODE may be extended with additional statuses via lookup configuration.