Search Results include_interorg_transfers

Overview

CSP_LOOP_CALC_RULES_V is a valid, predefined view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSP - Spares Management product. It exposes the calculation rule definitions used by the loop (demand/supply planning) calculation engine, joining the base and translation tables into a single language-aware record set. Because Spares Management is deployed across both 12.1.1 and 12.2.2, the view remains a stable, customer-facing reporting and integration interface in either release.

The view presents a denormalized, readable projection of each calculation rule, combining the technical attributes in CSP_LOOP_CALC_RULES_B with the language-specific name and description in CSP_LOOP_CALC_RULES_TL. It is intended primarily for reporting, inquiry, and integration rather than for direct DML; the translation join is filtered by USERENV('LANG'), so a query automatically returns rows in the session language.

The user search term include_purchase_orders maps to one of the rule's demand-source flags, INCLUDE_PURCHASE_ORDERS, which governs whether open purchase orders are treated as incoming supply or otherwise considered when the calculation rule computes loop quantities.

Underlying Base Objects

The documented view text is defined over two base objects, each exposed through an APPS synonym:

• CSP_LOOP_CALC_RULES_B (SYNONYM) — the base table holding the calculation rule header, keyed by CALCULATION_RULE_ID, with all technical flags, DFF attributes, and WHO audit columns.
• CSP_LOOP_CALC_RULES_TL (SYNONYM) — the translation table supplying CALCULATION_RULE_NAME and DESCRIPTION per language.

The two are joined on B.CALCULATION_RULE_ID = T.CALCULATION_RULE_ID with the additional predicate T.LANGUAGE = USERENV('LANG'). The view carries no WHERE clause restricting the underlying rows, so all rules defined in the base table are returned, one per rule per current session language. Because it is a view (and not a synonym to a single table), joins to inventory, order, or planning entities at the calculation-rule level are typically performed on CALCULATION_RULE_ID.

Key Columns

Alongside the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the row locator ROWID, the projection exposes the identification, source-inclusion, and control attributes of each rule:

• CALCULATION_RULE_ID — primary key linking the view to the base table and to any dependent planning/reporting joins.
• CALCULATION_RULE_NAME / DESCRIPTION — the translated name and description from the TL table.
• INCLUDE_SALES_ORDERS, INCLUDE_MOVE_ORDERS, INCLUDE_REPAIR_ORDERS, INCLUDE_WORK_ORDERS, INCLUDE_PURCHASE_ORDERS — the include flags selecting which order/document sources participate in the calculation. INCLUDE_PURCHASE_ORDERS specifically determines whether the engine considers open purchase orders as a supply source for the rule.
• INCLUDE_REQUISITIONS, INCLUDE_INTERORG_TRANSFERS — additional firm/incoming supply indicators.
• INCLUDE_ONHAND_GOOD, INCLUDE_ONHAND_BAD, INCLUDE_INTRANSIT_MOVE_ORDERS, INCLUDE_DOA — on-hand and in-transit posture flags, including the on-hand good/bad distinction and dead-on-arrival treatment.
• ROLLUP_SUPERCESSION, FORECAST_LOWER_SUPERCESSION — supersession roll-up and forecast lowering controls.
• TOLERANCE_PERCENT, TIME_FENCE — numeric thresholds governing tolerance and the planning time fence.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) context and segments carried through from the base table.

Common Use Cases and Queries

Typical usage includes rule inventory and audit, comparison of include flags across rules, and joining to operational data on CALCULATION_RULE_ID. A representative query listing all rules and their purchase order treatment is:

SELECT calculation_rule_id, calculation_rule_name, include_purchase_orders, include_sales_orders, tolerance_percent, time_fence FROM apps.csp_loop_calc_rules_v ORDER BY calculation_rule_name;

To isolate only rules that consume purchase orders as supply, filter on the searched attribute:

SELECT calculation_rule_id, calculation_rule_name, description FROM apps.csp_loop_calc_rules_v WHERE include_purchase_orders = 'Y';

Because the view resolves names in the session language, it is well suited to page-level LOVs, OAF/Forms value lists, and outbound integration extracts that require a human-readable rule identifier together with the source-inclusion flags. Rule-level comparisons between environments are also common, since the view reflects the base and translation tables directly without additional filtering logic.