Search Results oe_blanket_line_security




Overview
Explore in AI Chat

Overview

OE_BLANKET_LINE_SECURITY is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It implements the line-level security framework for blanket sales agreements processed through Oracle Order Management. Blanket agreements permit customers to place releases against pre-negotiated terms over an extended period, and the business requires that individual blanket lines be visible only to authorized operating units, organizations, or responsibility contexts. This package enforces those restrictions by evaluating the current runtime context against the attribute constraints maintained in the Oracle Pricing constraint engine.

The object is registered as VALID in both ETRM 12.1.1 and 12.2.2, and its API classification is OTHER, indicating that it is an internal supporting package rather than a public-interface API. It is referenced by 54 other database objects within the APPS schema, confirming its role as a foundational dependency for blanket agreement inquiry, release, and validation flows. It does not itself appear as a referenced object in any external dependency beyond the standard PL/SQL runtime and the application foundation packages it consumes.

Key Procedures and Functions

The documented package exposes 65 procedures and functions. The listed members map to specific blanket-line attributes that participate in the security and defaulting evaluation:

  • ACCOUNTING_RULE — resolves or validates the accounting rule associated with a blanket line for security filtering.
  • CUST_PO_NUMBER — handles the customer purchase order number attribute on the line.
  • DELIVER_TO_ORG — evaluates the deliver-to organization, a primary security dimension for line visibility.
  • FREIGHT_TERMS — processes the freight terms attribute.
  • INVENTORY_ITEM — resolves the inventory item on the blanket line.
  • INVOICE_TO_ORG — evaluates the invoice-to organization as a security constraint.
  • INVOICING_RULE — processes the invoicing rule attribute.
  • LINE_NUMBER — handles the line sequence identifier.
  • ORDER_QUANTITY_UOM — resolves the order quantity unit of measure.
  • PACKING_INSTRUCTIONS — processes packing instruction text on the line.
  • PAYMENT_TERM — evaluates the payment term attribute.
  • PRICE_LIST — resolves the price list associated with the line.
  • PRICING_QUANTITY_UOM — resolves the pricing quantity unit of measure.
  • SALESREP — evaluates the sales representative, frequently used as a security and visibility dimension.
  • SHIPPING_INSTRUCTIONS — processes shipping instruction text.
  • SHIPPING_METHOD — resolves the shipping method.
  • SHIP_FROM_ORG — evaluates the ship-from organization as a security constraint.
  • SHIP_TO_ORG — evaluates the ship-to organization, another primary visibility dimension.
  • UNIT_LIST_PRICE — resolves the unit list price for the line.
  • ITEM_IDENTIFIER_TYPE — resolves the item identifier type used for item resolution.

Parameter lists are intentionally not reproduced here; the ETRM metadata documents member existence and purpose only.

Tables Accessed

The documented table references are OE_PC_CONSTRAINTS and PLITBLM, both accessed through APPS synonyms.

  • OE_PC_CONSTRAINTS — the constraint store used by the Oracle Pricing constraint engine. The security package reads these constraint definitions to determine which line attributes restrict visibility for the current user context. Related administrative logic in OE_PC_CONSTRAINTS_ADMIN_PVT is also referenced.
  • PLITBLM — a public PL/SQL table used as an in-memory working structure during processing, consistent with the package's pattern of building and filtering collections in PL/SQL.

The package also depends on view OE_AK_BLANKET_LINES_V for the attribute values evaluated against the constraints, and on OE_BLANKET_PUB, OE_BLANKET_UTIL, FND_API, FND_GLOBAL, FND_PROFILE, OE_CODE_CONTROL, OE_DEBUG_PUB, OE_GLOBALS, OE_MSG_PUB, OE_PC_GLOBALS, OE_SYS_PARAMETERS, and OE_VERSIONING_UTIL for standards-compliant API handling, profile lookups, messaging, and versioning support.

Usage Notes

Because this package is classified as OTHER and is referenced by 54 other objects, it is invoked implicitly rather than called directly by end users. Typical invocation paths include:

  • Order Management forms — the Blanket Sales Agreement and blanket line inquiry windows, where line visibility must be filtered according to the current responsibility and organization context.
  • Release processing — when blanket lines are queried or selected for release into an order.
  • Concurrent programs and internal APIs — batch validation and pricing flows that consume blanket line data.
  • Custom extensions — the package should not be called directly by custom code; the supported integration point is OE_BLANKET_PUB, which this package supports internally.

Implementers diagnosing blanket line security behavior should inspect the constraint definitions in OE_PC_CONSTRAINTS and the enablement profile options resolved through FND_PROFILE, since the package's decisions are driven entirely by that configuration. Debug tracing is available through OE_DEBUG_PUB when the appropriate diagnostic profile settings are enabled.