Search Results expenditure_organization_code




Overview
Explore in AI Chat

Overview

POFV_PO_DISTRIBUTIONS is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module, documented under ETRM with the annotation "Retrofitted." It presents a denormalized, presentation-layer perspective on purchase order distribution records, joining the transactional distribution table PO_DISTRIBUTIONS_ALL to its parent shipment, line, header, release, requisition, project, and receiving context, along with descriptive flexfield and key flexfield references. The view exposes both the operative identifiers of the distribution (PO_DISTRIBUTION_ID, DISTRIBUTION_NUM) and human-readable descriptions such as vendor segment numbers, organization names, deliver-to persons, and code combination references.

Its principal role is to support Oracle Forms-based inquiry and reporting. The view text contains embedded bind markers — for example '_LA:PS.SHIPMENT_TYPE:PO_LOOKUP_CODES:SHIPMENTTYPE:DISPLAYED_FIELD', '_LA:PD.ACCRUE_ON_RECEIPT_FLAG:PO_LOOKUP_CODES:YES/NO:DISPLAYED_FIELD', '_KF:SQLGL:GL#:CC' — which instruct the Forms runtime to translate coded values into user-facing meanings via PO_LOOKUP_CODES and SQLGL key flexfield resolution. Consequently, the view is intended for query and display rather than as a source for high-volume ETL; consumers needing raw data should generally query PO_DISTRIBUTIONS_ALL directly.

Underlying Base Objects

The view is defined over more than two dozen documented base objects, all owned or referenced through the APPS schema. Its central driving object is PO_DISTRIBUTIONS_ALL, joined outward through a consistent chain of primary keys.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list distributions together with the expenditure organization code, which corresponds to the organization code joined from the expenditure organization identifier. The following sample returns distribution-level detail with expenditure organization context:

  • Expenditure organization reporting: SELECT distribution_num, segment1 po_number, line_num, shipment_num, ec.organization_code expenditure_organization_code, eo.name expenditure_organization, quantity_ordered, quantity_billed, amount_billed FROM apps.pofv_po_distributions WHERE expenditure_organization_id IS NOT NULL ORDER BY segment1, line_num;
  • Encumbrance and funds-check analysis: SELECT segment1, distribution_num, encumbered_amount, unencumbered_amount, gl_encumbered_period_name, failed_funds_lookup_code FROM apps.pofv_po_distributions WHERE encumbered_flag = 'Y';
  • Accrual versus non-accrual review: SELECT segment1, distribution_num, accrue_on_receipt_flag, accrued_flag, quantity_delivered, quantity_billed FROM apps.pofv_po_distributions WHERE accrue_on_receipt_flag = 'Y' AND accrued_flag = 'N';
  • Project-charged distribution listing: SELECT segment1, line_num, distribution_num, pj.name project_name, tk.task_number, expenditure_type FROM apps.pofv_po_distributions WHERE project_id IS NOT NULL;
  • Destination inventory and subinventory view: SELECT segment1, distribution_num, dc.organization_code destination_org, destination_subinventory, deliver_to_location_id FROM apps.pofv_po_distributions;

Because the view is APPS-owned and Retrofit-maintained, queries should be issued against APPS.POFV_PO_DISTRIBUTIONS and account for organization-level security where HR_SECURITY is applied. For bulk extraction or integration, the underlying PO_DISTRIBUTIONS_ALL and its joined base tables remain the preferred source.