Results for “ap_system_parameters_u1”

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

Overview

AP.AP_SYSTEM_PARAMETERS_ALL is the Oracle Payables configuration master table. It stores the operating parameters and cascading defaults that govern the entire Payables application for a given ledger, including functional currency, default payment terms, default accounts, matching and tolerance behavior, tax hierarchy, withholding tax, multi-currency handling, and payment processing options. The table corresponds directly to the Payables Options window in the EBS application, and the values defined here cascade to supplier sites, invoice entry, payment processing, and accounting.

Physically, the table is owned by the AP schema, resides in the APPS_TS_TX_DATA tablespace, and contains 183 documented columns in the 12.2.2 ETRM schema. Historically, a single row existed per installation; the presence of ORG_ID and a composite unique index in modern releases reflects the multi-org architecture and the MRC (Multiple Reporting Currencies) support. The ETRM dependency metadata also records AP_SYSTEM_PARAMETERS_PK on (SET_OF_BOOKS_ID, ORG_ID) as the primary key, with AP_SYSTEM_PARAMETERS_U1 (SET_OF_BOOKS_ID, ORG_ID) functioning as the unique business-key index. The heuristic Data Vault classification mined from the foreign-key structure is link, which is a reasonable modeling suggestion: the table resolves relationships between a ledger, its functional currency, and a large set of default accounting flexfield and payment objects rather than representing an independently identified business entity.

Key Information Stored

The identity of a row is anchored by SET_OF_BOOKS_ID (foreign key to GL_SETS_OF_BOOKS_11I) and ORG_ID, which together form both the declared primary key and the unique business-key candidate AP_SYSTEM_PARAMETERS_U1. There is no separate surrogate key column. The most operationally significant columns include:

• BASE_CURRENCY_CODE — the functional currency for the ledger, with a foreign key to FND_CURRENCIES.
• INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE — default currencies for invoice and payment entry; the payment currency must match the invoice currency or be an associated fixed-rate currency.
• ACCTS_PAY_CODE_COMBINATION_ID, SALES_TAX_CODE_COMBINATION_ID, DISC_LOST_CODE_COMBINATION_ID, DISC_TAKEN_CODE_COMBINATION_ID, GAIN_CODE_COMBINATION_ID, and LOSS_CODE_COMBINATION_ID — default accounting flexfield combinations referencing GL_CODE_COMBINATIONS, used for liability, tax, discount, and exchange gain/loss posting.
• TERMS_ID and PREPAYMENT_TERMS_ID — default payment terms applied to new invoices.
• DEFAULT_EXCHANGE_RATE_TYPE — default rate type, referencing GL_DAILY_CONVERSION_TYPES.
• ACCOUNTING_METHOD_OPTION and the posting option columns (EXPENSE_POST_OPTION, LIABILITY_POST_OPTION, CASH_POST_OPTION, FUTURE_PAY_POST_OPTION) — control when and how accounting entries are generated.
• AUTO_TAX_CALC_FLAG, MATCH_ON_TAX_FLAG, and TOLERANCE_ID — govern tax calculation and matching tolerance behavior, with TOLERANCE_ID referencing AP_TOLERANCE_TEMPLATES.
• ALLOW_AWT_FLAG, DEFAULT_AWT_GROUP_ID, and CREATE_AWT_INVOICES_TYPE — withholding tax configuration, with DEFAULT_AWT_GROUP_ID referencing AP_AWT_GROUPS.
• AUTOMATIC_OFFSETS_FLAG and ALLOW_FUTURE_PAY_FLAG — control offset generation and future-dated payment entry.
• CE_BANK_ACCT_USE_ID and BANK_ACCOUNT_ID — default bank account references to CE_BANK_ACCT_USES_ALL and AP_BANK_ACCOUNTS_ALL respectively.

Numerous legacy columns (INVOICE_NET_GROSS_FLAG, CHECK_OVERFLOW_LOOKUP_CODE, BATCH_CONTROL_FLAG) are documented as no longer used and should not be referenced in new development.

Common Use Cases and Queries

The most frequent requirement is retrieving the configuration for a ledger to drive downstream defaults or reporting. Because the table is keyed on SET_OF_BOOKS_ID and ORG_ID, joins to GL_SETS_OF_BOOKS_11I and to the accounting flexfield combinations are standard.

• Retrieve the functional currency and default payment terms for a ledger:
  SELECT set_of_books_id, org_id, base_currency_code, terms_id FROM ap_system_parameters_all WHERE set_of_books_id = :p_sob_id AND org_id = :p_org_id;
• Resolve default accounts to concatenated flexfield values by joining the *_CODE_COMBINATION_ID columns to GL_CODE_COMBINATIONS.
• Audit configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY, which are standard WHO columns.
• Report on matching tolerances and tax settings across ledgers by joining TOLERANCE_ID to AP_TOLERANCE_TEMPLATES and SERVICES_TOLERANCE_ID where applicable.
• Extract withholding tax and discount distribution configuration for tax and reconciliation reporting, joining DEFAULT_AWT_GROUP_ID to AP_AWT_GROUPS.

Because the table holds configuration rather than transactional data, it is typically accessed once per process to seed defaults and is rarely updated outside the Payables Options UI or approved APIs.

Related Objects

The FK metadata documents extensive relationships. The most significant are:

• GL_SETS_OF_BOOKS_11I — joined on SET_OF_BOOKS_ID; identifies the ledger owner of the parameter row.
• FND_CURRENCIES — joined on BASE_CURRENCY_CODE, INVOICE_CURRENCY_CODE, and PAYMENT_CURRENCY_CODE.
• GL_CODE_COMBINATIONS — referenced by multiple default account columns, including ACCTS_PAY_CODE_COMBINATION_ID, SALES_TAX_CODE_COMBINATION_ID, and the discount, gain/loss, and prepay combinations.
• GL_DAILY_CONVERSION_TYPES — joined on DEFAULT_EXCHANGE_RATE_TYPE.
• AP_TOLERANCE_TEMPLATES — joined on TOLERANCE_ID; defines matching tolerances.
• AP_AWT_GROUPS — joined on DEFAULT_AWT_GROUP_ID; defines withholding tax defaults.
• AP_BANK_ACCOUNTS_ALL and CE_BANK_ACCT_USES_ALL — joined on BANK_ACCOUNT_ID and CE_BANK_ACCT_USE_ID for default bank information.
• AP_INCOME_TAX_REGIONS — joined on INCOME_TAX_REGION for regional 1099/tax configuration.
• AP_EXPENSE_REPORTS_ALL — joined on EXPENSE_REPORT_ID for default expense report templates.
• HR_LOCATIONS_ALL — joined on LOCATION_ID for the default location used in document and payment formatting.

These relationships confirm the table's role as a configuration hub that links a ledger to the payment, accounting, tax, and banking objects that Payables depends upon.