Search Results ghr_sf113_v




Overview
Explore in AI Chat

Overview

The view APPS.GHR_SF113_V is a reporting object within the Oracle E-Business Suite GHR — US Federal Human Resources product family. Its documented purpose is to generate the SF-113A report, a U.S. federal personnel form that summarizes assignment and position data for active and terminated personnel. In the context of EBS 12.1.1 and 12.2.2, this view functions as a denormalized, read-only projection of core HR assignment data, joining person, assignment, grade, and status information into a single consumable rowset suitable for reporting and downstream integration.

The view is owned by the APPS schema and carries a VALID status in the ETRM registry. Because Oracle EBS exposes GHR federal objects through the APPS schema, this view is typically referenced by concurrent programs, BI Publisher report definitions, and custom extracts rather than being maintained by end users directly. Its role is therefore that of a stable query interface, shielding reporting logic from the normalized structure of the underlying PER tables.

Underlying Base Objects

The documented base objects referenced by GHR_SF113_V span views, synonyms, and packaged APIs. The primary data sources are the PER_ASSIGNMENTS_F and PER_PEOPLE_F date-tracked views, joined through PER_ASSIGNMENT_STATUS_TYPES, PER_GRADES, and PER_GRADE_DEFINITIONS. These are the fact-bearing objects from which assignment, person, grade, and status attributes are drawn.

The ETRM metadata additionally lists the package dependencies HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. These packages are significant: HR_SECURITY enforces row-level security (security profiles) so that the view returns only the people and assignments visible to the querying responsibility. HR_PERSON_NAME supports name formatting, while HR_GENERAL provides shared HR utilities. Note that the view text itself does not filter by business group or date-tracked effective dates explicitly; that behavior is inherited from the underlying _F views and the security packages.

Key Columns

The search term active_assign corresponds directly to the ACTIVE_ASSIGN system status. The view deliberately filters into the ACTIVE_ASSIGN and TERM_ASSIGN statuses only, so it excludes other assignment states. It also restricts PRIMARY_FLAG = 'Y' (primary assignments only) and ASSIGNMENT_TYPE <> 'B' (excluding applicant-type rows). Grade definitions beginning with the segments CC, NA, NL, or NS are suppressed via a SUBSTR filter on SEGMENT1.

Common Use Cases and Queries

The most frequent use case is SF-113A report generation and related workforce extracts. A representative query retrieving all active primary assignments is shown below.

  • Active assignment listing: SELECT person_id, assignment_id, status, effective_start_date, effective_end_date FROM apps.ghr_sf113_v WHERE status = 1 ORDER BY person_id;
  • Grade and location analysis: Join GRADE_ID and LOCATION_ID to PER_GRADES and HR_LOCATIONS to build distribution reports.
  • Status comparison: Filter WHERE status IN (1,2) to compare currently active versus terminated assignments for a submission period.
  • Integration: Consume the view in BI Publisher data models or OBIEE extracts where a flat person-assignment rowset is required.

Because row-level security is applied through HR_SECURITY, results vary by the responsibility or user context executing the query. Administrators should therefore test queries under the intended reporting responsibility to confirm the correct security profile is in effect. The DATE_TRACKED nature of the underlying _F views also means that a given assignment may appear across multiple effective-dated rows unless the caller constrains effective dates explicitly.