Results for “jtf_locations_b”

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

Overview

OKX_STATES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product. Its documented purpose is to expose information about geographical areas — states, provinces, counties, and comparable administrative divisions — in a denormalized, integration-friendly form. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2 and is defined over the Oracle Territory Manager / JTF location foundation tables rather than over any OKX-owned table.

The object is significant because Contract Integration components require a consistent, language-aware lookup of location areas when resolving party, contract, and territory addresses. Although the user search term was jtf_locations_b, the actual documented base of OKX_STATES_V is JTF_LOC_AREAS_B and its translation table JTF_LOC_AREAS_TL; JTF_LOCATIONS_B is the parent location table in the same JTF location model and is frequently joined alongside this view for address-level reporting.

Underlying Base Objects

The ETRM 12.2.2 metadata records two referenced base objects, both exposed to APPS as synonyms:

• JTF_LOC_AREAS_B — the base (non-translated) location area table, aliased JLA in the view text. It supplies the primary key LOCATION_AREA_ID, the hierarchical PARENT_LOCATION_AREA_ID, ORIG_SYSTEM_ID and ORIG_SYSTEM_REF, LOCATION_TYPE_CODE, LOCATION_AREA_CODE, SECURITY_GROUP_ID, and the START_DATE_ACTIVE / END_DATE_ACTIVE date range.
• JTF_LOC_AREAS_TL — the translation table, aliased TL. It supplies LOCATION_AREA_NAME and LOCATION_AREA_DESCRIPTION filtered by TL.LANGUAGE = USERENV('LANG'), so the view returns names in the session language.

The join condition is TL.LOCATION_AREA_ID = JLA.LOCATION_AREA_ID, an inner join that returns only location areas having a translation row in the current language.

Key Columns

• ID1 / ID2 — integration surrogate keys; ID1 carries LOCATION_AREA_ID and ID2 is the literal '#', a placeholder required by the OKX integration key convention.
• NAME and DESCRIPTION — the translated location area name and description from JTF_LOC_AREAS_TL.
• LOCATION_AREA_ID — primary identifier of the geographical area.
• ORIG_SYSTEM_ID / ORIG_SYSTEM_REF — identifies the source system and reference from which the area record originated.
• LOCATION_TYPE_CODE / LOCATION_AREA_CODE — classify the area (for example, state or province) and provide the short code.
• PARENT_LOCATION_AREA_ID — self-referencing parent, enabling country-to-state hierarchies.
• SECURITY_GROUP_ID — supports multi-tenant / operating unit style data segregation.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the area record.
• STATUS — derived at runtime via nested DECODE/SIGN logic against TRUNC(SYSDATE): 'A' for active, 'I' for inactive when the current date precedes START_DATE_ACTIVE or exceeds END_DATE_ACTIVE.
• PRIMARY_UOM_CODE — hard-coded NULL, present only to satisfy the OKX integration column contract.

Common Use Cases and Queries

Typical uses include populating state/province lists of values in contracts integration flows, resolving geographic hierarchies for territory and address validation, and feeding downstream reporting extracts that require a language-sensitive area name.

List active states in the session language:

• SELECT location_area_id, name, location_area_code FROM okx_states_v WHERE status = 'A' ORDER BY name;

Retrieve children of a given parent area:

• SELECT location_area_id, name FROM okx_states_v WHERE parent_location_area_id = :p_parent_id AND status = 'A';

Resolve the area for a party site by joining the JTF location model:

• SELECT s.name FROM okx_states_v s, jtf_locations_b l WHERE l.location_area_id = s.location_area_id AND l.location_id = :p_location_id;

Because the view is a simple two-table join with no aggregation, it is generally safe to query directly; for large extracts, filter on STATUS or LOCATION_TYPE_CODE to limit rows and avoid returning inactive areas.