Search Results ship_method_text

Overview

MRP_SCATP_SUPPLY_SOURCES_V is an APPS-owned database view within the Oracle E-Business Suite Master Scheduling/MRP product family. It functions as a Supply Chain ATP (Available-to-Promise) supply source view, exposing the sourcing and availability information required to evaluate supplier-based supply and promised availability dates in a global or distributed ATP context.

The view is a central reference for supply chain ATP processing, where availability of supply is not limited to on-hand inventory in a single warehouse but extends to vendor-sourced material, in-transit lead times, and schedule/ATP grouping attributes. Because it is registered as a VALID view in Oracle ETRM metadata for EBS 12.1.1 and 12.2.2, it is treated as a supported read-only reporting and integration object. The user search term "group_available_date" corresponds directly to the GROUP_AVAILABLE_DATE column exposed by this view, which is likely the attribute of primary interest for availability-date reporting.

Underlying Base Objects

The view is defined through a join of several core EBS objects. The documented referenced base objects are:

• FND_COMMON_LOOKUPS (VIEW) — provides lookup meaning for the ship method; joined with the SHIP_METHOD lookup type under application 401.
• FND_GLOBAL (PACKAGE) — used for session context (SESSION_ID and related session attributes).
• MTL_DEMAND_INTERFACE (SYNONYM) — aliased as D, the driving table supplying session, group, organization, ship method, vendor, and availability attributes.
• MTL_PARAMETERS (SYNONYM) — aliased as P, supplying the organization code for the organization context.
• PO_VENDORS (VIEW) — aliased as VENDOR, supplying vendor name.
• PO_VENDOR_SITES_ALL (VIEW) — aliased as SITE, supplying vendor site code.

The join conditions link MTL_DEMAND_INTERFACE to MTL_PARAMETERS on ORGANIZATION_ID, and use outer joins (+) for the ship method lookup, vendor, and vendor site records, so supply source rows remain visible even where lookup or vendor reference data is absent.

Key Columns

The view exposes the following important columns:

• SESSION_ID — Identifies the ATP/supply session context for the row.
• SCHEDULE_GROUP_ID and ATP_GROUP_ID — Grouping identifiers used to aggregate supply sources for schedule and ATP checking.
• ORGANIZATION_ID and ORGANIZATION_CODE — The inventory organization and its code, joined from MTL_PARAMETERS.
• SHIP_METHOD and SHIP_METHOD_TEXT — The ship method code and its decoded meaning from FND_COMMON_LOOKUPS.
• INTRANSIT_LEAD_TIME — The lead time for material in transit from the supply source.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, and VENDOR_SITE_CODE — Supplier identification details.
• GROUP_AVAILABLE_DATE — The date on which grouped supply becomes available; this is the column corresponding to the user search and is the principal availability-date attribute for reporting.
• GROUP_ATP_CHECK — Indicates the ATP check status or flag for the grouped supply.

Common Use Cases and Queries

Typical use cases include reporting on supplier-based supply availability by date, analyzing group-level ATP check results, and integrating supply source data into custom dashboards. A representative query retrieving grouped availability by organization is shown below.

SELECT organization_code, vendor_name, vendor_site_code, ship_method_text, group_available_date, group_atp_check FROM mrp_scatp_supply_sources_v WHERE organization_id = :org_id ORDER BY group_available_date;

For date-focused analysis, filter on the attribute captured in the user search:

SELECT schedule_group_id, atp_group_id, group_available_date, intransit_lead_time FROM mrp_scatp_supply_sources_v WHERE group_available_date BETWEEN :start_date AND :end_date;

Because the view relies on outer joins and validated EBS synonyms and views, it is safe for read-only reporting. Custom code should avoid DML against it and should observe organization-level access controls when querying across multiple inventory organizations.