Results for “geocodeco”

4 results




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

Overview

GEOCODECO is a database view registered under the Oracle E-Business Suite Receivables (AR) product family. It presents a denormalized geographic reference listing that flattens state and county information into a single queryable result set. In Oracle EBS 12.1.1 and 12.2.2, geography reference data of this type supports jurisdiction determination, tax and address validation, and location-based reporting across the Receivables modules.

The view carries no independent data storage; it is a projection over two underlying geography tables. ETRM documentation for 12.2.2 records the object with no owner value and no documented referenced base objects, and notes “Not implemented in this database” in the implementation/DBA data section. This status indicates the view is not deployed in the documented environment, which is common for geography views when the corresponding reference data set has not been installed or licensed. Consequently, the view text and column list serve as the authoritative definition of its intended structure rather than an indication of live availability.

Its practical role is as a join-friendly lookup for state and county codes. Applications or custom reports that need to resolve a state name or abbreviation to its county equivalents can query GEOCODECO directly instead of performing the two-table join themselves.

Underlying Base Objects

The view is defined over exactly two base tables:

  • LOCSTATE — supplies state-level geography attributes.
  • LOCCOUNTY — supplies county-level geography attributes.

The join condition links the two tables on the geography state identifier: LOCSTATE.LOCGEOSTATE = LOCCOUNTY.LOCGEOSTATE. This is a one-to-many relationship in which each state may map to multiple counties, so the result set contains one row per state-county combination. Because the join is an inner join, a state with no registered county rows, or a county whose state identifier does not match, will not appear in the output. Geography reference tables of this family are hierarchical by design; LOCSTATE sits above LOCCOUNTY in the geographic hierarchy.

Key Columns

The view exposes six columns, three from each base table:

  • LOCGEOSTATE — the geographic identifier for the state; the common key joining LOCSTATE and LOCCOUNTY.
  • LOCNAMESTATE — the descriptive name of the state (for example, a full state or province name).
  • LOCABBREVSTATE — the abbreviated state code, typically the standard two-character designation.
  • LOCGEOCOUNTY — the geographic identifier for the county.
  • LOCNAMECOUNTY — the descriptive name of the county.
  • LOCABBREVCOUNTY — the abbreviated county code or short name.

The column semantics follow the naming convention of the LOC* geography tables: LOCGEO* holds internal numeric or coded identifiers, LOCNAME* holds full descriptive names, and LOCABBREV* holds short display values.

Common Use Cases and Queries

Typical uses include resolving a state abbreviation to its full name and counties, populating address or jurisdiction validation lists, and driving county-level tax or reporting logic. A basic query retrieving all counties for a given state:

SELECT locnamestate, locabbrevstate, locnamecounty, locabbrevcounty
FROM   geocodeco
WHERE  locabbrevstate = 'CO'
ORDER BY locnamecounty;

To search by partial county name, useful when validating free-form location input:

SELECT locnamestate, locabbrevstate, locnamecounty
FROM   geocodeco
WHERE  locnamecounty LIKE '%Erie%';

To obtain a distinct state-level listing, aggregate the county rows:

SELECT DISTINCT locgeostate, locnamestate, locabbrevstate
FROM   geocodeco
ORDER BY locnamestate;

Because the view is documented as not implemented in the reference database, administrators should confirm its deployment with a data dictionary query against ALL_VIEWS before relying on it in concurrent programs, custom reports, or integrations. Where the view is unavailable, the equivalent result can be produced by joining LOCSTATE and LOCCOUNTY on LOCGEOSTATE directly.