Search Results ap_product_setup




Overview
Explore in AI Chat

Overview

AP_PRODUCT_SETUP is a Payables-owned configuration table in the AP schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the system-level options and defaults that govern how Oracle Payables operates across all operating units, providing the baseline behavior for supplier numbering, invoice entry, payment processing, and matching. Because it holds global setup rather than transactional records, it is a low-volume reference table, typically containing a single controlling row identified by RECORD_NUMBER. From a Data Vault modeling perspective, the mined relationship data classifies this table as standalone; a heuristic suggestion would treat it as a reference hub (or a single-row configuration satellite), given that no foreign-key dependencies were documented. Its influence is pervasive: many downstream Payables processes read these defaults during invoice validation, payment creation, and supplier registration.

Key Information Stored

The primary key is AP_PRODUCT_SETUP_PK, defined on RECORD_NUMBER. RECORD_NUMBER functions as the surrogate key; there is no documented business-key unique index, so column-level defaults act as the stable configuration values. The 21 documented columns include:

Common Use Cases and Queries

Typical scenarios include auditing global Payables configuration, verifying matching and hold policies before period close, and diagnosing why invoices received a particular default currency, terms, or payment method. A simple retrieval of the active configuration is:

  • SELECT terms_id, payment_method_lookup_code, match_option, hold_unmatched_invoices_flag FROM ap.ap_product_setup WHERE record_number = :record_number;
  • SELECT supplier_numbering_method, supplier_num_type, next_auto_supplier_num FROM ap.ap_product_setup;

Reporting uses include comparing configuration between environments, documenting setup during implementations, and confirming that ALWAYS_TAKE_DISC_FLAG or AUTO_CALCULATE_INTEREST_FLAG aligns with policy. Because the table is read-heavy and rarely changed, queries are inexpensive and can be safely joined to lookup views for descriptive values.

Related Objects

Since AP_PRODUCT_SETUP is classified as standalone, it exposes no documented foreign-key relationships. Nonetheless, its values are consumed by core Payables entities and processes:

  • AP_INVOICES_ALL — uses INVOICE_CURRENCY_CODE, TERMS_ID, and matching options as invoice defaults.
  • AP_PAYMENT_SCHEDULES_ALL — derives due dates and discount logic from TERMS_ID and ALWAYS_TAKE_DISC_FLAG.
  • AP_CHECKS_ALL and AP_INVOICE_PAYMENTS_ALL — reference PAYMENT_METHOD_LOOKUP_CODE and pay date basis defaults.
  • AP_SUPPLIERS — governed by SUPPLIER_NUMBERING_METHOD, SUPPLIER_NUM_TYPE, and NEXT_AUTO_SUPPLIER_NUM.
  • AP_TERMS — the source of TERMS_ID values referenced by this setup table.
  • AP_LOOKUP_CODES — supplies values for PAYMENT_METHOD_LOOKUP_CODE, PAY_DATE_BASIS_LOOKUP_CODE, and SUPPLIER_PAY_GROUP_LOOKUP_CODE.
  • Payables Setup and Open Interface concurrent programs — read these defaults during invoice import and payment processing.