Search Results mtl_atp_rules




The MTL_ATP_RULES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository for configuring Available-to-Promise (ATP) rules within the Inventory and Order Management modules. ATP functionality enables organizations to determine product availability in real-time, considering current inventory, supply chain constraints, and demand commitments. This table stores rule-based parameters that govern how ATP calculations are performed, ensuring accurate promise dates and inventory allocations. Below is a detailed breakdown of its structure, purpose, and usage in Oracle EBS.

Purpose of MTL_ATP_RULES

The MTL_ATP_RULES table defines the rulesets used by Oracle ATP engines to evaluate product availability. These rules influence whether ATP checks consider factors like:
  • On-hand inventory: Current stock levels at specific subinventories or organizations.
  • Supply and demand: Purchase orders, work orders, or sales orders in the pipeline.
  • Lead times: Supplier or manufacturing lead times for replenishment.
  • Allocation rules: Prioritization of orders (e.g., first-come-first-serve or customer priority).
ATP rules are assigned to items, categories, or organizations, allowing granular control over availability checks.

Key Columns in MTL_ATP_RULES

The table includes columns that define rule behavior, such as:
  • RULE_ID: Primary key, uniquely identifying each ATP rule.
  • ORGANIZATION_ID: Links the rule to a specific inventory organization.
  • RULE_NAME: User-defined name for the rule (e.g., "Global ATP" or "Priority Customer Rule").
  • ATP_FLAG: Determines whether ATP is enabled (Y/N) for the rule.
  • ATP_COMPONENTS_FLAG: Controls whether component-level ATP checks are performed for assemblies.
  • PEGGING_FLAG: Specifies if pegging (linking supply to demand) is used during ATP.
  • HORIZON_DAYS: Defines the time window (in days) for which ATP calculations are valid.
  • ENFORCE_CAPACITY: Indicates whether resource capacity constraints are considered (Y/N).

Integration with Oracle EBS Modules

The MTL_ATP_RULES table integrates with several EBS modules:
  • Inventory: Assigns ATP rules to items or categories via MTL_SYSTEM_ITEMS_B or MTL_ITEM_CATEGORIES.
  • Order Management: Uses ATP rules to validate order promises during booking or scheduling.
  • Advanced Supply Chain Planning (ASCP): Shares rule definitions for planning simulations.

Configuration and Usage

Administrators configure ATP rules via Oracle Forms or APIs, such as:
  • ATP Rule Form: Navigate to Inventory > Setup > ATP Rules to define or modify rules.
  • APIs: Use INV_ATP_PUB PL/SQL packages for programmatic rule management.
Once configured, rules are referenced during:
  • Sales order entry (promise date validation).
  • Inventory replenishment workflows.
  • Backorder processing.

Example SQL Query

To retrieve active ATP rules for an organization: 
SELECT rule_id, rule_name, atp_flag, horizon_days 
FROM mtl_atp_rules 
WHERE organization_id = 101 
AND atp_flag = 'Y';

Conclusion

The MTL_ATP_RULES table is foundational for Oracle EBS ATP functionality, enabling businesses to balance supply and demand dynamically. Proper configuration ensures accurate delivery commitments, reduces stockouts, and optimizes inventory utilization. Organizations leveraging ATP rules effectively gain a competitive edge through improved customer service and operational efficiency.