Search Results plsql_agent

Overview

AP_EXPENSE_FEED_DISTS_OPEN_V is a Payables (AP) view owned by the APPS schema that exposes the open expense feed distributions generated by Oracle Payables for Self-Service Expenses. It joins recorded expense feed distributions (AP_EXPENSE_FEED_DISTS) with their parent feed lines (AP_EXPENSE_FEED_LINES), enriching the result with procurement card context from the AP Cards, Card Profiles, and Card Programs tables, together with employee and payer instrument information. In Oracle EBS 12.1.1 and 12.2.2 the view is the documented source used to verify Open Transactions in Self-Service Expenses, meaning it drives the inquiry and validation screens that users rely on to confirm which corporate card charges are still awaiting reconciliation to an expense report or invoice. Because the view consolidates distribution-level amounts, accounting flexfield references, card merchant detail, tax information, and currency conversion data, it also functions as a practical integration surface for external reporting tools, AP reconciliation extracts, and custom concurrent programs that must identify unreconciled procurement card activity.

Underlying Base Objects

The view is defined primarily over the synonym AP_EXPENSE_FEED_DISTS, aliased EFD, which supplies the distribution-level records: feed identifiers, invoice and invoice line references, amounts, the distribution code combination, and status attributes. It is joined to AP_EXPENSE_FEED_LINES (EFL), which contributes the card-level transaction detail, including the employee, card, and program identifiers. Corporate card descriptive data is drawn from AP_CARDS, AP_CARD_PROFILES, and AP_CARD_PROGRAMS, while IBY_FNDCPT_PAYER_ALL_INSTRS_V supplies the payment instrument card number. Supporting objects include AP_LOOKUP_CODES for status and type meanings, HR_EMPLOYEES_CURRENT_V, HR_PERSON_NAME, HR_SECURITY, and HR_GENERAL for employee identity and security-based filtering, and the FND packages FND_GLOBAL, FND_PROFILE, FND_CURRENCY, and FND_HTTP_TICKET for organizational context, profile option resolution, currency handling, and payment processing connectivity.

Key Columns

The distribution side of the view exposes FEED_LINE_ID, FEED_DISTRIBUTION_ID, INVOICE_ID, and INVOICE_LINE_ID, which establish the link between the feed record and the resulting Payables invoice. AMOUNT carries the distribution amount, DIST_CODE_COMBINATION_ID identifies the accounting flexfield combination, and STATUS_LOOKUP_CODE together with STATUS_CHANGE_DATE and INVOICED_FLAG communicate the current reconciliation state and whether the charge has been invoiced. MANAGER_APPROVAL_ID and EMPLOYEE_VERIFICATION_ID support the approval and verification workflow. Card and transaction attributes include CARD_ID, CARD_PROGRAM_ID, CARD_NUMBER, REFERENCE_NUMBER, ALT_REFERENCE_NUMBER, TRANSACTION_DATE, POSTED_DATE, RECORD_TYPE, MERCHANT_NAME, MERCHANT_NUMBER, merchant address fields, and CUSTOMER_CODE. Financial and tax columns include LINE_AMOUNT, ORIGINAL_CURRENCY_AMOUNT, ORIGINAL_CURRENCY_CODE, POSTED_CURRENCY_CODE, CURRENCY_CONVERSION_RATE, TAX_PAID_FLAG, TAX_AMOUNT, TAX_RATE, and TAX_TYPE, along with the corresponding ALT_ tax and merchant tax identifier columns. Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE) and fifteen ATTRIBUTE flexfield columns are also present, and ORG_ID supports multi-org filtering.

Common Use Cases and Queries

Typical usage includes reconciling open procurement card charges, verifying distribution amounts and account coding before invoice creation, and populating custom reporting on unsubmitted or unapproved card transactions. Because the view is secured through HR security and profile-based org context, queries should be run with an appropriate APPS responsibility or explicit ORG_ID predicate.

• List open card distributions with merchant and amount: SELECT feed_distribution_id, card_number, merchant_name, amount, status_lookup_code FROM apps.ap_expense_feed_dists_open_v WHERE org_id = :p_org_id AND invoiced_flag = 'N';
• Reconcile card charges to invoices: SELECT e.invoice_id, e.invoice_line_id, e.reference_number, e.line_amount, e.posted_currency_code FROM apps.ap_expense_feed_dists_open_v e WHERE e.invoice_id IS NOT NULL;
• Audit tax treatment on card transactions: SELECT reference_number, merchant_name, tax_paid_flag, tax_amount, tax_rate FROM apps.ap_expense_feed_dists_open_v WHERE tax_paid_flag = 'Y';

All queries should account for the view's dependency on HR security functions, which may restrict rows to those employees visible to the querying user.