Search Results failed_funds_lookup_code

Overview

The APPS.AP_PO_DISTRIBUTIONS_AP2_V view is a retrofitted Payables (AP) object that exposes purchase order distribution data with Payables-specific derivations applied on top of the underlying purchasing distribution records. Within Oracle EBS 12.1.1 and 12.2.2 the view serves as a reporting and integration layer over PO_DISTRIBUTIONS, resolving the account context and descriptive attributes required by AP accounting, encumbrance, and funds-check processing.

The most significant behavioral difference between the view and its base synonym is the conditional resolution of CODE_COMBINATION_ID. Rather than exposing the raw column, the view applies a DECODE that inspects DESTINATION_TYPE_CODE and ACCRUE_ON_RECEIPT_FLAG, returning ACCRUAL_ACCOUNT_ID or the original CODE_COMBINATION_ID depending on whether the distribution represents expense accrual accounting. This makes the view suitable for downstream logic that must mirror the accounting entry Payables would actually generate.

Because the view retains columns such as FAILED_FUNDS_LOOKUP_CODE, it is frequently located by users investigating failed funds reservations and budget-check outcomes, particularly in encumbrance-enabled environments.

Underlying Base Objects

The view is defined in the APPS schema and is documented as referencing the following objects in ETRM 12.2.2:

• PO_DISTRIBUTIONS (SYNONYM) — the primary driving object, aliased as PD, supplying all column-level data and the ROWID exposed as ROW_ID.
• HR_ALL_ORGANIZATION_UNITS_TL and HR_ORG_UNITS_NO_JOIN — used to resolve the expenditure organization name exposed as EXPENDITURE_ORGANIZATION.
• PER_PEOPLE_F, HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY — support person-name derivation and organization security filtering.
• PA_PROJECTS_ALL, PA_TASKS_EXPEND_V, PA_TASK_UTILS, and PA_UTILS4 — provide project and task context for project-related distributions.
• FND_PROFILE — retrieves profile option values that govern view behavior, such as organization or operating unit context.

The dependence on HR and PA packages means the view respects organization security and project expenditure rules rather than exposing unfiltered purchasing data.

Key Columns

• ROW_ID — the ROWID of the underlying PO_DISTRIBUTIONS row, enabling row-level addressing.
• CODE_COMBINATION_ID — conditionally derived account; the central accounting column of the view.
• ACCRUAL_ACCOUNT_ID and ACCRUED_FLAG / ACCRUE_ON_RECEIPT_FLAG — drive accrual accounting logic.
• FAILED_FUNDS_LOOKUP_CODE — indicates the reason a funds reservation failed; central to budget-check troubleshooting.
• ENCUMBERED_AMOUNT, ENCUMBERED_FLAG, GL_ENCUMBERED_DATE, GL_ENCUMBERED_PERIOD_NAME — encumbrance state and GL posting context.
• DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, DELIVER_TO_LOCATION_ID, DELIVER_TO_PERSON_ID — destination and receiving context.
• EXPENDITURE_ORGANIZATION, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE — derived expenditure attributes for costing and projects.
• AMOUNT_BILLED, DISTRIBUTION_NUM, GL_CANCELLED_DATE, GL_CLOSED_DATE — invoicing and GL lifecycle columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context.

Common Use Cases and Queries

Typical usage targets funds-check failures, encumbrance reconciliation, and account derivation validation.

• Identifying distributions with failed funds reservations by filtering on FAILED_FUNDS_LOOKUP_CODE IS NOT NULL.
• Reconciling encumbered amounts against GL encumbrance periods.
• Verifying which account Payables would use, given accrual flags.

Sample query returning failed-funds distributions with their derived account and organization:

SELECT row_id,
       distribution_num,
       code_combination_id,
       failed_funds_lookup_code,
       encumbered_amount,
       expenditure_organization,
       destination_type_code
  FROM apps.ap_po_distributions_ap2_v
 WHERE failed_funds_lookup_code IS NOT NULL
 ORDER BY distribution_num;

Because the view joins HR security and PA structures, queries should be executed within an appropriately initialized APPS session to avoid unexpected row suppression.