Search Results fulltime_availabilty

Overview

APPS.HXC_RESOURCE_INFORMATION_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the APPS schema and associated with the Oracle Time and Labor (OTL / HXC) product family. It exposes a denormalized, security-aware snapshot of a person as a "resource" — the individual whose availability, schedule, and cost capacity are consumed when timecards are entered or when schedules are built. Because OTL treats every worker as a resource with assignable time, this view is the primary read-only presentation layer used by schedule administration, timecard validation, and downstream reporting rather than by transactional inserts.

The view is not a base table. It is a query that joins person, assignment, organization, and lookup data, then renames and reshapes those attributes into resource-centric aliases. This abstraction isolates reporting consumers from the underlying HRMS data model, whose tables (PER_PEOPLE_F, PER_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE) are effectively date-tracked and heavily secured.

Underlying Base Objects

The view draws on a broad set of HRMS and payroll objects. Core people and assignment data come from PER_PEOPLE_F, PER_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE, PER_POSITIONS, PER_JOBS, PER_GRADES, PER_CAGR_GRADES_DEF, PER_COLLECTIVE_AGREEMENTS, and PER_PAY_BASES. Organizational context is supplied by HR_ORGANIZATION_UNITS, HR_LOCATIONS, and PER_TIME_PERIODS. Lookups and validation helpers include HR_LOOKUPS, HR_LOCATIONS, PER_ASSIGNMENT_STATUS_TYPES_V, and PAY_PAYROLLS. Payroll and cost allocation attributes are joined from PAY_COST_ALLOCATIONS_F, PAY_COST_ALLOCATION_KEYFLEX, PAY_PEOPLE_GROUPS, and HR_SOFT_CODING_KEYFLEX. Finally, PL/SQL packages HR_API, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY provide business logic, formatted name derivation, and row-level security enforcement. HR_SECURITY in particular ensures a user only sees resources within their authorized organization hierarchy.

Key Columns

• Resource_ID — maps to pap.person_id, the person's unique identifier.
• Resource_Display_Name — formatted full name (pap.full_name).
• Resource_Number — employee_number.
• National_Identifier — the person's national identifier (e.g., SSN or NI number), subject to security masking.
• Hire_Date — derived from PER_PERIODS_OF_SERVICE.date_start, exposed only when current_employee_flag = 'Y'.
• Job_Title, Organization_Name — the job and the HR organization to which the assignment belongs.
• Supervisor_Name / Supervisor_Number — resolved from a self-join to the person record (pap2), identifying the resource's manager.
• Per_Information1 … Per_Information30 — a generic flexfield-style set of person-information attributes, with Per_Information_Category naming the context.
• Availability_Schedule — lookup meaning (hl1.meaning) describing the resource's availability calendar.
• Fulltime_Availabilty — derived from pap.fte_capacity. This is the column most relevant to the user's search term "fulltime_availabilty": it reflects the full-time-equivalent capacity of the resource, used when comparing a worker's available hours to a standard full-time schedule.
• Office_Number, Internal_Location, Mailstop — physical/contact location attributes.
• Attribute_Category and Attribute1 … AttributeN — descriptive flexfield (DFF) columns carrying client-specific resource attributes.

Common Use Cases and Queries

Typical uses include: populating resource lists for schedule administration, computing part-time versus full-time availability, joining resource data to timecard facts, and feeding downstream extraction or BI tools. The FTE column is frequently the filter of interest.

SELECT resource_id,
       resource_display_name,
       resource_number,
       hire_date,
       availability_schedule,
       fulltime_availabilty
  FROM apps.hxc_resource_information_v
 WHERE fulltime_availabilty < 1
   AND availability_schedule IS NOT NULL;

A second common pattern joins the view to supervisor or organization filters to drive labor-distribution reporting, relying on HR_SECURITY to restrict rows automatically. Because the view references date-effective base tables, callers should avoid assuming a single row per person without accounting for the effective date logic inherited from PER_ASSIGNMENTS_F and PER_PEOPLE_F.