Search Results allow_cross_charge_flag

Overview

PJM_TASKS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PJM (Project Manufacturing) product family. It exposes a flattened, denormalized projection of project task information, combining task-level attributes drawn from the Projects foundation with human-readable project identifiers. The view carries a status of VALID in both the 12.1.1 and 12.2.2 releases, and its definition is documented in the ETRM repository as a "Tasks view."

Functionally, PJM_TASKS_V does not store data of its own. It presents the caller with a stable, read-only interface over the Projects task model, resolving surrogate keys such as PROJECT_ID and TASK_ID into descriptive values. Because it encapsulates the name and number resolution logic inside the view definition, downstream reports, concurrent programs, and integrations can retrieve project and task context without repeatedly embedding the same conversion calls or join conditions. This makes the view particularly useful where project-manufacturing transactions must be validated against, or annotated with, chargeable task structures.

Underlying Base Objects

The documented view text selects exclusively from PA_TASKS_EXPEND_V, aliased as T, and projects a subset of its columns. The ETRM metadata further records the referenced base objects as FND_PROFILE (package), PA_IMPLEMENTATIONS_ALL (synonym), PA_LOOKUPS (view), PA_PROJECTS_ALL (synonym), PA_TASKS (synonym), and PA_TASK_UTILS (package). These objects sit beneath the expenditure view and supply the task records, lookup decoding, implementation-level configuration, and utility logic required to resolve identifiers.

Two conversion calls appear directly in the view text: PJM_PROJECT.ALL_PROJ_IDTONUM, which derives the PROJECT_NUMBER from PROJECT_ID, and PJM_PROJECT.ALL_PROJ_IDTONAME, which derives the PROJECT_NAME. These functions return the displayable project number and name, so the resulting view presents both the internal numeric keys and the business-facing identifiers side by side.

Key Columns

• PROJECT_ID — Surrogate key of the project, carried through from PA_TASKS_EXPEND_V.
• PROJECT_NUMBER — Project number resolved via PJM_PROJECT.ALL_PROJ_IDTONUM.
• PROJECT_NAME — Project name resolved via PJM_PROJECT.ALL_PROJ_IDTONAME.
• TASK_ID — Surrogate key of the task.
• TASK_NUMBER — Business identifier of the task.
• TASK_NAME — Descriptive name of the task.
• WBS_SORT_ORDER — Ordering value that reflects the task's position in the work breakdown structure.
• START_DATE and COMPLETION_DATE — Scheduled start and completion dates for the task.
• BILLABLE_FLAG — Indicates whether the task is billable.
• CHARGEABLE_FLAG — Indicates whether the task may receive charges.
• ALLOW_CROSS_CHARGE_FLAG — Indicates whether cross-charge processing is permitted for the task. This is the column most directly associated with the search term "allow_cross_charge_flag," and it is exposed without transformation from PA_TASKS_EXPEND_V.

Common Use Cases and Queries

The view is typically queried to list valid tasks for a project, to validate chargeability before posting project-manufacturing transactions, and to drive cross-charge eligibility logic. A representative query retrieves all cross-chargeable tasks for a given project:

SELECT project_number, project_name, task_number, task_name, allow_cross_charge_flag FROM apps.pjm_tasks_v WHERE project_id = :p_project_id AND allow_cross_charge_flag = 'Y' ORDER BY wbs_sort_order;

A second common pattern filters on the chargeable and billable indicators to identify tasks that may accept cost or be invoiced, while a third joins the view to PJM manufacturing transaction tables on TASK_ID to enrich work order or job detail with the project and task names. Because the view performs identifier resolution through packaged functions, queries against it should be constrained by PROJECT_ID or TASK_ID wherever possible to avoid unnecessary function invocations across the full result set.