Search Results source_org_supplier




Overview
Explore in AI Chat

Overview

APPS.MSC_FLP_SUPPLY_ATP_V is a supplementary database view in the Oracle Advanced Supply Chain Planning (ASCP) schema. According to the ETRM metadata, it is a VALID view owned by the APPS schema and registered under FND Design Data as MSC.MSC_FLP_SUPPLY_ATP_V. The view is classified as a "supplementary view used to simplify forms coding," a designation that carries an explicit Oracle warning: the view is not recommended for direct querying or data alteration, because its definition may change dramatically across minor or major releases. The acronym "FLP" in the object name refers to the Planner Workbench interface, while "ATP" (Available-to-Promise) indicates the view's role in exposing supply records relevant to ATP and scheduling decisions. The view presents plan supply data joined to item and organization context, making it convenient for application forms and, where sanctioned, for downstream reporting. Because the view consolidates supply, disposition, project, and source information, it serves as a denormalized read surface rather than a transactional object. It is not referenced by any other database object, confirming it functions as a top-level, forms-facing read view. Note also that SOURCE_ORG_SUPPLIER is exposed as a VARCHAR2(4000) column, which is relevant given the user search term.

Underlying Base Objects

The documented dependencies show that APPS.MSC_FLP_SUPPLY_ATP_V is defined over two synonyms and one package: MSC_SUPPLIES (SYNONYM), MSC_ITEMS (SYNONYM), and MSC_GET_NAME (PACKAGE). MSC_SUPPLIES is the core planning supply table in ASCP, containing planned and scheduled receipts such as purchase orders, work orders, and intransit shipments. MSC_ITEMS provides the item master context used for plan-level item resolution. The MSC_GET_NAME package supplies name resolution logic, likely used to derive human-readable values such as item/org descriptions or source labels exposed as VARCHAR2(4000) columns. The view therefore joins supply records to item definitions and enriches them with naming functions, producing a flattened, forms-friendly result set. The synonyms ultimately reference the underlying MSC tables in the same schema.

Key Columns

The view exposes twenty-two columns. Transaction and context identifiers include TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, PLAN_ID, and SR_INSTANCE_ID. Scheduling fields include ORDER_DATE, NEED_BY_DATE, and NEW_PROCESSING_DAYS. Quantity fields include SUPPLY_QUANTITY and NEW_ORDER_QUANTITY. Classification columns include ORDER_TYPE (numeric) and ORDER_NAME (VARCHAR2(4000)). The DISPOSITION and DISPOSITION_ID columns carry planning disposition values, while PROJECT_NUMBER, TASK_NUMBER, and BY_PRODUCT_USING_ASSY_ID support project and by-product attribution. Descriptive columns include ITEM_ORG, DESCRIPTION, and UNIT_NUMBER. SOURCE_ORG_SUPPLIER (VARCHAR2(4000)) indicates the supplying organization or supplier string for the receipt, aligning directly with the user's search term. All columns are non-mandatory in the metadata.

Common Use Cases and Queries

The view is used for reviewing plan supplies with item, organization, and source context. A representative query:

  • SELECT PLAN_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, ORDER_NAME, ORDER_TYPE, ORDER_DATE, NEED_BY_DATE, SUPPLY_QUANTITY, NEW_ORDER_QUANTITY, SOURCE_ORG_SUPPLIER, DISPOSITION FROM APPS.MSC_FLP_SUPPLY_ATP_V WHERE PLAN_ID = :plan_id AND ORGANIZATION_ID = :org_id ORDER BY ORDER_DATE;
  • Filtering by source: ... WHERE SOURCE_ORG_SUPPLIER IS NOT NULL;
  • Project-based review: ... WHERE PROJECT_NUMBER = :project_number.

Because Oracle explicitly discourages direct queries against this supplementary view, production reporting should preferentially target the underlying MSC_SUPPLIES and MSC_ITEMS objects or certified ASCP views. Where the view is used, results should be validated against patch-level changes.