Search Results css_def_attributes_b

Overview

The CSS_DEF_ATTRIBUTES_B table is a core data definition table within the now-obsolete CSS (Support) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functioned as the base table for storing metadata that defined custom attributes within the support application. These attributes were likely used to extend the data model to capture additional, user-defined information related to support cases, service requests, or other service-related entities. Its role was to provide a centralized repository for the structural definition of these extensible attributes, enabling flexible data capture. However, it is critical to note the explicit documentation states this table is "Not implemented in this database," indicating it may have been a placeholder, part of a deprecated feature, or its functionality was superseded by other extensibility frameworks within EBS.

Key Information Stored

Based on the provided metadata, the primary data element stored in this table is the unique identifier for a defined attribute. The key column is ATTRIBUTE_ID, which serves as the primary key (CSS_DEF_ATTRIBUTES_B_PK1). While the full column list is not detailed in the excerpt, a table of this nature in a definitional context would typically contain columns to describe the attribute's properties. This could logically include the attribute name, data type (e.g., VARCHAR2, NUMBER, DATE), display prompt, format mask, validation rules, and a flag indicating its active status. The ATTRIBUTE_ID column is the critical foreign key referenced by other transactional tables that store the actual attribute values for specific records.

Common Use Cases and Queries

Given the table's obsolete status and non-implementation note, direct operational use cases are minimal. Historically, its purpose would have been to support the administration and reporting of custom support attributes. Common queries would have focused on retrieving the definitional metadata. A fundamental query would list all active attribute definitions: SELECT attribute_id, name, data_type FROM css_def_attributes_b WHERE enabled_flag = 'Y' ORDER BY name;. Another typical pattern would involve joining to the transactional table (CSS_DEF_DEF_ATTRIBUTES) to understand which definitions were in use: SELECT def.attribute_id, def.name, COUNT(val.attribute_id) usage_count FROM css_def_attributes_b def LEFT JOIN css_def_def_attributes val ON def.attribute_id = val.attribute_id GROUP BY def.attribute_id, def.name;. These patterns illustrate the table's intended role as a reference source for attribute metadata.

Related Objects

The primary documented relationship for the CSS_DEF_ATTRIBUTES_B table is with the CSS_DEF_DEF_ATTRIBUTES table. A foreign key constraint exists where the ATTRIBUTE_ID column in CSS_DEF_DEF_ATTRIBUTES references the ATTRIBUTE_ID primary key in CSS_DEF_ATTRIBUTES_B. This establishes a classic master-detail relationship, where CSS_DEF_ATTRIBUTES_B is the master definition table and CSS_DEF_DEF_ATTRIBUTES is the transactional table storing the actual values for specific definitions or instances. No other related tables, views, or public APIs are specified in the provided metadata. Given the module's obsolete status, developers and administrators should verify the current extensibility architecture, such as Descriptive Flexfields (DFFs), which likely replaced the functionality this table was designed to support.