Search Results so_sales_credit_types_115_uk1

Overview

The SO_SALES_CREDIT_TYPES_115 table is a foundational setup table within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for releases 12.1.1 and 12.2.2. It serves as a master repository for defining the different categories or classifications of sales credit that can be assigned to sales representatives or partners upon booking an order. This table is critical for the sales compensation and incentive management processes, as it provides the valid list of credit types against which revenue or commission can be allocated. Its role is to ensure referential integrity and standardization of sales credit data across the order-to-cash cycle.

Key Information Stored

The table's structure, as indicated by its primary and unique keys, is designed to uniquely identify each credit type. The primary technical identifier is the SALES_CREDIT_TYPE_ID column, which is a numeric, system-generated primary key used for internal relationships. The primary business identifier is the NAME column, which holds the unique, user-defined name for the sales credit type (e.g., "Primary," "Secondary," "Override," "Split"). This column is enforced by a unique key constraint (SO_SALES_CREDIT_TYPES_115_UK1). While the provided metadata does not list other specific columns, typical implementations may include descriptive columns like DESCRIPTION, ENABLED_FLAG, and START_DATE_ACTIVE to manage the lifecycle of the credit type definition.

Common Use Cases and Queries

A primary use case is the validation and assignment of sales credits during order entry and import. When a user assigns a credit to a salesperson on an order line, the system validates the entered credit type against this table. This table is also central to reporting on sales performance and commission calculations by credit type. Common queries include listing all active credit types for setup forms or validating data during migrations. For instance, a basic query to retrieve all defined credit types would be: SELECT sales_credit_type_id, name FROM oe.so_sales_credit_types_115 ORDER BY name;. Another typical pattern is joining to sales credit transaction tables to analyze bookings: SELECT sct.name, SUM(sc.credited_amount) FROM oe.so_sales_credit_types_115 sct, oe.so_sales_credits sc WHERE sc.sales_credit_type_id = sct.sales_credit_type_id GROUP BY sct.name;.

Related Objects

As documented in the foreign key relationships, SO_SALES_CREDIT_TYPES_115 is referenced by several key transactional and setup tables, primarily using the SALES_CREDIT_TYPE_ID column. The documented relationships are:

• PA_IMPLEMENTATIONS_ALL: The Projects Accounting module references this table via the column PA_IMPLEMENTATIONS_ALL.SALES_CREDIT_TYPE_CODE to define a default credit type for project-related transactions.
• RA_SALESREPS_ALL: The Receivables module links sales representatives to a default sales credit type via RA_SALESREPS_ALL.SALES_CREDIT_TYPE_ID.
• SO_SALES_CREDITS: This is the core transactional table storing awarded credits for order lines, linked via SO_SALES_CREDITS.SALES_CREDIT_TYPE_ID.
• SO_SALES_CREDITS_INTERFACE: The order import interface table references this table for validation via two columns: SO_SALES_CREDITS_INTERFACE.SALES_CREDIT_TYPE_ID and SO_SALES_CREDITS_INTERFACE.SALES_CREDIT_TYPE.

These relationships underscore the table's central role in ensuring consistent sales credit data flows from order entry (OE) to receivables (AR) and projects (PA).