Results for “schedule_type_code”

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

Overview

PA_SCHEDULES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) application. Its documented purpose is to display schedule details for both requirements and assignments, and to expose calendar-based schedules. The view is registered as VALID in ETRM and is present in both the 12.1.1 and 12.2.2 releases. Functionally, it serves as a denormalized read layer that joins the transactional schedule table PA_SCHEDULES to the project status lookup table PA_PROJECT_STATUSES, so that each schedule row is returned together with its descriptive project system status. This makes it a convenient source for reports, concurrent program extracts, and integration interfaces that need schedule information without performing the status join themselves.

Underlying Base Objects

The documented base objects referenced by the view are PA_SCHEDULES (SYNONYM) and PA_PROJECT_STATUSES (SYNONYM), both resolved under the APPS schema. PA_SCHEDULES is the driving table and stores one row per schedule record, keyed by SCHEDULE_ID, with references to a calendar, assignment, and project. PA_PROJECT_STATUSES is the status reference table that maps a status code to a system status code and a status name. The view text performs an inner join between the two on the condition SCH.STATUS_CODE = PST.PROJECT_STATUS_CODE, which means only schedules whose status code matches a defined project status code are returned. The view does not itself store data; all columns are derived from these two base tables at query time.

Key Columns

• SCHEDULE_ID — Primary identifier of the schedule record, sourced from PA_SCHEDULES.
• CALENDAR_ID — Identifier of the calendar associated with a calendar schedule.
• ASSIGNMENT_ID — Identifier of the assignment to which the schedule belongs, where applicable.
• PROJECT_ID — Identifier of the project owning the schedule.
• SCHEDULE_TYPE_CODE — Discriminator indicating whether the row is a requirement schedule, an assignment schedule, or a calendar schedule.
• STATUS_CODE — The schedule's own status code from PA_SCHEDULES, which is used to join to the status table.
• SYSTEM_STATUS_CODE — The project system status code (PST.PROJECT_SYSTEM_STATUS_CODE) obtained from PA_PROJECT_STATUSES. This is the column commonly targeted when users search for "system_status_code" against this view.
• ASSIGNMENT_STATUS_DESC — The descriptive project status name (PST.PROJECT_STATUS_NAME) associated with the schedule status.
• START_DATE / END_DATE — Effective date range of the schedule.
• MONDAY_HOURS through SUNDAY_HOURS — Seven columns holding the planned hours for each day of the week, supporting both requirement and assignment hour distribution.

Common Use Cases and Queries

The view is typically queried to report planned effort per assignment or requirement, filtered by project and system status. A representative query retrieving active schedules for a project is:

SELECT schedule_id, assignment_id, schedule_type_code,
       system_status_code, assignment_status_desc,
       start_date, end_date, monday_hours, tuesday_hours
FROM   apps.pa_schedules_v
WHERE  project_id = :p_project_id
AND    system_status_code = :p_system_status_code;

Because STATUS_CODE is joined to the status table, callers can also resolve schedule status descriptions directly without an additional lookup. Typical scenarios include project effort reporting, assignment planning extracts, weekly capacity analysis using the seven daily hour columns, and integration feeds that must publish schedule data tagged with a system status code. Consumers should note the inner join behavior: schedules carrying a status code that does not exist in PA_PROJECT_STATUSES will not appear in the result set.