Search Results ozf_cust_trd_prfls_v




Overview
Explore in AI Chat

Overview

OZF_CUST_TRD_PRFLS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the Trade Management (OZF) product family. It presents customer trade profiles — the per-customer, per-site configuration records that govern how trade management transactions such as claims, accruals, and payments are processed for a trading partner. In EBS 12.1.1 and 12.2.2 the view is reported as VALID and exposes a denormalized image of OZF_CUST_TRD_PRFLS joined to the Trading Community Architecture (TCA) and Payables entities that give each profile row its business identity.

The view's practical role is to collapse the profile record and its surrounding descriptive attributes — party name, customer account number, site use code, and supplier name — into a single queryable surface. This is valuable for reporting, extracts, and integrations that require the trade profile configuration alongside human-readable identifiers without reproducing the multi-table join logic. Because it is a view rather than a table, it carries no storage of its own; it is a read-only projection and cannot be used as a DML target in supported customizations.

Underlying Base Objects

The view is defined over five documented objects, all referenced through APPS synonyms or views:

The outer join to PO_VENDORS is the only non-mandatory relationship; the remaining joins are inner joins, meaning a profile row without a valid TCA account, site use, or party will not appear in the view result set.

Key Columns

The view exposes the complete OZF_CUST_TRD_PRFLS column list plus descriptive columns from the joined objects. Primary and descriptive keys include TRADE_PROFILE_ID, PARTY_ID, PARTY_NAME, CUST_ACCOUNT_ID, ACCOUNT_NAME, ACCOUNT_NUMBER, CUST_ACCT_SITE_ID, SITE_USE_ID, SITE_USE_CODE, and LOCATION.

Configuration columns central to the view's purpose include DAYS_DUE and PAYMENT_METHOD; VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, and VENDOR_SITE_CODE; and the autopay group — AUTOPAY_FLAG, AUTOPAY_PERIODICITY, and AUTOPAY_PERIODICITY_TYPE — which together describe whether automatic payment is enabled and at what interval and interval unit. Claim and discount behavior is controlled by CLAIM_THRESHOLD, CLAIM_CURRENCY, and DISCOUNT_TYPE, while PRINT_FLAG, INTERNET_DEAL_VIEW_FLAG, and INTERNET_CLAIMS_FLAG govern output and self-service visibility. LAST_PAID_DATE records the most recent payment. The view also carries the standard EBS WHO columns, the DFF columns CONTEXT and ATTRIBUTE_CATEGORY through ATTRIBUTE15, and the multi-org column ORG_ID.

Common Use Cases and Queries

A frequent requirement is to audit autopay configuration across customers, for example to locate all profiles using a specific periodicity type:

  • SELECT trade_profile_id, party_name, account_number, autopay_flag, autopay_periodicity, autopay_periodicity_type FROM ozf_cust_trd_prfls_v WHERE autopay_flag = 'Y' AND autopay_periodicity_type = :p_type AND org_id = :p_org;

Other typical scenarios include extracting customer-to-supplier mappings for reconciliation, reporting claim thresholds and currencies by account, and validating self-service flags. When querying multi-org data, always constrain ORG_ID to the operating unit in context. Because the view performs inner joins to TCA and an outer join to PO_VENDORS, reports intended to include every profile row should be verified against the base table to confirm no records are silently excluded.