Search Results federal_reportable_flag




Overview
Explore in AI Chat

Overview

APPS.PO_VENDORS_ACTIVE_AP_V is a reporting view in Oracle E-Business Suite that exposes currently active supplier records from the Purchasing and Payables vendor model. It is defined over the PO_VENDORS base view and filters the supplier master down to those rows whose effective date range brackets the current system date and whose enabled flag is set to 'Y'. Because it strips out inactive, disabled, and date-expired suppliers, the view functions as a convenient, pre-filtered supplier list for operational reporting, concurrent programs, and integration extracts that should only consider valid, usable supplier records.

The view is owned by the APPS schema and is therefore callable from any session with the standard APPS grants. In EBS 12.1.1 and 12.2.2 alike, PO_VENDORS is itself a view over the supplier tables (AP_SUPPLIERS / PO_VENDOR_SITES_ALL lineage), so PO_VENDORS_ACTIVE_AP_V is effectively a second-level view that layers an active-date and enabled-status predicate on top of the supplier master.

Underlying Base Objects

Per the documented ETRM metadata, the only referenced base object is PO_VENDORS (VIEW). No direct table dependencies are declared, which means all column derivation and filtering logic is inherited from PO_VENDORS and its own underlying supplier tables. The WHERE clause is the distinguishing feature of this view:

  • SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE - 1) AND NVL(END_DATE_ACTIVE, SYSDATE + 1) — ensures only suppliers active as of today are returned. The NVL defaults mean a null start date is treated as already effective and a null end date as never expiring.
  • ENABLED_FLAG = 'Y' — restricts output to suppliers that have not been disabled.

Because PO_VENDORS consolidates both Purchasing and Payables supplier attributes, this view is a cross-module convenience object rather than a Payables-only or Purchasing-only construct.

Key Columns

The projection list is deliberately narrow and reporting-oriented:

  • VENDOR_ID — surrogate primary key identifying the supplier record; the primary join key to downstream tables.
  • VENDOR_NAME and VENDOR_NUMBER (SEGMENT1) — descriptive supplier identifiers.
  • VENDOR_TYPE_LOOKUP_CODE — supplier classification (e.g., supplier, employee, external).
  • TYPE_1099 — derived via DECODE(FEDERAL_REPORTABLE_FLAG, 'Y', TYPE_1099, ''). It returns the supplier's 1099 type only when the federal reportable flag is 'Y'; otherwise it returns an empty string. This column is the direct target of the user's "type_1099" search.
  • NUM_1099 — the supplier's 1099 tax identification number.
  • EMPLOYEE_ID — linkage to an employee where the supplier is also an employee.
  • VAT_REGISTRATION_NUM — tax registration identifier for VAT reporting.
  • AWT_GROUP_ID and ALLOW_AWT_FLAG — withholding tax grouping and eligibility.
  • HOLD_ALL_PAYMENTS_FLAG — indicates whether all payments to the supplier are currently on hold.
  • PARTY_ID — the TCA party identifier, enabling joins to the trading community model.

Common Use Cases and Queries

Typical uses include 1099 reporting eligibility checks, withholding tax analysis, payment-hold monitoring, and integration extracts that must exclude inactive suppliers. For example, to list active federally reportable suppliers and their 1099 classification:

  • SELECT vendor_id, vendor_name, vendor_number, type_1099, num_1099 FROM apps.po_vendors_active_ap_v WHERE type_1099 IS NOT NULL AND TYPE_1099 != '';
  • To find active suppliers with payment holds: SELECT vendor_id, vendor_name FROM apps.po_vendors_active_ap_v WHERE hold_all_payments_flag = 'Y';
  • To join supplier parties to TCA: SELECT v.vendor_name, p.party_name FROM apps.po_vendors_active_ap_v v, apps.hz_parties p WHERE v.party_id = p.party_id;

Because the view calls SYSDATE and applies NVL-based date logic, results vary by run date; use it for current-state reporting rather than historical point-in-time analysis, which should query PO_VENDORS or the underlying supplier tables directly.