Results for “min_release_amount”

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

Overview

APPS.OE_BLANKET_LINE_SECURITY is a PL/SQL package within the Oracle Order Management module of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. Its principal business function is to enforce attribute-level security and validation on blanket sales agreement lines. Blanket sales agreements in Order Management allow organizations to pre-negotiate pricing, terms, and item commitments with customers over a defined period; individual releases are subsequently drawn against the agreement. Because blanket lines carry many commercially sensitive attributes — price lists, payment terms, freight terms, sales representatives, and shipping instructions — the application must control which attributes a given user or responsibility may view or modify.

OE_BLANKET_LINE_SECURITY implements this control through a set of per-attribute validation functions that are wired into the Oracle AK (Attribute Knowledge) validation framework. Each function evaluates whether an operation against a specific attribute is permitted, returning a status and an operation-action indicator to the calling framework. The package therefore acts as the security gatekeeper for the Blanket Lines entity, operating alongside the generated validation packages that Oracle's attribute framework produces.

Key Procedures and Functions

The documented interface comprises 65 procedures and functions, of which 20 are explicitly identified in the source excerpt. Each function accepts an operation parameter (defaulting to the update operation defined in OE_PC_GLOBALS), a record based on the OE_AK_BLANKET_LINES_V view, and an OUT parameter indicating the action the framework should take. The attribute-specific functions include:

• ACCOUNTING_RULE — validates security for the accounting rule attribute on a blanket line.
• CUST_PO_NUMBER — governs the customer purchase order number attribute.
• DELIVER_TO_ORG — controls the deliver-to organization attribute.
• FREIGHT_TERMS — secures the freight terms attribute.
• INVENTORY_ITEM and ITEM_IDENTIFIER_TYPE — govern the inventory item and its identifier type.
• INVOICE_TO_ORG and INVOICING_RULE — control invoice-to organization and invoicing rule attributes.
• LINE_NUMBER — secures the blanket line number itself.
• ORDER_QUANTITY_UOM and PRICING_QUANTITY_UOM — validate the order and pricing quantity units of measure.
• PACKING_INSTRUCTIONS, SHIPPING_INSTRUCTIONS, and SHIPPING_METHOD — govern shipping-related instruction attributes.
• PAYMENT_TERM — secures the payment term attribute.
• PRICE_LIST and UNIT_LIST_PRICE — control price list and unit list price attributes.
• SALESREP — governs the sales representative attribute.
• SHIP_FROM_ORG and SHIP_TO_ORG — control ship-from and ship-to organization attributes.

Tables Accessed

The package references two tables through APPS synonyms. OE_PC_CONSTRAINTS stores constraint definitions used by the Order Management attribute and processing framework; the package consults it to determine which attribute constraints apply during validation. PLITBLM is an Order Management line table used in the blanket line processing context. The package additionally depends heavily on the OE_AK_BLANKET_LINES_V view, whose rowtype defines the global entity record g_record and the p_record parameter used throughout the validation functions.

Usage Notes

OE_BLANKET_LINE_SECURITY is invoked indirectly rather than called directly by end users. It is registered with the Oracle AK attribute validation framework, which invokes the appropriate attribute function during Blanket Sales Agreement entry, update, and release processing in the Order Management forms. The package is referenced by 54 other packages, indicating broad integration across Order Management validation and processing logic. Customizations that extend or override blanket line attribute security should be implemented through the supported attribute framework rather than by modifying this package, since it is a seeded, nonshipped-header object subject to patching. Developers writing custom validation logic may call individual functions, but must supply a properly populated OE_AK_BLANKET_LINES_V%ROWTYPE record and handle the returned operation-action indicator correctly.