Search Results hr_authoria_mappings




Overview
Explore in AI Chat

Overview

HR_AUTHORIA_MAPPINGS is a Human Resources (PER) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas, owned by the HR schema. Its documented description is "Authoria Mapping Information." The table stores configuration records that map Oracle HRMS plan and plan-in-program constructs to the Authoria benefits communication and enrollment platform, a third-party total benefits solution used to present benefit offerings, plan details, and enrollment pages to employees. Each row defines the relationship between an HR benefits plan, its placement within a plan-in-program, and the target Authoria page used when that combination is displayed or referenced during open enrollment or general benefits browsing.

The documented schema contains 11 columns. The heuristic Data Vault classification derived from the foreign-key structure is standalone, meaning no explicit parent-child dependencies were mined from the constraints. As a modeling suggestion, this places the table closest to a reference or mapping hub-satellite construct, where AUTHORIA_MAPPING_ID behaves as the surrogate hub key and the unique business key carries the descriptive mapping attributes. The standalone classification indicates the table can be loaded and queried independently of other HR benefits tables, though functional usage still depends on valid PL_ID and PLIP_ID values from the benefits configuration.

Key Information Stored

The primary key is enforced by HR_AUTHORIA_MAPPINGS_PK on AUTHORIA_MAPPING_ID, a system-generated surrogate identifier. A second unique index, HR_AUTHORIA_MAPPINGS_UK1, defines the business key over PL_ID, PLIP_ID, and OPEN_ENROLLMENT_FLAG, guaranteeing that only one mapping exists per plan, plan-in-program, and enrollment context. The most significant columns are:

  • AUTHORIA_MAPPING_ID — surrogate primary key for each mapping record.
  • PL_ID — identifier of the HR benefits plan being mapped.
  • PLIP_ID — identifier of the plan-in-program record that positions the plan within a program offering.
  • OPEN_ENROLLMENT_FLAG — indicates whether the mapping applies specifically to open enrollment versus general benefits viewing.
  • TARGET_PAGE — the Authoria destination page or URL invoked for this plan and program combination.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the HRMS framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE — standard WHO columns capturing the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns capturing the last modifying user, timestamp, and login session.

Common Use Cases and Queries

Administrators and integrators query this table to audit and troubleshoot Authoria enrollment mappings, particularly when an employee sees an incorrect or missing plan page. A typical verification query joins the mapping to plan and plan-in-program tables:

  • SELECT m.authoria_mapping_id, m.pl_id, m.plip_id, m.open_enrollment_flag, m.target_page FROM hr.hr_authoria_mappings m WHERE m.pl_id = :plan_id;
  • Filtering by OPEN_ENROLLMENT_FLAG = 'Y' isolates the mappings active during open enrollment windows for readiness checks.
  • Detecting duplicates or gaps against HR_AUTHORIA_MAPPINGS_UK1 by grouping on PL_ID, PLIP_ID, and OPEN_ENROLLMENT_FLAG.
  • Change auditing using LAST_UPDATED_BY, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER to identify recently reconfigured mappings.

These queries support benefits configuration validation, post-patch regression checks, and reconciliation with the external Authoria system.

Related Objects

Because the table is documented as standalone, relationships are largely functional rather than enforced by foreign keys. The most significant related objects are:

  • BEN_PL_F and BEN_PL_TL — plan definitions joined on PL_ID to resolve plan names.
  • BEN_PLIP_F — plan-in-program definitions joined on PLIP_ID to resolve program placement.
  • BEN_PGM_F — program definitions reachable through the plan-in-program relationship.
  • PER_ALL_PEOPLE_F — employee records relevant when mapping outcomes are presented to participants.
  • FND_APPLICATION / FND_USER — referenced through the WHO audit columns for ownership and session traceability.
  • BEN_ENRL_ACTIONS and related enrollment tables — depend functionally on correct plan and plan-in-program configuration established here.

PL/SQL packages and concurrent programs in the PER and BEN schemas that drive benefits enrollment and Authoria integration read these mappings during page resolution.