Results for “psp_schedule_lines”

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

Overview

PSP_SCHEDULE_LINES is a table in the PSP (Labor Distribution) product of Oracle E-Business Suite, owned by the PSP schema. It stores schedule lines associated with a particular schedule, forming the operational backbone of labor cost allocation and encumbrance processing. Each row represents an individual scheduling instruction — defining how a labor dollar should be distributed across an accounting code combination, project, task, expenditure type, and expenditure organization over a defined date range.

This table sits at the heart of the PSP scheduling model. It is populated when users define a labor distribution schedule, and it is consumed downstream by the distribution and distribution history tables that drive actual payroll costing results. Because schedules reference GL code combinations, projects, tasks, awards, and expenditure types simultaneously, the table also functions as a flexible costing template. The AWARD_ID column indicates integration with Oracle Grants Management (IGF_AW_AWARD_ALL), supporting grant-funded labor allocation scenarios.

From a Data Vault modeling perspective, the metadata suggests a satellite-leaning classification. This is a modeling suggestion, not a documented fact. The table carries many descriptive attributes (schedule percent, begin/end dates, encumbrance status, attributes) but those attributes would typically be grouped as an effectivity satellite. The defining business keys are the surrogate SCHEDULE_LINE_ID, the foreign key SCHEDULE_HIERARCHY_ID that ties the line to a parent schedule structure, and the composite of GL_CODE_COMBINATION_ID, PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE that qualifies the costing intent.

Key Information Stored

The table contains 39 documented columns in ETRM 12.2.2. The most important are:

• SCHEDULE_LINE_ID — the surrogate primary key (PSP_SCHEDULE_LINES_PK) and the unique business-key candidate captured in PSP_SCHEDULE_LINES_U1.
• SCHEDULE_HIERARCHY_ID — foreign key to PSP_SCHEDULE_HIERARCHY, tying the line to a parent schedule.
• GL_CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS, the accounting distribution target.
• PROJECT_ID, TASK_ID, AWARD_ID — foreign keys to PA_PROJECTS_ALL, PA_TASKS, and IGF_AW_AWARD_ALL, respectively, defining the project/task/grant charge context.
• EXPENDITURE_TYPE — foreign key to PA_EXPENDITURE_TYPES, categorizing the labor cost.
• EXPENDITURE_ORGANIZATION_ID and BUSINESS_GROUP_ID — both foreign keys to HR_ALL_ORGANIZATION_UNITS, defining the owning organization context.
• SET_OF_BOOKS_ID — foreign key to GL_SETS_OF_BOOKS, identifying the ledger.
• SCHEDULE_BEGIN_DATE, SCHEDULE_END_DATE, POETA_START_DATE, POETA_END_DATE — effective date ranges governing when the schedule line applies.
• SCHEDULE_PERCENT — the percentage of labor to allocate to this line.
• ENCUMBER_STATUS_CODE, DEFAULT_FLAG, WARNING_CODE — control flags governing encumbrance treatment and default behavior.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard Oracle DFF attribute set for extensibility.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit Who columns.

Common Use Cases and Queries

PSP_SCHEDULE_LINES is typically queried alongside its parent hierarchy and child distribution rows. A common reporting scenario retrieves all lines for a given schedule hierarchy:

SELECT sl.schedule_line_id, sl.schedule_percent,
       sl.schedule_begin_date, sl.schedule_end_date,
       cc.concatenated_segments, p.segment1 project_number
FROM   psp.psp_schedule_lines sl,
       gl_code_combinations_kfv cc,
       pa_projects_all p
WHERE  sl.gl_code_combination_id = cc.code_combination_id
AND    sl.project_id = p.project_id
AND    sl.schedule_hierarchy_id = :hierarchy_id;

Labor distribution analysis frequently joins PSP_SCHEDULE_LINES to PSP_DISTRIBUTION_LINES on SCHEDULE_LINE_ID to reconcile planned percentages against actually distributed payroll cost. Encumbrance reporting filters on ENCUMBER_STATUS_CODE and POETA_START_DATE/POETA_END_DATE. Period-based queries use SCHEDULE_BEGIN_DATE and SCHEDULE_END_DATE to find lines active in a pay period. Grant accountants join AWARD_ID to IGF_AW_AWARD_ALL to report sponsored labor by award.

Related Objects

• PSP_SCHEDULE_HIERARCHY — parent of this table, joined on SCHEDULE_HIERARCHY_ID.
• PSP_DISTRIBUTION_LINES — child table referencing PSP_SCHEDULE_LINES.SCHEDULE_LINE_ID, holding resulting labor cost distributions.
• PSP_DISTRIBUTION_LINES_HISTORY — historical child table also keyed on SCHEDULE_LINE_ID.
• GL_CODE_COMBINATIONS — joined on GL_CODE_COMBINATION_ID for account validation and reporting.
• PA_PROJECTS_ALL, PA_TASKS, PA_EXPENDITURE_TYPES — project costing dimension references.
• IGF_AW_AWARD_ALL — grant award reference via AWARD_ID.
• HR_ALL_ORGANIZATION_UNITS — referenced twice via EXPENDITURE_ORGANIZATION_ID and BUSINESS_GROUP_ID.
• GL_SETS_OF_BOOKS — ledger reference via SET_OF_BOOKS_ID.