Results for “territory_description”

18 results




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

Overview

OKL_SUBSIDY_CRITERIA_UV is a user interface view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL – Leasing and Finance Management product family. It is defined as the "User interface view for subsidy application criteria page," meaning it is the presentation-layer object that the Subsidy Criteria maintenance screen in the leasing application queries to render its results block. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2, and it is not itself a transactional table — all data is inherited from the underlying base tables it joins. Because it denormalizes descriptive attributes such as item names, organization names, territory descriptions, and lookup meanings onto the criteria rows, it is equally useful for reporting and integration work as it is for form display. Report developers, OAF/Forms personalization specialists, and integration architects query it directly to avoid re-deriving the same joins used by the application's subsidy setup UI.

Underlying Base Objects

According to the documented view metadata in ETRM 12.2.2, OKL_SUBSIDY_CRITERIA_UV is defined over the following referenced objects:

Key Columns

  • ID / SUBSIDY_ID / SUBSIDY_NAME / SUBSIDY_SHORT_DESCRIPTION — primary key and the concatenated subsidy descriptors.
  • INVENTORY_ITEM_ID / INVENTORY_ITEM_NAME / INVENTORY_ITEM_CODE — item reference; the name and flexfield concatenation come from MTL_SYSTEM_ITEMS_B_KFV.
  • INVENTORY_ORG_ID / INVENTORY_ORG_NAME / INVENTORY_ORG_CODE — the qualifying inventory organization.
  • CREDIT_CLASSIFICATION_CODE / CREDIT_CLASS_MEANING — the credit class stored on the criterion and its decoded lookup meaning.
  • SALES_TERRITORY_ID — the territory key; the adjacent flexfield expression concatenates RA_TERRITORIES SEGMENT1 through SEGMENT16 to produce the territory description rendered on the subsidy criteria page. This is the column set users associate with the search term "territory_description."
  • DISPLAY_SEQUENCE — the ordering sequence applied when criteria are presented in the UI.
  • OBJECT_VERSION_NUMBER — optimistic locking token carried from the base table.

Common Use Cases and Queries

Typical uses include auditing which territories are attached to a subsidy, reporting item/organization eligibility by subsidy, and integration extracts that require decoded descriptions rather than raw IDs. A representative query identifying subsidy criteria by territory description is:

  • SELECT subsidy_name, inventory_item_code, inventory_org_code, sales_territory_id FROM okl_subsidy_criteria_uv WHERE subsidy_id = :p_subsidy_id ORDER BY display_sequence;
  • Filter by territory flexfield: ... WHERE sales_territory_id IN (SELECT territory_id FROM ra_territories WHERE segment1 = :p_region);
  • Join items to reporting extracts: SELECT u.subsidy_name, u.inventory_item_name, u.inventory_org_name, u.credit_class_meaning FROM okl_subsidy_criteria_uv u WHERE u.inventory_item_id = :p_item_id;
  • Exclude secured organizations automatically, since HR_SECURITY predicates are already embedded in the view definition.

Consumers should query the view rather than reassembling the joins, ensuring consistent territory concatenation, lookup decoding, and security behavior across 12.1.1 and 12.2.2.