Search Results rla_schedule_type_code




Overview

APPS.OE_CRM_ORDER_LINES_V is a reporting and integration view within the Oracle E-Business Suite Order Management (OM) module. It exposes order line information in a flattened, denormalized form intended for consumption by CRM applications, external interfaces, and analytical reporting. The view presents line-level attributes spanning order entry, shipping, pricing, taxation, and demand scheduling, allowing downstream systems to retrieve comprehensive sales order line detail without joining multiple base tables directly. Because it is owned by APPS and exposed as a synonym, it is accessible to any database user granted the appropriate privileges, making it a common reference point for custom reports, extracts, and interface programs in both release 12.1.1 and 12.2.2.

Underlying Base Objects

According to the documented metadata, the view is defined over a single referenced base object: OE_ORDER_LINES (exposed through a synonym). OE_ORDER_LINES is the core transactional table in Order Management that stores line-level order data, including identifiers, quantities, dates, pricing, and descriptive flexfield columns. The view selects a defined subset of columns from this table, projecting them without the multi-table joins that characterize other OM views such as those that combine headers, lines, and shipments. Practically, this means the view inherits the granularity of OE_ORDER_LINES: one row per order line. The release notes identify the same base object for both 12.1.1 and 12.2.2, indicating structural continuity across the two releases with respect to this view.

Key Columns

The view exposes a broad set of line attributes. Notable groupings include:

RLA_SCHEDULE_TYPE_CODE is significant because it relates to return line authorization (RLA) scheduling. In Order Management, return authorizations carry a schedule type that governs how returned goods are scheduled and received. Querying this column allows integration and reporting logic to identify the scheduling behavior associated with return-related order lines.

Common Use Cases and Queries

The view supports sales order reporting, CRM data synchronization, and return processing extracts. A typical query retrieves scheduling detail for return lines:

  • SELECT line_id, header_id, ordered_item, ordered_quantity, rla_schedule_type_code FROM apps.oe_crm_order_lines_v WHERE rla_schedule_type_code IS NOT NULL;
  • SELECT header_id, line_number, ordered_item, promise_date, shipped_quantity FROM apps.oe_crm_order_lines_v WHERE org_id = :p_org AND ordered_quantity > shipped_quantity;
  • SELECT line_id, sold_to_org_id, unit_selling_price, tax_value FROM apps.oe_crm_order_lines_v WHERE tax_exempt_flag = 'Y';

These patterns illustrate how the view simplifies retrieval of consolidated line data for integration and analysis without direct access to OE_ORDER_LINES.