Search Results om




The OE_SYS_PARAMETER_DEF_B table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for system-level parameters governing the behavior of the Order Management (OM) module. As part of the Oracle Order Management foundation, this table stores default parameter definitions that influence processing rules, validations, and configurations across order entry, fulfillment, and pricing workflows. Below is a detailed analysis of its structure, purpose, and functional significance.

Table Overview

OE_SYS_PARAMETER_DEF_B is a base table (denoted by the "_B" suffix) that stores metadata for system parameters, including data types, default values, and validation constraints. It serves as the backbone for the OE_SYS_PARAMETERS_ALL table, which holds parameter values at the operating unit (org_id) level. Key columns include:
  • PARAMETER_ID: Primary key uniquely identifying each parameter.
  • PARAMETER_CODE: Unique code (e.g., "OM_ITEM_VALIDATION_LEVEL") used programmatically.
  • DATA_TYPE: Defines the parameter's data type (VARCHAR2, NUMBER, DATE).
  • DEFAULT_VALUE: Fallback value if no org-specific setting exists.
  • DESCRIPTION: Business context for the parameter's usage.
  • ENABLED_FLAG: Determines if the parameter is active (Y/N).

Functional Role

This table enables centralized control over OM behaviors such as:
  • Order Validation: Parameters like "OM_ITEM_VALIDATION_LEVEL" enforce item attribute checks.
  • Pricing: Defaults for price list hierarchies or rounding rules.
  • Fulfillment: Settings for auto-scheduling or shipping tolerances.
  • Integration: Flags for interfacing with Inventory, AR, or Procurement.

Implementation Notes

  1. Multi-Org Support: While OE_SYS_PARAMETER_DEF_B stores definitions, OE_SYS_PARAMETERS_ALL holds org-specific values via ORG_ID.
  2. Upgrades/Migrations: Custom parameters added to this table must be preserved during EBS upgrades.
  3. Performance: Indexes on PARAMETER_CODE optimize lookup during order processing.
  4. Audit Trail: Changes to parameters may require logging via triggers or audit tables.

Example Use Cases

  • Setting OM_DEFAULT_PRICE_LIST to enforce a standard price list for new orders.
  • Configuring OM_AUTO_BOOK_ORDER to automate order booking upon submission.
  • Defining OM_SHIPPING_TOLERANCE_PERCENT to allow over/under shipments.

Technical Considerations

  • APIs: Use OE_PARAMETER_PUB PL/SQL package for programmatic access.
  • Security: Direct DML on this table is discouraged; leverage Oracle's seeded APIs.
  • Custom Extensions: New parameters require updates to both this table and associated UI screens.

Version-Specific Notes

In EBS 12.2.2, this table remains structurally consistent with 12.1.1 but may include additional parameters supporting new features like Advanced Pricing enhancements or REST API integrations. Always reference the Oracle Data Dictionary (ALL_TAB_COLUMNS) for version-specific columns. In summary, OE_SYS_PARAMETER_DEF_B is a foundational table for configuring and standardizing Order Management operations. Its design ensures flexibility while maintaining governance, making it indispensable for EBS implementations requiring tailored order workflows.