Results for “css_def_attributes_b”

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

Overview

CSS_DEF_ATTRIBUTES_B is a base table within the Oracle E-Business Suite CSS – Support product family. In the Oracle EBS 12.1.1 and 12.2.2 data models, tables ending in the _B suffix conventionally designate the base (language-independent) portion of a translated entity, with a corresponding _TL table holding the translatable descriptive columns. CSS_DEF_ATTRIBUTES_B stores definitions of attributes used by the CSS Support configuration framework, providing the master list of attribute identifiers against which dependent definition records are resolved.

According to the ETRM documentation metadata, this object is flagged as obsolete. The Description field explicitly records "Not implemented in this database," indicating that the table is retained only as a legacy structural artifact — it appears in the data dictionary and relationship model but carries no active rows in a standard 12.1.1 or 12.2.2 installation. Any development, conversion, or integration work that references this table should verify physical existence before issuing DML, and should treat the object as a historical remnant of an earlier CSS Support schema iteration.

The metadata's heuristic Data Vault classification is hub-leaning. Read as a modeling suggestion rather than a directive, this indicates the table behaves structurally like a hub: it holds a relatively stable, non-volatile set of unique business identifiers (attributes) that are referenced by other objects, with no obvious transactional or rapidly mutating descriptive payload. A Data Vault implementation would likely place ATTRIBUTE_ID as the hub business key and route dependent/descriptive data to satellites.

Key Information Stored

The documented metadata exposes a deliberately narrow column set. The principal column is:

• ATTRIBUTE_ID — The surrogate primary key of the table, enforced by the constraint CSS_DEF_ATTRIBUTES_B_PK1. In the Data Vault reading suggested above, this column also serves as the hub business key candidate, since no separate unique business identifier is documented.

No additional columns are documented in the supplied ETRM excerpt, and no unique indexes beyond the primary key constraint are recorded. Because the table is not implemented, the metadata does not enumerate descriptive or audit columns (such as creation dates, user stamps, or enabled flags) that sibling CSS definition tables typically carry. Consulting the physical data dictionary (DBA_TAB_COLUMNS) is the only reliable means of confirming the full column list in a given environment.

Common Use Cases and Queries

Given its obsolete and unimplemented status, productive reporting against CSS_DEF_ATTRIBUTES_B is unlikely. Practical use cases center on impact analysis, schema archaeology, and migration validation:

• Existence verification — Confirm whether the object exists and holds rows prior to referencing it in custom code:

  SELECT COUNT(*) FROM css_def_attributes_b;

• Constraint discovery — Identify the primary key definition documented as CSS_DEF_ATTRIBUTES_B_PK1:

  SELECT constraint_name, constraint_type, column_name
  FROM   dba_cons_columns
  WHERE  table_name = 'CSS_DEF_ATTRIBUTES_B';

• Dependency mapping — Trace inbound references from dependent definition tables to assess the cost of dropping or repurposing the object.
• Upgrade assessment — Compare 12.1.1 and 12.2.2 dictionary views to determine whether the table persists across releases.

Because no rows are expected, queries intended to enumerate attribute values should target the implemented replacement structures in the current CSS Support model instead.

Related Objects

The documented foreign-key relationship identifies a single dependent object with a confirmed join path:

• CSS_DEF_DEF_ATTRIBUTES — References this table via CSS_DEF_DEF_ATTRIBUTES.ATTRIBUTE_ID → CSS_DEF_ATTRIBUTES_B.ATTRIBUTE_ID. This is the only relationship recorded in the ETRM metadata and represents the primary inbound link to the hub.

The _B naming convention implies a companion translated table, conventionally CSS_DEF_ATTRIBUTES_TL, joined on ATTRIBUTE_ID with a LANGUAGE discriminator; this should be validated in the target instance. Broader CSS Support definition tables — including other CSS_DEF_* objects that share the same definition framework — may also reference the attribute identifier indirectly, but no additional foreign keys are documented. Any join between CSS_DEF_DEF_ATTRIBUTES and this table should be written with an outer join or guarded by a row-existence check, since the base table is not populated in standard installations.