Results for “csd_defaulting_value_types”

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

Overview

APPS.CSD_RULES_V is a multilingual (ML) reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the defaulting rules maintained by the Common Strategy Defaulting (CSD) framework. Defaulting rules in CSD determine how attribute values are automatically derived for entities such as order lines, service contracts, and other transactional objects. The view joins the rule base table (CSD_RULES_B) with its translation table (CSD_RULES_TL) so that rule names and descriptions are returned in the session's current language, and it further decorates coded columns with their display meanings by joining to FND_LOOKUPS.

Because it resolves language via USERENV('LANG') and outer-joins lookup meanings, CSD_RULES_V is the preferred read interface for concurrent programs, OAF pages, and custom reports that need human-readable defaulting rule metadata. It is a view only — no direct DML is supported; base tables must be maintained through the standard CSD setup forms or APIs.

Underlying Base Objects

The view is defined over the following documented objects:

• CSD_RULES_B — the base (non-translated) table holding rule identifiers, precedence, rule type, entity attribute code and type, and value type, plus WHO audit columns and the DFF attribute1–15 segment columns.
• CSD_RULES_TL — the translation table providing NAME and DESCRIPTION per language, joined on RULE_ID and filtered by USERENV('LANG').
• FND_LOOKUPS — used four times with aliases (RTYPE_FND, ATTR_FND, ENT_FND, VAL_FND) to resolve lookup codes into meanings. ENT_FND uses lookup type CSD_DEFAULTING_ENTITIES; RTYPE_FND uses CSD_RULE_TYPES; VAL_FND uses CSD_DEFAULTING_VALUE_TYPES; ATTR_FND uses the entity attribute type itself as the lookup type. ATTR_FND, ENT_FND, and VAL_FND are outer-joined; RTYPE_FND is an inner join.
• FND_GLOBAL — referenced indirectly through USERENV('LANG'), which resolves the session language used for the TL and lookup joins.

The join to CSD_RULES_TL is a strict inner join on RULE_ID, so a rule appears only when a translation row exists for the active language. The lookup joins are predominantly outer joins, allowing rules whose codes lack a matching lookup entry to still be returned.

Key Columns

• RULE_ID — primary key of the rule, inherited from CSD_RULES_B.
• NAME / DESCRIPTION — localized text from CSD_RULES_TL.
• RULE_TYPE_CODE / MEANING (RTYPE_FND) — the rule category code and its lookup meaning (lookup type CSD_RULE_TYPES).
• PRECEDENCE — numeric ordering that determines the evaluation sequence when multiple rules apply.
• ENTITY_ATTRIBUTE_CODE / ATTR_FND.MEANING — the code of the attribute being defaulted and its display meaning.
• ENTITY_ATTRIBUTE_TYPE / ENT_FND.MEANING — the entity context, resolved through lookup type CSD_DEFAULTING_ENTITIES; this is the column most relevant to a search for "csd_defaulting_entities".
• VALUE_TYPE_CODE / VAL_FND.MEANING — indicates the nature of the defaulted value (lookup type CSD_DEFAULTING_VALUE_TYPES).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard WHO and concurrency-control columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments carried through from the base table.

Common Use Cases and Queries

Typical uses include auditing which defaulting rules exist for a given entity, verifying precedence order, and building setup reports that display meanings rather than codes. Because the entity dimension is driven by the CSD_DEFAULTING_ENTITIES lookup, listing rules by entity is a frequent query pattern.

• List all rules for a specific entity type:

  SELECT rule_id, name, entity_attribute_code, entity_attribute_type,
         precedence, value_type_code
  FROM   apps.csd_rules_v
  WHERE  entity_attribute_type = :entity_code
  ORDER  BY precedence;

• Report entity meanings and rule counts:

  SELECT entity_attribute_type, meaning, COUNT(*)
  FROM   apps.csd_rules_v
  GROUP  BY entity_attribute_type, meaning;

• Audit recently modified rules:

  SELECT rule_id, name, last_updated_by, last_update_date
  FROM   apps.csd_rules_v
  WHERE  last_update_date >= SYSDATE - 30;

These queries should be executed with APPS or a responsibility that has select privileges on the view; the view itself enforces no additional security predicates beyond language resolution.