Results for “pos_acnt_pay_pref_u1”

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

Overview

The POS.POS_ACNT_PAY_PREF table is a transactional table in the Oracle E-Business Suite Procurement and Payables schemas that stores supplier payment preferences at the address (party site) level. It functions as a preference repository that records how a supplier party or a specific supplier address should be paid, including currency and payment method selections. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes reside in APPS_TS_TX_IDX. It is documented as VALID in ETRM for both 12.1.1 and 12.2.2 and is owned by the POS schema. From a Data Vault modeling perspective, the mined relationship classification suggests this table behaves as a link entity: it resolves the association between a supplier party, a supplier address, and a payment preference configuration, with the payment preference identifier acting as the hub-like surrogate. The unique index POS_ACNT_PAY_PREF_U1 on PAYMENT_PREFERENCE_ID — the object the user searched for — confirms the primary key PAF_PK.

Key Information Stored

The table contains 13 documented columns. The most significant are summarized below.

• PAYMENT_PREFERENCE_ID (NUMBER 15) — Surrogate primary key (PAF_PK) and the single column of the unique business-key candidate index POS_ACNT_PAY_PREF_U1. This is the pointer referenced by dependent views and APIs.
• PARTY_ID (NUMBER 15) — Party identifier of the supplier; foreign key to HZ_PARTIES. Indexed non-uniquely by POS_ACNT_PAY_PREF_N1.
• PARTY_SITE_ID (NUMBER 15) — Party site identifier of the supplier address; foreign key to HZ_PARTY_SITES. Indexed non-uniquely by POS_ACNT_PAY_PREF_N2. Preferences are held at the address level, which makes this column the practical scope of the preference.
• PAYMENT_CURRENCY_CODE (VARCHAR2 15) — Currency in which the supplier prefers to be paid.
• INVOICE_CURRENCY_CODE (VARCHAR2 15) — Currency in which invoices are expected from the supplier at that site.
• PAYMENT_METHOD (VARCHAR2 30) — Method of disbursement (for example, check, electronic, wire).
• NOTIFICATION_METHOD (VARCHAR2 30) — How the supplier should be notified regarding payment activity.
• OBJECT_VERSION_NUMBER (NUMBER 15) — Optimistic locking column used by the underlying framework.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard Who columns for audit and row-level provenance.

There are no mandatory flags documented, but PARTY_ID, PARTY_SITE_ID, and PAYMENT_PREFERENCE_ID are effectively required in practice to make a preference row meaningful.

Common Use Cases and Queries

Typical uses include supplier payment preference maintenance, address-level disbursement review, and integration with payables processes that determine the currency or method for a payment. A frequent query pattern resolves preferences for a given supplier party:

• Look up all preferences for a supplier: SELECT * FROM POS.POS_ACNT_PAY_PREF WHERE PARTY_ID = :party_id;
• Look up preferences for a specific supplier address: SELECT * FROM POS.POS_ACNT_PAY_PREF WHERE PARTY_SITE_ID = :party_site_id;
• Retrieve a single preference row by its surrogate key: SELECT * FROM POS.POS_ACNT_PAY_PREF WHERE PAYMENT_PREFERENCE_ID = :payment_preference_id;
• Reporting joins against HZ_PARTIES and HZ_PARTY_SITES to display supplier name and address alongside the payment and invoice currency codes and payment method.

Because the unique index POS_ACNT_PAY_PREF_U1 is on the surrogate key, queries should not assume uniqueness on PARTY_ID or PARTY_SITE_ID alone; those are non-unique indexes intended for lookup path optimization.

Related Objects

• HZ_PARTIES — Referenced by PARTY_ID; provides supplier party attributes.
• HZ_PARTY_SITES — Referenced by PARTY_SITE_ID; provides supplier address attributes.
• POS.POS_ACNT_PAY_PREF (APPS synonym/view) — The APPS-layer object that exposes this table to concurrent programs and responsibilities.
• POS_ACNT_PAY_PREF_U1 / _N1 / _N2 — Indexes that support direct retrieval, party-based lookup, and address-based lookup respectively.

APIs and package logic that depend on this table typically resolve the payment preference for a supplier site before payment, and any customization should respect the Object Version Number for safe concurrent updates.