Search Results jtf_fm_request_outcome_code

Overview

CS_SR_FULFIL_STATUS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Service (CS) product family and is documented as a status reporting object for fulfillment requests. For a given source object and source object identifier, the view returns the current status of a submitted fulfillment request, together with the request identifier, an outcome description, and the submission timestamp.

The view is primarily consumed by reporting, extensions, and integration layer components that need to expose fulfillment progress without navigating the underlying JTF foundation schema objects directly. Because it joins the interaction history framework to the fulfillment request history, it abstracts the relationship between a service request activity and the fulfillment job that was triggered from it. The object carries a VALID status in the ETRM metadata and is documented in the 12.2.2 repository.

Underlying Base Objects

The view is defined over three documented base objects, joined in the view text:

• JTF_IH_ACTIVITIES_V — supplies the source context. Its columns DOC_REF, DOC_ID, and DOC_SOURCE_OBJECT_NAME are projected as SOURCE_CODE, SOURCE_ID, and REQUEST_ID.
• JTF_FM_REQUEST_HISTORY — supplies the fulfillment request history rows, including HIST_REQ_ID, OUTCOME_CODE, OUTCOME_DESC, and SUBMIT_DT_TM.
• FND_LOOKUP_VALUES — supplies the lookup translation for the outcome code via MEANING, filtered on LOOKUP_TYPE = 'JTF_FM_REQUEST_OUTCOME_CODE', VIEW_APPLICATION_ID = 690, and the user's language.
• FND_GLOBAL — a package referenced through FND_GLOBAL.LOOKUP_SECURITY_GROUP, used to enforce lookup security when resolving the outcome meaning.

The join condition links JTF_IH_ACTIVITIES_V.DOC_SOURCE_OBJECT_NAME to TO_CHAR(JTF_FM_REQUEST_HISTORY.HIST_REQ_ID), and the outcome code to the lookup code. Language and security group predicates restrict the lookup row returned.

Key Columns

• SOURCE_CODE — the document reference of the interaction activity (INTERACT.DOC_REF).
• SOURCE_ID — the document identifier of the interaction activity (INTERACT.DOC_ID). Together with SOURCE_CODE it identifies the originating source object.
• REQUEST_ID — the fulfillment request identifier, sourced from DOC_SOURCE_OBJECT_NAME and matched to HIST_REQ_ID.
• REQUEST_STATUS — the translated outcome meaning from FND_LOOKUP_VALUES.MEANING. This is the column historically searched as "request_status" and is the principal status indicator returned by the view.
• DESCRIPTION — the outcome description (FUL_REQ.OUTCOME_DESC), providing human-readable detail about the result.
• SUBMIT_DATE — the fulfillment request submission timestamp (FUL_REQ.SUBMIT_DT_TM).

Common Use Cases and Queries

The most common use case is retrieving the current status of a fulfillment request generated from a service request or another source object. A typical query filters on the source object and identifier, then selects the status column:

• SELECT request_id, request_status, description, submit_date FROM cs_sr_fulfil_status_v WHERE source_code = :p_source_code AND source_id = :p_source_id;
• SELECT request_status, COUNT(*) FROM cs_sr_fulfil_status_v GROUP BY request_status; — for status distribution reporting.
• SELECT * FROM cs_sr_fulfil_status_v WHERE request_id = :p_request_id; — to inspect a single fulfillment request.

Because REQUEST_STATUS is resolved through a lookup with language and security group predicates, callers should ensure the session language is initialized (USERENV('LANG')) and that the invoking user has access to the JTF_FM_REQUEST_OUTCOME_CODE lookup values. The view is a suitable foundation for custom concurrent programs, OAF/ADF pages, and BI Publisher reports that surface fulfillment status to service agents or external systems, and it should be treated as read-only in all integration code.