Search Results cs_multi_org_rules_u1




Overview
Explore in AI Chat

Overview

The CS.CS_MULTI_ORG_RULES table is a configuration-seed table within the Oracle E-Business Suite Customer Service (CS) module footprint, owned by the CS schema and registered as part of the FND Design Data for CS.CS_MULTI_ORG_RULES. Its purpose is to define the set of Multi Org Rules used by Customer Service and the sequence in which those rules are evaluated when the application resolves an Operating Unit (Org Id) for a given transaction, service request, or interaction. The rules themselves are not free-form; each entry corresponds to a Lookup Code registered under the Lookup Type CS_MULTI_ORG_RULES in FND_LOOKUPS, meaning that the table stores the ordering and enabled set of a governed lookup list rather than inventing rule logic of its own.

The table resides in the APPS_TS_SEED tablespace with a PCT Free of 10, consistent with its role as a seed/setup object. The object is marked VALID in the ETRM documentation for both 12.1.1 and 12.2.2. Based on the documented relationship structure — a single primary-key candidate, a small set of descriptive attributes, and a foreign key to FND_SECURITY_GROUPS — this table is best modeled as a satellite (reference/setup) rather than a transaction hub or link. It carries code-to-order mappings whose changes are tracked through the standard WHO columns, which is characteristic of a slowly changing setup entity.

Key Information Stored

  • MULTI_ORG_RULE_CODE (VARCHAR2(30)) — The business identifier for the rule. Its value is drawn from FND_LOOKUPS under the Lookup Type CS_MULTI_ORG_RULES and therefore carries the semantic meaning of the rule.
  • MULTI_ORG_RULE_ORDER (NUMBER) — The numeric sequence in which the rule is scanned while the application searches for an Org Id. This column is the operational heart of the table, as it determines precedence among competing rules.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording who created and last modified each rule row and when.
  • SECURITY_GROUP_ID (NUMBER) — Used in hosted environments to segregate data by security group; documented as a foreign key to FND_SECURITY_GROUPS.
  • ZD_EDITION_NAME (VARCHAR2(30)) — The edition column supporting Oracle's Edition-Based Redefinition (EBR), enabling online patching and edition-aware reads in 12.2.x.

The documented primary key is CS_MULTI_ORG_RULES_PK on MULTI_ORG_RULE_CODE. The unique index CS_MULTI_ORG_RULES_U1 — the key business-key candidate — is defined on the combination of MULTI_ORG_RULE_CODE and ZD_EDITION_NAME, confirming that rule code uniqueness is scoped per edition. Notably, the ETRM index listing shows CS_MULTI_ORG_RULES_U1 as a NORMAL, UNIQUE index in APPS_TS_SEED, which is consistent with this composite key. There is no documented unique constraint on MULTI_ORG_RULE_ORDER alone, so ordering collisions are possible unless enforced by setup discipline.

Common Use Cases and Queries

The principal use cases are: inspecting the effective rule order used during Operating Unit derivation; validating that every rule code present in FND_LOOKUPS has a corresponding ordering row; and auditing setup changes over time for compliance and troubleshooting.

A straightforward query lists the rules in evaluation order:

  • SELECT MULTI_ORG_RULE_CODE, MULTI_ORG_RULE_ORDER, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM CS.CS_MULTI_ORG_RULES ORDER BY MULTI_ORG_RULE_ORDER;

To reconcile the table against its owning lookup type:

  • SELECT l.LOOKUP_CODE, r.MULTI_ORG_RULE_ORDER FROM FND_LOOKUPS l LEFT JOIN CS.CS_MULTI_ORG_RULES r ON r.MULTI_ORG_RULE_CODE = l.LOOKUP_CODE WHERE l.LOOKUP_TYPE = 'CS_MULTI_ORG_RULES';

For change auditing, filter on the WHO columns:

  • SELECT MULTI_ORG_RULE_CODE, MULTI_ORG_RULE_ORDER, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM CS.CS_MULTI_ORG_RULES WHERE LAST_UPDATE_DATE >= :since_date;

In 12.2.x, queries should generally be edition-aware, either by joining through EBR views or by filtering on the appropriate ZD_EDITION_NAME.

Related Objects

  • FND_LOOKUPS — The definitive source of rule codes; join on FND_LOOKUPS.LOOKUP_CODE = CS_MULTI_ORG_RULES.MULTI_ORG_RULE_CODE where LOOKUP_TYPE = 'CS_MULTI_ORG_RULES'.
  • FND_SECURITY_GROUPS — Referenced via the documented foreign key CS_MULTI_ORG_RULES.SECURITY_GROUP_ID, used for hosted-environment data segregation.
  • CS_MULTI_ORG_RULES# — The editioning/incremental companion object documented as referencing this table.
  • CS_MULTI_ORG_RULES_PK — The primary key constraint on MULTI_ORG_RULE_CODE.
  • CS_MULTI_ORG_RULES_U1 — The unique index on MULTI_ORG_RULE_CODE and ZD_EDITION_NAME, acting as the business-key candidate.
  • FND_LOOKUP_VALUES — Holds the translatable meaning and description for the rule codes sourced from the owning lookup type.

These relationships position CS.CS_MULTI_ORG_RULES as a small but operationally significant setup table that governs how Customer Service resolves Operating Units, with its integrity anchored to the FND lookup framework and its auditability provided by the standard WHO columns and the editioning key.