Results for “edw_geog_postcode_ltc_iv”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view EDW_GEOG_POSTCODE_LTC_IV is a predefined Oracle E-Business Suite database object shipped with the BIS (Business Intelligence System) product family, the application module historically associated with the Enterprise Data Warehouse and analytical reporting layers of EBS. The suffix _IV denotes an "interface view"—an object exposed primarily for extraction, staging, or downstream integration rather than for direct transactional use within the EBS operational forms.
In the context of EBS 12.1.1 and 12.2.2, this view presents postal code (postcode) geography data together with its associated state/region foreign key references. Its role is to provide a simplified, extraction-friendly projection of the underlying geography postcode entity for reporting and data warehouse population. Notably, the ETRM documentation records the implementation status as "Not implemented in this database," indicating that the view definition is documented but may not be instantiated in every environment or release.
Underlying Base Objects
Per the documented view text, EDW_GEOG_POSTCODE_LTC_IV is defined over a single base object: EDW_GEOG_POSTCODE_LTC. The view is a straightforward SELECT ... FROM projection with no joins, unions, or aggregate functions, meaning every row and column maps one-to-one to the base object, with the sole addition of a literal OPERATION_CODE column.
The ETRM metadata lists no other referenced base objects, so the lineage terminates at EDW_GEOG_POSTCODE_LTC, which itself belongs to the EDW geography (GEOG) collection of tables. Because the view surface is flat and non-transforming, it inherits the refresh cadence, partitioning, and indexing characteristics of the underlying _LTC table.
Key Columns
ROW_ID— ExposesROWIDfrom the base table, providing a physical row locator useful for de-duplication or precise row addressing.POSTCODE_PK/POSTCODE_PK_KEY— Primary key and surrogate key identifiers for the postcode record.STATE_REGION_FK/STATE_REGION_FK_KEY— Foreign key references linking the postcode to its state or region, enabling geographic hierarchy navigation.NAME— The descriptive name of the postcode geography entity.POSTCODE_DP— The postcode data point value (the actual postal code string or code value).INSTANCE— Identifies the source instance or organizational context of the record.CREATION_DATE/LAST_UPDATE_DATE— Standard audit columns capturing row creation and most recent modification timestamps.USER_ATTRIBUTE1throughUSER_ATTRIBUTE5— Descriptive flexfield-style attribute columns reserved for customer-specific or implementation-specific extension data.OPERATION_CODE— A literal space character (' ') emitted by the view, typically used to signal a default operation code in change-data-capture or interface staging pipelines.
Common Use Cases and Queries
The view is normally consumed by ETL processes, BI extracts, and integration interfaces that require postcode-to-region mappings. For example, a query resolving a searched address such as "621 North Stuart Street, Essex, MD" would join this view to a region reference to confirm the postcode's state assignment.
Typical usage includes extracting all postcodes for a given region, filtering by name, or reconciling postcode reference data between the EDW and operational tables. A representative query follows:
SELECT postcode_pk,
name,
postcode_dp,
state_region_fk,
creation_date,
last_update_date
FROM edw_geog_postcode_ltc_iv
WHERE state_region_fk_key = :p_region_key
ORDER BY name;
Because the view carries no transformation logic, it is interchangeable with direct queries against EDW_GEOG_POSTCODE_LTC, but the added OPERATION_CODE literal makes it convenient for interface staging and change-detection routines. Administrators should verify whether the view is instantiated in the target 12.1.1 or 12.2.2 environment, since ETRM documents it as not implemented in the reference database.
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1