Results for “tp_schedule_id”

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

Overview

PA_CC_TP_SCHEDULES_BG is a Projects (PA) module table that stores transfer price schedules. These schedules define the rules and rates by which transfer pricing is calculated between a provider organization and a receiver organization for cross-charged labor and non-labor transactions. In an Oracle E-Business Suite 12.1.1 or 12.2.2 environment, the table acts as the master definition of a transfer price schedule header; the individual pricing tiers or rate lines associated with a schedule are held in child tables rather than in this header itself. Transfer price schedules are a foundational component of cross-charge processing, allowing an enterprise to value internal labor and non-labor transfers consistently across projects and tasks.

The table resides in the PA schema and is owned by the Projects product. Based on the foreign key topology documented in the ETRM metadata, the heuristic Data Vault classification for this object is a hub. In Data Vault modeling terms, this suggests the table functions as a business-key-centric anchor that records the unique identity of each transfer price schedule, with descriptive and transactional attributes distributed to satellite or link structures. The surrogate key TP_SCHEDULE_ID anchors the hub, while business identity is captured by the unique index combination of BUSINESS_GROUP_ID and NAME.

Key Information Stored

The table contains 27 documented columns. The most significant are summarized below.

• TP_SCHEDULE_ID — Surrogate primary key (PA_CC_TP_SCHEDULES_BG_PK). Uniquely identifies each transfer price schedule and is the column referenced by all dependent foreign keys.
• BUSINESS_GROUP_ID — Operating unit / business group discriminator. Combined with NAME it forms the unique business-key candidate PA_CC_TP_SCHEDULES_U2.
• NAME — User-visible schedule name; together with BUSINESS_GROUP_ID constitutes the second unique index (PA_CC_TP_SCHEDULES_U2).
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range during which the schedule is active for cross-charge pricing. These support date-effective lookups and validation at transaction time.
• DESCRIPTION — Free-text description of the schedule's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns providing audit and concurrency context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The Oracle descriptive flexfield (DFF) columns, allowing customers to capture additional schedule-level attributes without schema changes.

The surplus of descriptive flexfield columns beyond the core identifiers reflects Oracle's standard extensibility pattern for setup-style master tables.

Common Use Cases and Queries

Transfer price schedules are queried primarily to resolve which pricing rule applies to a given provider/receiver cross-charge, and to audit how schedules are assigned to projects and tasks. A typical lookup joins the header to its lines:

• Resolve schedule header by name and business group: SELECT * FROM pa.pa_cc_tp_schedules_bg WHERE business_group_id = :bg AND name = :name; — leverages the PA_CC_TP_SCHEDULES_U2 unique index.
• Locate active schedules for a date: filter on start_date_active and end_date_active to return only schedules effective on the transaction date.
• Retrieve rate lines for a schedule: join to PA_CC_TP_SCHEDULE_LINES on TP_SCHEDULE_ID to obtain the detailed pricing structure.
• Audit schedule assignments: join to PA_PROJECTS_ALL and PA_TASKS on LABOR_TP_SCHEDULE_ID and NL_TP_SCHEDULE_ID to see which schedules govern labor versus non-labor cross-charges for a given project or task.
• Reporting: DFF attributes (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) are commonly exposed in custom cross-charge reconciliation and profitability reports.

Related Objects

The following objects reference or depend on PA_CC_TP_SCHEDULES_BG, based on documented foreign key relationships.

• PA_CC_TP_SCHEDULE_LINES — child table joined on TP_SCHEDULE_ID; holds the individual pricing lines for each schedule.
• PA_CC_TP_SCHEDULE_LINE_LKP — lookup table joined on TP_SCHEDULE_ID.
• PA_PROJECTS_ALL — referenced via LABOR_TP_SCHEDULE_ID and NL_TP_SCHEDULE_ID, defining which schedule applies to a project's labor and non-labor cross-charges.
• PA_TASKS — referenced via LABOR_TP_SCHEDULE_ID and NL_TP_SCHEDULE_ID, allowing schedule assignment at the task level.

Together these relationships show that PA_CC_TP_SCHEDULES_BG is the header hub of the cross-charge transfer pricing model, with pricing detail held in the schedule lines and usage assignments distributed across projects and tasks.