Search Results sales




The OE_BLANKET_LINES_ALL table is a fundamental component of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically within the Order Management (OM) module. It stores detailed information about blanket sales agreement lines, which are long-term agreements between buyers and sellers outlining terms, pricing, and products/services to be delivered over a specified period. This table is part of the multi-org architecture, meaning it contains data for all operating units, distinguished by the ORG_ID column.

Key Attributes and Structure

The OE_BLANKET_LINES_ALL table includes critical columns such as:
  • LINE_ID: Primary key identifier for each blanket line.
  • HEADER_ID: Foreign key linking to OE_BLANKET_HEADERS_ALL, associating lines with their parent agreement.
  • INVENTORY_ITEM_ID: References MTL_SYSTEM_ITEMS_B to identify the product/service.
  • ORDERED_QUANTITY: Total quantity agreed upon in the blanket line.
  • UNIT_SELLING_PRICE: Pre-negotiated unit price for the item.
  • SHIP_FROM_ORG_ID: Indicates the inventory organization fulfilling the order.
  • SHIP_TO_ORG_ID: References HR_ALL_ORGANIZATION_UNITS for the delivery location.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard Oracle audit columns.

Functional Role in Order Management

Blanket agreements streamline procurement by eliminating repetitive negotiations. The OE_BLANKET_LINES_ALL table enables:
  • Pricing Consistency: Enforces pre-agreed pricing via the UNIT_SELLING_PRICE column, reducing manual input errors.
  • Quantity Tracking: Toggles ORDERED_QUANTITY against FULFILLED_QUANTITY to monitor remaining commitments.
  • Release Generation: Serves as a template for release orders (stored in OE_ORDER_LINES_ALL), ensuring compliance with agreement terms.

Integration with Other Modules

The table interacts with:
  • Inventory (INV): Validates item availability via INVENTORY_ITEM_ID and SHIP_FROM_ORG_ID.
  • Advanced Pricing: Applies complex pricing rules through modifiers linked to LINE_ID.
  • Receivables (AR): Feeds billing data when blanket lines are invoiced.

Technical Considerations

  • Multi-Org Access Control (MOAC): Queries must filter by ORG_ID to avoid cross-org data leaks.
  • Indexing: Key indexes include OE_BLANKET_LINES_N1 (HEADER_ID) and OE_BLANKET_LINES_U1 (LINE_ID) for performance.
  • Data Retention: Large volumes may require archival strategies, as historical blanket data is often retained for audits.

Customization and Extensions

Common extensions include:
  • Descriptive Flexfields (DFFs): Adding custom attributes like contract-specific metadata.
  • API Hooks: Using OE_BLANKET_LINES_PUB to programmatically create/modify lines.
  • Workflow: Triggering approvals based on line attributes (e.g., high-value items).

Conclusion

The OE_BLANKET_LINES_ALL table is pivotal in Oracle EBS Order Management, providing the structural foundation for blanket sales agreements. Its design supports multi-org operations, enforces contractual terms, and integrates seamlessly with inventory, pricing, and financial modules. Proper utilization ensures efficient long-term order processing while maintaining data integrity across the enterprise.