Results for “logout_date”

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

Overview

AHL_WORK_LOGIN_TIMES is a table in the AHL schema belonging to the Complex Maintenance Repair and Overhaul (CMRO) product family within Oracle E-Business Suite, and is documented as valid in both the 12.1.1 and 12.2.2 releases. Its stated purpose is to store employee login and logout times against an operation-resource, making it the transactional record of labor attendance at the resource level rather than at the department or shift level. In that role it functions as the bridge between a scheduled operation-resource assignment and the actual clock-on and clock-off events performed by an employee working that assignment.

From a data-modeling standpoint, the mined relationship structure suggests treating this table as a satellite-leaning object. This is a heuristic classification, not an Oracle-declared designation. A satellite interpretation is consistent with the presence of descriptive and temporal attributes (login date, logout date, login level) that accrue around a strong business key, together with standard EBS audit and DFF columns. The table carries a single-column primary key constraint, AHL_WORK_LOGIN_TIMES_PK, defined on WORK_LOGIN_TIME_ID, and the same column is also exposed through the unique index AHL_WORK_LOGIN_TIMES_U1, giving a one-to-one surrogate-to-business-key relationship at the row level.

Key Information Stored

The table is documented with 32 physical columns. The most significant are listed below.

• WORK_LOGIN_TIME_ID — surrogate primary key, protected by AHL_WORK_LOGIN_TIMES_PK and surfaced as the business-key candidate through AHL_WORK_LOGIN_TIMES_U1.
• WORKORDER_ID — foreign key to AHL_WORKORDERS; identifies the work order under which the labor was performed.
• OPERATION_RESOURCE_ID — foreign key to AHL_OPERATION_RESOURCES; the specific operation-resource instance the employee logged into.
• EMPLOYEE_ID — foreign key to PSB_EMPLOYEES; the individual whose attendance is being recorded.
• OPERATION_SEQ_NUM and RESOURCE_SEQ_NUM — the operation and resource sequence numbers within the work order routing, allowing the login to be tied to a precise routing step.
• LOGIN_DATE and LOGOUT_DATE — the timestamp pair capturing the start and end of the attendance interval.
• LOGIN_LEVEL — classification of the login event, used to distinguish the granularity or nature of the recorded time.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing the multi-tenant / operating-unit partitioning used in AHL.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS who-columns for audit and concurrency.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segment storage.

Common Use Cases and Queries

The predominant use of this table is labor-actual reporting: comparing planned operation-resource hours against logged attendance and computing downtime or utilization metrics. A typical join resolves the employee and resource context for a given work order interval:

• Joining AHL_WORK_LOGIN_TIMES to AHL_WORKORDERS on WORKORDER_ID and to AHL_OPERATION_RESOURCES on OPERATION_RESOURCE_ID to report planned versus actual labor per operation.
• Aggregating LOGIN_DATE and LOGOUT_DATE differences by EMPLOYEE_ID to produce timesheet or wrench-time summaries.
• Filtering on SECURITY_GROUP_ID to scope reporting to a specific operating unit.
• Detecting open or suspended sessions by selecting rows where LOGOUT_DATE is null.
• Reconciling maintenance cost rollups on the work order by summing attendance against the resource rate.

Because LOGOUT_DATE may legitimately be null while an employee is still clocked in, queries should use outer joins or null-safe predicates when comparing to AHL_OPERATION_RESOURCES.

Related Objects

• AHL_OPERATION_RESOURCES — referenced via OPERATION_RESOURCE_ID; the parent resource assignment.
• AHL_WORKORDERS — referenced via WORKORDER_ID; the maintenance order driving the work.
• PSB_EMPLOYEES — referenced via EMPLOYEE_ID; supplies employee identity and defaults.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; controls data partitioning.
• AHL_OPERATION_RESOURCES and the AHL work-order routing tables together form the primary navigation path into the AHL CMRO execution model, with AHL_WORK_LOGIN_TIMES acting as the attendance fact.