Search Results subject_description




Overview
Explore in AI Chat

Overview

The view APPS.CS_SR_LINK_VALID_OBJ_V is a reporting and integration construct in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes the configured valid subject-object combinations for service request (SR) links. Service request links provide the mechanism by which one service request can be associated with another business entity, such as an item, a customer, a contact, or another service request. The base configuration table CS_SR_LINK_VALID_OBJ stores only internal identifiers: link type, subject type, and object type are all recorded as coded values. The view resolves those codes into human-readable names and descriptions by joining to the link type and object definition views, producing a denormalized, presentation-ready result set.

In keeping with EBS coding conventions, the view is owned by the APPS schema and is intended to be consumed by Oracle Forms, concurrent programs, OAF pages, and custom reporting layers. It is not maintained directly; all data changes occur in the underlying synonym/table, with the view reflecting the current state at query time.

Underlying Base Objects

The view is defined over three documented base objects. CS_SR_LINK_VALID_OBJ, exposed as a synonym, is the driving table and supplies the primary key column LINK_VALID_OBJ_ID, the subject and object type codes, the date ranges, and the standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, APPLICATION_ID, SEEDED_FLAG, and SECURITY_GROUP_ID). CS_SR_LINK_TYPES_VL is a translated link-type view supplying the link type name and description. JTF_OBJECTS_VL is referenced twice, once as the subject side (aliased C via SUBJECT_TYPE = C.OBJECT_CODE) and once as the object side (aliased D via OBJECT_TYPE = D.OBJECT_CODE), supplying names and descriptions for both roles. Because JTF_OBJECTS_VL and CS_SR_LINK_TYPES_VL are _VL views, the joins automatically respect the run-time language of the session.

Key Columns

  • LINK_VALID_OBJ_ID — Surrogate primary key of the configuration row.
  • LINK_TYPE_ID, NAME, DESCRIPTION — Identifier, name, and description of the service request link type.
  • SUBJECT_TYPE, SUBJECT_NAME, SUBJECT_DESCRIPTION — The coded subject type plus its resolved object name and description (the SUBJECT_DESCRIPTION is the column of interest when searching on subject_description).
  • OBJECT_TYPE, OBJECT_NAME, OBJECT_DESCRIPTION — The coded object type plus its resolved name and description.
  • START_DATE_ACTIVE, END_DATE_ACTIVE — Effective date range governing when the valid combination is usable.
  • SEEDED_FLAG — Indicates whether the row is Oracle-seeded (Y) or customer-defined (N).
  • APPLICATION_ID, SECURITY_GROUP_ID, and the audit columns — Standard EBS ownership and multi-org/audit metadata.

Common Use Cases and Queries

Typical scenarios include validating whether a given link type permits a subject-object pairing, populating LOVs for link creation, and reporting on active link configuration by date. A representative query, filtering to non-expired, non-seeded configurations and searching on the subject description, is:

SELECT link_valid_obj_id,
       name          link_type_name,
       subject_type,
       subject_name,
       subject_description,
       object_type,
       object_name,
       object_description
FROM   apps.cs_sr_link_valid_obj_v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE))
                          AND NVL(end_date_active, TRUNC(SYSDATE))
AND    UPPER(subject_description) LIKE UPPER('%subject_description%');

The view is read-only from the reporting perspective; maintenance of links is performed through the corresponding EBS application. When extending reports, analysts should join back to CS_SR_LINK_VALID_OBJ on LINK_VALID_OBJ_ID if additional base columns are required, since the view projects only the documented set of columns.