Search Results employer_id




Overview
Explore in AI Chat

Overview

APPS.HR_ATH_EMPLOYER_V is a lightweight reporting and integration view in Oracle E-Business Suite, defined in the APPS schema. It exposes business group records as "employers," presenting each business group identifier as a character-formatted EMPLOYER_ID alongside the business group name and effective date range. The view name incorporates the ATH prefix associated with Oracle HRMS localization and statutory reporting components, and it is used where downstream processes require an employer abstraction rather than a direct business group reference.

In Oracle EBS 12.1.1 and 12.2.2, the business group is the highest organizational unit in the HRMS security and data model. Many external interfaces, tax-reporting layouts, and third-party payroll integrations expect an "employer" identity rather than a raw business group ID. HR_ATH_EMPLOYER_V bridges that gap by performing a simple projection and data type conversion, allowing consumers to retrieve employer identity and validity dates through a stable, read-only interface. Because it is a view, no physical storage is allocated and no DML is supported; it is intended strictly for query and extraction purposes.

Underlying Base Objects

The view is defined over a single documented base object: PER_BUSINESS_GROUPS, which is itself implemented as a view in the APPS schema. No joins, unions, or aggregations are present in the view definition, so the cardinality of HR_ATH_EMPLOYER_V matches the rows visible in PER_BUSINESS_GROUPS. The relationship is strictly one-to-one at the row level: each qualifying business group row produces exactly one employer row.

  • PER_BUSINESS_GROUPS — the sole referenced object, supplying BUSINESS_GROUP_ID, NAME, DATE_FROM, and DATE_TO.
  • No date-tracked or translated tables are joined directly by the view; any date-track or translation filtering occurs within the underlying PER_BUSINESS_GROUPS view definition.
  • Access is subject to the standard APPS schema grants and any HRMS security profiles applied to the querying responsibility.

Key Columns

  • EMPLOYER_ID — derived as TO_CHAR(BUSINESS_GROUP_ID). The business group primary key is converted from numeric to character, matching integration and reporting formats that expect a string employer identifier. This is the column most commonly retrieved when users search for "employer_id."
  • NAME — the business group name, passed through unchanged from PER_BUSINESS_GROUPS, representing the employer's descriptive label.
  • START_DATE — aliased from DATE_FROM; the date on which the business group (employer) record becomes effective.
  • END_DATE — aliased from DATE_TO with NVL(DATE_TO, TO_DATE('12/31/4712','MM/DD/YYYY')). A null end date is replaced by the Oracle EBS high date, 31-DEC-4712, indicating an open-ended or currently active employer record.

Common Use Cases and Queries

Typical scenarios include populating employer lists in statutory or tax-reporting extracts, validating that an employer identifier exists before loading interface data, and driving LOV-style lookups in custom concurrent programs. The string conversion of EMPLOYER_ID makes the view convenient for concatenation into flat-file layouts where numeric formatting must be avoided.

  • Retrieve all employers with their validity windows:
    SELECT employer_id, name, start_date, end_date FROM apps.hr_ath_employer_v;
  • Resolve a specific employer from a search term:
    SELECT employer_id, name FROM apps.hr_ath_employer_v WHERE employer_id = :p_employer_id;
  • Identify currently active employers:
    SELECT employer_id, name FROM apps.hr_ath_employer_v WHERE SYSDATE BETWEEN start_date AND end_date;

Because EMPLOYER_ID is character-typed, comparisons against numeric business group values require explicit conversion or character literals. Consumers should also account for HRMS security, which may restrict the business groups visible to a given responsibility, and should treat the view as read-only at all times.