Search Results ua_sched_attr1




Overview
Explore in AI Chat

Overview

The ITG_SP_REL_LINE_SCHED_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite environment (validated on 12.1.1 and 12.2.2). It belongs to the ITG – Internet Procurement Enterprise Connector product, a module that bridges Oracle Purchasing with external procurement and supplier portals. As its description states, the view "is used to generate XML at po release line schedules level." In practice, it flattens purchase order release line schedule (shipment) data into a denormalized, integration-friendly structure suitable for outbound XML payloads consumed by supplier networks, punchout systems, or third-party middleware.

The view's distinctive role is that it renames and exposes the descriptive flexfield (DFF) attribute columns of the schedule level as a contiguous sequence of generic placeholders, UA_SCHED_ATTR1 through UA_SCHED_ATTR15. This design lets the connector carry customer-specific DFF values through the XML generation layer without binding the integration to any particular business meaning, which is precisely why a search for ua_sched_attr15 surfaces this object.

Underlying Base Objects

The view is defined over three referenced base objects, all accessed through APPS synonyms:

The joins are inner joins, so only schedule rows whose parent line and matching UOM record both exist are returned. The header and release identifiers (PO_HEADER_ID, PO_RELEASE_ID) flow through directly from PO_LINE_LOCATIONS_ALL, allowing the consuming XML process to group schedules under their parent release and header.

Key Columns

  • PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_ID, LINE_LOCATION_ID – the identifying keys of the header, release, line, and shipment respectively.
  • DATETIME_NEEDDELV – the delivery date, computed as NVL(NEED_BY_DATE, PROMISED_DATE), ensuring a value is always returned even when the need-by date is null.
  • ORDERED_QUANTITY – the schedule quantity; ORDERED_UOM – the resolved unit of measure code.
  • SHIPMENT_NUM – the shipment/schedule number within the line.
  • UA_SCHEDLID – the LINE_LOCATION_ID cast to character via TO_CHAR, providing a string schedule identifier for XML.
  • UA_SCHED_ATTR1 … UA_SCHED_ATTR15 – the line-location descriptive flexfield segments, mapped one-to-one from PLLA.ATTRIBUTE1 through PLLA.ATTRIBUTE15. UA_SCHED_ATTR15 is the fifteenth and final DFF slot, typically reserved for a customer-configured value.

Common Use Cases and Queries

The view supports release-line schedule extraction for interface and reconciliation reporting. A typical query retrieving the fifteenth flexfield alongside shipment detail is:

  • SELECT PO_RELEASE_ID, PO_LINE_ID, LINE_LOCATION_ID, DATETIME_NEEDDELV, ORDERED_QUANTITY, ORDERED_UOM, UA_SCHED_ATTR15 FROM APPS.ITG_SP_REL_LINE_SCHED_V WHERE PO_RELEASE_ID = :p_release_id;
  • Filtering on a populated UA_SCHED_ATTR15 value to audit which schedules carry a specific supplier or contract reference.
  • Joining back to PO_LINE_LOCATIONS_ALL or PO_HEADERS_ALL to enrich the extracted schedules with supplier and currency context prior to XML generation.

Because the view reads directly from transactional Purchasing tables, queries should be scoped by header, release, or date ranges to limit execution cost in high-volume environments.