Search Results calc_method_code

Overview

PA_CC_TP_RULES_V is an APPS-schema view in the Oracle E-Business Suite Projects (PA) module that stores the rules defining how transfer price is calculated between internal organizations, business groups, and cross-charging relationships. Transfer pricing rules govern the markup or rate applied when one operating unit or project organization provides services, labor, or deliverables to another. The view presents a consolidated, business-facing projection of the underlying PA_CC_TP_RULES base table, resolving schedule identifiers into descriptive names so that reporting and integration layers can present rule definitions without additional joins.

Because the view is defined as a UNION ALL of three branches keyed on R1.CALC_METHOD_CODE, it exposes a single homogeneous row shape for what are logically distinct calculation methods: method 'A' covers rules with no rate schedule (SCHEDULE_ID IS NULL), method 'B' covers indirect rate schedule rules joined to PA_IND_RATE_SCHEDULES, and the third branch covers standard bill rate schedule rules resolved against schedule and organization name references. This design means consumers querying PA_CC_TP_RULES_V see all transfer price rule variants through one interface, which is the principal value of the view for reporting and integration.

Underlying Base Objects

The view is defined over PA_CC_TP_RULES (itself a view over the physical rule table), with the second branch additionally joining PA_IND_RATE_SCHEDULES to obtain the indirect rate schedule name, and the third branch referencing PA_STD_BILL_RATE_SCHEDULES_ALL and organization name sources to resolve standard bill rate schedule and organization descriptions. Documented base objects include FND_PROFILE, HR_GENERAL, HR_OPERATING_UNITS, HR_ORGANIZATION_UNITS, HR_SECURITY, PA_CROSS_BUSINESS_GRP, PA_UTILS, and PA_STD_BILL_RATE_SCHEDULES_ALL. The presence of HR_SECURITY and HR_OPERATING_UNITS indicates that organization-level security and operating unit context are applied when rows are surfaced, which is critical in multi-organization deployments.

PA_CROSS_BUSINESS_GRP governs cross-business-group validation, and PA_UTILS provides shared date and lookup utilities. The view therefore sits atop a security-aware stack: rules are not simply read from a flat table but are filtered and enriched according to the accessing responsibility and organization hierarchy.

Key Columns

• TP_RULE_ID — primary identifier for the transfer price rule.
• BUSINESS_GROUP_ID — the business group that owns the rule.
• NAME and DESCRIPTION — user-facing rule name and descriptive text.
• RULE_TYPE — classifies the rule's purpose.
• MARKUP_CALC_BASE_CODE — identifies the base against which the markup is calculated; this is the column most commonly searched for, and it determines whether markup applies to cost, raw cost, burden, or another base amount.
• CALC_METHOD_CODE — 'A' indicates a percentage-based rule without a schedule, 'B' indicates an indirect rate schedule rule, and the additional branch handles standard bill rate schedule rules.
• PERCENTAGE_APPLIED — the markup percentage where applicable.
• SCHEDULE_ID — the rate schedule reference for schedule-driven rules.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range controlling when the rule applies.
• IND_RATE_SCH_NAME, STD_BILL_RATE_SCHEDULE, and organization name columns — denormalized descriptive fields populated by the UNION ALL branches.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield segments.

Common Use Cases and Queries

Typical usage is to enumerate active transfer pricing rules by calculation method and markup base, to validate configuration before cross-charging runs, and to feed downstream reporting or integration extracts. The following query lists active percentage-based rules with their markup calculation base:

SELECT tp_rule_id, name, markup_calc_base_code, calc_method_code, percentage_applied FROM apps.pa_cc_tp_rules_v WHERE calc_method_code = 'A' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

A second common pattern joins the view to rate schedules or operating units to reconcile schedule-driven rules, filtering on the resolved IND_RATE_SCH_NAME. Because organization security is enforced via HR_SECURITY and HR_OPERATING_UNITS, queries should be run under a responsibility whose organization context includes the rules of interest. Reporting extracts frequently filter by MARKUP_CALC_BASE_CODE to group rules by their markup foundation, and by BUSINESS_GROUP_ID to scope output to a single business group.