Results for “task_description”

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

Overview

HXTFV_PROJECT_ACCOUNTING is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HXT (Time and Labor) product family. It is classified as a VIEW, is reported VALID, and is available in both the 12.1.1 and 12.2.2 release lines. The view consolidates timecard detail with the project and task hierarchy against which that time was charged, together with the person and assignment context of the worker who reported it. Its principal function is to present a denormalized, presentation-ready projection of hours worked at the intersection of employee, project, task, and organization, which makes it suitable for costing, project accounting reconciliation, and labor distribution reporting. The view is read-only and is intended for query and extraction rather than for transactional update.

Underlying Base Objects

The view is defined over a fixed join of transactional and reference objects: HXT_DET_HOURS_WORKED_F, HXT_TASKS, HXT_PROJECTS, PER_ALL_PEOPLE_F, PER_ASSIGNMENTS_F, and HR_ALL_ORGANIZATION_UNITS_TL, with HR_GENERAL and HR_SECURITY (both packages) invoked during resolution. HXT_DET_HOURS_WORKED_F is the driving detail table, holding the individual hours worked rows. HXT_TASKS and HXT_PROJECTS supply the task and project attributes. PER_ALL_PEOPLE_F and PER_ASSIGNMENTS_F provide person and assignment identity, while HR_ALL_ORGANIZATION_UNITS_TL is joined twice — once as ORGT for the organization and once as BGRT for the business group name. The joins are date-effective: the view restricts on SYSDATE between the effective start and end dates of the hours worked, person, and assignment rows. Language is constrained through USERENV('LANG'), and HR_SECURITY is applied to enforce row-level access to organizations and business groups. All referenced tables are accessed through public synonyms rather than direct schema references.

Key Columns

• PROJECT_DESCRIPTION — the descriptive text of the project from HXT_PROJECTS.DESCRIPTION; this is the column most commonly targeted by searches for "project_description".
• PROJECT_NAME / PROJECT_NUMBER / PROJECT_ID — the project's name, number, and the identifier drawn from TAS.PRO_ID.
• TASK_NAME / TASK_NUMBER / TASK_DESCRIPTION / TASK_ID — the task charged by the timecard line.
• PERSON_NAME / PERSON_ID / ASSIGNMENT_ID — the worker and assignment associated with the hours worked.
• BUSINESS_GROUP_NAME / ORGANIZATION_NAME / BUSINESS_GROUP_ID — the organization and business group context.
• DATE_WORKED / HOURS / TIME_IN / TIME_OUT — the transactional timecard detail, including reported hours and clock times.
• RATE_MULTIPLE / HOURLY_RATE / AMOUNT — the rate basis and computed amount for the reported hours.
• PROJECT_START / PROJECT_END / TASK_START / TASK_END — the effective ranges of the project and task.
• DET_HOURS_WORKED_ID / TIMECARD_ID / SHIFT_ID / SUM_HOURS_WORKED_ID — primary and foreign identifiers linking back to source tables.
• TASK_UNITS — the HXT_TASK_UNITS lookup value decoded through HR_GENERAL.DECODE_LOOKUP.

Common Use Cases and Queries

The view is typically used to reconcile reported time against project structures, to extract labor distribution for downstream costing, and to drive operational reports showing hours by project, task, and person. A representative query retrieving project descriptions with aggregated hours is:

SELECT project_name,
       project_number,
       project_description,
       task_name,
       person_name,
       SUM(hours) total_hours
  FROM apps.hxtfv_project_accounting
 WHERE date_worked BETWEEN :p_start AND :p_end
 GROUP BY project_name, project_number, project_description,
          task_name, person_name
 ORDER BY project_name, task_name;

Because the view applies HR_SECURITY and SYSDATE-based effective dating, results reflect only currently effective person and assignment records visible to the querying responsibility. Consumers should therefore treat the output as a secure, as-of-now snapshot rather than a historical archive, and should filter on DATE_WORKED rather than on the effective dates of the underlying people and assignment rows to retrieve prior-period time.