Results for “psp_schedule_lines_u1”

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

Overview

PSP.PSP_SCHEDULE_LINES is a transactional table within the Oracle EBS Project Billing and Costing schema (PSP), designed to store the schedule lines associated with a particular schedule. Each row defines the charging instructions that govern how costs are distributed across a defined period, identifying the GL account, project, task, expenditure organization, expenditure type, and award to which a line is charged, together with the schedule percentage and begin and end dates. The table operates in the ETRM 12.1.1 and 12.2.2 environments and is owned by the PSP schema with FND Design Data registered as PSP.PSP_SCHEDULE_LINES. The object status is VALID, and its storage resides in the APPS_TS_TX_DATA tablespace with PCT Free 10.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. This suggests modeling PSP_SCHEDULE_LINES as a satellite attached to the schedule hierarchy hub rather than as an independent hub or link, since its attributes describe the characteristics of a schedule line rather than representing an autonomous business entity.

Key Information Stored

The table is defined with 39 documented columns. The principal columns include:

• SCHEDULE_LINE_ID — the surrogate primary key (NUMBER, 15), uniquely identifying each schedule line and enforced through the unique index PSP_SCHEDULE_LINES_U1. This is the sole documented business-key candidate.
• SCHEDULE_HIERARCHY_ID — foreign key to PSP_SCHEDULE_HIERARCHY, linking the line to its parent schedule.
• SCHEDULE_BEGIN_DATE and SCHEDULE_END_DATE — the begin and end dates of the period governed by the charging instructions. Both are indexed through nonunique indexes PSP_SCHEDULE_LINES_N1 and PSP_SCHEDULE_LINES_N2 respectively.
• SCHEDULE_PERCENT — the percentage of time charged using the charging instructions on the line.
• GL_CODE_COMBINATION_ID — the GL account charged.
• PROJECT_ID, TASK_ID, and AWARD_ID — the project, task, and award to which the line is charged.
• EXPENDITURE_ORGANIZATION_ID and EXPENDITURE_TYPE — the expenditure organization and expenditure type charged.
• SET_OF_BOOKS_ID and BUSINESS_GROUP_ID — the ledger and business group context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield structure and segments.

Several columns are documented as not currently used, including ENCUMBER_STATUS_CODE, DEFAULT_FLAG, and WARNING_CODE.

Common Use Cases and Queries

Typical reporting on this table retrieves the charging instructions for a schedule across a date range or reconstructs the distribution of costs per project, task, or award. A common pattern joins the schedule hierarchy to filter lines for an active schedule:

• Select all lines where SCHEDULE_BEGIN_DATE and SCHEDULE_END_DATE bracket a reporting period, using PSP_SCHEDULE_LINES_N1 and N2 for efficient range access.
• Aggregate SCHEDULE_PERCENT by PROJECT_ID, TASK_ID, or AWARD_ID to validate that distribution percentages reconcile to expected totals.
• Join to PSP_DISTRIBUTION_LINES on SCHEDULE_LINE_ID to trace the actual distribution transactions generated from each schedule line.
• Query by GL_CODE_COMBINATION_ID to report charging instructions by GL account for accounting reconciliation.

Because the table stores date-bounded instructions, historical schedules may contain multiple lines per project or task, and queries should filter on the applicable period rather than assuming a single active line.

Related Objects

• PSP_SCHEDULE_HIERARCHY — parent schedule; joined on SCHEDULE_HIERARCHY_ID.
• PSP_DISTRIBUTION_LINES — references this table via SCHEDULE_LINE_ID and holds generated distribution records.
• PSP_DISTRIBUTION_LINES_HISTORY — historical distribution records also referencing SCHEDULE_LINE_ID.
• PA_PROJECTS_ALL — joined on PROJECT_ID for project attributes.
• PA_TASKS — joined on TASK_ID.
• PA_EXPENDITURE_TYPES — joined on EXPENDITURE_TYPE.
• GL_CODE_COMBINATIONS — joined on GL_CODE_COMBINATION_ID.
• GL_SETS_OF_BOOKS — joined on SET_OF_BOOKS_ID.
• IGF_AW_AWARD_ALL — joined on AWARD_ID for award information.
• HR_ALL_ORGANIZATION_UNITS — joined on EXPENDITURE_ORGANIZATION_ID and BUSINESS_GROUP_ID.