Results for “lock_rule”

48 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WMS_RULE_FORM_PKG is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It provides the programmatic backbone for the Warehouse Management System (WMS) rules maintenance form, the user interface through which warehouse administrators define, maintain and enforce the put-away, picking and replenishment rules that govern material movement inside a warehouse. The package encapsulates all form-level business logic for the WMS Rules window, separating presentation-tier concerns from the underlying API layer exposed by WMS_RULES_PKG, WMS_RULE_CONSISTENCIES_PKG and the restriction and sort-criteria packages.

The object is documented with status VALID and is classified as API classification OTHER, indicating it is not a public integration API but rather an internal form-support package. It is referenced by two other database objects, confirming its role as a dependency for higher-level WMS components. Its dependency list includes FND_API, FND_GLOBAL, FND_MESSAGE and FND_MSG_PUB, establishing that it participates in the standard Oracle Forms error-handling and message-stack conventions used throughout EBS.

Key Procedures and Functions

The package body exposes seven documented procedures and functions, all oriented toward the rule maintenance lifecycle:

  • INSERT_RULE — Creates a new rule record, invoking the underlying WMS_RULES_PKG API and initialising rule header attributes.
  • UPDATE_RULE — Applies modifications to an existing rule, including changes to consistency and sort-criteria definitions.
  • DELETE_RULE — Removes a rule record and its associated child rows, respecting referential integrity with rule consistencies and restrictions.
  • COPY_RULE — Duplicates an existing rule, including its consistencies and sort criteria, to accelerate configuration of similar warehouse logic.
  • LOCK_RULE — Obtains a logical lock on a rule row to prevent concurrent modification by another form session.
  • FIND_RULE — Retrieves rule data for display or validation, populating the form block from the WMS_RULES base tables.
  • CHECK_WMS_RULE_EXISTS — A validation utility that determines whether a given rule already exists, typically used to prevent duplicates before insert.

Tables Accessed

The package reads and writes the core WMS rule schema through APPS synonyms:

  • WMS_RULES, WMS_RULES_B, WMS_RULES_S — the base, base-translation and sequence/denormalised tables holding rule header data.
  • WMS_RULE_CONSISTENCIES, WMS_RULE_CONSISTENCIES_S — child tables storing the consistency conditions that constrain when a rule fires; the user search term wms_rule_consistencies_s maps directly to this sequence/summary table.
  • WMS_RESTRICTIONS — restriction definitions associated with rules (item, locator, category and similar criteria).
  • WMS_SORT_CRITERIA — ordering criteria used to sequence candidate records during rule evaluation.
  • DUAL — accessed for singleton queries and validation checks.

Usage Notes

WMS_RULE_FORM_PKG is invoked primarily from the Oracle Forms-based WMS Rules maintenance window. It is not intended for direct external calls; integrators requiring rule manipulation should use the published WMS_RULES_PKG and WMS_RULE_CONSISTENCIES_PKG interfaces instead. The package supports the standard EBS interaction pattern: forms block triggers call these procedures, which in turn delegate to WMS_RULES_PKG, WMS_RULE_CONSISTENCIES_PKG, WMS_RESTRICTION_FORM_PKG and WMS_SORT_CRITERIA_FORM_PKG. Because it references FND_MSG_PUB and FND_MESSAGE, errors are surfaced through the standard message stack, and FND_API provides the standard return-status conventions. Customisations should not modify this package body directly; extending rule behaviour is best accomplished through the documented APIs it depends upon.