Results for “client_extension_flag”

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

Overview

The PA_ALLOC_AUDIT_BASIS_V view is a Projects (PA) module reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the basis-level audit detail generated during a cost allocation run, allowing implementers and analysts to inspect the source amounts, basis percentages and line percentages that Oracle Projects used when distributing indirect costs across projects and tasks. The view is read-only and is defined in the ETRM metadata with a status of VALID.

The view is primarily consumed by allocation audit reports, reconciliation extracts and custom diagnostics that need to explain how an allocation run arrived at a particular distributed amount. It is not a transactional entry point; it is a denormalised projection that joins the run basis detail to project and task descriptive information, and it derives a resource name at query time through a PL/SQL function call.

Underlying Base Objects

The documented base objects are:

• PA_ALLOC_RUN_BASIS_DET (synonym) — the primary driver table, aliased PABD, holding run-level basis detail rows including amounts, basis percent, line percent and the sign of the line number.
• PA_PROJECTS_ALL (synonym) — aliased PP, supplying SEGMENT1 and NAME for the project.
• PA_TASKS (synonym) — aliased PT, supplying TASK_NUMBER and TASK_NAME.
• PA_ALLOC_UTILS (package) — invoked as PA_ALLOC_UTILS.RESOURCE_NAME to resolve the basis resource name from the resource list member and rule identifiers.

The joins are equated on PROJECT_ID between the basis detail and PA_PROJECTS_ALL, and on TASK_ID between the basis detail and PA_TASKS. All objects referenced are synonyms resolved to the APPS-owned definitions.

Key Columns

• RUN_ID — identifier of the allocation run to which the basis row belongs.
• LINE_NUMBER — the basis line number, normalised through DECODE(SIGN(...), -1, ABS(...), ...) so that negative-marker lines are reported as positive values.
• PROJECT_NUMBER / PROJECT_NAME — the project segment and name from PA_PROJECTS_ALL.
• TASK_NUMBER / TASK_NAME — the task description from PA_TASKS.
• RESOURCE_NAME — the basis resource resolved via PA_ALLOC_UTILS.RESOURCE_NAME('BASIS', ...).
• BASIS_AMOUNT — the underlying amount from PABD.AMOUNT against which the basis applies.
• BASIS_PERCENT — the basis percentage contributed by the row; this is the column most commonly searched for as basis_percent.
• LINE_PERCENT — the line percentage for the row.
• EFFECTIVE_PERCENT — computed as (BASIS_PERCENT * LINE_PERCENT)/100, giving the net percentage applied.
• CLIENT_EXTENSION_FLAG — flag derived from the sign of the line number; 'Y' when the original line number is negative, otherwise 'N'.

Common Use Cases and Queries

Typical uses include auditing a specific allocation run, reconciling basis percentages against the rules defined for the run, and validating the effective percentage applied to each project/task. A representative query is:

• SELECT run_id, line_number, project_number, task_number, resource_name, basis_amount, basis_percent, line_percent, effective_percent FROM pa_alloc_audit_basis_v WHERE run_id = :p_run_id ORDER BY line_number;
• To isolate rows where the basis percentage is non-zero: SELECT * FROM pa_alloc_audit_basis_v WHERE basis_percent <> 0;
• To identify client-extension lines: SELECT * FROM pa_alloc_audit_basis_v WHERE client_extension_flag = 'Y';

Because RESOURCE_NAME is resolved through a PL/SQL function, queries benefit from restrictive predicates on RUN_ID to limit function invocations. No DML should be issued against the view; it is strictly a read-only audit projection.