Results for “labor_percentage_applied”

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

Overview

PA_CC_TP_SCHEDULE_LINES is the transactional child table that stores the individual transfer price schedule lines belonging to a transfer price schedule in Oracle Projects. In Oracle EBS 12.1.1 and 12.2.2, transfer pricing governs the rates at which internal provider organizations charge receiving (receiver) organizations for labor, non-labor, or cross-charged work, and this table holds the row-level detail that defines those rates over time. Each row represents a single effective-dated pricing line that binds a provider organization to a receiver organization, an active period, and the transfer price rules and amounts that apply. The parent schedule, held in PA_CC_TP_SCHEDULES_BG, provides the header context, while this table provides the ordered, dated detail consumed during cost distribution and cross-charge processing.

From a Data Vault modeling perspective, the FK structure mined from the metadata suggests classifying this object as a link table. The two directional foreign keys to PA_CC_TP_RULES_BG (LABOR_TP_RULE_ID and NL_TP_RULE_ID) and the reference to PA_CC_TP_SCHEDULES_BG position it as an associative structure connecting schedules, rules, and organizations rather than a standalone hub or a descriptive satellite.

Key Information Stored

The surrogate primary key is TP_SCHEDULE_LINE_ID, implemented through the PA_CC_TP_SCHEDULE_LINES_PK constraint. This is the single-column unique identifier for each schedule line. The table also carries unique index PA_CC_TP_SCHEDULE_LINES_U1 on the same column and a compound business-key candidate, PA_CC_TP_SCHEDULE_LINES_U2, formed from TP_SCHEDULE_ID, PRVDR_ORGANIZATION_ID, START_DATE_ACTIVE, RECVR_ORGANIZATION_ID, END_DATE_ACTIVE, and TP_AMT_TYPE_CODE. The compound key confirms that a schedule line is uniquely determined by its schedule, provider, receiver, effective date range, and transfer price amount type.

• TP_SCHEDULE_ID — foreign key linking the line to its parent schedule in PA_CC_TP_SCHEDULES_BG.
• PRVDR_ORGANIZATION_ID — the provider organization supplying the transfer price.
• RECVR_ORGANIZATION_ID — the receiving organization being charged.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the active date window for the line.
• LABOR_TP_RULE_ID and NL_TP_RULE_ID — foreign keys to PA_CC_TP_RULES_BG defining the labor and non-labor transfer price rules.
• LABOR_PERCENTAGE_APPLIED and NL_PERCENTAGE_APPLIED — the percentages applied to labor and non-labor amounts.
• TP_AMT_TYPE_CODE — the transfer price amount type, part of the business key.
• SORT_ORDER — controls the display and evaluation ordering of lines within a schedule.
• DEFAULT_FLAG — indicates whether the line is the default for its schedule context.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the 15 ATTRIBUTE/ATTRIBUTE_CATEGORY descriptive flexfield columns support auditing and extensibility.

Common Use Cases and Queries

Typical usage centers on validating effective-dated transfer pricing configurations, tracing which rule governs a provider-to-receiver charge, and reporting scheduled rates by organization and period. A frequent pattern retrieves all active lines for a schedule:

SELECT TP_SCHEDULE_LINE_ID, PRVDR_ORGANIZATION_ID, RECVR_ORGANIZATION_ID, START_DATE_ACTIVE, END_DATE_ACTIVE, LABOR_TP_RULE_ID, NL_TP_RULE_ID, TP_AMT_TYPE_CODE FROM PA.PA_CC_TP_SCHEDULE_LINES WHERE TP_SCHEDULE_ID = :p_schedule_id AND TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE ORDER BY SORT_ORDER;

Because effective dates and rules may overlap, reconciliation queries commonly join to PA_CC_TP_RULES_BG to verify the rule name behind each LABOR_TP_RULE_ID or NL_TP_RULE_ID, and grouping by TP_AMT_TYPE_CODE helps detect duplicate or conflicting lines. The DEFAULT_FLAG column is useful for identifying fallback pricing when a specific provider-receiver pair is not explicitly configured.

Related Objects

• PA_CC_TP_SCHEDULES_BG — parent schedule table, joined via TP_SCHEDULE_ID.
• PA_CC_TP_RULES_BG — transfer price rule definitions, joined through LABOR_TP_RULE_ID and NL_TP_RULE_ID.
• PA_CC_TP_SCHEDULE_LINE_LKP — lookup table referencing this table via TP_SCHEDULE_LINE_ID.
• PA_CC_TP_SCHEDULE_LINES_PK / U1 / U2 — the primary and unique index constraints enforcing line identity.
• Oracle Projects cross-charge and cost distribution processes — consume these lines during transfer price calculation and internal billing.

When troubleshooting transfer price disputes, verify that line date ranges do not overlap for a given provider, receiver, and amount type, and confirm that each rule foreign key resolves to a valid, active row in PA_CC_TP_RULES_BG.