Results for “pay_date_basis_lookup_code”

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

Overview

The APPS.PO_VENDOR_SITES_PAY_AP_V view is a Payables-owned reporting object that consolidates supplier site payment attributes into a single, denormalized result set. It is defined in the APPS schema and its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. Although the object is prefixed with "PO_", its base data is drawn entirely from Payables (AP) and Payments (IBY) tables, and it is documented under the AP - Payables product. The view presents one row per supplier site, enriched with supplier-level, terms, distribution set, withholding tax, territory, and external payee information.

Its principal role is to support reporting, extensions, and integrations that require supplier site payment behavior without navigating the full normalized AP_SUPPLIER_SITES structure. Because the view exposes payment control flags — including HOLD_FUTURE_PAYMENTS_FLAG, HOLD_ALL_PAYMENTS_FLAG, ALWAYS_TAKE_DISC_FLAG, EXCLUDE_FREIGHT_FROM_DISCOUNT, and PAYMENT_PRIORITY — it is frequently referenced when analyzing payment holds, discount behavior, and disbursement configuration.

Underlying Base Objects

The view is defined over a join of AP_SUPPLIER_SITES (aliased PVS) with AP_SUPPLIERS, IBY_EXTERNAL_PAYEES_ALL, FND_TERRITORIES_VL, AP_TERMS, AP_DISTRIBUTION_SETS_ALL, and AP_AWT_GROUPS. Lookup display values are resolved through AP_LOOKUP_CODES, and FND_GLOBAL is referenced for session context. Collectively these documented references are:

• AP_SUPPLIER_SITES — the primary source of site-level attributes.
• AP_SUPPLIERS — supplier header context.
• IBY_EXTERNAL_PAYEES_ALL — payee party, payment function, bank charge bearer, settlement priority, and exclusive payment flag.
• FND_TERRITORIES_VL — territory short name for the site country.
• AP_TERMS — terms name for the site's payment terms.
• AP_DISTRIBUTION_SETS_ALL — distribution set name.
• AP_AWT_GROUPS — withholding tax group names (both invoice and payment AWT groups).
• AP_LOOKUP_CODES — displayed field values for lookup-backed columns.
• FND_GLOBAL — session/user/org context via the FND_GLOBAL package.

The join structure means the view inherits the multi-org behavior of AP_SUPPLIER_SITES; ORG_ID is exposed as a column so that operating unit filtering remains explicit in downstream queries.

Key Columns

• VENDOR_SITE_ID, VENDOR_SITE_CODE, VENDOR_ID — primary site identifiers and the owning supplier.
• HOLD_FUTURE_PAYMENTS_FLAG — site-level indicator controlling whether future payments are held; central to payment hold analysis.
• HOLD_ALL_PAYMENTS_FLAG — indicates that all payments for the site are held regardless of due date.
• PAYMENT_PRIORITY, PAY_GROUP_LOOKUP_CODE, PAYMENT_CURRENCY_CODE — disbursement sequencing and currency defaults.
• TERMS_ID, TERMS_NAME, TERMS_DATE_BASIS, TERMS_DATE_BASIS_DISP — payment terms and the date basis used for due-date calculation.
• ACCTS_PAY_CODE_COMBINATION_ID, PREPAY_CODE_COMBINATION_ID — liability and prepayment accounting flexfield references.
• INVOICE_AMOUNT_LIMIT, DISTRIBUTION_SET_ID, DISTRIBUTION_SET_NAME — invoice controls applied at the site.
• ALLOW_AWT_FLAG, AWT_GROUP_ID, AWT_GROUP_NAME, PAY_AWT_GROUP_ID, PAY_AWT_GROUP_NAME — withholding tax configuration.
• EXCLUDE_FREIGHT_FROM_DISCOUNT, ALWAYS_TAKE_DISC_FLAG — discount calculation behavior.
• ACTIVE_FLAG — derived via DECODE/SIGN logic against INACTIVE_DATE versus SYSDATE, returning 'Y' or 'N'.
• PAYEE_PARTY_ID, PAYMENT_FUNCTION, BANK_CHARGE_BEARER, SETTLEMENT_PRIORITY, EXCLUSIVE_PAYMENT_FLAG — sourced from IBY_EXTERNAL_PAYEES_ALL for payment processing.
• ORG_ID — operating unit discriminator.

Common Use Cases and Queries

A frequent scenario is auditing sites with future payment holds. The following query lists active sites and their hold configuration:

SELECT vendor_site_code, vendor_id, hold_future_payments_flag, hold_all_payments_flag, payment_priority, org_id
FROM apps.po_vendor_sites_pay_ap_v
WHERE active_flag = 'Y'
  AND NVL(hold_future_payments_flag,'N') = 'Y';

Another common use is joining the view to invoice or payment data to reconcile site hold flags against scheduled payments. Because the view already resolves TERMS_NAME, DISTRIBUTION_SET_NAME, and territory short name, it is also used for supplier master data extracts and interfaces into external payment or ERP systems. The ORG_ID column must be applied when results should be restricted to a single operating unit, and NVL handling on the flags is recommended because several indicator columns permit nulls.