Results for “hr_soft_coding_keyflex”

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

Overview

HR_SOFT_CODING_KEYFLEX is a Human Resources (PER) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores legislation-specific soft coding key flexfield information for payrolls, organizations, and assignments. Soft coding key flexfields provide a configurable, multi-segment classification mechanism that customers use to tag HR and payroll entities with client-defined codes—such as cost centers, funding sources, project references, or legislative reporting categories—that vary by country and business requirement. Because the flexfield structure is defined at runtime rather than fixed at design time, a single physical table serves all legislations through a repeating SEGMENT1 through SEGMENT30 column set plus a CONCATENATED_SEGMENTS display value.

From a Data Vault modeling perspective, the ETRM heuristic classification for this table is hub-leaning. This means HR_SOFT_CODING_KEYFLEX is best treated as a hub of unique soft coding keyflex identities, keyed by its surrogate identifier, with the descriptive segment values and audit columns behaving as satellite-style attributes. The classification is a modeling suggestion derived from the foreign key topology, not a physical property of the table.

Key Information Stored

The table contains 46 documented columns. The most significant are:

• SOFT_CODING_KEYFLEX_ID — the surrogate primary key, defined by the unique index HR_SOFT_CODING_KEYFLEX_PK. Every dependent table references this value.
• CONCATENATED_SEGMENTS — the concatenated display string of all populated segment values, used for reporting and user-facing code display.
• SEGMENT1 … SEGMENT30 — the individual segment columns. Only the segments enabled in the applicable key flexfield definition are populated; the remainder are null. This is the core business payload.
• ID_FLEX_NUM — the key flexfield definition identifier that governs which segments are active and their validation rules. It links the row to the flexfield structure registered in the application.
• SUMMARY_FLAG and ENABLED_FLAG — control whether the combination is a roll-up summary and whether it may be used on new transactions.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date-range enablement for the combination.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the request that last modified the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit columns used pervasively in reporting and audit trails.

The only documented unique index, HR_SOFT_CODING_KEYFLEX_PK on SOFT_CODING_KEYFLEX_ID, is purely surrogate. The true business key is the combination of ID_FLEX_NUM plus the populated segment values, which is why no natural unique constraint appears in the metadata.

Common Use Cases and Queries

Typical scenarios include payroll cost allocation reporting, organization-level legislative coding, and assignment-based funding analysis. A basic lookup resolves a foreign key to a readable code:

• SELECT soft_coding_keyflex_id, concatenated_segments FROM hr_soft_coding_keyflex WHERE soft_coding_keyflex_id = :p_id;
• Joining assignments to their soft coding: SELECT a.assignment_id, k.concatenated_segments FROM per_all_assignments_f a, hr_soft_coding_keyflex k WHERE a.soft_coding_keyflex_id = k.soft_coding_keyflex_id AND TRUNC(SYSDATE) BETWEEN a.effective_start_date AND a.effective_end_date;
• Segment-level filtering for a specific legislation, for example restricting to rows where id_flex_num = :flex and segment1 = :cost_center.
• Validity checks using enabled_flag = 'Y' and the active date range before allowing selection in a concurrent or form process.

Because segment semantics are defined by the flexfield, reporting queries should always constrain on ID_FLEX_NUM or join through the flexfield definition views to avoid mixing combinations from different structures.

Related Objects

The foreign key metadata shows HR_SOFT_CODING_KEYFLEX is referenced by several core dependent objects, confirming its hub role:

• PER_ALL_ASSIGNMENTS_F via SOFT_CODING_KEYFLEX_ID — assignment-level legislative coding.
• HR_ALL_ORGANIZATION_UNITS via SOFT_CODING_KEYFLEX_ID — organization-level coding (listed twice in the metadata).
• PAY_ALL_PAYROLLS_F via SOFT_CODING_KEYFLEX_ID — payroll-level coding.
• HR_PERSON_DEPLOYMENTS via SOFT_CODING_KEYFLEX_ID — deployment records.
• BEN_CWB_PERSON_INFO via SOFT_CODING_KEYFLEX_ID — benefits compensation workbench person data.
• HR_EDW_WRK_ACTVTY_F and HR_EDW_WRK_ACTVTY_FSTG via SOFT_CODING_KEYFLEX_ID — HR data warehouse fact and staging tables.

These relationships make the table a central reference point for HR, payroll, and benefits reporting, and a required dimension join wherever assignment, organization, or payroll activity is analyzed by soft coding.