Search Results fa_category

Overview

OKL_AM_RMK_ASSGN_UV is an Oracle E-Business Suite view owned by the APPS schema within the OKL (Lease and Finance Management) product family. It presents remarketer-to-category assignment data, exposing the effective-dated relationship between a remarketing team member, an item category, and an inventory location. The view is a reporting and integration artifact, intended to flatten normalized assignment records from the underlying transaction table OKL_DF_CTGY_RMK_TMS and resolve the associated IDs into human-readable descriptive values. The "_UV" suffix denotes a user-facing validation or lookup view, which is the standard ETRM convention for views intended to populate list of values (LOVs), descriptive flexfield references, and operational reports rather than to serve as a transactional base object.

The view is documented as VALID and is not registered as a multi-org secured database view; organization context is instead carried explicitly through the ORG_ID column, allowing callers to filter by operating unit when needed. This makes the object suitable for both single-org queries and cross-org administrative reporting, provided the querying responsibility has the appropriate data access.

Underlying Base Objects

The view text joins four documented objects:

• OKL_DF_CTGY_RMK_TMS (SYNONYM) — the driving table, aliased DCTB, holding the remarketer/category/location assignment rows, including effective dates and WHO audit columns.
• OKL_AM_REMARKET_TEAMS_UV (VIEW) — aliased WFU, joined on DCTB.RMR_ID = WFU.ORIG_SYSTEM_ID to resolve the remarketer's display name.
• OKL_AM_ITEM_CATEGORIES_UV (VIEW) — aliased FAC, joined on DCTB.ICO_ID = FAC.CATEGORY_ID to resolve the category description. This is the object most directly associated with the user's "fa_category" search term.
• FA_LOCATIONS (SYNONYM) — aliased FAL, joined on DCTB.ILN_ID = FAL.LOCATION_ID with an outer-join (+) marker, meaning assignments without a valid location still appear, with the location segments null.

The Metadata repository additionally records a reference to the FND_GLOBAL package, which supplies session context such as the current organization, user, and responsibility.

Key Columns

• ROW_ID / ID / OBJECT_VERSION_NUMBER — the physical row identifier, the surrogate primary key, and the optimistic-locking version used by the underlying ADF/BC4J entity.
• RMR_ID / REMARKETER_NAME — the remarketer identifier and the resolved display name used in LOVs and reports.
• ICO_ID / FA_CATEGORY — the item category identifier and its description. FA_CATEGORY answers the common "fa_category" lookup, providing the readable category label rather than the numeric ICO_ID.
• ILN_ID / FA_LOCATION — the location identifier and a concatenated four-segment location string (SEGMENT1-SEGMENT2-SEGMENT3-SEGMENT4) built from FA_LOCATIONS.
• DATE_EFFECTIVE_FROM / DATE_EFFECTIVE_TO — the validity window of the assignment; DATE_EFFECTIVE_TO is typically null for current, open-ended rows.
• ORG_ID and WHO columns — operating unit and standard CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN audit attributes.

Common Use Cases and Queries

Typical scenarios include validating which remarketers are authorized for a category at a given date, driving remarketing team LOVs, and feeding downstream asset remarketing reports. The user's "fa_category" search suggests retrieving the readable category for a set of assignments:

• List assignments effective on a date: SELECT remarketer_name, fa_category, fa_location, date_effective_from, date_effective_to FROM okl_am_rmk_assgn_uv WHERE TRUNC(SYSDATE) BETWEEN date_effective_from AND NVL(date_effective_to, TRUNC(SYSDATE)+1) AND org_id = :p_org_id;
• Resolve a category for a remarketer: SELECT fa_category FROM okl_am_rmk_assgn_uv WHERE rmr_id = :p_rmr_id;
• LOV lookup: SELECT DISTINCT fa_category FROM okl_am_rmk_assgn_uv WHERE org_id = :p_org_id ORDER BY 1;

Because the view joins validation views and FA_LOCATIONS, callers should expect it to be read-only and to perform best with filters on org_id and the effective-date columns.