Search Results pos_acnt_pay_pref




Overview
Explore in AI Chat

Overview

The table POS.POS_ACNT_PAY_PREF is a transactional data object within the Oracle E-Business Suite iSupplier Portal (product code POS). It stores the payment preferences that a supplier defines for each of its registered addresses, allowing the buying organization and the supplier self-service portal to negotiate and persist payment methods, currencies, and notification channels at the party-site level. The object is classified with status VALID in schemas spanning Oracle EBS 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, the FK structure — with references to HZ_PARTIES and HZ_PARTY_SITES — suggests this object behaves as a link entity, resolving relationships between a trading partner, an address site, and payment terms. It is not a pure hub (its primary key is a surrogate identifier rather than a natural business key), nor a standalone satellite, because it carries attributes that qualify the party/site association.

Key Information Stored

The table contains 13 documented columns. The most business-significant include:

Common Use Cases and Queries

Typical scenarios include supplier onboarding validation, payment preference reporting, and reconciliation of portal-entered data against payables setup. A representative query joins the preference record back to its party and site context:

SELECT paf.payment_preference_id,
       paf.party_id,
       paf.party_site_id,
       paf.payment_currency_code,
       paf.invoice_currency_code,
       paf.payment_method,
       paf.notification_method
FROM   pos.pos_acnt_pay_pref paf,
       hz_parties          hp,
       hz_party_sites      hps
WHERE  paf.party_id      = hp.party_id
AND    paf.party_site_id = hps.party_site_id
AND    paf.party_id      = :p_party_id;

Reporting use cases include auditing suppliers that maintain multiple payment currencies per site, identifying sites with mismatched invoice and payment currencies, and feeding downstream payment templates. Because the table is owned by the POS schema, care should be taken to respect access controls; read-only queries via a reporting schema are preferable to direct DML.

Related Objects

The most significant related objects, per documented FK relationships, are:

  • HZ_PARTIES — join column PARTY_ID; the parent trading partner entity.
  • HZ_PARTY_SITES — join column PARTY_SITE_ID; the address site to which each preference is scoped.
  • HZ_LOCATIONS — indirectly referenced via party sites to resolve physical address details.
  • HZ_CUST_ACCOUNTS — often co-queried to reconcile supplier account context with payment preference.
  • POS_SUPPLIER_CONTACTS — companion iSupplier Portal table for contact-level attributes.
  • IBY_PAYMENT_METHODS / IBY_FNDCPT_PMT_CHANNEL_TL — reference data for PAYMENT_METHOD and notification values.

These relationships make POS_ACNT_PAY_PREF a practical link between the TCA party model and downstream payments processing in the iSupplier Portal.