Search Results oe_sales_credit_types

Overview

OE_SALES_CREDIT_TYPES is a reference (setup) table owned by the ONT schema within the Oracle Order Management module. It stores the definition of sales credit types, the configurable categories used to attribute sales credit on order lines, such as quota-bearing revenue credit, non-quota credit, and other sales compensation classifications. In Oracle EBS 12.1.1 and 12.2.2, this table is a foundational lookup: each sales credit type is defined once here and then referenced when sales credits are assigned to order lines, enabling accurate attribution of sales performance across the order-to-cash flow.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as standalone (a heuristic derived from its foreign-key structure). This suggests it be modeled as a hub entity, since it represents a stable, uniquely identified business concept (the sales credit type) with its own surrogate key, rather than a transactional link or a dependent satellite. The associated descriptive attributes would naturally reside in a satellite attached to that hub.

Key Information Stored

The table consists of 27 documented columns. The most important are:

• SALES_CREDIT_TYPE_ID — the surrogate primary key that uniquely identifies each sales credit type; used as the foreign key from downstream sales-credit assignment records.
• NAME — the user-facing name of the sales credit type; together with ZD_EDITION_NAME it forms the unique business key.
• DESCRIPTION — free-text explanation of the credit type's purpose.
• QUOTA_FLAG — indicates whether the credit type counts toward sales quota.
• ENABLED_FLAG — controls whether the credit type is active and selectable in transaction entry.
• ZD_EDITION_NAME — the edition/versioning column used by Oracle's data-vault-style editioning support; participates in the unique index OE_SALES_CREDIT_TYPES_U1 (NAME, ZD_EDITION_NAME).
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN track record creation and modification history.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (Descriptive Flexfield) columns that allow customers to extend the credit type with site-specific attributes without schema changes.

The unique index OE_SALES_CREDIT_TYPES_U1 on (NAME, ZD_EDITION_NAME) is the documented business-key candidate, distinguishing it from the surrogate SALES_CREDIT_TYPE_ID primary key.

Common Use Cases and Queries

Typical usage centers on setup validation, credit attribution reporting, and quota analysis. Common patterns include:

• Listing active credit types for a picklist: SELECT sales_credit_type_id, name FROM oe_sales_credit_types WHERE enabled_flag = 'Y' ORDER BY name;
• Identifying quota-bearing types for sales compensation reporting: SELECT sales_credit_type_id, name FROM oe_sales_credit_types WHERE quota_flag = 'Y';
• Joining to sales credit assignment facts to aggregate credit by type. Downstream tables reference OE_SALES_CREDIT_TYPES.SALES_CREDIT_TYPE_ID via the foreign key pointing to SO_SALES_CREDIT_TYPES_115, enabling the credit type descriptions to be resolved onto transaction lines.
• Auditing setup changes by filtering on LAST_UPDATE_DATE to review recently modified or disabled credit types.

In 12.2.2, note the ZD_EDITION_NAME in the unique index; queries that assume NAME alone is unique may return duplicate rows across editions.

Related Objects

• SO_SALES_CREDIT_TYPES_115 — the foreign key target of SALES_CREDIT_TYPE_ID; the base sales credit types reference source that OE_SALES_CREDIT_TYPES derives from in Order Management context.
• OE_SALES_CREDITS — the transactional sales-credit assignment table that consumes SALES_CREDIT_TYPE_ID to classify each credited salesperson.
• OE_ORDER_LINES_ALL — order lines whose sales credits ultimately reference the credit types defined here.
• OE_SALES_CREDIT_SPLITS — captures how credit is split among salespeople, using the credit type for categorization.
• Sales Credit Type setup UI and APIs — Order Management setup forms and public APIs that maintain these records rather than direct DML.
• ASO / Quota and compensation reporting views — reporting objects that join credit types to performance facts for quota-flag-based analysis.

Because the table is standalone, all extensions typically derive from the sales-credit assignment chain rather than inward foreign keys.