Search Results oe_itord_pub




Overview
Explore in AI Chat

Overview

OE_ITORD_PUB is a public PL/SQL API in the Oracle E-Business Suite Order Management (OE) module that manages item orderability rules. Item orderability rules determine whether a specific inventory item may be ordered by a given customer, customer class, or customer category, and they can be scoped further by region, order type, ship-to location, sales channel, salesperson, and end customer. This package provides the programmatic interface for importing and maintaining the records stored in the OE_ITEM_ORDERABILITY family of tables, which the Order Management application consults during order entry to enforce selling restrictions.

The package is classified as a PUB (public) API, meaning it is intended for direct invocation by external callers such as concurrent programs, Oracle Forms, and custom code. The header comment (OEXPITOS.pls 120.1) indicates the source file was last revised in 2008, and the object remains documented in ETRM for both 12.1.1 and 12.2.2. It is not referenced by any other package, so it represents a top-level entry point rather than a shared internal utility.

A central element of the package is the Item_Orderability_Import_Rec record type, which maps nearly every column of the OE_ITEM_ORDERABILITY table, including the 20 DFF attribute columns and the CONTEXT column. A companion collection type, Item_Orderability_Import_Tbl, is an associative array indexed by BINARY_INTEGER, allowing callers to pass batches of orderability rules in a single call.

Key Procedures and Functions

  • IMPORT_ITEM_ORDERABILITY_RULES — The primary driver procedure. It accepts the import table type and a commit flag (defaulting to 'N') and processes the supplied set of orderability rules, orchestrating validation and insertion.
  • CHECK_REQUIRED_FIELDS — Examines an inbound Item_Orderability_Import_Rec record and populates the STATUS and MSG_COUNT/MSG_DATA fields to signal whether mandatory attributes are present. This is the procedure most commonly referenced by callers preparing data for import.
  • VALIDATE_REQUIRED_FIELDS — Performs field-level validation of required attributes, distinct from the presence check performed by CHECK_REQUIRED_FIELDS.
  • VALIDATE_CONDITIONAL_FIELDS — Validates attributes that are mandatory only under certain conditions, such as when a rule level or enable flag implies additional required values.
  • CHECK_DUPLICATE_RULES — Detects whether a submitted rule duplicates an existing orderability rule, preventing redundant or conflicting entries.
  • GET_RULE_COULUMN_DETAILS — Returns column metadata for the rule structures, supporting dynamic handling of the rule attributes (note the original spelling of "COULUMN" in the API name).
  • VALIDATE_RULES_DFF — Validates the descriptive flexfield segments carried in the CONTEXT and ATTRIBUTE1–20 columns.
  • INSERT_RULES — Writes the validated rules into the OE_ITEM_ORDERABILITY tables.

Tables Accessed

Usage Notes

OE_ITORD_PUB is typically invoked from the Item Orderability setup UI in Oracle Order Management, from concurrent programs that bulk-load orderability rules, and from custom PL/SQL code that needs to create or refresh rules during data migration or integration. Callers populate an Item_Orderability_Import_Tbl collection, invoke CHECK_REQUIRED_FIELDS or the individual validation routines to inspect STATUS and MSG_DATA, and finally call IMPORT_ITEM_ORDERABILITY_RULES with an explicit commit flag. Because the package is unpublished to other code (referenced by zero packages), implementers should treat it as an API surface and expect its internal validation routines to enforce all business rules before any row reaches OE_ITEM_ORDERABILITY.