Results for “emp_rights_flag”

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

Overview

EDW_HR_JOB_JOBS_LTC is a warehouse-style staging table that belongs to the HRI (Human Resources Intelligence) product family within Oracle E-Business Suite. The LTC suffix in EBS naming conventions denotes a "load-to-current" or collection table used by the HR Intelligence/Data Warehouse extraction layer to stage job and job-definition records before they are transformed into reporting structures. The table is documented in ETRM under both release 12.1.1 and 12.2.2, though it is flagged as Obsolete and its implementation/DBA description states that it is not implemented in the current database. This is significant: the table should not be expected to exist in a standard, provisioned EBS 12.1.1 or 12.2.2 instance unless the HRI/HRMS Intelligence product option was licensed and installed. It is owned by the HRI schema and carries 37 documented columns in the 12.1.1 physical model.

The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table does not serve as a hub, link, or satellite in a clean Vault model — it is a self-contained staging entity with a single inbound reference. This classification is a modeling suggestion only; the physical structure suggests a denormalized extract rather than a normalized hub/link/satellite pattern.

Key Information Stored

The table stores job and job-definition attributes collected from the transactional HR schema for warehouse consumption. The most important documented columns fall into three groups:

• Surrogate and key columns: JOB_PK appears in the composite unique index EDW_HR_JOB_JOBS_LTC_U2, while JOB_PK_KEY is the single-column business key candidate in the unique index EDW_HR_JOB_JOBS_LTC_U1. Both indexes together establish the row-level identity and join keys.
• Source identifiers: JOB_ID, JOB_DEFINITION_ID (the sole foreign key, referencing PER_JOB_DEFINITIONS), BENCHMARK_JOB_ID, and BUSINESS_GROUP_ID carry the transactional keys needed to reconcile staged rows back to the HR source.
• Descriptive and category attributes: NAME, JOB_DP, BENCHMARK_JOB_NAME, BENCHMARK_JOB_FLAG, EMP_RIGHTS_FLAG, and the category set columns JOB_CAT_SET1 through JOB_CAT_SET15 hold the descriptive and flexfield-category context. USER_ATTRIBUTE1 through USER_ATTRIBUTE5 and BUSINESS_GROUP capture the configured descriptive flexfield segments. CREATION_DATE and LAST_UPDATE_DATE provide the standard audit timestamps used for incremental extraction and change detection.

Common Use Cases and Queries

Because the table is obsolete, use cases are primarily historical or migration-related: auditing legacy HRI extracts, comparing staged job data against the current PER_JOBS / PER_JOB_DEFINITIONS model, or reconstructing reports from archived warehouse loads. Typical query patterns include:

• Change detection — filtering on LAST_UPDATE_DATE to identify rows refreshed in a given load window.
• Referential validation — joining JOB_DEFINITION_ID to PER_JOB_DEFINITIONS to confirm the staged row still resolves to a valid definition.
• Deduplication — grouping by JOB_PK and JOB_PK_KEY to detect duplicate staged rows prior to load.
• Reconciliation — comparing NAME and BUSINESS_GROUP_ID against the current PER_JOBS records to quantify drift between warehouse and transactional data.

Related Objects

The documented relationship data identifies one foreign key: JOB_DEFINITION_ID references PER_JOB_DEFINITIONS. Beyond that direct dependency, the staging semantics imply functional (not enforced) relationships with the core HR job tables and views used for comparison and load:

• PER_JOB_DEFINITIONS — referenced by JOB_DEFINITION_ID; the authoritative job definition source.
• PER_JOBS — the transactional job entity whose JOB_ID and NAME values map to staged JOB_ID and NAME.
• HR_ALL_ORGANIZATION_UNITS and PER_BUSINESS_GROUPS — resolve BUSINESS_GROUP_ID and BUSINESS_GROUP context.
• FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — decode the JOB_CAT_SET1–15 and USER_ATTRIBUTE flexfield values.
• PAY_BENCHMARK_JOBS — the likely source for BENCHMARK_JOB_ID, BENCHMARK_JOB_FLAG, and BENCHMARK_JOB_NAME.

Because the object is not implemented in the standard database, developers should verify schema presence in DBA_TABLES and DBA_OBJECTS for owner HRI before designing any integration that assumes its existence.