Search Results attribute_category_code

Overview

OKX_QTE_SLS_CREDITS_V is a reporting view owned by the APPS schema within the OKX - Contracts Integration product family in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. As documented in the ETRM repository, the view presents "Sales credits given to Sales persons," exposing the credit allocations that have been recorded against sales quotations and quote lines in the Oracle Quoting (ASO) module. The OKX integration layer relies on this view to surface quote-related sales credit data to downstream contracts functionality.

Because the object is a simple projection view rather than a denormalized or aggregated representation, it mirrors the row-level content of its base object without transformation. This makes it a stable, read-only access point for reporting and integration, insulating consumers from potential structural changes in the underlying table while still preserving the complete set of sales credit attributes. The view is marked VALID and holds no independent data storage of its own.

Underlying Base Objects

The view is defined over a single referenced base object: ASO_SALES_CREDITS, which is exposed in the APPS schema as a synonym. The view text is a straightforward SELECT that lists every documented column of ASO_SALES_CREDITS, joined by no additional tables or filters. Consequently, the cardinality and grain of OKX_QTE_SLS_CREDITS_V are identical to those of ASO_SALES_CREDITS: one row per sales credit allocation.

No WHERE clause or DISTINCT is applied, so the view performs no row filtering — any restriction on quote, line, resource, or sales person must be added by the calling query. Because there is a one-to-one column mapping, the view is effectively a synonym-like interface and any DML must be directed at the base table, not the view.

Key Columns

• SALES_CREDIT_ID — Primary identifier for each sales credit record; useful as the unique key in joins.
• QUOTE_HEADER_ID / QUOTE_LINE_ID — Foreign keys tying the credit to a specific quote and, when populated, a specific quote line.
• EMPLOYEE_PERSON_ID — The person identifier of the employee receiving the sales credit; the column most frequently searched by users referencing this view.
• RESOURCE_ID / RESOURCE_GROUP_ID — The resource and resource group to which the credit is attributed.
• PERCENT — The share of the credit allocated to the sales person, expressed as a percentage.
• SALES_CREDIT_TYPE_ID — Reference to the configured sales credit type (for example, quota-bearing versus non-quota-bearing).
• ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield and user-defined extension columns.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for auditing, plus OBJECT_VERSION_NUMBER for optimistic locking and the REQUEST_ID/PROGRAM_ID set for concurrent program tracking.

Common Use Cases and Queries

Typical usage centers on reporting and integration queries that resolve sales credits to the responsible employee. A common pattern filters on EMPLOYEE_PERSON_ID to retrieve all credits for a given person, joining to quote headers for context:

• Listing all sales credits for a specific sales person: SELECT sales_credit_id, quote_header_id, quote_line_id, percent FROM okx_qte_sls_credits_v WHERE employee_person_id = :p_person_id;
• Summarizing credit percentage by resource for a quote: aggregate PERCENT grouped by RESOURCE_ID and SALES_CREDIT_TYPE_ID, filtered on QUOTE_HEADER_ID.
• Integration extracts feeding OKX contracts processing, selecting the full column list for a range of QUOTE_HEADER_ID values.

Because the view exposes EMPLOYEE_PERSON_ID alongside the quote identifiers and PERCENT, it is the preferred access path for anyone searching on "employee_person_id" in the context of quote sales credits. Consumers should remember that all filtering and joins must be supplied explicitly, as the view itself performs none.