Search Results remarketer_name




Overview
Explore in AI Chat

Overview

OKL_AM_RMK_ASSGN_UV is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as OKL.OKL_AM_RMK_ASSGN_UV and documented for ETRM 12.1.1 and 12.2.2. It belongs to the Oracle Lease and Finance Management (OKL) module, specifically the asset management and remarketing functional area, and exposes the assignment relationship between remarketing teams and item catalog categories at the operating unit level. The view is classified as a supplementary view whose stated purpose is to simplify Oracle Forms coding; Oracle explicitly warns that the view should not be queried or altered directly for data maintenance because its definition may change substantially across minor or major releases. Its practical value lies in read-only reporting: the column RMR_ID carries the remarketer identifier, while REMARKETER_NAME (VARCHAR2(30), commented as "Team Name") resolves the human-readable name that users search for when they look up "remarketer_name."

Underlying Base Objects

The view is defined over a small, stable set of documented dependencies: OKL_AM_REMARKET_TEAMS_UV, OKL_AM_ITEM_CATEGORIES_UV, OKL_DF_CTGY_RMK_TMS, FA_LOCATIONS, and the FND_GLOBAL package. OKL_AM_REMARKET_TEAMS_UV supplies the remarketer/team identity and name, while OKL_AM_ITEM_CATEGORIES_UV and the synonym OKL_DF_CTGY_RMK_TMS supply the item catalog category (FA_CATEGORY) and its description, effectively implementing the category-to-remarketing-team mapping. FA_LOCATIONS contributes the FA_LOCATION column through the ILN_ID link, and FND_GLOBAL provides the session context (notably ORG_ID) used to restrict rows to the current operating unit. The view is a denormalized join of these sources: it does not store data itself, and no database object references it, confirming its role as a terminal, form-facing construct rather than a base entity relied upon by other code.

Key Columns

  • ROW_ID — the ROWID of the underlying row, used as a row identifier by the form.
  • ID — primary key column of the view.
  • OBJECT_VERSION_NUMBER — locking column used during updates to detect concurrent modification.
  • RMR_ID — foreign key to the remarketer (remarketing team) record.
  • REMARKETER_NAME — VARCHAR2(30), commented "Team Name"; the searchable display name of the remarketer.
  • ICO_ID — identifier for the item catalog category.
  • FA_CATEGORY — VARCHAR2(240), item catalog group description.
  • ILN_ID and FA_LOCATION — location identifier and its VARCHAR2(123) description from FA_LOCATIONS.
  • DATE_EFFECTIVE_FROM / DATE_EFFECTIVE_TO — the effective date range of the assignment.
  • ORG_ID — operating unit identifier, used for multi-org security.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage is read-only lookup and reporting: identifying which remarketing team is assigned to a given category in the current operating unit, and surfacing the remarketer name for display or extract. A representative query follows.

  • List remarketer assignments filtered by name: SELECT rmr_id, remarketer_name, fa_category, fa_location, date_effective_from, date_effective_to FROM apps.okl_am_rmk_assgn_uv WHERE UPPER(remarketer_name) LIKE UPPER(:p_name) AND org_id = :p_org_id;
  • Retrieve the effective assignment for a category as of a date: SELECT * FROM apps.okl_am_rmk_assgn_uv WHERE ico_id = :p_ico_id AND :p_date BETWEEN date_effective_from AND NVL(date_effective_to, :p_date);
  • Extract assignment data for integration or audit, joined to the remarketing team identifier: SELECT rmr_id, remarketer_name, fa_category, org_id FROM apps.okl_am_rmk_assgn_uv ORDER BY remarketer_name;

Because the view is a Forms convenience construct, queries should be limited to reporting and integration extracts; direct DML against the view is not supported.