Results for “sunday_flag”

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

Overview

CS_TM_LABOR_SCHEDULES is a Service (CS) module table that stores Time and Material (T&M) labor schedules used by Oracle E-Business Suite for service billing. Each row defines a billable labor schedule that associates a labor code or inventory item with specific working days and hours, allowing the Service Billing engine to determine when labor is performed and, consequently, how time is priced and invoiced. The table resides in the CS schema and is documented as valid in both EBS 12.1.1 and 12.2.2.

Its relationship structure — a single primary key with foreign keys to reference/master tables such as CS_BUSINESS_PROCESSES and FND_SECURITY_GROUPS — suggests, as a heuristic Data Vault classification, a satellite-leaning profile. In this modeling view, the table functions as a descriptive child of one or more parent business entities, carrying attributes and flags rather than acting as a pure hub or link.

Key Information Stored

The table contains 40 documented columns. The surrogate primary key is TM_LABOR_SCHEDULE_ID, enforced by the CS_TM_LABOR_SCHEDULES_PK constraint. A unique index, CS_TM_LABOR_SCHEDULES_U1, also exists on TM_LABOR_SCHEDULE_ID; in this documented schema the unique index does not expose a separate business-key column, so TM_LABOR_SCHEDULE_ID serves both as surrogate identifier and unique key candidate. The most significant columns include:

• TM_LABOR_SCHEDULE_ID — surrogate primary key uniquely identifying each labor schedule.
• BUSINESS_PROCESS_ID — foreign key to CS_BUSINESS_PROCESSES, linking the schedule to a business process.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling record-level access.
• INVENTORY_ITEM_ID — the inventory item associated with the labor schedule.
• LABOR_CODE — the labor code used for billing.
• START_TIME and END_TIME — the overall schedule window.
• START_HOUR, START_MINUTE, END_HOUR, END_MINUTE — decomposed time components for the schedule boundaries.
• MONDAY_FLAG through SUNDAY_FLAG — day-of-week indicators defining which days the schedule applies.
• HOLIDAY_FLAG — indicates holiday applicability.
• ATTRIBUTE1–ATTRIBUTE15, plus ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield (DFF) columns for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns.

Common Use Cases and Queries

Typical uses include validating that a labor code is billable on a given day, reporting schedules by business process, and auditing DFF-enabled attributes. A common join retrieves schedule and process context:

• Join to business process: SELECT s.tm_labor_schedule_id, s.labor_code, b.business_process_id FROM cs_tm_labor_schedules s, cs_business_processes b WHERE s.business_process_id = b.business_process_id;
• Filter by day: add WHERE monday_flag = 'Y' to identify schedules active on Mondays.
• Security-filtered retrieval: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS for access-controlled reporting.
• Item/labor mapping: group by INVENTORY_ITEM_ID and LABOR_CODE to audit schedule coverage.

Related Objects

The following objects are most significant in relation to CS_TM_LABOR_SCHEDULES, based on documented FK/PK relationships:

• CS_BUSINESS_PROCESSES — referenced via BUSINESS_PROCESS_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• CS_TM_LABOR_SCHEDULES_PK — primary key constraint on TM_LABOR_SCHEDULE_ID.
• CS_TM_LABOR_SCHEDULES_U1 — unique index on TM_LABOR_SCHEDULE_ID.
• Service Billing (CS) concurrent programs and pricing APIs — consume schedule rows to derive labor billing.

Because the documented FK set is limited, additional dependent objects (such as service labor and billing detail tables) should be confirmed against the CS data model for the specific release.