Search Results edw_organization_lcv

Overview

EDW_ORGANIZATION_LCV is a reporting view residing in the PER (Human Resources) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix "LCV" denotes a load or collection view associated with the Enterprise Data Warehouse (EDW) layer, a set of denormalized, read-oriented objects used to feed downstream reporting, business intelligence, and integration pipelines rather than transactional processing. The view presents a flattened, consolidated representation of organizational units — including operating units, inventory organizations, and Human Resources business groups — that are defined across the EBS enterprise structure.

Its principal role is to expose a single, stable interface over organization data so that EDW extracts, custom reports, and third-party integrations do not need to join the numerous underlying HR and inventory organization tables directly. The ETRM metadata indicates that the view is not implemented in the reference database examined, meaning it is deployed conditionally, typically only where the EDW or HR analytics components have been installed and the relevant grants and synonyms created.

Underlying Base Objects

The documented view text defines EDW_ORGANIZATION_LCV as a simple projection over EDWBV_ORGANIZATION_LCV, the EDW base view that carries the substantive join and transformation logic. EDW_ORGANIZATION_LCV selects the full column list from that base view and appends five placeholders mapped to USER_ATTRIBUTE1 through USER_ATTRIBUTE5, which are returned as NULL in the view definition. This pattern is characteristic of EDW descriptor views that reserve flexible attribute slots for customer-specific extensions without altering the base projection.

No base tables are documented directly for this view; the ETRM metadata lists no referenced base objects, confirming that the view is a thin wrapper rather than a direct join over PER_ORGANIZATION_DEFINITIONS or HR_OPERATING_UNITS. This layering allows Oracle to revise the underlying EDW business view while preserving a consistent contract for consumers of EDW_ORGANIZATION_LCV.

Key Columns

• ORGANIZATION_PK — The primary key of the organization record, the identifier most commonly used to join this view to other EDW organization-keyed facts and dimensions.
• OPERATING_UNIT_FK — Foreign key linking the organization to its parent operating unit, supporting enterprise-structure rollups.
• ORGANIZATION_DP — Descriptive flexfield context or descriptor value associated with the organization.
• NAME — The organization's descriptive name as displayed to users.
• DATE_FROM and DATE_TO — The effective date range for the organization record, enabling point-in-time and slowly changing dimension reporting.
• BUSINESS_GROUP — The HR business group that owns the organization.
• ORG_INT_EXT_FLAG — Indicates whether the organization is internal, external, or a third-party entity.
• ORG_TYPE, ORG_CODE, and ORG_PRIM_CST_MTHD — Organization classification, short code, and primary costing method (for inventory organizations).
• INSTANCE — Identifies the source EBS instance, useful in multi-instance consolidation.
• ORGANIZATION_ID — The operational organization identifier used throughout the EBS transaction model.
• LEVEL_NAME — The position in the organization hierarchy.
• LAST_UPDATE_DATE — Timestamp supporting incremental EDW loads and change detection.
• USER_ATTRIBUTE1–5 — Reserved attribute placeholders, returned as NULL in this view definition.

Common Use Cases and Queries

Typical consumers join this view on ORGANIZATION_PK to organization-keyed facts, or use ORGANIZATION_ID to align with operational EBS data. A common pattern filters active organizations for a business group:

• Validate organization-to-operating-unit mappings during EDW loads.
• Produce a point-in-time organization hierarchy report using DATE_FROM and DATE_TO.
• Cross-reference external organizations via ORG_INT_EXT_FLAG for intercompany reporting.
• Join to costing facts using ORG_PRIM_CST_MTHD for inventory valuation extracts.

Sample query:

SELECT ORGANIZATION_PK, NAME, ORGANIZATION_ID, BUSINESS_GROUP, DATE_FROM, DATE_TO
FROM EDW_ORGANIZATION_LCV
WHERE SYSDATE BETWEEN NVL(DATE_FROM, SYSDATE - 1) AND NVL(DATE_TO, SYSDATE + 1)
ORDER BY NAME;

Because availability is conditional, implementations should verify existence and synonyms before publishing dependent extracts.