Search Results pa_cc_tp_schedule_lines




Overview
Explore in AI Chat

Overview

The PA_CC_TP_SCHEDULE_LINES table is a core data structure within the Oracle E-Business Suite Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the detailed repository for the individual lines that constitute a transfer price schedule. In the context of Oracle Projects, transfer pricing governs the internal charging of costs between different segments of an organization, such as from a performing organization to a funding organization. This table is essential for defining the multi-tiered rules and rates that apply to different cost types, enabling complex, rule-based internal billing and cost allocation across projects and tasks.

Key Information Stored

While the full column list is not provided in the excerpt, the documented foreign key relationships and primary key reveal the table's critical components. Each record is uniquely identified by the TP_SCHEDULE_LINE_ID column, which serves as the primary key. The table's structure is designed to link each schedule line to its parent schedule and to the specific pricing rules applied. The key relational columns include TP_SCHEDULE_ID, which ties the line to its parent header record in PA_CC_TP_SCHEDULES_BG. Furthermore, it stores references to distinct pricing rules for different cost categories: LABOR_TP_RULE_ID for labor costs and NL_TP_RULE_ID for non-labor costs, both linking to the PA_CC_TP_RULES_BG table. Additional columns typically define the effective date range, sequence, and applicable conditions (e.g., task, expenditure type, or organization) for the schedule line.

Common Use Cases and Queries

This table is central to processes involving the generation of internal cross-charge transactions. Common operational and reporting scenarios include validating the active pricing rules for a given project task and cost type, auditing the hierarchy of transfer price schedules, and troubleshooting charge calculation discrepancies. A typical query might join this table to its related objects to retrieve a complete, effective schedule for reporting.

Sample Query Pattern:
SELECT sched_line.TP_SCHEDULE_LINE_ID,
sched_line.TP_SCHEDULE_ID,
sched_header.SCHEDULE_NAME,
labor_rule.RULE_NAME AS LABOR_RULE,
nl_rule.RULE_NAME AS NON_LABOR_RULE
FROM PA.PA_CC_TP_SCHEDULE_LINES sched_line,
PA.PA_CC_TP_SCHEDULES_BG sched_header,
PA.PA_CC_TP_RULES_BG labor_rule,
PA.PA_CC_TP_RULES_BG nl_rule
WHERE sched_line.TP_SCHEDULE_ID = sched_header.TP_SCHEDULE_ID
AND sched_line.LABOR_TP_RULE_ID = labor_rule.TP_RULE_ID(+)
AND sched_line.NL_TP_RULE_ID = nl_rule.TP_RULE_ID(+)
AND sched_header.SCHEDULE_NAME = '&SCHEDULE_NAME';

Related Objects

The PA_CC_TP_SCHEDULE_LINES table has defined dependencies on several key tables, as documented by its foreign key constraints:

  • PA_CC_TP_SCHEDULES_BG: This is the parent header table. Each line is linked to a single schedule via the column PA_CC_TP_SCHEDULE_LINES.TP_SCHEDULE_ID referencing PA_CC_TP_SCHEDULES_BG.
  • PA_CC_TP_RULES_BG (Labor Rule): The table references this rules table twice. The first relationship is for labor costs, where PA_CC_TP_SCHEDULE_LINES.LABOR_TP_RULE_ID references PA_CC_TP_RULES_BG.
  • PA_CC_TP_RULES_BG (Non-Labor Rule): The second relationship is for non-labor costs, where PA_CC_TP_SCHEDULE_LINES.NL_TP_RULE_ID also references PA_CC_TP_RULES_BG, potentially pointing to a different rule record.

This table is also likely referenced by various transactional and reporting views within the Projects module, which aggregate schedule data for application logic and user interfaces.