Results for “pa_cc_tp_schedule_lines_v”

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

Overview

The view PA_CC_TP_SCHEDULE_LINES_V (owner APPS, status VALID) is a reporting and integration layer over the transfer price schedule lines used in Oracle Projects cross-charging. Transfer price schedules define the rules by which labor and non-labor transactions cross-charged between organizations are priced. Each schedule consists of one or more lines, and this view presents those lines together with the resolved provider organization name, receiver organization name, and the descriptive names of the labor and non-labor transfer price rules referenced on each line. The object is documented as part of the PA - Projects product in ETRM for Oracle EBS 12.1.1 and 12.2.2.

Because the view denormalizes organizational and rule identifiers into names, it is the natural source for concurrent programs, Oracle Business Intelligence / XML Publisher reports, and inbound integration logic that must display or validate a transfer price schedule without re-implementing the language-sensitive joins against the HR organization views.

Underlying Base Objects

The view text selects from PA_CC_TP_SCHEDULE_LINES (referenced in the ETRM metadata through the synonym of the same name) as the driving table, aliased TPSL. It outer-joins to PA_CC_TP_RULES twice — once for the labor rule and once for the non-labor rule — and to the HR organization views to obtain organization names. The documented referenced base objects are:

• PA_CC_TP_SCHEDULE_LINES (synonym) — the schedule line records themselves.
• PA_CC_TP_RULES (view) — transfer price rule definitions used for labor (LABOR_TP_RULE_ID) and non-labor (NL_TP_RULE_ID).
• HR_ORG_UNITS_NO_JOIN (view) and HR_ALL_ORGANIZATION_UNITS_TL (synonym) — joined separately for provider and receiver organizations to resolve the translated organization names.
• HR_GENERAL, HR_SECURITY, FND_PROFILE, and PA_CROSS_BUSINESS_GRP (packages) — supporting security, language, and cross-business-group logic inherited through the HR organization views.

The joins to HR_ORG_UNITS_NO_JOIN, HR_ALL_ORGANIZATION_UNITS_TL, and PA_CC_TP_RULES are all outer joins (note the (+) operators), so a schedule line is still returned even when the organization or rule reference cannot be resolved or is null.

Key Columns

• TP_SCHEDULE_LINE_ID — primary key of the transfer price schedule line.
• TP_SCHEDULE_ID — the parent transfer price schedule to which the line belongs.
• PRVDR_ORGANIZATION_ID / PRVDR_ORGANIZATION_NAME — the providing organization and its resolved, language-appropriate name.
• RECVR_ORGANIZATION_ID — the receiving organization; its name is resolved through the second HR organization join.
• LABOR_TP_RULE_ID and NL_TP_RULE_ID — the transfer price rules applied to labor and non-labor transactions respectively.
• LABOR_PERCENTAGE_APPLIED and NL_PERCENTAGE_APPLIED — the percentage of the rule applied to each transaction class.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range of the line.
• DEFAULT_FLAG — indicates whether the line is the default for the schedule.
• SORT_ORDER — determines evaluation sequence of lines.
• TP_AMT_TYPE_CODE — the transfer price amount type classification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes reviewing the composition of a transfer price schedule, printing schedule line detail for a given provider/receiver pairing, and auditing which lines are flagged as default. A representative query lists the active lines for a schedule:

• SELECT tp_schedule_line_id, prvdr_organization_name, recvr_organization_id, labor_tp_rule_id, nl_tp_rule_id, start_date_active, end_date_active, default_flag FROM pa_cc_tp_schedule_lines_v WHERE tp_schedule_id = :p_schedule_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE) ORDER BY sort_order;
• SELECT tp_schedule_line_id, prvdr_organization_name, labor_percentage_applied, nl_percentage_applied FROM pa_cc_tp_schedule_lines_v WHERE default_flag = 'Y';
• SELECT tp_schedule_line_id, tp_amt_type_code, attribute1, attribute2 FROM pa_cc_tp_schedule_lines_v WHERE tp_schedule_id = :p_schedule_id;

Because the view exposes resolved organization names, it is preferred over the base PA_CC_TP_SCHEDULE_LINES table for reporting, while the base table remains the correct target for DML performed through the supported Projects APIs.