Results for “sst_flag”

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

Overview

HZ_ORIG_SYSTEMS_B is a reference table owned by the AR (Receivables) schema in Oracle E-Business Suite, holding the registry of originating source systems that feed data into the Trading Community Architecture (TCA) and adjacent EBS components. The "_B" suffix denotes the base (non-translated) table in a TCA entity group; in this case the entity is a lightweight lookup rather than a full TCA party object. Each row identifies a system that can act as the authoritative origin of a record — for example EBS itself, a legacy feeder system during a migration, or an external application integrated through interfaces and APIs. Because downstream tables store only the numeric ORIG_SYSTEM_ID, this table is the single point of truth for translating those identifiers back into readable system names and types.

From a heuristic Data Vault perspective, the metadata classifies this object as standalone. That classification suggests treating HZ_ORIG_SYSTEMS_B as a reference hub or, more simply, a flat reference dimension rather than a link or satellite. There are no meaningful parent foreign keys within the table itself; instead it sits at the top of a wide fan-in of dependent tables across Receivables, Trading Community, Workflow, HR, Approvals Management, and EDI/Print modules.

Key Information Stored

The documented physical schema contains 36 columns. The most important are:

• ORIG_SYSTEM_ID — the surrogate primary key, enforced by HZ_ORIG_SYSTEMS_B_PK. This is the value propagated into every referencing table.
• ORIG_SYSTEM — the short business identifier of the source system. A unique index, HZ_ORIG_SYSTEMS_U2 (ORIG_SYSTEM, ZD_EDITION_NAME), makes this a business-key candidate.
• ORIG_SYSTEM_TYPE — categorizes the origin system, allowing consumers to distinguish EBS-internal from external or upload sources.
• SST_FLAG — flags whether the row participates in the Single Source of Truth mechanism, key to master-data governance.
• STATUS, START_DATE_ACTIVE, END_DATE_ACTIVE — lifecycle and effective-dating controls that allow a source system to be retired without deleting historical references.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the TCA API layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• CREATED_BY_MODULE — identifies the module that inserted the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the DFF/extension block for client-specific data.
• ZD_EDITION_NAME — the editioning column that supports online patching and is part of both unique indexes: HZ_ORIG_SYSTEMS_U1 (ORIG_SYSTEM_ID, ZD_EDITION_NAME) and HZ_ORIG_SYSTEMS_U2 (ORIG_SYSTEM, ZD_EDITION_NAME).

Common Use Cases and Queries

Because ORIG_SYSTEM_ID is stored as a foreign key in more than twenty dependent tables, the dominant use case is a decode/join to render a human-readable source system alongside TCA, Workflow, and HR data. A typical pattern resolves the originating system for workflow role entries:

• Join WF_LOCAL_ROLES to HZ_ORIG_SYSTEMS_B on ORIG_SYSTEM_ID to report who or what created each role assignment.
• Join PER_EMPDIR_* and JTF_LOC_POSTAL_CODES to tag directory and geography rows with their source system.
• Filter active systems using STATUS and the START/END_DATE_ACTIVE window to exclude retired integrations from reports.
• Join FND_CONC_PP_ACTIONS and FND_RUN_REQ_PP_ACTIONS to attribute concurrent post-processing actions to a source.
• Validate SST_FLAG to confirm which systems are trusted as Single Source of Truth before loading master data.

A representative query is SELECT s.orig_system, r.role_name FROM wf_local_roles r JOIN hz_orig_systems_b s ON s.orig_system_id = r.orig_system_id WHERE s.status = 'A'; Reporting tools and TCA extraction scripts favour this table because it is small, stable, and cacheable.

Related Objects

The FK lineage shows a broad fan-in; the most significant referencing objects are:

• WF_LOCAL_ROLES (and its TL/OLD/STAGE variants) via ORIG_SYSTEM_ID — workflow role and user resolution.
• WF_LOCAL_USERS via ORIG_SYSTEM_ID — workflow user identity mapping.
• PER_EMPDIR_PEOPLE, PER_EMPDIR_ASSIGNMENTS, PER_EMPDIR_ORGANIZATIONS, PER_EMPDIR_JOBS, PER_EMPDIR_POSITIONS, PER_EMPDIR_LOCATIONS and PER_EMPDIR_PHONES via ORIG_SYSTEM_ID — the HR employee/manager directory extracts.
• AME_APPROVAL_GROUP_MEMBERS via ORIG_SYSTEM_ID — approver membership sourcing.
• JTF_LOC_POSTAL_CODES and JTF_LOC_AREAS_B via ORIG_SYSTEM_ID — geography reference data.
• AP_APINV_APPROVERS, FND_CONC_PP_ACTIONS, FND_RUN_REQ_PP_ACTIONS, and the EDR_PSIG_* tables via ORIG_SYSTEM_ID — payables approval, concurrent post-processing, and EDI print signature history.

In short, HZ_ORIG_SYSTEMS_B is the small but central registry that makes source-system provenance meaningful across TCA, Workflow, HR, and EDI reporting.