Results for “cst_moh_rules_transaction”

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

Overview

The view APPS.CST_MATERIAL_OVHD_RULES_V exposes the material overhead rule definitions maintained in Oracle EBS Cost Management. Material overhead is applied during the transaction costing process according to user-defined rules that determine which transactions, items, categories, and shipping organizations are subject to the absorption of a material overhead cost element. The view denormalizes the underlying rule table, CST_MATERIAL_OVHD_RULES, by resolving lookup codes into their descriptive meanings and by resolving the applicable cost type. It therefore presents material overhead rules in a form suitable for reporting, inquiry, and integration rather than for maintenance.

The view is read-only with respect to the base rule table. Rule maintenance is performed through the Cost Management setup windows, which write to CST_MATERIAL_OVHD_RULES; the view is the query surface used to display those rules with human-readable values. The view is owned by APPS and is available in both 12.1.1 and 12.2.2. In 12.2.2 the same object metadata is preserved, with the referenced base objects resolved through synonyms and a lookup view.

Underlying Base Objects

• CST_MATERIAL_OVHD_RULES — the driving table (aliased CMOHR) that stores each material overhead rule, including the transaction type, selection criteria, category, item range, item type, ship-from organization, earn flag, and cost type.
• MFG_LOOKUPS — a view on the lookup definitions, joined twice: once for the transaction type (MFG1, lookup type CST_MOH_RULES_TRANSACTION) and once for the item type (MFG2, lookup type CST_MTL_ITEM_TYPE). These joins supply the MEANING columns.
• CST_COST_TYPES — the cost type definitions, joined by COST_TYPE_ID to return the cost type name.
• MTL_PARAMETERS — the organization parameters, accessed through a scalar subquery to supply a default cost type when the rule itself does not specify one.

The COST_TYPE_ID join is the most notable: a DECODE statement substitutes the organization's AVG_RATES_COST_TYPE_ID (defaulting to cost type 1) whenever the rule carries a null cost type, ensuring every row resolves to a valid cost type definition.

Key Columns

• ROWID, RULE_ID — the physical row identifier and the surrogate primary key of the rule.
• ORGANIZATION_ID — the inventory organization to which the rule applies.
• TRANSACTION_TYPE with its decoded MEANING — the transaction type that triggers the rule.
• SELECTION_CRITERIA, CATEGORY_ID, ITEM_FROM, ITEM_TO, ITEM_TYPE — the qualifying conditions that determine which items are affected.
• SHIP_FROM_ORG — the shipping organization constraint applied to the rule.
• EARN_MOH — the flag indicating whether material overhead is earned for the qualifying transactions.
• COST_TYPE_ID and the resolved cost type name — the basis on which the overhead amount is calculated.
• Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Common Use Cases and Queries

Typical use is inspection and reporting of the rules configured for a given organization and cost type, often in support of cost rollup or absorption analysis, or as a source for integration extracts.

• List all rules for an organization:

  SELECT rule_id, transaction_type, meaning, item_type, earn_moh
  FROM   apps.cst_material_ovhd_rules_v
  WHERE  organization_id = :org_id;

• Identify rules that earn material overhead:

  SELECT rule_id, category_id, item_from, item_to, cost_type
  FROM   apps.cst_material_ovhd_rules_v
  WHERE  earn_moh = 'Y'
  ORDER  BY transaction_type;

• Join to CST_MATERIAL_OVHD_RULES on ROWID when write operations are required, since the view is not inherently updatable.

Because the view depends on lookup and cost type master data, incomplete lookup definitions or missing cost types will suppress rows in the result set, a behavior worth noting when reconciling the view against the base table.