Search Results hz_orig_systems_vl




Overview
Explore in AI Chat

Overview

HZ_ORIG_SYSTEMS_VL is a bilingual (MLS-compliant) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and sits within the Oracle Trading Community Architecture (TCA) foundation layer that governs party, customer, and account registries. The view presents origin system definitions — the registry of external and internal source systems that feed party, account, and contact data into TCA. Every record created in TCA carries an ORIG_SYSTEM and ORIG_SYSTEM_ID reference identifying the system of record, making this view a foundational lookup for entity provenance and multi-source data governance.

The "_VL" suffix indicates a "view with language" — a translated view that joins base and translated table rows and filters the translation rows to the session language using USERENV('LANG'). This allows applications and reports to present the origin system name and description in the user's preferred language while keeping ID-based joins against the untranslated base table.

Underlying Base Objects

The document metadata identifies two referenced base objects, both exposed to APPS as synonyms:

The view text joins the two on ORIG_SYSTEM_ID and filters on T.LANGUAGE = USERENV('LANG'), producing a single logical row per origin system for the current session language. Because the view is a projection over both tables, DML is generally performed against the underlying _B and _TL tables rather than through the view itself; applications typically use the TCA public APIs instead of direct DML.

Key Columns

  • ORIG_SYSTEM_ID — primary surrogate key of the origin system; the value stored on HZ_PARTIES, HZ_CUST_ACCOUNTS, and related entities.
  • ORIG_SYSTEM — the internal short name or code used to identify the source system in data-load and integration processes.
  • ORIG_SYSTEM_TYPE — the classifier queried via the "orig_system_type" search term; distinguishes how the system interacts with TCA (for example, whether it represents an external feeder system, a merge source, or another defined category). This column drives filtering logic in import and interface processing.
  • ORIG_SYSTEM_NAME — the translated, user-facing name of the origin system.
  • DESCRIPTION — translated descriptive text.
  • SST_FLAG — indicates whether the origin system supports the single-source-of-truth designation for related entities.
  • STATUS and START_DATE_ACTIVE / END_DATE_ACTIVE — control the active lifecycle of the origin system definition.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and concurrency columns.
  • ATTRIBUTE1–ATTRIBUTE20, ATTRIBUTE_CATEGORY — descriptive flexfield columns available for customer extension.

Common Use Cases and Queries

Typical scenarios include resolving the origin system behind a party record, validating interface loads before inserting into TCA, and building reports that group customers or accounts by their source system.

  • List all defined origin systems with their type and language-specific name.
  • Retrieve the ORIG_SYSTEM_ID for a known short name prior to an interface insert.
  • Join the view to HZ_PARTIES to report party population by originating system.

Sample queries:

SELECT orig_system_id, orig_system, orig_system_type, orig_system_name, status FROM hz_orig_systems_vl ORDER BY orig_system;

SELECT b.orig_system_id, b.orig_system, b.orig_system_type FROM hz_orig_systems_b b WHERE b.orig_system = :p_orig_system AND NVL(b.status,'A') = 'A';

SELECT h.orig_system, h.party_name FROM hz_parties h, hz_orig_systems_vl o WHERE h.orig_system_id = o.orig_system_id AND o.orig_system_type = :p_type;

Because the view resolves the language at query time, session configuration (NLS_LANG / FND language) directly affects which translated rows are returned; reports requiring deterministic output should join the base and translation tables explicitly or constrain the language.