Results for “claim_currency”

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

Overview

The OZF_CUST_TRD_PRFLS_ALL table, owned by the OZF schema within the Oracle E-Business Suite Trade Management module, stores trade customer profiles. It functions as the central configuration repository that links a customer or supplier party to the trade management behaviors governing that relationship, including auto-payment, claim handling, payment instrument preferences, and tolerance thresholds. Because the table carries the _ALL suffix and an ORG_ID column, it is partitioned by operating unit in a multi-org context, allowing distinct trade profile settings per organization. It is available in both EBS 12.1.1 and 12.2.2.

Under the heuristic Data Vault classification derived from the foreign-key structure, this object is best modeled as a link table. It does not behave as a standalone hub, since it lacks a purely intrinsic, single-source business entity identity; instead it associates multiple reference dimensions — customer accounts, parties, vendors, and vendor sites — into a single trade profile record. This modeling suggestion reflects the table's role as a relationship carrier between customer and supplier master data and trade-specific attributes.

Key Information Stored

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

• TRADE_PROFILE_ID — the surrogate primary key, defined by the constraint OZF_CUST_TRD_PRFLS_ALL_PK and reinforced by the unique index OZF_CUST_TRD_PRFLS_ALL_U1. It uniquely identifies each trade profile row.
• CUST_ACCOUNT_ID and CUST_ACCT_SITE_ID, SITE_USE_ID — foreign keys identifying the customer account, account site, and site use to which the profile applies.
• PARTY_ID — the TCA party owning the profile, linking to HZ_PARTIES.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_SITE_CODE — supplier identifiers, indicating the table can also hold profiles for vendor-side trade relationships.
• AUTOPAY_FLAG, AUTOPAY_PERIODICITY, AUTOPAY_PERIODICITY_TYPE — control the automated payment behavior for the trade profile.
• CLAIM_THRESHOLD and CLAIM_CURRENCY — define the monetary limit and currency for claim processing.
• PAYMENT_METHOD and DISCOUNT_TYPE — capture the preferred settlement and discount treatment.
• HEADER_TOLERANCE_OPERAND, HEADER_TOLERANCE_CALC_CODE, LINE_TOLERANCE_OPERAND, LINE_TOLERANCE_CALC_CODE — configure header- and line-level tolerance logic for claims.
• POS_WRITE_OFF_THRESHOLD and NEG_WRITE_OFF_THRESHOLD — bound positive and negative write-off amounts.
• UN_EARNED_PAY_ALLOW_TO, UN_EARNED_PAY_THOLD_AMOUNT, UN_EARNED_PAY_THOLD_FLAG, UN_EARNED_PAY_THOLD_TYPE — govern unearned payment allowances.
• ORG_ID, SECURITY_GROUP_ID, CREATED_FROM, REQUEST_ID, PROGRAM_ID and WHO columns (LAST_UPDATE_DATE, CREATED_BY, etc.) — provide multi-org, security, and reference/audit context.
• The 15 ATTRIBUTE columns and CONTEXT/ATTRIBUTE_CATEGORY — support the standard Oracle DFF extensibility framework.

The primary key TRADE_PROFILE_ID is a system-generated surrogate. No separate user-facing business-key unique index is documented beyond the seed profile identifier itself.

Common Use Cases and Queries

Typical usage centers on retrieving and maintaining a customer's trade payment and claim configuration, and on driving automated payment and claim-tolerance logic across operating units.

SELECT tp.trade_profile_id, tp.cust_account_id,
       tp.autopay_flag, tp.claim_threshold,
       tp.payment_method, tp.pos_write_off_threshold
FROM   ozf.ozf_cust_trd_prfls_all tp,
       hz_cust_accounts ca
WHERE  tp.cust_account_id = ca.cust_account_id
AND    tp.org_id = :p_org_id
AND    NVL(tp.autopay_flag,'N') = 'Y';

Reporting scenarios include auditing auto-payment entitlements, reconciling claim thresholds to actual deductions, and extracting tolerance settings for mass updates. Because the table is multi-org, most queries should filter on ORG_ID or rely on MOAC (Multi-Org Access Control) policy.

Related Objects

• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID.
• HZ_CUST_ACCT_SITES_ALL — joined via CUST_ACCT_SITE_ID.
• HZ_CUST_SITE_USES_ALL — joined via SITE_USE_ID.
• HZ_PARTIES — joined via PARTY_ID.
• PO_VENDORS — joined via VENDOR_ID.
• PO_VENDOR_SITES_ALL — joined via VENDOR_SITE_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID.

These relationships confirm the profile's spanning function between TCA customer data and supplier master data, coordinated through the Trade Management application's profile maintenance pages and concurrent programs.