Results for “project_expenditure_type”

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

Overview

POFV_REQUISITION_DISTRIBUTIONS is a retrofitted Oracle E-Business Suite view owned by the APPS schema in the Purchasing (PO) product family. It presents a denormalized, reporting-oriented projection of requisition distribution data, combining the transactional distribution records in PO_REQ_DISTRIBUTIONS_ALL with their parent requisition lines, requisition headers, operating units, sets of books, accounting flexfield combinations, project and task attributes, and Oracle Contract Core deliverable references. The view is intended for inquiry, reporting, and integration scenarios where a single flat record is required for each requisition distribution, including its encumbrance, funds-check, tax, and project accounting context.

The name and structure follow the standard Oracle "FV" (form/view) convention used for descriptive, multi-table views that support Oracle Forms-based inquiry or external extracts. It is marked VALID in 12.1.1 and 12.2.2 and is exposed for read access through APPS.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_REQ_DISTRIBUTIONS_ALL (synonym) — the primary distribution table (aliased RD), supplying distribution ID, quantity, amounts, accounting, encumbrance, and tax attributes.
• PO_REQUISITION_LINES_ALL (synonym) — parent requisition lines (RL), supplying line number, drop-ship flag, and header linkage.
• PO_REQUISITION_HEADERS_ALL (synonym) — requisition headers (RH), supplying the requisition number (SEGMENT1).
• HR_ALL_ORGANIZATION_UNITS (synonym) — operating unit name (OP.NAME) via RD.ORG_ID.
• GL_SETS_OF_BOOKS (view) and GL_CODE_COMBINATIONS (synonym) — set of books name and four accounting flexfield combinations: charge (CC), budget (BC), accrual (AC), and variance (VC).
• PA_PROJECTS_ALL (synonym) and PA_TASKS (synonym) — project name and task number for project-related distributions.
• OKC_K_LINES_B (synonym) and OKE_K_DELIVERABLES_B (synonym) — contract line number and deliverable number references.

Joins are established through REQUISITION_LINE_ID, REQUISITION_HEADER_ID, ORG_ID, and the respective ID columns, making the view a fully resolved distribution-level record.

Key Columns

• DISTRIBUTION_ID / DISTRIBUTION_NUM — primary key and user-visible distribution identifier.
• REQUISITION_LINE_ID / REQUISITION_HEADER_ID / SEGMENT1 / LINE_NUM — requisition lineage.
• REQ_LINE_QUANTITY / REQ_LINE_AMOUNT / REQ_LINE_CURRENCY_AMOUNT — distribution quantity and monetary values. The distribution_quantity sought by the user corresponds to REQ_LINE_QUANTITY, the quantity allocated to the distribution.
• GL_CANCELLED_DATE / GL_CLOSED_DATE / ENCUMBERED_FLAG / ENCUMBERED_AMOUNT / GL_ENCUMBERED_DATE / GL_ENCUMBERED_PERIOD_NAME — encumbrance and funding lifecycle.
• CODE_COMBINATION_ID / BUDGET_ACCOUNT_ID / ACCRUAL_ACCOUNT_ID / VARIANCE_ACCOUNT_ID — accounting flexfields, resolved through _KF descriptors.
• PROJECT_ID / TASK_ID / EXPENDITURE_TYPE / EXPENDITURE_ITEM_DATE — project accounting attributes.
• RECOVERABLE_TAX / NONRECOVERABLE_TAX / RECOVERY_RATE / TAX_RECOVERY_OVERRIDE_FLAG — tax recovery details.
• Descriptive _DF and _LA descriptor columns expose PO_REQ_DISTRIBUTIONS as the base table and decodable lookup meanings.

Common Use Cases and Queries

Typical uses include auditing requisition-to-accounting flow, reconciling encumbrance balances, extracting project-related requisitions, and reporting tax recovery on distributions. A sample query to list distributions with quantity and account:

SELECT distribution_num,
       segment1,           -- requisition number
       line_num,
       req_line_quantity,  -- distribution_quantity equivalent
       req_line_amount,
       name                -- operating unit
FROM   apps.pofv_requisition_distributions
WHERE  segment1 = :requisition_number;

To find project-related distributions:

SELECT distribution_id, segment1, line_num, req_line_quantity, project_id, task_id
FROM   apps.pofv_requisition_distributions
WHERE  project_related_flag = 'Y';

Because the view resolves lookups and flexfields into descriptive columns, it is well suited to BI Publisher extracts and downstream integration feeds that require requisition distribution context without additional lookup joins.