Search Results src_parameter_name

Overview

OE_DEF_ATTR_RULES_V is a VALID view owned by the APPS schema within the ONT – Order Management product of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the configuration metadata that drives Oracle Order Management's defaulting engine, presenting the rules that determine how attribute values are derived and propagated onto order headers, lines, and related entities. The underlying tables (OE_DEF_ATTR_DEF_RULES and OE_DEF_ATTR_CONDNS) are the physical repositories of defaulting rule definitions and their associated conditions, while AK_OBJECT_ATTRIBUTES_VL provides the descriptive attribute metadata (column name, label, application) for the objects being defaulted.

Rather than requiring direct joins across the three base objects, this view delivers a pre-joined, transaction-ready representation of defaulting logic. It is therefore suited to reporting, integration, and diagnostic work where the goal is to understand or audit which source types, constants, profile options, system variables, or API calls supply values to specific order attributes.

Underlying Base Objects

The view is defined over three documented objects, joined on attribute and object identifiers:

• OE_DEF_ATTR_DEF_RULES (SYNONYM) — the primary table holding one row per defaulting rule, aliased R. It supplies the source-type definition (SRC_TYPE) and the various source-value columns.
• OE_DEF_ATTR_CONDNS (SYNONYM) — the condition table, aliased C, joined via ATTR_DEF_CONDITION_ID and DATABASE_OBJECT_NAME.
• AK_OBJECT_ATTRIBUTES_VL (VIEW) — the attribute-registry view, aliased A, joined on DATABASE_OBJECT_NAME and ATTRIBUTE_CODE to deliver COLUMN_NAME, ATTRIBUTE_APPLICATION_ID, and the attribute label.

The join conditions bind rule, condition, and attribute-registry rows to the same database object and attribute code, ensuring the returned defaulting logic is internally consistent.

Key Columns

• ATTR_DEF_RULE_ID / ATTR_DEF_CONDITION_ID / CONDITION_ID — rule and condition identifiers tying the configuration together.
• DATABASE_OBJECT_NAME / ATTRIBUTE_CODE — identify the target object and attribute being defaulted.
• SRC_TYPE — the defaulting source category (constant, profile option, system variable, API, foreign key, sequence, and so on).
• SRC_CONSTANT_VALUE, SRC_PROFILE_OPTION, SRC_API_PKG, SRC_API_FN, SRC_SYSTEM_VARIABLE_EXPR, SRC_PARAMETER_NAME, SRC_FOREIGN_KEY_NAME, SRC_SEQUENCE_NAME — the specific source parameters applicable to the selected SRC_TYPE.
• SRC_DATABASE_OBJECT_NAME / SRC_ATTRIBUTE_CODE — the originating object/attribute when the value is sourced from another attribute.
• SEQUENCE_NO — evaluation order among competing defaulting rules.
• SYSTEM_FLAG / PERMANENT_FLAG — indicate Oracle-seeded versus user-defined rules and whether the rule is protected.
• COLUMN_NAME / ATTRIBUTE_LABEL_LONG / ATTRIBUTE_APPLICATION_ID — descriptive metadata from AK_OBJECT_ATTRIBUTES_VL.

Common Use Cases and Queries

Typical uses include auditing which source populates a given order attribute, documenting configuration before an upgrade, and diagnosing unexpected defaulting behavior. A simple inventory of rules follows:

• All defaulting rules for a given attribute: SELECT ATTR_DEF_RULE_ID, SRC_TYPE, SRC_CONSTANT_VALUE, SRC_PROFILE_OPTION, SEQUENCE_NO FROM OE_DEF_ATTR_RULES_V WHERE DATABASE_OBJECT_NAME = :object AND ATTRIBUTE_CODE = :attr ORDER BY SEQUENCE_NO;
• Rule source distribution: SELECT SRC_TYPE, COUNT(*) FROM OE_DEF_ATTR_RULES_V GROUP BY SRC_TYPE;
• System-seeded versus custom: SELECT * FROM OE_DEF_ATTR_RULES_V WHERE SYSTEM_FLAG = 'Y';
• Profile-option-driven defaults: SELECT ATTRIBUTE_CODE, SRC_PROFILE_OPTION FROM OE_DEF_ATTR_RULES_V WHERE SRC_TYPE = 'PROFILE';

Because the view is read-only and joins metadata across objects, it is safe for ad-hoc querying against production; however, large AK_OBJECT_ATTRIBUTES_VL joins should be filtered by DATABASE_OBJECT_NAME to limit result sets on high-volume instances.