Results for “team_number”

50+ results




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

Overview

OKL_AM_REMARKET_TEAMS_UV is a read-only Oracle EBS view owned by the APPS schema in the OKL (Lease and Finance Management) product. It exposes remarketing teams — groups of resources assigned the REMARKETER role — in a denormalized, presentation-friendly format suitable for LOVs, reporting, and integration. The view joins team header data to role-relation data so that both team-level attributes (name, number, description, email) and role-level attributes (RESOURCE_TYPE, ROLE_CODE) are returned in a single row per qualifying team. The ROLE_CODE column is a primary filter target for users searching this view, since it identifies the team classification and is hard-coded to REMARKETER in the defining query. The suffix _UV denotes a user-facing validation view, and the object is documented as VALID in ETRM 12.2.2 and applicable to 12.1.1 / 12.2.2.

Underlying Base Objects

The view is defined over three documented base objects:

  • JTF_RS_TEAMS_VL — the teams view (alias T), supplying team identity and descriptive attributes. Its date-effective columns (START_DATE_ACTIVE, END_DATE_ACTIVE) are bracketed against SYSDATE with NVL defaults so that open-ended teams remain visible.
  • JTF_RS_ROLE_RELATIONS_VL — the role-to-resource relation view (alias JTFR), supplying the role assignment. The join condition ties JTFR.ROLE_RESOURCE_ID to T.TEAM_ID with ROLE_RESOURCE_TYPE = 'RS_TEAM' and ROLE_CODE = 'REMARKETER'.
  • FND_GLOBAL — the standard EBS package referenced for session context (responsibility, user, application), typically invoked at runtime rather than joined in the SQL text.

Because both base objects are themselves views over the JTF Resource Manager schema, the effective dependency chain runs back to the JTF_RS_TEAMS and JTF_RS_ROLE_RELATIONS tables. Filtering on ROLE_CODE is applied inside the view, so the result set is inherently scoped to remarketing teams.

Key Columns

  • DISPLAY_NAME — the team name, exposed from T.TEAM_NAME; used as the LOV display value.
  • ORIG_SYSTEM_ID — the team identifier (T.TEAM_ID), used as the LOV return value and as a foreign key to teams.
  • ROLE_CODE — the role classification (JTFR.ROLE_CODE), always REMARKETER given the view's filter; searched by users to confirm remarketer scoping.
  • RESOURCE_TYPE — the role resource type (JTFR.ROLE_RESOURCE_TYPE), always RS_TEAM.
  • TEAM_DESC, TEAM_NUMBER, EMAIL_ADDRESS — descriptive team attributes from JTF_RS_TEAMS_VL.

Common Use Cases and Queries

Typical uses include restriction-of-lists for remarketing assignment, and reporting on remarketing team rosters. A user searching role_code is usually validating that a team carries the REMARKETER role before assignment.

SELECT display_name, orig_system_id, role_code
FROM   okl_am_remarket_teams_uv
WHERE  role_code = 'REMARKETER';

Because the view hard-codes the role filter, the WHERE clause above is redundant but is often retained in integration code for explicitness. Retrieving contact information follows the same pattern:

SELECT team_number, display_name, email_address
FROM   okl_am_remarket_teams_uv
ORDER  BY display_name;

For joined reporting, expose the team LOV alongside contract remarketing activity, keying on ORIG_SYSTEM_ID. Note that the view is not date-parameterized by the caller; effective dating is applied internally, so results reflect teams active on the current SYSDATE.