Results for “reservation_exists”

46 results




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

Overview

CTO_OM_WF_API is an Oracle Applications (APPS) PL/SQL package that belongs to the Configure-to-Order (CTO) module and integrates with the Oracle Order Management (OM) and Oracle Workflow (WF) validation framework. In Oracle EBS 12.1.1 and 12.2.2, the package is classified in the ETRM repository as an API and is owned by the APPS schema. Its primary business function is to supply validation logic to Oracle Workflow-driven security constraints that govern whether modifications to an order line are permissible. Specifically, the package provides the Reservation_Exists validation template, which determines whether a change attempted against a configured order line should be allowed based on reservation status.

The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the defining APPS user. This design supports the standard Oracle Workflow validation signature model, allowing the package to be called safely from within workflow-driven constraint evaluation.

Key Procedures and Functions

ETRM documents a single procedure in this package: RESERVATION_EXISTS. Its documented purpose is to serve as the API that is called from security constraints to validate whether a change is allowed on an order line. The procedure is associated with the Reservation_Exists Validation Template.

The procedure conforms to the standard Oracle Workflow validation signature format, accepting the set of standard parameters — application identifier, entity short name, validation entity short name, validation template short name, record set short name, and scope — and returning a result through an OUT parameter. Per the documented metadata, the parameter list is fixed by the standard signature and should not be altered. The OUT result communicates the validation outcome, indicating whether a reservation exists such that the attempted change must be constrained.

Because the package contains only this single documented procedure, it should be regarded as a narrowly scoped, purpose-built validation API rather than a general-purpose utility package. Custom development should not extend or overload its documented signature.

Tables Accessed

The ETRM metadata for this object does not list any tables referenced via APPS synonyms. This absence indicates either that the package performs no direct SQL against base tables, or that its data access is indirect — for example, through calls to other APIs or through workflow attribute data supplied by the calling validation framework. Because no tables are documented, no table-level dependencies should be assumed when planning upgrades, cloning, or dependency analysis. Any implementation-level verification should be performed against the actual package body in the target environment, since the documented metadata is the authoritative source provided here.

Usage Notes

CTO_OM_WF_API is intended to be invoked indirectly by the Oracle Workflow validation engine rather than being called directly from forms, concurrent programs, or ad hoc custom code. It is wired into the system through the Reservation_Exists validation template, which is referenced by security constraints that protect configured order lines. When a user or process attempts a change against such a line, the validation framework calls the procedure, and the returned result governs whether the change proceeds or is blocked.

Because the package adheres to the standard Workflow validation signature, invocation is performed by the framework with the correct application ID, entity names, template names, record set, and scope values. The ETRM metadata records that the package is referenced by zero other packages, confirming it is a terminal validation component rather than a shared library. Extensions should therefore be implemented by configuring the associated validation template and its security constraints, not by modifying the package or calling it from custom code. The package header identifies a 2003 revision (115.1), indicating it is a long-standing, stable component of the CTO/OM validation infrastructure across both 12.1.1 and 12.2.2 releases.