Search Results policy_code

Overview

ENG_CHANGE_POLICIES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, within the Engineering (ENG) product family. It exposes the configuration of Engineering Change Order (ECO) policies, specifically the rules and attribute-level values that determine when a change is required, how it is routed, and what values must be assigned during the change management lifecycle. The view consolidates data from change policy definitions, policy values, change rules, and rule attributes into a single denormalized result set.

The view is significant in ETRM 12.1.1 and 12.2.2 because engineering change policies govern the automatic behavior of the ECO workflow. The column POLICY_CODE — the term most frequently associated with this object in metadata searches — provides a stable, human-readable identifier for each policy definition. This makes the view suitable for both seeded and user-defined policy lookups, and it is commonly referenced in reporting, integration, and diagnostic queries rather than in the transaction-processing path itself. As a view rather than a table, it carries no independent storage and reflects the current state of the underlying base objects at query time.

Underlying Base Objects

According to the documented view definition, ENG_CHANGE_POLICIES_V is defined over four synonym-referenced base objects:

• ENG_CHANGE_POLICIES — the policy header, providing POLICY_CODE, POLICY_OBJECT_NAME, POLICY_COLUMN_TYPE, and the five POLICY_OBJECT_PK1–PK5_VALUE key columns.
• ENG_CHANGE_POLICY_VALUES — the values assigned to each policy, supplying POLICY_NUMBER_VALUE and POLICY_CHAR_VALUE, joined to ENG_CHANGE_POLICIES on CHANGE_POLICY_ID.
• ENG_CHANGE_RULES — the change rule set, supplying ATTRIBUTE_CODE and ATTRIBUTE_OBJECT_NAME and joining to policy values on CHANGE_RULE_ID.
• ENG_CHANGE_RULE_ATTRIBUTES_B (referenced through the ENG_CHANGE_RULE_ATTRIBUTES_VL synonym in the view text) — the attribute definition providing ATTRIBUTE_COLUMN_TYPE and the attribute object name used in the join.

The joins link policy to policy values, policy values to change rules, and change rules to rule attributes, with the attribute join conditioned on both ATTRIBUTE_OBJECT_NAME and ATTRIBUTE_CODE. The result is a cross-product-style projection that pairs each rule attribute with the policy values that apply to it.

Key Columns

The view returns fifteen columns. The most important are:

• POLICY_CODE — the identifying code for the change policy. It is the primary lookup key for reporting and integration scenarios.
• ATTRIBUTE_CODE and ATTRIBUTE_OBJECT_NAME — identify the engineering attribute and the object (item, ECO, or similar) to which the rule attribute applies.
• ATTRIBUTE_COLUMN_TYPE and POLICY_COLUMN_TYPE — declare whether the corresponding value is numeric or character, directing consumers to read the right value column.
• ATTRIBUTE_NUMBER_VALUE / ATTRIBUTE_CHAR_VALUE and POLICY_NUMBER_VALUE / POLICY_CHAR_VALUE — the paired value columns for the attribute and the policy respectively.
• POLICY_OBJECT_NAME and POLICY_OBJECT_PK1_VALUE through POLICY_OBJECT_PK5_VALUE — identify the policy target object and its primary key components, allowing the policy to be tied back to the specific entity it governs.

Common Use Cases and Queries

Typical uses include validating which policy a rule maps to, auditing attribute-to-policy value pairings before an upgrade, and building extracts for external change-management reporting. A basic query filtered on the policy code is:

• SELECT policy_code, attribute_code, attribute_object_name, policy_column_type, policy_number_value, policy_char_value FROM apps.eng_change_policies_v WHERE policy_code = :p_code;
• To list all policies governing a given attribute: SELECT DISTINCT policy_code FROM apps.eng_change_policies_v WHERE attribute_code = :attr AND attribute_object_name = :obj;
• To audit mixed-type values: SELECT policy_code, attribute_code, policy_column_type, COALESCE(policy_char_value, TO_CHAR(policy_number_value)) value_text FROM apps.eng_change_policies_v ORDER BY policy_code, attribute_code;

Because the view is read-only and composes four base objects, queries should be limited to the columns required, and consumers should always resolve values using the corresponding COLUMN_TYPE flag rather than assuming character or numeric content.