Search Results get_tp_amt_type_code

Overview

APPS.PA_TASKS_EXPEND_V is a reporting view in Oracle EBS Project Accounting (PA) that exposes task-level expenditure attributes for projects. It is defined as a join across PA_TASKS, PA_PROJECTS_ALL, and the PA_LOOKUPS view, filtered by the profile option PA_TASKS_DISPLAYED. The view presents both base task data (project identifier, task identifier, task number, task name, dates, chargeable and billable flags, rate information) and supplementary derived attributes, including a WBS sort order string and two values resolved through package functions: the work type name and the task pricing amount type code. Its role is primarily to support inquiry and reporting screens that need a flattened, cross-organization view of project tasks with expenditure-relevant attributes, rather than as a transactional base table.

Underlying Base Objects

The view's SELECT statement joins PA_TASKS (aliased T), PA_PROJECTS_ALL (aliased P), and PA_LOOKUPS (aliased LU) on task-to-project and lookup criteria. The documented referenced objects extend beyond those three: FND_PROFILE (package), PA_ALTERNATE_TASKS, PA_IMPLEMENTATIONS, PA_RBS_ELEMENTS, PA_TASK_UTILS (package), and PA_UTILS4 (package). FND_PROFILE supplies the PA_TASKS_DISPLAYED value used to restrict rows to CHARGEABLE, LOWEST, or ALL tasks. PA_LOOKUPS provides the PA_TASKS_TO_DISPLAY lookup driving that filter. PA_TASK_UTILS supplies SORT_ORDER_TREE_WALK and CHECK_CHILD_EXISTS for hierarchical ordering and lowest-level filtering. PA_UTILS4 supplies GET_WORK_TYPE_NAME and GET_TP_AMT_TYPE_CODE, the latter being the function most relevant to the search term "get_tp_amt_type_code." PA_IMPLEMENTATIONS is referenced in the EXISTS subquery that enforces organization-level implementation checks, and PA_RBS_ELEMENTS and PA_ALTERNATE_TASKS support related task and resource structures.

Key Columns

• PROJECT_ID / PROJECT_NUMBER — Project identifier and the SEGMENT1 project number from PA_PROJECTS_ALL.
• TASK_ID / TASK_NUMBER / TASK_NAME — Core task identity columns from PA_TASKS.
• TASK_NAME (indented form) — DECODE over the PA_TASKS_TO_DISPLAY lookup; when lookup code is ALL, the name is left-padded by WBS level for hierarchical display.
• WBS_SORT_ORDER — SUBSTR of either PA_TASK_UTILS.SORT_ORDER_TREE_WALK (when lookup code is ALL) or TASK_NUMBER, providing a navigable WBS ordering key.
• START_DATE / COMPLETION_DATE — Task scheduling dates.
• CHARGEABLE_FLAG / BILLABLE_FLAG / ALLOW_CROSS_CHARGE_FLAG — Flags controlling charging and billing behavior.
• PROJECT_RATE_DATE / PROJECT_RATE_TYPE / TASKFUNC_COST_RATE_TYPE / TASKFUNC_COST_RATE_DATE / LABOR_COST_MULTIPLIER_NAME — Rate and cost multiplier attributes relevant to expenditure and costing.
• WORK_TYPE_ID / WORK_TYPE_NAME — Work type identifier and name resolved via PA_UTILS4.GET_WORK_TYPE_NAME.
• TP_AMT_TYPE_CODE — Task pricing amount type code resolved via PA_UTILS4.GET_TP_AMT_TYPE_CODE, truncated to 200 characters.
• DESCRIPTION / ORG_ID / CARRYING_OUT_ORGANIZATION_ID — Task description and organizational context.

Common Use Cases and Queries

The view is typically queried to populate task selection lists and expenditure inquiry pages, especially where the caller needs the derived TP amount type code alongside task identifiers. A representative query retrieving the pricing amount type code for chargeable tasks is:

SELECT project_number, task_number, task_name, tp_amt_type_code, work_type_name FROM apps.pa_tasks_expend_v WHERE chargeable_flag = 'Y' ORDER BY project_number, wbs_sort_order;

Because TP_AMT_TYPE_CODE is generated by PA_UTILS4.GET_TP_AMT_TYPE_CODE, callers searching for "get_tp_amt_type_code" use this view as a read-only conduit to that function's output without invoking the package directly. Filtering by ORG_ID or PROJECT_ID supports multi-organization and project-specific reporting, while the WBS_SORT_ORDER column enables hierarchical report output consistent with Project Accounting inquiry screens.