Search Results request_problem_code

Overview

The JTF_RS_PROBLEM_CODES_V view is a CRM Foundation (JTF) database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of valid problem codes for which resource skills can be assigned, serving as a controlled reference list that links service request classification to the skills framework used by field service, tele-service, and depot repair operations. Rather than maintaining a dedicated problem-code table, the view derives its content dynamically from the FND Lookups infrastructure, filtering a single lookup type so that consumers see only the problem codes relevant to resource skill assignment. Because it is a view and not a table, it carries no storage of its own; its rows always reflect the current state of the underlying lookup values, which means any addition, disablement, or date-based activation of a problem code is immediately visible through the view without further data maintenance.

Underlying Base Objects

The view is defined over a single documented base object, the FND_LOOKUP_VALUES synonym, which resolves to the FND_LOOKUP_VALUES table in the Application Object Library. The view text applies several predicate filters to that source. It restricts rows to LOOKUP_TYPE = 'REQUEST_PROBLEM_CODE', constrains the owning application through VIEW_APPLICATION_ID = 170, and enforces language and security-group conditions. The language filter uses LV.LANGUAGE = USERENV('LANG') so that meanings and descriptions are returned in the session's language. The security-group predicate compares the lookup's SECURITY_GROUP_ID against a decoded value extracted from the client information string, resolving null or blank positions to zero and taking the greatest of zero and the parsed number. Together these predicates ensure that only effective, language-appropriate, and security-accessible problem codes are surfaced.

Key Columns

• PROBLEM_CODE — Sourced from LOOKUP_CODE; the unique identifier used programmatically when assigning or referencing a resource skill problem code.
• PROBLEM_NAME — Sourced from MEANING; the user-facing display name of the problem code shown in forms and reports.
• DESCRIPTION — The long description of the problem code, useful for explanatory context in reporting.
• ENABLED_FLAG — Indicates whether the code is currently active (Y) or disabled (N); disabled codes should generally be excluded from selection lists.
• START_DATE_ACTIVE — The date from which the code becomes usable.
• END_DATE_ACTIVE — The date after which the code is no longer usable; a null value indicates no expiry.

Common Use Cases and Queries

Typical scenarios include validating that a resource skill is being associated with a live problem code, building value lists for service request entry, and reporting on the active problem-code catalogue. The following query returns all currently enabled codes:

SELECT problem_code, problem_name, description
FROM   apps.jtf_rs_problem_codes_v
WHERE  enabled_flag = 'Y'
ORDER  BY problem_name;

A second pattern filters by active date range to confirm a code is valid as of the current date:

SELECT problem_code, problem_name
FROM   apps.jtf_rs_problem_codes_v
WHERE  enabled_flag = 'Y'
AND    (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND    (end_date_active   IS NULL OR end_date_active   >= SYSDATE);

Because the view is the authoritative source for assignable problem codes, integrations and reports should query it rather than reading FND_LOOKUP_VALUES directly, ensuring the correct lookup type, application, language, and security-group filters are consistently applied.