Search Results msc_atp_rules_u1

Overview

MSC.MSC_ATP_RULES is a planning table in the MSC schema that stores the rule definitions and processing options used by Oracle Advanced Supply Chain Planning (ASCP) and related applications when computing Available To Promise (ATP). Each row represents one named ATP rule that governs how supply and demand are selected, netted, and accumulated across a time horizon. ATP rules are attached to items, organizations, or planning parameters and drive the calculation of promise dates and available quantities returned to order capture, order management, and scheduling processes.

The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is classified in the ETRM documentation as VALID with FND Design Data mapping to MSC.MSC_ATP_RULES. Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as standalone, meaning it behaves as a reference or configuration entity rather than participating in a hub/link/satellite dependency chain. In Data Vault terms, it is best treated as a standalone reference table whose business key is the ATP rule identity scoped by instance.

Key Information Stored

The table is physically defined with 65 documented columns. Its primary key is MSC_ATP_RULES_PK, composed of SR_INSTANCE_ID and RULE_ID. The unique index MSC_ATP_RULES_U1 (SR_INSTANCE_ID, RULE_ID) on the APPS_TS_TX_IDX tablespace is the documented business-key candidate and is the access path most queries will use. RULE_ID is the surrogate ATP rule identifier, and SR_INSTANCE_ID scopes the rule to a source instance.

The most operationally significant columns include:

• RULE_NAME and DESCRIPTION — the user-facing identity and narrative of the rule.
• ACCUMULATE_AVAILABLE_FLAG and ACCUMULATION_WINDOW — control whether availability is accumulated and over what window.
• BACKWARD_CONSUMPTION_FLAG and FORWARD_CONSUMPTION_FLAG — determine how shortages are consumed backward or forward in time.
• PAST_DUE_DEMAND_CUTOFF_FENCE and PAST_DUE_SUPPLY_CUTOFF_FENCE — exclude stale demand or supply beyond a day threshold.
• INFINITE_SUPPLY_FENCE_CODE and INFINITE_SUPPLY_TIME_FENCE — define the infinite supply horizon.
• ACCEPTABLE_EARLY_FENCE and ACCEPTABLE_LATE_FENCE — tolerance windows for promise dates.
• DEFAULT_ATP_SOURCES and DEMAND_CLASS_ATP_FLAG — select on-hand subinventories and whether demand class is considered.
• INCLUDE_SALES_ORDERS, INCLUDE_DISCRETE_WIP_DEMAND, INCLUDE_PURCHASE_ORDERS, and related INCLUDE_* flags — specify which supply and demand sources participate.
• Audit columns LAST_UPDATE_DATE, CREATED_BY, and the ATTRIBUTE1–ATTRIBUTE15 flexfield set.

Common Use Cases and Queries

Typical usage includes retrieving rule configuration for ATP diagnostics, comparing rules across instances, and joining rules to item or organization assignments. A representative query resolving a rule by its unique key:

• SELECT rule_id, rule_name, accumulate_available_flag, backward_consumption_flag, forward_consumption_flag FROM msc.msc_atp_rules WHERE sr_instance_id = :instance AND rule_id = :rule;
• SELECT rule_name, infinite_supply_fence_code, infinite_supply_time_fence, acceptable_early_fence, acceptable_late_fence FROM msc.msc_atp_rules WHERE sr_instance_id = :instance ORDER BY rule_name;
• Reporting on inclusion flags to audit which demand and supply sources feed ATP for a given rule.

Because the table is owned by MSC rather than APPS, queries should be executed from a session with visibility to the MSC schema, and joins to application-level rule assignments rely on RULE_ID and SR_INSTANCE_ID.

Related Objects

The ETRM relationship data classifies this object as standalone with no exported foreign keys, so dependencies are logical rather than enforced. The most significant related objects are:

• MSC_ATP_RULES assignments consumed by MSC planning engines — joined on RULE_ID and SR_INSTANCE_ID.
• MSC_ATP_RULE_ITEMS / ATP rule-to-item association tables — reference RULE_ID to attach rules to items or organizations.
• MRP/MSC planning parameter tables — reference an active ATP rule for a plan.
• OE_ORDER_LINES and scheduling APIs — consume ATP results derived from the selected rule.
• FND_STANDARD / WHO audit columns — LAST_UPDATED_BY and CREATED_BY resolve against application user tables.

When troubleshooting "msc_atp_rules_u1" lookups, the unique index on SR_INSTANCE_ID and RULE_ID is the definitive access path.