Search Results oe_item_orderability_s

Overview

The APPS.OE_ITORD_PUB package body provides the public API layer for managing and validating item orderability rules within Oracle Order Management. Item orderability determines whether a specific item may be ordered by a given customer, ship-to location, or within a defined context, and it is governed by configurable rules stored in the OE_ITEM_ORDERABILITY_RULES table. The package serves as the programmatic entry point through which Order Management forms, concurrent processes, and custom extensions create, validate, and persist these rules.

The package is classified as a PUB (public) API, indicating it is intended for supported external invocation rather than internal use only. Its responsibilities include importing rule definitions, enforcing mandatory and conditional field validation, detecting duplicate rule conditions, resolving descriptive flexfield (DFF) values, and inserting validated rules into the underlying schema. It operates against Oracle E-Business Suite 12.1.1 and 12.2.2 and is owned by the APPS schema, with status VALID in the deployed instance.

Key Procedures and Functions

The package exposes eight documented procedures and functions that together form a complete rule-management workflow:

• IMPORT_ITEM_ORDERABILITY_RULES — Orchestrates the import of item orderability rule data, invoking the downstream validation and insertion logic to load rules into the application tables.
• CHECK_REQUIRED_FIELDS — Verifies that all mandatory attributes for an orderability rule are populated before further processing proceeds.
• VALIDATE_REQUIRED_FIELDS — Performs validation on required fields, confirming their values are both present and consistent with expected formats or reference data.
• VALIDATE_CONDITIONAL_FIELDS — Applies conditional validation logic, where field requirements depend on the values of other rule attributes (for example, a customer-specific rule requiring an associated customer identifier).
• CHECK_DUPLICATE_RULES — Detects whether a candidate rule duplicates an existing definition, preventing redundant or conflicting orderability configurations.
• GET_RULE_COULUMN_DETAILS — Retrieves metadata describing the rule columns, supporting dynamic column handling and user-facing descriptions. Note the documented spelling "COULUMN" reflects the delivered object name.
• VALIDATE_RULES_DFF — Validates descriptive flexfield segments associated with rules, invoking flexfield validation services to confirm segment values are valid.
• INSERT_RULES — Persists validated rule records into the orderability rule tables, completing the import or maintenance transaction.

Tables Accessed

The package reads and writes across Order Management, inventory, and trading-partner schemas. Core rule storage resides in OE_ITEM_ORDERABILITY, OE_ITEM_ORDERABILITY_RULES, and OE_ITEM_ORDERABILITY_S. Item context is resolved through MTL_SYSTEM_ITEMS_B, MTL_ITEM_CATEGORIES, MTL_CATEGORIES, and MTL_DEFAULT_CATEGORY_SETS. Customer and party data is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_PROFILE_CLASSES, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES. Supporting lookups come from AR_LOOKUPS, OE_LOOKUPS, OE_ORDER_TYPES_V, RA_SALESREPS, HR_OPERATING_UNITS, FND_USER, WSH_REGIONS_V, and system parameters. Utility sources include FND_API, FND_MESSAGE, FND_GLOBAL, FND_FLEX_DESCVAL, OE_DEBUG_PUB, OE_MSG_PUB, OE_ITORD_UTIL, and DUAL.

Usage Notes

OE_ITORD_PUB is typically invoked from the Order Management item orderability setup forms and from concurrent programs that bulk-load or migrate orderability rules. Because it is documented as a public API, custom code may call it to import rules during implementation or data conversion. Validations should always be run before insertion to preserve rule integrity. The package is not referenced by any other database object, confirming its role as a top-level entry point rather than a shared internal utility.