Results for “customer_class_code”

2 results




Overview
Explore in AI Chat

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

Overview

The SO_DISCOUNT_CUSTOMERS table is an Order Entry (OE) module object in the Oracle E-Business Suite, owned by the OE schema and classified with a status of VALID in both release 12.1.1 and 12.2.2. Its documented description — "Discounts for specific customers" — identifies it as the intersection of the Oracle Advanced Pricing / Order Management discounting model and the Trading Community Architecture (TCA) customer and site model. Each row qualifies a discount defined in SO_DISCOUNTS for a particular customer party (RA_CUSTOMERS) and, optionally, for a specific customer site or site-use record (RA_SITE_USES_ALL). This allows pricing administrators to scope a promotional or contractual discount to a named buying organization rather than to a broad price-list or qualifier.

From a Data Vault modeling perspective — a heuristic classification mined from the foreign-key structure — this object behaves as a link. It resolves a many-to-many association among the discount entity, the customer party entity, and the customer site entity, carrying its own surrogate key (DISCOUNT_CUSTOMER_ID) plus effectivity and descriptive attributes. It is not a hub, because its identity is derived from the relationships it connects, and it is not purely a satellite, because it holds its own business attributes (activation dates, customer class code, and a 15-column descriptive flexfield block).

Documented physical schema shows 32 columns in the 12.2.2 ETRM metadata set. The table includes the standard Oracle Applications WHO columns for audit and concurrent-program tracking: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

Key Information Stored

The most significant columns fall into three groups: identity, relationships, and control attributes.

  • DISCOUNT_CUSTOMER_ID — the surrogate primary key, backed by both the SO_DISCOUNT_CUSTOMERS_PK constraint and the unique index SO_DISCOUNT_CUSTOMERS_U1. This is the only documented business-key candidate; there is no alternate unique key on the natural combination of discount and customer.
  • DISCOUNT_ID — foreign key to SO_DISCOUNTS, identifying the discount header being scoped.
  • CUSTOMER_ID — foreign key to RA_CUSTOMERS, identifying the customer party eligible for the discount.
  • SITE_USE_ID — foreign key to RA_SITE_USES_ALL, identifying the specific site use (for example, bill-to or ship-to) to which the discount applies.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the customer-specific discount is active.
  • CUSTOMER_CLASS_CODE — the customer classification associated with the entry, supporting class-based reporting or eligibility logic.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield columns used for customer-specific extensions.

Common Use Cases and Queries

Typical scenarios include determining which customers receive a given discount, identifying all discounts available to a customer, and validating effectivity windows for pricing setups.

Sample query — list active customer-specific discounts for a customer:

SELECT sdc.discount_customer_id,
       sdc.discount_id,
       sdc.customer_id,
       sdc.site_use_id,
       sdc.start_date_active,
       sdc.end_date_active
FROM   oe.so_discount_customers sdc
WHERE  sdc.customer_id = :p_customer_id
AND    TRUNC(SYSDATE) BETWEEN NVL(sdc.start_date_active, SYSDATE)
                          AND NVL(sdc.end_date_active, SYSDATE);

A second pattern joins to SO_DISCOUNTS to retrieve the discount name and to RA_SITE_USES_ALL to resolve the site, producing a complete picture for a pricing audit or a customer-facing quote review.

Related Objects

  • SO_DISCOUNTS — joined on SO_DISCOUNT_CUSTOMERS.DISCOUNT_ID = SO_DISCOUNTS.DISCOUNT_ID; the discount definition that this row qualifies.
  • RA_CUSTOMERS — joined on SO_DISCOUNT_CUSTOMERS.CUSTOMER_ID = RA_CUSTOMERS.CUSTOMER_ID; the party-level customer record.
  • RA_SITE_USES_ALL — joined on SO_DISCOUNT_CUSTOMERS.SITE_USE_ID = RA_SITE_USES_ALL.SITE_USE_ID; the site-level applicability.

Additional dependent objects include the pricing qualifier and list-line tables in the QP (Advanced Pricing) schema, which commonly reference the same customer and site identifiers, as well as Order Management pricing APIs such as QP_PREQ_GRP and the OE order pricing engine that consumes these discount-customer associations during order line pricing.