Search Results tim_row_id

Overview

APPS.HXT_TIM_SUMMARY_FMV is a reporting view in Oracle E-Business Suite that consolidates timecard, rotation plan, assignment, payroll, and person data relevant to the Oracle Time and Labor (OTL) and Enterprise Territory/Resource Management (ETRM) time-recording model. The view joins transactional timecard rows held in HXT_TIMECARDS against the period, assignment, organization, payroll, person, and rotation-plan dimensions required to render a human-readable summary of time entries. It is exposed as a multi-table join view (the "_FMV" suffix conventionally denotes a formatted/flexible model view) and is intended primarily for reporting, extracts, and integration consumers that must present approved time without directly reconstructing the entity relationships.

The most common entry point for developers interacting with this object is the surrogate identifier exposed as tim_row_id, which is the physical ROWID of the underlying HXT_TIMECARDS row. Because it is a ROWID rather than a stable business key, consumers often search for it as a means of locating, updating, or correlating a specific timecard record within the view's output.

Underlying Base Objects

The view is owned by APPS and is defined over a combination of tables, views, synonyms, and packages. The documented referenced base objects are:

• HR_GENERAL (PACKAGE) — supplies the start_of_time and end_of_time boundary constants used in the approved-person temporal join.
• HR_ORGANIZATION_UNITS (VIEW) — provides the organization name and business group for the assignment's organization.
• HR_PERSON_NAME (PACKAGE) — used to resolve person name formatting.
• HR_SECURITY (PACKAGE) — supports security-based row filtering.
• HXT_PER_AEI_DDF_V (VIEW) — supplies the assignment effective-dated attributes, including the rotation plan reference.
• HXT_ROTATION_PLANS (SYNONYM) — the rotation plan definition providing rotation_plan_name.
• HXT_TIMECARDS (VIEW) — the primary transactional source, exposing the timecard id, approval person, approval timestamp, and audit columns.
• PAY_PAYROLLS_F (VIEW) — provides the payroll id and payroll name.
• PER_ASSIGNMENTS (VIEW) — supplies organization, business group, and assignment effective dates.
• PER_PEOPLE_F (VIEW) — used twice (aliases per and per2) to resolve the employee and the approver respectively.
• PER_TIME_PERIODS (SYNONYM) — provides the period end date driving the effective-dated joins.

The join predicate centres on tim.time_period_id = ptp.time_period_id and correlates the period end date against the effective date ranges of the person, assignment, approver, and assignment attribute rows, ensuring a single consistent "as-of-period-end" snapshot.

Key Columns

• tim_id — the HXT_TIMECARDS primary key; tim_row_id — the underlying ROWID of that row.
• time_period_id, end_date — period identity and its end date.
• person_id, employee_number, full_name — the employee whose timecard is reported.
• approv_person_id, approv_person_name, approved_timestamp — who approved the timecard and when.
• organization_id, organization_name, hxt_rotation_plan_id, rotation_plan_name — assignment placement and rotation plan.
• payroll_id, payroll_name — payroll linkage.
• The business-group columns (asg_bus_grp_id, org_bus_grp_id, pay_bus_grp_id, emp_bus_grp_id, app_bus_grp_id) expose the security context of each joined entity.
• Audit columns created_by, creation_date, last_update_date, last_update_login, last_updated_by.

Common Use Cases and Queries

Typical uses include timecard approval reporting, rotation-based summarisation, and extracts keyed by period. Retrieving a single timecard by row id:

SELECT tim_id, person_id, full_name, end_date, approved_timestamp FROM apps.hxt_tim_summary_fmv WHERE tim_row_id = :p_rowid;

Summarising approved entries per rotation plan for a period:

SELECT rotation_plan_name, organization_name, COUNT(*) FROM apps.hxt_tim_summary_fmv WHERE end_date = :p_period_end GROUP BY rotation_plan_name, organization_name;

Because tim_row_id is a ROWID, it is not persistent across reorganisations; joins back to HXT_TIMECARDS should generally be performed on tim_id, reserving tim_row_id for direct row location and audit correlation.