Search Results is_op_constrained

Overview

OE_LINE_ADJ_SECURITY is an Oracle Order Management security package in Oracle E-Business Suite 12.1.1 and 12.2.2 that enforces processing constraints on adjustments made to order lines. Processing constraints allow implementers to define business rules that restrict who may perform a given operation, under which conditions, and on which attributes. This package body provides the security enforcement layer for line-level price adjustment activity, ensuring that a user's responsibility, application, and the current transaction phase of an order are validated against the constraint definitions held in the processing constraints repository before an adjustment is permitted. The package is classified as OTHER within the ETRM repository and operates as an internal supporting unit of Order Management rather than as a publicly released API.

Key Procedures and Functions

The metadata documents a large suite of procedures and functions, many corresponding to individual order-line adjustment attributes and context fields. The central function identified in the source is IS_OP_CONSTRAINED, which accepts an operation name, an optional column name, an adjustment record, and returns an outcome indicator together with an action code describing what the caller should do when the operation is constrained. It resolves the user's responsibility and application identifiers from FND globals, determines the transaction phase code through the order cache, and delegates the actual constraint evaluation to OE_PC_CONSTRAINTS_ADMIN_PVT.IS_OP_CONSTRAINED.

The remaining documented members correspond to the configurable adjustment fields against which constraints may be applied: ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT, representing the descriptive flexfield segments of the line adjustment entity; AUTOMATIC, DISCOUNT, and the descriptive and administrative columns CREATED_BY and CREATION_DATE. These members supply or evaluate the individual column values used during constraint checking. Their presence reflects the standard pattern in which constraint logic is exposed per attribute so that the constraint administration layer can request evaluation of a specific field.

Tables Accessed

The package references OE_ORDER_HEADERS_ALL through an internal cursor that retrieves the BOOKED_FLAG for a given header identifier. This lookup establishes whether the order has been booked, since booking status governs which constraints remain active at the line adjustment stage. The package also references OE_PC_CONSTRAINTS, the processing constraints definition table, which stores the constraint identifiers, qualifying conditions, and on-operation actions consumed during evaluation. Access to both tables occurs through APPS synonyms. Additional state is obtained from OE_SYS_PARAMETERS, OE_CODE_CONTROL, OE_ORDER_CACHE, and OE_PC_GLOBALS to establish the audit trail flag, code release level, cached header transaction phase, and shared constraint constants.

Usage Notes

OE_LINE_ADJ_SECURITY is invoked indirectly whenever line adjustments are validated within the Order Management flow, including order entry forms that manipulate price adjustments and any concurrent or custom process that applies adjustments to existing order lines. Callers do not invoke the package directly; instead, the Order Management adjustment framework calls it during validation. Because it is referenced by 63 other packages, changes to its behavior have broad impact, and it should be treated as a restricted internal component. The IS_OP_CONSTRAINED function checks the code release level and loads the order header into cache before evaluation, so it depends on the correct initialization of Order Management globals and cache structures at call time. Customizations should avoid modifying this package and should instead define appropriate processing constraints through the supported constraint administration interface.